7/16/2023

Maintenance Management
Generated on: 2023-07-16 07:10:01 GMT+0000

SAP S/4HANA | 2022 Latest

PUBLIC

Original content: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/e72f747389b340229f7fa343975bfa57?locale=en-

US&state=PRODUCTION&version=2022.002

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
 7/16/2023

Maintenance Management

Apps for Maintenance Management

Mass Schedule Maintenance Plans

Use
As a maintenance planner, you can use this app to schedule all maintenance plans that are due within a speci c time frame. This
simpli es the creation of maintenance call objects for maintenance plans, especially if you need to schedule large numbers of
maintenance plans.

For each scheduling run, the system goes through all the maintenance plans taking parameters such as maintenance strategies
and counter readings into account to calculate the due date. It then generates a maintenance call object, for example a
maintenance order, for each due maintenance item. Which object the system generates is determined by the maintenance plan
category. Furthermore, you can control special scheduling requirements using the scheduling parameters in the maintenance
plan.

Additionally, the following data is taken into consideration during scheduling:

For performance-based or time-based strategy plans: the maintenance strategy

For single cycle plans: the maintenance cycles de ned in the maintenance plan

For multiple counter plans: the maintenance cycles de ned in the maintenance plan

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

You can view a list of all maintenance plans already scheduled within a certain time frame and navigate to the job results.

You can generate new maintenance calls and call objects:

Choose a job template and enter a job name.

Specify the scheduling options:

Specify the date and time for the system to start the scheduling. You can also decide to start the scheduling
immediately.

Add more scheduling options such as the calendar, or whether maintenance plans shall only be scheduled on
working days.

Enter a recurrence pattern to specify how often the scheduling job is to be processed. You can run the job daily or
even several times a day.

Specify the maintenance plan options:

Enter a time frame within which the maintenance calls and call objects should be generated.

Use parallel processing for the automatic scheduling of maintenance plans.

This is custom documentation. For more information, please visit the SAP Help Portal 2
 7/16/2023
You then can specify the number of parallel processes and which application servers can be used to what extent.

Specify additional selection parameters for the maintenance plan, such as the technical object or the main work
center.

Specify additional selection parameters for the technical object, such as the planning plant or the maintenance
planner group.

Supported Device Types

Desktop

Tablet

Technical Object Breakdowns

With this app you can analyze the causes of a particular breakdown more closely and calculate the distribution of duration of the
various breakdowns or repairs. You can also nd out the cause behind a short or long breakdown period, or the period between
two consecutive breakdowns.

Key Features
View the number of effective breakdowns. You can also lter noti cations and technical objects that are reviewed to
evaluate their reliability.

 Note
Due to complex algorithm, it may take few seconds for the main chart and table area to be displayed.

With the lters, you can restrict technical objects to reduce the time it takes to generate the report. You can create
variants with mandatory lter Maintenance Plant and other optional attributes such as main work center, planning
group, equipment type, catalog pro le, and so on. These variants can be reused.

View effective time between repair and effective time to repair, as well as mean time between repair and mean time to
repair for every breakdown or repair activity

Filter breakdowns based on various criteria, such as object type or planning plant

View leading noti cations and perform any drilldown as needed

Identify the possible functional location where an equipment has failed

Drill down to various dimensions, such as maintenance noti cation, maintenance order, or technical object to get
detailed information about the repair work performed

This app uses the c_maintobjbreakdownquery CDS view.

 Note
This analytical app only takes current data into account. Archived or deleted maintenance noti cations are not considered.

Supported Device Types

Desktop

Tablet

This is custom documentation. For more information, please visit the SAP Help Portal 3
 7/16/2023

Technical Object Damages

With this app, you can see which damages occur frequently and nd the technical object parts that cause them. You can nd the
related maintenance noti cations in the list which is based on maintenance items. You can lter the tables and charts and
navigate to the related applications.

Key Features
View the number of damages as a chart or table. You can also lter noti cations and technical objects that are reviewed
to evaluate their reliability.

 Note
Due to complex algorithm, it may take few seconds for the main chart and table area to be displayed.

With the lters, you can restrict technical objects to reduce the time it takes to generate the report. You can create
variants with mandatory lter Maintenance Plant and other optional attributes such as main work center, planning
group, equipment type, catalog pro le, and so on. These variants can be reused.

View the number of causes, activities, and technical object parts in the Key Performance Indicator (KPI) tags and cards

Filter damages based on various criteria, such as Maintenance Plant, Object Type, Construction Type, and Catalog
Pro le

View damages based on object part code groups and drill down as needed

Identify the functional location where a piece of equipment has been damaged

Drill down to various dimensions, such as maintenance noti cation and technical object, to get detailed information
about the repair work performed

This app uses the c_damageanalysisquery Core Data Services (CDS) view.

 Note
This analytical app only takes current data into account. Archived and deleted maintenance noti cations are not considered.

Supported Device Types

Desktop

Tablet

 Note
Please note that KPI tags may not show up for tablets.

Maintenance Backlog Overview

With this app, you can view information about maintenance (request and order) backlogs for a series of planning buckets that
have been created from a single reference planning bucket. To display information in the app, you rst select a range of planning
buckets by choosing a planning bucket template, a number of planning buckets in the past, and a number of planning buckets in
the future. The analytical cards and quick view cards provide different kinds of information about the selected planning buckets.
Both card types let you navigate from the card view to other relevant applications. Note that the Phase lter that is available in
the selection area is only applicable for the Maintenance Backlog card.

This is custom documentation. For more information, please visit the SAP Help Portal 4
 7/16/2023
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.

Key Features
The following cards are available in this app:

Maintenance Backlog Card

The Maintenance Backlog card contains a stacked bar chart that shows the total number of phase-enabled maintenance
requests and maintenance orders in each of the selected planning buckets. You can display the chart data by phase,
maintenance activity type, order and noti cation type, or priority. When you select one of these categories in the dropdown
menu of the card, the X-axis represents the selected planning buckets and the Y-axis shows the number of maintenance
requests and orders arranged according to the selected category. If you select one or more phases in the selection area, the
system only displays maintenance requests and orders in the selected phases.

Depending on the selected category, the chart offers the following navigation options:

If you choose By Maintenance Activity Type, By Order and Noti cation Type, or By Priority, you navigate to a pre-
ltered list of information in the Manage Maintenance Noti cations and Orders app.

If you choose By Phase, the navigation is as follows:

Navigation By Phase

Maintenance Phase Target Application

Initiation (01) Maintenance Supervisor: Screen Maintenance Requests

Maintenance Planner: Display Maintenance Noti cations

Screening (02) Maintenance Supervisor: Screen Maintenance Requests

Maintenance Planner: Display Maintenance Noti cations

Planning (03) Manage Maintenance Noti cations and Orders

Approval (04) Manage Maintenance Noti cations and Orders

Preparation (05) Manage Maintenance Backlog

Scheduling (06) Find Maintenance Orders

 Note
If you have enhanced the core functions of SAP S/4HANA
with an additional license for Resource Scheduling, the
target application is the Manage Work Center Utilization
app.

Execution (07) Find Maintenance Orders

Post Execution (08) Find Maintenance Orders

Completion (09) Find Maintenance Orders

This is custom documentation. For more information, please visit the SAP Help Portal 5
 7/16/2023

 Note
If a chart section represents only a single order or noti cation, the application opens the object page of the order or
noti cation.

If you click on the card header, you navigate to the Manage Maintenance Backlog app. By default, the backlog for the
rst planning bucket in the chart is displayed.

Maintenance Orders Card

The Maintenance Orders card allows you to view the number of all maintenance orders in each of the selected planning buckets.
By clicking on a bar in the chart, you can display the orders in the Manage Maintenance Backlog app.

External Procurement Card

The External Procurement card supports you in proactively preparing your maintenance orders and ensuring streamlined
scheduling and execution of maintenance work. The card shows the total number of non-stock components and services for
which a procurement activity is due within the time period of each selected planning bucket – even if the corresponding
maintenance orders fall into different planning buckets based on their scheduled start and end. The card shows the following
procurement activities:

Create Purchase Requisition

Release Purchase Requisition

Send Purchase Order to Vendor

Receive Purchase Order Con rmation

Receive Shipment Con rmation

Receive Delivery

The system considers the non-stock components and lean services in all planning buckets that have been generated from the
selected planning bucket template. Each bar covers the time period of the respective planning bucket, but the rst bar and the
last bar may cover additional planning buckets:

The rst bar covers the time period of any further planning buckets that have been generated from the template in the
past.

The last bar covers the time period of any further planning buckets that have been generated from the template in the
future.

The different chart sections offer the following navigation options:

Procurement Activity Target Application

Create Purchase Requisition Manage Components and Services

Release Purchase Requisition Procurement for Maintenance Planner (Purchase Requisition)

Send Purchase Order to Vendor Procurement for Maintenance Planner (Purchase Requisition)

Receive Purchase Order Con rmation Procurement for Maintenance Planner (Purchase Order)

Receive Shipment Con rmation Procurement for Maintenance Planner (Purchase Order)

Receive Delivery Procurement for Maintenance Planner (Purchase Order)

This is custom documentation. For more information, please visit the SAP Help Portal 6
 7/16/2023
For more information, see Monitoring Procurement Activities.

Rework Orders Card

The Rework Orders card enables you to detect repetitive maintenance work during a given period of time. This helps you to
avoid issues that could result in equipment failure. In general, if an order has been technically completed and another order of
the same order type is created for the same technical object within a speci ed period, this new order can be considered as a
rework order, depending on how you have con gured the rework analysis.

To enable the system to display rework orders and to de ne the criteria that the system uses to identify these orders, you need
to maintain the relevant parameters in Customizing for Plant Maintenance and Customer Service under Information
Systems for Plant Maintenance and Customer Service De ne Order Parameters for Rework Analysis . For more
information, see the Con guration Tasks section under App Implementation: Maintenance Backlog Overview.

The Rework Orders card contains a stacked bar chart that provides information about outstanding rework orders per planning
bucket. The X-axis represents the selected planning buckets, and the Y-axis represents the number of rework orders
aggregated by maintenance activity type. From each of the chart sections, you can navigate to the Find Maintenance Orders
app to view the list of rework orders.

Quick Links Card

The Quick Links card allows you to navigate to other relevant applications for managing your maintenance orders.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
App Implementation: Maintenance Backlog Overview
Manage Maintenance Planning Buckets
Manage Maintenance Backlog
Manage Components and Services
Find Maintenance Orders
Find Maintenance Orders and Operations
Manage Maintenance Noti cations and Orders

App Implementation: Maintenance Backlog Overview

Prerequisites
Some features of this app are only available for maintenance noti cations and maintenance orders that are processed
according to phases. Before implementing the app, we strongly recommend that the scope items 4HH (Reactive Maintenance )
and 4HI (Proactive Maintenance ) are active in your system, or you have con gured the phase model in Customizing the same
way as it is delivered for these scope items.

Required SAP Notes

This is custom documentation. For more information, please visit the SAP Help Portal 7
 7/16/2023
For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-End Server 3200004 SAP S/4HANA 2022 SPS 02: Release

Information Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2022 SPS
02: Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library here.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (0001) EAM_MAINT_PLANNER_OVERVIEW_SRV

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application EAM_BCKLG_MONS1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

This is custom documentation. For more information, please visit the SAP Help Portal 8
 7/16/2023
Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

EAM_MAINT_PLANNER_OVERVIEW_SRV You can use the example business catalog Use one of the existing roles:
(0001) SAP_EAM_BC_PLNBKTS_MNG or your
SAP_BR_MAINTENANCE_PLANNER
custom catalog to create the back-end
PFCG role. SAP_BR_MAINT_SUPERVISOR

Con guration Tasks

To ensure that some of the cards can display information correctly, you need to perform the following con guration tasks in your
backend system:

External Procurement Card

The completion of several procurement activities depends on changes in the purchase order and, for non-stock components, the
posting of the goods receipt. To enable the system to react to these changes and update the chart on the External
Procurement card, several event type linkages must be activated in your system. For more information, see Procurement
Milestones.

Rework Orders Card

To enable the system to display information on the Rework Orders card and to de ne the criteria that the system uses to
identify rework orders, you need to maintain the following parameters in Customizing for Plant Maintenance and Customer
Service under Information Systems for Plant Maintenance and Customer Service De ne Order Parameters for Rework
Analysis :

Under Order History (in Days), specify a time frame for the analysis. Enter a number of days in the past to determine the
period of time in which technically completed orders are considered for the rework analysis based on their reference
date.

Under Order/Activity Type, specify one or more combinations of order type and maintenance activity type that you want
the system to consider when identifying rework orders.

Related Information
Maintenance Backlog Overview

Maintenance Planning Overview

This app supports you in the planning and execution of your maintenance work and allows effective monitoring of important,
time-sensitive process steps. According to selection criteria that you have de ned, the system analyzes critical factors in a
chosen reference period, such as, for example, open or outstanding maintenance noti cations that have not yet been assigned,
missing spare parts or overdue orders. Different cards display the results in gures and colored charts and allow you to

This is custom documentation. For more information, please visit the SAP Help Portal 9
 7/16/2023
navigate to lists in which you can edit the documents that have been identi ed as critical or contact persons responsible. You
can use this app to analyze, for example, which maintenance orders have not yet been released, which spare parts will possibly
not be able to be procured and made available on time, or which maintenance orders have not yet been nally con rmed
although the end date has already passed.

Key Features
If you have the maintenance planner user role, you can use the following functions:

Analyze outstanding noti cations that have not yet been processed and that have not yet been assigned to a
maintenance order

Analyze maintenance orders that are still in planning and have not yet been released for processing

Analyze purchase requisitions or purchase orders that have not yet been released for non-stock materials that are
required as spare parts in maintenance orders

Display approved purchase requisitions for non-stock materials for which no purchase order has been generated

Display non-stock materials that have been ordered but may not be available on the requirement date

Analyze released maintenance orders whose end date is in the past and have still not been nally con rmed

Analyze con rmed maintenance orders whose required end date lies in the selected reference period but have neither
been completed technically, nor from a business perspective

Supported Device Types

Desktop

Tablet

Smartphone

Procurement for Maintenance Planner (Purchase Requisition)

With this app, you can view a list of all purchase requisition items that have been created for your maintenance orders and
display key procurement information. You navigate to this app via the Purchase Requisitions Not Approved card or the
Purchase Requisitions Not Converted to Purchase Orders card in the Maintenance Planning Overview app. If you process your
maintenance orders by phases, you can also access this app via the External Procurement card in the Maintenance Backlog
Overview app.

Key Features
This app provides the following key features:

View a pre ltered list of purchase requisitions, for example purchase requisitions which have not yet been approved. The
prede ned lter settings depend on how you navigate to this app.

Filter the list of purchase requisition items, for example by orders in a speci c maintenance planning bucket, pending
procurement activities, and other criteria.

View relevant procurement information, such as the release status of the purchase requisition and information about
the requested product, the supplier, the requirement date, as well as the purchase order and purchase order item.

Branch to individual purchase requisitions or purchase requisition items.

This is custom documentation. For more information, please visit the SAP Help Portal 10
 7/16/2023
Branch to the product master data of the requested products.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
Maintenance Planning Overview
Maintenance Backlog Overview

Procurement for Maintenance Planner (Purchase Order)

With this app, you can view a list of all purchase order items that have been created for your maintenance orders and display
key procurement information. You navigate to this app via the Purchase Orders Not Approved card or the Missing Components
card in the Maintenance Planning Overview app. If you process your maintenance orders by phases, you can also access this app
via the External Procurement card in the Maintenance Backlog Overview app.

Key Features
This app provides the following key features:

View a pre ltered list of purchase orders, for example purchase orders which have not yet been approved. The
prede ned lter settings depend on how you navigate to this app.

Filter the list of purchase order items, for example by the availability date of the ordered components and services, the
release status of the purchase order, and other criteria.

View relevant procurement information, such as the order quantity and order value, contact information of the supplier,
or the availability date and the requirement date of the ordered components and services.

Branch to individual purchase orders or purchase order items.

Branch to the product master data of the ordered products and to the corresponding maintenance orders.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
Maintenance Planning Overview
Maintenance Backlog Overview

Manage Components and Services

This is custom documentation. For more information, please visit the SAP Help Portal 11
 7/16/2023
With this app, you can view and manage all externally-procured materials and lean services that are required to execute your
maintenance orders in a single place. You access this app by choosing the procurement activity Create Purchase Requisition on
the External Procurement card in the Maintenance Backlog Overview app. By default, the system displays all non-stock
components and lean services in the selected maintenance planning buckets for which a purchase requisition needs to be
created. However, you can also lter the list by other attributes and, for example, view information about externally-procured
materials and services in different planning buckets or for which other procurement activities are pending.

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.

Key Features
You can use this app to do the following:

Filter externally-procured materials and services by one or more maintenance planning buckets, pending procurement
activities, and other criteria. The system displays all non-stock components and lean services that match the selected
lter criteria.

Navigate to the maintenance order to which a non-stock component or lean service is assigned. From the maintenance
order you can, for example, create a purchase requisition for the relevant non-stock component or lean service.

View the order operation to which a non-stock component or lean service is assigned, and navigate to the object page to
view the operation details.

View all relevant procurement information for each component or service, such as the product number and product
description, the supplier, the purchase requisition, and the requirement date.

Branch to the product master data of a non-stock component or lean service by using the corresponding link.

Select a supplier or a purchase requisition and navigate to the relevant object page.

Supported Device Types

Desktop

Tablet

Smartphone

Perform Maintenance Jobs

With this app, as a Maintenance Technician, you can review, execute, and report the ndings for the jobs dispatched for
execution.

Jobs that are Ready for Execution are listed according to their schedules. The list will also include jobs that do not support the
phase model. For such jobs, subphase details will not be available. The default lters available with the Standard variant allows
you to view jobs assigned to you and your team. The jobs that are not yet assigned can be self-assigned.

The app maintains information required to perform a maintenance job such as related details, reference documents, and
materials. This app allows you to start, pause, and mark the job as work done. You can record time for the job and it also allows
you to record failure data and measurement readings.

This is custom documentation. For more information, please visit the SAP Help Portal 12
 7/16/2023
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 differ 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.

Key Features
You can use this app to do the following:

Identify outstanding jobs that need to be performed.

Self-assign jobs that are yet to be assigned.

Assess all information required to perform a job. For example, the reference documents linked to the order, operation,
equipment, or functional location levels.

Record the progress of the work being performed and view con rmation data.

Record malfunction information.

Issue and return goods more than what the planner has already planned.

Issue goods that are not added previously into the order.

Save measurement results for an object.

App Description
Each task that the app helps you to perform is described below:

Plan and Assign Jobs

A job is an operation or a suboperation associated with a maintenance order, which is Ready for Execution, and is assigned to a
maintenance technician. Jobs that are Ready for Execution are listed according to their schedules. The standard variant with
the following lters and its corresponding value allows you to list jobs:

Responsibilities with the value Mine and My team's

Subphase with the value Ready for Execution, Work in Execution, and Work Paused

In the standard variant, these jobs are sorted according to the Latest Scheduled Finish eld in the descending order so that the
jobs that are nearing their schedule nish time appears at the top. You can also plan maintenenace for jobs by applying the
lters such as Responsibilities, Earliest Schedule Start Date and so on. The jobs that are not yet assigned can be viewed (or
accessed) by selecting any one of the values from the Responsibilities lter such as Mine and to be assigned in my team or To
be assigned in my team. Based on the con guration settings for a particular plant and order type, you can self-assign one or
more jobs that are in the execution phase using the Assign to me button at the top of the listed jobs table.

Apart from the lters mentioned above, there are additional lters to search for jobs relevant for Functional Location and
Equipment. If a piece of equipment is part of a functional location hierarchy and a search is initiated for jobs related to
immediate superior functional location, all jobs under the selected piece of equipment are listed. You can see details about a job
and respective columns such as Priority, Equipment, Functional Location, Noti cation, Order and so on. Certain elds such as
Order, Noti cation, Equipment allow you to view more information and navigate to the respective details.

 Example
This is custom documentation. For more information, please visit the SAP Help Portal 13
 7/16/2023
A job scheduled on 10 December 11:30 a.m. appears at the top if all other jobs are scheduled after 10 December. If there is
more than one job scheduled on 10 December with the time schedule 11:00 a.m. and 11:30 a.m., the job scheduled at 11:00
a.m. will appear at the top.

To list jobs, you can use any of the following values of the Responsibilities lter:

All Jobs : This lter shows all the jobs that are available for execution.

Mine and My team's: This lter shows all the operations that belong to your team and are already assigned to you or any
other team member. It excludes all the operations that are yet to be assigned to anyone from your team.

Mine only: This lter lists all the jobs that have been assigned to you.

Mine and to be assigned in my team: This lter lists all the jobs that have been assigned to you or that still have to be
assigned to members of your work center (team). Hence, the Assigned To column in the list appears with your name or
will appear empty.

My team’s only: This lter lists all the jobs that have been assigned to the team members of your work center (team)
excluding the jobs assigned to you.

To be assigned in my team: This lter lists all jobs that belong to your work center (team) but still have to be assigned to
you or any other team members.

 Note
To add yourself to a team, access the Personalization app on the SAP Fiori Launchpad. Enter your work center details in the
Organization section of the app. Similarly, a con guration expert can also add a maintenance technician to a team using the
Manage Teams and Responsibilities for Work Centers- Asset Management application. While a search is initiated to identify
a maintenance technician according to their assigned team, the search functionality determines the assigned team
according to the sequence below:

The team de ned in the Personalisation application.

If no team is de ned, the team de ned in the Manage Teams and Responsibilities for Work Centers - Asset
Management application is considered.

Quick Con rm This action allows you to complete con rmation of one or more jobs
from the list page without navigating to the details page. It is
recommended for jobs that does not require editing and are
considered as nally con rmed according to the initial plan of the
maintenance planner. In this process, the effort planned for a job is
automatically considered as the nal effort except for jobs with
system status PCNF (Partially Con rmed). For partially con rmed
jobs, remaining efforts are considered. Quick con rmation is not
possible for jobs that have the following conditions:

Jobs with the system status as con rmed (CNF)

Jobs that are assigned to other maintenance technicians or

are unassigned

More than 10 jobs are selected for con rmation

View Job Details

Before you start a job, choose the job to navigate to the details page and view the various details using the following steps:

This is custom documentation. For more information, please visit the SAP Help Portal 14
 7/16/2023

Step Description

Review Operations You can visualize details associated with the operation such as long
description, short description, planned effort, assigned work center,
technical object and so on.

Visualize suboperations The suboperations section allows you to visualize suboperations

associated with the operation.

Visualize Related Jobs You can view all the jobs associated to the maintenance order using
the Order tab and to view jobs associated to the header technical
object use the Technical object tab.

Malfunction Details You can view the existing observed malfunction information in this
section.

Review reference documents The Attachment section contains various reference documents
corresponding to the order. You can download and view
attachments associated with operation, order, equipment, and
functional location.

Execute Maintenance Jobs

After understanding the job requirements, start the job. The following steps need to be performed:

Step Description

View and Post Materials required to perform a job You can use the Planned Components section to display the
different materials that are required to perform the maintenance
job for an order. The Post action allows you to issue goods.

Each order has a bar code. This option enables you to scan the
order details using a barcode scanner and software which can help
to increase efficiency and improve operations.

Unplanned Components This section lets you issue goods that are not added previously to
the order. The Post action allows you to issue unplanned
components. You cannot return the unplanned goods once issued.

Record Time This action allows you to record the time that you or any other team
member has spent on a job. You can reassess the job and adjust
the effort required to perform the job. By selecting the Final
Con rmation option, you can mark the job as complete and no
further time recording is required.

You can record the Work Start and Work End date and time while
performing time con rmation. Default values are available for these
elds. For the rst con rmation, the earliest start date value
mentioned in the order is used as the work start date. If the earliest
start date is in future, the current date is taken as the work start
date. The current date is also taken as the end date for the work.
For subsequent con rmations, the end date for the last con rmed
operation is taken as the start date. Current date is taken as the
end date.

You also have the option to select a date of your choice while
starting and ending a work.

You can also choose the Reason for Variance option. This option
allows you to provide a reason for variation from the prede ned list
whenever there is a deviation from the planned work.

This is custom documentation. For more information, please visit the SAP Help Portal 15
 7/16/2023

Step Description

Visualize Work Done You can refer to the graphical view representing the amount of work
done for an operation at the top of the details page.

Add Measurements This action allows you to save measurement results for an object.

Follow -On Noti cation You identify the requirement during the execution of the current
maintenance job and choose the Follow-On Noti cation button. The
Create Maintenance Request application appears and enables you
to create the reactive maintenance request. After you submit the
request, you are redirected back to the details page of the Perform
Maintenance Jobs application. The technical object is pre- lled
with the technical object available at the order header level. After
the request is submitted, it is sent for screening and then listed in
the My Maintenance Requests application.
During the submission of the request, the document ow creation is
also triggered. The document ow links the current order with the
newly created follow-on noti cation. For an order there can be
multiple follow-on noti cations. The requirement does not have any
life-cycle impact on the existing order execution.

Post-completion of Maintenance

After the maintenance job is completed, you can perform the following steps:

Step Description

Return unused materials after maintenance You can use the Planned Components section to view the quantity
of components not yet issued from the warehouse. The Return
action lets you return issued components to the warehouse after
the technician completes the job.

Report Malfunction The Malfunctions section allows you to share observations about
the condition of the technical object that is being maintained and
report any damages, associated causes, and activities performed.

 Note
The malfunction section is enabled only if the order has an
associated noti cation.

The machine learning feature in the Add Malfunction Details

Damage Details section provides appropriate damage code and
object part as part of the value help. You can view the proposed
damage code and object part for an existing maintenance order.
The damage code and object part suggestions are based on the
information available for the noti cation, such as noti cation type,
description, plant, functional location, equipment number short
text, and long text. Additionally, object part is also one of the
in uencing factor for predicting damage code.

 Note
The machine learning functionality to predict damage code and
object part is deprecated.

Supported Device Types

Desktop
This is custom documentation. For more information, please visit the SAP Help Portal 16
 7/16/2023

Display Serial Numbers

As an inventory manager or warehouse clerk, you can use this app to display a list of the serial numbers assigned to a material.
The list re ects the serial numbers of the materials according to the last posted Goods Movement. You can sort and lter this
list according to your needs. You can then export the list. This app is accessible through the Stock – Single Material and Stock –
Multiple Materials apps.

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.

Key Features
You can use this app to:

Display a list of serial numbers assigned to a material, plant, storage location, stock type, special stock or batch.

Search for a speci c serial number.

Export a list of serial numbers.

Filter, sort, and group your results list according to your needs.

Supported Device Types

Desktop

Tablet

Smartphone

Relevant Business Catalog

EAM - Display Serial Numbers: SAP_EAM_BC_SERIALNO_DSP_PC (business roles: Inventory Manager and Warehouse
Clerk)

Related Information
Serial Number Management (LO-MD-SN)
Serial Number Pro le
Working With Serial Numbers
Serial Number Master Record

Display Maintenance Noti cations

With this app, you can display maintenance noti cations. You can quickly view details of a maintenance noti cation such as
phase, subphase, detection method, malfunction data, priority, and so on.

Note

This is custom documentation. For more information, please visit the SAP Help Portal 17
 7/16/2023
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.

Key Features
Display maintenance noti cations by using free text search or by ltering for parameters, such as noti cation type,
priority, dates, and statuses

Display quick views with details of the related maintenance noti cation and technical object.

View and navigate to apps that are related to this app.

Display the items, tasks and activities in the noti cation.

Export the search result table and the tables of the maintenance noti cation to a downloadable spreadsheet le.

List the attachments of the noti cation.

Display the relevant maintenance plan and item.

Display the history of changes made to the noti cation.

View the nal due date for a maintenance noti cation. If the nal due date was changed, then you can also view the
previous nal due date.

Additional Information
This app is a variant of the app Find Maintenance Noti cation (F2071) but this app does not allow you to update noti cation or
perform any action. In this app, you can only view details of maintenance noti cations. For more information, see Feature
Comparison for Maintenance Noti cation Apps.

Related Information
Feature Comparison for Maintenance Noti cation Apps
Manage Maintenance Noti cations and Orders
Find Maintenance Noti cation

App Implementation: Display Maintenance Noti cations

Description
With this app, you can view maintenance noti cations.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

This is custom documentation. For more information, please visit the SAP Help Portal 18
 7/16/2023

Back-End / Front-End Server SAP Note Description

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F5797.

Back-End Server: Create Connectors

This app is based on ABAP Core Data Services and does not require search models to work. However, if you want to start the
app from the search results list, you must activate the underlying search connectors. You can create connectors in transaction
ESH_COCKPIT.

For more information, see Creating Connectors.

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Object pages are based on search models. To be able to use an object page, you must activate the underlying search models by
creating connectors. Create connectors in transaction ESH_COCKPIT.

You can nd the search models for this app in the SAP Fiori apps reference library.

For more information, see Creating Connectors.

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

This is custom documentation. For more information, please visit the SAP Help Portal 19
 7/16/2023

Front-End Server: Activate OData Services

For more information about activating OData services, see Activating OData Services.

Front-End Server: Activate OData Services

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAPUI5 Application

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

EAM_OBJPG_MAINTNOTIFICATION_SRV(0001) You can use the example business Assign the existing role
catalog SAP_EAM_BC_MNTWRK_MNG_PC SAP_BR_MAINTENANCE_PLANNER or
or your custom catalog to create the create a new one.
back-end PFCG role.

Related Information

This is custom documentation. For more information, please visit the SAP Help Portal 20
 7/16/2023
Display Maintenance Noti cations

Feature Comparison for Maintenance Noti cation Apps

The following table compares the features offered by various apps in the area Maintenance Management for maintenance
noti cations. The column headings contain links to the app documentation and the app's entry in the SAP Fiori apps reference
library.

Compared Features Display Maintenance Noti cations Find Maintenance Noti cation

F5797 F2071

Generate order No Yes

Assign order No Yes

Change responsibilities No Yes

Change scheduling No Yes

Set or unset status No Yes

Edit multiple (mass) maintenance No Yes

noti cations

Search for maintenance noti cations Yes Yes

View phase and subphase information Yes No

Assess priority based on consequences and Yes No

likelihoods

Assign detection method Yes No

Create Maintenance Request

With this app, you can create maintenance requests. While creating a maintenance request, you can provide relevant
information that is required to identify and solve the problem.

Note

This app has been designed to be used within the functional scope of the Reactive Maintenance (4HH) scope item 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.

Key Features
This app allows you to do the following:

Create maintenance requests for technical objects. The technical object may be a functional location or a piece of an
equipment

The new maintenance request is displayed in the Screen Maintenance Requests app. For more information, see Screen
Maintenance Requests.

This is custom documentation. For more information, please visit the SAP Help Portal 21
 7/16/2023
The maintenance requests created by you are also available in My Maintenance Requests app. For more information,
see Screen Maintenance Requests.

View and update the latest draft. When you enter details to create a maintenance request and exit the app without
submitting the details, the maintenance request is saved as a draft. When you access the app next time, the draft is
displayed by default. You can complete the draft and submit it to create a maintenance request or discard the draft. If
you discard the draft, a new form is displayed. The discarded draft cannot be restored.

 Note
For each user, only the latest draft is available.

View associated maintenance requests. When you select a technical object for which you want to create a maintenance
request, you can also view the open maintenance requests for the same technical object.

View hierarchy of functional location and equipment. If the functional location is an identifying level, complete hierarchy
of a technical object is 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 de ned in the structure indicator that has for a functional location.

Only if the functional location is con gured as an identifying level in the activity Create Structure Indicator for Reference
Locations/ Functional Locations, the underlying technical objects will be shown in hierarchy.

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

View open maintenance requests. When you select a technical object, you can view all the maintenance requests that
are available for the technical object.

Scan barcode to enter the ID of the technical object.

 Note
This feature is available only on mobile device and is enabled by the SAP Fiori Client.

Enter description of the current location of the technical object. It is applicable for the technical objects that are not xed
assets.

Select the mode of failure of the technical object for which you are creating the maintenance request. When a technical
object has the probability of failing in various ways, it helps to have speci c information about the mode of failure. The
failure mode group and failure mode help you to capture such information.

 Note
The catalog type D (coding) is used for de ning failure modes in maintenance management. You can use the Edit
Code Group app to de ne failure mode groups and codes. In the Maintain Catalog Pro le app, you can assign them so
that they can be used in the maintenance requests.

Select a detection method to indicate how the failure was discovered. For more information, see Detection Methods.

Use the template to provide information about the maintenance request. The long text can have only 1333 characters.
There is one prede ned template. You can also create a template and use it to create long text For more information,
see App Extensibility: How to Add Long Text Templates.

Enter name of the user who reported the maintenance request.

Enter the start date of the malfunction.

This is custom documentation. For more information, please visit the SAP Help Portal 22
 7/16/2023
Select the processing context for the maintenance request to indicate how the request should be processed. For
more information, see How to Use Noti cation Processing Context.

Select a priority that you want to assign to the maintenance request. You can create priorities in the con guration
activity De ne Priorities for Each Priority Type.

Assess Priority

You can also determine a priority through risk assessment by selecting a combination of consequence categories,
consequences, and likelihood. Prioritization pro les can be de ned using the activity De ne Prioritization Pro les. For
more information, see How to Assign Priorities to Noti cation Types

The priority de nes 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 nal due date.

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
noti cation 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 noti cation 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.

Upload documents related to the maintenance request. You can upload documents that have information related to the
maintenance request and will help the processor to provide quick resolution.

Provide link to documents related to the maintenance request.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
Detection Methods
My Maintenance Requests
Screen Maintenance Requests
Phase-Based Maintenance Process

App Implementation: Create Maintenance Request

Prerequisites
To use this app, the Reactive Maintenance (4HH) scope item must be activated.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

This is custom documentation. For more information, please visit the SAP Help Portal 23
 7/16/2023

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library here.

Back-End Server: Create Connectors

This app is based on ABAP Core Data Services and does not require search models to work. However, if you want to start the
app from the search results list, you must activate the underlying search connectors. You can create connectors in transaction
ESH_COCKPIT.

For more information, see Creating Connectors.

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Object pages are based on search models. To be able to use an object page, you must activate the underlying search models by
creating connectors. Create connectors in transaction ESH_COCKPIT.

You can nd the search models for this app in the SAP Fiori apps reference library.

For more information, see Creating Connectors.

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

This is custom documentation. For more information, please visit the SAP Help Portal 24
 7/16/2023

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) UI_MAINTWORKREQUESTOVW_V2 (0001)

OData Service (Version Number) UI_PRIORITIZATION_PROFILE (0001)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application EAM_WREQ_CRTS1

Generic Drill-Down Application /default_host/sap/bc/ui5_ui5/sap/eam_wreq_crts1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

This is custom documentation. For more information, please visit the SAP Help Portal 25
 7/16/2023

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

UI_MAINTWORKREQUESTOVW_V2 (0001) You can use the example business catalog Use one of the existing roles:
SAP_EAM_BC_MREQ_MNG_PC or your
SAP_BR_EMPLOYEE_MAINTENANCE
custom catalog to create the back-end
PFCG role. SAP_BR_MAINTENANCE_PLANNER

SAP_BR_MAINTENANCE_TECHNICIAN

SAP_BR_MAINT_SUPERVISOR

Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:

To de ne noti cation types, go to Plant Maintenance and Customer Service Maintenance and Service Processing
Maintenance and Service Noti cations Noti cation Creation Noti cation Types

To de ne detection methods, go to Plant Maintenance and Customer Service Maintenance and Service Processing
Maintenance and Service Noti cations Noti cation Creation Noti cation Content Additional Functions for
Noti cation Types De ne Detection Methods

Related Information
Create Maintenance Request

App Extensibility: Create Maintenance Request

As a key user, you can extend the Create Maintenance Request app according to your business needs.

Custom Fields
With the Custom Fields app, you can create and maintain custom elds that you can use to enhance applications. You can add
elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Noti cation (EAMS_NTF) Fiori Create Maintenance Create Page Floorplan

Request Adapt UI

 Note
Editing of custom eld values is not available.

For more information, see:

Creating Custom Fields

Adding Extension Fields to Apps with Different UI-Technologies

Business Scenario

This is custom documentation. For more information, please visit the SAP Help Portal 26
 7/16/2023
You can transfer the custom eld data from a maintenance noti cation to a maintenance order by enabling the business
scenario EAM_NTF_TO_ORD.

You can transfer the custom eld data from an equipment to a maintenance noti cation by enabling the business
scenario EAM_EQUI_TO_NTF.

You can transfer the custom eld data from a functional location to a maintenance noti cation by enabling the business
scenario EAM_FL_TO_NTF.

Related Information
Key User Extensibility
Creating Extension Items and Transporting Them

App Extensibility: How to Add Long Text Templates

To create long texts, you need to implement a BAdI.

Key Features
To implement the BAdI, follow these steps:

1. Go to transaction SE18.

2. Enter the name of the BAdI eam_ltxt_tml_maint_notif

3. Right-click on Implementations and select Create BAdI implementation.

4. Enter a name for the enhancement implementation.

5. Select a transport request or a local object to save the implementation.

6. Enter an implementation class.

7. Choose the Copy Sample Class button.

8. Go to Implementations and double-click on Get Templates method.

When you refresh the Create Maintenance Request app, the template you added is displayed.

Example Implementation

You can use the above sample code to add long text templates. Changes have to be made in the Get Templates method of the
implementation class.

The sample ABAP code is displayed here.

 Sample Code

Data: ls_tmpl like LINE OF ct_ltxt_tml.

"Please remember that the description has to be unique (name of template)
if is_criteria-ntf_type eq 'Y1'.
ls_tmpl-description = 'Reactive Template'.
ls_tmpl-text = 'Test template for Y1'.
append ls_tmpl to ct_ltxt_tml.
ENDIF.

This is custom documentation. For more information, please visit the SAP Help Portal 27
 7/16/2023
IF is_criteria-maintenanceplant eq '1010'.
ls_tmpl-description = 'Template for Plant 1 DE'.
ls_tmpl-text = 'Test Template for Plant 1 DE(1010)'.
append ls_tmpl to ct_ltxt_tml.
ENDIF.

IF is_criteria-tec_obj_type eq 'EAMS_FL'.

ls_tmpl-description = 'Template for Functional Location'.

ls_tmpl-text = 'Please give a detailed address : '.
append ls_tmpl to ct_ltxt_tml.
ENDIF.
IF is_criteria-tec_obj_type eq 'EAMS_EQUI'.

ls_tmpl-description = 'Template for Equipment'.

ls_tmpl-text = 'Please give the details of damaged part : '.
append ls_tmpl to ct_ltxt_tml.
ENDIF.
" Add new template from SE61
cl_eam_ntf_lngtxt_tmplt=>add_template(
EXPORTING
iv_docu_id = 'DT'
iv_docu_typ = 'E'
iv_description = 'Customer Template'
iv_doku_obj = 'CUSTOMER_TEMPLATE'
CHANGING
ct_ltxt_tml = ct_ltxt_tml ).

In the sample code, the following values that you had entered in transaction SE61 are shown:

iv_docu_id - The document class to which the text belongs to. Here, it needs to be Dialog Text.

iv_docu_typ - The language in which the long text template should be displayed.

iv_description - The name of the template you are adding and, which must be shown in the app.

iv_docu_obj - The name of the document object.

Parameters

The long text template can be con gured based on parameters such as:

Technical object

Technical object type

Noti cation type

Maintenance plant

Edit a Long Text Template

To edit the template, follow these steps:

1. Go to transaction SE61.

This is custom documentation. For more information, please visit the SAP Help Portal 28
 7/16/2023
2. Add description for the long text template.

Detection Methods
Detection method is an activity or a method by which a failure is discovered. This information is important and helps in
evaluating the effect of maintenance. It helps in determining the differences between failures that are detected during regular
maintenance, inspection, and failures that are discovered by chance (casual occurrences).

The 9 prede ned detection methods are as follows:

Detection Method Description

Periodic maintenance The failure is discovered during preventive service, replacement or

overhaul of an item while executing preventive maintenance.

Functional testing The failure is discovered by activating an intended function and

comparing the response against a prede ned standard. This is
often used for detecting hidden failures.

Inspection The failure is discovered during planned inspection such as visual

inspection and non-destructive testing.

Periodic condition monitoring The failure is revealed during a planned, scheduled condition
monitoring of a prede ned failure mode, either manually or
automatically such as thermography, vibration measuring, oil
analysis, and sampling.

Continuous condition monitoring The failure is revealed during a continuous condition monitoring of a
prede ned failure mode.

Production interference The failure is discovered by production upset, reduction, and so on.

Corrective maintenance The failure is observed during corrective maintenance.

On demand The failure is discovered during an on-demand attempt to activate

an equipment unit (for example, safety valve fails to close, fails to
start a gas turbine on demand, and so on.)

Other The failure is discovered through the observation method and/or

combination of several methods.

Detection method pro les can be assigned to noti cations. If noti cation type has not been con gured for a noti cation, then
the detection method pro le cannot be assigned to a noti cation. You can add one or more detection method groups to a
detection method pro le.

Detection Method Groups

Detection methods are grouped depending on when the failure was discovered. Each detection method group is a category to
which detection methods belong. The detection method groups can be assigned to detection method pro les which can then be
assigned to noti cation types.

The prede ned detection method groups are as follows:

Scheduled activities

Continuous monitoring

Casual occurrences

This is custom documentation. For more information, please visit the SAP Help Portal 29
 7/16/2023
Other

The prede ned detection methods are assigned to detection method groups as follows:

Detection Method Group Detection Method

Scheduled activities Periodic maintenance

Functional testing

Inspection

Periodic condition monitoring

Continuous monitoring Continuous condition monitoring

Production interference

Casual occurrences Corrective maintenance

On demand

Other Other

Related Information
Create Maintenance Request
My Maintenance Requests
Screen Maintenance Requests

How to Assign Priorities to Noti cation Types

Prioritization enables you to determine a priority based on selected consequence categories, consequences, and likelihoods.
When you select consequences and likelihoods while creating a maintenance request, the system calculates and suggests the
applicable priority for the maintenance request. This provides additional contextual information to the screener.

For example, if oil is dripping from a pump in a plant, you can create a maintenance request for the technical object. While
determining priority through this assessment, you can specify that it is a high priority equipment which is responsible for core
drilling tasks and, if it is not repaired within two weeks, it could lead to total asset damage. Based on these details, the system
suggests Very High as the priority.

To determine a priority based on risk assessment:

1. De ne consequence categories, consequences, and likelihoods

2. De ne prioritization pro les

De ning Consequence Categories, Consequences, and Likelihoods

To de ne consequence categories, consequences, and likelihoods, follow these steps:

1. In your con guration environment, use the search function to open the following activity: De ne Consequence
Categories, Consequences, and Likelihoods.

2. Maintain consequence categories.

3. Within each consequence category, you can de ne multiple consequences.

This is custom documentation. For more information, please visit the SAP Help Portal 30
 7/16/2023
4. Maintain likelihood of occurrence of events.

5. Create groups and add consequence categories into the groups. This enables you to use a group in multiple pro les
without having to select the same consequence categories individually in various pro les.

Example

Calculated Priority = Function (Consequence Categories, Consequences, Likelihoods, Mapped Priority)

You can choose multiple consequence categories to arrive at a calculated priority. So, it is possible that you will receive more
than one priority as a result. For example,

People Impact -> High

Asset Impact -> Very High

Reputation Damage -> Medium

Environment Impact -> Low

The system will calculate and return the highest of these priorities as the calculated priority. In this case, it is Asset Impact.

If more than one consequence leads to the same priority, the system will suggest those two consequences as leading
consequences. For example,

People Impact -> Very High

Asset Impact -> Very High

Reputation Damage -> Medium

Environment Impact -> Low

The leading consequences are People Impact and Asset Impact.

De ning Prioritization Pro les

To de ne prioritization pro les, follow these steps:

1. In your con guration environment, use the search function to open the following activity: De ne Prioritization Pro les.

2. De ne a list of prioritization pro les. A pro le can be compared to a container that has consequence category groups,
noti cation types, and plants. When you create a maintenance request of type M1 for a technical object that is assigned
to plant 1010, and assess priority, the system tries to locate the pro le that matches this combination.

If you enter M1 as noti cation type, 1010 as maintenance plant, and CHEMICAL_PROF as pro le, and assess priority, the
system identi es CHEMICAL_PROF as the selected pro le and refers to the Consequence to Priority mapping table. It
fetches the priority for the selected combination of consequences and likelihood.

3. Assign prioritization pro le to a noti cation type and a plant. You can assign a pro le to many plants but a plant cannot
have more than one pro le assigned to it. Ensure that you maintain only one pro le for each noti cation type and plant.

4. Assign consequence category group to a prioritization pro le. You can assign a pro le to only one group. But, you can
assign the same group to one or more pro les.

5. Assign UI (user interface) position to a consequence category. Within a group, you can choose to arrange the
consequence categories in a particular order. When you assess priority, you will see the consequence categories in this
order.

This is custom documentation. For more information, please visit the SAP Help Portal 31
 7/16/2023
6. Assign a priority to consequences. You can assign an appropriate priority to a combination of consequence categories,
consequences, and likelihood. It is important that priorities are carefully assigned to the combinations as the priorities
directly in uence other factors of a maintenance request such as the nal due date, required start date, and required
end date.

De ning Priorities
1. In your con guration environment, use the search function to open the following activity: De ne Priorities for Each
Priority Type.

2. You can de ne different priority types and assign a priority type to each noti cation type. For each priority type, you
de ne:

Priority for a maintenance noti cation.

Start date and nish date for the maintenance noti cation. This is based on the date on which the maintenance
noti cation was created.

You can change the parameters for the priority types after you have gathered enough values based on experience.

To assign a suitable priority type to a noti cation type, follow these steps:

1. De ne priority types.

2. For each priority type, de ne its priority (rank) and basic dates.

3. Assign a suitable priority type to each noti cation type.

How to Use Noti cation Processing Context

Noti cation processing context allows you to create maintenance requests that do not have to follow all the nine steps of the
maintenance process. Based on the noti cation processing context, the maintenance request can receive exception and skip
few steps of the maintenance process.

Prerequisites
You should be using the 9 phase maintenance process.

You need to ensure that the authorization object I_EXCP_MN (Exception Process - Maintenance Noti cation) is
assigned to your role.

For emergency work, the authorization object I_EXCP_MO (Exception Process - Maintenance Order) also must be
assigned to your business role. Moreover, the order type, maintenance planning plant, and additional processing context
must be maintained for the Reactive Maintenance order type, the relevant planning plants, and the processing context E
(Emergency Order).

If you have maintained 01 (emergency work), you will be able to create maintenance requests for emergency
work.

If you have maintained 02 (minor work), you will be able to create maintenance requests for minor work.

To use the noti cation processing context for any noti cation type in the Create Maintenance Request app, you need to
select the Approval Required checkbox in the following con guration activity: Plant Maintenance and Customer
Service Maintenance and Service Processing Maintenance and Service Noti cations Overview of Noti cation
Type Partner Functions, Approval

This is custom documentation. For more information, please visit the SAP Help Portal 32
 7/16/2023
The overall status pro les must be maintained in the following con guration activity: Plant Maintenance and Customer
Service Maintenance and Service Processing Maintenance and Service Noti cations Maintenance and Service
Noti cations Fiori Apps for Maintenance Processing -> Con gure Overall Status Pro le-> Assign Overall Status
Pro le for Noti cation Types Con gure Overall Status Pro le Assign Overall Status Pro le for Noti cation Types

Emergency Work
When an asset requires immediate maintenance or urgent repair work, you can create a maintenance request for emergency
work. This request will get accepted without the need for screening. This reduces the time it takes for a maintenance request to
be accepted for processing and prevents delay in the maintenance work. This also saves the situation from greater damage.

Process

To create a maintenance request with processing context emergency work, follow these steps:

1. In the Create Maintenance Request app, select a technical object and enter all the details. For more information see,
Create Maintenance Request.

2. Select Emergency Work as the processing context. The elds relevant for an emergency work are available on the app.
These elds are available only when you select emergency work as the processing context.:

Main work center

Work center plant

Order type

Planning plant

The system will try to determine the main work center, work center plant, and the planning plant based on the technical
object you selected. If values are not available for the technical object, system provides the default values that you
maintained in the user settings. These elds are mandatory so if there are no default values, you can enter the values.

The order type is lled in based on the prede ned con guration in the con guration activity Assign Noti cation Types to
Order Types

3. De ne priority of the emergency work. This is also a mandatory eld.

4. Enter all details and submit the maintenance request. The maintenance request is created and is in Planning phase and
Order Assigned (Request) subphase.

Along with the maintenance request, a maintenance order is also created. For more information, see Reactive
Maintenance: Emergency Work.

5. The maintenance request can be seen along with the accepted requests in the My Maintenance Requests app and
Screen Maintenance Requests app.

Minor Work
In a minor work, you create a maintenance request with Minor Work as the noti cation processing context. The minor work
maintenance request will be accepted as soon as you submit it. You can record malfunction details and complete the
maintenance request.

If you have the required authorization, you can create a minor work when:

You observe maintenance issues during regular inspection which can be xed immediately.

A maintenance order is not required for the maintenance request.

This is custom documentation. For more information, please visit the SAP Help Portal 33
 7/16/2023

 Note
Minor work is used to record malfunction data for maintenance issues that can be xed immediately and do not need
a maintenance order.

The maintenance request does not need to be planned or approved.

You are able to create a minor work maintenance request, record the malfunction details, and complete the
maintenance request.

Process

To create a minor work (02), follow these steps:

1. Go to the Create Maintenance Request app.

2. Create a maintenance request with Minor Work as the noti cation processing context. The maintenance request is
immediately accepted.

3. Go to the Accepted tab in the My Maintenance Requests app and select the minor work (02). To locate the minor work
with ease, you can lter by noti cation processing context.

4. Choose the Malfunction Details button. Enter the damage details, cause, activity, and malfunction data and submit the
details.

Before completing it, choose the minor work and review the malfunction details in the object page.

5. Choose the Complete Noti cation button. Enter the reference date and time to complete the noti cation.

 Note
Reference date and time will be displayed based on the settings in the Reference Time eld of the con guration
activity SPRO Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance
and Service Noti cations Noti cation Creation Noti cation Types De ne Noti cation Types.

Related Information
Create Maintenance Request
Reactive Maintenance: Emergency Work
My Maintenance Requests
Screen Maintenance Requests
Reactive Maintenance: Minor Work

Final Due Date

Final due date is the latest date by which a maintenance activity must be completed. Final due date is determined for a
maintenance order or a maintenance noti cation based on the priority of a maintenance activity. When you select the priority
for the maintenance activity, the nal due date is determined and displayed.

Prerequisites

When you select a priority, the nal due date is determined. If priority is not selected, then the nal due date will not be
determined.

De ne Final Due Date

This is custom documentation. For more information, please visit the SAP Help Portal 34
 7/16/2023
To de ne the nal due date, follow these steps:

1. In your con guration environment, use the search function to open the following activity: De ne Priorities for Each
Priority Type.

2. Enter the priority, priority text, duration for nal due date, and the unit of measure. Based on these details, the nal due
date is determined and displayed when you assign a priority to a maintenance order or a maintenance noti cation.

The nal due date unit of measure de nes the duration by which the maintenance activity should be completed and can
be in hours, days, weeks, and months. The nal due date is calculated based on the factory calendar, current date, the
duration, and the unit of measure. If factory calendar is not maintained for the plant, then the system looks for the
factory calendar of the main work center.

Example

Here is an example of how nal due date is determined:

Priority Priority Text Duration for Final Due Unit of Measure for Final Due Date
Date Final Due Date

1 Very High 5 D Current Date + 5 Days

2 High 8 D Current Date + 8 Days

3 Medium 2 W Current Date + 2 Weeks

Edit Final Due Date

If you want to edit the nal due date for a maintenance noti cation, your role must contain the authorization object
I_VORG_MEL with the relevant noti cation type and business transaction LACD assigned to it.

If you want to edit the nal due date for a maintenance order , your role must contain the authorization object
I_VORG_ORD with the relevant noti cation type and business transaction LACD assigned to it.

While screening a maintenance request, the maintenance supervisor can edit the nal due date. The maintenance
supervisor has the authorization to edit the nal due date.

Feature Comparison - Request Maintenance and Create

Maintenance Request
The following table compares the features offered by various apps Maintenance Management for maintenance request. The
column headings contain links to the app documentation and the app's entry in the SAP Fiori apps reference library.

Compared Features Request Maintenance Create Maintenance Request

F1511 F1511A

Draft maintenance requests are available. No Yes

Assessing risks based on consequence No Yes

categories, consequences, and likelihoods
to determine priority of a maintenance
request.

Key user extensibility Yes. In this app, you can remove and Yes. In this app, you can add, rename, and
rename elds. remove elds.

This is custom documentation. For more information, please visit the SAP Help Portal 35
 7/16/2023

Compared Features Request Maintenance Create Maintenance Request

F1511 F1511A

Failure mode and failure mode group No Yes

Malfunction start date and time No Yes

Breakdown No Yes

Location of the technical object No Yes

Detection method No Yes

Default noti cation type Select any noti cation type. You can change the default noti cation type.
Y1 is selected by default.

View hierarchy of technical objects No Yes

Barcode Yes Yes

Default template for long text is available Yes Yes. The long text is pre lled with the
template.

Change default template Yes Yes

Relevant scope items BH1 (Corrective Maintenance) 4HH (Reactive Maintenance)

My Maintenance Requests
With this app, you can view your maintenance requests. You can also copy maintenance requests or delete maintenance
requests.

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.

Key Features
This app allows you to do the following:

View maintenance requests that were submitted only by you. All the requests you submitted can be seen here.

View maintenance requests based on the status of the request. The statuses are:

Submitted: These are the maintenance requests that you had submitted. When you submit a maintenance
request, it moves to Screen Maintenance Requests app where a supervisor will review the request. For more
information, see Screen Maintenance Requests.

Action Required: During screening, if the supervisor requires additional details to accept the request, the
maintenance request is sent back to you. You can enter the required details and submit the request for screening.
After you submit the request, the status of the request changes to Submitted.

Accepted: When the supervisor accepts a maintenance request, the request appears here. The accepted
requests are sent for planning and processing.

This is custom documentation. For more information, please visit the SAP Help Portal 36
 7/16/2023
For a minor work, add malfunction details and complete the noti cation. For more details, see How to Use
Noti cation Processing Context.

Rejected: You can view the maintenance requests that were rejected. During screening, if information is incorrect
or incomplete, the maintenance request is rejected. You cannot resubmit a rejected maintenance request.

Completed: You can view all your maintenance requests that have been processed. Solution has been provided for
these maintenance requests.

Draft : You can view drafts of maintenance requests. To edit a draft, choose a draft and make changes. You can
select one or more drafts and delete them. If you discard a draft, it will not be available in the queue. If you submit
it, it will be sent for screening.

Copy maintenance requests that are in status Submitted, Accepted, or Completed

View the phase and sub phase of a maintenance request. The phase and sub phase of a maintenance request provide us
with details about the status of a maintenance request.

Use quick view for technical object and maintenance order and navigate to corresponding object pages for additional
details. 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. Quick views are available for order numbers also.

View details such as noti cation type, order number, nal due date, phase, and subphase in the overview section. Order
number is shown if an order is assigned to the maintenance request.

Navigate to Create Maintenance Request app to create a new maintenance request. For more information, see Create
Maintenance Request.

How to Create Maintenance Requests

From the My Maintenance Requests app, you can create new maintenance requests.

Choose Create to create a new maintenance request. You will be taken to the Create Maintenance Request app.

Select a maintenance request that is in status Submitted, Accepted, or Completed and choose Copy. Long text is not
copied into the new maintenance request. Instead of the long text, the default template is available in the new
maintenance request. You can add long text.

Supported Device Types

Desktop

Tablet

Smartphone

App Implementation: My Maintenance Requests

Prerequisites
To use this app, the Reactive Maintenance (4HH) scope item must be activated.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

This is custom documentation. For more information, please visit the SAP Help Portal 37
 7/16/2023

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library here.

Back-End Server: Create Connectors

This app is based on ABAP Core Data Services and does not require search models to work. However, if you want to start the
app from the search results list, you must activate the underlying search connectors. You can create connectors in transaction
ESH_COCKPIT.

For more information, see Creating Connectors.

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Object pages are based on search models. To be able to use an object page, you must activate the underlying search models by
creating connectors. Create connectors in transaction ESH_COCKPIT.

You can nd the search models for this app in the SAP Fiori apps reference library.

For more information, see Creating Connectors.

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

This is custom documentation. For more information, please visit the SAP Help Portal 38
 7/16/2023

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) UI_MAINTWORKREQUESTOVW_V2 (0001)

OData Service (Version Number) UI_PRIORITIZATION_PROFILE (0001)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application EAM_WREQ_CRTS1

Generic Drill-Down Application /default_host/sap/bc/ui5_ui5/sap/eam_wreq_crts1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

This is custom documentation. For more information, please visit the SAP Help Portal 39
 7/16/2023

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

UI_MAINTWORKREQUESTOVW_V2 (0001) You can use the example business catalog Use one of the existing roles:
SAP_EAM_BC_MREQ_MNG_PC or your
SAP_BR_EMPLOYEE_MAINTENANCE
custom catalog to create the back-end
PFCG role. SAP_BR_MAINTENANCE_PLANNER

SAP_BR_MAINTENANCE_TECHNICIAN

SAP_BR_MAINT_SUPERVISOR

Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:

To de ne noti cation types, go to Plant Maintenance and Customer Service Maintenance and Service Processing
Maintenance and Service Noti cations Noti cation Creation Noti cation Types

To de ne detection methods, go to Plant Maintenance and Customer Service Maintenance and Service Processing
Maintenance and Service Noti cations Noti cation Creation Noti cation Content Additional Functions for
Noti cation Types De ne Detection Methods

Related Information
My Maintenance Requests

App Extensibility: My Maintenance Requests

As a key user, you can extend the My Maintenance Requests app according to your business needs.

Custom Fields
With the Custom Fields app, you can create and maintain custom elds that you can use to enhance applications. You can add
elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Maintenance Noti cation Fiori My Maintenance Requests Object Page Section

(EAMS_NTF) Any item Adapt UI
General Information tab
and/or Malfunction
Information tab

 Note
Editing of custom eld values is not available.

For more information, see:

Creating Custom Fields

Adding Extension Fields to Apps with Different UI-Technologies

This is custom documentation. For more information, please visit the SAP Help Portal 40
 7/16/2023

Related Information
Key User Extensibility
Creating Extension Items and Transporting Them

Screen Maintenance Requests

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.

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 noti cation. If you want it to be available for
other maintenance noti cation 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 con guration activity: Plant Maintenance and Customer Service
Maintenance and Service Processing Maintenance and Service Noti cations Overview of Noti cation Type
Partner Functions, Approval .

After this con guration is maintained for a maintenance noti cation 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.

This is custom documentation. For more information, please visit the SAP Help Portal 41
 7/16/2023
Generate output items using the Determine Output Items quick action button on the noti cation 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 speci c 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 nally 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.

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 a technical object. The hierarchy displays the technical object's superior piece of equipment and
functional location, aggregated open orders, and aggregated open requests.

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 pro les can be de ned using the activity De ne Prioritization Pro les. For
more information, see How to Assign Priorities to Noti cation Types

The priority de nes 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 nal 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
noti cation 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 noti cation 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.

Reassess the risk and redetermine the priority of the maintenance request. As a maintenance supervisor, you can
manually change the nal 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 elds, 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.

Assign task lists to a maintenance request.

This is custom documentation. For more information, please visit the SAP Help Portal 42
 7/16/2023

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
Create Maintenance Request
My Maintenance Requests
How to Assign Priorities to Noti cation Types
Final Due Date
Detection Methods

App Implementation: Screen Maintenance Requests

System Landscape Requirements

For information about the system requirements, see SAP Fiori Overview.

 Note
The app offers the possibility to upload les. For security reasons, we strongly recommend that you install an appropriate
virus scanner in your SAP Fiori system landscape and de ne sufficiently restrictive scan pro les to prevent the upload of
malicious content.

For more information on virus scanning and scan pro les for apps, see section Virus Scanning in the SAP S/4HANA Security
Guide .

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library here.

Back-End Server: Create Connectors

This is custom documentation. For more information, please visit the SAP Help Portal 43
 7/16/2023
This app is based on ABAP Core Data Services and does not require search models to work. However, if you want to start the
app from the search results list, you must activate the underlying search connectors. You can create connectors in transaction
ESH_COCKPIT.

For more information, see Creating Connectors.

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Object pages are based on search models. To be able to use an object page, you must activate the underlying search models by
creating connectors. Create connectors in transaction ESH_COCKPIT.

You can nd the search models for this app in the SAP Fiori apps reference library.

For more information, see Creating Connectors.

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) UI_MAINTWORKREQUESTOVW_V2 (0001)

OData Service (Version Number) UI_PRIORITIZATION_PROFILE (0001)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application EAM_WR_OVWS1_A1

This is custom documentation. For more information, please visit the SAP Help Portal 44
 7/16/2023

Component Technical Name

Generic Drill-Down Application /default_host/sap/bc/ui5_ui5/sap/eam_wr_ovws1_a1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

UI_MAINTWORKREQUESTOVW_V2 (0001) You can use the example business catalog Use one of the existing roles:
SAP_EAM_BC_MREQ_DSP_PC or your
SAP_BR_MAINT_SUPERVISOR
custom catalog to create the back-end
PFCG role.

Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:

To de ne noti cation types, go to Plant Maintenance and Customer Service Maintenance and Service Processing
Maintenance and Service Noti cations Noti cation Creation Noti cation Types

To de ne detection methods, go to Plant Maintenance and Customer Service Maintenance and Service Processing
Maintenance and Service Noti cations Noti cation Creation Noti cation Content Additional Functions for

This is custom documentation. For more information, please visit the SAP Help Portal 45
 7/16/2023
Noti cation Types De ne Detection Methods

Related Information
Create Maintenance Request

App Extensibility: Screen Maintenance Request

As a key user, you can extend the Screen Maintenance Request app according to your business needs.

Custom Fields
With the Custom Fields app, you can create and maintain custom elds that you can use to enhance applications. You can add
elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Noti cation (EAMS_NTF) Fiori Screen Maintenance Object Page Section

Request Any item Adapt
UI General Information tab
and/or Malfunction
Information tab

 Note
Editing of custom eld values is not available.

For more information, see:

Creating Custom Fields

Adding Extension Fields to Apps with Different UI-Technologies

Related Information
Key User Extensibility
Creating Extension Items and Transporting Them

Manage Maintenance Noti cations and Orders

With this app, you can manage maintenance noti cations and maintenance orders that are processed by phases.

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.

Key Features

This is custom documentation. For more information, please visit the SAP Help Portal 46
 7/16/2023
This app allows you to do the following:

View maintenance noti cations that have been screened and accepted following this process:

1. A maintenance request is created for a technical object. For more information, see Create Maintenance Request.

2. The new maintenance request is available for screening and acceptance. For more information, see Screen
Maintenance Requests.

3. The accepted maintenance request is available in this app for processing.

Filter maintenance noti cations and orders. By default, the system displays reactive maintenance noti cations with a
date range of +/- 15 days. You can clear the default parameters to view the complete list of noti cations and orders or
change the lter parameters to select noti cations or orders with speci c attributes. You can, for example, lter
maintenance noti cations and orders by their priority or subphase, by their account assignment details, or by the cost
receivers that have been speci ed in a settlement rule. The system only displays maintenance orders and noti cations
that are processed by phases.

Group and sort maintenance noti cations or maintenance orders.

View details of a maintenance noti cation such as priority, failure mode, nal due date, associated orders, and so on.

View details of a maintenance order such as priority, nal due date, associated noti cations, and so on.

Create a maintenance order for a single maintenance noti cation. When you create an order for a noti cation, the
noti cation becomes the header noti cation of the order. The order inherits details from the noti cation. The new
maintenance order has a unique order number. You can create an order for a noti cation only if the noti cation has not
already been assigned to an order.

Select multiple maintenance noti cations and create one or more maintenance orders.

Create a single maintenance order for the noti cations you have selected and assign one of the noti cations as
the header noti cation. This noti cation will be displayed in the overview. To view other noti cations associated
with the maintenance order, choose More.

Create multiple maintenance orders for the maintenance noti cations you have selected. A separate order will be
created for each of the noti cations.

Assign an existing order to one or more noti cations. If you receive a noti cation for an object and a problem for which
an order has already been created, then you don't have to create a new order. You can assign the existing order to the
noti cation.

Unassign an order from a noti cation. You can only unassign an order from a noti cation that is not the header
noti cation. You can change the header noti cation in the Change Maintenance Order app.

Select one or more maintenance orders and mass-edit several attributes by means of a quick action. For example, you
can edit the location data, responsibilities, or the cost receivers that are maintained in a settlement rule. You can run a
simulation to test the data, or apply the mass change directly in the system. You can view the details of the simulated or
scheduled job in the Application Logs. For more information, see Mass Editing of Maintenance Orders.

Submit one or more orders for approval. Some orders require an approval based on order attributes and cost. In this
case, the maintenance planner has to submit the order for approval before it can be released to the Preparation phase.
Whether or not an approval is required depends on the approval settings that have been de ned for a combination of
maintenance order type and planning plant in Customizing under De ne Approval Settings for Maintenance Orders.

 Note
The approvers for an order can be determined by means of work ow rules. Depending on the con gured work ows,
the de ned approvers will see the submitted orders in the My Inbox app, where they can approve or reject them. For
more information, see Manage Work ows for Maintenance Orders and Manage Teams and Responsibilities.

This is custom documentation. For more information, please visit the SAP Help Portal 47
 7/16/2023
Change the responsibility for one or more maintenance noti cations and maintenance orders. For each attribute, you
can keep the existing values, select new values, or leave the eld blank. You can't change the responsibility for orders
that have been submitted for approval.

Select one or more maintenance orders and change the order status. You can, for example, release the selected orders,
complete them from a technical and business perspective, block further processing, or mark orders for deletion. You can
also cancel certain order statuses.

Select one or more maintenance noti cations and change the noti cation status. You can complete the selected
noti cations, mark them for deletion, or remove the deletion ag.

Navigate to related apps from the object page.

Generate output items using the Determine Output Items quick action button on the noti cation 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. Once the output is sent, it moves to the status To be Output and then to
Completed when it is nally 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.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
App Implementation: Manage Maintenance Noti cations and Orders
Maintenance Process Phases
Mass Editing of Maintenance Orders

App Implementation: Manage Maintenance Noti cations and

Orders

Prerequisites
This app only displays maintenance noti cations and maintenance orders that are processed according to phases. Before
implementing the app, we strongly recommend that the scope items 4HH (Reactive Maintenance ) and 4HI (Proactive
Maintenance ) are active in your system, or you have con gured the phase model in Customizing the same way as it is delivered
for these scope items.

Tile Type for Launching App

The Manage Maintenance Noti cations and Orders app is launched using an app launcher tile.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

This is custom documentation. For more information, please visit the SAP Help Portal 48
 7/16/2023

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F4604.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) UI_MAINTWRKREQ_ORD_MANAGE (0001)

OData Service (Version Number) UI_MAINTWORKREQUESTOVW_V2 (0001)

OData Service (Version Number) EAM_OBJPG_MAINTNOTIFICATION_SRV (0001)

OData Service (Version Number) EAM_OBJPG_MAINTENANCEORDER_SRV (0001)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application EAM_WRORD_MANS1

/sap/bc/ui5_ui5/sap/eam_wrord_mans1

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

This is custom documentation. For more information, please visit the SAP Help Portal 49
 7/16/2023

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

All services (see above) You can use the example business catalog Assign the existing role
SAP_EAM_BC_MP_ORD_MNG or your SAP_BR_MAINTENANCE_PLANNER or
custom catalog to create the back-end create a new one.
PFCG role.

Related Information
Manage Maintenance Noti cations and Orders
Maintenance Process Phases

Mass Editing of Maintenance Orders

In the Manage Maintenance Noti cations and Orders app, you can select and edit one or more maintenance orders and their
attributes at a single time.

Context
You can select several maintenance orders from the list report and change the general data, reference objects, location,
responsibilities, and settlement rules for all selected orders.

Procedure
1. On the initial screen of the app, select the maintenance orders that you would like to edit.

2. Choose Edit Orders. In the new window, you can change the following parameters for all selected objects:

Section Change/Add

General Data Description, activity type, priority, and system condition

Reference Object Equipment, functional location, material, and serial number

Location Data Location, plant section, and ABC indicator

Additional Data Responsible cost center

Responsibilities Main work center, planner group, plant for work center, and
person responsible.

This is custom documentation. For more information, please visit the SAP Help Portal 50
 7/16/2023

Section Change/Add

Settlement Rule Add cost center, add settlement order, add WBS element, add
asset, and remove assignments.

 Note
You can add only one settlement rule per mass edit
action.

You cannot change existing settlement rules.

If you add a settlement rule and select No/Keep

Existing Values in the Remove Assignments eld,
the new rule is added to the list of existing
settlement rules (if any).

If you select Yes in the Remove Assignments eld,

all existing settlement rules are removed. If you add
a settlement rule at the same time, existing
settlement rules (if any) are deleted rst and then
the new settlement rule is added.

If you try to add a settlement receiver that is not

valid for a selected order, the system displays an
error message in the Application Logs.

 Note
You can set, overwrite and clear eld values, or, when applicable, enter them manually. Depending on the speci c
parameter, the following options may be available in the drop down list:

<leave blank>: allows you to leave the eld empty for all selected objects

<keep existing values>: use it to keep the existing values for your selected objects

<value help>: you can choose the value from the list of pre-de ned values

Pre-existing data: apply values of one of the selected object to all selected objects

3. Choose Simulate to check the data for correctness without saving your changes, or choose Save to proceed with saving
your changes to the database. In both cases, you can enter a job description or keep the default description suggested
by the system.

4. You can view the details of the simulated or scheduled job in the Application Logs.

Manage Maintenance Planning Buckets

With this app, you can create maintenance planning buckets that aid you in effectively managing your maintenance backlog. You
can create operational maintenance planning buckets or event-based maintenance planning buckets. Operational maintenance
planning buckets are recurrent planning buckets that allow you to plan regular maintenance work. They are generated
automatically based on the time and recurrence details that you specify. Event-based maintenance planning buckets are one-
time planning buckets that help you to organize major maintenance events, where a group of maintenance orders needs to be
planned and executed during the same period.

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

This is custom documentation. For more information, please visit the SAP Help Portal 51
 7/16/2023
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.

Key Features
Create operational planning buckets to plan ongoing day-to-day work. For more information, see Creating Operational
Maintenance Planning Buckets.

Create event-based planning buckets to set up and manage one-time maintenance events. For more information, see
Creating Event-Based Maintenance Planning Buckets.

Manage maintenance events. For more information, see Maintenance Events.

Specify a time period for the maintenance planning buckets.

Specify a recurrence and a recurrence interval for operational maintenance planning buckets. The system uses this
information to calculate the start and end dates of the individual planning buckets it generates, and to assign
maintenance orders to them based on their scheduled start and end dates. You can also specify how many planning
buckets should be created in advance.

De ne the scope of the planning bucket by adding additional attributes such as the main work center, the planner group,
the maintenance plant, the plant section, or the technical object. The scope attributes serve as a lter that restricts
which maintenance orders are assigned to a planning bucket.

View a list of all maintenance planning buckets.

Search for individual maintenance planning buckets or lter the list according to several criteria, such as the reference
planning bucket, the planning plant, or the planning bucket type.

From each maintenance planning bucket, navigate to the Manage Maintenance Backlog app to view a list of the
maintenance orders that are assigned to the planning bucket. For more information, see Manage Maintenance Backlog.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
App Implementation: Manage Maintenance Planning Buckets
Creating Operational Maintenance Planning Buckets
Creating Event-Based Maintenance Planning Buckets
Maintenance Events
Comparison: Maintenance Event and Revision
Manage Maintenance Backlog
Maintenance Process Phases

App Implementation: Manage Maintenance Planning Buckets

Prerequisites
Before implementing the app, you must ensure the following:

This is custom documentation. For more information, please visit the SAP Help Portal 52
 7/16/2023
This app uses the technical job SAP_EAM_MTPLNGBKT_GENERATION which runs nightly to generate recurrent planning
buckets in advance. The background job is performed automatically when there is at least one recurring planning bucket
for which the system creates planning buckets in advance. You can verify that the job is active in transaction SJOBREPO.
Also review the prerequisites of the technical job repository in SAP Note 2190119 .

Tile Type for Launching App

The Manage Maintenance Planning Buckets app is launched using an app launcher tile.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F3888.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) EAM_PLNGBUCKET_MANAGE (0001)

For more information about activating OData services, see Activating OData Services.

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application EAM_BKT_MANS1

/sap/bc/ui5_ui5/sap/eam_bkt_mans1

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

This is custom documentation. For more information, please visit the SAP Help Portal 53
 7/16/2023
SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

EAM_PLNGBUCKET_MANAGE (0001) You can use the example business catalog Assign the existing role
SAP_EAM_BC_PLNBKTS_MNG or your SAP_BR_MAINTENANCE_PLANNER or
custom catalog to create the back-end create a new one.
PFCG role.

Con guration Tasks

Before you create maintenance events using this app, review the con guration information under Maintenance Events.

Related Information
Manage Maintenance Planning Buckets
Manage Maintenance Backlog
Maintenance Process Phases

Creating Operational Maintenance Planning Buckets

Operational maintenance planning buckets assist you in preparing maintenance orders for execution. They allow you to focus on
only those orders that are relevant for you and split them into manageable groups based on a speci c time period, such as a
week.

Context
To set up operational planning buckets, you create a reference planning bucket with speci c time data and other criteria to
specify which maintenance orders should be selected. Based on the details of the reference planning bucket, the system

This is custom documentation. For more information, please visit the SAP Help Portal 54
 7/16/2023
generates new planning buckets on an ongoing basis and assigns backlogs with matching maintenance orders to them. You can
access these backlogs directly from each individual planning bucket.

Procedure
1. In the Manage Maintenance Planning Buckets app, select Create.

2. Enter a unique alphanumeric label for the planning bucket. Additionally, you can enter a description.

For each planning bucket the system generates, a time speci cation is added to the label. If you plan a weekly bucket, the
week and year are added (_ww_yyyy). If you plan a daily bucket, the date is added (_ddmmyyyy). If the label and the time
speci cation exceed 40 characters, the system shortens the label at the end. To avoid this, limit the label text to 31
characters.

3. In the Type eld, select Operational Maintenance.

4. Specify a planning plant.

When assigning orders to the respective planning buckets, the system will only select orders that belong to this planning
plant.

5. Specify a time period and a recurrence pattern:

a. Specify the start date and time and the duration of the reference planning bucket. The start date and time must
be in the future or less than 30 days in the past.

The system uses this information to calculate the end date and time of the reference planning bucket, as well as
the time period of the planning buckets that are generated from it. The time period of the reference planning
bucket corresponds to the time period of the rst generated planning bucket.

b. If necessary, change the default entry in the Recurrence and Recurs Every eld to determine how often new
planning buckets should be available. If you don't change the default setting, the system will create one planning
bucket for each week.

The recurrence interval must be equal to or longer than the duration of the maintenance planning bucket. This
restriction helps to avoid overlaps in the consecutive chain of generated planning buckets. Let's assume that you
want the system to generate one planning bucket every four days. Therefore, you enter Daily in the Recurrence
eld and 4 DAY in the Recurs Every eld. In the Duration eld, you can enter any value equal to or smaller than 4
days.

c. Specify the number of planning buckets that the system creates in advance. Your entry in this eld determines
how many current and future planning buckets are available at any given point in time.

If you change any data in the reference planning bucket, these changes are only copied to planning buckets that
will be created in the future and are not applied to planning buckets that have already been created in advance.
Therefore, and for performance reasons, we recommend that you do not enter a high number in the eld Number
of Buckets in Advance.

 Tip
Planning buckets cannot be deleted. If you want the system to stop generating new planning buckets for a
reference planning bucket, set the number in the Number of Buckets in Advance eld to zero ("0").

6. Specify scope attributes to restrict the maintenance orders that should be assigned to the planning bucket. You can
specify one or more planner groups, maintenance plants, technical objects, plant sections, and main work centers.

 Note
Specifying a high number of scope attributes can have a negative impact on the system performance when you use a
planning bucket. For this reason, we recommend that you de ne no more than 30 scope attributes.

7. Save the reference planning bucket.

This is custom documentation. For more information, please visit the SAP Help Portal 55
 7/16/2023

Results
When you have created a reference planning bucket, the system continually generates new planning buckets based on the data
in the reference planning bucket. It automatically assigns maintenance orders to the planning buckets according to their
scheduled start date, their scheduled end date, and to the scope attributes that have been de ned in the reference planning
bucket.

The reference planning bucket and all planning buckets that have been generated from it are displayed in the Manage
Maintenance Planning Buckets app. You can access the list of assigned orders by selecting a planning bucket from the list and
choosing Manage Backlog.

Example
The following example illustrates how the system continuously generates planning buckets based on the time data that you
specify in the reference planning bucket.

On July 9, you create an operational maintenance planning bucket with the following time details:

Start Date and Time: July 10 at 3 pm

Duration: 3 hours

Recurrence: Daily

Recurs Every: 1 DAY

Number of Buckets in Advance: 2

The system generates new planning buckets according to the following pattern:

Date Buckets Created

July 9 Reference planning bucket with start date and time July 10 at 3pm

One planning bucket that starts on July 10 at 3pm

One planning bucket that starts on July 11 at 3pm

2 planning buckets are available

July 10 No new planning buckets

2 planning buckets are available

July 11 One planning bucket that starts on July 12 at 3pm

2 planning buckets are available

Creating Event-Based Maintenance Planning Buckets

A maintenance event allows you to group several maintenance activities to be performed during a maintenance window for a
technical object. To create a maintenance event, you rst create an event-based planning bucket in the Manage Maintenance
Planning Buckets app. Then you create a maintenance event inside the planning bucket.

Prerequisites
Make sure that one or more maintenance event types have been de ned in Customizing as described under Maintenance
Events.
This is custom documentation. For more information, please visit the SAP Help Portal 56
 7/16/2023

Procedure
To create a maintenance event, you rst create an event-based planning bucket. Then you create a maintenance event inside
the planning bucket.

 Note
Maintenance events are permanently associated with a planning bucket: They cannot be deleted or reassigned to another
planning bucket. Furthermore, a planning bucket can only contain a single maintenance event.

To create an event-based planning bucket with a maintenance event, follow these steps:

1. In the Manage Maintenance Planning Buckets app, select Create.

2. Enter a unique alphanumeric label for the planning bucket. Additionally, you can enter a description.

3. In the Type eld, select Event-Based Maintenance.

4. Specify the planning plant for which the planning bucket is valid and press Enter .

5. Enter the start date and time and the end date and time of the maintenance event. The system calculates the duration
based on the speci ed start date and end date.

6. In the Scope section, you can enter additional attributes to restrict which maintenance orders can be assigned to the
maintenance event. You can specify one or more planner groups, maintenance plants, technical objects, plant sections,
and main work centers.

The scope attributes are optional, but if you want to create an administrative maintenance order for the maintenance
event, you must specify a main work center.

 Note
Specifying a high number of scope attributes can have a negative impact on the system performance when you use a
planning bucket. For this reason, we recommend that you de ne no more than 30 scope attributes.

7. In the Event Planning section, choose Create Event. Enter a maintenance event ID. The ID can have a maximum of 8
characters. If you don't enter an ID, the system assigns an internal number to the event. Then select a maintenance
event type:

If you choose a maintenance event type for which an administrative maintenance order will be created, an
additional dropdown list is displayed from which you can select a system condition. To block the production
capacity of the asset, choose not in operation.

If you choose a maintenance event type for which no administrative maintenance order will be created, this
dropdown list is not displayed.

8. Con rm the creation of the maintenance event. Depending on the maintenance event type, an administrative
maintenance order is automatically created when you save the planning bucket.

Results
You can view the maintenance event, the maintenance event type, and the ID of the administrative maintenance order in the
Event Planning section, and you can navigate directly to the order object page to view or edit the order details.

Related Information
Maintenance Events
Managing Maintenance Events

Maintenance Events

This is custom documentation. For more information, please visit the SAP Help Portal 57
 7/16/2023
Maintenance events allow you to group and manage several maintenance activities to be performed during a maintenance
window for a technical object.

A maintenance event is one-off maintenance project, where a group of maintenance orders needs to be planned and executed
during the same period. For example, your company might plan maintenance windows for certain periods during the year.
During these periods, certain assets or even the entire company may shut down, allowing a large amount of maintenance work
to be performed. You can create maintenance events for these maintenance windows to group several maintenance orders
together and carry them out within the speci ed time period.

The Manage Maintenance Planning Buckets app allows you to create and manage maintenance events. You can then use
different apps to assign maintenance orders to a maintenance event. The Manage Maintenance Backlog app, for example,
allows you to assign maintenance orders to a maintenance event and monitor the progress of all maintenance activities that
are planned for the event. For more information, see Creating Event-Based Maintenance Planning Buckets and Managing
Maintenance Events.

 Note
In SAP GUI, you can create an object called a revision to manage such one-off maintenance projects. A comparison between
maintenance events and revisions can be found here: Comparison: Maintenance Event and Revision.

Administrative Maintenance Orders

When you create a maintenance event, you can choose to automatically create an administrative maintenance order to plan
the maintenance work and block the production capacity of the technical object in the order header. An administrative
maintenance order is permanently assigned to a speci c maintenance event and inherits the event dates, so that it is always in
sync with the maintenance event. For more information, see Administrative Maintenance Orders.

Customizing
When you create a maintenance event using the Manage Maintenance Planning Buckets app, you need to select a maintenance
event type. The available maintenance event types correspond to revision types that have been de ned in Customizing for Plant
Maintenance and Customer Service under Maintenance and Service Processing Maintenance Event Builder Maintain
Revision Type . To be able to create maintenance events, de ne one or more revision types with the following details:

In the WPS Control table column, select Planning Bucket.

If you want the system to create an administrative maintenance order for a maintenance event, assign an order type to
the relevant revision type. If you do not want the system to create an administrative maintenance order, do not assign
an order type to the revision type.

To be able to create a maintenance event with an administrative maintenance order, you also need to de ne a scheduling type
Only Capacity Requirements for which the With Time checkbox is selected. You can de ne scheduling types in Customizing for
Plant Maintenance and Customer Service under Maintenance and Service Processing Maintenance and Service Orders
Scheduling Maintain Scheduling Types .

Comparison: Maintenance Event and Revision

Understand the difference between a maintenance event and a revision and nd out which solution can be used in which
business scenario.

De nition

This is custom documentation. For more information, please visit the SAP Help Portal 58
 7/16/2023
In general, the terms revision and maintenance event both refer to a period of time during which several maintenance activities
need to be planned and executed together on one or more technical objects. In some cases, it may be necessary to temporarily
shut down a technical object so that service or maintenance work can be performed.

To facilitate the planning of the maintenance activities, you can create an object called a revision or maintenance event and, for
example, assign maintenance orders to it. The term revision is used if you create and manage this object in SAP GUI. The term
maintenance event is used if you create and manage this object in the SAP Fiori app Manage Maintenance Planning Buckets.

Revisions and maintenance events differ in their complexity and available features. For example, while you need to specify the
same basic details when you create a revision or a maintenance event (planning plant, start and end, unique ID), you can de ne
different scope attributes to indicate which execution objects are relevant for the revision or maintenance event. Note that
using the phase model is optional for both maintenance events and revisions.

Comparison
The following overviews compare maintenance events with different ways to create and manage revisions in SAP S/4HANA and
highlight some key features that are available in each case.

Creation and Purpose

Maintenance event Revision Revision for Simpli ed revision

Maintenance Event
Builder

UI technology SAP Fiori SAP GUI SAP GUI SAP GUI

Transaction / app Manage Maintenance IWR1 IWR1 OIOB

Planning Buckets
WPS1
(F3888)

Terminology Maintenance event Revision Revision Revision

Purpose Allows you to create and Allows you to manage Allows you to manage Provides a simpli ed
manage one-off one-off maintenance one-off maintenance way to group
maintenance projects projects in SAP GUI. projects in SAP GUI maintenance activities in
using the Manage using the Maintenance SAP GUI.
Maintenance Planning Event Builder.
Buckets app.
For more information, see
For more information, see Maintenance Event
Maintenance Events. Builder.

This is custom documentation. For more information, please visit the SAP Help Portal 59
 7/16/2023

Maintenance event Revision Revision for Simpli ed revision

Maintenance Event
Builder

De nition of revision Mandatory Mandatory Mandatory Not available

type required
Control type: Planning Control type: Not WPS Control type: WPS
You de ne revision types Bucket Controlled Controlled
in Customizing for Plant
For more information, see
Maintenance and
Customizing.
Customer Service under
Maintenance and
Service Processing
Maintenance Event
Builder Maintain
Revision Type .

When you de ne a
revision type, you need
to select a control type in
the WPS Control table
column of this
Customizing activity to
determine how revisions
or maintenance events of
the corresponding type
can be processed.

For more information,

refer to the
documentation of this
Customizing activity.

Key Features

Maintenance event Revision Revision for Simpli ed revision

Maintenance Event
Builder

Possibility to manage Yes No No No

using the Manage
For more information, see
Maintenance Planning
Managing Maintenance
Buckets app (F3888)
Events.
and the Manage
Maintenance Backlog
app (F4073)

Possibility to visualize in Yes No No No

the Manage
For more information, see
Maintenance Schedule
Finding and Using
for Assets app (F4577)
Maintenance Windows.
that is available for
Resource Scheduling

For more information, see

Manage Maintenance
Schedule for Assets.

Integration with No No Yes No

Maintenance Event
Builder

This is custom documentation. For more information, please visit the SAP Help Portal 60
 7/16/2023

Maintenance event Revision Revision for Simpli ed revision

Maintenance Event
Builder

Possibility to create an Yes No No No

administrative
For more information, see
maintenance order, e.g.
Administrative
to determine the system
Maintenance Orders.
condition and to record
overhead costs

Possibility to assign Yes Yes Yes Yes

maintenance orders
For more information, see You can create orders for
Managing Maintenance a revision. For more
Events. information, see Creating
Orders in the
Maintenance Event
Builder.

Possibility to assign No Yes Yes Yes

maintenance
noti cations

Possibility to reschedule Yes Yes, using transaction Yes, using the Yes, using transaction
along with assigned IW38 to refresh the Maintenance Event IW38 to refresh the
For more information, see
orders dates of assigned orders Builder dates of assigned orders
Managing Maintenance
Events.

Possibility to monitor Yes No Yes No

resource availability for
You can monitor the For more information, see
assigned orders
availability of materials Maintenance Event
and services as well as Builder.
the work progress of
internal resources using
the Manage
Maintenance Backlog
app. For more
information, see Manage
Maintenance Backlog.

Possibility to mark as No Yes Yes Yes

completed

Possibility to delete No Yes Yes Yes

Available Scope Attributes

Maintenance event Revision Revision for Simpli ed revision

Maintenance Event
Builder

Planning plant Mandatory Mandatory Mandatory Mandatory

One entry is possible. One entry is possible. One entry is possible. One entry is possible.

Technical object Optional Optional Optional Not available

Several entries are One entry is possible. One entry is possible.

possible. You usually specify a You usually specify a
superior functional superior functional
location. location.

This is custom documentation. For more information, please visit the SAP Help Portal 61
 7/16/2023

Maintenance event Revision Revision for Simpli ed revision

Maintenance Event
Builder

Main work center Mandatory if an Optional Mandatory Not available

administrative order is
created, otherwise One entry is possible. One entry is possible.
optional

Several entries are

possible.

WBS element and Not available Optional Optional Not available

network

Planner group Optional Not available Not available Not available

Several entries are

possible.

Plant section Optional Not available Not available Not available

Several entries are

possible.

Maintenance plant Optional Not available Not available Not available

Several entries are

possible.

Maintenance orders can Yes Partially Partially No

only be assigned if they
match the speci ed For more information, see The technical object The technical object
attributes Managing Maintenance must belong to the same must belong to the same
Events. object hierarchy. object hierarchy.

Managing Maintenance Events

Once you have created a maintenance event, you can assign maintenance orders to the event. When you need to change the
dates of the maintenance event, you can choose to reschedule these orders automatically.

Prerequisites
You have created a maintenance event using the Manage Maintenance Planning Buckets app. For more information, see
Creating Event-Based Maintenance Planning Buckets.

Assigning Maintenance Orders to a Maintenance Event

When you create or change a maintenance order, you have the option to assign the order to a maintenance event. In addition,
the Change Scheduling quick action in the Find Maintenance Orders app and the Manage Maintenance Backlog app also allow
you to assign one or more maintenance orders to a maintenance event.

When you assign a maintenance order to a maintenance event, you can choose to align the execution dates of the maintenance
order with the dates of the maintenance event. The event dates are copied to the order header and are then adjusted based on
parameters like the duration of the operations, scheduling constraints, and the available capacity of the work center.

You can view all orders that have been assigned to a maintenance event in the maintenance backlog of the maintenance
planning bucket to which the maintenance event belongs.

This is custom documentation. For more information, please visit the SAP Help Portal 62
 7/16/2023

 Note
You can only assign maintenance orders to a maintenance event that coincide completely with all the criteria that you have
de ned as the planning bucket scope. When you have assigned an order to a maintenance event and change the planner
group, maintenance plant, technical object, plant section, or main work center of the order in such a way that it no longer
matches the de ned planning bucket scope, the system raises an error message. You can change the con guration of these
messages in Customizing for Plant Maintenance and Customer Service under Maintenance and Service Processing
Maintenance and Service Orders Message Control and determine whether they should be shown as warning messages,
information messages, or not at all. To do this, you must make the desired setting for the relevant messages in message
class EAM_MTPLNGBKT.

Editing a Maintenance Event

To edit a maintenance event, open the corresponding event-based planning bucket in edit mode. You can then change the
planning bucket description and the time period. If you have created a maintenance event without an administrative
maintenance order and if no additional maintenance orders have been assigned to the maintenance event, you can also edit the
planning bucket scope.

When you change the time period of an existing maintenance event, you can specify whether the assigned orders should also be
rescheduled to ensure that the execution dates fall into the new time period of the maintenance event. You have these options:

No Orders: The system changes the dates of the maintenance event without adjusting the dates of any assigned orders.
If you choose this option, the assigned orders may no longer fall into the time period of the maintenance event. If an
administrative maintenance order has been created for the event, this order will be rescheduled even if you select this
option.

Unscheduled Orders: The system changes the dates of the maintenance event and adjusts the dates of any assigned
orders that have not yet been scheduled for execution. The following orders remain unchanged, so they may no longer
fall into the time period of the maintenance event:

Orders with dispatched operations

Orders with operations that have been marked as Job in Process (JIPR), for example by printing a job card

Orders with con rmed operations

Orders with operations that have scheduling constraints

All Orders: The system changes the dates of the maintenance event and adjusts the dates of all assigned orders. It
removes any constraint dates that do not fall within the new time period of the maintenance event. It also cancels any
dispatched operations and resets the system status of the relevant orders and operations to Ready for Scheduling
(ORSC). Note that changing the dates of scheduled orders is not always possible, for example when con rmations have
already been posted.

If you choose the option All Orders or Unscheduled Orders, the system processes the relevant changes in the background when
you save the maintenance planning bucket. You can view the status of the mass change as well as detailed warning and error
messages in the Application Logs.

 Note
The scheduling type of an order has an impact on whether the order can be rescheduled. If an order is not rescheduled and
the system does not raise a message, review the relevant scheduling parameters in Customizing.

Related Information
Maintenance Events

This is custom documentation. For more information, please visit the SAP Help Portal 63
 7/16/2023
Creating Event-Based Maintenance Planning Buckets
Comparison: Maintenance Event and Revision

Administrative Maintenance Orders

Administrative maintenance orders are maintenance orders with limited processing options that can be created for a
maintenance event to block the production capacity of the technical object in the order header. They can also be used to record
additional overhead costs.

When you create a maintenance event in the Manage Maintenance Planning Buckets app, you can choose to automatically
create an administrative maintenance order to plan the maintenance work and block the production capacity of the technical
object on which the maintenance is performed. This maintenance order will be permanently assigned to the maintenance event.
It automatically inherits the time and scope data of the planning bucket to which the maintenance event belongs. It also inherits
the system condition that you specify when you create the maintenance event. Whether or not an administrative maintenance
order is created depends on the con guration of the respective maintenance event type in Customizing. For more information,
see Maintenance Events.

Special Characteristics
In general, an administrative maintenance order can be processed like any other maintenance order of the respective order
type. However, there are some special characteristics and restrictions:

The basic start date and time and the basic end date and time correspond to the time period that has been speci ed in
the corresponding planning bucket. You can only edit these dates in the planning bucket. If you change the dates in the
planning bucket, they are updated automatically in the maintenance order.

The technical object corresponds to the technical object that has been speci ed in the corresponding planning bucket. If
several technical objects have been speci ed, the rst technical object is copied to the order header and the other
technical objects are copied to the object list. The technical object and the object list cannot be edited.

The system condition corresponds to the system condition that has been speci ed when creating the maintenance
event. The system condition cannot be edited.

The maintenance event to which the administrative maintenance order is assigned is copied to the order header. The
assignment cannot be changed.

The planning plant corresponds to the planning plant that has been speci ed in the corresponding planning bucket. The
planning plant cannot be edited.

If a planning bucket scope has been de ned by specifying a maintenance plant, a plant section, a main work center,
and/or a planner group, these attributes are also copied to the maintenance order. If several values have been speci ed
for any of these attributes in the planning bucket, only the rst value is copied to the maintenance order. Editing these
elds is restricted:

You cannot edit the maintenance plant.

You can only edit the plant section, the main work center, and the planner group as long as they still match the
de ned planning bucket scope. If you enter a value that doesn't match the planning bucket scope, the system
raises an error message. You can change the con guration of these messages in Customizing for Plant
Maintenance and Customer Service under Maintenance and Service Processing Maintenance and Service
Orders Message Control and determine whether they should be shown as warning messages, information
messages, or not at all. To do this, you must make the desired setting for the relevant messages in message class
EAM_MTPLNGBKT.

Related Information
This is custom documentation. For more information, please visit the SAP Help Portal 64
 7/16/2023
Creating Event-Based Maintenance Planning Buckets

Manage Maintenance Backlog

With this app, you can view a list of the maintenance orders that are associated with a speci c maintenance planning bucket.
The maintenance backlog of an operational planning bucket shows all orders that have been automatically assigned to the
planning bucket according to their scheduled start, their scheduled end, and to the attributes tting in the scope of the planning
bucket. The maintenance backlog of an event-based planning bucket shows all orders that have been assigned manually to the
maintenance event. Orders that have been set to Do not execute or that have been marked for deletion are not displayed in
this app.

You can view important order details, such as the order status, the order priority and the nal due date. You can view the
availability and consumption of the required stock components, view messages from the latest ATP check, and navigate directly
to the Schedule Material Availability Check app. You can monitor the procurement process for all required non-stock
components and external services. In addition, you can view all maintenance work that has to be performed by an internal work
center.

You can only access this app via the Manage Maintenance Planning Buckets app and the Maintenance Backlog Overview app.

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.

Key Features
You can use this app to:

Jump easily from the maintenance orders of the current planning bucket to those of the previous or the next planning
bucket.

View a list of all maintenance orders associated with the selected planning bucket or a pre- ltered list of maintenance
orders that are in the Preparation phase.

Check the overall readiness of the order with the help of colored icons indicating whether the maintenance order is time-
critical, whether the required materials and services are expected to be available, and whether the order has already
been submitted for scheduling.

Select individual orders and pass them on to the Scheduling phase.

Select one or more maintenance orders and reschedule them either by changing the basic start and end dates or by
assigning them to the next or the previous planning bucket.

Assign one or more maintenance orders to a maintenance event using the Change Scheduling quick action. You can also
unassign maintenance orders from a maintenance event.

Branch to the maintenance orders and the assigned technical objects by using the corresponding links.

View order details, such as the order status, the priority and the nal due date.

View order operation details such as the execution stage and the short text.

Check the availability and consumption of the required stock components for all maintenance orders associated with the
selected planning bucket or particularly for orders in the Preparation phase.

This is custom documentation. For more information, please visit the SAP Help Portal 65
 7/16/2023
The Schedule Material Availability Check app allows you to perform an enhanced ATP check and reassign stock material
to the maintenance orders with the highest priority and urgency. Messages from the latest ATP run are displayed if you
click on the Status symbols of the stock components.

Check whether committed quantities of a component can be cleared or reassigned to another order in a material
availability check, and change this setting for one or more components using a quick action. For more information, see
How to Perform an ATP Check for Stock Components.

View the details of the stock component, such as the goods movement type and the product type.

Branch to the product master data of the stock component by using the corresponding links.

Monitor the required quantity, the committed quantity and the withdrawn quantity of the stock component.

Monitor the procurement of the required non-stock components and external services for all maintenance orders
associated with the selected planning bucket or particularly for orders in the Preparation phase. For more information,
see Monitoring Procurement Activities.

View the supplier from whom a required non-stock component or external service is procured.

Monitor the requirement date for non-stock components and external services.

Branch to the supplier or the material master data by using the corresponding links.

View the relevant purchase requisition and purchase order, and display the details via a link.

Monitor the details and the actual work progress of any internal resources that are needed for completing the
maintenance work.

View the operation and suboperation details, such as the work center or the execution stage.

Check the work progress by evaluating the forecast work, the actual work and the remaining work.

Identify time-critical maintenance work by monitoring the earliest start and end dates as well as the execution start and
end dates.

View the details of a maintenance planning bucket. For more information, see Manage Maintenance Planning Buckets.

In addition, the app supports the following technical features and options:

If the long material number has been activated in your back-end system, it is automatically displayed in the Material eld in this
SAP Fiori app.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
App Implementation: Manage Maintenance Backlog
Manage Maintenance Planning Buckets
Monitoring Procurement Activities
Procurement Milestones
Maintenance Process Phases

This is custom documentation. For more information, please visit the SAP Help Portal 66
 7/16/2023

App Implementation: Manage Maintenance Backlog

Prerequisites
Before implementing the app, you must ensure the following:

You can use this app to monitor the procurement of non-stock materials and services by means of procurement
milestones. The completion of some milestones depends on changes in the purchase order and posting of the goods
receipt for non-stock components. To enable the system to react to these changes and update the respective milestones
automatically, you need to activate the corresponding event type linkages as described in the Con guration Tasks below.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F4073.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) EAM_BACKLOG_MANAGE (0001)

For more information about activating OData services, see Activating OData Services.

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application EAM_BL_MANS1

/sap/bc/ui5_ui5/sap/eam_bl_mans1

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

This is custom documentation. For more information, please visit the SAP Help Portal 67
 7/16/2023
The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

EAM_BACKLOG_MANAGE (0001) You can use the example business catalog Assign the existing role
SAP_EAM_BC_PLNBKTS_MNG or your SAP_BR_MAINTENANCE_PLANNER or
custom catalog to create the back-end create a new one.
PFCG role.

Con guration Tasks

To enable the system to update the procurement milestones automatically based on changes in the purchase order and
posting of the goods receipt, you need to activate the corresponding event type linkages in Customizing for Plant
Maintenance and Customer Service under Maintenance and Service Processing Maintenance and Service Orders
Functions and Settings for Order Types Procurement .

If you want to change the default procurement milestones for a combination of maintenance order type, procurement
demand category, maintenance plant, and material group, you can de ne custom rules in Customizing for Plant
Maintenance and Customer Service under Maintenance and Service Processing Maintenance and Service Orders
Functions and Settings for Order Types Procurement De ne Assignment Rules for Procurement Milestones .

Related Information
Manage Maintenance Backlog
Monitoring Procurement Activities
Manage Maintenance Planning Buckets
Maintenance Process Phases

This is custom documentation. For more information, please visit the SAP Help Portal 68
 7/16/2023

Schedule Material Availability Check

Use
As a maintenance planner, you can use this app to execute material availability checks for several maintenance orders at
runtime or schedule these checks as a recurrent batch job.

The system checks whether the components required for a maintenance order are available and updates the availability status
in the orders accordingly. If you schedule the availability check as a batch job, a report displays all error and warning messages
that occurred during the checking process, as well as the system and user statuses of the orders.

If you also schedule maintenance orders that are processed by phases, the Material Availability Check for Maintenance Orders
template enables you to reassign committed stock from one maintenance order to another of higher priority and urgency.

For more information, see How to Perform an ATP Check for Stock Components.

Note

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

You can view a list of all material availability checks already scheduled and navigate to the results of the jobs that you have
created.You can only view the job results on desktop devices.

You can schedule new material availability checks:

Choose a job template and enter a job name.

Specify the scheduling options:

Specify the date and time for the system to start the scheduling. You can also decide to start the scheduling run
immediately.

Enter a recurrence pattern to specify how often the scheduling job is to be processed. You can run the job daily or
even several times a day.

Specify the parameters of the material availability check. The parameters depend on the job template that you have
chosen.

In the Material Availability Check for Maintenance Orders template, specify the following parameters:

Restrict the maintenance orders to be included in the ATP run by selecting one or more maintenance order types,
maintenance planning plants and maintenance activity types.

Determine the maintenance orders by their scheduled start date and scheduled end date. Alternatively, you can
determine a relative scheduled date to select maintenance orders within a rolling time period when scheduling
recurrent ATP runs.

Select one or more process phases.

Select one or more execution stages to restrict the operations whose components are to be included in the ATP
run.

Select one or more material groups to restrict the stock components that are to be assigned in the ATP run.

Determine the scheduling options and specify whether the system should clear all committed material quantities
and reassign the committed stock material.

This is custom documentation. For more information, please visit the SAP Help Portal 69
 7/16/2023
In the PM Orders: Material Availability Check template, specify the following parameters:

Use parallel processing for the automatic scheduling of material availability checks, and specify the number of
threads the system may use.

Specify whether the system is to display all messages or only errors and exceptions.

Specify whether you want the results to be saved to the application log.

Specify which status orders must have so that they are considered by the availability check ( for example In
Progress, Outstanding, Completed, Historical)

Specify additional selection parameters, such as location parameters or account assignment parameters

Enter general data or administration data as additional selection parameters

Supported Device Types

Desktop

Tablet

Related Information
App Implementation: Schedule Material Availability Check
How to Perform an ATP Check for Stock Components
Maintenance Process Phases

App Implementation: Schedule Material Availability Check

Prerequisites
Before implementing the app, you must ensure the following:

This app provides two templates with different options to specify the parameters of the material availability check. To
use either of these templates, you need to activate them in Customizing as described in the Con guration Tasks below.
For a description of the functionalities offered by each template, see Schedule Material Availability Check. Note that the
Material Availability Check for Maintenance Orders template has been designed to be used within the functional scope
of the Reactive Maintenance (4HH) and Proactive Maintenance (4HI) scope items and some of the functionality
requires that the maintenance orders are processed by phases.

Tile Type for Launching App

The Schedule Material Availability Check app is launched using an app launcher tile.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

This is custom documentation. For more information, please visit the SAP Help Portal 70
 7/16/2023

Back-End / Front-End Server SAP Note Description

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F2465.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) APJ_JOB_MANAGEMENT_SRV (0001)

For more information about activating OData services, see Activating OData Services.

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application NW_APS_APJ

/sap/bc/ui5_ui5/sap/nw_aps_apj

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

This is custom documentation. For more information, please visit the SAP Help Portal 71
 7/16/2023
Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

APJ_JOB_MANAGEMENT_SRV (0001) You can use the example business catalog Assign the existing role
SAP_EAM_BC_ORD or your custom catalog SAP_BR_MAINTENANCE_PLANNER or
to create the back-end PFCG role. create a new one.

Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:

This app provides two templates with different options to specify the parameters of the material availability check: The
PM Orders: Material Availability Check template and the Material Availability Check for Maintenance Orders template.
To use one or both of these templates, you need to activate them by entering the name of the relevant application job
catalog entry in the table APJ_C_SCOPE. You do this in the Customizing activity Activation of Scope-Dependent
Application Job Catalog Entries in the SAP Customizing Implementation Guide under ABAP Platform Application
Server System Administration .

Template Application Job Catalog

PM Orders: Material Availability Check SAP_PM_EAM_ATP_RIAUFK20

Material Availability Check for Maintenance Orders SAP_PM_EAM_MATL_AVAILY_CHECK

Related Information
Schedule Material Availability Check
Maintenance Process Phases

How to Perform an ATP Check for Stock Components

You can use the Schedule Material Availability Check app to execute material availability checks for several maintenance
orders. You can also schedule these checks as a recurrent batch job. The Material Availability Check for Maintenance Orders
template enables you to reassign committed stock from one maintenance order to another of higher priority and urgency.

To check the availability of the required stock components and reassign required material, proceed as follows:

Create a new job and select the Material Availability Check for Maintenance Orders template. This template provides
enhanced lter parameters and the option of reassigning committed stock material.

After having de ned the Scheduling Options, select values for the lter parameters and thereby determine which
maintenance orders shall be included in the ATP run:

This is custom documentation. For more information, please visit the SAP Help Portal 72
 7/16/2023
Restrict the maintenance orders to be included in the ATP run by selecting one or more maintenance order types,
maintenance planning plants and maintenance activity types from the input help.

Determine the maintenance orders by their scheduled start date and scheduled end date. The ATP run considers
all maintenance orders whose scheduled start dates and scheduled end dates lie within the de ned time frame.
Alternatively, you can determine a relative scheduled date to select maintenance orders within a rolling time
period when scheduling recurrent ATP runs. The system then includes all maintenance orders in the ATP run
which have their scheduled start date in the selected time period. Note that the scheduled end date of the
maintenance orders is not taken into account in this case.

If you have determined a relative scheduled date as selection criterion, the system will no longer consider any
values that you might have entered in the Scheduled Start Date and Scheduled End Date selection elds and
therefore deletes the corresponding lter values.

Select one or more process phases. The system only includes maintenance orders in the ATP run that belong to
one of the selected phases. By default, the phases Planning (03), Approval (04) and Preparation (05) are
selected. In addition, you can select the phases Scheduling (06) and Execution (07).

If you have entered selection values in the Maintenance Order Type eld as well as in the Process Phase eld, the
ATP run considers maintenance orders as follows:

The system considers all maintenance orders of those order types that have not been activated for the
phase model. Maintenance orders of these order types are all included in the ATP run independently of any
entries you may have made in the Process Phase eld.

The system only considers those maintenance orders which are in the selected process phases if the order
type of these orders has been activated for the phase model.

Select one or more execution stages to restrict the operations whose components are to be included in the ATP run. You
can, for example, determine that only the components of main operations should be evaluated.

Select one or more material groups to restrict the stock components that are to be assigned in the ATP run. With this
lter parameter you can execute availability checks based on individual material groups.

Determine the scheduling options. If you select the Reset Availability Data checkbox together with the Execute
Availability Check checkbox, the system checks the reservations that have been created for the maintenance orders and
clears all committed material quantities. In a second step, the system reassigns the available stock material to the
maintenance orders taking the following parameters into account:

1. the nal due date

2. the priority

3. the ABC indicator

4. the scheduled basic start date and time

5. the scheduled basic end date and time

Taking these parameters into account, the system ensures that the required stock components are assigned to the
maintenance orders with the highest priority and urgency. If an order does not have scheduled dates, the system uses
the basic start date and time and the basic end date and time instead.

If you do not want the system to clear the committed quantities in the reservations for maintenance orders that have
already been scheduled, make sure that you have not included the process phase Scheduling (06) and higher as a
parameter value for the order selection.

To check material availability without clearing and reassigning any committed stock, do not select the Reset Availability
Data checkbox.

This is custom documentation. For more information, please visit the SAP Help Portal 73
 7/16/2023
If you only select the Reset Availability Data checkbox, the system sets all committed material quantities to 0. You can
use this option to free up material availability by removing all committed stock from a set of maintenance orders.

When you create or change a maintenance order, you can manually determine that committed quantities of individual
components should not be cleared and reassigned during a material availability check by selecting the Keep Committed
Quantities checkbox. In this case, available quantities will only be assigned to the respective maintenance order but
cannot be removed by the ATP check. For more information, see Working with Operation Data in the Order.

 Caution
When running an ATP check, the system groups the orders by the required materials and sequentially processes
these groups. Orders are only locked for editing while a corresponding group of materials is processed.

If you choose to reassign committed stock materials, any orders that are open in change mode during an ATP run may
be excluded from the reassignment of some or all materials. This has the following consequences for these orders:

Shortages may not be covered. If new stock material is available, it might be assigned to other orders, possibly
of lower priority and urgency.

Committed stock material might not be reassigned to other, more important orders.

Orders that have not been included in an ATP run are listed in the log. To include these orders in the reassignment,
you need to schedule another ATP check.

To minimize the exclusion of orders, different background jobs should not be scheduled at the same time and ideally
run outside working hours.

After the ATP check has been executed, the system will also adjust the header-level system status to indicate the overall
material situation of the order, for example Material Committed (MACM).

Schedule Output for Maintenance Orders

With this app, you can create application jobs to schedule the output for maintenance orders.

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.

Key Features
You can use this app to do the following:

Create a new job to schedule the output for maintenance orders.

Select orders to be output based on different parameters.

Schedule the output of maintenance orders for a speci c day and time, set up a recurrence, or send orders to the output
immediately.

Check the correctness of entered data before scheduling a job.

View the log of each scheduled job in the Application Jobs list. You can, for example, see whether a job was carried out
successfully or was canceled.

Filter the Application Jobs list using different criteria, such as date, job name, job status, or the person who created the
job.

This is custom documentation. For more information, please visit the SAP Help Portal 74
 7/16/2023
Copy an existing job and use it as a template for a new job that is similar to the existing one.

 Note
Maintenance orders are printed or sent by email based on the prede ned parameters of the output channel.

Supported Device Types

Desktop

Tablet

App Implementation: Schedule Output for Maintenance Orders

Prerequisites
Before implementing the app, you must ensure the following:

This app provides a template to specify the parameters for the maintenance order output. To use this template, you
need to activate it in Customizing as described in the following Con guration Tasks.

Tile Type for Launching App

The Schedule Output for Maintenance Orders app is launched using an app launcher tile.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F6075.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) APJ_JOB_MANAGEMENT_SRV (0001)

For more information about activating OData services, see Activating OData Services.
This is custom documentation. For more information, please visit the SAP Help Portal 75
 7/16/2023

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application NW_APS_APJ

/sap/bc/ui5_ui5/sap/nw_aps_apj

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

APJ_JOB_MANAGEMENT_SRV (0001) You can use the example business catalog Assign the existing role
SAP_EAM_BC_OSAM_MNG_PC or your SAP_BR_BPC_EXPERT or create a new
custom catalog to create the back-end one.
PFCG role.

Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:

This is custom documentation. For more information, please visit the SAP Help Portal 76
 7/16/2023
This app provides a template to specify the parameters of the maintenance order output: Job Template for Scheduling
Mass Output for Maintenance Orders. To use this template, you need to activate it by entering the name of the relevant
application job catalog in the table APJ_C_SCOPE. You do this in the Customizing activity Activation of Scope-
Dependent Application Job Catalog Entries in the SAP Customizing Implementation Guide under ABAP Platform
Application Server System Administration .

Template Application Job Catalog

Job Template for Scheduling Mass Output for Maintenance SAP_EAM_MAINTORDER_MASS_OUTPUT

Orders

Related Information
Schedule Output for Maintenance Orders

Schedule Output for Maintenance Noti cations

With this app, you can create application jobs to schedule the output for maintenance noti cations.

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.

Key Features
You can use this app to do the following:

Create a new job to schedule the output for maintenance noti cations.

Select noti cations to be output based on different parameters.

Schedule the output of maintenance noti cations for a speci c day and time, set up recurrence, or send noti cations for
the output immediately.

Check whether the entered data is correct before scheduling a job.

View the log of each scheduled job in the Application Jobs list. You can, for example, see whether a job was carried out
successfully or was cancelled.

Filter the Application Jobs list using different criteria, such as date, job name, job status, or the person who created the
job.

Copy an existing job and use it as a template for a new job that is similar to the existing one.

 Note
Maintenance noti cations are printed out or sent by email based on the prede ned parameters of the output channel.

Supported Device Types

This is custom documentation. For more information, please visit the SAP Help Portal 77
 7/16/2023
Desktop

Tablet

App Implementation: Schedule Output for Maintenance

Noti cations

Prerequisites
Before implementing the app, you must ensure the following:

This app provides a template to specify the parameters of the maintenance noti cation output. To use this template, you
need to activate it in Customizing as described in the following Con guration Tasks.

Tile Type for Launching App

The Schedule Output for Maintenance Noti cations app is launched using an app launcher tile.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F6074.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) APJ_JOB_MANAGEMENT_SRV (0001)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application NW_APS_APJ

This is custom documentation. For more information, please visit the SAP Help Portal 78
 7/16/2023

Component Technical Name

/sap/bc/ui5_ui5/sap/nw_aps_apj

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

APJ_JOB_MANAGEMENT_SRV (0001) You can use the example business catalog Assign the existing role
SAP_EAM_BC_OSAM_MNG_PC or your SAP_BR_BPC_EXPERT or create a new
custom catalog to create the back-end one.
PFCG role.

Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:

This app provides a template to specify the parameters of the maintenance noti cation: Job Template for Scheduling
Mass Output for Maintenance Noti cations. To use this template, you need to activate it by entering the name of the
relevant application job catalog in the table APJ_C_SCOPE. You do this in the Customizing activity Activation of Scope-
Dependent Application Job Catalog Entries in the SAP Customizing Implementation Guide under ABAP Platform
Application Server System Administration .

This is custom documentation. For more information, please visit the SAP Help Portal 79
 7/16/2023

Template Application Job Catalog

Job Template for Scheduling Mass Output for Maintenance SAP_EAM_MAINTNOTIF_MASS_OUTPUT

Noti cations

Related Information
Schedule Output for Maintenance Noti cations

SAP Apps for S/4HANA Output Management

Manage Work Packs

With this app, you can nd existing work packs, select work packs, job packs, and included items and send them to the output
immediately or schedule them to be eligible for the mass output. A work pack consists of a list of job packs in which the system
can output together and the work order operations (jobs) belonging to the corresponding job packs (the set of jobs in a job pack
are work order operations that you can create one output request for). Work packs allow you to include multiple output types
and leverage support for print and email channels for the output.

Key Features
You can use this app to do the following:

Search for and display created work packs

See detailed information about selected work packs, such as type, grouping criteria, output status

Select work packs, job packs, and job pack items and send them to the output immediately or prepare them for mass
output

Select multiple attachments, add them to a single output item, and trigger a single printout or email.

Attachments for noti cations are retrieved from:

Noti cation header

Equipment in the noti cation header

Functional location in the noti cation header

Attachments from an order are retrieved from:

Order header

Equipment in the order header

Functional location in the order header

Operations of the order

Equipment in the operation of the order

Functional location in the operation of the order

Object list of the order

Equipment in the object list of the order

Functional location in the object list of the order

This is custom documentation. For more information, please visit the SAP Help Portal 80
 7/16/2023
Noti cation from the order header

Noti cation from operations of the order

 Note
Only PDF type documents can be added to output items to create a single document. All other document types are
considered separate documents.

Retry output or set the status of the output to completed manually in case of any errors

Prerequisites
To view the app, ensure that the business catalog SAP_EAM_BC_WRKPCK_MNG is assigned for the roles Maintenance Planner
and Maintenance Supervisor.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
Schedule Output for Maintenance Job Packs

Create Work Pack

Create work packs that include one or more maintenance order operations.

Context
You can create work packs from maintenance order operations using the quick action button Create Work Pack in the apps Find
Maintenance Orders and Find Maintenance Orders and Operations.

When you create a work pack, you select one or more maintenance order operations to be included in the work pack, choose a
work pack type, and assign a grouping criterion for your new work pack.

 Note
For work packs to be successfully created for maintenance order operations with an active phase model, the system status
must be DSPT (Dispatched), for maintenance order operations with an inactive phase model, the system status must be
REL (Released)

 Note
Some work pack grouping criteria are delivered by default. You can use the following work pack con gurations:

De ne Grouping Criteria for Work packs: For work pack output management, you can enable creation of grouping
criteria for work packs and work pack items.

This is custom documentation. For more information, please visit the SAP Help Portal 81
 7/16/2023
Assign Grouping Criteria to Work Pack Type: You have the option to choose and assign grouping criteria for work pack
types.

Procedure
1. To create a work pack, select at least one maintenance order operation from the list report. Then choose Create Work
Pack.

2. In the dialog window, enter values for Work Pack Name, Work Pack Type, and Group By.

The name of the work pack is populated by the system but you can choose another name.

Choose the work pack type from the drop-down list of all available work pack types.

Select one grouping criteria for the work pack type. Depending on the Work Pack Type selected, the relevant
values are provided in the drop-down list.

You can also decide if you want to include work pack operations that are already included in other work packs in
the new work pack.

3. Select Save, to schedule the background application job that creates your new work pack.

4. In the Application Logs, you can check the status of the scheduled job and see if it has been successfully completed or if
any errors occurred.

Related Information
Manage Work Packs

Schedule Output for Maintenance Job Packs

With this app, you can create application jobs to schedule the output for maintenance job packs.

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.

Key Features
You can use this app to do the following:

Create a job to schedule the output for maintenance job packs.

Select job packs to be output based on different parameters.

Schedule the output of maintenance job packs for a speci c day and time, set up recurrence, or send job packs for the
output immediately.

Check whether the entered data is correct before scheduling a job

View the log of each scheduled job in the Application Jobs list. You can, for example, see whether a job was carried out
successfully or was cancelled. You can lter the list based on different criteria, such as date, job status, and the person
who created the job.

Filter the Application Jobs list using different criteria, such as date, job name, job status, or the person who created the
job.
This is custom documentation. For more information, please visit the SAP Help Portal 82
 7/16/2023
Copy an existing job and use it as a template for a new job that is similar to the existing one.

Prerequisites
For maintenance job packs to be eligible for scheduling to the output, the following parameters must be set by the Maintenance
Planner or Maintenance Supervisor in the Manage Work Pack app:

The status is set to To Be Output.

The dispatch time is set to Scheduled.

Emails of Sender and Receiver are set and valid.

 Note
Maintenance Job Packs are printed out or sent by email based on the prede ned parameters of the output channel.

Supported Device Types

Desktop

Tablet

App Implementation: Schedule Output for Maintenance Job

Packs

Prerequisites
Before implementing the app, you must ensure the following:

This app provides a template to specify the parameters of the maintenance noti cation output. To use this template, you
need to activate it in Customizing as described in the following Con guration Tasks.

Tile Type for Launching App

The Schedule Output for Maintenance Noti cations app is launched using an app launcher tile.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks

This is custom documentation. For more information, please visit the SAP Help Portal 83
 7/16/2023
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F6076.

Back-End Server: Create Connectors

This app is based on ABAP Core Data Services and does not require search models to work. However, if you want to start the
app from the search results list, you must activate the underlying search connectors. You can create connectors in transaction
ESH_COCKPIT.

For more information, see Creating Connectors.

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Object pages are based on search models. To be able to use an object page, you must activate the underlying search models by
creating connectors. Create connectors in transaction ESH_COCKPIT.

You can nd the search models for this app in the SAP Fiori apps reference library.

For more information, see Creating Connectors.

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) APJ_JOB_MANAGEMENT_SRV (0001)

For more information about activating OData services, see Activating OData Services.

This is custom documentation. For more information, please visit the SAP Help Portal 84
 7/16/2023

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application NW_APS_APJ

/sap/bc/ui5_ui5/sap/nw_aps_apj

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

APJ_JOB_MANAGEMENT_SRV (0001) You can use the example business catalog Assign the existing role
SAP_EAM_BC_OSAM_MNG_PC or your SAP_BR_BPC_EXPERT or create a new
custom catalog to create the back-end one.
PFCG role.

Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:

This is custom documentation. For more information, please visit the SAP Help Portal 85
 7/16/2023
This app provides a template to specify the parameters of the maintenance order output: Job Template for Scheduling
Mass Output for Maintenance Job Packs. To use this template, you need to activate it by entering the name of the
relevant application job catalog in the table APJ_C_SCOPE. You do this in the Customizing activity Activation of Scope-
Dependent Application Job Catalog Entries in the SAP Customizing Implementation Guide under ABAP Platform
Application Server System Administration .

Related Information
Schedule Output for Maintenance Job Packs

Actual Cost Analysis

This app supports you in monitoring and evaluating actual costs resulting from current maintenance orders. It enables you, for
example, to analyze the actual costs for materials and labor in maintenance or to compare the total corrective and preventive
actual maintenance costs during a selected time period. In addition, you can easily identify the maintenance activities leading to
the highest costs or the parts of the asset that were particularly costly on inspections. Altogether, this analytical list page offers
you multiple possibilities to evaluate actual maintenance costs stored in the Universal Journal Entry.

Filters allow you to analyze critical costs in a speci c scal year from different perspectives, such as the order type, the
construction type, the location, the planner group or the manufacturer. A condensed view enables you to identify and compare
relevant areas within data sets using data visualization and business intelligence. On the other hand, you can also navigate
directly to signi cant single instances. All this can be done seamlessly within one page that combines transactional and
analytical data using chart and table visualization.

This app is available for the maintenance planner user role.

Key Features
In the header area that can be collapsed or expanded, lter the result set, which feeds the main content area

Select the lters to be displayed and combine multiple lters in different ways

Add lter values by using the value help

Gain a condensed overview of the actual costs in colored charts in the visual lter bar and thereby spot relevant data
more quickly

Decide whether non-time-related data is to be displayed in an interactive doughnut chart or in a bar chart

Display time series data in a line chart with up to six data points

In the content area, switch between the chart-only view, the table-only view and the hybrid view that combines both,
chart and table view

In the chart view, analyze aggregated actual cost data from different perspectives and use the drilldown functionality

In the chart view, easily change chart types, customize the chart settings and use the drilldown option to change the
chart grouping dimension

In the table view, access the transactional content and act on maintenance orders by navigating directly to the individual
business objects

In the table view, decide which dimensions are to be displayed in the table and choose dimensions to group actual cost
data accordingly

In the hybrid view, interact with both the chart and the table. Selecting a dimension within a chart area automatically
lters all relevant information in the table area.

This is custom documentation. For more information, please visit the SAP Help Portal 86
 7/16/2023
In addition, the app supports the following technical features and options:

If the long material number has been activated in your back-end system, it is automatically displayed in the Material eld in this
SAP Fiori app. For more information, see Extended Material Number in SAP Fiori Apps.

This app uses the C_MaintOrderActualCostQ CDS view.

Supported Device Types

Desktop

Tablet

 Note
Using the app on mobile devices with small displays is not recommended due to usability issues. Small displays require
condensing the complex data and relevant information to such a degree that it might be difficult to work with the app
efficiently.

In this app, cost element hierarchies are used to determine a Spend Category for the cost elements. Together with the
relevant ledger and the company code, you select the relevant cost element hierarchy on a popup before working with the
app. However, the tables and charts of this app also include costs associated to cost elements that are not inserted in the
respective cost element hierarchy. Since the system cannot determine a Spend Category for these costs, they are not
grouped by the spend category in the table view. For more information about the necessary con guration tasks, see the app
implementation documentation.

Related Information
App Implementation: Actual Cost Analysis

App Implementation: Actual Cost Analysis

Prerequisites
In this app, cost element hierarchies are used to determine a Spend Category for the cost elements. Before implementing the
app, you therefore must ensure that cost element hierarchies are created and replicated as described in the Con guration
Tasks below.

System Landscape Requirements

For information about the system requirements, see SAP Fiori Overview.

Tile Type for Launching App

The Actual Cost Analysis app is launched using an app launcher tile.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

This is custom documentation. For more information, please visit the SAP Help Portal 87
 7/16/2023

Back-End / Front-End Server SAP Note Description

Back-End Server 2769531 Release & Information Note: SAP S/4HANA

1909 - SPS 01 (02/2020) FP

Front-End Server 2805572 Release & Information Note: SAP Fiori for
SAP S/4HANA 1909 - SPS 01 (02/2020) FP

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appID=F3567.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) EAM_ORDER_ACTUALCOST_MONITOR (01)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application EAM_ACOST_MONS1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

This is custom documentation. For more information, please visit the SAP Help Portal 88
 7/16/2023

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

EAM_ORDER_ACTUALCOST_MONITOR (01) You can use the example business catalog Use an existing role or create a new one.
EAM-Order (SAP_EAM_BC_ORD) or your
custom catalog to create the back-end
PFCG role.

Con guration Tasks

In this app, cost element hierarchies are used to determine a Spend Category for the cost elements. To be able to nd cost
element hierarchies in the input help of the initial screen, you must perform the following con guration task in the back-end
system:

1. Create a cost element hierarchy in transactions KAH1 and KAH2. When you insert a cost element into the hierarchy, the
cost element group which is the direct successor of that cost element will be considered as the Spend Category in the
app. However, the tables and charts of this app also include costs associated to cost elements that are not inserted in
the respective cost element hierarchy. Since the system cannot determine a Spend Category for these costs, they are
not grouped by the spend category in the table view.

2. Replicate the cost element hierarchy into a runtime repository which acts like a cache.

a. Ensure that cost element hierarchies are enabled for replication in Customizing for Financial Accounting under
Financial Accounting Global Settings (New) Tools Work ow Set Report Relevancy for Hierarchies . On the
selection screen, enter set class 0102 and then choose the cost element groups which you want to enable for
replication.

b. Con gure the replication process in the Replicate Runtime Hierarchy app or with the Manually Replicate Runtime
Hierarchy (New) report (transaction HRRP_REP).

Manage Teams and Responsibilities

With this app, you can manage teams or team members associated with certain functions. You can identify which function can
be performed by which member. The teams and team members can be mapped as responsible for an activity type, for example,
in a process step of a work ow scenario. As a key user, you can access this app via the Manage Teams and Responsibilities -
Asset Management tile to manage teams and responsibilities for the cost approval of maintenance orders. As a maintenance
supervisor, you can access this app via the via the Manage Teams and Responsibilities for Work Centers tile to manage work
center teams for resource scheduling.

Using Teams in Work ow Scenarios

In Asset Management, teams and responsibilities can be used in work ow scenarios. There are ve prede ned functions to
model cost approval authority in a company:

This is custom documentation. For more information, please visit the SAP Help Portal 89
 7/16/2023
Cost Approval Level 1

Cost Approval Level 2

Cost Approval Level 3

Cost Approval Level 4

Cost Approval Level 5

You can use either teams or functions in agent determination of the work ow.

Using Functions in a Work ow

You can see the available functions when you create a work ow step and select Assignment By Role in the Recipients
section. When a maintenance order is submitted for approval, the system determines the approvers based on the function
con gured in the work ow rule. For example, when you set up a team with several team members who have different cost
approval functions, the system will determine the team members who are eligible to approve based on the function that is
de ned in the work ow rule.

Using Teams in a Work ow

You can see the teams that you have con gured when you create a work ow step and select Assignment By Team in the
Recipients section. When a maintenance order is submitted for approval, the system determines the approvers based on the
team con gured in the work ow rule. For example, when you set up a team with several team members who have different cost
approval functions, the system will determine the team and send the order for approval to the team members irrespective of
their functions.

Creating Teams for Maintenance Work Centers

You can also set up teams for work centers. Maintenance planners who use the resource scheduling apps can then search for
people in speci c work centers when assigning a person responsible to maintenance order operations. For more information,
see Setting Up Teams for Work Centers. This option is only relevant if you have enhanced the core functions of SAP S/4HANA
with an additional license for Resource Scheduling.

Key Features
This app allows you to do the following:

Create, edit, and delete teams

Copy an existing team and its change attributes

Add a member to an existing team

Delete a member from an existing team

Add a function to an existing team member

Delete a function from an existing team member

Maintain values for responsibility de nitions of teams

View teams in hierarchies

Manage subteams in a hierarchy

This is custom documentation. For more information, please visit the SAP Help Portal 90
 7/16/2023
You can make teams and team members responsible for a particular activity or scenario in a work ow. For more information,
see Manage Work ows for Maintenance Orders.

For more information about teams and responsibilities, see Manage Teams and Responsibilities.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
Manage Teams and Responsibilities
Manage Work ows for Maintenance Orders
Setting Up Teams for Work Centers

App Implementation: Manage Teams and Responsibilities

Prerequisites
This app allows you to de ne the responsibility of teams and team members for speci c tasks. Before implementing the app, we
strongly recommend that the scope items 4HH (Reactive Maintenance ) and 4HI (Proactive Maintenance ) are active in your
system, or you have con gured the phase model in Customizing the same way as it is delivered for these scope items. In this
app you de ne the responsibility of teams and team members for speci c tasks.

Tile Type for Launching App

The Manage Teams and Responsibilities app is launched using an app launcher tile:

As a key user, you can access this app via the Manage Teams and Responsibilities - Asset Management tile.

As a maintenance supervisor, you can access this app via the via the Manage Teams and Responsibilities for Work
Centers - Asset Management tile.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks

This is custom documentation. For more information, please visit the SAP Help Portal 91
 7/16/2023
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F4988.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) CA_RSM_TEAM_SRV (0001)

CA_RSM_TEAM_ACTION_SRV (0001)

C_RESPYMGMTTEAMHIERARCHY_CDS (0001)

APS_CHANGE_DOCUMENTS_SRV (0001)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application RSM_TEAM_MANS1

/sap/bc/ui5_ui5/sap/rsm_team_mans1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

This is custom documentation. For more information, please visit the SAP Help Portal 92
 7/16/2023
On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

CA_RSM_TEAM_SRV (0001) You can use the example business catalog Assign the existing role
SAP_EAM_BC_CONFIG or your custom SAP_BR_BPC_EXPERT or create a new
catalog to create the back-end PFCG role. one.

Con guration Tasks

If the scope items 4HH and 4HI are active, SAP delivers pre-con gured functions, a function pro le, a team category and team
types. You do not need to perform the following con guration tasks in the back-end system. However, you can check whether
the con guration meets your business requirements.

Create Functions

Functions are assigned to team members so that they can perform various tasks. With the scope items 4HH and 4HI,
SAP delivers the following pre-de ned functions:

Functions that represent ve levels of approval for maintenance orders:

MAINTAP_L1 (Cost Approval Level 1)

MAINTAP_L2 (Cost Approval Level 2)

MAINTAP_L3 (Cost Approval Level 3)

MAINTAP_L4 (Cost Approval Level 4)

MAINTAP_L5 (Cost Approval Level 5)

Functions that represent roles in work center teams:

SMNT_INT (Internal)

SMNT_EXT (External)

SMNT_LEAD (Lead)

The functions are created in Customizing for Cross-Application Components under General Application Functions
Responsibility Management Functions De ne Functions .

Create a Function Pro le

A function pro le groups functions that ful ll a similar task in the business process. With the scope items 4HH and 4HI,
SAP delivers the following function pro les:

The MAINT_APPR function pro le is pre-con gured for the approval process of maintenance orders and includes
the ve functions mentioned above.

The SMNT_TEAM function pro le is pre-con gured for the management of work center teams and includes the
three functions mentioned above.

The function pro les are created in Customizing for Cross-Application Components under General Application
Functions Responsibility Management Functions De ne Function Pro les .

This is custom documentation. For more information, please visit the SAP Help Portal 93
 7/16/2023
Assign the Function Pro le to the Team Category

A team category describes the functions and responsibilies of a team for a speci c business process. With the scope
items 4HH and 4HI, SAP delivers the following team categories:

Team category MAINT_P_E to which the function pro le MAINT_APPR is already assigned

Team category MAINT_TEAM to which the function pro le SMNT_TEAM is already assigned

The function pro les are assigned to the standard team categories in Customizing for Cross-Application Components
under General Application Functions Responsibility Management Teams and Responsibilities SAP Delivered Team
Categories Assign Function Pro les to Standard Team Category .

De ne Team Types and Assign them to the Team Category

A team type is a classi cation that represents a subprocess of a business process. The team type is associated with a
team category and inherits its functions and responsibility de nitions. With the scope items 4HH and 4HI, SAP delivers
the following team types:

Team type MAINT_P_E, which is already assigned to the team category MAINT_P_E

Team type SMNT_TEAM, which is already assigned to the team category MAINT_TEAM

The team types are created and assigned to the standard team category in Customizing for Cross-Application
Components under General Application Functions Responsibility Management Teams and Responsibilities SAP
Delivered Team Categories Create Team Types .

Related Information
Manage Teams and Responsibilities

Manage Work ows for Maintenance Orders

With this app, you can manage the approval work ow for maintenance orders. As a con guration expert, you can con gure
work ows to optimize the approval process for maintenance orders. If a work ow with one or more steps is activated and the
con gured start conditions are ful lled, the approval process is initiated.

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.

Key Features
This app allows you to do the following:

De ne start conditions for a work ow such as planning plant and order type. Work ow will be selected only if the start
conditions are met. You can set up the start conditions based on various attributes of the work order. It is advisable to
de ne the start conditions as generic as possible. In the step sequences, you can provide speci c conditions.

De ne the sequence in which the start conditions of existing work ows are checked.

If you have de ned several work ows, the start conditions are checked in the sequence you have de ned. As soon as the
start conditions for a work ow are met, this work ow is used. This ensures that only one work ow in the list of your
de ned work ows is started, even if several work ows have matching start conditions.

This is custom documentation. For more information, please visit the SAP Help Portal 94
 7/16/2023
Navigate into the details of a work ow

Activate or deactivate a work ow

Copy an existing work ow and modify it according to your requirements, or add a new work ow. You can con gure the
work ow as follows:

De ne properties such as a description and a validity period. You can de ne the criteria that needs to be ful lled for the
work ow to start. You can choose a planning plant and order type. For example, preconditions can be 'order type is
ʻReactive Maintenance (YA01)’ and planning plant is 1010'.

Add one or more step sequences. For each step sequence, you can de ne recipients, timelines, and preconditions. You
can de ne the sequence of the steps and delete unnecessary steps.

 Note
If you use either the role Manager of Last Approver or Manager of Work ow Initiator, the managers must be
maintained in the system. If you use the role “Person Responsible for Cost Center in Settlement Rule(s)”, then the
person responsible must be maintained in the cost center. If you use the role “Person Responsible for WBS Elements
(s) in Settlement Rule(s)”, then a nancial controller must be maintained for the project of the WBS element. This
ensures that the work ow can nd the correct approver.

De ne the validity of a work ow.

Activate scenarios. If you opt to automatically release the maintenance order, the work ow is activated by default.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
App Implementation: Manage Work ows for Maintenance Orders
Manage Teams and Responsibilities
Maintenance Process Phases

App Implementation: Manage Work ows for Maintenance Orders

Prerequisites
This app allows you to manage approval work ows for maintenance orders that are processed according to phases. Before
implementing the app, we strongly recommend that the scope items 4HH (Reactive Maintenance ) and 4HI (Proactive
Maintenance ) are active in your system, or you have con gured the phase model in Customizing the same way as it is delivered
for these scope items. Make sure that the phase model is activated for the order types for which you want to use approval
work ows.

Tile Type for Launching App

The Manage Work ows for Maintenance Orders app is launched using an app launcher tile.

This is custom documentation. For more information, please visit the SAP Help Portal 95
 7/16/2023

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F4989.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) SWF_FLEX_DEF_SRV (0001)

S_EAM_WF_C_VH_CDS (0001)

EAM_MAINTORDER_WORKFLOW_SRV (0001)

For more information about activating OData services, see Activating OData Services.

Front-End Server: Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application NW_APS_BPM_SWE

/sap/bc/ui5_ui5/sap/nw_aps_bpm_swe

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

This is custom documentation. For more information, please visit the SAP Help Portal 96
 7/16/2023

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

SWF_FLEX_DEF_SRV (0001) You can use the example business catalog Assign the existing role
SAP_EAM_BC_CONFIG or your custom SAP_BR_BPC_EXPERT or create a new
catalog to create the back-end PFCG role. one.

Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:

Use the Manage Teams and Responsibilities app to con gure teams for the approval of maintenance orders. For more
information and prerequisites, see App Implementation: Manage Teams and Responsibilities.

SAP delivers the pre-de ned work ow scenario WS02000019 for approving the maintenance orders that are processed
by phases. You can check whether the work ow scenario is active in Customizing under ABAP Platform Application
Server Business Management SAP Business Work ow Flexible Work ow Scenario Activation .

To ensure that the approval work ows you de ne in this app can be executed, you must rst indicate for which
combinations of order type and maintenance planning plant an approval step is required before maintenance orders can
be released. You do this in Customizing for Plant Maintenance and Customer Service under Maintenance and Service
Processing Maintenance and Service Orders Functions and Settings for Order Types Order Types and Investment
Management De ne Approval Settings for Maintenance Orders .

Related Information
Manage Work ows for Maintenance Orders
Manage Teams and Responsibilities
Maintenance Process Phases

My Inbox
With this app, you can approve or reject maintenance orders.

This is custom documentation. For more information, please visit the SAP Help Portal 97
 7/16/2023

Key Features
This app allows you to do the following:

Approve a maintenance order.

Reject a maintenance order.

When an order is approved or rejected, the status for that order is updated in the maintenance order. For more
information, see Manage Maintenance Noti cations and Orders.

 Note
In addition to maintenance orders, you may see other documents, like purchase orders.

Maintenance Order Costs

With this app you can monitor and evaluate estimated costs, baseline costs, planned costs and actual costs resulting from
current maintenance orders. It enables you, for example, to compare planned costs or baseline costs with actual costs caused
by maintenance orders of a speci c order type during a selected time period.

Filters allow you to analyze estimated costs, baseline costs, planned costs and actual costs in a speci c time frame from
different perspectives such as the order type, the responsible cost center, the main work center or the maintenance activity
type. A condensed view enables you to identify and compare relevant areas within data sets using data visualization and
business intelligence. On the other hand, you can also navigate directly to signi cant single maintenance orders. All this can be
done seamlessly within one page that combines transactional and analytical data using chart and table visualization.

Key Features
This app provides the following key features:

In the header area that can be collapsed or expanded, lter the result set, which feeds the main content area.

Select the lters to be displayed and combine multiple lters in different ways. You must provide lter values for the
Relative Date Function, the G/L Account Hierarchy, the Ledger and the Company Code.

Gain a condensed overview of the maintenance order costs in colored charts in the visual lter bar and thereby spot
relevant data more quickly.

In the content area, switch between the chart-only view, the table-only view and the hybrid view that combines both,
chart and table view.

In the chart view, analyze aggregated estimated costs, baseline costs, planned costs and actual costs from different
perspectives and use the drilldown functionality. Estimated costs, baseline costs, planned costs and actual costs are
colored differently to provide you with a rapid overview.

In the chart view, easily change chart types, customize the chart settings and use the drilldown option to change the
chart grouping dimension.

In the table view, access the costs summed up for speci c order types and spend categories but also act on individual
maintenance orders by navigating directly to them.

In the table view, decide which dimensions are to be displayed in the table and choose dimensions to group and sort
maintenance order cost data accordingly.

In the hybrid view, interact with both the chart and the table. Selecting a dimension within a chart area automatically
lters all relevant information in the table area.

This is custom documentation. For more information, please visit the SAP Help Portal 98
 7/16/2023

 Note
The system shows the costs always based on the maintenance location, plant section and maintenance plant on order
header level. In maintenance orders with operations that have different technical objects with different locations, plant
sections and maintenance plants assigned, the system nevertheless sums up the costs associated with any of the
operations and shows them as if they were incurred within the location, the plant section and the maintenance plant entered
in the order header. Keep this in mind when you evaluate the analytical results.

In addition, the app supports the following technical features and options:

If the long material number has been activated in your back-end system, it is automatically displayed in the Material eld
in this SAP Fiori app.

This app also runs in standalone mode.

Supported Device Types

Desktop

Tablet

Smartphone

 Note
Using the app on mobile devices with small displays is not recommended due to usability issues. Small displays require
condensing the complex data and relevant information to such a degree that it might be difficult to work with the app
efficiently.

Before you implement this app, you need to perform several con guration tasks in the back-end system. For more
information, see App Implementation: Maintenance Order Costs .

App Implementation: Maintenance Order Costs

Prerequisites
In this app, cost element hierarchies are used to determine a Spend Category for the cost elements. Before implementing the
app, you therefore must ensure that cost element hierarchies are created and replicated as described in the Con guration
Tasks below.

System Landscape Requirements

For information about the system requirements, see SAP Fiori Overview.

Tile Type for Launching App

The Maintenance Order Costs app is launched using an app launcher tile.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

This is custom documentation. For more information, please visit the SAP Help Portal 99
 7/16/2023

Back-End / Front-End Server SAP Note Description

Back-End Server 3015539 SAP S/4HANA 2021: Release Information

Note

Front-End Server 3067553 SAP FIORI FOR SAP S/4HANA 2021:

Release Information Note

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appID=F4603.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) UI_MAINTORD_PLNACTCOST (0001)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application EAM_PACST_MONS1

/sap/bc/ui5_ui5/eam_pacst_mons1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution

This is custom documentation. For more information, please visit the SAP Help Portal 100
 7/16/2023
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

UI_MAINTORD_PLNACTCOST (0001) You can use the example business catalogs Assign the existing roles
SAP_EAM_BC_MP_ORD_DSP and SAP_BR_MAINTENANCE_PLANNER or
SAP_EAM_BC_ORD_DSP or your custom SAP_BR_MAINT_SUPERVISOR or create a
catalog to create the back-end PFCG role. new one.

Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:

De ne the Plan Categories for Estimated Costs, Planned Costs and Baseline Costs

1. De ne the plan categories for estimated costs, planned costs and baseline costs in Customizing of Controlling under
General Controlling Planning Maintain Category for Planning . De ne the three plan categories (e.g. PMORDER01,
PMORDER02, PMORDER03) for the application type Maintenance Order and with No speci c usage. Do not allow
import, copy or delete.

2. De ne which of the three plan categories that you de ned in the last step is valid for estimated costs, which one for
planned costs and which one for baseline costs. You can do this in Customizing for Controlling under General
Controlling Planning Application-Speci c Categories Maintain Categories for Maintenance Orders . Note that
you cannot change this assignment retrospectively.

Create and Replicate the Cost Element Hierarchy

In this app, cost element hierarchies are used to determine a Spend Category for the cost elements. To be able to nd cost
element hierarchies in the input help of the initial screen, you must perform the following con guration task in the back-end
system:

1. Create a cost element hierarchy in transactions KAH1 and KAH2 or in the Manage Global Hierarchies app. When you
insert a cost element into the hierarchy, the cost element group, which is the direct successor of that cost element, will
be considered as the Spend Category in the app. However, the tables and charts of this app also include costs
associated to cost elements that are not inserted in the respective cost element hierarchy. Since the system cannot
determine a Spend Category for these costs, they are not grouped by the spend category in the table view.

2. Replicate the cost element hierarchy into a runtime repository which acts like a cache.

a. Ensure that cost element hierarchies are enabled for replication in Customizing for Financial Accounting under
Financial Accounting Global Settings (New) Tools Work ow Set Report Relevancy for Hierarchies . On the
selection screen, enter set class 0102 and then choose the cost element groups which you want to enable for
replication.

b. Con gure the replication process in the Replicate Runtime Hierarchy app or with the Manually Replicate Runtime
Hierarchy (New) report (transaction HRRP_REP).
This is custom documentation. For more information, please visit the SAP Help Portal 101
 7/16/2023
Determine Cost Element Hierarchy, Company Code and Ledger

Since cost element hierarchies are used to determine a spend category for the cost elements, you must enter the relevant cost
element hierarchy, the company code and the ledger in the Default Values of your Settings on the Fiori Launchpad. You can
enter the relevant values in the COA/GL Account Hier. eld, in the Company Code eld and in the Ledger eld of the Financial
Accounting area. You can also provide this mandatory data each time you open the app.

Custom Date Function

In the Maintenance Order Costs app, you must select a relative date function for the cost analysis. Relative date functions can
specify a single date (for example, the rst day of the previous month) or a date range (for example, the entire previous
quarter). SAP provides pre-de ned date functions that are displayed in the input help of the Relative Date Function lter eld.
You can only select a relative date function for the cost analysis if you have activated the OData Service DATEFUNCTION.

However, the analytics specialist can create additional custom date functions in the Manage Date Functions app (for more
information, see Manage Date Functions). Any custom date functions that the analytics specialist creates becomes available for
the relative date selection in any app with the corresponding lter eld.

Ensure that Cost Data is Stored in ACDOCP table

Make sure that maintenance planners and supervisors who process the maintenance orders have the authorization to write
planned costs into the table for Financial Plan Data Line Items (ACDOCP). You therefore need to provide speci c values or full
authorization in the elds Plan Category (Category_P ) and Ledger (GLRLDNR) of the authorization object K_ACDOCP_P and
assign this authorization object to the relevant users.

Request Maintenance

Use
You can use this app to easily request that maintenance work or repairs be done on a technical object. While creating a
maintenance request, the app helps you provide all the relevant information required to solve the problem quickly. You enter
important information such as the technical object, the location where the problem occurred, the effect on safety or
environmental compliance, as well as a detailed description of the problem. Questionnaires ensure that you describe the
problem without leaving out important information. By launching the second tile provided for this app, you open a noti cation
list for monitoring all the different maintenance requests that have been submitted. The list provides you with a quick overview
so you can easily track the status of the noti cations. You can use the search function and lters to determine which
noti cations are displayed.

This app is available for the Employee (Maintenance) role.

Key Features
Two tiles are provided for this app.

By launching the Request Maintenance tile, you can do the following:

Create a maintenance request with all the relevant information required.

Find the affected technical object using the type ahead search.

Use a questionnaire for the long text to provide the most important information about the problem.

Attach pictures or descriptions of the damage, which are automatically saved as DMS documents.

Stay informed about the progress of the repair work by selecting the Notify me checkbox.

This is custom documentation. For more information, please visit the SAP Help Portal 102
 7/16/2023
By launching the Monitor Maintenance Requests tile, you can do the following:

Get a quick overview of maintenance requests and their current status by viewing a list of noti cations.

Narrow down the scope of the noti cation list by using lters. You can use the default lters or add additional ones.

View the date monitor symbols to quickly detect time issues and monitor the progress of the noti cations.

Get all relevant contact information about the person who reported the malfunction and the person who created the
noti cation.

Personalize the table by choosing which table columns are shown and how table entries are sorted.

Navigate to the details of a noti cation and edit it if necessary.

Tailor the app to your needs and save the combination of lters and table personalization as a variant.

Save your personalized variants as tiles on your home page from which you can access the noti cation list directly.

Key Features Available on Mobile Devices

If you run the app on a mobile device (smartphone or tablet), the following additional features are available:

Use a barcode scanner to enter the ID of the technical object that has to be repaired. Barcode scanning is a feature
enabled by the SAP Fiori Client or a customer-generated instance thereof.

Use the camera symbol to take a picture of the damage that is automatically attached to the noti cation. This function
is only available if it is technically possible to take pictures with the mobile device and browser you are currently using.

 Note
Using the app on mobile devices with small displays is not recommended due to usability issues. Small displays require
condensing the complex data and relevant information to such a degree that it might be difficult to work with the app
efficiently.

Component for Customer Incidents

PM-FIO

More Information
App Implementation: Request Maintenance

App Extensibility: Request Maintenance

App Implementation: Request Maintenance

System Landscape Requirements
For information about the system requirements, see SAP Fiori Overview.

 Note
The app offers the possibility to upload les. For security reasons, we strongly recommend that you install an appropriate
virus scanner in your SAP Fiori system landscape and de ne sufficiently restrictive scan pro les to prevent the upload of

This is custom documentation. For more information, please visit the SAP Help Portal 103
 7/16/2023
malicious content.

For more information on virus scanning and scan pro les for apps, see section Virus Scanning in the SAP S/4HANA Security
Guide .

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-end and front-end servers 2241569 Release Information Note for the SAP Fiori
App "Request Maintenance"

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F1511.

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number)

EAM_NTF_CREATE (01)

CV_ATTACHMENT_SRV (01)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAP UI5 Application

Component Technical Name

SAP UI5 Application EAM_NTF_CRES1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server: Activate ICF Service

Component Technical Name

ICF Service
EAM_NTF_REUSES1

PLM_ATH_CRES1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

This is custom documentation. For more information, please visit the SAP Help Portal 104
 7/16/2023
The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to Users

You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

EAM_NTF_CREATE (01) Does not apply Assign the existing role

SAP_BR_EMPLOYEE_MAINTENANCE or
create a new one.

Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:

If you want the Notify Me checkbox to be displayed, you have to make the relevant Customizing settings for Plant
Maintenance and Customer Service under Maintenance and Service Processing Maintenance and Service
Noti cations Noti cation Creation Partners De ne Partner Determination Procedure and Partner Function .

Assign the function IT (Interested Party) to a partner determination procedure that allows the noti cation of
partners.

Assign this partner determination procedure to the relevant noti cation types.

To con gure the upload of attachments, specify a default document type in view /PLMI/V_DIR_ATT, and activate the
default storage category in view CV_V_STOR_CAT.

If you want to allow other noti cation types in addition to M1 and M2, you have to enhance the OData service.

App Extensibility: Request Maintenance

This is custom documentation. For more information, please visit the SAP Help Portal 105
 7/16/2023

Use
You can extend the Request Maintenance app according to your business needs for different aspects. For this purpose, the
following extensibility options are available:

Additional UI elements while creating or editing a noti cation

You can add additional UI elements at the beginning of the form.

You can add additional UI elements below the header and above the form.

You can add additional UI elements at the end of the form.

You can replace the default implementation for selecting noti cation types.

You can display additional UI elements below the Location eld.

Replace default search option (barcode) for nding technical objects

You can replace the default search option (barcode) with customer-speci c methods for nding technical objects while
creating a noti cation. Note that you must also implement the extension hook extHookAdditionalSearchOption to
control visibility of these methods.

Provide users with customer-speci c questionnaires when they report a problem

You can replace the questionnaire provided by clicking on the Use Template link above the Long Text eld.

Additional UI elements while displaying a noti cation

You can add additional UI elements at the beginning of the form.

You can add additional UI elements below the header and above the tabbed area.

You can add additional UI elements below the tabbed area.

You can add additional UI elements at the end of the form.

You can add additional tab pages to the IconTabBar.

You can display additional UI elements below the Location eld.

Additional UI elements in the noti cation list

You can add additional UI elements between the lter bar and the worklist.

Additional UI elements in the technical object quickview

You can add additional UI elements after the object header.

You can add additional UI elements between the header and details sections.

You can add additional UI elements below the details section.

Further Extensibility Entities

Business Add-Ins (BAdIs)

The following BAdIs are available for extensibility purposes:

BAdI: Extensibility of Templates in "Request Maintenance“ App (BADI_EAM_LTXT_TML_NTF)

You can use this BAdI to provide employees with customer-speci c questionnaires when they report a problem using the
Request Maintenance app. This ensures that they enter all the relevant information required so that the problem can be

This is custom documentation. For more information, please visit the SAP Help Portal 106
 7/16/2023
solved quickly.

Extension Points

The following extension points are available:

View Extension Point Use

MaintainNotification.view.xml extBeginForm Allows you to add additional UI

elements at the beginning of the
form used for creating or editing a
noti cation.

S2.view.xml extAfterObjectHeader Allows you to add additional UI

elements below the header and
above the form when editing a
noti cation.

MaintainNotification.view.xml extEndForm Allows you to add additional UI

elements at the end of the form used
for creating or editing a noti cation.

MaintainNotification.view.xml extNotificationType Replaces the default implementation

for selecting noti cation types.

MaintainNotification.view.xml extAdditionalLocationData Allows you to display additional UI

elements below the Location eld
while creating or editing a
noti cation.

Search.fragment.xml extButtonSearchOptions Replaces the default search option

(barcode) with customer-speci c
methods for nding technical
objects.

Note that you must also implement

the extension hook
extHookAdditionalSearchOption

S3.view.xml S3.view.extBeginForm Allows you to add additional UI

elements at the beginning of the
form used for displaying a
noti cation.

S3.view.xml S3.view.extAfterObjectHeader Allows you to add additional UI

elements below the header and
above the tabbed area when
displaying a noti cation.

S3.view.xml extAfterIconTabBar Allows you to add additional UI

elements below the tabbed area
when displaying a noti cation.

S3.view.xml extEndForm Allows you to add additional UI

elements at the end of the form used
for displaying a noti cation.

S3.view.xml extInIconTabBar Adds additional tabs to the

IconTabBar when displaying a
noti cation.

This is custom documentation. For more information, please visit the SAP Help Portal 107
 7/16/2023

View Extension Point Use

S3.view.xml extAdditionalLocationDataDisplay Allows you to display additional UI

elements below the Location eld
while displaying a noti cation.

S0.view.xml extBeginPage Allows you to add additional UI

elements below the lter bar and
above the noti cation list.

TechnicalObjectOverview.fragment.xml extAfterObjectHeader Allows you to add additional UI

elements in the technical object
quickview after Object Header.

TechnicalObjectOverview.fragment.xml extBeginForm Allows you to add additional UI

elements in the technical object
quickview between the header and
details sections.

TechnicalObjectOverview.fragment.xml extEndForm Allows you to add additional UI

elements in the technical object
quickview below the details section.

If there are additional elds available in the OData service, you can display these elds on the UI. For more information about
extension points, see Extend SAP Fiori Apps.

UI Controller Hooks

To plug in and execute custom code, the following hooks are available in the controller code:

Controller Hook

App.controller.js {boolean} i2d.eam.pmnoti cation.create.controller.App~extHookAttachmentSwitch()

App.controller.js {sap.ui.model.Filter}
i2d.eam.pmnoti cation.create.controller.App~extHookFilterOpenNoti cations({sap.ui.mod
[aFilters], {string} “open”)

MaintainNotification.controller.js {boolean}
i2d.eam.pmnoti cation.create.controller.MaintainNoti cation~extHookAdditionalSearchO

If there are additional UI controller hooks available in the controller code, you can extend the UI controller code. For more
information about UI controller hooks, see Extend SAP Fiori Apps.

Display of UI Controls

As an example, the following UI controls can be hidden from the app UI:

This is custom documentation. For more information, please visit the SAP Help Portal 108
 7/16/2023

View Control ID Use

App.view.xml fioriContent

S0.view.xml pmNotifSmartTableFilterWorklist Smart Filter

S0.view.xml pmNotifSmartFilterBarControlConfiguration Smart Filter

- Control
Con guratio

S0.view.xml pmNotifSmartTableWorklist Smart Table

display
noti cations

S0.view.xml pmNotifButtonAdd Button for

adding
noti cation

S0.view.xml pmNotifColumnDateMonitor Column Dat

Monitor

S0.view.xml pmNotifButtonShareTile Button for S

Tile

S1.view.xml pmNotifViewCreateNotification View Create

Noti cation

S1.view.xml pmNotifButtonCancel Cancel Butt

S1.view.xml pmNotifButtonMyNotifications Noti cation

Button

S1.view.xml pmNotifButtonShareTile Button for S

Tile

S2.view.xml pmNotifViewEditNotification View Edit

Noti cation

S3.view.xml pmNotifIconTabFilterGeneralData IconTab for

General Dat
Display

S3.view.xml pmNotifInputTechnicalObject Input Field f

Technical Ob

S3.view.xml pmNotifIconTabFilterNotes IconTab for

Comments
Display

S3.view.xml pmNotifTimelineTimelineNotes Notes Displ

in a Timeline
Display

S3.view.xml pmNotifIconTabFilterAttachments IconTab for

Attachment
Display

S3.view.xml pmNotifContainerAttachments Container fo

Attachments

S3.view.xml pmNotifIconTabFilterContacts IconTab for

Contacts in
Display

This is custom documentation. For more information, please visit the SAP Help Portal 109
 7/16/2023

View Control ID Use

S3.view.xml pmNotifTableContactsTable Table of

Contacts in
Display

Attachments.fragment.xml pmNotifContainerAttachments Container fo

Attachments

CurrentNotifications.fragment.xml pmNotifListNotifications List of Curre

Noti cations

CurrentNotifications.fragment.xml pmNotifObjectAttributeReporter Object Attrib

Reporter in
Noti cation

CurrentNotifications.fragment.xml pmNotifObjectAttributeShortText Object Attrib

Short text in
Noti cation

CurrentNotifications.fragment.xml pmNotifObjectAttributeTimestamp Object Attrib

Timestamp
Noti cation

GeoMap.fragment.xml pmNotifViewGeoMapView GeoMap to b

Displayed in
Popover/Dia

NotificationHeader.fragment.xml pmNotifObjectAttributeReporter Object Attrib

Reporter in
Noti cation
Header

NotificationHeader.fragment.xml pmNotifObjectAttributeTimestamp Object Attrib

Timestamp
Noti cation
Header

Search.fragment.xml pmNotifButtonBarcodeSearch Button to Se

via Barcode

TechnicalObjectOverview.fragment.xml pmNotifLabelTechnicalObjectDescription Technical Ob

Description

TechnicalObjectOverview.fragment.xml pmNotifLabelTechnicalObjectType Technical Ob

Type

TechnicalObjectOverview.fragment.xml pmNotifLabelPlantSection Plant Sectio

TechnicalObjectOverview.fragment.xml pmNotifLabelModelNumber Model Numb

TechnicalObjectOverview.fragment.xml pmNotifLabelManufacturer Manufacture

TechnicalObjectOverview.fragment.xml pmNotifLabelLocation Location

TechnicalObjectOverview.fragment.xml pmNotifLabelRoom Room

TechnicalObjectOverview.fragment.xml pmNotifLabelAdditionalDocuments Additional

Documents
(Attachment

TechnicalObjectOverview.fragment.xml pmNotifViewTechnicalObjectOverviewAttachmentsSimple SubView for

Attachments
Technical Ob
Overview

This is custom documentation. For more information, please visit the SAP Help Portal 110
 7/16/2023

View Control ID Use

GeoMap.view.xml pmNotifHorizontalLayoutGeoMap Holds the

GeoMap Co

MaintainNotification.view.xml pmNotifLabelTechnicalObject

MaintainNotification.view.xml pmNotifInputTechnicalObject Input eld fo

the Technica
Object in
Create/Edit
Mode

MaintainNotification.view.xml pmNotifLabelNotificationType

MaintainNotification.view.xml pmNotifComboBoxNotificationType ComboBox f

Noti cation
Types

MaintainNotification.view.xml pmNotifLabelTitle Shorttext/T

MaintainNotification.view.xml pmNotifInputTitle Input Field f

Short Text/T
in Create/Ed
Mode

MaintainNotification.view.xml pmNotifLabelLongText TextAreas:

(History and
Update) for
Text/Descri
in Create Mo

MaintainNotification.view.xml pmNotifLongTextCreate TextAreas fo

Long
Text/Descri
in Create Mo

MaintainNotification.view.xml pmNotifLongTextEdit TextAreas:

(History and
Update) for
Text/Descri
in Edit Mode

MaintainNotification.view.xml pmNotifLabelLocation Location

MaintainNotification.view.xml pmNotifInputLocation

MaintainNotification.view.xml pmNotifLabelEffect Effect

MaintainNotification.view.xml pmNotifSelectEffect Effect eld

MaintainNotification.view.xml pmNotifLabelDateTime Date/Time

MaintainNotification.view.xml pmNotifInputDateTime

MaintainNotification.view.xml pmNotifLabelReportedBy Reported by

MaintainNotification.view.xml pmNotifInputReporter Input Field f

the Reporter
Create/Edit
Mode

MaintainNotification.view.xml pmNotifLabelNotifyMe Notify me la

MaintainNotification.view.xml pmNotifCheckBoxNotifyMe Notify me

This is custom documentation. For more information, please visit the SAP Help Portal 111
 7/16/2023

View Control ID Use

MaintainNotification.view.xml pmNotifContainerAttachments Attachments

Fragment in
Edit/Create
Mode

For more information about hiding UI controls, see Extend SAP Fiori Apps.

More Information
For a general description of the extensibility options and procedures of SAP Fiori apps, see Extend SAP Fiori Apps.

Business Scenario
You can transfer the custom eld data from a maintenance noti cation to a maintenance order by enabling the business
scenario EAM_NTF_TO_ORD.

You can transfer the custom eld data from an equipment to a maintenance noti cation by enabling the business
scenario EAM_EQUI_TO_NTF.

You can transfer the custom eld data from a functional location to a maintenance noti cation by enabling the business
scenario EAM_FL_TO_NTF.

Report and Repair Malfunction

Use
You can use this app to easily report that a technical object has a malfunction, plan the required repair work, as well as
document and con rm the maintenance work when it's done.

While creating a malfunction report, the app helps you provide all the relevant information required to solve the problem quickly.
You enter important information such as the technical object, the location where the problem occurred, the effect on safety or
environmental compliance, as well as a detailed description of the problem. Furthermore, the app supports you when planning
your repair work. This includes gathering information about the affected technical object and any repair work that has been
recently carried out, searching for the required spare parts and checking if they're in stock, as well as assigning the work
centers involved. Once you've nished the repair work, you can provide information about the malfunction and the job, con rm
your job, and close the malfunction report.

You can also get a quick overview of all the malfunction reports or of all work items assigned to you and their current status. You
have the possibility to personalize the list of reports, view the status of the jobs, and navigate to the job details. There you can
start working on the jobs assigned to you and con rm them.

This app is available for the Maintenance Technician role.

Key Features
Three tiles are provided for this app: The Report Malfunction tile for creating malfunction reports, the Manage Malfunction
Reports tile that provides a list of malfunction reports that have already been created, and the Repair Malfunctions - My Job
List tile that provides a list of all work items assigned to you or to your team.

By launching the tiles, you can do the following:

This is custom documentation. For more information, please visit the SAP Help Portal 112
 7/16/2023
Create a malfunction report with all the relevant information required:

Find the affected technical object using the type-ahead search

View the hierarchical structure of a technical object and identify where a piece of equipment is installed

View details about the technical object by navigating to related apps

View a list of all malfunction reports that have recently been created for the relevant technical object and navigate to
individual noti cations

Write a long text to describe the problem in detail

Attach pictures or descriptions of the damage

Attach a URL to provide further information about the technical object or the damage

Gather more information about the technical object and plan your repair work:

View further details on the technical object (Details)

Gain insight into recent repair work that has been carried out on the technical object (History)

Create different work items and assign the maintenance technicians responsible. The maintenance technicians can only
process the work items to which they are assigned.

Choose the required spare parts in the bill of material for the technical object or search it in a list with recently used
parts needed for repairs on this technical object. You can also use a generic search on all materials and add inventory-
managed components, such as components with item category L (Stock Item) or R (Variable-size item).

View if the quantity of spare parts you need are in stock in the relevant storage location or plant

Add the required spare parts to your malfunction report, which creates reservations for the stock materials

Add work items by entering the respective work center, person responsible, information about the work to be done, and
the estimated time effort

Release the malfunction report and start the repair work

Execute, document, and con rm the repair work:

View the overall status to see in which phase individual jobs are and track the progress of the entire malfunction report.

Start working and pause your work whenever needed. You can document why you had to pause your work by selecting a
reason such as Waiting for Parts or Waiting for Approval.

Con rm the time you have already been working on the job by creating partial con rmations. Whenever you pause your
work, the system proposes a value for the actual time effort.

Document that the work has been done when you have completely nished your work.

Con rm the time spent on the job and enter the nal con rmation of your work item.

Adjust the required quantity of the spare parts and the storage location, where needed.

Add malfunction details, such as the affected object parts, the appropriate damage code, the cause, and the activities
performed. You can determine one cause as the root cause.

Enter the malfunction duration and specify if the machine was broken down.

As the lead technician, who has been entered as processor for the entire malfunction report, complete and close the
malfunction report. If the malfunction report is completed before all jobs have been nally con rmed, the system sets
the nal con rmation indicator for all open jobs.

This is custom documentation. For more information, please visit the SAP Help Portal 113
 7/16/2023
Work together with different maintenance technicians on the same malfunction report

Assign a maintenance technician as the lead technician who is the processor of the entire malfunction report and
therefore is the only one who can release and close the malfunction report.

Create different work items and assign the maintenance technicians responsible. Multiple work items can be assigned to
a technician. The technicians can only perform actions that are relevant for their work item, such as start and pause
their work or set the status of their work item to Work is Done.

View a list of malfunction reports that have already been created by launching the Manage Malfunction Reports tile.

Get a quick overview of malfunction reports and their current status by viewing a list of malfunction reports.

View and change malfunction reports. You can also do this for malfunction reports that have not been created within the
app.

Narrow down the scope of the list by using lters. You can use the default lters or add additional ones.

Get all relevant contact information about the person who reported the malfunction and the person who is processing
the malfunction report.

Personalize the table by choosing which table columns are shown and how table entries are sorted.

Navigate to the details of a malfunction report and edit it if necessary.

Find the malfunction reports assigned to you, open the details of a report, and start or con rm your repair work.

Tailor the app to your needs and save the combination of lters and table personalization as a variant.

Save your personalized variants as tiles on your home page.

View a list of the work items assigned to you or your team by launching the Repair Malfunctions - my Job List tile.

Get a quick overview of all work items assigned to you or to your team. You can also display all the jobs of your work
center that have not yet been assigned to a technician.

Narrow down the scope of the list by using lters, such as the status or the priority of the work items.

Navigate to the details of the maintenance noti cation and edit it if necessary.

Navigate to the details of the jobs assigned to you, open the details of a job, and start or con rm your repair work.

Attach pictures, descriptions, or a URL to provide further information about the damage or your repair work.

Supported Device Types

Desktop

Tablet

Smartphone

Key Features Available on Mobile Devices

If you run the app on a mobile device (smartphone or tablet), the following additional features are available:

Use a barcode scanner to enter the ID of the technical object that has to be repaired or to add the ID of a required spare
part. Barcode scanning is a feature enabled by the SAP Fiori Client or a customer-generated instance thereof.

This is custom documentation. For more information, please visit the SAP Help Portal 114
 7/16/2023
Use the camera symbol to take a picture of the damage that is automatically attached to the noti cation. This function
is only available if it is technically possible to take pictures with the mobile device and browser you are currently using.

If you run the app on a mobile device (smartphone or tablet), the following constraints apply:

You cannot navigate to the master data of the technical object or view the technical object in the Asset Viewer.

If you use the app on a smartphone, you cannot view any hierarchical lists, such as the structure of the technical object
or the bill of material for the technical object.

 Note
Using the app on mobile devices with small displays is not recommended due to usability issues. Small displays require
condensing the complex data and relevant information to such a degree that it might be difficult to work with the app
efficiently.

Related Information
App Implementation: Report and Repair Malfunction

App Implementation: Report and Repair Malfunction

System Landscape Requirements

For information about the system requirements, see SAP Fiori Overview.

 Note
The app offers the possibility to upload les. For security reasons, we strongly recommend that you install an appropriate
virus scanner in your SAP Fiori system landscape and de ne sufficiently restrictive scan pro les to prevent the upload of
malicious content.

For more information on virus scanning and scan pro les for apps, see section Virus Scanning in the SAP S/4HANA Security
Guide .

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-end and front-end servers 2488413 Release Information Note: EAM Apps on
SAP S/4HANA 1709

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F2023.

This is custom documentation. For more information, please visit the SAP Help Portal 115
 7/16/2023

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number)

EAM_MALFUNCTION_MANAGE (01)

EAM_MALFUNCTION_MANAGE_ANNO_MDL (02)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAP UI5 Application

Component Technical Name

SAP UI5 Application EAM_MALF_MANS1

Path to ICF Node /sap/bc/ui5_ui5/sap/eam_malf_mans1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

This is custom documentation. For more information, please visit the SAP Help Portal 116
 7/16/2023

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

EAM_MALFUNCTION_MANAGE (01) Does not apply Assign the existing role

SAP_BR_MAINTENANCE_TECHNICIAN or
EAM_MALFUNCTION_MANAGE_ANNO_MDL
create a new one.
(02)

Con guration Tasks

To be able to implement the app, you must perform the following con guration tasks in the back-end system:

You have to activate the overall status pro le MAINTJOB in the Customizing for Plant Maintenance and Customer
Service under Maintenance and Service Processing Fiori Apps for Maintenance Processing General Settings
De ne Overall Status .

The system calculates an overall status for maintenance noti cations, maintenance orders and operations whenever a
maintenance noti cation or order is processed in the system. The overall status then is also calculated when
maintenance noti cations and orders are being processed using backend transactions or the Web Dynpro-based
applications.

You need to assign a default noti cation type to the planning plants in the Customizing for Plant Maintenance and
Customer Service under Maintenance and Service Processing Fiori Apps for Maintenance Processing General
Settings Assign Noti cation Types to Maintenance Planning Plants .

When a malfunction report is created via this Fiori app, the system determines the noti cation type from the planning
plant of the technical object.

You need to synchronize the business partners so that the lead maintenance technician can assign work items to
different maintenance technicians and choose the corresponding employee numbers from the input help. For more
information, you can refer to the Customizing under Personnel Management SAP S/4HANA for Human Resources
Synchronization of Business Partner for SAP HCM Employee Role . Furthermore, it is mandatory to provide a system
user name for every maintenance technician in their employee record under infotype 0105 (Communication).

Related Information
Report and Repair Malfunction

App Extensibility: Manage Malfunction Reports

As a key user, you can extend the Manage Malfunction Report app according to your business needs.

Features
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

EAMS_NTF Fiori Manage Malfunction Report Object Page Section

Any Item Details Page
Adapt UI Malfunction tab
Malfunction group

This is custom documentation. For more information, please visit the SAP Help Portal 117
 7/16/2023

Business Context UI Technology Navigation Path UI Element Type

EAMS_NTF Fiori Manage Malfunction Report List Report Filters

Adapt Filters

EAMS_NTF Fiori Manage Malfunction Report List Report View Settings

Table Toolbar Settings

EAMS_EQUI Fiori Manage Malfunction Report Object Page Section

Any Item Details Page
Adapt UI Malfunction tab
Technical Object Details
group

EAMS_EQUI Fiori Manage Malfunction Report List Report Filters

Adapt Filters

EAMS_EQUI Fiori Manage Malfunction Report List Report View Settings

Table Toolbar Settings

EAMS_FL Fiori Manage Malfunction Report Object Page Section

Any Item Details Page
Adapt UI Malfunction tab
Technical Object Details
group

EAMS_FL Fiori Manage Malfunction Report List Report Filters

Adapt Filters

EAMS_FL Fiori Manage Malfunction Report List Report View Settings

Table Toolbar Settings

EAMS_ORD Fiori Manage Malfunction Report Object Page Section

Any Item Details Page
Adapt UI Malfunction tab
Technical Object Details
group

EAMS_ORD Fiori Manage Malfunction Report List Report Filters

Adapt Filters

EAMS_ORD Fiori Manage Malfunction Report List Report View Settings

Table Toolbar Settings

 Note
Custom elds appropriate for Noti cation (EAMS_NTF) and Order (EAMS_ORD) business context can be added to the lter
bar.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Maintenance Noti cation Noti cation (EAMS_NTF) Change the properties of noti cation header
elds without changing the standard logic
(EAM_NOTIFICATION_FIELD_CONTROL)

This is custom documentation. For more information, please visit the SAP Help Portal 118
 7/16/2023

BAdI Name Business Context Business Use

Field Control for Maintenance Order Order (EAMS_ORD) Change the properties of order header
elds without changing the standard logic
(EAM_ORDER_FIELD_CONTROL)

Field Control for Technical Object Equipment (EAMS_EQUI) Change the properties of technical object
header elds without changing the standard
(EAM_TECHNOBJECT_FIELD_CONTROL) Functional Location (EAMS_FL)
logic

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

App Extensibility: Repair Malfunctions

As a key user, you can extend the Repair Malfunctions app according to your business needs.

Features
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

EAMS_NTF Fiori Repair Malfunctions Any Object Page Section

Item Details Page Adapt UI
Malfunction tab
Malfunction group

EAMS_NTF Fiori Repair Malfunctions List Report Filters

Adapt Filters

EAMS_NTF Fiori Repair Malfunctions Table List Report View Settings

Toolbar Settings

EAMS_EQUI Fiori Repair Malfunctions Any Object Page Section

Item Details Page Adapt UI
Malfunction tab Technical
Object Details group

EAMS_EQUI Fiori Repair Malfunctions List Report Filters

Adapt Filters

EAMS_EQUI Fiori Repair Malfunctions Table List Report View Settings

Toolbar Settings

EAMS_FL Fiori Repair Malfunctions Any Object Page Section

Item Details Page Adapt UI
Malfunction tab Technical
Object Details group

EAMS_FL Fiori Repair Malfunctions List Report Filters

Adapt Filters

EAMS_FL Fiori Repair Malfunctions Table List Report View Settings

Toolbar Settings

This is custom documentation. For more information, please visit the SAP Help Portal 119
 7/16/2023

Business Context UI Technology Navigation Path UI Element Type

EAMS_ORD Fiori Repair Malfunctions Any Object Page Section

Item Details Page Adapt UI
Malfunction tab Technical
Object Details group

EAMS_ORD Fiori Repair Malfunctions List Report Filters

Adapt Filters

EAMS_ORD Fiori Repair Malfunctions Table List Report View Settings

Toolbar Settings

 Note
Custom elds appropriate for Asset Management: Maintenance Order (EAMS_ORD) business context can be added to the
lter bar.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Maintenance Noti cation Noti cation (EAMS_NTF) Change the properties of noti cation header
elds without changing the standard logic
(EAM_NOTIFICATION_FIELD_CONTROL)

Field Control for Maintenance Order Order (EAMS_ORD) Change the properties of order header
elds without changing the standard logic
(EAM_ORDER_FIELD_CONTROL)

Field Control for Technical Object Equipment (EAMS_EQUI) Change the properties of technical object
header elds without changing the standard
(EAM_TECHNOBJECT_FIELD_CONTROL) Functional Location (EAMS_FL)
logic

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

App Extensibility: Report Malfunction

As a key user, you can extend the Report Malfunction app according to your business needs.

Features
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Noti cation (EAMS_NTF) Fiori Report Malfunction Adapt Create Page

UI

This is custom documentation. For more information, please visit the SAP Help Portal 120
 7/16/2023

 Note
Custom elds appropriate for Noti cation (EAMS_NTF) business context can be added to the lter bar.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Maintenance Noti cation Noti cation (EAMS_NTF) Change the properties of noti cation header
elds without changing the standard logic
(EAM_NOTIFICATION_FIELD_CONTROL)

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

SAP Apps for Maintenance Master Data

Display Technical Object

Use
As a maintenance technician, you can use this app to view technical objects that have been created to efficiently manage and
evaluate technical assets and maintenance objects.

Key Features
If you have the business role Maintenance Technician, you can view the information stored in the master record of a technical
object by accessing the Display Technical Object app. You can perform the following tasks:

View the master record of functional locations or pieces of equipment.

A functional location represents an area within a system or plant where an object can be installed. Functional locations
are created in hierarchical structures and thus allow a functional or process-oriented structuring of your systems.
Individual maintenance objects are represented by pieces of equipment that are installed at functional locations. The
usage times of a piece of equipment at a functional location are documented over the course of time.

View general data, location data, organizational data, and structure data.

View classi cation information assigned to the master records of equipment and functional locations.

View linear data if the technical object is a linear asset.

View assigned permits to speci c technical objects for which certain regulations or conditions must be taken into
account when using them or performing maintenance work.

View master records for measuring points or counters that are located on the technical object and help to document the
condition of this technical object at a particular point in time.

Create a noti cation for the technical object.

This is custom documentation. For more information, please visit the SAP Help Portal 121
 7/16/2023
View the risks associated with the technical object together with the appropriate responses and safety measures.

This feature is only available if you are working with an external risk management system, such as SAP BusinessObjects
Risk Management.

Display the technical object in the Asset Viewer.

You can display the hierarchical structure of the object and navigate to subordinate objects, such as materials. In
addition, you can open the usage list and view the history of the installation location of a piece of equipment which is
installed in a technical object. The system records a usage period for each installation location, enabling you to track the
complete installation history.

 Note
If you have the business role Maintenance Planner, you can also use this app as well as access the apps Create Technical
Object and Change Technical Object. For more information about processing a technical object, see Process Technical
Object.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Technical Object MW (SAP_EAM_BC_TO_MW)

Related Apps
Display Master Data Information Center

Process Technical Object

Use
Three apps are provided for processing a technical object: Create Technical Object, Change Technical Object, and Display
Technical Object. As a maintenance planner, you can create and change technical objects to efficiently manage and evaluate
technical assets and maintenance objects and monitor the costs involved. You can specify general data, location data,
organizational data, and structure data as well as edit classi cation data and characteristic values, and assign documents.

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

Create a master record for each functional location or piece of equipment.

A functional location represents an area within a system or plant where an object can be installed. Functional locations
are created in hierarchical structures and thus allow a functional or process-oriented structuring of your systems.
Individual maintenance objects are represented by pieces of equipment that are installed at functional locations. The
usage times of a piece of equipment at a functional location are documented over the course of time.

Specify general data, location data, organizational data, and structure data.

Assign classi cation information to the master records of equipment and functional locations.

This is custom documentation. For more information, please visit the SAP Help Portal 122
 7/16/2023
After having created characteristics and classes, this classi cation enables you to easily locate your objects and group
them together for evaluations.

Edit and view linear data if the technical object is a linear asset.

Assign permits to speci c technical objects for which certain regulations or conditions must be taken into account when
using them or performing maintenance work.

Serialize a piece of equipment by assigning a material number and serial number to it.

This makes inventory management possible for the equipment.

Choose a status pro le and set one or several user statuses to further restrict the business transactions allowed by the
various system statuses.

Create master records for measuring points or counters that are located on the technical object and help you to
document the condition of this technical object at a particular point in time.

Create a noti cation or an order for the technical object.

View the risks associated with the technical object together with the appropriate responses and safety measures.

This feature is only available if you are working with an external risk management system, such as SAP BusinessObjects
Risk Management.

Display the technical object in the Asset Viewer.

You can display the hierarchical structure of the object and navigate to subordinate objects, such as materials. In
addition, you can open the usage list and view the history of the installation location of a piece of equipment which is
installed in a technical object. The system records a usage period for each installation location, enabling you to track the
complete installation history.

Assign real estate objects to technical objects.

 Note
To assign real estate objects to technical objects, SAP Intelligent Real Estate needs to be activated. For more
information, see SAP Note 3218235

 Note
If you have the business role Maintenance Technician, you are only able to view the information stored in the technical
object by accessing the Display Technical Object app. For more information about displaying a technical object, see Display
Technical Object.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Technical Object (SAP_EAM_BC_TO)

Related Apps
Process Object Network

Display Master Data Information Center

This is custom documentation. For more information, please visit the SAP Help Portal 123
 7/16/2023

Related Information
For more information about creating, changing and displaying a technical object on the SAP Web user interface for Plant
Maintenance, see Technical Objects on the Web User Interface (PM-EQM).

App Extensibility: Display Technical Object

As a key user, you can extend the Display Technical Object app according to your business needs.

Features
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Equipment (EAMS_EQUI) FPM (WebDynpro) Display Technical Object Detail Page

Call Application in
Customizing Mode Any
Equipment Item Customizing
Page or Show Customizable
Areas Create Customizing
General Data

Functional Location (EAMS_FL) FPM (WebDynpro) Display Technical Object Detail Page
Call Application in
Customizing Mode Any
Functional Location Item
Customizing Page or Show
Customizable Areas Create
Customizing General Data

 Note
The extensibility of the initial screen is not supported for the Display Technical Object app.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Technical Object Equipment (EAMS_EQUI) Change the properties of technical object
header elds without changing the standard
(EAM_TECHNOBJECT_FIELD_CONTROL) Functional Location (EAMS_FL)
logic

 Note
This BAdI does not support changing eld properties on the initial screen.

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

This is custom documentation. For more information, please visit the SAP Help Portal 124
 7/16/2023

App Extensibility: Create Technical Object

As a key user, you can extend the Create Technical Object app according to your business needs.

Features
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Equipment (EAMS_EQUI) FPM (WebDynpro) Create Technical Object Detail Page

Call Application in
Customizing Mode Any
Equipment Item Customizing
Page or Show Customizable
Areas Create Customizing
General Data

Functional Location (EAMS_FL) FPM (WebDynpro) Create Technical Object Detail Page
Call Application in
Customizing Mode Any
Functional Location Item
Customizing Page or Show
Customizable Areas Create
Customizing General Data

 Note
The extensibility of the initial screen is not supported for the Create Technical Object app.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Technical Object Equipment (EAMS_EQUI) Change the properties of technical object
header elds without changing the standard
(EAM_TECHNOBJECT_FIELD_CONTROL) Functional Location (EAMS_FL) logic

 Note
This BAdI does not support changing eld properties on the initial screen.

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

App Extensibility: Change Technical Object

As a key user, you can extend the Change Technical Object app according to your business needs.

This is custom documentation. For more information, please visit the SAP Help Portal 125
 7/16/2023

Features
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Equipment (EAMS_EQUI) FPM (WebDynpro) Change Technical Object Detail Page

Call Application in
Customizing Mode Any
Equipment Item Customizing
Page or Show Customizable
Areas Create Customizing
General Data

Functional Location (EAMS_FL) FPM (WebDynpro) Change Technical Object Detail Page
Call Application in
Customizing Mode Any
Functional Location Item
Customizing Page or Show
Customizable Areas Create
Customizing General Data

 Note
The extensibility of the initial screen is not supported for the Change Technical Object app.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Technical Object Equipment (EAMS_EQUI) Change the properties of technical order
header elds without changing the standard
(EAM_TECHNOBJECT_FIELD_CONTROL) Functional Location (EAMS_FL)
logic

 Note
This BAdI does not support changing eld properties on the initial screen.

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

Process Object Network

Use
Three apps are provided for processing an object network: Create Object Network, Change Object Network, and Display Object
Network. As a maintenance planner, you can use these apps to structure your technical systems horizontally by creating object
networks. This lets you represent and evaluate connections between technical objects. Object networks are represented by
links between various pieces of equipment or functional locations.

This is custom documentation. For more information, please visit the SAP Help Portal 126
 7/16/2023

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

Create either a functional location network or an equipment object network.

An object link can only consist of objects in the same object category, that is, a piece of equipment can only be linked with
another piece of equipment and a functional location with another functional location.

Create the object links that represent the object network by determining the source object and the target object and
entering an object link description.

If your company has speci ed internal number assignment for object links, do not enter a link ID. The system assigns a
number to the object link master record automatically.

Determine the validity of the link, the medium that ows through the link, and the relation between the linked objects.

You can also specify a connecting object between the source and target object by entering the link object. Note that two
pieces of equipment can only be linked by a piece of equipment and two functional locations by a functional location.

Navigate to the master data of the source and target object.

View status information about the object links that represent the object network.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Object Network (SAP_EAM_BC_ON)

Related Apps
Process Technical Object

Display Measuring Point

Use
As a maintenance technician, you can use this app to view master records for measuring points that are located on technical
objects:

Measuring Points document the condition of a technical object at a particular point in time.

Documenting the condition of a particular object is of great importance in cases where detailed records regarding the
correct condition have to be kept for legal reasons. This could involve critical values recorded for environmental
protection purposes, as well as measurements of emissions and pollution for objects of all types. In the case of condition-
based maintenance, maintenance activities are triggered when the measuring point of a technical object has reached a
particular state.

Counters are a special form of measuring point and are used to represent the wear and tear of an object, consumption,
or the reduction of an object’s useful life (for example, the mileage for a vehicle, or an electricity meter for an electrically-
powered system).

This is custom documentation. For more information, please visit the SAP Help Portal 127
 7/16/2023
If you perform counter-based maintenance, maintenance activities are always performed when the counter of the
technical object has reached a particular counter reading.

Key Features
If you have the business role Maintenance Technician, you can perform the following tasks:

View the master record of a measuring point.

View general data, such as a description and the measurement position.

Measuring points are uniquely identi ed by the numbers that they are assigned internally. Since this number is not
descriptive, measuring points sometimes have a text or a descriptive number to describe the position of a measuring
point at a technical object.

View the category that is assigned to the measuring point.

Categories are used to group measuring points for which the same measuring point attributes are valid.

View classi cation information that is assigned to the measuring point.

Numerical characteristics are assigned to determine the unit of measurement reading.

View the measurement range.

The measurement range represents the values that a measuring instrument or counter can display. It can be de ned
that only readings that fall between the upper and lower limits are possible. The measurement range unit speci es the
unit in which the measurement is made by the measuring instrument.

View the target value for the measuring point.

If there is an optimum value for a particular measuring point to which the device concerned is calibrated, this
measurement reading is speci ed as a target value.

View whether the valuation of the measurement reading shall be quantitative, qualitative, or a combination of both.

In a quantitative measurement reading, the current reading measured is entered in the system. The unit of the
measurement reading (for example, degrees Celsius) is de ned by the characteristic in the master record of the
measuring point.

In a qualitative measurement reading, a valuation code is entered in the system. This code represents the current
reading measured. A solely qualitative valuation can only be entered if this is speci ed in the system explicitly for the
measuring point by having selected the Valuation Code Sufficient checkbox.

Display the technical object on which the measuring point is located.

Create measurement documents using the measuring point.

View the measuring point in the Asset Viewer.

 Note
If you have the business role Maintenance Planner, you can also use this app as well as access the apps Create Measuring
Point and Change Measuring Point. For more information about processing a measuring point, see Process Measuring Point.

Supported Device Types

Desktop

This is custom documentation. For more information, please visit the SAP Help Portal 128
 7/16/2023

Relevant Business Catalog

EAM - Measuring Point MW (SAP_EAM_BC_MEAPT_MW)

Related Apps
Process Measurement Document

Process Measuring Point

Use
Three apps are provided for processing master records for measuring points: Create Measuring Point, Change Measuring Point,
and Display Measuring Point. As a maintenance planner, you can create and change master records for measuring points that
are located on technical objects directly or while changing a technical object:

Measuring Points help you to document the condition of a technical object at a particular point in time.

Documenting the condition of a particular object is of great importance in cases where detailed records regarding the
correct condition have to be kept for legal reasons. This could involve critical values recorded for environmental
protection purposes, as well as measurements of emissions and pollution for objects of all types. In the case of condition-
based maintenance, maintenance activities are triggered when the measuring point of a technical object has reached a
particular state.

Counters are a special form of measuring point and are used to represent the wear and tear of an object, consumption,
or the reduction of an object’s useful life (for example, the mileage for a vehicle, or an electricity meter for an electrically-
powered system).

If you perform counter-based maintenance, maintenance activities are always performed when the counter of the
technical object has reached a particular counter reading.

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

Create and change the master record of a measuring point.

Specify general data, such as a description and the measurement position.

Measuring points are uniquely identi ed by the numbers that they are assigned internally. Since this number is not
descriptive, you have the option of giving the measuring point a text or a descriptive number to describe the position of a
measuring point at a technical object.

Assign a measuring point category.

After having created measuring point categories in Customizing, you can use them to group measuring points for which
the same measuring point attributes are valid.

Assign classi cation information to the measuring point.

After having created numerical characteristics to which a unit has been assigned, you assign these characteristics to
determine the unit of measurement reading.

Specify the measurement range.

This is custom documentation. For more information, please visit the SAP Help Portal 129
 7/16/2023
The measurement range represents the values that a measuring instrument or counter can display. You can de ne that
only readings that fall between the upper and lower limits are possible. With the measurement range unit, you de ne the
unit in which the measurement is made by the measuring instrument.

Specify a target value for the measuring point.

If there is an optimum value for a particular measuring point to which the device concerned is calibrated, you can specify
this measurement reading as a target value.

Specify whether the valuation of the measurement reading shall be quantitative, qualitative, or a combination of both.

In a quantitative measurement reading, the current reading measured is entered in the system. The unit of the
measurement reading (for example, degrees Celsius) is de ned by the characteristic in the master record of the
measuring point.

In a qualitative measurement reading, a valuation code is entered in the system. This code represents the current
reading measured. You can only enter a solely qualitative valuation if you have speci ed this in the system explicitly for
the measuring point by selecting the Valuation Code Sufficient checkbox.

Display the technical object on which the measuring point is located.

Create measurement documents using the measuring point.

View the measuring point in the Asset Viewer.

Create a measuring point with transfer data (SAP GUI) while changing a technical object.

 Note
If you have the business role Maintenance Technician, you are only able to view the information stored in the measuring
point by accessing the Display Measuring Point app. For more information about displaying a measuring point, see Display
Measuring Point.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Measuring Point (SAP_EAM_BC_MEAPT)

Related Apps
Process Measurement Document

Process Measurement Document

Use
Two apps are provided for processing a measurement document: Create Measurement Document and Display Measurement
Document. You can use these apps to easily enter the data after a measurement has been taken at a measuring point or a
counter. You can create and display measurement documents as a maintenance planner and as a maintenance technician.

After a measurement has been taken at a measuring point or a counter, the data is stored in a measurement document. You
can create the measurement document directly or enter measurement reading data while con rming a maintenance order.

This is custom documentation. For more information, please visit the SAP Help Portal 130
 7/16/2023
Based on the measurement document, the system calculates the next planned maintenance date and the call date on which a
maintenance order is created. Each time you create a new measurement document, the system recalculates the planned date
for the next maintenance work.

Key Features
Depending on the role to which you are assigned, you can perform the following tasks:

Determine whether the reference object or the measuring point serves as a basis for the measurement reading.

View the measuring point data, including the measuring point number, measurement position, description, characteristic
and unit.

Maintain the measurement result data. Check the time of the measurement reading and the name of the person who
took the measurement reading and change the values where necessary. The time stamp and person are proposed by the
system.

Enter the measurement or counter reading.

If you create a measurement document for a counter, you can either enter the counter reading, or the difference
between the current reading and the last reading. The system will automatically calculate the other value in each case.

Choose a valuation code for providing a qualitative judgment with respect to the result of the measurement.

If you create a measurement document for a measuring point that has not been de ned as a counter, it may be sufficient
to simply enter the valuation code without entering a measurement reading.

Write a long text to provide further information.

View the reference object.

If the reference object is a linear asset, you can also view linear data.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Measurement Document: SAP_EAM_BC_MEADOC (business role: Maintenance Planner)

EAM - Measurement Document MWSAP_EAM_BC_MEADOC_MW (business role: Maintenance Technician)

Related Apps
Process Measuring Point

Display Measuring Point

Process Linear Reference Pattern

Use
Three apps are provided for processing a linear reference pattern: Create Linear Reference Pattern, Change Linear Reference
Pattern, and Display Linear Reference Pattern. As a maintenance planner, you can use these apps to group markers that are

This is custom documentation. For more information, please visit the SAP Help Portal 131
 7/16/2023
alongside a linear asset. A linear reference pattern can be assigned to one or several technical objects.

If you have created markers and linear reference patterns with markers, you can use markers as input help for processing linear
data in maintenance documents, such as functional locations, pieces of equipment, measuring points, maintenance plans and
orders.

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

Create a linear reference pattern directly or use another linear reference pattern as a template.

Create and edit multilingual texts for naming the linear reference pattern.

Specify whether the distance between a marker and a linear point can be negative, or positive, or both, by selecting a
marker distance code.

Specify the unit of measurement (UoM) for the distance from a marker.

Create markers alongside the linear asset and edit multilingual texts for describing the markers.

Select a marker type.

The functional location and equipment marker types always refer to technical objects. If you enter a technical object for
one of these marker types, the system defaults the linear data of the marker and you cannot change the data. You can
also choose the "normal" marker types that do not refer to a technical object. For those markers, you enter the linear
data of the marker manually.

Determine the offset of the marker.

With the offset, you can specify the distance or displacement of the marker from the reference line of a linear technical
asset (such as the distance of a signal post from the middle of the railway line, or the distance of a manhole cover from
the edge of the road).

Add several technical objects as reference objects for markers in one step.

Export and import marker data to and from Microsoft Excel.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Linear Reference Pattern (SAP_EAM_BC_LRP)

Display Master Data Information Center

Use
As a maintenance planner and as a maintenance technician, you can use this app to access the Master Data Information
Center that serves as a central point of access for working with master data. In the Master Data Information Center, you can
use the SAP Enterprise Search, work with different lists and you have direct access to individual task lists, maintenance plans
and technical objects.

This is custom documentation. For more information, please visit the SAP Help Portal 132
 7/16/2023

Key Features
Depending on the role to which you are assigned, you can perform the following tasks:

Con gure the list layout, sort table columns and create lters.

Use the SAP Enterprise Search to search for maintenance objects, such as maintenance noti cations, jobs or orders.

This search solution allows you to search using keywords and search categories and re ne your search by using lters.
Furthermore, you can use additional search criteria and search across different elds. So you can search for functional
locations whose long text contains a speci c search string or for pieces of equipment with a speci c system status, for
example. You can navigate directly to the objects listed in the result list.

Work with different master data lists.

You can con gure a worklist with your favorites and call master data that you have recently processed.

You can access the Technical Object List and the Maintenance Plan and Item List.

The personal object worklists (POWL) contain the most important information on technical objects and maintenance
plans in the form of a table and allow you to process the objects directly. From the personal worklist, you can navigate to
the individual technical objects and to the maintenance plans and items, carry out mass changes and change the status
for several objects.

Directly access individual master data objects.

Directly access and process individual task lists, maintenance plans and technical objects. You can also display technical
objects in the Asset Viewer.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Information Center: SAP_EAM_BC_INFO (business role: Maintenance Planner)

EAM - Information Center MW: SAP_EAM_BC_INFO_MW (business role: Maintenance Technician)

Related Information
For more information about using the Master Data Information Center on the SAP Web user interface for Plant Maintenance,
see Master Data Information Center.

My Inbox
With this app you can process your work ow tasks via mobile or desktop devices anywhere and anytime. If you have con gured
the work ow Deactivation of Technical Objects in the back-end, you can make decisions based on the decision options de ned in
the back-end system and trigger the corresponding follow-up activities.

Key Features
View and add comments

View, upload and delete attachments

This is custom documentation. For more information, please visit the SAP Help Portal 133
 7/16/2023
Create and manage substitution rules to manage the tasks in your absence

Send emails or post tasks on a precon gured JAM site

Browse, sort, lter, and group tasks requiring action

If you have con gured the work ow Deactivation of Technical Objects, you are noti ed, for example, about maintenance
noti cations or orders that have a deactivated technical object assigned and have not yet been completed.

Navigate to object lists to process individual maintenance noti cations or maintenance orders or perform mass actions,
for example.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
App Implementation: My Inbox

App Implementation: My Inbox

Prerequisites
Before implementing the app, you must ensure the following:

You have con gured the work ow Deactivation of Technical Objects in the back-end that de nes the task types to be
used for the My Inbox app.

You have con gured the connections between the Gateway system and your back-end system(s) from which you want to
retrieve the work items. For more information about how to implement the My Inbox app for SAP Business Work ows,
see SAP Help Portal at http://help.sap.com under Technology Platform SAP Gateway SAP Gateway 2.0
Con guration and Deployment Information Con guration Guide SAP Gateway Con guration Guide Gateway
Con guration Connection Settings for SAP Gateway Hub System Connection Settings: SAP Gateway to SAP
Systems .

You have activated the Task Gateway My Service in Customizing for SAP NetWeaver under SAP Gateway OData
Channel Administration General Settings Activate and Maintain Services .

For more information about how to activate the Task Gateway Service, see SAP Help Portal at http://help.sap.com
under Technology Platform SAP Gateway SAP Gateway 2.0 Con guration and Deployment Information
Con guration Guide SAP Gateway Con guration Guide Con guration Settings for SAP Gateway Supported
Scenarios Con guration Settings for OData Channel Scenarios Con guring the Task Gateway Service Activating
Task Gateway Service .

You have assigned the software version to the service in Customizing for SAP NetWeaver under SAP Gateway OData
Channel Administration General Settings Assign Data Provider to Data Model .

For more information about how to assing the software version, see SAP Help Portal at http://help.sap.com under
Technology Platform SAP Gateway SAP Gateway 2.0 Con guration and Deployment Information Con guration
Guide SAP Gateway Con guration Guide Con guration Settings for SAP Gateway Supported Scenarios

This is custom documentation. For more information, please visit the SAP Help Portal 134
 7/16/2023
Con guration Settings for OData Channel Scenarios Con guring the Task Gateway Service Assigning a Software
Version to Service .

If you run on SAP NetWeaver lower than 7.4, you have assigned the back-end system aliases for the Task Processing
Service (/IWPGW/TASKPROCESSING Version 2) in Customizing for SAP NetWeaver under SAP Gateway OData
Channel Development with IW_BEP Registration Assign SAP System Aliases to OData Service .

For more information, see SAP Help Portal at http://help.sap.com under Technology Platform SAP Gateway SAP
Gateway 2.0 Development Information Developer's Guide SAP Gateway Developer Guide OData Channel
Basic Features Service Life-Cycle Activate and Maintain Services .

System Landscape Requirements

For information about the system requirements, see SAP Fiori Overview.

 Note
The app offers the possibility to upload les. For security reasons, we strongly recommend that you install an appropriate
virus scanner in your SAP Fiori system landscape and de ne sufficiently restrictive scan pro les to prevent the upload of
malicious content.

For more information on virus scanning and scan pro les for apps, see section Virus Scanning in the SAP S/4HANA Security
Guide .

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server SAP Note Description

Back-end and front-end servers 2576975 Release Note for My Inbox (Deactivate
Technical Object)

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at

https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F2953.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (Version Number) /IWPGW/TASKPROCESSING (Version 2)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAP UI5 Application

This is custom documentation. For more information, please visit the SAP Help Portal 135
 7/16/2023

Component Technical Name

SAP UI5 Application CA_FIORI_INBOX

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

/IWPGW/TASKPROCESSING (Version 2) You can use the example business catalog Use an existing role
or your custom catalog to create the back- (SAP_BR_MAINTENANCE_PLANNER) or
end PFCG role. create a new one.

For example, to process maintenance

noti cations or maintenance orders that
have a deactivated technical object
assigned, you can use the business catalog
SAP_EAM_BC_MYINBOX.

Con guration Tasks

De ning the Work ow Scenario

This is custom documentation. For more information, please visit the SAP Help Portal 136
 7/16/2023
De ne your work ow scenario by completing the following steps in your Gateway system: add a scenario, assign the consumer
type, assign roles, and de ne tasks.

 Note
This section is only relevant if you want to de ne and use a scenario-speci c tile.

1. Add a work ow scenario.

a. In Customizing for SAP NetWeaver, choose Gateway Service Enablement Content Task Gateway Task
Gateway Service Scenario De nition .

b. Choose New Entries.

c. Fill in the Scenario Decision table as described below and save your entries:

Scenario Identi er: De ne a scenario ID.

Scenario Display Name : De ne a name for your scenario.

Scenario Order: Not relevant for My Inbox.

Technical Service Name : Enter /IWPGW/TASKPROCESSING.

Version: Enter 2.

EntitySet External Name : Enter Task.

Property External Name : Enter TaskDefinitionID.

Default Sort by Property: De ne how you want to sort the work items on the list screen of the application.
If you do not set this parameter, the default value is CreatedOn.

 Note
You can use all the properties of the task collection here.

To display a list of all the possible properties, see SAP Help Portal at http://help.sap.com under
Technology Platform SAP Gateway SAP Gateway 2.0 Content Information Content Guide
SAP Gateway Content Guide SAP Gateway Supported OData Channel Scenarios Task Gateway
Task Gateway Administrator Task Gateway Service Task Gateway Service Version 2 Task
Collection .

The property you have selected is added to the list of possible sorting properties on the detail screen of
the application.

 Note
You can also de ne the sorting principles on the UI of the application. You can choose from a list of
properties.

Mass Action: If you set this parameter to true, you can process, for example, approve or reject, several
tasks of the same type at the same time.

Class for Scenario Count : Leave it empty.

 Note
If the scenario is not part of the Business Work ow engine or BPM, and you want to see the number of
tasks pending for this scenario, enter the name of the class that implements the
/IWWRK/IF_TGW_SCENARIO interface in the back-end system.

This is custom documentation. For more information, please visit the SAP Help Portal 137
 7/16/2023
Quick Act.: Select the Quick Act. checkbox to enable quick approval of work ow items by swiping on the
screen.

This eld is only relevant if you use a touch screen device.

2. Assign the consumer type to the scenario.

a. Select the row containing your approval scenario and choose table Assign Consumer Type to Scenario in the
navigation panel.

b. Choose New Entries.

c. In the Task Gateway Consumer Type eld, select TABLET.

d. Save your entries.

3. Assign a role to the consumer type and the scenario (optional).

Now you can assign an approval scenario to a number of roles, that is, the scenario will only be available to users who are
assigned to at least one of the relevant PFCG roles.

a. Select the row for TABLET (for all devices), and choose Assign Role to Consumer Type and Scenario in the
navigation panel.

b. Choose New Entries.

c. In the Role column, select the role you want to use.

d. Save your entries.

4. De ne tasks for your scenario.

 Note
You can de ne several tasks for your scenario. Make sure that you follow the steps below for each task.

a. Choose Scenario De nition in the navigation panel, and select the row containing your approval scenario.

b. Choose Task De nition for Scenario in the navigation panel.

c. Choose New Entries.

d. Enter the two task type IDs TS00800268 and TS00800273.

 Note
In case of SAP Business Work ow, you can nd your task type ID in the back-end system as described below:

Start the Work ow Builder.

Search for the work ow de nition you would like to enable.

Open the approval step.

Go to Control tab, and check the Task eld.

5. In the SAP System Alias eld, enter the source system alias for the task type.

 Note
Make sure that the Task Gateway Service is connected to the selected system aliases.

6. Save your entries.

This is custom documentation. For more information, please visit the SAP Help Portal 138
 7/16/2023

Con guring the SAP Fiori Launchpad for Your Scenario-Speci c Tiles

To enable My Inbox, create a tile for each work ow scenario as described below.

1. Choose the App Launcher - Dynamic tile.

2. Select the newly created tile, and ll in the following elds as described below:

Title : Enter the name of your work ow scenario, for example, Deactivation of Technical Objects.

Icon: Use any of the available icons.

Service URL: Enter /sap/opu/odata/IWPGW/TASKPROCESSING;mo;v=2/ScenarioCollection?

$filter=key eq '<your scenario identifier>'.

Semantic Object : Enter WorkflowTask.

Action: Enter displayInbox.

Parameters: Enter scenarioId=<ID of your scenario>&listSize=<number of items you want

to display on your list screen>>&showAdditionalAttributes=<true or false>.

where:

scenarioId is mandantory.

listSize is optional. the default is 100.

show AdditionalAttributes = true; if you want to display custom attributes in the List View.

Related Information
App Implementation: My Inbox

SAP Apps for Maintenance Planning and Scheduling

Display Maintenance Plan

Use
As a maintenance technician, you can use this app to view the planning data for recurrent maintenance work stored in time-
based and performance-based maintenance plans, strategy plans and multiple-counter plans. In time-based maintenance
planning, maintenance is performed in speci c cycles, for example, every two months or every six months. Performance-based
maintenance plans contain information about regular maintenance based on counter readings maintained for measuring points
of pieces of equipment and at functional locations.

Key Features
If you have the business role Maintenance Technician, you can perform the following tasks:

View maintenance items that describe which preventive maintenance tasks should take place regularly for a technical
object or a group of technical objects.

View general information about the maintenance item, such as the reference object, the planning data, and the order or
noti cation type (for example, Maintenance Order if the call object to be generated is a maintenance order).

This is custom documentation. For more information, please visit the SAP Help Portal 139
 7/16/2023
View the location and account assignment information for the maintenance item. If the maintenance object is a linear
asset, you can also view its linear data.

Display the technical object and the task list assigned to the maintenance item.

The task list speci es the individual work steps that must be executed, the spare parts and tools required for the job, as
well as the required completion time.

View the maintenance cycles of the maintenance plan as Planning Data.

If the maintenance plan is a strategy plan, the assigned maintenance strategy determines the maintenance cycles. If the
maintenance plan is performance-based, counters are assigned. Furthermore, you can view other scheduling information
speci c to the maintenance plan, such as shift factors and call control parameters.

View the scheduled Maintenance Calls for the maintenance plan.

You can display the call object (for example, the maintenance order) and view the most important information about the
scheduled maintenance calls in a table. For example, you can view the planned date, the call date, the completion date
and the scheduling status.

Open quickviews to access relevant information about technical objects and task lists without having to navigate away
from the screen you are working in.

 Note
If you have the business role Maintenance Planner, you can also use this app as well as access the apps Create Maintenance
Plan and Change Maintenance Plan. For more information about processing a maintenance plan, see Process Maintenance
Plan.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Maintenance Plan MW (SAP_EAM_BC_MPLAN_MW)

Related Apps
Manage Maintenance Plan and Item List

Display Maintenance Item

Process Maintenance Plan

Use
Three apps are provided for processing a maintenance plan: Create Maintenance Plan, Change Maintenance Plan, and Display
Maintenance Plan. As a maintenance planner, you can use these apps to plan recurrent maintenance work by creating time-
based and performance-based single cycle plans, strategy plans, and multiple-counter plans. In time-based maintenance
planning, maintenance is performed in speci c cycles, for example, every two months or every six months. With performance-
based maintenance plans, you can plan regular maintenance based on counter readings maintained for measuring points of
pieces of equipment and at functional locations.

This is custom documentation. For more information, please visit the SAP Help Portal 140
 7/16/2023

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

Create a maintenance plan and determine which maintenance call object the system generates for the maintenance
plan when a maintenance call is due (for example, maintenance order). You can create single cycle plans, strategy plans
or multiple-counter plans.

Create and assign maintenance items that describe which preventive maintenance tasks should take place regularly for
a technical object or a group of technical objects.

View and edit general information for the maintenance item, such as the reference object, the planning data and the
order or noti cation type (for example, Maintenance Order if the call object to be generated is a maintenance order).

View the location and account assignment information for the maintenance item. If the maintenance object is a linear
asset, you can also view its linear data.

Assign a task list to the maintenance item to specify the individual work steps that must be executed, the spare parts
and tools required for the job, as well as the required completion time. You can create a new task list or assign an
existing one.

Assign maintenance items to the maintenance plan by creating new items or selecting existing ones. You can also delete
existing assignments.

Determine and view the maintenance cycles of the maintenance plan as Planning Data.

If the maintenance plan is a strategy plan, the assigned maintenance strategy determines the maintenance cycles. If the
maintenance plan is performance-based, you can assign counters. Furthermore, you can write a long text and edit other
scheduling information speci c to the maintenance plan, such as shift factors and call control parameters.

View the scheduled Maintenance Calls for the maintenance plan.

You can display the call object (for example, the maintenance order) and view the most important information about the
scheduled maintenance calls in a table. For example, you can view the planned date, the call date, the completion date
and the scheduling status.

Open quickviews to access relevant information about technical objects and task lists without having to navigate away
from the screen you are working in.

Deactivate and reactivate the maintenance plan.

Select and deselect the maintenance plan for deletion.

When a maintenance planner de nes a maintenance process for a piece of equipment or a functional location, he has to
de ne the target system condition when the maintenance job is carried out by the maintenance technician. If a piece of
equipment has to be shut down during maintenance and if shutting down this equipment has an impact on production,
this has to be planned upfront and not on the day of the maintenance. This allows you to plan the maintenance of the
pieces of equipment in an optimal manner.

In the Create Maintenance Plan app, for maintenance plans of the category Maintenance Order, you as a maintenance
planner can select the appropriate operating system condition value and assign it to a maintenance item. During
scheduling, when the maintenance call is called which results in the creation of a call object of type Maintenance Order,
the maintenance order header will have the system condition. The system condition can then be used for further
business processes wherever it is relevant.

The system condition can be selected while executing a preventive maintenance order.

The prede ned system conditions are:

0 - not in operation

This is custom documentation. For more information, please visit the SAP Help Portal 141
 7/16/2023
1 - in operation

Final Due Date for Preventive Maintenance Noti cations

Final due date is the latest date by which a maintenance activity must be completed. Final due date is calculated based on the
priority of a maintenance activity. When you select the priority for a maintenance activity, the nal due date is calculated and
displayed.

During a maintenance activity, maintenance noti cations that are created for a piece of equipment or a functional location
must be completed by the nal due date to ful l compliance or regulatory requirements. Although required start date and
required end date de ne the time by which a job must be nished, you may want to provide some time to plan for contingencies.
This time period is called the nal due date and is relative to the date when the maintenance noti cation was created in the
system.

You can use the Final Due Date eld in maintenance noti cations that originate from a preventive maintenance process
(maintenance plan scheduling) and the standard corrective maintenance process where the maintenance noti cations are
created when an issue occurs in the system.

 Note
If you have the business role Maintenance Technician, you are only able to view the information stored in the maintenance
plan by accessing the Display Maintenance Plan app. For more information about displaying a maintenance plan, see Display
Maintenance Plan.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Maintenance Plan (SAP_EAM_BC_MPLAN)

Related Apps
Manage Maintenance Plan and Item List

Display Maintenance Item

Related Information
For more information about processing a maintenance plan on the SAP Web user interface for Plant Maintenance, see
Maintenance Plan.

App Extensibility: Display Maintenance Plan

As a key user, you can extend the Display Maintenance Plan app according to your business needs.

Custom Fields
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

This is custom documentation. For more information, please visit the SAP Help Portal 142
 7/16/2023

Business Context UI Technology Navigation Path UI Element Type

Maintenance Plan FPM (WebDynpro) Display Maintenance Plan Detail Page

(EAMS_MPLA) Call Application in
Customizing Mode Any Plan
Customizing Page or Show
Customizable Areas Create
Customizing Planning Data

Maintenance Item FPM (WebDynpro) Display Maintenance Plan Detail Page

(EAMS_MPOS) Call Application in
Customizing Mode Any Plan
Customizing Page or Show
Customizable Areas Create
Customizing Items

 Note
The extensibility of the initial screen is not supported for the Display Maintenance Plan app.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Maintenance Plan Maintenance Plan (EAMS_MPLA) Change the properties of maintenance plan
header elds without changing the standard
(EAM_MAINT_PLAN_FIELD_CONTROL)
logic

Field Control for Maintenance Item Maintenance Item (EAMS_MPOS) Change the properties of maintenance item
header elds without changing the standard
(EAM_MAINT_ITEM_FIELD_CONTROL)
logic

 Note
This BAdI does not support changing eld properties on the initial screen.

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

Business Scenarios
The following business scenarios are available:

You can transfer the custom eld data from maintenance plan to a maintenance noti cation (call object) by enabling the
business scenario EAM_MPLA_2_NTF.

You can transfer the custom eld data from maintenance plan to a maintenance order (call object) by enabling the
business scenario EAM_MPLA_2_ORD.

App Extensibility: Change Maintenance Plan

This is custom documentation. For more information, please visit the SAP Help Portal 143
 7/16/2023
As a key user, you can extend the Change Maintenance Plan app according to your business needs.

Custom Fields
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Maintenance Plan FPM (WebDynpro) Change Maintenance Plan Detail Page

(EAMS_MPLA) Call Application in
Customizing Mode Any Plan
Customizing Page or Show
Customizable Areas Create
Customizing Planning Data

Maintenance Item FPM (WebDynpro) Change Maintenance Plan Detail Page

(EAMS_MPOS) Call Application in
Customizing Mode Any Plan
Customizing Page or Show
Customizable Areas Create
Customizing Items

 Note
The extensibility of the initial screen is not supported for the Change Maintenance Plan app.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Maintenance Plan Maintenance Plan (EAMS_MPLA) Change the properties of maintenance plan
header elds without changing the standard
(EAM_MAINT_PLAN_FIELD_CONTROL) logic

Field Control for Maintenance Item Maintenance Item (EAMS_MPOS) Change the properties of maintenance item
header elds without changing the standard
(EAM_MAINT_ITEM_FIELD_CONTROL) logic

 Note
This BAdI does not support changing eld properties on the initial screen.

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

Business Scenarios
The following business scenarios are available:

This is custom documentation. For more information, please visit the SAP Help Portal 144
 7/16/2023
You can transfer the custom eld data from maintenance plan to a maintenance noti cation (call object) by enabling the
business scenario EAM_MPLA_2_NTF.

You can transfer the custom eld data from maintenance plan to a maintenance order (call object) by enabling the
business scenario EAM_MPLA_2_ORD.

App Extensibility: Create Maintenance Plan

As a key user, you can extend the Create Maintenance Plan app according to your business needs.

Custom Fields
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Maintenance Plan FPM (WebDynpro) Create Maintenance Plan Detail Page

(EAMS_MPLA) Call Application in
Customizing Mode
Customizing Page or Show
Customizable Areas Create
Customizing Planning Data

Maintenance Item FPM (WebDynpro) Create Maintenance Plan Detail Page

(EAMS_MPOS) Call Application in
Customizing Mode
Customizing Page or Show
Customizable Areas Create
Customizing Items

 Note
The extensibility of the initial screen is not supported for the Create Maintenance Plan app.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Maintenance Plan Maintenance Plan (EAMS_MPLA) Change the properties of maintenance plan
header elds without changing the standard
(EAM_MAINT_PLAN_FIELD_CONTROL)
logic

Field Control for Maintenance Item Maintenance Item (EAMS_MPOS) Change the properties of maintenance item
header elds without changing the standard
(EAM_MAINT_ITEM_FIELD_CONTROL)
logic

 Note
This BAdI does not support changing eld properties on the initial screen.

This is custom documentation. For more information, please visit the SAP Help Portal 145
 7/16/2023
For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

Business Scenarios
The following business scenarios are available:

You can transfer the custom eld data from maintenance plan to a maintenance noti cation (call object) by enabling the
business scenario EAM_MPLA_2_NTF.

You can transfer the custom eld data from maintenance plan to a maintenance order (call object) by enabling the
business scenario EAM_MPLA_2_ORD.

Manage Maintenance Plans

With this app, you can manage maintenance plans.

Key Features
You can use this app to do the following:

View maintenance plans by using the free text search or by ltering for parameters.

View maintenance plans according to their status:

Scheduled: The maintenance plans have been scheduled.

Created: This is a new maintenance plan which has not yet been scheduled.

Deactivated: The maintenance plan cannot create maintenance orders.

Marked for Deletion: The maintenance plan that is marked for deletion is still available in the database and it can
be restored.

View details of a maintenance plan.

Choose a maintenance plan to access the quick view and navigate to speci c apps to perform additional tasks.

Create a maintenance plan and determine which maintenance call object the system generates for the maintenance
plan when a maintenance call is due. The maintenance plan may generate maintenance orders or maintenance requests.

Create the various types of maintenance plans such as:

Single cycle time-based plan or single cycle performance-based plan

Time-based strategy plan or counter-based strategy plan

Multiple counter plan

Activate or deactivate one or more maintenance plans.

Mark one or more maintenance plans for deletion. You can also remove the deletion ag.

View the progress of a maintenance plan schedule through micro charts in the list report and the object page.

View the change log of a maintenance plan in a dedicated timeline view section.

View the list of maintenance calls that are generated when a maintenance plan is scheduled.

Navigate to the detail page of the maintenance calls to view further details of the call.
This is custom documentation. For more information, please visit the SAP Help Portal 146
 7/16/2023
For a selected maintenance call, navigate to the call object detail page to derive further details on the speci c call object.

Create and assign maintenance items that describe which preventive maintenance tasks should take place regularly for
a technical object or a group of technical objects.

View and edit general information for the maintenance item, such as the reference object, the planning data and the
order or noti cation type (for example, Maintenance Order if the call object to be generated is a maintenance order).

View the location and account assignment information for the maintenance item.

Assign a task list to the maintenance item to specify the individual work steps that must be executed, the spare parts
and tools required for the job, as well as the required completion time. You can create a new task list or assign an
existing one.

While updating a maintenance plan, you can assign an existing maintenance item to the plan. To create a maintenance
item, go to Manage Maintenance Items app. For more information, see Manage Maintenance Items.

Determine and view the maintenance cycles of the maintenance plan as planning data.

If the maintenance plan is a strategy plan, the assigned maintenance strategy determines the maintenance cycles. If the
maintenance plan is performance-based, you can assign counters. Furthermore, you can write a long text and edit other
scheduling information speci c to the maintenance plan, such as shift factors and call control parameters.

View the scheduled maintenance calls for the maintenance plan.

You can display the call object (for example, the maintenance order) and view the most important information about the
scheduled maintenance calls in a table. For example, you can view the planned date, the call date, the completion date,
and the scheduling status.

Perform mass editing of maintenance plans.

Attach any relevant documents or links to provide additional information about the maintenance plan. You can attach
documents which can give information such as the reason for setting up the program based on the outcome of reliability-
centered maintenance (RCM), root cause analysis (RCA), and failure mode and effects analysis (FMEA).

 Recommendation
We recommend that you use Document Management System (DMS) with Harmonized Document Management
(HDM) and not Generic Object Services (GOS).

Mass Editing of Maintenance Plans

In the Manage Maintenance Plans app, you can edit multiple plans at a time.

Procedure
As a maintenance planner, you can change the parameters such as scheduling indicator, authorization group, cycle modi cation
factor, and so on for multiple plans at once. Using a simulation option, you can check the correctness of data in the application
log.

1. In the list report, select at least two maintenance plans that you would like to edit.

2. Choose Mass Change.

3. Change the required details and choose Next.

4. Enter a description for the mass job or keep a default name that is the combination of the object name, username, and
the date and time.

This is custom documentation. For more information, please visit the SAP Help Portal 147
 7/16/2023
5. Select Simulate to verify the entered data without saving the changes.

In the Application Logs, you can check the job for potential error and view the history of previous mass change jobs.

6. Choose Apply to save the changes.

Related Information
Manage Maintenance Plans

Display Maintenance Item

Use
You can use this app to view the information stored in a maintenance item. A maintenance item describes which preventive
maintenance tasks should take place regularly at a technical object or a group of technical objects. You can display maintenance
items as a maintenance planner and as a maintenance technician.

Key Features
Depending on the role to which you are assigned, you can perform the following tasks:

View general information such as the long text, the maintenance strategy, the maintenance plan and the technical
object.

View the planning data for the maintenance item, such as the planning plant and the order or noti cation type (for
example, Maintenance Order if the call object to be generated is a maintenance order).

View the location and account assignment information for the maintenance item.

If the maintenance object is a linear asset, you can also view its linear data

Display the maintenance item in the Asset Viewer.

Display the maintenance plan to which the maintenance item is assigned.

Display the technical object and the assigned task list.

The task list speci es the individual work steps that must be executed, the spare parts and tools required for the job, as
well as the required completion time. You can also display the technical object in the Asset Viewer.

Open quickviews to access relevant information about the maintenance plan, the technical object and the assigned task
list without having to navigate away from the screen you are working in.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Maintenance Plan Item: SAP_EAM_BC_MPLANIT (business role: Maintenance Planner)

EAM - Maintenance Plan Item MW: SAP_EAM_BC_MPLANIT_MW (business role: Maintenance Technician)

Related Apps
This is custom documentation. For more information, please visit the SAP Help Portal 148
 7/16/2023
Manage Maintenance Plan and Item List

App Extensibility: Display Maintenance Item

As a key user, you can extend the Display Maintenance Item app according to your business needs.

Custom Fields
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Maintenance Item FPM (WebDynpro) Display Maintenance Item Detail Page

(EAMS_MPOS) Call Application in
Customizing Mode Any Item
Customizing Page or Show
Customizable Areas Create
Customizing General Data

 Note
The extensibility of the initial screen is not supported for the Display Maintenance Item app.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Maintenance Item Maintenance Item (EAMS_MPOS) Change the properties of maintenance item
header elds without changing the standard
(EAM_MAINT_ITEM_FIELD_CONTROL)
logic

 Note
This BAdI does not support changing eld properties on the initial screen.

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

Manage Maintenance Items

With the Manage Maintenance Items app, you as a maintenance planner can manage maintenance items. You can create
maintenance items, decide how to evaluate nal due date for a maintenance item, assign maintenance item to a maintenance
plan, view details of a maintenance item, view status of an equipment or a functional location within a maintenance item, and so
on.

Key Features
This is custom documentation. For more information, please visit the SAP Help Portal 149
 7/16/2023
You can use this app to do the following:

View maintenance items by using the free text search or by ltering for parameters.

View details of a maintenance item.

View if an equipment or a functional location has been deactivated or if it has been marked for deletion

Select several maintenance items and edit multiple parameters of all selected items at a time

View the status of an equipment or a functional location within a maintenance item. This provides you with a quick
glimpse of details of the maintenance item and enables you to take quick action on such maintenance items. For
example, you can lter those maintenance items and detach them from the corresponding maintenance plans to avoid
call objects from getting created for those inactive pieces of equipment or functional locations.

Choose a maintenance item to access the quick links and navigate to speci c apps to perform additional tasks.

Create maintenance items for the category Maintenance Order or Maintenance Request.

Navigate to a speci c instance of a call object that was generated from this maintenance item

 Note
When you view the call objects for a maintenance item, you can view the completion date and time in your local user
time zone. The system converts the system time zone into the time zone of the current user as set in the SAP Fiori
Launchpad and the browser.

Decide how you want to manage the nal due date for maintenance noti cations and maintenance orders by selecting
one of the three options:

Compliance Check by Priority - Based on the priority of the maintenance item, the nal due date is calculated.
For more information, see Final Due Date.

Compliance Check by Offset - For a single cycle plan with the category Maintenance Order, you will be able to
check the compliance and set the required dates by offset.

 Note
The calculated order start date and end date are default values that can be overwritten by the standard
scheduling parameters in the maintenance order.

 Note
The offset days for the maintenance item are different from the cycle offset that is de ned for a maintenance
plan. The cycle offset helps in starting the maintenance plan after the offset days are reached.

No Compliance Check - Final due date is calculated without verifying the compliance requirements. The nal due
date is a default inde nite date which is 31 December, 9999.

Assign an unassigned maintenance item to a maintenance plan.

Remove or unassign a maintenance item from a maintenance plan.

Assigning Causes and Reasons

With the Manage Maintenance Items app, you can assign cause codes or reason codes to a maintenance item to specify why a
maintenance activity is performed.

 Recommendation
We recommend creating a new customer-speci c catalog for de ning your own cause and reason code groups.
This is custom documentation. For more information, please visit the SAP Help Portal 150
 7/16/2023

To simplify the selection of codes, you can assign code groups to a catalog pro le. You can then assign these catalog pro les to
the maintenance plan category in customizing.

If a maintenance item is assigned to a maintenance strategy, you can assign reasons or causes to individual maintenance
packages of the strategy.

You can de ne maintenance plan types or categories in SAP Customizing Implementation Guide Plant Maintenance and
Customer Service Maintenance Plans, Work Centers, Task Lists and PRTs Maintenance Plans Set Maintenance Plan
Categories.

You can de ne the origin of the cause and reason details assigned to the maintenance item in SAP Customizing
Implementation Guide Plant Maintenance and Customer Service Maintenance Plans, Work Centers, Task Lists and PRTs
Maintenance Plans De ne Origin of Maintenance Item.

Compliance
It is necessary for the maintenance item to be compliant to regulatory requirements. For adherence to compliance, you can use
certain values to calculate essential dates by which the maintenance activity must be completed.

 Note
This feature is available only in the Fiori apps Manage Maintenance Items (F5356) and Manage Maintenance Plans (F5325).

Key Features
You can decide to calculate the nal due date using one of the options:

Compliance Check by Priority - Based on the priority of the maintenance item, the nal due date is calculated. For more
information, see Final Due Date.

Compliance Check by Offset - For a single cycle plan with the category Maintenance Order, you will be able to check the
compliance and set the required dates by offset.

 Note
The calculated start date and end date of the maintenance order can be overwritten by the standard scheduling
parameters in the maintenance order.

 Note
The offset days for the maintenance item are different from the cycle offset that is de ned for a maintenance plan
which helps in starting the maintenance plan after the offset days are reached.

No Compliance Check - Final due date is calculated without verifying the compliance requirements. The nal due date is
a default inde nite date which is 31 December, 9999.

Offset
Compliance by offset is available only for single cycle plans with the category Maintenance Order.

When you create or update a single cycle maintenance plan that belongs to the category Maintenance Order, you can choose to
check compliance of the maintenance item by offset. The nal due date, basic start date, and basic end date are calculated and

This is custom documentation. For more information, please visit the SAP Help Portal 151
 7/16/2023
updated based on the start offset days and the end offset days. When you assign a maintenance item to this single cycle
maintenance plan of category Maintenance Order, the maintenance item inherits the the capability to allow you to decide the
dates based on compliance by offset. If you unassign the maintenance item from the maintenance plan, it loses the capability to
check compliance by offset.

When you create a maintenance item without association with a maintenance plan, you cannot calculate the dates by checking
the compliance by offset. Only if a single cycle maintenance plan of category Maintenance Order is associated with the
maintenance item, you can calculate dates based on compliance of the maintenance item by offset.

 Note
The offset values in uence the basic start date and the basic end date. However, the order scheduling parameters will
decide the dates based on the duration of the operation and the scheduling direction (forward or backward, number of days
in the past, and so on).

In the below image, A is working with a maintenance item that is assigned to a single cycle plan of category Maintenance Order.
A has chosen to calculate the nal due date by checking the compliance based on offset.

Compliance By Offset

Calculation of Compliance Check By Offset

The nal due date is always equal to the planned date which is determined by the system.

Example

Let us consider that a maintenance plan has the following values:

Planned date = 6th March (the date by which the maintenance order is planned for execution)

Start offset as 5 days, Start date = 6 March (start date is the same as the planned date) - 5 days (start offset) = 1st
March

End offset as 3 days, End date = 6 March - 3 days (end offset) = 3rd March

Final due date = 6th March (planned date)

In this image, you can view the dates:

This is custom documentation. For more information, please visit the SAP Help Portal 152
 7/16/2023

Example for Compliance by Offset

From the above values, you can gather the following:

According to the maintenance plan, the planned date is 6th March. But, A would like to have a buffer period as
precaution.

A enters the start offset (5 days) and end offset (3 days).

Depending on the number of start offset days, A can start the work before 6th March. Here, the start offset days are 5
so A can start the work on 1st March.

A can also nish his work ahead of the planned date depending on the end offset days.

 Note
The end offset cannot be greater than the start offset which means that the maintenance activity cannot end before
it starts.

Mass Editing of Maintenance Items - Find Maintenance Items

In the Find Maintenance Items app, you (as a Maintenance Planner) can change multiple parameters for several maintenance
items at a single time.

Context
You can select multiple items from the list report and change general and planning data for all selected objects. Using the
simulation option, you can check the correctness of the job in the Application Logs.

Procedure
1. On the initial screen, select at least two items that you would like to edit from the list.

2. Choose Mass Edit Items. In a dialog window, you can change the following parameters for all selected items:

In the General Data section, you can change the assembly, description, material, and other parameters.

In the Planning Data section, you can edit the planning plant, order and noti cation types, priority and other
details.

 Note
You can set, overwrite, and clear eld values, or, when applicable, enter them manually. Depending on the speci c
parameter, the following options may be available in the dropdown list:
This is custom documentation. For more information, please visit the SAP Help Portal 153
 7/16/2023
<leave blank>: allows you to leave the eld empty for all selected items

<keep existing values>: use it to keep the existing values for your selected items

<value help>: you can choose the value from the list of pre-de ned values

Pre-existing data: apply values of one of the selected items to all selected items

3. Choose Simulate to check the job for correctness without saving changes. You can enter the description of the job or let
the system de ne the description by default. Choose Apply to simulate the job. OR,

4. Select Save, if you want to proceed with saving of your changes. You can enter the job description or let the system
de ne the description by default. Select Apply to apply mass changes.

5. You can view the details of the simulated or scheduled job in the Application Logs.

Related Information
Find Maintenance Items

Mass Editing of Maintenance Items - Manage Maintenance Items

In the Manage Maintenance Items app, you can edit multiple items at a time.

Procedure
As a maintenance planner, you can change the parameters such as maintenance planner group, equipment, functional location,
and so on for multiple items at once. Using a simulation option, you can check the correctness of data in the application log.

1. In the list report, select at least two maintenance items that you would like to edit.

2. Choose Mass Change.

3. Change the required details and choose Next.

4. Enter a description for the mass job or keep a default name that is the combination of the object name, username, and
the date and time.

5. Select Simulate to verify the entered data without saving the changes.

In the Application Logs, you can check the job for potential error and view the history of previous mass change jobs.

6. Choose Apply to save the changes.

Related Information
Manage Maintenance Items

Manage Maintenance Plan and Item List

Use
As a maintenance planner, you can use this app to access the Maintenance Plan and Item List. This worklist provides, in a table,
the most important information about maintenance plans and items and enables you to not only process individual documents,
but also carry out mass changes to maintenance plan and maintenance item data.

This is custom documentation. For more information, please visit the SAP Help Portal 154
 7/16/2023

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

De ne queries in which you specify selection criteria for maintenance plans and maintenance items.

If you only specify selection criteria for maintenance plans, the results list only displays maintenance plans and the
maintenance items that belong to them. If you only specify selection criteria for maintenance items, the results list only
displays maintenance items.

Navigate from the list to the maintenance plans and maintenance items and process them.

Navigate from the list to the assigned technical objects and call objects (such as noti cations or maintenance orders)
and process them.

Change how the information on maintenance plans and items is displayed by con guring the layout of the list.

Print the results list of your query as a PDF document.

Change the system status of one or more selected maintenance plans.

Only those statuses that are currently possible for the maintenance plans you selected are available.

Carry out mass data changes for maintenance plans and maintenance items.

You can see which maintenance plans and maintenance items the system was able to change successfully by viewing the
icons in the Changed table column.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Maintenance Plan Item (SAP_EAM_BC_MPLANIT)

Related Apps
Process Maintenance Plan

Display Maintenance Item

Related Information
For more information about using the maintenance plan and item list on the SAP Web user interface for Plant Maintenance, see
Maintenance Plan and Maintenance Item List.

Display Task List

Use
As a maintenance technician, you can use this app to view all relevant information about recurring standardized work
sequences, inspections and repairs. Maintenance task lists describe a sequence of individual maintenance activities that must

This is custom documentation. For more information, please visit the SAP Help Portal 155
 7/16/2023
be performed repeatedly within a company. They contain important information about the spare parts and tools required for
the work steps, the work centers involved, and the time required to perform the work.

Key Features
If you have the business role Maintenance Technician, you can perform the following tasks:

View general task list information, such as the responsible work center and plant, the status, and the maintenance
strategy.

View the task list operations that describe the individual work steps to be executed in detail.

Find out which spare parts you need to execute the maintenance task.

View which production resources or tools are required to perform the maintenance tasks, such as measuring and
inspection instruments or cranes.

View the chronological interdependence between the maintenance tasks.

Relationships describe how operations are linked to one another in the process and determine their sequence.

View which technical objects and assemblies are assigned for inspection rounds. In the operation details, measuring
points can be represented by production resources/tools for the technical objects.

Read the long text with a detailed description about the individual work step which must be executed.

Display assigned documents.

Display quickviews with relevant information about technical objects, materials, and long texts without having to
navigate to these objects.

Display the task list in the Asset Viewer.

 Note
If you have the business role Maintenance Planner, you can also use this app as well as access the apps Create Task List and
Change Task List. For more information about processing a maintenance task list, see Process Task List.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Task List MW (SAP_EAM_BC_TL_MW)

Process Task List

Use
Three apps are provided for processing a maintenance task list: Create Task List, Change Task List, and Display Task List. As a
maintenance planner, you can use task lists to standardize recurring work sequences and to plan inspections, maintenance, and
repairs. Maintenance task lists describe a sequence of individual maintenance activities that must be performed repeatedly
within a company. They contain important information about the spare parts and tools required for the work steps, the work
centers involved, and the time required to perform the work. Furthermore, task lists enable you to react quickly to changing

This is custom documentation. For more information, please visit the SAP Help Portal 156
 7/16/2023
environmental protection or occupational safety regulations that may affect continuous maintenance. When you assign a task
list to a maintenance item, maintenance noti cation, or a maintenance order, the system copies this maintenance data from
the task list into the respective maintenance document.

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

Create a general task list or a task list for a speci c piece of equipment or functional location.

You can specify a validity date that can be today's date or a date in the past or future.

You can use an existing task list as a template (reference) when creating a new task list. The system copies the general
data and the operation data of the task list as default values to the new task list. You can specify whether you want to
also copy relationships, permits, linked documents, and task list descriptions to the new task list.

Provide general information, such as the responsible work center and plant, the status, and the maintenance strategy.

Create task list operations to describe the individual work steps which must be executed in detail

Specify the required spare parts by assigning material components from the bill of material or adding materials that are
not in the BOM of the maintenance object. Add or update non-stock components with or without master data details.

Lean Services can now be added to the task list operations. It can be added only as a description or can be added from
the material master. It can also be de ned as enhanced limit service by changing the item category. By default, lean
services are added as non-stock material item category.

 Note
Update of non-stock material/lean service only allows to update quantity and unit of measure. During update, you
can add a new non-stock material/lean service or delete an existing non-stock material/lean service.

Determine which production resources or tools are required to perform the maintenance tasks, such as measuring and
inspection instruments or cranes.

Describe the chronological interdependence between the maintenance tasks and create relationships between
operations. Relationships describe how operations are linked to one another in the process and determine their
sequence.

For inspection rounds, assign technical objects and assemblies at operation level. In the operation details, you can enter
measuring points as production resources/tools for the technical objects that you have assigned at operation level.

Create and edit a long text to describe the individual work step which must be executed in detail.

Assign and display documents.

Display quickviews with relevant information about technical objects, materials, and long texts without having to
navigate to these objects.

Display the task list in the Asset Viewer.

Maintain details about Storage Location and Plant for stock materials in task list.

 Note
If you have the business role Maintenance Technician, you are only able to view the information stored in the maintenance
task list by accessing the Display Task List app. For more information about displaying a maintenance task list, see Display
Task List .

This is custom documentation. For more information, please visit the SAP Help Portal 157
 7/16/2023

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Task List (SAP_EAM_BC_TL)

Related Information
For more information about processing a task list on the SAP Web user interface for Plant Maintenance, see Task list .

SAP Apps for Maintenance Execution

Process Maintenance Noti cation

Use
Three apps are provided for processing a maintenance noti cation: Create Maintenance Noti cation, Change Maintenance
Noti cation, and Display Maintenance Noti cation. You can use these apps to easily report a malfunction or a problem in a
technical system. You do this by creating a noti cation in which you specify the technical object, describe the malfunction, and
enter the activities to be performed. In addition, you can describe the causes by using codes, con rm the time spent on each
activity and print out job papers. You can create, change, and display noti cations as a maintenance planner and as a
maintenance technician.

Key Features
Depending on the role to which you are assigned, you can perform the following tasks:

Specify the technical object by using hierarchical structure lists that also provide you with information about assigned
materials and components.

Describe the breakdown in detail and create tasks and activities to be performed.

Describe the damages and causes by choosing appropriate codes.

By doing the above, you can ensure that issues are entered in a standardized way and can be evaluated automatically.

Upload and attach documents to add further information to the noti cation.

Con rm the time spent on each activity after you have completed your work.

Print out the shop paper of the noti cation physically or virtually on the job card and transfer the noti cation to the job
list.

Manage print and email output details for output control of maintenance noti cations by specifying the required print
queue for outputs to be printed and providing email details for outputs to be sent by email. The Preview column provides
the option to preview the output.

Add attachments to maintenance noti cations and provide attachment details such as document type, part, and version.
You can also add a description for the attachment.

Open quickviews to get relevant information about maintenance documents, technical objects, materials, and long texts
without having to navigate away from the screen on which you are working.
This is custom documentation. For more information, please visit the SAP Help Portal 158
 7/16/2023
View the nal due date for a maintenance noti cation. This date is determined based on the priority of the maintenance
noti cation. When you select the priority for a maintenance noti cation, the nal due date is determined and displayed.
When you change the priority of the maintenance noti cation, the nal due date is redetermined.

If you update the nal due date after the maintenance order is created, the nal due date will not be updated in the
maintenance order. If it is necessary to change the nal due date, you can manually change it if you have authorization
for the business transaction LACD.

You can also view the previous nal due date. Whenever there is a change in the nal due date, the previous nal due
date is displayed for your reference. This is the date that existed before the current nal due date.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Noti cation: SAP_EAM_BC_NTF (business role: Maintenance Planner)

EAM - Noti cation MW: SAP_EAM_BC_NTF_MW (business role: Maintenance Technician)

Related Apps
Manage Noti cation List

Manage Orders and Noti cations in Information Center

Related Information
For more information about creating, changing, and displaying maintenance noti cations on the SAP Web user interface
for Plant Maintenance, see Maintenance Noti cation.

Final Due Date

Manage Noti cation List

Use
As a maintenance planner, you can use this app to access a worklist of all the maintenance noti cations that match the
selection criteria in the query you have de ned. The noti cation list contains the most important information on maintenance
noti cations in the form of a table and allows you to process noti cations and the assigned technical objects directly.
Furthermore, you can carry out mass changes and assign one or more noti cations to a speci c order. You can con gure the list
layout, sort table columns and create lters. In addition, you have the option of displaying a table column for monitoring critical
dates, whose colors help you detect issues.

With this app you can also access the Order List, the combined Order and Noti cation List, and the Order and Operation List.

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

Con gure the personal object worklist (POWL) by creating queries.

This is custom documentation. For more information, please visit the SAP Help Portal 159
 7/16/2023
The query de nes the content of the noti cation list displayed.

Get a quick overview of all maintenance noti cations and view the most important information.

Navigate to single noti cations and assigned technical objects and process them.

Change the data of selected noti cations using the mass change function.

On a popup you can de ne which elds you want to change and which eld values should replace the current values.

Change the status of several selected noti cations.

You can choose from the statuses that are currently possible for at least one of the rows you selected.

View the date monitor symbols to quickly detect time issues and monitor the progress of the noti cations.

Assign one or more noti cations that have not yet been assigned to a maintenance order either to an existing order or
to a new order by creating one without leaving the list.

Print out the shop paper of the noti cation physically or virtually on the job card and transfer the noti cation to the job
list.

Personalize the table by choosing which table columns are shown and how table entries are sorted.

You can narrow down the scope of the noti cation list by using lters.

Process orders and their assigned noti cations in the combined Order and Noti cation List

Change the data of selected order operations, such as internal data, external data, and scheduling data, in the Order and
Operation List

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Noti cation (SAP_EAM_BC_NTF)

Related Apps
Process Maintenance Noti cation

Manage Orders and Noti cations in Information Center

Related Information
For more information about using the combined Order and Noti cation List list on the SAP Web user interface for Plant
Maintenance, see Order and Noti cation List.

Display Maintenance Order

Use
As a maintenance technician, you can use this app to view maintenance orders that have been created for a malfunction.
Maintenance orders describe in detail the maintenance tasks that are to be performed on the technical object and provide all

This is custom documentation. For more information, please visit the SAP Help Portal 160
 7/16/2023
the information needed to plan and execute maintenance work. This includes start and nish dates, location information,
planned materials and production resources/tools.

Key Features
If you have the business role Maintenance Technician, you can perform the following tasks:

Display the technical object that is assigned to the order.

Display assigned task lists and noti cations.

Display assigned documents at header level and operation level.

Display order operations and suboperations and view the work steps that need to be carried out. View dates, capacity
requirements, and costs of the maintenance work as well as the required materials and the date on which a particular
material should be available.

View system statuses and user statuses that document the progress of the repair work.

Open quickviews to get relevant information about maintenance documents, technical objects, materials and long texts
without having to navigate away from the screen you are working in.

View the nal due date for a maintenance order. If the nal due date was changed, then you can also view the previous
nal due date.

 Note
If you have the business role Maintenance Planner, you can also use this app as well as access the apps Create Maintenance
Order and Change Maintenance Order. For more information about processing a maintenance order, see Process
Maintenance Order.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Order MW (SAP_EAM_BC_ORD_MW)

Process Maintenance Order

Use
Three apps are provided for processing a maintenance order: Create Maintenance Order, Change Maintenance Order, and
Display Maintenance Order. As a maintenance planner, you can create and change orders when a malfunction is detected to
de ne in detail the maintenance tasks that are to be performed on the technical object. You can create a maintenance order for
a speci c noti cation or create the maintenance order directly with or without reference to an existing order. When creating or
changing a maintenance order, you can either assign existing task lists and noti cations or create new ones for the order.

In the maintenance order, you provide all the information needed to plan and execute the maintenance work. This includes start
and nish dates, location information, planned materials, and production resources/tools. The system supports you in nding
the relevant technical object, choosing the required materials and checking their availability, scheduling the job, and
determining the costs.

This is custom documentation. For more information, please visit the SAP Help Portal 161
 7/16/2023

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

Create a maintenance order directly or for a speci c noti cation.

Create a maintenance order using a template (or reference order) and use checkboxes to specify which data you want to
be copied from the reference order to the new order.

Assign existing task lists and noti cations to the order and open the task lists and noti cations that are assigned to the
order.

You can specify that the status of noti cations should depend on the status of the orders to which they are assigned.

Specify the technical object by using hierarchical structure lists that also provide you with information about assigned
materials and components.

Display, create, and assign documents at header level and operation level.

Create and change order operations and suboperations and explain the work steps that need to be carried out by
entering a short description. You can determine dates, capacity requirements, and costs of the maintenance work and
choose the required materials using a catalog.

Use the scheduling function to determine the actual execution dates, the capacity requirement needed to execute the
order, and the date on which a particular material should be available.

Determine costs and run cost simulations.

Use system statuses and user statuses to document the progress of the repair work and specify which activities the
system or users can carry out for an order or an operation.

For inspection rounds, enter technical objects and assemblies at operation level and assign measuring points as
production resources/tools to the technical objects.

Print out the shop paper of the maintenance order physically or virtually on the job card and by doing so, transfer the
order to the job list.

You can even allow shop papers to be printed for orders that have the status created or technically completed, for
example.

Manage print and email output details for output control of maintenance orders by specifying the required print queue
for outputs to be printed and providing email details for outputs to be sent by email. The Preview column provides the
option to preview the output only after a maintenance order is sent for output.

Add attachments to maintenance orders and provide attachment details such as document type, part, and version. You
can also add a description for the attachment.

Assign documents to a material or service at component level.

Open quick views to get relevant information about maintenance documents, technical objects, materials, and long texts
without having to navigate away from the screen you are working in.

View the nal due date of the maintenance order. When you create a maintenance order manually, the nal due date is
determined based on the priority of the maintenance order. When you select the priority for a maintenance order, the
nal due date is immediately determined and displayed. Once you have selected a priority and the nal due date has
been de ned, any additional change in priority will not result in a change of the nal due date.

You can change the nal due date directly by editing the eld only if you have authorization for the business transaction
LACD. If you edit the nal due date this way, then the previous nal due date is displayed for your reference.

If you create a maintenance order based on an existing maintenance noti cation, the nal due date from the
maintenance noti cation is copied into the maintenance order and is not redetermined even if the maintenance order

This is custom documentation. For more information, please visit the SAP Help Portal 162
 7/16/2023
was created days after the creation of the maintenance noti cation.

If the priority of the maintenance order is different from the priority of the maintenance noti cation from which it was
created, the priority of the maintenance noti cation is not inherited by the maintenance order. The nal due date is not
redetermined if the priority of the maintenance order is changed. If you change the nal due, the previous nal due date
is updated immediately even before you save the maintenance order. If you change the nal due date again, the last
changed nal due date is shown and not the original nal due date.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Order (SAP_EAM_BC_ORD)

Manage Order List

Use
As a maintenance planner, you can use this app to access a worklist of all the maintenance orders that match the selection
criteria in the query you have de ned. The order list contains the most important information on maintenance orders in the
form of a table and allows you to process orders and the assigned noti cations and technical objects directly. Furthermore, you
can carry out mass changes, and change the status of several selected orders. You can con gure the list layout, sort table
columns, and create lters. In addition, you have the option of displaying table columns for monitoring critical dates and costs,
whose colors help you detect issues.

With this app you can also access the Noti cation List, the combined Order and Noti cation List, and the Order and Operation
List.

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

Con gure the personal object worklist (POWL) by creating queries.

The query de nes the content of the order list displayed.

Get a quick overview of all maintenance orders and view the most important information in the form of a table.

Navigate to single orders and assigned noti cations or technical objects and process them.

Change the data of selected orders using the mass change function.

On a popup, you can de ne which elds you want to change and which eld values should replace the current values.

Change the status of several selected orders.

You can choose from the statuses that are currently possible for at least one of the rows you selected.

Display table columns for monitoring critical dates and costs, whose colors help you detect issues.

Print out the shop paper of the maintenance order physically or virtually on the job card and transfer the order to the job
list.

Personalize the table by choosing which table columns are shown and how table entries are sorted.
This is custom documentation. For more information, please visit the SAP Help Portal 163
 7/16/2023
You can narrow down the scope of the order list by using lters.

Process orders and their assigned noti cations in the combined Order and Noti cation List.

Change the data of selected order operations, such as internal data, external data, and scheduling data, in the Order and
Operation List.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Order (SAP_EAM_BC_ORD)

Related Apps
Process Maintenance Order

Manage Orders and Noti cations in Information Center

Related Information
For more information about using the combined Order and Noti cation List list on the SAP Web user interface for Plant
Maintenance, see Order and Noti cation List.

Manage Orders and Noti cations in Information Center

Use
As a maintenance planner, you can use this app to process your maintenance orders and noti cations by using a worklist that
you can con gure to suit your requirements (POWL).

Key Features
If you have the business role Maintenance Planner, you can perform the following tasks:

Use the SAP NetWeaver Enterprise Search to search for maintenance orders and/or noti cations.

Call orders and noti cations that you have saved as favorites or have recently processed.

Access the Order List, the Noti cation List, the Order and Noti cation List, and the Order and Operation List.

The personal object worklists (POWL) contain the most important information on maintenance noti cations and orders
in the form of a table and allow you to process noti cations, orders and the assigned technical objects directly.
Furthermore, you can carry out mass changes and assign one or more noti cations to a speci c order. You can con gure
the list layout, sort table columns and create lters. In addition, you have the option of displaying a table column for
monitoring critical dates, whose colors help you detect issues.

Call and process individual maintenance noti cations and orders.

Supported Device Types

This is custom documentation. For more information, please visit the SAP Help Portal 164
 7/16/2023
Desktop

Relevant Business Catalog

EAM - Information Center (SAP_EAM_BC_INFO)

Related Apps
Manage Order List

Manage Noti cation List

Process Maintenance Order

Process Maintenance Noti cation

Related Information
For more information about using the Order and Noti cation Information Center on the SAP Web user interface for Plant
Maintenance, see Order and Noti cation Information Center.

Display Job List

Use
As a maintenance technician, you can use this app to access a list of maintenance jobs to be carried out. A maintenance job is a
view of the order or noti cation (the reference object) that provides the technician or a team of technicians with information on
all their assigned operations or tasks. This app lists your jobs and provides crucial information for each job at a glance, such as
the urgency, start and end dates, and assigned work center. You can con gure job lists so that they re ect how work is
organized in your particular organization and therefore only contain the jobs that are relevant to you.

Key Features
If you have the business role Maintenance Technician, you can perform the following tasks:

Get a quick overview of all maintenance jobs assigned to you or your team and view the most important information.

Access additional information on a selected job, such as the reference document on which the job is based and a list of
objects associated with the reference document at header level including technical objects, materials, and documents.

Display the job card for a selected job.

The job card is a printable PDF document that provides you with all the information you need to perform a job: what you
have to do (operations and tasks), where you have to do it, and so on. The job card contains the data of existing shop
papers such as operation control ticket, time ticket, and pick list.

Reassign the whole job or single work items in the job to another person responsible or to a combination of work center
and person responsible.

The person and work center responsible for a job are determined from the reference document. If the job has not been
assigned to a person or work center yet, you can also assign the job for the rst time.

Supported Device Types

This is custom documentation. For more information, please visit the SAP Help Portal 165
 7/16/2023
Desktop

Relevant Business Catalog

EAM - Job MW (SAP_EAM_BC_JOB_MW)

Related Apps
Con rm Jobs

Con rm Jobs

Use
As a maintenance technician, you can use this app to con rm planned and unplanned maintenance jobs. A maintenance job is a
view of the order or noti cation (as reference object) that provides the technician or a team of technicians with information on
all their assigned operations or tasks. Con rmation lists contain all the planned maintenance jobs that can be con rmed. You
can check the planned job data and con rm or adjust it. This includes the time you spent on the job and the materials you
consumed as well as the activities you performed and the measurement readings. Depending on how con rmation is handled in
your company, you can con gure different con rmation lists.

You can also con rm unplanned jobs and enter all the required data after having nished your work. You then can enter the time
spent and the required materials, write a long text and, if necessary, create an activity report. The system automatically creates
an order and - if an activity report exists - a noti cation, sets the order and noti cation to technically completed, stores the
time con rmation, and posts a goods issue for the order. You can also con rm unplanned jobs while working in the Asset Viewer.

Key Features
If you have the business role Maintenance Technician, you can perform the following tasks:

Con rm one or several jobs as planned.

In this case, the planned data is copied as actual data that you simply have to con rm. The operations or tasks that
belong to the con rmed job are then con rmed with the planned data and materials.

Change the proposed job data of planned maintenance work or add data to the job and then con rm it.

Enter con rmation data for each operation if the reference document is a maintenance order.

If several maintenance workers were involved in a job, each of these maintenance workers can select the job in the
con rmation list and enter data until all the operations are nally con rmed. Con rmation data includes time
information, such as when the repair work was done and how long it took, as well as the quantities of which materials you
used. Furthermore, you can enter the results of measurements and counter readings. If the order references a linear
asset, you can also enter linear data.

Enter malfunction data retroactively for an unplanned job.

You add malfunction data in order to record a problem that was discovered during preventive maintenance. You can
enter breakdown data, as well as information about damages and causes to describe the problem or malfunction in
greater detail.

Use long texts and comments or upload and attach documents to describe the repair work in detail.

By con rming a maintenance job trigger a con rmation as well as a goods issue in the back-end system.

This is custom documentation. For more information, please visit the SAP Help Portal 166
 7/16/2023
This means that the system statuses are updated and the system creates all the necessary documents, such as goods
movements and measurement documents. If there are any errors, you can view the error logs and post-process the
goods movements using the transaction COGI.

Supported Device Types

Desktop

Relevant Business Catalog

EAM - Job MW (SAP_EAM_BC_JOB_MW)

Related Apps
Display Job List

Create Time Con rmations

With this app, you can view status of time con rmations and post them.

This app can be launched only when you upload time con rmations in the Find Maintenance Orders and Operations app. For
more information, see Find Maintenance Orders and Operations.

Key Features
View status of uploaded time con rmations.

Post time con rmations into the system.

Additional Details
When you upload time con rmations in the Find Maintenance Orders and Operations app, you are taken to the Create Time
Con rmations app. For more information, see Find Maintenance Orders and Operations.

In the Create Time Con rmations app, you can view the uploaded time con rmations. The status of each time con rmation
may be Ready or Errors.

The time con rmations in the Ready tab are validated and are ready to be posted. The time con rmations in the Preprocessing
Errors tab are validated and have errors. If there are multiple errors, you can view them in a popup. You can optionally correct
these errors outside the app and trigger revalidation. Choose Check to revalidate the time con rmations. If there are no errors,
the time con rmations move to the Ready tab.

You can choose Close to discard all drafts in the Preprocessing Errors tab. Choose Cancel to discard time con rmations and
return to the Find Maintenance Orders and Operation app.

After posting the time con rmations, you can view the posted time con rmations in Posted tab. If any postprocessing errors
occur due to actual cost posting, the entire posting is terminated. The record along with the error details are viewed in the
Postprocessing Errors tab. You can resolve the errors and again post the time con rmations.

 Example

This is custom documentation. For more information, please visit the SAP Help Portal 167
 7/16/2023
Postprocessing errors can occur if a nancial period is not open for posting, incorrect activity type is entered while posting
and so on.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
Find Maintenance Orders and Operations

SAP Apps for Finding Technical Objects and Maintenance

Execution Data

Find Technical Object

Use
With this app, you can list the technical objects in your system. You can nd the one you need by ltering the list according to
various properties or by using a free-text search. You can display a single technical object to view its properties, its assigned
noti cation and operations, and its attachments.

Key Features
List technical objects

Filter technical objects by various parameters, such as type, location, manufacturer, and status

Search for technical objects

Display a single technical object

Show details of the related noti cations and orders

Display general information about the technical order, such as long text, category, and manufacturer

Display installation information about the technical object, such as location, plant, and plant section

Display the responsible planning plant, planner group, and work center of the technical object

Display the company code, business area, asset, cost center and WBS element of the technical object

Display the system and user statuses of the technical object

Display the noti cations, orders, and maintenance items of the technical object

Display the measurement documents, and measuring points of the technical object, and navigate to them

List the attachments of the technical object

In addition, this app supports the following technical features and options:
This is custom documentation. For more information, please visit the SAP Help Portal 168
 7/16/2023
If the long material number has been activated in your back-end system, it is automatically displayed in the Material eld in this
SAP Fiori app. For more information, see Extended Material Number in SAP Fiori Apps.

Supported Device Types

Desktop

Tablet

Smartphone

Relevant Business Catalog

EAM - Technical Object

App Extensibility: Find Technical Object

As a key user, you can extend the Find Technical Object app according to your business needs.

Features
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Equipment (EAMS_EQUI) Fiori Find Technical Object Any Object Page Section
Item Details Page Adapt UI
General Information tab

Equipment (EAMS_EQUI) Fiori Find Technical Object Any Object Page Section
Item Details Page Adapt UI
Status tab

Functional Location (EAMS_FL) Fiori Find Technical Object Any Object Page Section
Item Details Page Adapt UI
General Information tab

Functional Location (EAMS_FL) Fiori Find Technical Object Any Object Page Section
Item Details Page Adapt UI
Status tab

Equipment (EAMS_EQUI) Fiori Find Technical Object List Report Filters

Adapt Filters

Equipment (EAMS_EQUI) Fiori Find Technical Object Table List Report View Settings
Toolbar Settings

Functional Location (EAMS_FL) Fiori Find Technical Object List Report Filters
Adapt Filters

Functional Location (EAMS_FL) Fiori Find Technical Object Table List Report View Settings
Toolbar Settings

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 169
 7/16/2023
Custom elds appropriate for Equipment (EAMS_EQUI) and Functional Location (EAMS_FL) business context can be added
to the lter bar.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Business Context Business Use

Field Control for Technical Object Equipment (EAMS_EQUI) Change the properties of technical object
header elds without changing the standard
(EAM_TECHNOBJECT_FIELD_CONTROL) Functional Location (EAMS_FL) logic

For more information, see:

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic
app: Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI
Documentation.

Find Maintenance Noti cation

Use
With this app, you can list the maintenance noti cations in your system and nd the one you need. You can do this by ltering
the list according to various properties or by using a free-text search. You can perform prede ned quick actions on one or more
noti cations. You can display a single noti cation to view its properties, its assigned technical object and maintenance order,
and its attachments.

Key Features
View the list of all maintenance noti cations

Search for maintenance noti cations by various parameters, such as type, priority, dates, equipment, functional location,
and so on.

Export the search result tables into a spreadsheet le

Assign a maintenance noti cation or several noti cations to an existing maintenance order

Create a maintenance order for one noti cation or combine several noti cations in one maintenance order

Select either the status, scheduling or responsibilities for a noti cation to edit a single noti cation or edit several
noti cations at once

Apply a mass change of noti cations to edit multiple parameters at once such as general data, technical object,
malfunction details, or custom elds, if any, and simulate the changes to identify errors in the application log

Generate output items using the Determine Output Items quick action button on the noti cation object page. If output
items aren't yet available for a maintenance noti cation, 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 noti cation. Once the output is sent, it moves to the status To be Output and then to
Completed when it is nally 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.

Display the change log of the maintenance noti cation.

This is custom documentation. For more information, please visit the SAP Help Portal 170
 7/16/2023
Display the detailed information about the maintenance noti cation, including the malfunction information, completion
date and time, tasks, activities, maintenance plan and item, and so on.

View the nal due date for a maintenance noti cation. If the nal due date was changed, then you can also view the
previous nal due date.

Additional Information
This app is a variant of the app Display Maintenance Noti cations (F5797) which does not allow you to update noti cation or
perform any action. For more information, see Feature Comparison for Maintenance Noti cation Apps.

Supported Device Types

Desktop

Tablet

Smartphone

Related Information
Feature Comparison for Maintenance Noti cation Apps

Mass Editing of Noti cations

In the Find Maintenance Noti cation app, you can edit multiple noti cations at a time.

Context
As a maintenance planner or a maintenance supervisor, you can change the parameters such as general data, due dates,
breakdown details and responsibilities for multiple noti cations at once. Using a simulation option, you can check the
correctness of data in the application log.

Procedure
1. In the list report, select at least two noti cations that you would like to edit.

2. Choose Mass Edit Noti cations. In the dialog box, you can change the following parameters for all selected noti cations:

General Data, such as maintenance code, maintenance activity type, location, plant section and other data

Reference Object: technical object

Deadline data, such as priority and due dates

Breakdown, for example, malfunction start and end, effect, other details

Responsibilities, for example, person responsible, main work center and so on

 Note
Any custom elds you have created will also be available for mass editing in the relevant section of the dialog window.

You can set, overwrite and clear eld values, or, when applicable, enter them manually. Depending on speci c parameter,
the following options may be available in the dropdown list:

<leave blank>: allows you to leave the eld empty for all selected noti cations

This is custom documentation. For more information, please visit the SAP Help Portal 171
 7/16/2023
<keep existing values>: enables you to keep predetermined values for all selected noti cations

<value help>: allows you to choose values from a prede ned list

Pre-existing data: allows to apply pre-existing values from the chosen noti cations

3. Select Simulate to check the corectness of entered data without saving changes. In the dialog box, you can enter a name
of the new Mass Change Job or keep a default name that is the combination of the object name, username and the date
and time.

In the Application Logs, you can check the job for potential error and, if needed, to view the history of previous mass
change jobs.

4. Select Schedule to proceed with saving of changes. You can enter the name of the job or leave it as de ned by the
system.

5. Select Apply to apply your changes.

App Extensibility: Find Maintenance Noti cation

As a key user, you can extend the Find Maintenance Noti cation app according to your business needs.

Features
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

EAMS_NTF Fiori Find Maintenance Object Page Section

Noti cation Any Item
Details Page Adapt UI
General tab

EAMS_NTF Fiori Find Maintenance Object Page Section

Noti cation Any Item
Details Page Adapt UI
Scheduling tab

EAMS_NTF Fiori Find Maintenance Object Page Section

Noti cation Any Item
Details Page Adapt UI
Malfunction Information tab

EAMS_NTF Fiori Find Maintenance Object Page Section

Noti cation Any Item
Details Page Adapt UI
Maintenance Plan and Item
tab

EAMS_NTF Fiori Find Maintenance Object Page Section

Noti cation Any Item
Details Page Adapt UI
User Status with Number tab

EAMS_NTF Fiori Find Maintenance List Report Filters

Noti cation Adapt lters

This is custom documentation. For more information, please visit the SAP Help Portal 172
 7/16/2023

Business Context UI Technology Navigation Path UI Element Type

EAMS_NTF Fiori Find Maintenance List Report View Settings

Noti cation Table toolbar
Settings

 Note
Custom elds appropriate for Noti cation (EAMS_NTF) business context can be added to the lter bar.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Maintenance Noti cation Noti cation (EAMS_NTF) Change the properties of the noti cation
header elds without changing the standard
(EAM_NOTIFICATION_FIELD_CONTROL)
logic

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

Find Maintenance Orders

With this app, you can display a list of maintenance orders and perform different mass changes, such as changing the
responsibility, the status, and the scheduling of the selected maintenance orders. You can also assign the orders to a
maintenance event and dispatch all their operations.

Key Features
You can use this app to do the following:

Search and display maintenance orders by using free text search or by ltering for parameters such as type, priority,
dates, and statuses.

Filter the maintenance orders to display all the orders that still have operations or suboperations with the execution
stage MAIN assigned to them and that have not been completed. For more information, see Has Open Main Work.

Select one or more maintenance orders and change the responsibility, such as the person responsible or the main work
center.

Select one or more maintenance orders and change the order status. You can, for example, release the selected orders,
complete them from a technical and business perspective, block further processing, or mark orders for deletion.
Additional status changes are available for orders that are processed by phases. You can also cancel certain order
statuses.

Select several maintenance orders and create a work pack using the Create Work Pack quick action button. When
creating the work pack you can choose the work pack type and grouping criteria and decide whether you want to include
operations that are already included in other work packs. For more information, see Create Work Pack.

This is custom documentation. For more information, please visit the SAP Help Portal 173
 7/16/2023
Select one or more maintenance orders and set, overwrite or clear the values of the scheduling-related elds, such as
the priority, the required start date, and the required end date.

Assign one or more maintenance orders to a maintenance event using the Change Scheduling quick action. You can also
unassign maintenance orders from a maintenance event. For more information, see Maintenance Events.

Select one or more maintenance orders and dispatch all their operations at once.

Show the detailed information about the maintenance order, such as long text, work center, operations, organizational
data, related noti cations, etc.

Show the estimated, planned, and actual costs for the order for each value category

View the nal due date for a maintenance order. If the nal due date was changed, then you can also view the previous
nal due date.

List the attachments of the maintenance order.

Display the change log of the maintenance order.

In addition, this app supports the following technical features and options:

If the long material number has been activated in your back-end system, it is automatically displayed in the Material eld in this
SAP Fiori app. For more information, see Extended Material Number in SAP Fiori Apps.

Supported Device Types

Desktop

Tablet

Smartphone

Relevant Business Catalog

EAM - Order

App Extensibility: Find Maintenance Orders

As a key user, you can extend the Find Maintenance Orders app according to your business needs.

Custom Fields
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Order (EAMS_ORD) Fiori Find Maintenance Orders Object Page Section

Any Item Details Page
Adapt UI General tab

Order (EAMS_ORD) Fiori Find Maintenance Orders Object Page Section

Any Item Details Page
Adapt UI Scheduling tab

This is custom documentation. For more information, please visit the SAP Help Portal 174
 7/16/2023

Business Context UI Technology Navigation Path UI Element Type

Order (EAMS_ORD) Fiori Find Maintenance Orders Object Page Section

Any Item Details Page
Adapt UI Malfunction
Information tab

Order (EAMS_ORD) Fiori Find Maintenance Orders Object Page Section

Any Item Details Page
Adapt UI Maintenance Plan
and Item tab

Order (EAMS_ORD) Fiori Find Maintenance Orders Object Page Section

Any Item Details Page
Adapt UI User Status with
Number tab

Order (EAMS_ORD) Fiori Find Maintenance Orders List Report Filters

Adapt Filters

Order (EAMS_ORD) Fiori Find Maintenance Orders List Report View Settings
Table Toolbar Settings

 Note
Custom elds appropriate for Order (EAMS_ORD) business context can be added to the lter bar.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Maintenance Order Order (EAMS_ORD) Change the properties of order header
elds without changing the standard logic
(EAM_ORDER_FIELD_CONTROL)

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

Find Maintenance Orders and Operations

With this app, you can display a list of maintenance orders and their operations. You can perform mass changes of different
operation parameters, add and display time con rmations, and create work packs for selected operations.

Key Features
You can use this app to do the following:

Search and display maintenance orders and their operations by using free text search or by ltering for parameters,
such as type, priority, dates, and statuses.

Filter order operations according to their execution stage and thereby group operations that describe a preliminary task,
a main repair and maintenance task or a post execution activity. For more information, see Assigning Execution Stages.

This is custom documentation. For more information, please visit the SAP Help Portal 175
 7/16/2023
Display quick views with details of the maintenance order or the related technical object.

Navigate to the order, or to the technical object of the order.

Display the amount of work needed for the listed operations.

View the nal due date for a maintenance order. If the nal due date was changed, then you can also view the previous
nal due date.

List the attachments of a maintenance order.

Select one or more order operations and change the work center, the work center plant, and the person responsible to
which these order operations are assigned.

Add individual time con rmations.

View time con rmations for an order and operation.

Download a template to record collective time con rmations.

 Note
We recommend that you use this template to avoid errors while uploading time con rmations. Do not change the
template by deleting or reordering columns or by changing the format of the cell. The system reads time
con rmations until it encounters the rst blank row in the spreadsheet.

Verify and upload collective time con rmations.

 Note
We recommend that you post the time con rmations as a background job. You need to select the Post Immediately
check box for posting as a background job.

Only 100 entries must be uploaded if you want to post immediately.

The uploaded time con rmations are available in the Create Time Con rmations app where you can post them. For
more information, see Create Time Con rmations.

Upload collective time con rmations as background jobs by selecting the Post Immediately checkbox. Choose the
application log ID to view details.

Select one or more order operations and change the status of the corresponding orders. You can, for example, release
the selected orders, complete them from a technical and business perspective, block further processing, or mark orders
for deletion. Additional status changes are available for orders that are processed by phases. You can also cancel certain
order statuses.

Create a work pack including one or more selected operations, choose work pack type and grouping criteria. For more
information, see Create Work Pack.

Select one or more operations and mass-edit several attributes by means of a quick action. You can run a simulation to
test the data, or apply the mass change directly in the system. You can view the details of the simulated or scheduled job
in the Application Logs. For more information, see Mass Editing of Operations.

Export the search result table and the tables of the maintenance order operation to downloadable spreadsheet les.

Supported Device Types

Desktop

Tablet

This is custom documentation. For more information, please visit the SAP Help Portal 176
 7/16/2023
Smartphone

Relevant Business Catalog

EAM - Order

App Extensibility: Find Maintenance Orders and Operations

As a key user, you can extend the Find Maintenance Orders and Operations app according to your business needs.

Custom Fields
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Order (EAMS_ORD) Fiori Find Maintenance Orders Object Page Section

and Operations Any item
Detail Page Adapt UI
General Information tab

Order (EAMS_ORD) Fiori Find Maintenance Orders Object Page Section

and Operations Any item
Detail Page Adapt UI
External Data tab

Order (EAMS_ORD) Fiori Find Maintenance Orders Object Page Section

and Operations Any item
Detail Page Adapt UI
Planned Dates and Times tab

Order (EAMS_ORD) Fiori Find Maintenance Orders Object Page Section

and Operations Any item
Detail Page Adapt UI
Status tab

 Note
Custom elds appropriate for Order (EAMS_ORD) business context can be added to the lter bar.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Maintenance Order Order (EAMS_ORD) Change the properties of order header
elds without changing the standard logic
(EAM_ORDER_FIELD_CONTROL)

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation
This is custom documentation. For more information, please visit the SAP Help Portal 177
 7/16/2023

Mass Editing of Operations

In the Find Maintenance Orders and Operations app, you can select one or more maintenance orders and edit their operations
at a single time.

Context
You can select one or more operations from the list report and change the general data, internal data, and external data of
these operations.

Procedure
1. On the initial screen of the app, select one or more maintenance order operations that you would like to edit.

2. Choose Edit Operations. In the new window, you can change the following parameters for all selected objects:

Section Change/Add

General Data Assembly, operation control key, operation functional location,

and operation description

Internal Data Operation work center and operation work center plant

External Data Operation quantity, goods recipient, price, tracking number,

requisitioner, supplier, and unloading point.

 Note
You can set, overwrite and clear eld values, or, when applicable, enter them manually. Depending on the speci c
parameter, the following options may be available in the drop down list:

<leave blank>: allows you to leave the eld empty for all selected objects

<keep existing values>: use it to keep the existing values for your selected objects

<value help>: you can choose the value from the list of pre-de ned values

Pre-existing data: apply values of one of the selected object to all selected objects

3. Choose Simulate to check the data for correctness without saving your changes, or choose Save to proceed with saving
your changes to the database. In both cases, you can enter a job description or keep the default description suggested
by the system.

4. You can view the details of the simulated or scheduled job in the Application Logs.

Find Maintenance Order Con rmation

Use
With this app, you can list the maintenance order con rmations in your system. You can nd the one you need by ltering the list
according to various properties or by using a free-text search. You can display a single order con rmation to view its properties
and its assigned order and technical object.

Key Features

This is custom documentation. For more information, please visit the SAP Help Portal 178
 7/16/2023
List maintenance order con rmations

Filter order con rmations by various parameters, such as order status, operation number, and dates

Search for order con rmations

Display a single order con rmation

Navigate to the con rmed order

Display general information, such as long text, con rmation text, and work center

Display the actual start and end dates, and cumulative actual work amount

Supported Device Types

Desktop

Tablet

Smartphone

Relevant Business Catalog

EAM - Order

App Extensibility: Find Maintenance Order Con rmation

As a key user, you can extend the Find Maintenance Order Con rmation app according to your business needs.

Custom Fields
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Order (EAMS_ORD) Fiori Find Maintenance Order Object Page Section

Con rmation Any item
Detail Page Adapt UI
Con rmation Data tab

Order (EAMS_ORD) Fiori Find Maintenance Order Object Page Section

Con rmation Any item
Detail Page Adapt UI Total
Con rmation Data

 Note
Custom elds appropriate for Order (EAMS_ORD) business context can be added to the lter bar.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following

This is custom documentation. For more information, please visit the SAP Help Portal 179
 7/16/2023
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Maintenance Order Order (EAMS_ORD) Change the properties of order header
elds without changing the standard logic
(EAM_ORDER_FIELD_CONTROL)

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

Find Maintenance Task List

With this app, you can nd and display the following maintenance task lists:

Equipment task list

Functional location task list

General maintenance task list

You can do this either by ltering the list or by using the free text search. You can display a single task list to view its properties,
its assigned operations, and its attachments.

 Note
You cannot access hierarchical task lists from this application.

Key Features
Display maintenance task lists by using the free text search or by ltering for parameters, such as Planning Plant, Work
Center, and Key Date

Display a single maintenance task list

Show general information about the maintenance task list, such as Long Text and Work Center

Show the details of the related operations

Show the operations and suboperations of the maintenance task list

List the maintenance packages of the maintenance task list

List the attachments of the maintenance task list

Supported Device Types

Desktop

Tablet

Smartphone

Find Maintenance Task List and Operation

This is custom documentation. For more information, please visit the SAP Help Portal 180
 7/16/2023
With this app, you can nd and display the following maintenance task lists and their operations:

Equipment task list

Functional location task list

General maintenance task list

You can do this either by ltering the list or by using the free text search. You can display a single task list to view its properties,
its assigned operations, and its attachments.

 Note
You cannot access hierarchical task lists from this application.

Key Features
Display maintenance task lists by using the free text search or by ltering for parameters, such as Planning Plant, Work
Center, and Key Date

Filter operations according to their execution stage and thereby group operations that describe a preliminary task, a
main repair and maintenance task or a post execution activity

List operations by using free-text search in the Operation eld or by ltering for various parameters, such as Operation
Description, Work Center, and Activity Type

Display a single maintenance task list

Show general information about the maintenance task list, such as Long Text and Work Center

Show the details of the related operations

Show the operations and suboperations of the maintenance task list

List the maintenance packages of the maintenance task list

List the attachments of the maintenance task list

Supported Device Types

Desktop

Tablet

Smartphone

Find Maintenance Plans

With this app, you can nd and display maintenance plans. You can do this either by ltering the list or by using a free text
search. You can display a single maintenance plan to view its properties, its assigned maintenance items, and its scheduled and
manual maintenance calls.

Key Features
You can use this app to:

This is custom documentation. For more information, please visit the SAP Help Portal 181
 7/16/2023
View maintenance plans by using the free text search or by ltering for parameters.

 Note
The maintenance plans that belong to the category Stability Study will not be displayed here. To view these
maintenance plans, use the transaction QST08.

View details of a maintenance plan.

Export the maintenance plans visible in the table to a spreadsheet.

Choose a maintenance plan to access the quick view and navigate to speci c apps to perform additional tasks.

View validity data of the respective maintenance plans

Supported Device Types

Desktop

Tablet

Smartphone

App Extensibility: Find Maintenance Plans

As a key user, you can extend the Find Maintenance Plans app according to your business needs.

Custom Fields
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Maintenance Plan Fiori Find Maintenance Plans Object Page Section

(EAMS_MPLA) Any Item Detail page
Adapt UI Basic Data tab

Maintenance Plan Fiori Find Maintenance Plans Object Page Section

(EAMS_MPLA) Any Item Detail page
Adapt UI Planning Data tab

 Note
Custom elds appropriate for Maintenance Plan (EAMS_MPLA) business context can be added to the lter bar.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

This is custom documentation. For more information, please visit the SAP Help Portal 182
 7/16/2023

BAdI Name Business Context Business Use

Field Control for Maintenance Plan Maintenance Plan (EAMS_MPLA) Change the properties of maintenance plan
header elds without changing the standard
(EAM_MAINT_PLAN_FIELD_CONTROL)
logic

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

Find Maintenance Items

With this app, you can nd and display maintenance items. You can do this either by ltering the list or by using a free text
search. You can display a single maintenance item and view its properties.

Key Features
You can use this app to:

View maintenance items by using the free text search or by ltering for parameters.

View maintenance items by ltering based on the system condition.

View details of a maintenance item.

Export the maintenance items visible in the table to a spreadsheet.

Display quick views with details of the maintenance plan or the related technical object.

Choose a maintenance item to access the quick view and navigate to speci c apps to perform additional tasks.

Supported Device Types

Desktop

Tablet

Smartphone

App Extensibility: Find Maintenance Items

As a key user, you can extend the Find Maintenance Items app according to your business needs.

Custom Fields
With the Custom Fields tab in the Custom Fields and Logic app, you can create and maintain custom elds that you can use to
enhance applications. You can add elds to the following UI elements using key user adaptation:

Business Context UI Technology Navigation Path UI Element Type

Maintenance Item Fiori Find Maintenance Items Object Page Section

(EAMS_MPOS) Any Item Detail page
Adapt UI Basic Data tab

This is custom documentation. For more information, please visit the SAP Help Portal 183
 7/16/2023

Business Context UI Technology Navigation Path UI Element Type

Maintenance Item Fiori Find Maintenance Items Object Page Section

(EAMS_MPOS) Any Item Detail page
Adapt UI Location tab

 Note
Custom elds appropriate for Maintenance Item (EAMS_MPOS) business context can be added to the lter bar.

Custom Logic
With the Custom Logic tab in the Custom Fields and Logic app, you can create and maintain implementations of custom logic
that can be used to enhance applications and change application behavior. You can implement custom logic for the following
Business Add-Ins (BAdIs):

BAdI Name Business Context Business Use

Field Control for Maintenance Item Maintenance Item (EAMS_MPOS) Change the properties of maintenance item
header elds without changing the standard
(EAM_MAINT_ITEM_FIELD_CONTROL)
logic

For more information about the individual BAdIs, check the BAdI-speci c documentation in the Custom Fields and Logic app:
Custom Fields and Logic Custom Logic <your implementation > BAdI Documentation View BAdI Documentation

SAP Apps for Permit to Work

Create Work Permit Request

App ID: F4691

With this app, you can create a new work permit with reference to an existing maintenance order, a predesigned work permit
template, or independently. You can assign additional information such as technical objects, additional orders and operations,
partners, nature of work items, safety precautions, personal protective equipment items, and so on to enhance the work permit
with details related to the work activity and the safety procedures. You can also add approval types to assign authorized
approvers for the approval process.

Key Features
This app provides the following key features:

Enables permit requestors and maintenance planners to create and manage safety work permits

Supports the creation of work permits with reference to a maintenance order and/or a work permit template and
independently

Allows the con guration of the nature of work, personal protective equipment, and safety precautions as integral
components of the work permit solution

Provides the ability to assign multiple functional locations, equipment, and maintenance orders to the work permit

Offers easy data validation and a simpli ed approval process that adheres to a four-eyes principle

Supports the printing of work permit in the output form maintained by the user

This is custom documentation. For more information, please visit the SAP Help Portal 184
 7/16/2023
In addition, the app supports the following technical features and options:

Attachment Service

Application Logs

Supported Device Types

Desktop

Tablet

Relevant Business Catalog

SAP_WCM_BC_PTW (business role: Maintenance Planner)

Related Apps
Manage Work Permits

Manage Work Permit Templates

Related Information
For more information about creating work permits, see Permit to Work.

Manage Work Permits

App ID: F6579

With this app, you can create new permits or manage the existing work permits that are active, non-active, or closed in the
system. New work permits can be created with reference to an existing maintenance order, a predesigned work permit
template, or independently. Once the work permit has been created, you can enhance the record with additional details related
to the work activity and the safety requirements.

Key Features
This app provides the following key features:

Enables permit requestors and maintenance planners to create and manage safety work permits

Supports the creation of work permits with reference to a maintenance order and/or a work permit template and
independently

Allows the con guration of the nature of work, personal protective equipment, and safety precautions as integral
components of the work permit solution

Provides the ability to assign multiple functional locations, equipment, and maintenance orders to the work permit

Offers easy data validation and a simpli ed approval process that adheres to a four-eyes principle

Supports the printing of work permit in the output form maintained by the user

In addition, the app supports the following technical features and options:

This is custom documentation. For more information, please visit the SAP Help Portal 185
 7/16/2023
Attachment Service

Application Logs

Supported Device Types

Desktop

Tablet

Relevant Business Catalog

SAP_WCM_BC_PTW

Related Apps
Create Work Permit Request

Manage Work Permit Templates

Related Information
For more information about creating work permits, see Permit to Work.

Manage Work Permit Templates

App ID: F4692

With this app, you can create new work permit templates or manage the existing templates that are active, non-active, or
closed in the system. Once the work permit template has been created, you can enhance the record with additional details
related to the work activity and the safety requirements. A partially approved or a fully approved template can be used as a
reference template in the Manage Work Permits and the Create Work Permit Request apps to generate work permits in a
consistent format.

Key Features
This app provides the following key features:

Enables permit requestors and maintenance planners to create and manage safety work permit templates

Allows the con guration of the nature of work, personal protective equipment, and safety precautions as integral
components of the work permit template

Provides the ability to assign multiple functional locations, equipment, and maintenance orders to the work permit
template

Offers easy data validation and a simpli ed approval process that adheres to a four-eyes principle

Enables the use of a partially approved and a fully approved work permit template in the creation of work permits

In addition, the app supports the following technical features and options:

Attachment Service

Application Logs

This is custom documentation. For more information, please visit the SAP Help Portal 186
 7/16/2023

Supported Device Types

Desktop

Tablet

Relevant Business Catalog

SAP_WCM_BC_PTW (business roles: Maintenance Planner, Industrial Hygienist, Plant Manager)

Related Apps
Create Work Permit Request

Manage Work Permits

Related Information
For more information about creating work permit templates, see Permit to Work.

Phase-Based Maintenance Process

This comprehensive phase-based process supports you in the maintenance of technical objects. Maintenance requests and
orders are processed according to nine phases.

 Note
The phase-based maintenance process 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). This means that you can only process your maintenance orders
according to phases if the scope items Reactive Maintenance and Proactive Maintenance are active or if you have
con gured the phase model in Customizing the same way as it is delivered for these scope items.

The phase-based maintenance process supports the order types Reactive Maintenance and Proactive Maintenance . The order
type determines the process phases that the maintenance order runs through. For more information about the supported order
types, see

Reactive Maintenance

Overview: Reactive Maintenance Process

Proactive Maintenance

Assigning a processing context to a maintenance order allows you to modify the end-to-end process how it is determined by the
order type. For more information, see

Processing Contexts

Reactive Maintenance: Emergency Work

If you create maintenance requests and maintenance orders of the Reactive Maintenance or the Proactive Maintenance order
type, these maintenance requests and orders are processed according to phases. For more details about the individual process
phases, see Maintenance Process Phases.

This is custom documentation. For more information, please visit the SAP Help Portal 187
 7/16/2023
To ensure the maximum bene t out of the monitoring options that the phase model offers, you need to organize the necessary
maintenance work in a speci c way. Only then the phases and subphases support you in monitoring the performance of
individual maintenance tasks. For more information, see Representing Work in Maintenance Orders.

The phase model also offers features for monitoring the procurement status of non-stock components and external services.
For more information, see Monitoring Procurement Activities.

Maintenance Order Types

The maintenance process supports the following order types:

Reactive Maintenance: The process that involves this order type allows you to perform maintenance of technical objects
whenever a breakdown or a failure occurs. This process helps you reduce an asset’s downtime and increase productivity.
For more information, see Reactive Maintenance.

Proactive Maintenance: The process that involves this order type allows you to prevent the failure or breakdown of an
asset by implementing preventive maintenance and using proactive measures. This ensures that the assets are well
utilized and are available. It encourages optimal performance of assets and reduces cost by minimizing breakdowns. For
more information, see Proactive Maintenance.

Reactive Maintenance
When you create maintenance orders of the Reactive Maintenance order type, the end-to-end maintenance process is
structured according to the following nine phases:

Initiation

During this phase, you submit a maintenance request, view the details of all the maintenance requests you submitted
and prioritize maintenance events.

For more information, see Initiation.

Screening

During this phase, you can review the submitted maintenance requests and see whether the required information is
complete.

For more information, see Screening.

Planning

After the maintenance request has been accepted, you can start planning the resources for the maintenance order. This
order inherits the data of the accepted maintenance request.

For more information, see Planning.

Approval

During this phase, maintenance orders are approved by means of a exible work ow process.

For more information, see Approval.

Preparation

Once the order has been released, the maintenance planner divides the maintenance effort into manageable groups,
levels out the work load over several weeks, determines the concrete time period for the requested maintenance work
and checks the availability of all the required resources, spare parts and services.

This is custom documentation. For more information, please visit the SAP Help Portal 188
 7/16/2023
For more information, see Preparation.

Scheduling

During this phase the maintenance planner or scheduler dispatches the order operations and suboperations and thereby
con rms that they have been scheduled at the right work center and at the right time.

For more information, see Scheduling.

Execution

During this phase, the maintenance technician executes the preliminary and main maintenance tasks, captures time and
material consumption and con rms that the main work has been executed.

For more information, see Execution.

Post Execution

During this phase, the maintenance technician executes the nishing maintenance tasks and documents time and
material consumption.

For more information, see Post Execution.

Completion

During this phase, the maintenance planner or nancial controller reviews maintenance orders that have already been
technically completed but not yet nancially settled, performs all the necessary tasks and nally sets the orders to
Complete (Business).

For more information, see Completion.

To view and monitor all the maintenance orders belonging to a speci c phase or subphase, you can lter the maintenance order
list accordingly in the Find Maintenance Orders app. The phase and subphase is also displayed as a table column in several apps
such as in the Manage Maintenance Backlog app.

Overview: Reactive Maintenance Process

The following tables provide an overview of the phases, subphases and system statuses in the Reactive Maintenance process.

Initiation

During the Initiation phase, you can create maintenance requests for a technical object such as a piece of equipment or a
functional location. You enter all the necessary details, include attachments and links, prioritize the maintenance request and
nally submit it for screening.

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

You detect a failure at a You create a maintenance Noti cation Header: Submitted Noti cation Header:
technical object. request and submit it for (Request)
OSNO (Outstanding
screening.
Note that this subphase is Noti cation)
associated with the Screening
APRQ (Approval
phase.
Required)

This is custom documentation. For more information, please visit the SAP Help Portal 189
 7/16/2023

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The screener has reviewed the The screener evaluated the Noti cation Header: Action Noti cation Header:
submitted maintenance information that you provided Required (Request)
OSNO (Outstanding
requests. as insufficient. This is why the
Noti cation)
maintenance request has been
sent back to the Initiation AIRQ (Additional Info
phase. Required)

You receive a maintenance You add the necessary Noti cation Header:
OSNO (Outstanding
request in the Action Required information and resubmit the Resubmitted (Request)
Noti cation)
(Request) subphase. maintenance request.
Note that this subphase is
APRQ (Approval
associated with the Screening
Required)
phase.

The screener has reviewed the The screener has rejected the Noti cation Header: Rejected Noti cation Header:
submitted maintenance maintenance request that you (Request)
APRF
requests. created. As a result, the
(Approval:Refused)
maintenance request has been
sent back to the Initiation NOCO (Noti cation
phase. Completed)

Apps Relevant for the Initiation Phase

Business Transaction Apps

You want to create a maintenance request. Create Maintenance Request

You want to view the maintenance requests that you have My Maintenance Requests
submitted.

For more information about the Initiation phase, see Initiation.

Screening

During the Screening phase, you as a supervisor, review and accept or reject the submitted maintenance requests. You can also
edit information related to malfunction, responsibility, priority, and other details. If you require additional details to accept the
request, you can send the maintenance request back to the person who created it and thereby send it back to the Initiation
phase. The person who created the maintenance request can then add the required information and resubmit the maintenance
request for screening.

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

This is custom documentation. For more information, please visit the SAP Help Portal 190
 7/16/2023

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The maintenance request has As a supervisor, you review the Noti cation Header: Accepted Noti cation Header:
been created and submitted or submitted maintenance (Request)
APOK (Approval: OK)
resubmitted for screening. requests. If you evaluate the
information as sufficient, a NOPR (Noti cation in
maintenance order can be Process)
based on the maintenance
request.

Note: If you reject a

maintenance request or need
more details, the maintenance
request is sent back. For more
information, see the description
of the Initiation phase.

Apps Relevant for the Screening Phase

Business Transaction Apps

You want to screen the maintenance requests. Screen Maintenance Requests

For more information about the Screening phase, see Screening.

Planning

After the maintenance request has been accepted, the maintenance planner can start planning the resources for the
maintenance order.

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

Mandatory: Accepted You create a maintenance order Noti cation Header: Order Order Header:
Noti cation of the Reactive Maintenance Assigned (Request)
CRTD (Created)
order type based on an
Order Header: In Planning
accepted noti cation.
(Order) If you have con gured
The maintenance order inherits your system
the most important data of the All Order Operations: In accordingly, the
accepted noti cation. Planning following system status
is set in addition: ORAR
All Order Suboperations: In
(Order Approval
Planning
Required)

Order Operations: CRTD

(Created)

Order Suboperations: CRTD

(Created)

Apps Relevant for the Planning Phase

Business Transaction Apps

You want to create a maintenance order for one or more Manage Maintenance Noti cations and Orders
maintenance noti cations from within a list view.

You want to create a maintenance order. Create Maintenance Order (Process Maintenance Order)

For more information about the Planning phase, see Planning.

This is custom documentation. For more information, please visit the SAP Help Portal 191
 7/16/2023

Approval

After the maintenance order has been planned, the maintenance planner can submit it for approval. The maintenance order is
then approved or rejected.

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The planning of the maintenance You request the approval of the Order Header: Submitted for Order Header: ORAI (Order
order has been completed. All maintenance order so that the Approval (Order) Approval in Process)
necessary information related to order can be released.
operations, material, labor,
services, and costs have been
added.

The maintenance order has Depending on the con guration Order Header: Approved Order Header: ORAP (Order
been submitted for approval. of the work ow, the maintenance (Order) or Rejected (Order) Approved) or ORRJ (Order
order shows up in the My Inbox Rejected)
app of the responsible
approver. The responsible
person can approve or reject the
maintenance order.

Apps Relevant for the Approval Phase

Business Transaction Apps

You want to con gure the work ow for the maintenance order
approval. Manage Teams and Responsibilities

Manage Work ows for Maintenance Orders

My Inbox

You want to submit the maintenance order for approval.

Change Maintenance Order (Process Maintenance Order)

Manage Maintenance Noti cations and Orders

For more information about the Approval phase, see Approval.

Preparation

Once the maintenance order has been approved, the maintenance planner prepares the order for execution. In the Preparation
phase, the maintenance planner divides the maintenance effort into manageable groups, levels out the workload over several
weeks, determines the concrete time period for the requested maintenance work and checks the availability of all the
resources, spare parts and services needed.

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The maintenance order has You release the maintenance Order Header: In Preparation Order Header: REL (Released)
been approved. order to initiate the procurement (Order)
Order Operations: REL
process and enable material
All Order Operations: In (Released)
commitments.
Preparation
Order Suboperations: REL
All Order Suboperations: In (Released)
Preparation

This is custom documentation. For more information, please visit the SAP Help Portal 192
 7/16/2023

Apps Relevant for the Preparation Phase

Business Transaction Apps

You want to effectively manage the maintenance backlog and create

Manage Maintenance Planning Buckets
once-off or recurrent planning buckets that allow you to organize
major maintenance events such as a planned shutdown as well as Manage Maintenance Backlog
de ne weekly maintenance windows for recurrent maintenance
work.

You want to monitor whether externally procured materials or

Monitoring Procurement Activities
services will be available by their planned requirement dates.
Maintenance Backlog Overview

You want to check the availability of the required stock components Schedule Material Availability Check
and reassign committed quantities from one maintenance order to
another of higher priority.

For more information about the Preparation phase, see Preparation.

Scheduling

During this phase you dispatch the maintenance order or the individual order operations and suboperations and thereby
con rm that they have been scheduled at the right work center and at the right time.

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The maintenance order has You con rm that all the required Order Header: Ready to Order Header: ORSC (Ready for
been released. resources (stock materials, non- Schedule (Order) Scheduling)
stock materials and lean
services) will be available on All Order Operations: Ready to Order Operations: ORSC
the required dates. Schedule (Ready for Scheduling)

All Order Suboperations: Ready Order Suboperations: ORSC

to Schedule (Ready for Scheduling)

The maintenance order with all You dispatch all the operations Order Header: Ready for All Order Operations: DSPT
its operations and and suboperations of a Execution (Order) (Scheduled)
suboperations is ready for speci ed maintenance order
scheduling. and thereby con rm that all All Order Operations: Ready for All Order Suboperations: DSPT
operations and suboperations Execution (Scheduled)
have been dispatched at the
All Order Suboperations: Ready
right work center and at the right
for Execution
time.
This subphase belongs to the
Execution phase.

This is custom documentation. For more information, please visit the SAP Help Portal 193
 7/16/2023

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The maintenance order with all You have an additional license As soon as at least one order Individual order operations that
its operations and for Resource Scheduling and operation with execution stage are dispatched: DSPT
suboperations is ready for dispatch individual order MAIN has been dispatched, the (Scheduled)
scheduling. operations and suboperations. order header is passed on to the
Ready for Execution (Order) Individual order suboperations
subphase. that are dispatched: DSPT
(Scheduled)
Individual order operations and
suboperations that are
dispatched: Ready for
Execution .

If an order operation has no

working hours and no lean
services assigned, this order
operation is passed on to the
Ready for Execution subphase
as soon as at least one of its
suboperations is dispatched.

Note that the order operation

subphase has no effect on the
subphase of the corresponding
suboperations.

This subphase belongs to the

Execution phase.

You have an additional license You select one or more order The system checks the Individual suboperations for
for Resource Scheduling and suboperations and choose preceding phases of the whom the Cancel Dispatch
you have dispatched individual Cancel Dispatch. individual order suboperations business transaction has been
operations and suboperations. and then changes the executed: ORSC (Ready for
These operations and subphases back. This means Scheduling) or REL (Released)
suboperations have the system that after the business
status DSPT (Scheduled). transaction Cancel Dispatch Corresponding order operations
has been completed, the that do not have any working
individual suboperations are hours, lean services or
directed back to the Ready to dispatched suboperations:
Schedule or In Preparation ORSC (Ready for Scheduling)
subphase. or REL (Released)

The system automatically

executes the Cancel Dispatch
business transaction for the
corresponding order operation if
the following prerequisites
apply:

The order operation has

no working hours and no
lean services assigned.

The order operation has

no suboperations that
still have the system
status DSPT
(Scheduled).

Apps Relevant for the Scheduling Phase

This is custom documentation. For more information, please visit the SAP Help Portal 194
 7/16/2023

Business Transaction Apps

You want to dispatch all operations and suboperations of speci ed Find Maintenance Orders
maintenance orders from within a list view.

You want to dispatch all operations and suboperations of a Manage Maintenance Backlog
speci ed order after having monitored the committed quantities
and milestones.

You have an additional license for Resource Scheduling and want to Maintenance Scheduling Board
dispatch single operations and suboperations of a speci ed
maintenance order individually.

You have an additional license for Resource Scheduling and want to

Manage Schedules
set up a schedule to schedule order operations. You can create
multiple schedules to simulate and compare work center utilization Manage Work Center Utilization
in different scenarios, collaborate with others, and dispatch all
scheduled operations in one go.

For more information about the Scheduling phase, see Scheduling.

Execution

Maintenance orders are only passed on to this phase if at least one order operation with execution stage MAIN is dispatched.
During this phase you as a maintenance technician receive a work list containing all the order operations and suboperations
that have been dispatched. You perform the repair work that is described in the individual order operations and suboperations -
be it preliminary, main or nishing work. Moreover, you indicate your work progress. Once the work has been completed, the
corresponding order operation or suboperation is passed on to the Post Execution phase.

The subphase and system status on order header level indicates the work progress of the main repair work and is therefore
derived from the subphases and system statuses of the order operations with execution stage MAIN.

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

This is custom documentation. For more information, please visit the SAP Help Portal 195
 7/16/2023

Prerequisites Business Transaction Resulting Subphase Resulting System Status

Only order operations and As a maintenance technician, As long as only order operations Order Operation: JIPR (Job in
suboperations with execution you select an order operation or with execution stage PRE have Process)
stage PRE have been suboperation with execution been dispatched, the
Order Suboperation: JIPR (Job
dispatched. stage PRE and start working on maintenance order remains in
in Process)
it. the Ready to Schedule (Order)
subphase of the Scheduling
phase.

If you start working on an order

operation with execution stage
PRE, this order operation is
passed on to the Work in
Execution subphase. However,
since only preliminary work has
been performed and the order
header only indicates the
progress in the main repair
work, the subphase and phase
of the order header are not
updated.

If an order operation has no

working hours and no lean
services assigned, this order
operation is passed on to the
Work in Execution subphase as
soon as you start working on one
of its suboperations.

Order operations or As a maintenance technician, As soon as the rst order Order Operation: JIPR (Job in
suboperations with execution you select an order operation or operation with execution stage Process)
stage MAIN have been suboperation with execution MAIN has been dispatched, the
Order Suboperation: JIPR (Job
dispatched. stage MAIN and indicate that order header is passed on to the
in Process)
you start with the repair work. Ready for Execution (Order)
subphase of the Execution
phase.

As soon as you start working on

an order operation with
execution stage MAIN, this
order operation is passed on to
the Work in Execution
subphase. Since main repair
work has been performed, the
corresponding order header is
passed on to the Main Work
Started (Order) subphase.

If an order operation has no

working hours and no lean
services assigned, this order
operation is passed on to the
Work in Execution subphase as
soon as you start working on one
of its suboperations.

This is custom documentation. For more information, please visit the SAP Help Portal 196
 7/16/2023

Prerequisites Business Transaction Resulting Subphase Resulting System Status

Order operations or As a maintenance technician, If order operations with The system status of the order
suboperations with execution you select an order operation or execution stage POST have header does not change.
stage POST have been suboperation with execution been dispatched, this has no
Order Operation: JIPR (Job in
dispatched. stage POST and start working effect on the order header
Process)
on it. subphase.
Order Suboperation: JIPR (Job
If you start working on an order
in Process)
operation with execution stage
POST, this order operation is
passed on to the Work in
Execution subphase. However,
since nishing work has been
performed and the order header
only indicates the progress in
the main repair work, the
subphase and phase of the
order header are not updated.

If an order operation has no

working hours and no lean
services assigned, this order
operation is passed on to the
Work in Execution subphase as
soon as you start working on one
of its suboperations.

You have started the You need to pause the work on Pausing your work has no effect
maintenance work described in an order operation. on the subphase of the order
an order operation. header.

Order Operation: Work Paused

As a maintenance technician, You post a partial time Partial time con rmations have Order Header: PCNF (Partially
you have started the con rmation for a selected no effect on the subphases Con rmed)
maintenance work described in order operation. associated with an order
Order Operation: PCNF
an internally-processed order operation or with the order
(Partially Con rmed)
operation. header.

If you post a partial time

con rmation and the
maintenance work described in
the order operation has not been
started yet, the partial time
con rmation has the same
effect on the subphases as if
the repair work had already
been started.

This is custom documentation. For more information, please visit the SAP Help Portal 197
 7/16/2023

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The maintenance order has one You post a partial time Partial time con rmations have Order Suboperation: PCNF
operation with several con rmation for one selected no effect on the subphases (Partially Con rmed)
suboperations and is internally order suboperation. associated with the order
Corresponding Order Operation:
processed. suboperation.
SPCF (Suboperation Partially
You have set up the order If you post a partial time Con rmed)
operation as an organizational con rmation and the
element that serves as a kind of maintenance work described in
grouping operation for the the order suboperation has not
suboperations. Consequently been started yet, the partial
the order operation has no time con rmation has the same
working hours and no lean effect on the subphases as if
services assigned. You have the repair work had already
planned all the maintenance been started.
work in the suboperations only.
However, the partial time
As a maintenance technician, con rmation of the
you have started the suboperation might in uence
maintenance work described in the subphase of the
one of the order suboperations. corresponding grouping
operation.

The maintenance order is As the responsible person for Subphase: Work in Execution Order Operation: SEPC (Service
planned to be performed by an approval, you approve the Partially Con rmed)
Phase: Execution
external service provider and submitted service entry sheets.
This system status indicates
has one operation with several
that at least one lean service
lean services assigned.
that has been assigned to the
order operation has been
partially or nally con rmed.

The maintenance order is As a purchaser, you post a Subphase: Work in Execution Order Operation: EOPD
planned to be performed by an goods receipt for the external (External Operation Partially
Phase: Execution
external service provider. operation to con rm that the Delivered)
Therefore you have categorized planned external work has been
the order operation as external partially performed.
by having assigned the control
key YBM2.

This is custom documentation. For more information, please visit the SAP Help Portal 198
 7/16/2023

Prerequisites Business Transaction Resulting Subphase Resulting System Status

A partial time con rmation has You use the Cancel PM Order If you cancel the partial time The system status PCNF
been posted for at least one Con rmation app to cancel a con rmation of the order (Partially Con rmed) is
internally-processed order partial time con rmation of an suboperation or operation, the removed from the
operation or suboperation. internally-processed order system checks the preceding corresponding order
operation or suboperation. phases of the order suboperation, order operation or
suboperation, operation and the order header.
order header and then changes
the phases and subphases
back.

If the order header has been in

the Main Work Started (Order)
subphase because a
maintenance technician has
already performed work (status
JIPR (Job in Process) is set),
the cancellation of the partial
time con rmation has no effect
on the subphases associated
with the order operation or with
the order header.

If you cancel the partial time

con rmation of a suboperation,
the system automatically
executes the Cancel
Con rmation business
transaction for the
corresponding order operation if
the following prerequisites
apply:

The order operation has

no working hours and no
lean services assigned.

The order operation has

no suboperations that
still have the system
status PCNF (Partially
Con rmed).

Apps Relevant for the Execution Phase

Business Transaction Apps

You want to review, execute, and report the ndings for all Perform Maintenance Jobs
operations and suboperations that are in the Ready for Execution
subphase.

You want to post a partial time con rmation. Find Maintenance Orders and Operations

You want to cancel the partial time con rmation of an internally- Cancel PM Order Con rmation
processed order operation.

For more information about the Execution phase, see Execution.

For more information how to organize internal and external work in maintenance orders, see Representing Work in Maintenance
Orders.

This is custom documentation. For more information, please visit the SAP Help Portal 199
 7/16/2023
For the prerequisites that apply when working with lean services and external operations, see Organizing External Maintenance
Work.

Post Execution

During this phase you, as a maintenance technician, record the time spent on the order operations and suboperations, provide
malfunction details and failure data, and check the nal con rmation.

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The maintenance order has As a maintenance planner or Order Header: Main Work Order Header: OMWC (Order
been released. supervisor, you indicate that the Completed (Order) Main Work Completed)
main work of a maintenance
The main repair work has been All Preliminary and Main Order Preliminary and Main
order has been completed.
completed. Operations: Work Finished Operations: OMWC (Order Main
Work Completed)
All Preliminary and Main
Suboperations: Work Finished Preliminary and Main
Suboperations: OMWC (Order
Main Work Completed)

The maintenance order has one You indicate that you have Individual Order Suboperation:
Suboperation:
operation with several nished your work on one
JBFI (Job Finished)
suboperations and is internally individual order suboperation Subphase: Work
processed. You have planned without posting a nal time Finished PWF (Planned Work
the maintenance work only in con rmation. Finished)
the suboperations. Phase: Post Execution
Consequently, the Since there are still
Operation:
corresponding order operation suboperations with
has no working hours and no Subphase: Work in maintenance work to be
lean services assigned. Execution performed, the corresponding
order operation remains in
The maintenance suboperation Phase: Execution system status JIPR (Job in
is in the Work in Execution
Process).
subphase.

The maintenance operation or You indicate the end of your The order header is passed on The system can only assign the
suboperation is in the Work in maintenance work on an to the Work Done (Order) JBFI (Job Finished) status to an
Execution subphase. internally-processed order subphase as soon as all order order header if the following
operation or suboperation. operations and suboperations requirements have been
ful ll one of the following ful lled:
You post a nal time
requirements:
con rmation for an internally- If none of its order
processed order operation or The end of the operations have any
suboperation. maintenance work has suboperations
been indicated for the assigned, all the
operation or operations have been
suboperation. set to at least JBFI (Job
Finished).
A nal time con rmation
Consequently, the PWF
has been posted for the
(Planned Work
operation or
Finished) system
suboperation.
status has been set for
all order operations.
Order operations and
suboperations that have been If the order operations
completed, are passed on to the have any suboperations
Work Finished subphase assigned, the following
regardless of their execution logic applies:
stage.

This is custom documentation. For more information, please visit the SAP Help Portal 200
 7/16/2023

Prerequisites Business Transaction Resulting Subphase Resulting System Status

All
suboperations
have already
been set to JBFI
(Job Finished).
Consequently,
the
corresponding
order operation
is set to SPCF
(Suboperation
Partially
Con rmed) and
PWF (Planned
Work Finished).

All
suboperations
have already
been set to CNF
(Con rmed).
Consequently,
the
corresponding
order operation
is set to SCNF
(Suboperation
Finally
Con rmed) and
PWF (Planned
Work Finished).

The order header is set to CNF

(Con rmed) as soon as all the
order operations and
suboperations have been set to
CNF (Con rmed) or the order
operation has been set to SCNF
(Suboperation Finally
Con rmed).

This is custom documentation. For more information, please visit the SAP Help Portal 201
 7/16/2023

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The maintenance order is You set all the lean services to Order Operation: Order Operation:
planned to be performed by an nally con rmed.
Subphase: Work Finished SECF (Service
external service provider and
Con rmed)
has one operation with several Phase: Post Execution
lean services assigned. This system status
indicates that all lean
services of the order
operation have been
nally con rmed and
that all purchase order
items for the lean
services have been
marked as Delivery
Completed.

PWF (Planned Work

Finished)

This system status

indicates that all the
planned maintenance
work - be it internal or
external - has been
nished. It causes the
order operation to be
passed on to the Work
Finished subphase.

The maintenance order is You post several goods receipts Order Operation: Order Operation:
planned to be performed by an mapping the planned quantity
Subphase: Work Finished EODL (External
external service provider. of the external operation. The
Operation Delivered)
Therefore you have categorized system marks the Delivery Phase: Post Execution
the order operation as external Completed indicator in the PWF (Planned Work
by having assigned the control referenced purchase order Finished)
key YBM2. items.
This system status
indicates that all the
planned maintenance
work - be it internal or
external - has been
nished. It causes the
order operation to be
passed to the Work
Finished subphase.

This is custom documentation. For more information, please visit the SAP Help Portal 202
 7/16/2023

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The maintenance order has You use the Cancel PM Order If you cancel the nal time The system status CNF
been released. Con rmation app to cancel the con rmation of the order (Con rmed) is removed from
nal time con rmation of an suboperation or operation, the the order suboperation, the
A nal time con rmation has
internally-processed order system checks the preceding order operation or the order
been posted for at least one
operation or suboperation. phases of the order header.
internally-processed order
suboperation, the order
operation or suboperation.
operation and the order header
and then changes the phases
and subphases back.

If the order header has already

been in the Work Done (Order)
subphase because a
maintenance technician has
indicated the end of the
maintenance work and the
system status JBFI (Job
Finished) has been set for all
order operations, the order
header remains in the Work
Done (Order) subphase.

If you cancel the nal time

con rmation of a suboperation,
the system automatically
executes the Cancel
Con rmation business
transaction for the
corresponding order operation if
the following prerequisites
apply:

The order operation has

no working hours and no
lean services assigned.

The order operation has

no suboperations that
still have the system
status CNF (Con rmed)
.

Apps Relevant for the Post Execution Phase

Business Transaction Apps

As a maintenance planner, you want to post a partial or nal time Find Maintenance Orders and Operations
con rmation from within a list view.

As a maintenance planner or supervisor, you want to set a

maintenance order to Main Work Completed from within a Manage Maintenance Noti cations and Orders
maintenance order list view.
Find Maintenance Orders

As a maintenance planner or supervisor, you want to set a Change Maintenance Order (Process Maintenance Order)
maintenance order to Main Work Completed.

As a maintenance technician, you want to indicate the end of your Perform Maintenance Jobs
repair work or post a con rmation.

This is custom documentation. For more information, please visit the SAP Help Portal 203
 7/16/2023

Business Transaction Apps

You want to cancel the nal time con rmation of an internally- Cancel PM Order Con rmation
processed order operation.

For more information about the Post Execution phase, see Post Execution.

For more information about setting and reversing the Main Work Completed status, see Main Work in the Maintenance Order.

For more information how to organize internal and external work in maintenance orders, see Representing Work in Maintenance
Orders.

Completion

During this phase, the maintenance planner or nancial controller reviews maintenance orders that are in subphase Technically
Complete (Order), settles the orders nancially, performs all the necessary tasks and nally changes the corresponding order
status to Complete (Business). Thereby, the maintenance order is nally set to the Closed (Order) subphase.

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The maintenance order has As a maintenance planner or Order Header: Technically Order Header: TECO
already been released. supervisor, you indicate that all Complete (Order) (Technically Completed)
work described in the
Furthermore, all the All Order Operations: Order Operations: TECO
maintenance order has been
maintenance technicians should Technically Complete (Technically Completed)
completed and change the order
have posted the nal time
status to Technically All Order Suboperations: Order Suboperations: TECO
con rmation and thereby
Completed. Technically Complete (Technically Completed)
con rmed that the repair work
has been completed.

The maintenance order has As a maintenance planner or Order Header: Closed (Order) Order Header: CLSD (Closed)
already been released. nancial controller, you analyze
Note that for the individual
the costs, check open purchase
order operations and
orders and invoices and settle
suboperations no corresponding
the maintenance order
subphase is issued.
nancially. After the
maintenance order is fully
settled and no additional costs
need to be posted on this
maintenance order, you change
the system status to Completed
(Business).

The maintenance order is As a maintenance planner or The system checks the The system status TECO
associated with the Technically supervisor, you cancel the preceding phases of the order (Technically Completed) is
Complete (Order) subphase. technical completion of the header and then changes the removed from the order header
maintenance order. phases and subphases back. and the corresponding order
operations and suboperations.

Apps Relevant for the Completion Phase

Business Transaction Apps

You want to set an individual maintenance order to Technically Change Maintenance Order (Process Maintenance Order)
Completed or Completed (Business).
For more information about how to analyze maintenance order
costs, see Analyzing Costs in the Maintenance Order.

This is custom documentation. For more information, please visit the SAP Help Portal 204
 7/16/2023
For more information about the Completion phase, see Completion.

In case of emergency, you need to ensure that urgent repair work is carried out immediately without delay. If you are authorized
to trigger emergency work, some of the steps that have been described in this document are performed automatically by the
system. For more information about the Reactive Maintenance process in the Emergency Work context, see Reactive
Maintenance: Emergency Work.

Proactive Maintenance
When you create a maintenance noti cation of the type Proactive Maintenance using the Create Maintenance Plan app, it
follows the process from Screening to Completion.

When you create a maintenance order of the type Proactive Maintenance using the Create Maintenance Plan app, the order
does not go for initiation and screening. One of the following will take place:

If you opted not to release the order immediately, then the order moves to the Approval phase.

If you opted to release the order immediately, then the order moves to the Preparation phase.

For more information, see Do Not Release Immediately.

The phases are as follows:

Screening

You can review and accept maintenance requests. For more information, see Screening.

Planning

After the maintenance request has been accepted, you can start planning the resources for the maintenance order. This
order inherits the data of the accepted maintenance request. For more information, see Planning.

Approval

During this phase, maintenance orders are approved by means of a exible work ow process. For more information, see
Approval.

Preparation

Once the order has been released, the maintenance planner divides the maintenance effort into manageable groups,
levels out the work load over several weeks, determines the concrete time period for the requested maintenance work
and checks the availability of all the required resources, spare parts and services. For more information, see Preparation.

Scheduling

During this phase the maintenance planner or scheduler dispatches the order operations and suboperations and thereby
con rms that they have been scheduled at the right work center and at the right time. For more information, see
Scheduling.

Execution

During this phase, the maintenance technician executes the preliminary and main maintenance tasks, captures time and
material consumption and con rms that the main work has been executed. For more information, see Execution.

Post Execution

During this phase, the maintenance technician executes the nishing maintenance tasks and documents time and
material consumption. For more information, see Post Execution.

This is custom documentation. For more information, please visit the SAP Help Portal 205
 7/16/2023
Completion

During this phase, the maintenance planner or nancial controller reviews maintenance orders that have already been
technically completed but not yet nancially settled, performs all the necessary tasks and nally sets the orders to
Complete (Business). For more information, see Completion.

To view and monitor all the maintenance orders belonging to a speci c phase or subphase, you can lter the maintenance order
list accordingly in the Find Maintenance Orders app. The phase and subphase is also displayed as a table column in several apps
such as in the Manage Maintenance Backlog app.

Processing Contexts
Order Type and Processing Context

If you create a maintenance order of a speci c order type, the order type determines the process phases that the maintenance
order runs through. For example, if you create a maintenance order of the Reactive Maintenance order type, the maintenance
order runs through the Planning, Approval, Preparation, Scheduling, Execution, Post Execution and Completion phase. Assigning
a processing context to a maintenance order allows you to modify this end-to-end process how it is determined by the order
type.

If a maintenance order is assigned to a processing context other than Standard Order, the system sets the status EXCP
(Exception Process) on order header level.

Since the processing context in uences the end-to-end process that the maintenance order runs through, you can only
assign a different processing context when the maintenance order is created. You can lter maintenance orders
according to their processing context in the Find Maintenance Orders app and in the Find Maintenance Orders and
Operations app. But - similar to the order type - you cannot change the processing context of a maintenance order
retrospectively.

Processing Context: Standard Order

By default, the system assigns the processing context Standard Order to a newly-created maintenance order. As long as you do
not select a different processing context during order creation, the maintenance order runs through the standard end-to-end
process that is determined by the order type.

For more information about the end-to-end process in Reactive Maintenance with processing context Standard Order, see
Overview: Reactive Maintenance Process.

Processing Context: Emergency Order

In the case of an emergency, it must be ensured that any urgent repair work is carried out without delay. If you create a
maintenance request and specify the maintenance work as Emergency Work, the system creates a maintenance order based
on this accepted maintenance request and assigns it to the Emergency Order (E) processing context. This has the effect that
the maintenance order of the Reactive Maintenance order type is passed immedieately to the Execution phase without running
through any intermediate planning, approval, preparation or scheduling steps. The system releases the maintenance order and
dispatches the order operation subsequently.

For more information about the end-to-end process in Reactive Maintenance with processing context Emergency Order (E), see
Reactive Maintenance: Emergency Work.

Reactive Maintenance: Emergency Work

This is custom documentation. For more information, please visit the SAP Help Portal 206
 7/16/2023
In the case of an emergency, you need to ensure that urgent repair work is carried out without delay. If you are authorized to
trigger emergency work, the Reactive Maintenance process runs through the following steps:

You create a maintenance request and select Emergency Work as the Noti cation Processing Context. When you
submit the maintenance request, the system automatically accepts it.

Based on this accepted noti cation, the system creates a maintenance order, releases it and subsequently dispatches
the order operation. This means that the maintenance order of the Reactive Maintenance order type is passed directly
to the Execution phase without running through any intermediate planning, approval, preparation and scheduling steps.

In the Execution phase you, as a maintenance planner, can add an additional operation to involve an additional
maintenance technician in the repair work and dispatch the newly-entered operation manually. Since the maintenance
technician can already view the job list and therefore also the order operation that has been created by the system, the
emergency work can be carried out immediately.

Once the operation has been dispatched, the emergency order is processed in the same way as a regular maintenance
order of the Reactive Maintenance order type and runs through all the remaining phases and subphases of the standard
Reactive Maintenance process.

 Note

To create a maintenance request and specify the noti cation processing context as Emergency Work, assign the
authorization object Exception Process - Maintenance Noti cation (I_EXCP_MN) to your business role and maintain
IEXCP_MN = 01 (Emergency Work).

After the maintenance request has been submitted, the system creates an emergency order based on the accepted
request if the authorization object Exception Process - Maintenance Order (I_EXCP_MO) has been assigned to your
business role. Moreover, the order type, maintenance planning plant, and additional processing context must be
maintained for the Reactive Maintenance order type, the relevant planning plants, and the processing context E
(Emergency Order).

The following descriptions and tables provide an overview of the phases, subphases and system statuses of the Reactive
Maintenance process in the Emergency Work processing context.

Initiation

During the Initiation phase, you create the maintenance request for a piece of equipment or a functional location. They must
have a valid cost center assigned.

 Note
In the Reactive Maintenance process, the cost center (CTR) serves as a default cost receiver for account assignment. The
cost center therefore has to be speci ed in the technical object so that the default settlement rule can be automatically
generated for the resulting emergency order. If the cost center is not provided, the system creates neither the maintenance
request nor the maintenance order.

You enter all the necessary details and specify the Reactive Maintenance process as Emergency Work in the Noti cation
Processing Context eld. You make sure that the main work center and the planning plant are speci ed and nally submit the
request. The maintenance request does not run through the Screening phase but immediately is passed to the Accepted
(Request) subphase of the Planning phase. The system automatically creates a maintenance order based on this accepted
maintenance request.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 207
 7/16/2023
If you have con gured the Reactive Maintenance order type in a way that a phase control code blocks the
maintenance order from being released, the system creates neither a maintenance request nor an emergency order.

If you have con gured the Reactive Maintenance order type in a way that a phase control code blocks the
maintenance order from being scheduled, the system creates the maintenance request and the maintenance order,
releases the order automatically and passes the order to the Preparation phase.

If you want phase control codes to be active for the Planning or Scheduling phase in the standard Reactive Maintenance
order, you need to use the Business Add-In (BAdI) Phase Control Activation and Deactivation
(EAM_PHASE_CONTROL_ACTIVATION) to deactivate these phase control codes for the processing context E (Emergency
Order).

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

You detect a failure at a You create a maintenance Noti cation Header: Accepted Noti cation Header:
technical object that has to be request, specify the (Request)
NOPR (Noti cation in
repaired immediately. maintenance process as
Process)
Emergency Work and submit it.
APOK (Approval: OK)

ORAS (Order Assigned)

Apps Relevant for the Initiation Phase

Business Transaction Apps

You want to create a maintenance request for the Reactive Create Maintenance Request
Maintenance process and de ne it as Emergency Work.

You want to view the maintenance requests that you have My Maintenance Requests
submitted.

For more information, see How to Use Noti cation Processing Context.

Automated Process Phases: Planning, Approval, Preparation and Scheduling

After you have submitted a maintenance request that has been de ned as Emergency Work, the system automatically
processes the following phases:

Planning

The system automatically accepts the maintenance request and passes it to the Accepted (Request) subphase.

Based on this accepted maintenance request, the system creates a maintenance order of the Reactive
Maintenance order type and associates the maintenance order with the processing context Emergency Order.
The emergency order has one order operation assigned and inherits the most important data of the maintenance
request. Besides the technical object, the following mandatory data is particularly important:

Cost Center: the data is copied from the technical object

Main Work Center: the data is copied from the maintenance request

Planning Plant: the data is copied from the maintenance request

Approval

This is custom documentation. For more information, please visit the SAP Help Portal 208
 7/16/2023
For a maintenance order with the processing context Emergency Order no approval steps are performed. Even if you
have con gured your system in a way that causes the maintenance order to have to be approved before it can be
released, the resulting system status ORAR (Order Approval Required) will be deactivated automatically.

Preparation

The system releases the emergency order automatically and sets the system status REL (Released) on order header
and order operation level. However, due to the con guration, the system can only release the emergency order if a
default settlement rule has been generated. If no cost center has been provided and the default settlement rule could
not be generated, the system creates neither a maintenance request nor an emergency order.

Scheduling

The system dispatches the order operation automatically and sets the system status DSPT (Scheduled) on operation
level.

Subphases and System Statuses

Prerequisites Automated System Process Resulting Subphase Resulting System Status

You have submitted a The system creates a Noti cation Header: Order Order Header:
maintenance request. Since you maintenance order of the Assigned (Request)
REL (Released)
have de ned the urgent repair Reactive Maintenance order
Order Header: Ready for
work as Emergency Work, the type based on the accepted EXCP (Exception
Execution (Order)
maintenance request has maintenance request, releases Process)
automatically been passed to the emergency order and Order Operation: Ready for
the Accepted (Request) dispatches the order operation. Execution Order Operation:
subphase.
REL (Released)

DSPT (Dispatched)

Relevant Apps

Business Transaction Apps

You want to view all the maintenance requests with the noti cation
processing context Emergency Work. Find Maintenance Noti cation

My Maintenance Requests

Screen Maintenance Requests

You want to view all the maintenance orders that the system has
created with the processing context Emergency Order. Find Maintenance Orders

Find Maintenance Orders and Operations

Execution

The emergency order has been created, released and passed directly to this phase. It contains one dispatched order operation
with execution stage MAIN. This order operation shows up in the worklist of the maintenance technician who can immediately
start to perform the urgent repair work and document the work progress.

You, as a maintenance planner, can add an additional operation to the emergency order if you want an additional maintenance
technician to contribute to the resolution of the emergency repair work. To dispatch any newly-added operations individually,
you mark the operations and select Dispatch Operation.

Following the standard Reactive Maintenance process, the maintenance technician documents the work progress and
ultimately the completion of the urgent repair work. Once the work on an order operation has been completed, the

This is custom documentation. For more information, please visit the SAP Help Portal 209
 7/16/2023
corresponding order operation is passed on to the Post Execution phase. In general, the emergency order runs through the
Execution, Post Execution and Completion phase in the same way as any standard Reactive Maintenance order.

 Note
As a maintenance planner or supervisor, you can change and update emergency orders even if you do not have the
authorization to create maintenance orders of this processing context.

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

Order operations or As a maintenance technician, As soon as the rst order Order Operation: JIPR (Job in
suboperations with execution you select an order operation or operation with execution stage Process)
stage MAIN have been suboperation with execution MAIN has been dispatched, the
Order Suboperation: JIPR (Job
dispatched. stage MAIN and indicate that order header is passed on to the
in Process)
you start with the repair work. Ready for Execution (Order)
subphase of the Execution
phase.

As soon as you start working on

an order operation with
execution stage MAIN, this
order operation is passed on to
the Work in Execution
subphase. Since main repair
work has been performed, the
corresponding order header is
passed on to the Main Work
Started (Order) subphase.

If an order operation has no

working hours and no lean
services assigned, this order
operation is passed on to the
Work in Execution subphase as
soon as you start working on one
of its suboperations.

As a maintenance technician, You post a partial time Partial time con rmations have Order Header: PCNF (Partially
you have started the con rmation for a selected no effect on the subphases Con rmed)
maintenance work described in order operation. associated with an order
Order Operation: PCNF
an internally-processed order operation or with the order
(Partially Con rmed)
operation. header.

If you post a partial time

con rmation and the
maintenance work described in
the order operation has not been
started yet, the partial time
con rmation has the same
effect on the subphases as if
the repair work had already
been started.

If you work with suboperations or externally-processed operations, look at the following documentation to learn how the system
determines the subphases and system statuses: Overview: Reactive Maintenance Process.

Apps Relevant for the Execution Phase

Business Transaction Apps

This is custom documentation. For more information, please visit the SAP Help Portal 210
 7/16/2023

Business Transaction Apps

You want to review, execute, and report the ndings for all Perform Maintenance Jobs
operations and suboperations that are in the Ready for Execution
subphase.

You want to post a partial time con rmation. Find Maintenance Orders and Operations

For more information about the Execution phase, see Execution.

Post Execution

During this phase you, as a maintenance technician, record the time spent on the order operations, provide malfunction details
and failure data, and check the nal con rmation. The emergency order is processed in this phase in the same way as the
standard Reactive Maintenance order.

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The maintenance order has As a maintenance planner or Order Header: Main Work Order Header: OMWC (Order
been released. supervisor, you indicate that the Completed (Order) Main Work Completed)
main work of a maintenance
The main repair work has been All preliminary and main order All preliminary and main
order has been completed.
completed. operations: Work Finished operations: JBFI (Job Finished)

The maintenance operation is in As a maintenance technician, The order header is passed on The order header is set to JBFI
the Work in Execution you indicate the end of your to the Work Done (Order) (Job Finished) as soon as all
subphase. maintenance work on an subphase as soon as all order order operations have been set
internally-processed order operations ful l one of the to one of the following statuses:
operation. following requirements:
JBFI (Job Finished) and
As a maintenance technician, The end of the PWF (Planned Work
you post a nal time maintenance work has Finished)
con rmation for an internally- been indicated for the
processed order operation. operation. CNF (Con rmed)

The order header is set to JBFI

A nal time con rmation
(Job Finished) and CNF
has been posted for the
(Con rmed) as soon as all
operation.
order operations have been set
Order operations that have been to CNF (Con rmed).
completed, are passed on to the
Work Finished subphase
regardless of their execution
stage.

If you work with suboperations or externally-processed operations, look at the following documentation to learn how the system
determines the subphases and system statuses: Overview: Reactive Maintenance Process.

Apps Relevant for the Post Execution Phase

Business Transaction Apps

As a maintenance planner, you want to post a partial or nal time Find Maintenance Orders and Operations
con rmation from within a list view.

As a maintenance planner or supervisor, you want to set a

Manage Maintenance Noti cations and Orders
maintenance order to Main Work Completed from within a
maintenance order list view. Find Maintenance Orders

This is custom documentation. For more information, please visit the SAP Help Portal 211
 7/16/2023

Business Transaction Apps

As a maintenance planner or supervisor, you want to set a Change Maintenance Order (Process Maintenance Order)
maintenance order to Main Work Completed.

As a maintenance technician, you want to indicate the end of your Perform Maintenance Jobs
repair work or post a con rmation.

For more information about the Post Execution phase, see Post Execution.

For more information about setting and reversing the Main Work Completed status, see Main Work in the Maintenance Order.

Completion

During this phase, the maintenance planner or nancial controller reviews maintenance orders that are in subphase Technically
Complete (Order), settles the orders nancially, performs all the necessary tasks and changes the corresponding order status
to Complete (Business). This means that the maintenance order can then ultimately be passed to the Closed (Order) subphase.

 Note
If you want the maintenance supervisor to approve whether the urgent repair work has been carried out correctly and the
emergency order can be set to TECO (Technically Completed), you can use the BAdI Phase Control Activation and
Deactivation (EAM_PHASE_CONTROL_ACTIVATION) to activate a phase control code for all emergency orders
automatically when they are created. This phase control code prevents the emergency order from being technically
completed. This allows a supervisor to be able to check the work that has been performed and the condition of the asset that
was under repair. After having completed these checks, the supervisor can deactivate the phase control code so that the
technical completion can be triggered.

Subphases and System Statuses

Prerequisites Business Transaction Resulting Subphase Resulting System Status

The maintenance order has As a maintenance planner or Order Header: Technically Order Header: TECO
already been released. supervisor, you indicate that all Complete (Order) (Technically Completed)
the work described in the
All maintenance technicians maintenance order has been All Order Operations: Order Operations: TECO
should have posted the nal completed. Technically Complete (Technically Completed)
time con rmation and thereby
have indicated that the repair
work has been completed.

The maintenance order has As a maintenance planner or Order Header: Closed (Order) Order Header: CLSD (Closed)
already been released. nancial controller, you analyze
the costs, check open purchase Note that for the individual
orders and invoices and settle maintenance order operations
the maintenance order no corresponding subphase is
nancially. After the issued.
maintenance order has been
fully settled and no additional
costs need to be posted on this
maintenance order, you change
the system status to Completed
(Business).

Apps Relevant for the Completion Phase

Business Transaction Apps

This is custom documentation. For more information, please visit the SAP Help Portal 212
 7/16/2023

Business Transaction Apps

You want to set an individual maintenance order to Technically Change Maintenance Order (Process Maintenance Order)
Completed or Completed (Business).
For more information about how to analyze maintenance order
costs, see Analyzing Costs in the Maintenance Order.

For more information about the Completion phase, see Completion.

Reactive Maintenance: Minor Work

In a typical reactive maintenance process, you notice a maintenance issue in the operation of a technical object and create a
maintenance request. This request is screened, accepted, planned, scheduled, executed (here, malfunction details are
recorded), and completed. But, a minor work maintenance request is accepted as soon as it is submitted.

If you have authorization, you can create a minor work when you notice maintenance issues that can be xed immediately. A
minor work will go through the following steps:

1. You create a maintenance request with minor work as the noti cation processing context. When you submit the
maintenance request, the system automatically accepts it. You can view the accepted maintenance request in My
Maintenance Requests app.

2. Perform corrective actions.

3. After the maintenance issue is xed, you can record the malfunction data and complete the noti cation.

For detailed steps to create minor work, see How to Use Noti cation Processing Context.

Apps Relevant for the Initiation Phase

Business Transaction Apps

You want to create a maintenance request for the Reactive Create Maintenance Request
Maintenance process and de ne it as Minor Work.

You want to view the maintenance requests that you have My Maintenance Requests
submitted.

Authorization

To create a minor work, you need to ensure that the following authorization object is assigned to your role:

I_EXCP_MN (Exception Process - Maintenance Noti cation)

If you maintain 02 (minor work), you will be able to create maintenance requests for minor work.

Related Information
How to Use Noti cation Processing Context

Maintenance Process Phases

If you create maintenance requests and maintenance orders of a speci c type, these maintenance requests and orders are
processed according to the following phases:

This is custom documentation. For more information, please visit the SAP Help Portal 213
 7/16/2023
Initiation

Screening

Planning

Approval

Preparation

Scheduling

Execution

Post Execution

Completion

For more information about which phases are relevant for which order type, see the detailed descriptions of the different order
types:

Reactive Maintenance

Proactive Maintenance

Initiation
During the Initiation phase, you can create maintenance requests for a technical object such as an equipment or a functional
location using the Create Maintenance Request app. You can enter all necessary details to help in screening, processing,
planning, and execution of the request. You can also include attachments and links. The app allows you to view open requests of
a technical object. Until a maintenance request is submitted, the latest draft is available.

Each maintenance request can be prioritized using one of the two options. You can select a priority from the list or assess
priority. The priority assessment is done based on a combination of consequence categories, consequences, and likelihoods.
Priorities can be assessed only if prioritization pro les are maintained for a combination of maintenance plant and noti cation
type.

When you submit a maintenance request, the new request is available in My Maintenance Requests app. Only your requests are
displayed. The requests are grouped and displayed based on their processing statuses. You can view the requests that you
submitted, the requests that have been sent to you because information was insufficient, the requests that were rejected, and
the requests that have been completed. If you have a request that requires additional information, edit the request and
resubmit it for screening. From this app, you can also navigate to Create Maintenance Request app to create a new request.

The new request moves to the Screening phase where it is reviewed.

Related Information
Create Maintenance Request
My Maintenance Requests

Screening
The submitted maintenance request moves to the Screening phase. Here, maintenance requests are screened and accepted.

This is custom documentation. For more information, please visit the SAP Help Portal 214
 7/16/2023
As a supervisor, you can review all the open maintenance requests in the Screen Maintenance Requests app. If information is
insufficient, you can send the request back to the initiator. When the initiator provides information and resubmits the request,
you can review the request again.

In the home screen of the app, the maintenance requests are grouped according to their statuses (Open, Accepted, Rejected,
Action Required, and Completed). By default, open requests are displayed.

While reviewing a request, you can also edit information related to malfunction, responsibility, priority, and other details.
Accepted maintenance requests move to the Planning phase.

Related Information
Screen Maintenance Requests

Planning
The Planning phase begins when a maintenance request is accepted. The accepted maintenance request is now known as a
maintenance noti cation. As a Maintenance Planner, you can now create and plan orders.

In the Manage Maintenance Noti cations and Orders app, maintenance orders can be created for one or more maintenance
noti cations. Alternatively, you can assign an existing maintenance order to a maintenance noti cations. Information from the
leading maintenance noti cation is copied into the maintenance order. The quick view for maintenance order allows you to
navigate to related apps. Orders can also be created in the Create Maintenance Order app.

In the Change Maintenance Order app, you can add information related to operation, material, labor, services, and cost to plan
the order. Only with the role of a supervisor, you can change the nal due date and priority for the maintenance order.

When you create an order, the order is in the phase Planning and subphase In Planning (Order). Depending upon the
con guration of the order type in the SSCUI Activate Work ow for Order Type, an order needs a cost approval. An order can be
released without an approval if the order type is not con gured for work ow. If the work ow is con gured for the order type, the
order goes through the work ow steps for approval. If the work ow is con gured for automatic approval, then the order is
approved immediately. If work ow is set up for manual approval, it will move to the approver's inbox.

You can submit an order for approval from Manage Maintenance Noti cations and Orders app and Change Maintenance Order
app.

As a maintenance planner, you need to ensure that a maintenance order has all the operations, required components,
resources, and documents to perform the maintenance. The system will calculate the planned costs for the maintenance.

If the maintenance order type is con gured for cost approval, then the planner will submit the order for cost approval.

The submitted order moves to My Inbox app. When an order is submitted for approval, the phase and subphase of the order are
Approval and Submitted for Approval (Order) respectively. If the order is approved, then the subphase of the order is Approved
(Order). If the order is rejected, then the subphase is Rejected (Order).

You can release the accepted maintenance orders for preparation. You can edit a rejected maintenance order and submit it for
approval. It moves to the Approval phase.

Related Information
Manage Maintenance Noti cations and Orders
Actual Cost Analysis

This is custom documentation. For more information, please visit the SAP Help Portal 215
 7/16/2023

Approval
Maintenance orders are approved through a exible work ow process in the Manage Work ows for Maintenance Orders app. It
is recommended that you con gure a generic step condition and speci c step sequences. Each step sequence can have step
conditions and one or more approvers. Only one work ow is used but each step condition in the work ow is evaluated. If multiple
step conditions are true, they are created as approval steps and approval from approver of each step is required.

Orders that are ready for approval are available in My Inbox app. To approve a maintenance order, select the work ow request,
review details of the order, enter comments, and approve. You cannot resubmit rejected orders for approval.

When you approve an order, baseline cost is set to equal to the planned cost. Approved orders can be released. After you
release an order, the order moves to Preparation phase.

Related Information
Manage Work ows for Maintenance Orders
Manage Teams and Responsibilities
My Inbox

Preparation
Once an order has been approved for execution and released, it is set to In Preparation and passed to the Preparation phase.
As a maintenance planner, you divide the backlog of maintenance work into manageable groups, determine the concrete time
period for the requested work, and check the availability of any resources, spare parts and services needed.

Structuring the Maintenance Backlog

The Manage Maintenance Planning Buckets app aids you in effectively managing the maintenance backlog by creating
maintenance planning buckets. You can, for example, de ne operational planning buckets to distribute your recurrent
maintenance work. When the maintenance work should take place within speci c, one-time maintenance windows, you can also
create event-based planning buckets to set up maintenance events.

For each planning bucket, you de ne a planning bucket scope which includes a speci c time period, such as a concrete calendar
week, and other attributes, such as the maintenance planning plant or the main work center. When you plan recurrent
maintenance work, the system automatically groups maintenance orders and associates them with a speci c planning bucket
based on the scope. When you plan a maintenance event, you assign orders manually to the event. In this case, the scope
restricts which orders can be assigned to the event.

For more information about creating maintenance planning buckets, see Creating Operational Maintenance Planning Buckets
and Creating Event-Based Maintenance Planning Buckets.

Monitoring the Order Readiness

When maintenance planning buckets have been created, the Manage Maintenance Backlog app provides a list of all
maintenance orders associated with a speci c planning bucket. You can view important order details, the availability status of
components and services, and all maintenance work that has to be performed by an internal work center.

With the help of colored icons indicating the overall readiness of the order, you can easily identify whether a maintenance order
is time-critical, whether the required materials and services are available, and whether the order has already been submitted
for scheduling. You can then take action to ensure the timely availability of certain resources or reschedule the maintenance
order.

This is custom documentation. For more information, please visit the SAP Help Portal 216
 7/16/2023
If you have set up a recurrent ATP check with the relevant parameters in the Schedule Material Availability Check app, you can
monitor the availability of all required stock components in the Manage Maintenance Backlog app. In addition, colored icons
that represent key phases in the procurement process allow you to quickly identify pending procurement activities for any non-
stock components and services and take the necessary actions to ensure they are completed in time. For more information, see
Monitoring Procurement Activities.

While the Manage Maintenance Backlog app provides a list of orders in a speci c maintenance planning bucket, the
Maintenance Backlog Overview app provides aggregated information about several maintenance planning buckets at once and
allows you to navigate to other relevant applications, including the Manage Components and Services app.

Submitting Orders for Scheduling

Once you are con dent that all required resources will be available on the required dates, you can select individual orders in the
Manage Maintenance Backlog app and choose Submit for Scheduling. You can also select the relevant orders in the Find
Maintenance Orders app and change their status to Ready to Schedule or set this status for an individual order in the Change
Maintenance Order app. With this action you pass the corresponding maintenance orders on to the Scheduling phase.

Related Information
Manage Maintenance Planning Buckets
Manage Maintenance Backlog
Schedule Material Availability Check
Find Maintenance Orders
Maintenance Backlog Overview
Manage Components and Services

Scheduling
Once you have submitted a maintenance order for scheduling and changed the order status to Ready to Schedule (ORSC), this
order with all of its operations is passed on to the Scheduling phase. During this phase you dispatch the maintenance order or
the individual order operations and suboperations and thereby con rm that they have been scheduled at the right work center
and at the right time.

 Note
To be able to dispatch single operations and suboperations individually and level the work center utilization, you need to
enhance the core functions of SAP S/4HANA with the additional license for Resource Scheduling.

Scheduling Maintenance Orders Without "Resource Scheduling"

Without Resource Scheduling you cannot dispatch operations individually but always dispatch maintenance orders with all their
operations in the Find Maintenance Orders app or in the Change Maintenance Order app. The system passes the maintenance
orders with all their operations and suboperations to the Ready for Execution subphase of the Execution phase.

Scheduling Maintenance Orders With "Resource Scheduling"

With an additional license, you can use Resource Scheduling for speci c work centers and assign users to these work centers. If
you use Resource Scheduling for the performing work center that is assigned to the order, you can dispatch individual order
operations and suboperations and thereby pass the corresponding orders to the Execution phase. In Resource Scheduling,
there are two options to dispatch order operations: You can dispatch operations and suboperations directly or schedule the
maintenance order operations in a multistep process.

This is custom documentation. For more information, please visit the SAP Help Portal 217
 7/16/2023

Executing "Cancel Dispatch"

As long as the order is not technically complete and not agged for deletion, you can also cancel the Scheduled (DSPT) system
status in the Change Maintenance Order app. Then the system removes the status DSPT so that the operations and
suboperations have their preceding system status. Moreover, the system checks the preceding phases of the order
suboperations, the operations and the order header and then changes the phases back.

For detailed information about dispatching order operations and suboperations and canceling the dispatch of order operations
and suboperations, see Dispatching and Canceling the Dispatch of Order Operations.

Dispatching and Canceling the Dispatch of Order Operations

By dispatching order operations or suboperations, you con rm that they have been scheduled at the right work center and at
the right time. There are two options to dispatch maintenance orders that are ready for scheduling:

If you do not have an additional license for Resource Scheduling, you always dispatch the maintenance orders with all
their operations.

If you have enhanced the core functions of SAP S/4HANA with the additional license for Resource Scheduling, you can
dispatch operations and suboperations individually and level the work center utilization.

Dispatching Maintenance Orders Without "Resource Scheduling"

You can dispatch maintenance orders in the Find Maintenance Orders app or in the Change Maintenance Order app.

In the Find Maintenance Orders app, you lter the maintenance orders by the subphase Ready to Schedule (Order) and
additional lter criteria. You can also use the pre ltered maintenance order list Find Maintenance Orders. Scheduling to
only view maintenance orders that are in the Scheduling phase. You select one or several maintenance orders from the
results list and choose Dispatch Operations.

In the Change Maintenance Order app, you open an individual maintenance order in Change mode and choose
Additional Functions Dispatch Operations .

The system dispatches all operations of the selected orders and passes the suboperations, the operations and the
corresponding order headers to the Ready for Execution subphase of the Execution phase.

After having dispatched a maintenance order, you can still create new operations for this order. These new operations have
their relevant system status and subphase assigned. To dispatch these operations at a later point in time, you can select the
maintenance order again and choose Dispatch Operations. The system will only dispatch the operations that have not been
dispatched before.

 Note
The Dispatch Operations action is available if you are not using Resource Scheduling for the performing work center that is
assigned to the order. The system assumes that Resource Scheduling is used if a user is assigned to the performing work
center in Resource Scheduling.

Scheduling Maintenance Orders With "Resource Scheduling"

With an additional license, you can use Resource Scheduling for speci c work centers and assign users to these work centers. If
you use Resource Scheduling for the performing work center that is assigned to the order, you can dispatch individual order
operations and suboperations and thereby pass the corresponding orders to the Execution phase. In Resource Scheduling,
there are two options to dispatch order operations and suboperations:

This is custom documentation. For more information, please visit the SAP Help Portal 218
 7/16/2023
Scheduling Operations Directly

You can dispatch the operations and suboperations of a maintenance order directly. We recommend that you dispatch
and schedule all operations in a maintenance order together. For more information, see Dispatching Order Operations

To level work center utilization, you can also change the operation work center or enter a new start date and time for an
order operation. For more information, see Moving Order Operations to Another Date or Work Center.

The following two apps support you in scheduling operations directly:

Manage Work Center Utilization

Maintenance Scheduling Board

Scheduling Operations in a Multistep Process

You can also schedule the maintenance order operations in a multistep process. You rst create one or more schedule
simulations for the schedule period. When you are satis ed with the schedule, you dispatch the scheduled order
operations and freeze the nal schedule. For more information, see Scheduling Maintenance Order Operations.

You can schedule operations in a multistep process, using the Manage Schedules app.

If you dispatch individual operations or suboperations, the following logic applies:

When individual operations are dispatched and as a result set to Ready for Execution, it depends on the execution stage
of the operations whether the maintenance order itself is passed to the Ready for Execution (Order) subphase of the
Execution phase:

If only operations with execution stage PRE have been dispatched, the order stays in the Scheduling phase.

As soon as the rst operation with execution stage MAIN has been dispatched, the order itself moves to the
Execution phase. This phase then is also displayed in the order header.

When individual suboperations are dispatched and the corresponding order operation has no working hours and no lean
services assigned, this order operation is passed on to the Ready for Execution subphase as soon as at least one of its
suboperations is dispatched.

When you dispatch an order operation, this has no effect on the corresponding suboperations.

Executing "Cancel Dispatch"

Canceling the Dispatch Without "Resource Scheduling"

If you do not have an additional license for Resource Scheduling and therefore have dispatched the maintenance orders with all
their operations, you cancel the Scheduled (DSPT) system status in the Change Maintenance Order app. If you select
Additional Functions Cancel Dispatched Operations , the system removes the system status DSPT so that the operations
and the order header have their preceding system status. Moreover, the system checks the preceding phases of the order
operations and order header and then changes the phases back.

Canceling the Dispatch With "Resource Scheduling"

With an additional license for Resource Scheduling, you use the Manage Work Center Utilization app to select one or more
individual order operations or suboperations and choose the Cancel Dispatch button. The system removes the system status
DSPT so that the suboperations, the operations and the order header have their preceding system status. Moreover, the
system checks the preceding phases of the order suboperations, operations and order header and then changes the phases
back.

If you execute the Cancel Dispatch business transaction for any suboperations, the individual suboperations are directed back
to the Ready to Schedule or In Preparation subphase. The system automatically executes the Cancel Dispatch business

This is custom documentation. For more information, please visit the SAP Help Portal 219
 7/16/2023
transaction for the corresponding order operation if both of the following prerequisites apply:

The order operation has no working hours and no lean services assigned.

The order operation has no suboperations that still have the system status Scheduled (DSPT).

Execution
Phase to perform maintenance of orders.

This is the execution phase. In this phase, a maintenance technician receives all the orders that need to be executed. The
technician performs the required maintenance tasks according to the recommendations provided in the order operation.
Generally, the technician executes the PRE (preliminary) and MAIN (main) operations for an order in this phase.

The various process subphases for an operation and an order are as mentioned in the table below:

Operation Operation Process Subphase Order Process Subphase

Job is listed in the My Maintenance Jobs Ready for Execution Ready for Execution (Order)
app. This is the app used for execution of
the order operation.

Technician starts a job by adding time Work in Execution Main Work Started (Order)
con rmation for the operation.

After completion of the work, the Final Work Finished

Con rmation checkbox is selected.

After the technician has performed the maintenance task and sets all the PRE and MAIN operations to Finally Con rmed, the
system deselects the Has Open Main Work checkbox in the order header data. The supervisor can now lter the result list in the
Find Maintenance Orders application to display the orders for review and agrees to the completion of the main work. The
supervisor changes the status of the order to Main Work Completed in the Find Maintenance Orders application.

Related Information
Perform Maintenance Jobs

Post Execution
Phase to complete maintenance tasks for an order.

The supervisor changes the status of the order to Main Work Completed in the Find Maintenance Orders application and the
order appears in the post-execution phase. The technician proceeds with the post execution tasks for the order. These tasks
include the recording of time spent on post execution operations, preparing malfunction details and failure data, and checking
nal con rmation of post-execution operations. This activity is performed in the Perform Maintenance Jobs application. The
order is set to Work Done .

Supervisor reviews the failure data, approves the order, and changes the status of the order to Complete Technically in the Find
Maintenance Orders application. Supervisor also reviews the noti cation status and approves it as completed, if the order has
associated noti cation. The order moves to the Completion phase.

Related Information

This is custom documentation. For more information, please visit the SAP Help Portal 220
 7/16/2023
Perform Maintenance Jobs

Completion
Once all pre, main and post maintenance tasks have been executed, the maintenance order is set to Technically Complete
(Order) and thereby passed on to the Completion phase. During this phase, the maintenance planner or nancial controller
reviews maintenance orders in subphase Technically Complete (Order), settles the orders nancially, performs all the necessary
tasks and nally changes the corresponding order status to Complete (Business). Thereby, the maintenance order is nally set
to the Closed (Order) subphase.

In the Find Maintenance Orders app, you can display a list of maintenance orders, lter the list to only monitor orders in the
subphase Technically Complete (Order) and perform the following tasks:

Compare the actual costs posted for the maintenance orders with the planned costs or baseline costs.

If you navigate to an individual maintenance order, the Detailed Cost Analysis view in the Costs area provides you with a
hierarchical overview of all the costs entered and incurred for the individual order operations and suboperations. The
system displays the estimated costs entered for the maintenance order for each spend category, as well as planned
costs, baseline costs and actual costs that were posted to individual operations and suboperations. For more
information, see Analyzing Costs in the Maintenance Order.

If you want to monitor and evaluate estimated costs, baseline costs, planned costs and actual costs resulting from
several maintenance orders, you can use the Maintenance Order Costs app.

Check the status of purchase orders for parts and services that have been created for speci c maintenance orders

Check the status of invoices associated with the maintenance orders and ensure that all the invoices are received,
checked and paid

Settle the maintenance orders nancially

After you have analyzed the costs, checked open purchase orders and invoices and settled the maintenance orders nancially,
you change the maintenance order status to Completed (Business). This status prevents further costs from being allocated to
the corresponding maintenance order. The system checks whether the completed maintenance order has any open header
maintenance noti cation and sets the corresponding maintenance request to Completed (Request).

 Note
If the maintenance work that is documented in the order will not be performed due to any reason, you can change the order
status to Do Not Execute as long as the maintenance order has not been released. Thereby the order is passed on to the
Work Not Performed (Order) subphase of the Completion phase.

If the maintenance order has been set to Do Not Execute or Complete (Business) and you want to set the deletion ag, you
can change the system status in the Change Maintenance Order app accordingly. The relevant order is then passed on to the
Deletion Flag (Order) subphase of the Completion phase, provided that it is not yet in this phase.

Related Information
Find Maintenance Orders
Maintenance Order

Representing Work in Maintenance Orders

This is custom documentation. For more information, please visit the SAP Help Portal 221
 7/16/2023
As a maintenance planner, you plan maintenance tasks on a speci c reference object in the maintenance order. These
maintenance tasks can be performed internally or externally (lean services, external operations) and are described in order
operations and suboperations. The following topics support you in optimizing the way in which you represent maintenance work
in order operations and suboperations. To ensure the maximum bene t out of the monitoring options that the phase model
offers, you need to organize the necessary maintenance work in a speci c way. Only then the phases and subphases support you
in monitoring the performance of individual maintenance tasks:

Organizing Internal Maintenance Work

Organizing External Maintenance Work

Organizing Internal and External Maintenance Work

Organizing Internal Maintenance Work

If you process the maintenance order internally, the maintenance tasks are performed by your own maintenance technicians. An
internally performed order operation or suboperation makes reference to a work center that is responsible for its execution.
You can plan the necessary capacity requirements in the operation and suboperation.

Planning Internal Work in One Single Order Operation

In the simplest case, only one work center is involved in the maintenance work and you plan the maintenance task in one order
operation. In the phase model, system statuses and subphases allow you to monitor the progress of the maintenance work.

The order operation is passed to the Work in Execution subphase if the maintenance technician indicates that he has
started the work or if he posts a partial time con rmation.

The order operation is passed to the Work Finished subphase if the maintenance technician indicates the end of the work
or if he posts a nal time con rmation.

The following overview shows business transactions during the Execution and Post Execution phase and the impact on the
system statuses and subphases.

Internal Maintenance Work Documented in One Single Operation

Business Role Business Transaction Resulting System Status of the Resulting Subphase and Phase
Operation of the Operation

Maintenance Planner You dispatch the order DSPT (Scheduled) Subphase: Ready for Execution
operation.
Phase: Execution

Maintenance Technician You indicate that you are JIPR (Job in Process) Subphase: Work in Execution
starting the maintenance work
Phase: Execution
on the order operation

Maintenance Technician You post a partial time PCNF (Partially Con rmed) Subphase: Work in Execution
con rmation.
Maintenance Planner Phase: Execution

Maintenance Technician You indicate that you have Subphase: Work Finished
JBFI (Job Finished)
nished your work without
Phase: Post Execution
posting a nal time PWF (Planned Work
con rmation. Finished)

This is custom documentation. For more information, please visit the SAP Help Portal 222
 7/16/2023

Business Role Business Transaction Resulting System Status of the Resulting Subphase and Phase
Operation of the Operation

Maintenance Technician You post a nal time Subphase: Work Finished

CNF (Con rmed)
con rmation.
Maintenance Planner Phase: Post Execution
PWF (Planned Work
Finished)

Planning Internal Work in Several Operations and Suboperations

If the maintenance work is more complex, several work centers might be involved. You can follow two different approaches to
plan the maintenance execution in several operations or suboperations:

You determine the maintenance work in the Planned Work eld of the order operation itself. In this case, any
suboperations that you might create for this order operation have an independent system status and also are passed to
the next subphase independently. This means that the order operation does not provide any information about the work
progress of the corresponding suboperations.

You use the order operation as an organizational element that includes all stock components and non-stock materials
that are needed for the maintenance work. Furthermore, you plan all the maintenance work in the corresponding
suboperations. If different technicians are involved in the same order operation and you want to monitor the progress of
the individual maintenance tasks, you might create one suboperation for each maintenance task and technician. If you
plan the maintenance work in the suboperations only, the status and subphase of the order operation indicates the
progress of the maintenance work because the system status and phase of the order operation is derived from its
suboperations.

The following table indicates how system statuses and subphases support you in monitoring the progress of the maintenance
work. It is based on the assumption that you have planned the maintenance order as follows:

The maintenance order has one operation with several suboperations. You have planned the internal maintenance work
only in the suboperations.

Consequently, the corresponding order operation has no working hours and no lean services assigned.

In this case, the status and phase of the order operation is derived from its suboperations in the following way:

The order operation is passed to the Ready for Execution subphase as soon as at least one of its suboperations is passed
on to this subphase.

The order operation is passed to the Work in Execution subphase as soon as at least one of its suboperations is passed
on to this subphase.

The order operation is passed to the Work in Execution subphase if all suboperations are still in the Ready for Execution
subphase and you post a nal time con rmation for one of the suboperations.

The order operation stays in the Execution phase as long as there are any suboperations left that have not yet been set
to JBFI (Job Finished) or have not been con rmed with CNF (Con rmed). This means that the order operation is not
passed to the Work Finished subphase before all suboperations have been set to PWF (Planned Work Finished).

Internal Maintenance Work Documented in Several Suboperations

Business Role Business Transaction Resulting System Status of the Resulting Subphase and Phase
Suboperation and Operation of the Suboperation and
Operation

This is custom documentation. For more information, please visit the SAP Help Portal 223
 7/16/2023

Business Role Business Transaction Resulting System Status of the Resulting Subphase and Phase
Suboperation and Operation of the Suboperation and
Operation

Maintenance Planner You dispatch all the order DSPT (Scheduled) Subphase: Ready for Execution
operations including the
Phase: Execution
suboperations.

Maintenance Planner You have an additional license Individual Order Suboperation Subphase: Ready for Execution
for Resource Scheduling and and Corresponding Order
Phase: Execution
dispatch individual order Operation: DSPT (Scheduled)
operations and suboperations.

Maintenance Technician You indicate that you are Order Suboperation and Subphase: Work in Execution
starting the maintenance work Corresponding Order Operation:
Phase: Execution
on one individual order JIPR (Job in Process)
suboperation with execution
stage MAIN.

Maintenance Technician You post a partial time Order Suboperation: PCNF Subphase: Work in Execution
con rmation for one selected (Partially Con rmed)
Phase: Execution
order suboperation.
Corresponding Order Operation:
SPCF (Suboperation Partially
Con rmed)

Maintenance Technician You indicate that you have Individual Order Suboperation:
Suboperation:
nished your work on one
JBFI (Job Finished)
individual order suboperation Subphase: Work
without posting a nal time PWF (Planned Work Finished
con rmation. Finished)
Phase: Post Execution
Since there are still
Operation:
suboperations with maintenance
work to be performed, the Subphase: Work in
corresponding order operation Execution
remains in system status JIPR
(Job in Process). Phase: Execution

Maintenance Technician You have indicated for all All Order Suboperations: Subphase: Work Finished
suboperations that you have
JBFI (Job Finished) Phase: Post Execution
nished the maintenance work
without posting a nal time PWF (Planned Work
con rmation. Finished)

Order Operation:

PWF (Planned Work

Finished)

This is custom documentation. For more information, please visit the SAP Help Portal 224
 7/16/2023

Business Role Business Transaction Resulting System Status of the Resulting Subphase and Phase
Suboperation and Operation of the Suboperation and
Operation

Maintenance Technician You post a nal time Order Suboperation:

Suboperation:
con rmation for one individual
CNF (Con rmed)
order suboperation Subphase: Work
PWF (Planned Work Finished
Finished)
Phase: Post Execution
Order Operation:
Operation (depends on
If there are still remaining
suboperations with suboperations):
maintenance work to be
Subphase: Work in
performed: JIPR (Job in
Execution (Phase:
Process)
Execution ) or
If all suboperations have Subphase: Work
already been set to JBFI Finished (Phase: Post
(Job Finished): Execution )

PWF (Planned
Work Finished)

SPCF
(Suboperation
Partially
Con rmed)

Maintenance Technician You have posted a nal time All Order Suboperations: Subphase: Work Finished
con rmation for all the
CNF (Con rmed) Phase: Post Execution
suboperations of an order
operation. PWF (Planned Work
Finished)

Corresponding Order Operation:

The system removes

the status SPCF
(Suboperation Partially
Con rmed)

The system adds the

status SCNF
(Suboperation Finally
Con rmed) to indicate
that nal time
con rmations have been
posted for all
suboperations.

The system adds the

status PWF (Planned
Work Finished).

Organizing External Maintenance Work

If you process the maintenance order externally, the maintenance tasks are performed by a service provider. You can plan
external maintenance work by adding lean services in the details of an order operation or by creating external order operations:

This is custom documentation. For more information, please visit the SAP Help Portal 225
 7/16/2023
You can add planned or unplanned lean services to an order operation or suboperation in the same way as non-stock
materials that you require for your maintenance work. Lean services differ from the material by their product type
(SERV). For more information, see Adding Lean Services.

You can plan individual order operations or suboperations to be performed externally by assigning the control key PM02
or a control key that you have con gured similarly to PM02. The duration of an external operation is calculated using
standard values or the planned delivery time.

As a maintenance planner, you need to monitor the procurement of the external services (lean services and external
operations) as well as the performance of maintenance work that is executed externally by a service provider.

Prerequisites
To enable the procurement of lean services, you have activated the Enhanced Procurement Mode for a combination of order
type and maintenance planning plant in Customizing for Plant Maintenance and Customer Service under Maintenance and
Service Processing Maintenance and Service Orders Functions and Settings for Order Types Procurement . If an order is
not con gured for lean service procurement, external services can only be entered as external operations.

The setting of speci c system statuses depends on changes in the purchase order and in the service entry sheet. To enable the
system to react to these changes and update the respective system statuses, you need to activate the following event type
linkages in Customizing for ABAP Platform under Application Server Business Management SAP Business Events
Con gure Event Type Linkages (transaction SWETYPV):

Event Type Linkages

Business Action Object Type Event Receiver Type

Create Purchase Order for Lean CL_MM_PUR_WF_OBJECT_PO Created LEANSERVICESTATUSES

Service

Change Purchase Order for Lean CL_MM_PUR_WF_OBJECT_PO Changed LEANSERVICESTATUSES

Service

Create Service Entry Sheet for CL_MM_PUR_WF_OBJECT_SES Created LEANSERVICESTATUSES

Lean Service

Change Service Entry Sheet for CL_MM_PUR_WF_OBJECT_SES Changed LEANSERVICESTATUSES

Lean Service

Post Goods Receipt for Lean CL_MMIM_MATDOC_EVENT Created LEANSERVICESTATUSES

Service

Post Goods Receipt for External CL_MMIM_MATDOC_EVENT Created EXTERNALDATASTATUSES

Operation

In the Details of the respective event type linkage entries, you need to make the following entries:

For event type linkage entries with the receiver type LEANSERVICESTATUSES enter
CL_EAM_ENTRYSHEET_EVNTRECEIVER as the class name for the receiver type.

For event type linkage entries with the receiver type EXTERNALDATASTATUSES enter
CL_EAM_EXT_DATA_GR_EVNTREC as the class name for the receiver type.

Make sure in the Details view that the Linkage Activated checkbox has been selected for the respective event type linkage.

Monitoring the Procurement of External Services

This is custom documentation. For more information, please visit the SAP Help Portal 226
 7/16/2023
You can monitor the procurement of external services (lean services and external operations) in the SAP Fiori apps Manage
Maintenance Backlog and Maintenance Backlog Overview. The system tracks the completion of several milestones, which
correspond to key points in the procurement process. Since timely completion of these milestones can be an indicator for
whether externally procured materials or services will be available by their planned requirement date, the system also
calculates a due date for each milestone based on this date.

By default, the system tracks the following procurement milestones:

Purchase Requisition Created

Purchase Requisition Released

Purchase Order Sent to Vendor

Order Con rmed by Vendor

For more information about procurement milestones, see Monitoring Procurement Activities.

Monitoring the Procurement of External Services

Business Role Business Transaction Resulting Milestone Completion of the

Operation

Maintenance Planner You have added several lean services to an The system marks the following
order operation, or you have created procurement milestones as completed:
external operations. Purchase requisitions
Purchase Requisition Created
and purchase orders have been created,
and the purchase orders have been sent to Purchase Requisition Released
the vendor.
Purchase Order Sent to Vendor

Service Provider The service providers con rm that they The system marks the procurement
have received the purchase orders. milestone Order Con rmed by Vendor as
completed.

Monitoring the Performance of External Maintenance Work - Lean Services

As a maintenance planner, you can add lean services to an order operation or suboperation. System statuses support you in
monitoring the performance of maintenance work that is executed externally by a service provider. The performance of the lean
service is recorded in the service entry sheet.

One Single Order Operation with Several Lean Services Assigned

Business Role Business Transaction Resulting System Status of the Resulting Subphase and Phase
Order Operation of the Operation

Service Performer The service performers submit

the service entry sheets to
partially con rm the
maintenance work that has
already been performed.

Responsible Person for You approve the submitted SEPC (Service Partially Subphase: Work in Execution
Approval (depending on the service entry sheets. The Con rmed)
Phase: Execution
work ow: probably the Person system creates goods receipts
This system status indicates
responsible that is determined for the external work that has
that at least one lean service
in the maintenance order been con rmed.
that has been assigned to the
header)
order operation has been
partially or nally con rmed.

This is custom documentation. For more information, please visit the SAP Help Portal 227
 7/16/2023

Business Role Business Transaction Resulting System Status of the Resulting Subphase and Phase
Order Operation of the Operation

Purchaser You set the lean service to SECF (Service Con rmed) Subphase: Work Finished
nally con rmed. You can
Service Performer This system status indicates Phase: Post Execution
nally con rm a lean service by
that all lean services of the
Responsible Person for performing one of the following
order operation have been
Approval (depending on the business transactions:
nally con rmed and that all
work ow: probably the Person
You mark the Delivery purchase order items for the
responsible that is determined
Completed indicator in lean services have been marked
in the maintenance order
the referenced purchase as Delivery Completed.
header)
order item. The lean
PWF (Planned Work Finished)
service is set to nally
con rmed even if no
The PWF system status
service entry sheets
indicates that all the planned
have been submitted.
maintenance work - be it
As a service performer, internal or external - has been
you submit a service nished. It causes the order
entry sheet and mark operation to be passed to the
the Final Entry indicator Work Finished subphase.
to nally con rm that
the planned work has
been nished. As the
responsible person for
the approval, you
approve this service
entry sheet.
Consequently, the
system sets the
Delivery Completed
indicator in the
referenced purchase
order item and the lean
service is nally
con rmed.

Monitoring the Performance of External Maintenance Work - External Operations

As a maintenance planner you can categorize order operations or suboperations as external operations and thereby determine
that the maintenance work is planned to be performed by an external service provider. To categorize an order operation as
external, you assign the control key PM02. System statuses support you in monitoring the performance of maintenance work
that is performed externally.

Maintenance Order with One Order Operation that is Categorized as External

Business Role Business Transaction Resulting System Status of the Resulting Subphase and Phase
Operation of the Operation

Purchaser You post a goods receipt for the EOPD (External Operation Subphase: Work in Execution
external operation to con rm Partially Delivered)
Phase: Execution
that the planned external work
has been partially performed.

This is custom documentation. For more information, please visit the SAP Help Portal 228
 7/16/2023

Business Role Business Transaction Resulting System Status of the Resulting Subphase and Phase
Operation of the Operation

Purchaser You post several goods receipts EODL (External Operation Subphase: Work Finished
mapping the planned quantity Delivered)
Phase: Post Execution
of the external operation. The
PWF (Planned Work Finished)
system marks the Delivery
Completed indicator in the On operation level, this system
referenced purchase order status indicates that all
items. maintenance work - be it
internal or external - has been
nished. The status causes the
order operation to be passed to
the Work Finished subphase.

The following table indicates how system statuses and subphases support you in monitoring the progress of the external
maintenance work if you have planned the maintenance order as follows:

The maintenance order has one operation with several suboperations. You have planned all the suboperations as
external operations.

Consequently, the corresponding order operation has no working hours and no lean services assigned.

Several Suboperations that are Categorized as External

Business Role Business Transaction Resulting System Status of the Resulting Subphase and Phase
Operation and Suboperation of the Operation and
Suboperation

Purchaser You post a goods receipt for one Suboperation: EOPD (External Subphase of Suboperation:
external suboperation to Operation Partially Delivered) Work in Execution
con rm that the planned
Phase of Suboperation:
external work has been partially
Execution
performed.

Purchaser You post several goods receipts Suboperation: EODL (External Subphase: Work Finished
mapping the planned quantity Operation Delivered)
Phase: Post Execution
of the external suboperations.
PWF (Planned Work Finished)
The system marks the Delivery
Completed indicator in the
Operation: PWF (Planned Work
referenced purchase order
Finished)
items.
On operation level, this system
status indicates that all
maintenance work - be it
internal or external - has been
nished. The status causes the
order operation or suboperation
to be passed to the Work
Finished subphase.

Organizing Internal and External Maintenance Work

The maintenance or repair work that you want to plan in a maintenance order might include tasks that are performed by your
maintenance technicians as well as tasks that need to be performed by external service providers.

For the prerequisites that apply when working with lean services, see Organizing External Maintenance Work.

This is custom documentation. For more information, please visit the SAP Help Portal 229
 7/16/2023
There are several possibilities to combine internal and external work within one single maintenance order:

You create an order operation to plan the internal work and add a lean service to this order operation.

You create an order operation to plan the internal work and plan the lean service in a suboperation.

You use the order operation as a kind of grouping operation and plan the internal work and the lean service in two
suboperations.

Internal and External Work in One Order Operation

If you create only one order operation and add the lean service to it, the phase model only provides a rough overview about the
work progress:

The order operation is passed to the Work in Execution subphase as soon as the internal or external work has been
started.

The order operation is passed to the Work Finished subphase as soon as the internal work has been set to JBFI (Job
Finished) or CNF (Con rmed) and the lean service has been set to SECF (Service Con rmed).

 Example
The order operation with internal work and a lean service assigned is in the subphase Work in Execution. This could mean the
following concerning the work progress:

Only internal work has been started

Only external work has been started

Internal and external work have been started

Internal work has been nished but external work is still in progress

External work has been nished but internal work is still in progress

The example shows that you need to monitor the work progress with the help of the system statuses or the received quantity if
you plan internal work and lean services within one operation.

Internal Work in the Operation and Lean Service in the Suboperation

If you plan the internal work in the order operation and the lean service in the suboperation, the subphases and phases of the
suboperation and operation are determined independently of each other. This means that the subphase of the operation does
not include any information about the work progress of the suboperation. For more information about internal and external
maintenance work, see Organizing Internal Maintenance Work, Organizing External Maintenance Work

Internal Work and Lean Service in Suboperations

If you plan the external and internal work in two separate suboperations and do not assign any working hours or lean services to
the operation itself, the subphases and phases of the suboperations provide a good overview over the work progress. In this
case, the operation serves as a kind of grouping element and has only stock materials and non-stock materials assigned.

Internal and External Work in Suboperations

Business Transaction Suboperation Lean Service Suboperation Internal Work Grouping Order Operation

This is custom documentation. For more information, please visit the SAP Help Portal 230
 7/16/2023

Business Transaction Suboperation Lean Service Suboperation Internal Work Grouping Order Operation

The service performer submits System Status: SEPC (Service System Status: DSPT Subphase: Work in Execution
the service entry sheet to Partially Con rmed) (Scheduled)
partially con rm the
maintenance work that has Subphase: Work in Execution Subphase: Ready for Execution
already been performed.

The responsible person

approves the service entry
sheet.

The internal work has not been

started yet.

As a maintenance technician, System Status: SEPC (Service System Status: JIPR (Job in System Status: JIPR (Job in
you select the suboperation that Partially Con rmed) Process) Process)
documents the internal work
and indicate that you start Subphase: Work in Execution Subphase: Work in Execution Subphase: Work in Execution
working.

You set the lean service to System Status: System Status: JIPR (Job in System Status: JIPR (Job in
nally con rmed. Process) Process)
SECF (Service
The internal work is still in Con rmed) Subphase: Work in Execution Subphase: Work in Execution
execution.
PWF (Planned Work
Finished)

Subphase: Work Finished

You nally con rm that the System Status: System Status: System Status: PWF (Planned
internal work has been nished. Work Finished)
This means that all the planned SECF (Service JBFI (Job Finished)
work has been nally con rmed. Con rmed) Subphase: Work Finished
PWF (Planned Work
PWF (Planned Work Finished)
Finished)
Subphase: Work Finished
Subphase: Work Finished

Monitoring Procurement Activities

As a maintenance planner, you can monitor the availability status of non-stock components and services (external operations
and lean services) in the Manage Maintenance Backlog app and the Maintenance Backlog Overview app.

For this purpose, the system tracks several milestones in the procurement process. They mark the completion of the following
important procurement activities:

Procurement Activity Procurement Milestone

Create Purchase Requisition Purchase Requisition Created

Release Purchase Requisition Purchase Requisition Released

Send Purchase Order to Vendor Purchase Order Sent to Vendor

Receive Purchase Order Con rmation Order Con rmed by Vendor

Receive Shipment Con rmation Order Shipped

Receive Shipment Order Received in Full

This is custom documentation. For more information, please visit the SAP Help Portal 231
 7/16/2023

 Note
The milestones Order Shipped and Order Received in Full are only monitored for non-stock components.

For more information about procurement milestones, including prerequisites, con guration options and detailed descriptions of
how the system creates these milestones, calculates their due dates, and marks them as completed, see Procurement
Milestones.

Manage Maintenance Backlog

The Manage Maintenance Backlog app allows you to monitor the procurement status of the non-stock components, lean
services, and external operations that are assigned to the orders in a maintenance planning bucket.

For this purpose, the procurement milestones are represented by colored status symbols on the Non-Stock Components and
Services tab pages. The status symbols allow you to identify potential delays in the procurement process and take the
appropriate actions:

A green symbol indicates that the procurement activity to reach the milestone is pending completion and the warning
period before the milestone due date has not started. With the standard con guration, this means that there are more
than two days left to complete the activity by the milestone due date. Completed milestones are also green.

A yellow symbol indicates that the procurement activity to reach the milestone is pending completion and the warning
period has started. With the standard con guration, this means that there are two days or less left to complete the
activity by the milestone due date.

A red symbol indicates that the procurement activity to reach the milestone is pending completion and the milestone
due date has been reached or passed.

A gray symbol indicates that the procurement activity to reach the milestone is not yet pending completion or that the
milestone has not been created by the system. Depending on the procurement scenario, not all available milestones are
actually created by the system. For example, if the procurement process begins with the creation of a purchase order
which is then linked with a maintenance order, it is not necessary to monitor the creation and the release of the
purchase requisition. As a result, no milestones are created for these activities and the corresponding status symbols
are gray.

For more information about this app, see Manage Maintenance Backlog.

Maintenance Backlog Overview

When you select a range of planning buckets in the Maintenance Backlog Overview app, the stacked bar chart on the External
Procurement card shows the total number of non-stock components and services for which a procurement activity is due within
the time period of each selected planning bucket – even if the corresponding maintenance orders fall into different planning
buckets based on their scheduled start and end.

 Example
A maintenance order is scheduled for execution in October and is therefore assigned to the planning bucket for calendar
week 40. However, one of the non-stock components has to be ordered 6 months before it can be shipped. Therefore, the
milestone Order Sent to Vendor has to be completed in calendar week 14. The component is displayed in the planning bucket
for calendar week 14, although the corresponding maintenance order is assigned to the planning bucket for calendar week
40.

The following graphic provides an example of this bar chart with a range of six planning buckets:

This is custom documentation. For more information, please visit the SAP Help Portal 232
 7/16/2023

Each bar in the chart represents one planning bucket and covers the time period of that planning bucket. However, the rst bar
in the sequence also covers the time period of any further planning buckets that have been generated from the planning bucket
template in the past, and the last bar in the sequence also covers the time period of any further planning buckets that have
been generated from the planning bucket template in the future. This way, you can monitor the procurement status of all the
non-stock components and lean services in an entire series of planning buckets, even if they are not included in your current
selection. By clicking on the corresponding chart sections, you can navigate directly to the relevant apps to manage your
procurement activities, for example to follow up on the approval of open purchase requisitions.

For more information about this app, see Maintenance Backlog Overview.

Related Information
Procurement Milestones
Manage Maintenance Backlog
Maintenance Backlog Overview

Procurement Milestones
To ensure that maintenance orders can be scheduled for execution as planned, you can closely monitor the availability status of
required non-stock components and services (lean services and external operations). For this purpose, the system creates and
tracks the completion of several milestones in the procurement process.

Prerequisites
The completion of several procurement milestones depends on changes in the purchase order and, for non-stock components,
the posting of the goods receipt. To enable the system to react to these changes and update the respective milestones
automatically, several event type linkages must be activated in your system. To activate the relevant event type linkages in your
system, you can use the Customizing activity Activate Event Type Linkage for Procurement Milestones in the SAP Reference
IMG under Plant Maintenance and Customer Service Maintenance and Service Processing Maintenance and Service
Orders Functions and Settings for Order Types Procurement . The relevant entries and settings are precon gured in client
000. By performing a table adjustment, you can copy the entries to your system. Make sure that the Linkage Activated
checkbox is selected in the Details of each entry.

Procurement Scenarios

This is custom documentation. For more information, please visit the SAP Help Portal 233
 7/16/2023
The system distinguishes between two procurement scenarios, which have an impact on the number of procurement
milestones that are created and how the system determines their completion:

Planned procurement: The procurement process begins with the creation of a purchase requisition from within a
maintenance order.

Unplanned procurement: The procurement process begins with the creation of a purchase order, which is then linked
with a maintenance order.

Creation of Procurement Milestones

When you plan the non-stock components, lean services, and external operations that are required to execute a maintenance
order, the system determines which procurement activities must be performed in each case and then creates the
corresponding procurement milestones. It also determines a requirement date for each component or service.

Procurement Scenario Business Transaction Resulting Milestones Requirement Date

Planned procurement You add a non-stock component Purchase Requisition Corresponds to the requirement
to an order operation. Created date of the component or
service.
Purchase Requisition
Released

Purchase Order Sent to

Vendor

Order Con rmed by

Vendor

Order Shipped

Order Received in Full

You add a lean service to an Purchase Requisition

order operation or suboperation. Created

Purchase Requisition
Released

Purchase Order Sent to

Vendor

Order Con rmed by

Vendor

You create an external operation. Purchase Requisition Derived from the scheduled
Created dates of the operation.

Purchase Requisition
Released

Purchase Order Sent to

Vendor

Order Con rmed by

Vendor

This is custom documentation. For more information, please visit the SAP Help Portal 234
 7/16/2023

Procurement Scenario Business Transaction Resulting Milestones Requirement Date

Unplanned procurement You specify a maintenance order Purchase Order Sent to Derived from the scheduled
as account assignment for a Vendor start date of the maintenance
non-stock component in a order.
Order Con rmed by
purchase order.
Vendor

Order Shipped

Order Received in Full

You specify a maintenance order Purchase Order Sent to

as account assignment for a Vendor
lean service in a purchase order.
Order Con rmed by
Vendor

Calculation of the Milestone Due Date

After creating the milestones for a component or service, the system determines a due date for each milestone. The due date
corresponds to the date on which each milestone should be completed if the component or service is to be available on the
planned requirement date. The due date enables the system to indicate potential delays in the procurement process, for
example in the Manage Maintenance Backlog app. The calculation is performed backwards, starting from the planned
requirement date. When the requirement date changes, the system recalculates the due date.

The following graphic illustrates at which point in time each milestone should be completed:

The following table explains how the system calculates a due date for each milestone and where it obtains the data on which
the calculation is based. Note that the order of the milestones is reversed to illustrate the backward calculation based on the
requirement date:

Procurement Milestone Calculation of the Due Date Relevant Information

Order Received in Full The system subtracts the goods receipt Planned procurement: The system uses
processing time from the requirement date. the goods receipt processing time that is
maintained in the maintenance order.

Unplanned procurement: The system uses

the goods receipt processing time that is
maintained in the purchase order.

This is custom documentation. For more information, please visit the SAP Help Portal 235
 7/16/2023

Procurement Milestone Calculation of the Due Date Relevant Information

Order Shipped The calculation is based on the planned Planned procurement: The system uses
delivery date: If a negative value has been the planned delivery time that is
maintained as the second reminder in the maintained in the maintenance order to
purchasing values of the purchasing info calculate the planned delivery date.
record or the material master record, the
Unplanned procurement: The system uses
system subtracts this value from the
the delivery date that is maintained in the
planned delivery date. Otherwise, the due
purchase order.
date is set to 20% of the planned delivery
date. For example, if the delivery is planned
for May 10, the due date for the order
shipment would be May 8.

Order Con rmed by Vendor The calculation is based on the planned

delivery date: If purchasing has maintained
a negative value as the rst reminder in the
purchasing values of the purchasing info
record or the material master record, the
system subtracts this value from the
planned delivery date. Otherwise, the due
date is set to 50% of the planned delivery
date. For example, if the delivery is planned
for May 10, the due date for the order
con rmation would be May 5.

Purchase Order Sent to Vendor The purchasing department processing The system uses the purchasing
time for the plant is added to the purchase department processing time for the
requisition release date. relevant plant that has been maintained in
Customizing for Production under Material
Requirements PlanningPlant
ParametersCarry Out Overall Maintenance
of Plant Parameters.

The purchase requisition release date is

calculated automatically by subtracting the
goods receipt processing time, the planned
delivery time, and the purchasing
department processing time for the plant
from the requirement date.

Purchase Requisition Released The due date corresponds to the purchase The purchase requisition release date is
requisition release date calculated automatically by subtracting the
goods receipt processing time, the planned
delivery time, and the purchasing
Purchase Requisition Created The due date is 2 days before the purchase
department processing time for the plant
requisition release date.
from the requirement date.

 Tip
The procurement status can only be displayed reliably if all the information that the system needs to calculate the milestone
due date is maintained correctly. For optimum results, we recommend the following:

Maintain a goods receipt processing time in the material master record of your products.

Maintain a planned delivery time in the material master record of your products. You can also specify a different
delivery time in the purchasing info record for a speci c material/supplier combination.

Maintain the purchasing department processing time for each relevant plant in Customizing for Production under
Material Requirements PlanningPlant ParametersCarry Out Overall Maintenance of Plant Parameters.

This is custom documentation. For more information, please visit the SAP Help Portal 236
 7/16/2023

Completion of Procurement Milestones

The completion of each procurement milestone is triggered by certain events or actions. At the same time, speci c conditions
must be ful lled. The following graphic summarizes these actions and conditions:

The following table explains how the system completes each milestone for non-stock components and services and which
conditions must be ful lled in the different procurement scenarios:

Procurement Milestone Event that Triggers the Conditions for Planned Conditions for Unplanned
Milestone Completion Procurement Procurement

This is custom documentation. For more information, please visit the SAP Help Portal 237
 7/16/2023

Procurement Milestone Event that Triggers the Conditions for Planned Conditions for Unplanned
Milestone Completion Procurement Procurement

Purchase Requisition Created The purchase requisition is The creation of the purchase This milestone does not exist in
created. requisition depends on the this procurement scenario.
value that is maintained in the
Reservation/Purchase
Requisition table column of the
component or service in the
maintenance order:

Immediately: The
purchase requisition is
generated when you
save the order.

From release: The

purchase requisition is
generated when you
release the order.

Never: The system

doesn't generate a
purchase requisition.

If this milestone does not get

completed, check the value in
this table column.

Purchase Requisition Released The purchase requisition is Releasing a purchase requisition This milestone does not exist in
released. requires an approval step. this procurement scenario.
Depending on your system
settings, this approval can
either be performed
automatically or manually by a
responsible approver.

If this milestone does not get

completed, check the Approval
Details of the purchase
requisition item.

Purchase Order Sent to Vendor The purchase order is marked Components: Components:
as Sent.
The quantity stated in The delivery date
If output management is the purchase order must stated in the purchase
enabled, the purchase order is not be lower than the order must be on or
marked as sent automatically quantity stated in the before the due date for
when you print it. maintenance order. the milestone Order
Received in Full.
The delivery date stated
in the purchase order
must be on or before the
due date of the
milestone Order
Received in Full.

This is custom documentation. For more information, please visit the SAP Help Portal 238
 7/16/2023

Procurement Milestone Event that Triggers the Conditions for Planned Conditions for Unplanned
Milestone Completion Procurement Procurement

Services: Services:

The start and end date No additional conditions are

of a lean service must applicable in this procurement
be between the earliest scenario.
start date and the latest
end date of the
corresponding
operation.

The start and end date

of an external operation
must be between the
scheduled start date
and the scheduled end
date of the maintenance
order. If scheduled
dates are not available,
the start and end date
must be between the
basic start date and the
basic end date of the
maintenance order.

The quantity stated in

the purchase order must
not be lower than the
quantity stated in the
maintenance order.

Order Con rmed by Vendor One or more order Components: Components:

acknowledgments for the entire
The delivery date The delivery date
requirement quantity have been
indicated in the order indicated in the order
entered in the purchase order.
acknowledgements acknowledgements
must be on or before the must be on or before
delivery date speci ed the delivery date
in the maintenance speci ed in the
order. purchase order.

This is custom documentation. For more information, please visit the SAP Help Portal 239
 7/16/2023

Procurement Milestone Event that Triggers the Conditions for Planned Conditions for Unplanned
Milestone Completion Procurement Procurement

Services: Services:

The start and end date The start and end date
of a lean service must of the lean service must
be between the earliest be between the
start date and the latest scheduled start date
end date of the and the scheduled end
corresponding date of the maintenance
operation. order. If scheduled
dates are not available,
The start and end date
the start and end date
of an external operation
must be between the
must be between the
basic start date and the
scheduled start date
basic end date of the
and the scheduled end
maintenance order.
date of the maintenance
order. If scheduled
dates are not available,
the start and end date
must be between the
basic start date and the
basic end date of the
maintenance order.

The quantity stated in

the purchase order must
not be lower than the
quantity stated in the
maintenance order.

Order Shipped Option 1: The Delivery If shipping noti cations are If shipping noti cations are
Completed checkbox is entered, the following conditions entered, the following
selected in the purchase order. apply: conditions apply:

Option 2: One or more shipping The delivery date in The delivery date in
noti cations for the entire each shipping each shipping
requirement quantity have been noti cation must be on noti cation must be on
entered in the purchase order. or before the delivery or before the delivery
date speci ed in the date speci ed in the
maintenance order. purchase order.

Order Received in Full One or more goods receipts The maintenance order must be No additional conditions are
have been posted for the entire released to post goods receipts. applicable in this procurement
requirement quantity. scenario.

 Note
If you have activated the corresponding event type linkages in Customizing, the milestones Purchase Order Sent to Vendor,
Order Con rmed by Vendor, Order Shipped, and Order Received in Full are updated automatically upon completion. The
milestones Purchase Requisition Created and Purchase Requisition Released are updated when the maintenance order is
saved. If you do not activate one or more event type linkages, the corresponding procurement milestones will only be
updated when the maintenance order is opened in change mode and saved again the next time.

 Tip
To ensure that the procurement status can be displayed correctly, the required actions must be performed reliably and meet
the conditions detailed in the table. You can use the External Procurement card in the Maintenance Backlog Overview app

This is custom documentation. For more information, please visit the SAP Help Portal 240
 7/16/2023
for this purpose. For more information, see Maintenance Backlog Overview.

Optional Con guration

You can de ne custom rules to restrict which milestones are monitored for a combination of maintenance order type,
maintenance planning plant, maintenance plant, material group, and procurement demand category (non-stock components,
lean services, and/or external operations).

You can also change the default warning period for the milestone due date. The warning period speci es the time period
between the date on which a milestone becomes due and the date on which the system starts to display the procurement
status in the Manage Maintenance Backlog app as a warning. By default, the warning period is two days before the milestone
due date.

To change the default settings, you can de ne custom rules in Customizing for Plant Maintenance and Customer Service under
Maintenance and Service Processing Maintenance and Service Orders Functions and Settings for Order Types
Procurement De ne Assignment Rules for Procurement Milestones .

Resource Scheduling
Resource scheduling provides you with insights into your maintenance workload and available capacities for current and
upcoming maintenance activities. Use the apps for resource scheduling to check current and forecasted work center utilization,
build schedules, and determine required capacities before dispatching the scheduled work.

 Note
Resource scheduling requires a separate license. For more information, please get in touch with your SAP Account Executive.

Key Bene ts
Gain insights into current and forecasted workloads

Identify due and overdue maintenance orders quickly and build an optimal schedule before dispatching maintenance
order operations for execution.

Optimize the use of maintenance resources

Control weekly maintenance workloads by adjusting the scope of your schedule and distribute the work evenly across
your work centers.

Reduce asset downtime and increase productivity

Group and schedule maintenance orders by asset, consider work that requires planned downtime, and identify
relationships between order operations.

How to Get Started with Resource Scheduling

After your key user assigned the required business role to you, the resource scheduling apps are available in your SAP Fiori
launchpad.

The following interactive overview shows you how to get started with resource scheduling.

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

This is custom documentation. For more information, please visit the SAP Help Portal 241
 7/16/2023

Please note that image maps are not interactive in PDF output.

What You Can Do with Resource Scheduling

The following interactive overview shows the main tasks that you can perform using the resource scheduling apps. Hover over a
box for a short description and click to navigate to more detailed information.

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

Please note that image maps are not interactive in PDF output.

Related Information
Information for Key Users
SAP Fiori Apps Reference Library

This is custom documentation. For more information, please visit the SAP Help Portal 242