After Event Recording (immediate repair process) using Confirm Job App
Introduction: Why After Event Recording is used by companies (immediate repair) ?
Many companies uses the After Event Recording process to record all the maintenance activities for immediate repair wise, please find below the information that can be gathered and registered in this process :
- Information regarding the technical object,
- Malfunction data (breakdown duration, damage, cause, etc.),
- Time confirmation,
- Spare part consumption information.
This process is used generally when we have a need to enter the maintenance data and the maintenance repair has already taken place.
As an example of this scenario, you have a forklift truck breaks down in transit or elevator in a building get stuck and you need to immediately repair the damage and enter the maintenance data afterward.
The proposed approach is to implement this scenario by using the Confirm Job App – W0020, the user will be able to use one App in single screen to record all the maintenance activities.
For more informations about the App, please refer to the FIori Library link: https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps(‘W0020’)/S17OP
Let’s discuss the process details and prerequisites.
Please note that the scenario is demonstrated in S/4HANA 1909 On-Premise system.
Prerequisites to use the App:
Before using the App, the user should be assigned to a maintenance planning plant in the user setting, otherwise the error below will be raised by the system Message no. EAMS_SP006 – Enter planning plant in user default settings.
Use the Tcode EAM_USER in the backend and assign the maintenance planning plant:
It’s also recommended to assign a maintenance notification type to a maintenance order type using the IMG activity below:
Plant Maintenance and Customer Service • Maintenance and Service Processing •Maintenance and Service Orders • Functions and Settings for Order Types • Define Notification and Order Integration.
We use the Confirm Job App for this scenario.
Step 1: create the maintenance order for the technical object:
With this step the notification will be created automatically using the notification type defined in the prerequisites.
Step 2: Time Confirmation:
Step 3: Goods Issue of spare parts consumed in the maintenance operations:
This step can be performed if the user has the authorisations to issue the goods, otherwise this step can be performed by the Warehouse Clerk using the App/Transaction MIGO.
Step 4 – Enter the malfunction data:
As the main aim of this scenario is to record the malfunction data to be able to do the breakdown and damage analysis, this step can be achieved by choosing the Malfunction Data tab as below :
Additional comments can be added as well in the comment tab.
If the activity is finished, the button Save and complete can be pressed.
DO NOT confuse with Emergency Maintenance process (scope item BH2):
Please note that this scenario is different from Emergency Maintenance Process proposed by SAP as a Best Practice Scenario (scope item BH2 Scope item BH2 ).
The major difference between the two processes is the the ability to plan and assign to the malfunction report a maintenance technician in the Emergency Maintenance Process (assigning the technician name and the planned number of hours).
The after event recording process can be implemented with the Fiori App, Confirm Job using single screen, this will drastically increase the usability of the system as the process will be simplified.
This process is different from the Emergency Maintenance process where the operations can be planned and assigned to the maintenance technician.