Implementation of the Phase Model
Note
Please note that the best method to implement the phase model is the use of the Best Practices and the pre-configured content of scope items 4HH, 4HI, 4VT and 4WM. This will allow an automatic customizing.
If you cannot use the Best Practices scope items, you can configure the phase model manually. However, this will result in a much bigger effort.
Business Feature
- Activate Business Feature for Phase Model
For using the Phase Model the Business Feature EAM_PHASE_MODEL_PROCESSING needs to be activated.
Notification
- 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
- 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).
Teams and Responsibilities
- 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.
Workflows
- 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 and Phases
- 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.
- 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.
Customizing Paths for the Phase Model
Access to Customizing
On the SAP Menu screen, choose
Tools → Customizing → IMG → Execute Project.
Choose button SAP Reference IMG.
Business Feature
| Field Name or Data Type | Path |
|---|---|
| Business Feature | ABAP Platform → → Application Server → Business Management → SAP Business Feature → Activate Business Feature |
Notification
| Field Name or Data Type | Path |
|---|---|
| Notification Type | Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance and Service Notifications → Notification Creation → Notification Types → Define Notification Types |
| Approval Required / Action Required | Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance and Service Notifications → Overview of Notification Type → Partner Functions, Approval |
| Event Prioritization – Consequences and Likelihoods | Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance and Service Notifications → Notification Processing → Response Time Monitoring → Event Prioritization → Define Consequences Categories, Consequences, and Likelihoods |
| Event Prioritization – Prioritization Profiles | Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance and Service Notifications → Notification Processing → Response Time Monitoring → Event Prioritization → Define Prioritization Profiles |
| Detection Methods | Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance and Service Notifications → Notification Creation → Notification Content → Additional Functions for Notification Types → Define Detection Methods |
| Assign Notification Types to Order Types | Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance and Service Notifications → Notification Creation → Notification Types → Assign Notification Types to Order Types |
Order
| Field Name or Data Type | Path |
|---|---|
| Order Type | Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance and Service Orders → Functions and Settings for Order Types → Configure Order Types. |
| Template for the Material Availability Check | ABAP Platform → Application Server → System Administration → Activation of Scope-Dependent Application Job Catalog Entries |
| Activate Event Type Linkage for Procurement Milestones | Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance and Service Orders → Functions and Settings for Order Types → Procurement → Activate Event Type Linkage for Procurement Milestones |
| Define Assignment Rules for Procurement Milestones | Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance and Service Orders → Functions and Settings for Order Types → Procurement → Define Assignment Rules for Procurement Milestones |
| Define Notification and Order Integration | Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance and Service Orders → Functions and Settings for Order Types → Define Notification and Order Integration |
| Rework Orders Card (in Maintenance Backlog Overview) | Plant Maintenance and Customer Service → Information Systems for Plant Maintenance and Customer Service → Define Order Parameters for Rework Analysis |
Teams and Responsibilities
| Field Name or Data Type | Path |
|---|---|
| Define Functions and Function Profiles | Cross-Application Components → General Application Functions → Responsibility Management → Functions → Define Functions and Define Function Profiles |
| Assign Functions to Template Roles | Cross-Application Components → General Application Functions → Responsibility Management → Teams and Responsibilities → Team Categories → Validate Team Members → Assign Functions to Template Roles |
| Assign Function Profiles to Team Category | Cross-Application Components → General Application Functions → Responsibility Management → Teams and Responsibilities → Team Categories → Assign Function Profiles to Team Category |
Workflows
| Field Name or Data Type | Path |
|---|---|
| Standard Settings | ABAP Platform → Application Server → Business Management → SAP Business Workflow → Maintain Standard Settings |
| Activate Workflow Scenario | ABAP Platform → Application Server → Business Management → SAP Business Workflow → Flexible Workflow → Scenario Activation |
| Maintain Scenario Definition | ABAP Platform → SAP Gateway Service Enablement → Content → Task Gateway → Task Gateway Service → Scenario Definition |
| Maintain Task Names and Decision Options | ABAP Platform → SAP Gateway Service Enablement → Content → Workflow Settings → Maintain Task Names and Decision Options |
Overall Status Profile
| Field Name or Data Type | Path |
|---|---|
| Overall Status Profile | Plant Maintenance and Customer Service → Maintenance and Service Processing → Fiori Apps for Maintenance Processing → General Settings → Configure Overall Status Profiles |
| Phases and Subphases | Plant Maintenance and Customer Service → Maintenance and Service Processing → Fiori Apps for Maintenance Processing → General Settings → Define Subphases and Map to Overall Statuses |
| Phase Control Codes | Plant Maintenance and Customer Service → Maintenance and Service Processing → Fiori Apps for Maintenance Processing → General Settings → Define Phase Control Code for Maintenance Orders |
Maintenance Events and Revisions
| Field Name or Data Type | Path |
|---|---|
| Maintain Revision Type | Plant Maintenance and Customer Service → Maintenance and Service Processing → Maintenance Event Builder → Maintain Revision Type |