C_S43_2023 Questions and Answers

 A maintenance request within the phase-based process differs from a maintenance notification in the standard process in that it contains an additional screening phase where requests can be acceptedor rejected. In the standard process, a maintenance notification is created and processed without any screening. In the phase-based process, a maintenance request is created and submitted for screening. The screening phase allows the supervisor to review the request and decide whether to accept it or reject it. If the request is accepted, it becomes a maintenance notification and moves to the planning phase. If the request is rejected, it is closed and no further action is taken1.

The other options are incorrect because:

A maintenance request does not always use the risk-based assessment for prioritization. It can also use a predefined priority list2.

A maintenance request is not a new business object with no connection to a maintenance notification. It is a maintenance notification that is in the initiation or screening phase3.

It is not mandatory to assign a task list to the maintenance request. A task list can be assigned to the maintenance order in the planning phase4.

References: Explaining the Phase-based Process, New Phase Model for the Maintenance Processes in S/4HANA Cloud, SAP S/4HANA Cloud release of 2011 – Asset Management (Maintenance Management), Introducing Reactive Maintenance (4HH)

 The Report and Repair Malfunction app is a Fiori app that uses SAPUI5 as the UI technology. SAPUI5 is a modern, HTML5-based, JavaScript UI library that enables developers to create rich and responsive web applications. Web Dynpro, SAP GUI for HTML, and Business Server Pages are older UI technologies that are not used for Fiori apps. References:

Report and Repair Malfunction | SAP Help Portal

First Fiori App for Maintenance Technician: “Report and Repair Malfunction” for SAP S/4HANA Cloud 1708 and 1709 | SAP Blogs

The Maintenance Planning Overview app allows the planner to analyze critical factors in a chosen reference period, such as outstanding notifications, maintenance orders, purchase requisitions, and purchase orders. The app displays the data in multiple cards that show the number of objects and their status. The planner can use the default filters or adapt them according to their needs.

The activities that the planner can perform by using the app with the default filters are:

Display approved purchase requisitions for which NO purchase orders have been generated. This is shown in the card “Purchase Requisitions Not Released” which displays the number of purchase requisitions that have been approved but not converted into purchase orders. The planner can navigate to the list of purchase requisitions and take further actions, such as creating purchase orders or changing the requirement date.

Analyze overdue maintenance orders that have NOT been finally confirmed. This is shown in the card “Overdue Orders” which displays the number of maintenance orders that have been released but not completed within the planned end date. The planner can navigate to the list of overdue orders and check the status of the operations, confirmations, and goods movements.

Analyze maintenance orders that are still in planning and have NOT been released. This is shown in the card “Orders in Planning” which displays the number of maintenance orders that have not been released for execution. The planner can navigate to the list of orders in planning and complete the planning activities, such as assigning task lists, materials, and resources.

The activities that the planner cannot perform by using the app with the default filters are:

Display approved purchase requisitions for which purchase orders have been generated. This is not shown in any of the cards in the app. The planner can use the app “Manage Purchase Requisitions” to display this information.

Analyze confirmed maintenance orders that have NOT been settled. This is not shown in any of the cards in the app. The planner can use the app “Maintenance Order Costs Analysis” to display this information.

References:

SAP S/4HANA : New app in Plant Maintenance (Asset Management) – Maintenance Planning Overview

Highlights for Asset Management in SAP S/4HANA 2021

Maintenance Management | SAP Help Portal

 To set up a scenario for regular maintenance, the first event should take place after 1 year, and after that, it is a regular cycle of 6 months, you have to use the maintenance package offset parameter to map this in the system. The maintenance package offset is used to define the time interval between the start of the maintenance plan and the first call date of the maintenance package1. A maintenance package is a set of data that defines the frequency and scope of the maintenance tasks2.

For example, if you want to create a maintenance plan with two maintenance packages, one for annual inspection and one for semi-annual inspection, you can use the following settings:

Maintenance package 1: Cycle length = 12 months, Offset = 0 months, Scheduling indicator = Time-based

