STEP #1: There is a malfunction notification created in SAP ERP to conduct a pump inspection.
STEP #2: A maintenance planner releases the notification in SAP GUI to trigger the inspection process.
STEP #3: A technician from the service center, assigned to M2 notification, receives an email asking to carry out inspection. The email is generated and sent by Skybuffer SAP Add-on.
STEP #4: The technician goes to the pump location (somewhere out of the urban area) and makes a visual inspection.
STEP #5: The technician takes a photo of the pump.
STEP #6: The technician clicks the CREATE REPORT button in the email that is generated for him by Skybuffer SAP add-on when the M2 notification has been released.
STEP #7: The technician is typing a report on the mobile device.
STEP #8: When he finishes typing, the screen of the mobile device shows a regular email. You can see that UUID is used as the email subject, that is, alongside with the sender’s email account it is used in SAP to verify identity and authorize making changes to a particular M2 notification.
STEP #9: The technician sends the email to SAP.
STEP #10: The maintenance planner gets an email from SAP system at the very moment when the technician’s email reaches the SAP system and SAP captures the inspection report on the M2 notification level.
STEP #11: The maintenance planner sees the email on his mobile device and goes to his laptop to check M2 notification in SAP ERP via SAP GUI.
STEP #12: The maintenance planner opens SAP GUI and finds the M2 notification there.
STEP #13: The maintenance planner checks the inspection report via SAP GUI on M2 notification object level.
STEP #14: The maintenance planner is happy to see Skybuffer SAP add-on facilitate the business process and help decrease M2 notifications processing time and, for sure, save costs on M2 notifications processing.