Adapt a Maintenance Notification Type for Use in 9-Phase Maintenance Process of SAP S/4HANA Maintenance Management (On Premise)
With SAP S/4HANA Cloud 2011 and SAP S/4HANA 2021 FPS0, we delivered the 9 Phase Reactive and Proactive Maintenance Processes that provide a standardised and simplified process flow for the Maintenance Technician, Maintenance Supervisor and Maintenance Planner roles; These processes also come with new Fiori Apps that simplify the jobs of the related roles to a great extent.
In SAP S/4HANA Cloud, the standard content allows you to create new maintenance requests (aka maintenance notifications) of type Y1 by using the “Create Maintenance Request (F1511A)”. However, in the SAP S/4HANA On Premise world, you may want to either use a different notification type as per your business needs, or even change the behaviour of an existing notification type (M1) for usage in the 9–phase model of a maintenance process.
This blog explains how you can configure an existing notification type (such as M1) to be used in the 9-phase maintenance process in SAP S/4HANA on premise.
This blog is divided into 3 parts:
- Configuration settings
- SAP Fiori Launchpad settings
- Authorization settings
To enable an existing notification type for the 9-phase maintenance process, it is important to complete the following configuration settings:
In this document, we will modify the notification type M1 as an example.
Configure Settings for Notification Type
To configure the notification type, follow these steps:
- In your configuration environment, choose Plant Maintenance and Customer Service > Maintenance and Service Processing > Maintenance and Service Notifications > Overview of Notification Type.
- Select the notification type M1 (Maintenance Request) and then select Partner Functions, Approval.
- Select the checkbox Approval Required to indicate that the notification type needs approval.
- Select the checkbox Action Required if you wish to allow the maintenance supervisor to send the maintenance request back to the requestor if additional information is required to process the notification.
- Save the settings and exit from the activity.
Assign Notification Type to Order Type
To assign the notification type to an order type, follow these steps:
- In your configuration environment, choose Plant Maintenance and Customer Service > Maintenance and Service Processing > Maintenance and Service Notifications > Notification Creation > Notification Types > Assign Notification Types to Order Types.
- Select the notification type M1 and assign it to an order type, for example, YA01.
- Save the settings and exit from the activity.
Configure Overall Status Profiles
The overall status profile controls the flow of objects through the various phases and subphases. This configuration is mandatory and important to enable M1 to be used in the 9-phase maintenance process.
To configure overall status profiles, follow these steps:
- In your configuration environment, choose Plant Maintenance and Customer Service > Maintenance and Service Processing > Fiori Apps for Maintenance Processing > Configure Overall Status Profiles.
- Choose Assign Overall Status Profile for Notification Types.
- Create a new entry and enter the notification type as M1 and the overall status profile as PMSP1. The overall status profile PMSP1 (for reactive maintenance) is delivered as standard content.
- Choose Assign Overall Status Profile for Order Types.
- Create a new entry and enter the order type that was assigned to this notification type in the configuration activity Assign Notification Types to Order Types. Also assign the status profile PMSP1 to this order type.
- Save the settings and exit from the activity.
This concludes the configuration activities necessary to use the M1 notification type within the 9-phase maintenance process.
SAP Fiori Launchpad Settings
The current Fiori app Create Maintenance Request that is included in the business catalog SAP_EAM_BC_MREQ_MNG has the default notification type Y1 maintained in the tile configuration.
To be able to launch the app with notification type M1, a few enhancements to the tile configuration are needed. These changes must be done through the Fiori Launchpad Designer.
Define Target Mapping
To define the target application, follow these steps:
- Log in to the Fiori Launchpad Designer.
- Create a new business catalog called Z_TEST_M1_MREQ.
- At the bottom left section of the screen, search for the technical catalog SAP_TC_EAM_COMMON.
- At the right side of the screen where you can see all the tiles, switch to the second icon tab called Tiles.
- Search for Create Maintenance Request.
- Select the first item and choose the button Create Reference. In the catalog selection dialog, select the catalog that you created in step 2, that is, Z_TEST_M1_MREQ.
- Next, search for the app My Maintenance Requests.
- Repeat steps 6 and 7.
- Select the icon tab Target Mapping. Search for Create Maintenance Request and select the line item.
- Select Create Reference and repeat steps 6 and 7.
- Do the same for the My Maintenance Requests app too.
Configure Tiles in Custom Catalog
To configure the tiles in the custom catalog, follow these steps:
- In the Fiori Launchpad Designer, search for your custom catalog (as defined in step 2 of Define Target Mapping).
- Choose the second icon tab Tiles, and select the item Create Maintenance Request, and choose Configure from the footer.
- In the Tiles section, change the title to a name of your choice. This will be the text that appears when you view your tile on the launchpad.
- Save your changes. At this point, you will be informed that if you save your changes, the reference will be broken.
- Choose OK.
- Switch to the Target Mapping icon tab.
- Select the line item and configure it.
- In the section Parameters at the bottom of the screen, change the value for parameter NotificationType from Y1 to M1.
- Save the settings.
With these changes, you have created custom tiles and apps to display M1 notification type.
This is the last step towards enabling the maintenance notification type M1 in a 9-phase maintenance process.
If you have a single system that acts as the front-end and back-end server, then you must follow these steps. If you have separate front-end and back-end servers, you must repeat these steps, once in each server.
- Log in to the back-end system (+client).
- Execute transaction PFCG and edit the role that you may have created already.
- On the menu, select Insert Node that appears next to the Transaction button on the toolbar.
- Choose SAP Fiori Launchpad > Launchpad Catalog.
- If you have a separate front-end server, then in the pop-up choose Remote Front-End Server. (If you have the same server for front-end and back-end, choose the option Local Front-End Server and enter the catalog directly.)
- Select RFC Destination and enter the destination ID of the front-end system.
- In the field for the catalog, enter the name of the catalog that you created in step 2 of Define Target Mapping under the section SAP Fiori Launchpad Settings.
- Choose OK. (System will retrieve the catalog from the front-end repository and include it in the menu section of the PFCG role.)
- Now generate the PFCG role and log in to the Fiori launchpad with the user after assigning this role to the user.
You should be able to create a maintenance request for any notification type in the SAP S/4HANA On Premise landscape and make use of the same in the simplified 9 Phase Model Reactive Maintenance process
Interesting blog as we are just exploring these possibilities in an on-premise installation. However, in our system the PMSP1 status profile is not available. When you write that it is delivered as standard content, does that apply e.g. only to greenfield installations?
I searched the support system for notes that would deliver the configuration, but haven't found any.
This is part of standard content which is packaged in scope item 4HH - Reactive Maintenance. Reactive Maintenance is available from OP 2021 and if you have activated this scope item then you can see standard notification type Y1 and status profile PMSP1.
Hello can we use the create maintenance request app without the 9 phase process as well or is it restricted to use along with phase model activated ?
For now F1511A - Create Maintenance Request app is meant to be used for 9 phase process model.
Fantastic configuration document.
We are just starting to look at 2021 and this 9 PHASE process model has some merit. The only issue we have and I'm sure other long term SAP business would have is it is a massive change to the current business process using the older transactions. My challenge here is how to I deliver this new user friendly process so it runs in tandem with the current process. My first thoughts are to stay with the Y1 Notification type but how this will integrate with the current Work Order types will be a challenge.
Thanks again for the config steps.
Hi. Very helpful information. Could you please advise where to find item 4.Select the checkbox Action Required in Configure Settings for Notification Type. I don't see it available in the mentioned path. Thanks
You can refer https://launchpad.support.sap.com/#/notes/3195754 if Action Required flag is not enabled in your system.
Great post - thanks a lot!
There is an app called "Perform Maintenance Jobs".
This seems very useful but runs on "YA01" order type (phase model).
Is it possible to change the parameters for this app to example run order type "PM01"?
I will test this - was just wondering if you have tried that.
Hi, Perform Maintenance Job only works with orders that are enabled for the phase model. If PM01 is not enabled for phase model (through the flag called "Enabled for phase model" in Order type configuration) and if no Overall status profile is assigned to the order type, then an order of this type shall not be available in Perform Maintenance Job cockpit.
Thanks - all of those settings are already in place. My point is that the app "Perform maintenance job" by default only looks for order type "YA01" and I assume if we change the target mapping (as described in this blog), then maybe we could use the app for other than the order type YA01. I will however see if I can make it work - it could be very useful.