Maintenance package 2: Cycle length = 6 months, Offset = 12 months, Scheduling indicator = Time-based

This means that the first maintenance package will be called at the start of the maintenance plan, and then every 12 months thereafter. The second maintenance package will be called after 12 months from the start of the maintenance plan, and then every 6 months thereafter.

The other parameters that are not relevant for this scenario are:

Package hierarchy: This is used to define the relationship between different maintenance packages within a maintenance plan. It allows you to create nested or parallel maintenance packages that are dependent on each other3.

Scheduling indicator: This is used to define the type of scheduling for the maintenance package, such as time-based, performance-based, or condition-based4.

Cycle modification factor: This is used to modify the cycle length of the maintenance package by a certain percentage or factor5.

References: 1: SAP Help Portal - Maintenance Package Offset 2: SAP Help Portal - Maintenance Package 3: SAP Help Portal - Package Hierarchy 4: SAP Help Portal - Scheduling Indicator 5: SAPHelp Portal - Cycle Modification Factor

To set up Inspection Checklist processing, you need to customize the following settings:

Maintain settings at plant level for usage decisions. This is required to define the default values for the usage decision codes and the follow-up actions for the inspection lots. You can do this by using the customizing activity ‘Default Setting at Plant Level’ under 'Quality Management→Quality Inspection→Inspection Lot Completion→Maintain Default Values for Usage Decisions’1.

Assign an Inspection Type to a Maintenance Order Type and a Planning Plant. This is required to enable the creation of inspection lots for the maintenance orders. You can do this by using the customizing activity ‘Assign Inspection Type to Maintenance Order Type’ under 'Plant Maintenance and Customer Service→Maintenance and Service Processing→Maintenance and Service Orders→Functions and Settings for Order Types→Assign Inspection Type to Maintenance Order Type’2.

You do not need to create a control key which expects inspection characteristic assignments or assign an Inspection Type to a Maintenance Order Type only. These are not relevant settings for the Inspection Checklist processing. References:

Set up your SAP S/4HANA system for EAM Inspection Checklists

Explaining Inspection Checklists - SAP Learning

Non-stock materials are materials that are not kept in stock, but are procured externally as required1. They can be maintained in the material master as service products (product type SERV). You can add non-stock materials to an operation or suboperation as a component. The system creates a purchase requisition and a purchase order in the same way as for non-stock materials that you procure externally1.

Among the given options, the following are possible for non-stock materials in a released maintenance order:

A purchase requisition can be created automatically as soon as the order is saved. This is the default behavior for non-stock materials, unless you change the configuration settings2.

The maintenance order can be set to TECO (technically completed) before the invoice is created. This is possible if you use the compatibility mode for external procurement, which allows you to technically complete the order even if there are open purchase requisitions or purchase orders2.

A goods receipt can be posted after the maintenance order is technically completed. This is possible if you use the enhanced mode for external procurement, which allows you to post goods receipts for non-stock materials after the order is technically completed2.

The following options are not possible for non-stock materials in a released maintenance order:

A purchase order is created automatically as soon as the order is saved. This is not possible, as the purchase order requires manual processing and approval after the purchase requisition is created2.

A purchase requisition will ALWAYS be created as soon as the order is saved. This is not always true, as you can change the configuration settings to create the purchase requisition manually or at a later point in time2.

Therefore, the correct answers are A, B, and C. References: 1: What’s New in SAP S/4HANA 2021 - SAP Online Help 2: How to Configure SAP S/4HANA Asset Maintenance Subcontracting - SAP PRESS

 External refurbishment is the process of sending defective or worn-out spare parts to an external vendor for repair or replacement. To carry out this process, you need to create a maintenance order with an external operation that has the subcontracting indicator activated. This indicator allows you to create a purchase requisition and a purchase order for the external service. The external operation also requires an external work center, a control key, and a material component with the valuation type of the defective part. The order type for external refurbishment is not a prerequisite, but a configuration option that can be used to differentiate the process from internal refurbishment. The material group for externally refurbished materials is not relevant for the process, as the material master data is not changed by the refurbishment. The assignment of an external work center to a maintenance order operation is necessary, but not sufficient, for external refurbishment. You also need to activate the subcontracting indicator in the external activity. References:

