SAP Plant Maintenance Processes
in S/4 HANA 1909
using FIORI APP
Request Maintenance
FIORI App
Only M1 and M2 as Notification TYpe selections
Set the Notification Types for the FIORI App here
Check detail settings
Only M1 and M2 was selected for Use in Request Maintenance App
Submit a Maintenance Request using Notification Type “M1”
Notification
10000090 created
IW28 (ECC and S/4 1909 similar transaction)
Notification created using the “Maintenance Request” FIORI App can be found in S/4 backend
the Notification in S/4 backend
OK
After OK button, FIORI App brings user to this screen which is a List of Notifications (including the new Maintenance Request”
Looks like a simplified view of the Notification
Looks like the same “List of Notification” that shows the newly created Notification when creating Maintenance Request via “Maintenance Request” FIORI App,
The “+” button will navigate to “Maintenance Request” FIORI App !!
The FIORI App was delivered with the Filter closed
Example, use date to filter,
click GO
The Simplified view of the Notification
No Notes
The Private Notes entered in IW32 do not show in the FIORI App
“Notes” entry section cannot be found ...
Document links are stored only in FIORI App
No Attachment List at the Backend Notification
Create Note
SAVE the Note
Not Private Notes but Notes in the Backend Notification can be seen in the FIORI App
Further process the Maintenance Request
Filter the Maintenance Request
No message if the Notification created via “Malfunction Report”
Unlike “Malfunction Report” App which generates Notification and Order at the same time;
the “Maintenance Request” App only creates the Notification
No noticeable features to convert the Notification to Order, but let's click “+” to add Work
Work added result in Maintenance Order generated
Plan for Hours
Plan for 5 hours
5 Hours Planned
MO created with “CRTD” status
with 5 hours planned
Note 21 Notifications
Further process the MO
Even this App do not show any further processing function (in this case Release the MO function does not seem available here)
Unlike Notification-Order directly created via “Malfunction Report” FIORI App which can Release the MO via the FIORI Apps
MO Released
2 > 3 after MO was released
Note Status “Ready for Work”
New Customizing in the S/4 backend:
IMG > PM/CS
> Maint.& Service Processing
> Fiori Apps …
> General Setting
> Assign Overall Status
(mapped S/4 backend Notification/MO system status to FIORI Malfunction report statuses)
Double-click
CONDITIONs
for the FIORI Status
FIORI Order Operation status “Ready for Work”
FIORI Order Operation status “Ready for Work” when S/4 MO set with Released System Status
Start Work
The “Start Work” Button sets the FIORI “Malfunction Report” to “IN Process” status
Next step possible is “Pause Work” or “Work is Done”
FIORI set “Start Work” adjust the Backend MO with System status JIPR
Note JIPR system status (for backend S/4 MO)
Note JIPR system status (for backend S/4 MO)
when
“IN Process” FIORI status in “Malfunction Report” FIORI App is logged via the “Start Work” button
Confirm Hours
Final COnfirmation
Note “Work in Done” status in the FIORI App
Note backend MO
shows
CNF and JBFI system status
Note in the IMG,
MO System Status “JBFI” when ….
Note in the IMG,
MO System Status “JBFI” when
….
“Work is DOne” is Logged
Also closed Notification
MO “TECO”ed and Notification “NOCO”ed
3 Job become 2 as the latest MO completed