Screen Maintenance Requests
Application component: Fiori UI for PM Maintenance Notifications
App type: Transactional
Line of business: Asset Management
Leading industry: Cross Industry
Solution capability: Maintenance Execution (S/4, Asset Mgr)
Description:  With this app, you can screen and accept maintenance requests. You can view status of a maintenance request along with other details such as priority of the maintenance request, breakdown and malfunction details, and so on. Note This app has been designed to be used within the functional scope of the Reactive Maintenance (4HH) and Proactive Maintenance (4HI) scope items that differs from how the maintenance process had been run before (based on the scope items BH1, BH2 and BJ2). Some of the features might not work in the same way or they might not work at all. Furthermore, not all the features of this Fiori app are available for maintenance orders of order types for which the phase model has not been activated. 
With this app, you can screen, accept or reject maintenance requests. You can view status of a maintenance request along with other details such as priority of the maintenance request, breakdown and malfunction details, and so on. You can also update the request or send it back to the initiator for additional information if necessary and accept for further processing.
Key features:  This app allows you to do the following:   Filter, group, or sort maintenance requests by various parameters such as planning plant, planner group, main work center, maintenance plant, technical object, location, and so on.   Filter maintenance requests according to the status.    Open: All maintenance requests that need to be screened are displayed.   Action Required: The maintenance requests that you sent back to the initiator to receive more information are displayed. By default, the Action Required button is available for Y1 notification. If you want it to be available for other maintenance notification types, you can see the information given in the SAP Note 3195754 . To enable the Action Required button, you need to select the Approval Required checkbox and then select the Action Required checkbox in the following configuration activity: Plant Maintenance and Customer Service  Maintenance and Service Processing   Maintenance and Service Notifications  Overview of Notification Type  Partner Functions, Approval.  After this configuration is maintained for a maintenance notification type, the Action Required button is shown in the Screen Maintenance Requests app. If you choose the Action Required button, the maintenance request will go back to the initiator and the initiator can review this request in the My Maintenance Requests app for further action. Note If the maintenance request originated from a third-party system or an API or from a maintenance plan, the Action Required button will not work even if the button is enabled.    Accepted: The maintenance requests that you reviewed and accepted are displayed. The accepted requests are sent for planning and processing.  Rejected: The requests that you rejected are displayed.  Completed: You can view all your maintenance requests that have been processed. Solution has been provided for these maintenance requests.     View details of the maintenance request such as priority, technical object, ABC indicator, superior functional location, failure mode, open maintenance requests, open maintenance orders, phase, subphase, and so on. Note The catalog type D (Coding) is used for defining failure modes in maintenance management. You can use the Edit Code Groups app to define failure mode groups and codes. In the Maintain Catalog Profile app, you can assign them so that they can be used in the maintenance requests.If catalog profile is not maintained for the technical object or the notification type, the failure mode is blank and the field is disabled. You cannot select a failure mode.   Generate output items using the Determine Output Items quick action button on the notification object page. If output items aren't yet available for a maintenance request, pressing the quick action button populates the output items table. If output items have already been generated, pressing the button again redetermines the output items depending on the parameters or status of the request. You can edit specific columns such as Dispatch Time, Output Type, Attachments, Channel and so on when the status of the output item is In Preparation and the maintenance request is in Open or Action Required subphase. Once the output is sent, it moves to the status To be Output and then to Completed when it is finally done. You can see the output preview from the icon in the Display column. For output items where the Dispatch Time is maintained as Scheduled, the application job, which runs in the background, picks and sends the output to the queue.Note To determine the output, the following prerequisites must be fulfilled:   Set up SAP S/4HANA output control. For more information, see Setup of SAP S/4HANA Output Control.   The application object type MAINTENANCE_NOTIFICATION must be active in the configuration activity Manage Application Object Type Activation.    Use quick views to get more information about open maintenance requests, technical objects, and maintenance orders. The quick view for a technical object allows you to quickly view important details about the equipment or functional location. It also allows you to navigate to the Display Technical Objects app where you can view additional details about the technical object.    View details of the technical object.   View hierarchy of functional location and equipment. If the functional location is an identifying level, the first hundred technical objects in the hierarchy are displayed which include superior functional locations and child technical objects. These are technical objects that are installed in the functional location. If it is not an identifying level it will show only superior functional location and not child technical objects. The hierarchy of functional location and equipment shown in this app is based on the second identifying level. The identifying level for a functional location is defined in the structure indicator that has for a functional location.  Only if the functional location is configured as an identifying level, the underlying technical objects will be shown in hierarchy. To verify this, in your configuration environment, use the search function to open the following activity Create Structure Indicator for Reference Locations/ Functional Locations. If you enter an equipment directly and select F4, the entire hierarchy of the equipment is displayed. This happens only for equipment and not for functional location. For better user experience, it is recommended that you use filters to search for a technical object.   Edit a maintenance request. If you have details that are missing or incomplete in the maintenance request, you can edit the request. You can update any information in the request to ensure that the request has all the details that is necessary to process it   Review and assign priority. You can also assess priority by selecting a combination of consequence categories, consequences, and likelihood. Prioritization profiles can be defined using the activity Define Prioritization Profiles. For more information, see How to Assign Priorities to Notification Types The priority defines the importance of the maintenance request. The priority helps to derive the key dates for a maintenance request such as the required start date, required end date, and the final due date.Note Without the priority, you cannot accept a maintenance request. Assume that you have selected priority for the maintenance request. If you update the technical object, the priority is also removed from the maintenance request. This happens only when the combination of maintenance plant and the notification type is different.  In the Create Maintenance Request app (F1511A) and the Screen Maintenance Requests app (F4072), when you remove a technical object or change the notification type, the priority that you selected for the technical object manually or by assessing the consequences and likelihoods is also removed. The assessment details of the priority are also deleted.   You can scan the bar code to enter a technical object or search for a technical object and select it. For better user experience, it is recommended that you use filters to search for a technical object.   Reassess the risk and redetermine the priority of the maintenance request. As a maintenance supervisor, you can manually change the final due date.   Review the details of the maintenance request and accept it. If the maintenance request has all details that are required for processing, you can accept it. The accepted request is available for planning and execution.  Reject a maintenance request. A rejected maintenance request cannot be edited or resent for screening.   During screening, if you require additional information to accept a maintenance request, you can send the request back to the initiator.   Change responsibility for the maintenance requests. You can select several maintenance requests and choose this button to set, overwrite, or clear the values of the responsibility-related fields, such as the main work center, main work center plant, planner group, planning plant, and the person responsible.   You can select one or more maintenance requests and accept or reject them.   The long text can have only 1333 characters. You cannot change the long text after it is saved.  If you add to the existing long text of a maintenance request, the changes (date, time, time zone, user ID, and business phone number) are saved.  The long text that you enter last will be seen first among the long texts.   Upload documents related to the maintenance request which have information related to the maintenance request and will help the processor to provide quick resolution. You can upload a document, add a link or assign an existing document to the maintenance request. Two predefined document types are available – YP1 and YP2. If you configure a document type in the configuration activity Define DMS Document Types (ID 101090), the document type that you define will be available for selection in the dropdown list.   Assign task lists to a maintenance request.   
Business roles: Maintenance Supervisor
Maintenance Supervisor : 
Collects, reviews, and prioritizes all maintenance requests from different sources and ensures that they contain all the relevant information required so that the problems can be solved quickly.