Explaining Refurbishment of Spare Parts, section “Refurbishing Spare Parts Externally”

Refurbishment of Repairable Spares: Integration between SAP-PM and SAP-MM, section “4.2 External Refurbishment: Major Steps”

A SAP Fiori tile group is a subset of apps from one or more catalogs that are displayed on the user’s entry page of the SAP Fiori launchpad1. A tile group has the following characteristics:

It is based on an SAP Fiori tile catalog. A catalog is a logical group of apps or tiles that defines the set of all tiles that users can use to personalize the home page2. A group can contain apps from different catalogs, depending on the user’s role and authorization1.

It can be assigned directly to the user via personalization. The user can personalize the entry page by adding or removing apps to pre-delivered groups or self-defined groups2. The user can also reorder the groups and tiles according to their preference1.

It does not provide only HTML5-based apps. A tile group can contain apps that are based on different technologies, such as SAPUI5, Web Dynpro ABAP, or SAP GUI transactions1.

It is not assigned via a portal role. A tile group is assigned to the user’s role via the SAP Role Maintenance transaction PFCG2. A portal role is a different concept that is used in the SAP Enterprise Portal to define the access rights and content for portal users.

References: Configure the Fiori Launchpad Tiles using Catalogs & Groups, Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad, [Portal Roles]

 A maintenance plant is the organizational unit in which the technical objects to be maintained are physically present. A maintenance plant can be directly assigned to the following objects:

A maintenance work center, which is a location where maintenance tasks are performed. A maintenance work center can be a person, a group of persons, or a technical object, such as a machine or a vehicle. A maintenance work center is defined by its capacity, availability, and cost rates1

A storage location, which is a place where spare parts and materials are stored within a plant. A storage location can be a warehouse, a bin, or a shelf. A storage location is defined by its address, stock type, and valuation area2

The other options are incorrect because:

A maintenance planner group, which is a group of planners who are responsible for planning maintenance activities in a maintenance planning plant. A maintenance planner group is not directly assigned to a maintenance plant, but to a maintenance planning plant. A maintenance planning plant is the organizational unit in which maintenance requirements are planned3

An organizational unit, which is a generic term for any unit of an organization that performs a specific function or task. An organizational unit can be a company code, a plant, a sales organization, a purchasing organization, etc. An organizational unit is not directly assigned to a maintenance plant, but to a higher-level organizational unit, such as a company code or a controlling area.

References: 1: Maintenance Work Center | SAP Help Portal 2: Storage Location | SAP Help Portal 3: Maintenance Planner Group | SAP Help Portal : Organizational Unit | SAP Help Portal

Orders with Operation Account Assignment (OAA) are a special type of PM/CS orders that allow the detailed planning, capture and reporting of costs at the order operation level. The operations have their own settlement rules enabling more accurate cost updating of multiple assets maintained using a single PM/CS order. The mandatory characteristics of OAA orders are:

A technical object must be assigned to an order operation. This ensures that the operation is linked to a specific asset and can be settled accordingly. The technical object can be an equipment, a functional location, or a material.

Costs are stored only for the operation object. This means that the order header does not have any costs associated with it. The costs are allocated to the operations based on the actual postings of goods movements, confirmations, and invoices.

Purchase requisitions have the operation as account assignment. This means that the purchase requisitions created from the order components are assigned to the operation instead of the order header. This allows the tracking of costs at the operation level.

The characteristics that are not mandatory for OAA orders are:

Overall costs are dynamically summed up on the header level. This is an optional feature that can be activated by using the business function LOG_EAM_SIMPLICITY_2. This allows the display of the total costs of the order operations on the order header level.

