There are several methods of obtaining solutions to SAP issue, depending upon the type of issue.
Initially when I started learning SAP, way back in 1999, the objective was to first understand the fundamentals of ERP and what it stood for.Those were the days when old programs like Dbase,Foxpro,COBOL etc were used. We spent a lot of time to create even a single report and integration was something unheard of.Our MM department had their own software running inventory and PSL or Priced Store Ledger.Today it's called Material Ledger. They had to talk to the Finance department to know if any payment has been made or any statement of outstanding is available.
Once we started implementing SAP, we realized that it integrates the functions of several departments seamlessly,thus eliminating redundant data-entry and resultant errors.But like any beginner,we made a lot of mistakes and left it to the support guys to rectify the same.The business colleagues also felt that SAP is magic and will provide solutions to all their issues.Most of them actually showed disappointment after the initial expectations.
After 3 or 4 implementations under my belt I realized that the more you learn the less you have actually learnt and achieved. I understood the meaning a of what a great thinker who once remarked:"Strange how much you should know before you know how little you know".Today after 13 years, 10 implementations, 20 rollouts and multiple upgrades, I feel as if I have just started my SAP career.The product evolves continuously, is upgraded,enhanced and updated.so much so that a trainee is able to tell you more about it than what you knew.
But one of the most common issues faced by all SAP consultants is error-handling. With this in view, I have decided to create a blog focusing exclusively on error-handling with illustrations.
I request everyone to absorb the contents and provide your valuable feedback so that we can continuously improve and contribute with greater sense of satisfaction.After all, the process of learning never stops.
Tuesday, December 11, 2012
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment