Customizing the Phase-Based Process

The following methods to adapt the process are available:

• Use Notification Processing Contexts

  (see lesson Initiation and Screening)

• Use Phase Control Codes

• Adapt the Overall Status Profile (f.ex. use Events)

• Configure Requirements for Creating Phase-Enabled Orders

Phase control codes allow you to control the transition between phases. If you activate a phase control code for a maintenance order for blocking a phase, the system will not allow you to transition to the phase until you deactivate the phase control code. Phase control codes can be activated for order headers and operations.

It is possible to control the validity of phase control codes. The business or legal requirements might have changed in a way that a previously configured phase control code becomes irrelevant. To depict this, you can determine the validity of a phase control code. You can indicate whether the phase control code is still valid (Valid), will no longer be used in future (Deprecated) or is an invalid entry (No longer valid).

You can adapt the sequence of phases and subphases and the way they control the process within the Overall Status Profile.

One way of doing this is to change the conditions which have to be fulfilled for a phase or subphase (i.e. modify the system status which must be set or must not be set for the transition into the next phase).

Another way of doing this is to configure events for specific subphases. This allows you to perform actions depending on self-defined conditions for a number of affected entities - such as the notification header or the order header.

The new Business Add-In (BAdI) BAdI: Processing of Phase-Enabled Maintenance Orders (EAM_CREATE_PHASE_ENABLED_ORDER) and the Customizing activity Define Requirements for Creating Phase-Enabled Orders (Customizing view V_EAM_NOTIFCNFG) allow you to determine whether maintenance requests need to be approved before phase-enabled maintenance orders can be based on them.

With the Customizing view V_EAM_NOTIFCNFG and this BAdI, you can determine different combinations of planning plants, notification types and order types for which you want to implement a business logic different from the SAP standard described above. On the level of the maintenance planning plant, you can determine for each combination of notification type and order type whether an accepted maintenance request is mandatory for creating the corresponding phase-enabled maintenance order.

If you have entered the corresponding data in the Customizing view, the BAdI is called in the following cases:

• You create a phase-enabled maintenance order in the Create Maintenance Orderapp.

• You create a phase-enabled maintenance order in the Manage Maintenance Notifications and Orders app.

• You create a phase-enabled maintenance order via the BAPI BAPI_ALM_ORDER_MAINTAIN .

Activate Business Feature for Phase Model

For using the Phase Model the Business Feature EAM_PHASE_MODEL_PROCESSING needs to be activated.

Notification Type

Define Notification Type for Phase Model (standard is Y1).

Approval Required / Action Required

Setting Approval Required is active for notification type Y1 by default. Function and status Action Required has to be activated separately for the notification type.

Event Prioritization

Event prioritization enables you to assess priorities based on consequence categories, consequences, and likelihoods, and to have the priority automatically calculated.

Detection Methods

With a detection method you can describe how a failure is discovered. It helps in determining the differences between failures that are detected during regular maintenance and failures that are casual occurrences.

Assign Notification Type to Order Type

The notification type (Y1) must be assigned to the order type (YA01).

Order Type

Define Order Type for Phase Model (standard is YA01).

Job Template for Material Availability Check

There are two templates available for EAM:

• SAP_PM_EAM_ATP_RIAUFK20 >Standard Template
• SAP_PM_EAM_MATL_AVAILY_CHECK >Extended Template for Phase Model

Monitoring Procurement Milestones

As a maintenance planner, you can monitor the procurement of non-stock components and external services in the SAP Fiori app Maintenance Backlog Overview. For this purpose, the system tracks the completion of several milestones in the procurement process such as Purchase Requisition Created, Purchase Requisition Released, Purchase Order Sent to Vendor, Order Confirmed by Vendor, Order Shipped, and Order Received in Full.

Rework Orders Card

Detect repetitive maintenance work during a given period of time.

Notification and Order Integration

The order type (YA01) must be linked to the notification type (Y1). In addition, the Assignment of Operations to All Object List Entries must be activated for the order type (YA01).

Functions

A function describes a task within a workflow based on which the approver is determined.

Function Profiles

A function profile groups similar functions.

Function Profiles and Team Categories

Function profiles need to be assigned to a team category. The standard team category for Asset Management is MAINT_P_E.

Functions and Roles

The team category together with the function must be linked to the corresponding role for the user in the backend system.

Standard Settings

The standard settings describe settings and system activities required for Workflows, which are to be performed on a client-specific basis.

Scenario Activation

Scenario WS02000019 - WFL_EAM_MO Workflow for Maintenance Order needs to be activated.

Scenario Definition

Assign scenario WFL_EAM_MO to consumer types Desktop, Mobile, Tablet. Also assign task type TS02000040.

Tasks and Decision Options

This activity allows you to maintain workflow tasks that need to be included in the task filter together with their names and decision keys (within the My Inbox app).

Overall Status Profile

In this configuration step, you can define:

• Status profiles with overall statuses that record the progress of repair work in the Fiori app Report and Repair Malfunction.
• Status profiles with overall statuses that record the progress of maintenance activities when active phase model for an order type is set.

Note

As of SAP S/4HANA 2023 FPS02 you can specify the Overall Status Profile for the combination of Order Type and Planning Plant.

Events

To adapt some steps within the Reactive Maintenance end-to-end process to your business needs, you can configure events for the respective overall status profile.

You configure an event for a specific subphase in a specific overall status profile. You specify the subphase that is to trigger the event in the field Overall Status. You then select the affected entity and the business transaction that the system is to execute.

Define Subphases and Map to Overall Statuses

Subphases allow you to abstract the overall statuses. You can define subphases for a phase and map the subphase to multiple overall statuses. This allows you to query and monitor the maintenance orders using phase and subphase.

Define Phase Control Code for Maintenance Orders

Phase control codes allow you to control the transition from one phase to another. You can define authorization keys for phase control codes.

Note

Phase Control Codes are configured in two steps:

1. Assign a user status profile for the combination of order type and entity (i.e. order header and order operation).

2. Define phase control codes for the combination of order type and entity (i.e. order header and order operation).

   Attention: when a phase control code is defined, a corresponding entry is made automatically in the user status profile assigned to order type and entity.

On the SAP Menu screen, choose

Tools→Customizing→IMG→Execute Project.

Choose button SAP Reference IMG.