Creating and Planning a Maintenance Task

Operators of technical assets, but also any employee who needs maintenance support can enter their maintenance request easily.

1. Request Maintenance

   This UI5 app can be used by all employees to request maintenance. Available notification types: M1 and M2.

2. Create Maintenance Notification

   This Web Dynpro app is used within the standard process to create a maintenance notification (all notification types of category 01 - Maintenance Notification can be used).

3. Create Maintenance Request

   This UI5 app is used in the phase-based processes to create a maintenance request. The notification type is preconfigured (Y1 in standard SAP).

4. Find Maintenance Notification

   You can use this UI5 app to search and find notifications based on a flexible filter.

You can use Web Dynpro apps Create Maintenance Order and Change Maintenance Order to create or change maintenance orders.

Further apps for order processing are:

• UI5 app Find Maintenance Orders to select orders based on a flexible filter.

• UI5 app Find Maintenance Orders and Operations to select orders and operations based on a flexible filter.

• UI5 app Manage Maintenance Notifications and Orders to select and process phase-based notifications and orders.

Similar to SAP ERP the S/4HANA system also offers the possibility to activate additional functionality via Business Functions.

Examples:

• Generating the Object List in the Maintenance Order

  LOG_EAM_SIMPLICITY_11, LOG_EAM_CI_12

• Copying Descriptive Texts from the Maintenance Order to the Purchase Requisition

  LOG_EAM_CI_12

• Mass Change of Additional Order Header Data and Customer-Specific Fields

  LOG_EAM_CI_12

• Specifying Default Settlement Rules for the Maintenance Order

  LOG_EAM_SIMPLICITY_12, LOG_EAM_CI_13

• Carrying out Mass Change in the Order and Operations List (SAP GUI transaction IW37N)

  LOG_EAM_CI_13

The procurement of internal material follows the usual steps and has not changed.

The PM-EWM (Extended Warehouse Management) integration establishes seamless flow between Plant maintenance, Inventory management, Logistics and EWM thereby enabling easy tracking of requested stock components across the end to end process.

The Recipient Location is introduced with this integration to easily identify the location where the intended recipient can receive the component. It can be assigned to one or more plants and it refers to a specific location in the warehouse or a common location between warehouses from where the stock components can be received. The Recipient Location is used to derive the staging area in EWM.

Since the components are stocked in a EWM managed warehouse, on posting a goods movement via transaction code MIGO or Pick List ie., transaction code MB26, a logistics outbound delivery document and an EWM outbound delivery order is created in the SAP S/4HANA system. The warehouse personnel ensure that the component(s) are made available in the intended recipient location by completing the warehouse tasks allocated to them.

1. Assign component in order operation:

   Stock material which is kept on stock in one of your EWM warehouses can be entered into the component view of the order operation using item category L.

2. Material Reservation with Recipient Location:

   Planning a stock material with item category L leads to a material reservation containing a Recipient Location. The Recipient Location is used to derive the staging area in EWM and can be created via transaction IRL01. In addition, it can be set as default value for each user (via transaction EAM_USER).

3. Outbound Delivery:

   On posting a goods movement (via transaction code MIGO / MB26) a logistics outbound delivery document is created in the SAP S4/HANA system.

4. Outbound Delivery EWM:

   On creating a logistics outbound delivery document in the SAP S4/HANA system an Outbound Delivery Order is created in EWM.

5. Pick / Pack / Load EWM:

   The necessary warehouse tasks are completed within EWM.

6. Goods Issue EWM for Recipient Location:

   The material is delivered to the specified recipient location.

The component line in the Plant Maintenance Order is not editable until the delivery is completed.

Actions such as:

• Deletion of a component

• Deletion of associated operation

• Rescheduling the Start and End date

Are not permitted on the PM Order having open delivery document associated with a stock component and appropriate error messages are issued in each case.

Delivery documents created using MIGO or MB26 transactions are not reflected in the document flow of the maintenance order. If for any reason the posting of goods issue or delivery document posting fails, the user has to resolve these errors using transaction COGI.

The procurement of external material follows the usual steps and has not changed.

There are two Procurement Modes available which can be selected in Customizing:

1. Enhanced Procurement Mode

2. Compatibility Mode ( = standard mode)

The Enhanced Procurement Mode enables the procurement of Lean Services.

Lean services are intended for the procurement of small or highly specialized services that are carried out by external suppliers as part of an internal or external operation. They can be maintained in the material master as service products. Service products have the product type group 2 and are delivered with the material type SERV in the standard system. Lean services can also be procured as enhanced limit items.

You can add lean services to an operation or suboperation as a component. You can either enter a planned lean service with the item category Non-stock item (N) or an unplanned lean service with the item category Enhanced Limit (E). Unplanned lean services are services for which the exact value is not known at the time of creating the purchase requisition. Instead of a fixed price, you can enter a value limit that must not be exceeded. The system checks the adherence to this limit when the work that has been performed is recorded in the service entry sheet for lean services.

The Compatibility Mode does not support lean service procurement but allows you to procure externally processed operations (control keys PM02 and PM03). The system default setting is the Compatibility Mode.

1. Create order operation with control key PM02:

   This will define an external operation with a service specification.

2. Enter a material of type Service into view Services:

   View Services is only available in the Enhanced Procurement Mode and only in the Web application.

3. Purchase Requisition:

   Depending on the order type, a purchase requisition is generated either when the order is saved or when it is released. The purchase requisition contains the service to be procured.

4. Order Release:

   Latest point in time when purchase requisition can be created. A standard purchaser is receives the purchase requisition.

5. Purchase Order:

   In purchasing a purchase order is created with reference to the maintenance order. The purchase order contains the service to be procured.

6. Service Entry (Optional):

   A service entry sheet is created for the purchase order. The services delivered are entered into the service entry sheet. After the final entry the service sheet has to be accepted.

7. Invoice Receipt:

   The invoice is entered with reference to the purchase order and will appear in the document flow of the order. Any invoice differences are automatically credited or debited to the maintenance order.

The procurement of external service External (Standard) follows the usual steps and has not changed.

The procurement of external service External (Service) follows the usual steps and has not changed.