“SAP” a world renowned organization or a parallel term for a business management software in IT lingo, is still not clear to many in the realms of that very business. It’s not the fault of the people or something wrong with the company’s branding strategy rather it’s a testimony to the reliance of the corporate world on this acronym. Everyday, I have my share of marvels at the intricacies of this tool, the thought process that would have gone behind each n every simple functionality it contains and the very vastness of it’s range.
I have recently entered this fascinating world of simplifying business processes through software. A few months back I was also one among the many of my batch mates scampering here n there for the answers to the query that what actually SAP ERP world is like? What do you mean by being a functional consultant in SAP? What will be my role involve? Queries were many but answers were few n that too made little sense given the limited rationality of fresh grad brain. Maybe this was because in this world of “Let’s Google this” it’s foolish to ask such questions or in this quest for simplifying businesses we have made such complex terms that it’s not easy for Masters to convey the real meaning of the word SAP to novices like me. So this blog is just an effort to put into words some of the learnings which I have learnt over the time, to be of some help to those standing at the same cross-roads as i once did.
Whatever I could gather in these few months about this “three lettered behemoth” is that it’s literally behemoth in terms of it’s vastness and sheer ability to cover diverse business needs. For starters it’s not for people who resist change and that goes for every technology centered product. But the point here is that one should be receptive of any new changes, be it in terms of the add-ons which are released for the standard modules or radical new products which are launched at regular intervals. A passion for continuously learning and re-learning is one trait which I believe is must in this field. The second attribute is patience. It takes perseverance to master a module and then to build on this knowledge of one to move to another. Why another? Because I believe it’s a maze of interconnected processes. You don’t know when a concept of finance module will come for role-play in materials module or when a Sales Order will be in a guest appearance in Purchasing scenario. So don’t be averse to the variety rather embrace it as a part of journey towards a holistic growth.
And now the basic question “What do I have to do actually?”. Well, the answer to this what I have figured out to the best of my knowledge is that first try to learn as much as possible about the module you are working on. What are the various functionalities it can be used for? How to configure a module for certain function? From which path I can generate the required transaction? Immerse yourself completely into it and learn the nitty-griity of the module. Then after that the next stage comes, when you understand the client’s processes and on the basis of the knowledge repository which you have acquired in your chosen art, you suggest to the client the ways to incorporate his company’s processes in the software. Here the art of simplifying processes comes into play and mind it this is not an easy art but still can be acquired if one is willing to go that Xtra mile!