The settlement rule is maintained on the header level. This is not a characteristic of OAA orders, but rather a limitation. The settlement rule for OAA orders can only be maintained on the operation level, not on the header level. This means that each operation has its own settlement rule and can be settled to different receivers.

References:

Operation Account Assignment

Operation Account Assignment 2

The Technical Object Breakdowns and Technical Object Damages app use SAP Lumira Designer to display data in a user-friendly and interactive way. SAP Lumira Designer is a tool that allows you to create analytical applications and dashboards based on SAP S/4HANA Core Data Services (CDS) views. SAP Asset Strategy and Performance Management and SAP Predictive Analysis are not components used to display data in this app, but they are other solutions that can help you optimize your asset management strategy and performance. References:

Technical Object Breakdowns

Technical Object Damages

[SAP Lumira Designer]

After a maintenance order is technically completed, the responsible person can perform the following operations1:

Lock or unlock the order: This prevents or allows further changes to the order data, such as actual costs, settlement rule, or confirmation data.

Change the settlement rule: This allows the responsible person to adjust the distribution of costs to the relevant receivers, such as cost centers, assets, or orders.

Post goods movements: This allows the responsible person to record the consumption or return of materials that were used for the maintenance work.

Enter measurement documents: This allows the responsible person to record the measurement readings of the technical objects that were maintained.

The responsible person cannot perform the following operations after a maintenance order is technically completed1:

Update the estimated costs: This is only possible before the order is released or during the execution phase.

Change the planned costs: This is only possible before the order is released or during the execution phase.

Change the order type: This is only possible before the order is released.

Change the order status: This is only possible before the order is technically completed or after it is reversed.

Therefore, the correct answers are A and C. References: 1: Maintenance Order Types | SAP Help Portal

A notification item is used to describe a problem, damage, or the activity executed in greater detail. A notification item can be assigned to one or more object parts and one or more causes of damage. An object part is a component of a technical object that is affected by a malfunction or damage. A cause of damage is a factor that leads to a malfunction or damage. You can use catalogs to enter object parts and causes of damage in a coded form. Therefore, the correct answers are B and D.

References:

SAP Help Portal - Notification Item

SAP Help Portal - Object Part

SAP Help Portal - Cause of Damage

[SAP Learning - Creating Notifications]

The SAP Service and Asset Manager application enables maintenance workers to perform various tasks related to asset management, such as:

Confirm time sheets: Maintenance workers can record the time spent on work orders and operations, and submit them for approval. They can also view the status of their time confirmations and edit or delete them if needed. This functionality helps to track the labor costs and efficiency of the maintenance work1.

Attach documents: Maintenance workers can attach documents, such as photos, videos, audio files, or PDFs, to work orders, notifications, or equipment. This functionality helps to provide additional information or evidence for the maintenance work2.

Display maps: Maintenance workers can view the location of assets, work orders, or notifications on a map. They can also use the map to navigate to the destination, filter the map items, or switch between different map layers. This functionality helps to improve the spatial awareness and planning of the maintenance work3.

Display and maintain technical objects: Maintenance workers can view the details of technical objects, such as equipment, functional locations, or linear assets, and perform actions on them, such as creating notifications, work orders, or measurements. They can also edit the technical object data, such as the status, serial number, or manufacturer. This functionality helps to manage the lifecycle and performance of the assets.

The functionalities that are not available in the SAP Service and Asset Manager application for a maintenance worker are:

Schedule resources: This functionality is available in the SAP S/4HANA Asset Management application, which is a web-based application that supports the planning and scheduling of maintenance work. Maintenance planners and schedulers can use this application to assign resources, such as technicians, tools, or materials, to work orders and operations, and optimize the resource utilization and availability.

Change task list: This functionality is also available in the SAP S/4HANA Asset Management application, which allows maintenance planners and engineers to create and modify task lists, such as general task lists, equipment task lists, or functional location task lists. Task lists are used to define the sequence of operations and activities for recurring maintenance work.

