C_S43_2023 SAP Certified Associate - SAP S/4HANA Cloud Private Edition Asset Management Questions and Answers

 The Customizing for the functional location category includes the following settings: usage period, object information, and status profile.

The usage period defines the start and end dates of the functional location’s usage. It can be used to control the validity of maintenance plans and orders, and to calculate the age of the functional location. You can define the usage period in the Customizing activity Define Functional Location Categories1.

The object information defines the additional data that can be entered for the functional location, such as manufacturer, construction type, serial number, and equipment number. You can define the object information in the Customizing activity Define Functional Location Categories1.

The status profile defines the user statuses that can be assigned to the functional location. The user statuses can be used to control the business transactions that are allowed for the functional location, such as creating orders, notifications, or measuring documents. You can define the status profile in the Customizing activity Define Status Profile2.

References: 1: Define Functional Location Categories 2: Define Status Profile

SAPUI5 apps are web applications that use the SAPUI5 framework to create user interfaces for SAP business applications. SAPUI5 apps can be integrated into the SAP Fiori Launchpad, which is a shell that hosts SAP Fiori apps and provides them with services such as navigation, personalization, embedded support, and application configuration1.

To implement SAPUI5 apps in the SAP Fiori Launchpad, two mandatory elements are catalogs and tile groups.

Catalogs are collections of tiles and target mappings that define the SAPUI5 apps that can be launched from the SAP Fiori Launchpad. Tiles are the entry points to the SAPUI5 apps, and target mappings define the semantic objects and actions that are used to navigate to the SAPUI5 apps. Catalogs are created and maintained by administrators in the SAP Fiori Launchpad Designer.

Tile groups are collections of tiles that are displayed on the SAP Fiori Launchpad home page. Tile groups are created and maintained by end users or administrators in the SAP Fiori Launchpad. Tile groups allow users to organize and access the SAPUI5 apps that are relevant for their roles and tasks.

The other options are incorrect because:

Web Dynpro Apps are web applications that use the Web Dynpro framework to create user interfaces for SAP business applications. Web Dynpro Apps are not SAPUI5 apps, and they require a different integration approach to be launched from the SAP Fiori Launchpad.

Transactions are executable programs in the SAP system that perform specific businessfunctions, such as creating a sales order or posting a goods receipt. Transactions are not SAPUI5 apps, and they require a different integration approach to be launched from the SAP Fiori Launchpad.

References: 1: SAPUI5 - Overview - Tutorialspoint : SAP Fiori Launchpad - SAP Help Portal : Integrating Web Dynpro ABAP Applications into the SAP Fiori Launchpad - SAP Help Portal : Integrating SAP GUI for HTML (WebGUI) Applications into the SAP Fiori Launchpad - SAP Help Portal

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

A cross-plant planning scenario is a special planning process that allows you to carry out material requirements planning for various plants centrally. This facilitates the production of a product in another plant and it also guarantees a smooth flow of materials between different plants. In a cross-plant planning scenario, you can assign multiple maintenance plants to a planning plant (n: 1) or multiple planning plants to a maintenance plant (m: 1). This means that you can plan and execute maintenance orders in different plants using a common planning plant or a common maintenance plant. There is no limit on the number of maintenance plants that can be assigned to a planning plant, so answer B is incorrect. A cross-plant planning scenario is also possible across different company codes, as long as the plants belong to the same controlling area. Therefore, answer D is also incorrect. References: Cross-Plant Planning | SAP Help Portal and SAP S/4HANA Asset Management: Plants from a Maintenance … - SAP PRESS

 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

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]

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

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 Report and Repair Malfunction app supports the maintenance technician in the following steps:

Plan repair work for the responsible work center: The app allows the technician to assign the work items to the work center that is responsible for the repair work. The work center can be a person, a group of persons

The SAP Fiori app “Create Technical Object” allows you to create a new functional location and perform the following actions:

Edit classification data and characteristics. You can assign a class to the functional location and enter values for the characteristics of the class. This helps you to categorize and search for functional locations based on their attributes1

Assign documents. You can attach documents to the functional location, such as drawings, manuals, or certificates. This helps you to provide additional information and documentation for the functional location1

Assign a subordinate piece of equipment. You can assign an existing piece of equipment as a subordinate object to the functional location. This helps you to establish a hierarchical structure of technical objects and show the relationship between them1

The SAP Fiori app “Create Technical Object” does not allow you to perform the following actions:

