SAP® MM Plant Creation
Creation of material management plants in SAP system by executing around 30 transaction codes depending on the requirement.
Total efforts saved per execution: ~ 3 hours
Execution Interval: 8 times / week
Tool: UiPath
The inputs for this process were fetched from the Service Requests in Service Now. The request contained all the required information needed in order to create the requested plant in SAP. All the details were received in a predefined template in order to increase bot's stability, thereby also standardising the process.
This process was interesting in the sense that there were specifically four parts to this automation. The very first step was fetching input data and gathering other relevant details accordingly. Other steps were actually performing the necessary operations in SAP environments such as Development, QA and Production in that specific order. Once the predefined transaction codes were executed in one particular environment, reports were sent out to stakeholders for verification and approval. This process was also implemented using the same Ticket which was received initially (i.e.) the ticket was updated after each stage and was checked by the bot at every execution for any updates from the approver. Once the particular step was approved, the automation would further proceed and execute the following steps. This process repeated until the changes were finally moved to production.
There were many parts that were focussed on in order to make the end to end process error free by catching all possible scenarios of exception. A tracker was maintained and updated frequently with proper status to make sure none of the tickets are left unattended. All the temporary data of a ticket were saved in archives for a period of one month in order to keep track of the changes made in case of need.
The final output of this particular process was closure of ticket and notifying the stakeholders via email about the completion. It took almost five executions of the bot across three days to completely address one ticket due to the involvement of different team members at different stages of the process. This was a great success and implemented for other similar requirements.