Change BOM: This functionality is also available in the SAP S/4HANA Asset Management application, which allows maintenance engineers and technicians to create and change bills of materials (BOMs) for technical objects, such as equipment or functional locations. BOMs are used to list the components and materials that are required for the maintenance work.

Create a work order on the ESRI map: This functionality is not available in the SAP Service and Asset Manager application, which only supports viewing the existing work orders on the map. To create a work order on the map, the maintenance worker would needto use the SAP Work Manager application, which is another mobile application that integrates with the ESRI ArcGIS platform. The SAP Work Manager application allows the maintenance worker to create a work order by tapping on a map location, and assign the work order to a technician or a crew.

References: 1: SAP Service and Asset Manager User Guide - Maintenance Persona - Time Management 2: SAP Service and Asset Manager User Guide - Maintenance Persona - Attachments 3: SAP Service and Asset Manager User Guide - Maintenance Persona - Maps : [SAP Service and Asset Manager User Guide - Maintenance Persona - Technical Objects] : [SAP S/4HANA Asset Management - Resource Scheduling] : [SAP S/4HANA Asset Management - Task Lists] : [SAP S/4HANA Asset Management - Bills of Material] : [SAP Work Manager User Guide - Creating Work Orders on the Map]

When implementing UI technologies in SAP S/4HANA Asset Management, you have to consider the following points:

Web Dynpro apps can be used in the SAP Fiori Launchpad. This is true because Web Dynpro is one of the UI technologies that are supported by the SAP Fiori Launchpad, along with SAP Fiori apps, SAP GUI for HTML, and WebClient UI12.

SAP Fiori Launchpad supports only SAPUI5 apps. This is false because SAP Fiori Launchpad supports not only SAPUI5 apps, but also other UI technologies such as WebDynpro, SAP GUI for HTML, and WebClient UI12.

SAP GUI for HTML can be used in the SAP Fiori Launchpad. This is true because SAP GUI for HTML is one of the UI technologies that are supported by the SAP Fiori Launchpad, along with SAP Fiori apps, Web Dynpro, and WebClient UI12.

The cloud version can also use SAP GUI for Windows. This is false because SAP GUI for Windows is only available for the on-premise version of SAP S/4HANA Asset Management, not for the cloud version31.

References: 3: Explaining the Intelligent Enterprise - SAP Learning 1: UI Technology Guide for SAP S/4HANA 1909 - SAP Online Help 2: SAP S/4HANA UI Technology | SAP Help Portal

 The visible tiles for a specific user in SAP Fiori Launchpad are determined by the PFCG roles that are assigned to the user. The PFCG roles contain the SAP Fiori catalogs and tile groups that define the available and visible tiles for the user.

The steps to set up the visible tiles for a specific user are:

Create or use an existing PFCG role in the backend system that contains the SAP Fiori catalogs and tile groups that are relevant for the user. The catalogs and tile groups can be created or copied from the SAP Fiori Launchpad Designer app. The catalogs contain the tiles and target mappings that represent the apps that can be launched from the launchpad. The tile groups are collections of tiles that are displayed on the launchpad home page.

Assign the PFCG role to the user in the backend system. The user can have multiple PFCG roles assigned, depending on their business needs and authorizations.

Log on to the SAP Fiori Launchpad with the user credentials. The user will see the tiles that are assigned to them through the PFCG roles on the launchpad home page. The user can also personalize the launchpad by adding, removing, or rearranging the tiles and groups.

The other options are incorrect because:

Portal roles are not used to assign SAP Fiori catalogs and tile groups. Portal roles are used to assign portal content, such as iViews and pages, to users in the SAP Enterprise Portal.

Assigning the tiles directly to the user is not possible. The tiles are part of the catalogs and tile groups that are assigned to the user through the PFCG roles.

References:

Setting Up Launchpad Content | SAP Help Portal

Creating and Configuring Tiles | SAP Help Portal

SAP Fiori Launchpad Tiles Setup - Go Coding

How to create Fiori Catalog, Group and custom Fiori tiles