Create a task list for functional location. You cannot create a task list for the functional location using this app. You need to use a different app, such as “Manage Task Lists”, to create and maintain task lists for technical objects2

Change a reference location. You cannot change the reference location of the functional location using this app. You need to use a different app, such as “Change Functional Location”, to modify the reference location of an existing functional location3

References: 1: Create Technical Object | SAP Help Portal 2: [Manage Task Lists | SAP Help Portal] 3: [Change Functional Location | SAP Help Portal]

A personnel number is a unique identifier for an employee in the SAP system. A personnel number can be directly assigned to the following objects:

C. Work center. A work center is a location where maintenance activities are performed. A work center can have one or more personnel numbers assigned to it, which represent the employees who work at that location. The personnel numbers can be used for capacity planning, scheduling, and confirmation of maintenance orders1.

D. Business partner. A business partner is a person or an organization that has a business relationship with the company. A business partner can have one or more roles, such as customer, vendor, or contact person. A personnel number can be assigned to a business partner role, which allows the system to identify the employee who is responsible for the business partner or who acts as a contact person for the business partner2.

A personnel number cannot be directly assigned to the following objects:

A. Planner group. A planner group is a group of employees who are responsible for planning and processing maintenance orders. A planner group is assigned to a maintenance order header, but not to a personnel number. A planner group can have one or more work centers assigned to it, which in turn can have personnel numbers assigned to them3.

B. Maintenance plan. A maintenance plan is a document that defines the frequency and scope of preventive maintenance activities for technical objects. A maintenance plan is assigned to a maintenance item, which contains the technical object and the task list for the maintenance activities. A maintenance plan does not have a direct assignment to a personnel number, but it can have a planner group assigned to it, which can have work centers and personnel numbers assigned to it. References: 1: Work Center 2: Business Partner 3: Planner Group : [Maintenance Plan]

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

The offset within a maintenance strategy is a parameter that allows you to adjust the due dates of the maintenance packages in a maintenance plan.The offset can be used for two purposes:

To determine the first due date of a maintenance package. For example, if you have a quarterly maintenance package with an offset of 2 months, the first due date will be 2 months after the start date of the maintenance plan, and the subsequent due dates will be every 3 months after that.

To shift a maintenance package by a one-time amount. For example, if you have a monthly maintenance package with an offset of 10 days, the first due date will be 10 days after the start date of the maintenance plan, and the subsequent due dates will be every month after that. However, if you want to shift the second due date by 5 days, you can enter an offset of 5 days for the second maintenance package, and the due date will be 5 days later than the normal cycle. The offset will only apply to the second maintenance package, and the subsequent due dates will follow the normal cycle. The offset does not affect the call date for the maintenance order, which is determined by the call horizon and the scheduling period. The offset also does not create a preliminary buffer shifting the reference date of the maintenance order, which is determined by the lead float and the tolerance. References: 1: SAP Help Portal, SAP S/4HANA Asset Management, Learning Journey: SAP S/4HANA Asset Management, Topic: Maintenance Planning, Subtopic: Maintenance Strategy2: SAP Community, Maintenance Strategy-offset and float in days3: SAP Blogs, Highlights for Asset Management in SAP S/4HANA 2021, Topic: Maintenance Planning.

 A Maintenance Service Plan is a type of Maintenance Plan that is used to schedule periodic services for external customers. When a Maintenance Service Plan is scheduled, a Maintenance Service Call is generated, which contains a Customer Service Order Header and a Maintenance Order. The Maintenance Order is linked to a Service Order Item, which represents the serviceable material or asset. The Maintenance Order contains the technical details of the service, such as operations, components, and confirmations. The Service Order Item contains the commercial details of the service, such as pricing, billing, and credit check. The Maintenance Order and the Service Order Item are integrated through the Dynamic Item Processor (DIP), which transfers the costs and revenues between them. References: Maintenance Service Plan and Maintenance Service Order in SAP Help Portal.

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

The Resource Scheduling for Maintenance Planners app allows you to monitor important KPIs for your work centers, such as utilization, priority of due maintenance orders, and unconfirmed maintenance orders. You can also use filters to show the information that you are interested in. By clicking a card, you can access the Manage Work Center Utilization app, where you can dispatch maintenance order operations to your work centers. You cannot schedule and dispatch maintenance operations by shifts or print job papers from a maintenance order in this app. These functions are available in other apps, such as the Maintenance Scheduling Board app and the Print Job Papers app. References: Resource Scheduling for Maintenance Planners | SAP Help Portal and Resource Scheduling for Maintenance Planners | SAP Blogs