ERPs and Excel-based tools – friend or foe?
DILBERT ? 2016 Scott Adams. Used By permission of ANDREWS MCMEEL SYNDICATION. All rights reserved.

ERPs and Excel-based tools – friend or foe?

ERPs sometimes generate frustration … and lots of spreadsheets!

No matter how much effort you put in building and deploying the optimal ERP solution, you will always be confronted with two things:

  1. Whatever its level of customization, your ERP solution will always leave “functional orphans” with gaps for certain business units or user groups, who will be unsatisfied
  2. Whatever the change management effort you put into your deployment, you will always witness the persistence or creation of shadowy Excel files (or even ‘factories’ some say), which users cling to obstinately to perform their daily tasks

Observation 1 may be tagged a necessary evil on the path to a controlled and efficient ERP deployment - It has been demonstrated and is now commonly accepted that to keep your initially planned ROI for your solution, you should focus it on your essential business processes and avoid too many customizations, which lead to unexpected additional costs both in the short and longer terms.

Observation 2, which is somehow a by-product of observation 1, should be used as a guide to further productivity gains and insights for innovation.

Let me be clear, not all ‘Excel factories’ and silos are a good thing. Some of them clearly bypass the ERP and standard process from a lack of knowledge (or training?) and contribute to the parallel maintenance of conflicting data which may lead to improper business decision-making. These ventures are easily recognizable as they generally make-up or reproduce the inputs from the ERP and produce similar output information, except that they do it in a different (wrong?) way – consuming significant resources in the process.

Manage the pipeline

Most of the time however, users spend significant amounts of time feeding their Excel model and manipulating it because they want to achieve a result, superior to that achievable trough the use of the standard ERP functionalities. It could be:

  • merging data from several scattered ERP systems allowing a better consolidated vision
  • adding a twist to usual data visualization, allowing for further optimization in the business process
  • or – best-case scenario - calculating or simulating new trends necessary to improve decision-making on key business items

Both functional experts and IT teams should regularly follow on their internal creative excel geeks and users as they would on a pipeline of potential ideas for innovation. Some of those ideas can prove to be quick wins for the organization: if it proves fundamental to the company’s business advantage, it should maybe worth it to consider how to secure or improve it, or to reinforce a potential business case for future IT investments.

Improve and secure the spreadsheet-based processes

Not all those ideas will qualify for a customization of your core ERP solution of course, and there are many ways available today to improve Excel-based processes at a fraction of the cost of a specific development:

  • automate data retrieval from your core ERP system to Excel – copy-paste or manual input processes generally are resource-intensive and produce the highest proportion of error within a spreadsheet
  • guide the consolidation/calculation/simulation process by reinforcing your Excel model with code
  • automate data upload and synchronization back to your core ERP if the results are used as inputs in other processes
  • organize the sharing and distribution of your Excel model, preventing unwanted modifications or manipulations, yet allowing for frequent updates if necessary

I wouldn’t risk labeling it the ‘agile part of your bimodal IT’, but Excel-based processes are, in essence, reactive and flexible, and overwhelmingly owned by business and functional experts – why risk stifling this potential innovation? All the more so considering that fixing the usual issues found in them is no longer insurmountable. Nor costly. From the points listed above, we contend that the vulnerability, manual data entry, version management and sharing issues, which were commonly and rightly quoted as Excel limitations, can now be tackled effectively. We have a track record of successful client projects to attest to it at XSBS – and a modular solution which can help your organization simply overcome the usual friend-or-foe paradigm.

I would add, the Excel functionality is a good tool for mitigating the data. Once a report format is chosen for making corporate decisions, it should continue to follow the SDLC by becoming an SSRS or similar report. If normal IT regulations follow, the report becomes documented, it now has support even after the originator leaves, it has the ability to transform as the company changes, it can now relate the history of changes and why, and becomes a starting point for the next manager or corporate lead. Too many times the root knowledge reports that drive a company are lost when an individual leaves.

John Barry

Global Vice President, SAP Strategic Alliance at BlackLine

7 年

little known fact - i went to the same college as Dilbert author Scott Adams. He fared slightly better but the race is not run yet....and yes, xls still a huge risk in the financial close. we both know that;)

David Herd FCCA, MAAT, Prince2

Director Amey Business Services. Shared Business Services Leader & Consultant Practitioner, Finance Professional, Change Management, Lean CI

7 年

About right then! ha ha

回复
Colin Glass

Consultant Finance

7 年

There is a space somewhere between a spreadsheet and database and it is beginning to be occupied by addin tools and even AI. Good old Dilbert!

Sharon Morley FCICM (grad)

Senior Credit Control Manager - Beazley

7 年

Hilarious!

回复

要查看或添加评论,请登录

Daniel Lellouche的更多文章

  • Optimization, so good, so tough!

    Optimization, so good, so tough!

    (*) If you like this article, “Like” it, “Repost” it, “Comment” it, we grow by exchanging opinions! Not only a title…

    1 条评论
  • Throwing a new light on MRP results

    Throwing a new light on MRP results

    Over the last 50 years, MRP engine has been the most used program in Supply Chain, to calculate replenishments. On one…

    2 条评论
  • DOWAP releases IBP-AT for SAP-IBP

    DOWAP releases IBP-AT for SAP-IBP

    Since SAP-IBP launch time in 2012, DOWAP conducts permanent Fitgap analysis between customer requirements versus SAP…

  • Demand balancing: from requirement to solution!

    Demand balancing: from requirement to solution!

    Sometimes ago, I wrote an article on Inventory Balancing & Optimization which is a solution we specifically developed…

  • SAP IBP Business rule modeling

    SAP IBP Business rule modeling

    Foreword I recently wrote an article about SAP-IBP solution which opens a new era in Advanced planning system so called…

    5 条评论
  • Inventory balancing & Optimization within SAP-ECC or APO

    Inventory balancing & Optimization within SAP-ECC or APO

    Did you ever think your company had a good supply chain set up, its Supply Chain processes were nicely implemented…

    10 条评论
  • Why is Supply Chain so using Excel?

    Why is Supply Chain so using Excel?

    Many statistics report majority of SCM users keep on working in Excel several times a day if not constantly. I read…

    1 条评论
  • SAP software like IBP revealed up with Excel & XSBS!

    SAP software like IBP revealed up with Excel & XSBS!

    My recent post https://www.linkedin.

    2 条评论
  • SAP IBP, a new ERA!

    SAP IBP, a new ERA!

    Foreword Thru this article I wish proposing the reader a quick and instructive tour about SAP-IBP, whereas comparison…

    18 条评论
  • Safety Stock, c'est quoi?

    Safety Stock, c'est quoi?

    Introduction S’il est des sujets récurrents dans les magazines de Supply Chain, celui du safety stock détient…

    3 条评论

社区洞察

其他会员也浏览了