C_S43_2022 SAP Certified Application Associate - SAP S/4HANA Asset Management Questions and Answers

SAP S/4HANA Asset Management, Public Cloud Edition is a cloud-based solution that offers a simplified and standardized configuration of the system via the self-service configuration UI. You can use this UI to adjust the system settings according to your business needs. You do not have access to the SAP S/4HANA back-end system, as it is managed by SAP. SAP Asset Intelligence Network is a separate cloud-based solution that connects manufacturers, operators, and service providers of physical assets. You can use SAP Asset Intelligence Network to share and exchange asset information, but you cannot use it to configure SAP S/4HANA Cloud. References:

• SAP S/4HANA Cloud, Public Edition - SAP Learning
• SAP S/4HANA Cloud for Asset Management, Public Edition

The inspection checklist process is an end-to-end process from the creation of inspection plans to results recording and follow-up actions in Plant Maintenance. The necessary steps of the inspection checklist process are:

• Generate object lists for the maintenance order, which contain the technical objects to be inspected.
• Generate inspection checklists for the maintenance order, which contain the inspection lots based on the inspection plans assigned to the technical objects.
• Record the inspection results for the inspection characteristics in the inspection lots.
• Record the usage decision for the inspection lots, which determines whether the technical objects are accepted or rejected.

Therefore, option A (Generate Inspection Lots within the checklists view) and option C (Record the usage decision for an Inspection Lot) are correct, while option B (Link PM task list with assigned inspection point type to a maintenance item) and option D (Generate Inspection Lots assigned to maintenance order headers) are not part of the inspection checklist process.

References:

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

 Linear data is used to describe the location and extent of linear assets, such as pipelines, roads, or cables. Linear data can be stored in the master data of technical objects, such as functional locations and equipment, as well as in the transactional data of maintenance processes, such as notifications, orders, and confirmations. The objects that have been enhanced with linear data in maintenance processes are:

• Work order confirmation: You can record the processing status of a maintenance order by entering linear data in the confirmation. You can also use the linear data from the order operation or the notification item as a default value1
• Maintenance plan item: You can define inspections and maintenance tasks in linear assets by creating and managing the maintenance items in maintenance plans with linear data. You can also use the linear data from the technical object or the task list as a default value2
• Notification item: You can describe the condition of your linear asset or report a malfunction by entering linear data in the notification item. You can also use the linear data from the technical object as a default value3

References: 1: Linear Data in Maintenance Order Confirmation 2: Linear Data in Maintenance Plan Item 3: Linear Data in Maintenance Notification Item

• A. An Inspection Plan and a technical object must be assigned to the same class. This is true because the inspection plan and the technical object must have matching classification characteristics for the inspection checklist generation. The class defines the characteristics that are relevant for the inspection plan and the technical object1.
• B. A PM task list with inspection point type must be assigned to the maintenance order. This is false because the inspection checklist generation does not depend on the PM task list. The inspection checklist is based on the QM inspection plan, which is a different type of task list2.
• C. An object list must have been generated manually or automatically. This is true because the object list contains the technical objects that will be checked for matching inspection plans. The object list can be generated from the header object of the order, and objects from the maintenance plan item3.
• D. A checklist type must be assigned to the maintenance order header. This is false because the checklist type must be assigned to the maintenance order operation, not the header. The checklist type defines the inspection lot origin and the inspection type for the inspection checklist4. References: 1: Explaining Inspection Checklists 2: Inspection Lot 3: Object List and Inspection Checklist 4: Checklist Type in Task List Operation

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 Web Dynpro, 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

Changing the primary key of a functional location means changing the label of the functional location. The label is the unique identifier of the functional location and it consists of a structure indicator and a functional location identification. The structure indicator defines the allowed characters and the hierarchy levels of the functional location structure. The functional location identification is the actual name of the functional location. When you change the primary key of a functional location, you can either change the structure indicator or the functional location identification, or both. If you change the structure indicator, you need to adjust the functional location identification accordingly. If you change the functional location identification, you need to decide whether the functional location is assigned to a new superior functional location or not. A superior functional location is the functional location that is directly above the current functional location in the hierarchy. For example, if you have a functional location FL-01-02-03, where FL is the structure indicator, 01 is the first level, 02 is the second level, and 03 is the third level, you can change the primary key to FL-01-02-04, which means changing the functional location identification within the same level. In this case, you need to decide whether the functional location is still assigned to FL-01-02 as the superior functional location or not. Alternatively, you can change the primary key to FL-01-03, which means changing the functional location identification to a different level. In this case, you need to decide whether the functional location is still assigned to FL-01 as the superior functional location or not.

The user does not need to define a new labelling system for the new primary key, as the labelling system is defined by the structure indicator, which can be reused for different functional locations. Therefore, answer A is incorrect. The functional location can be assigned to a new superior functional location when the new label is entered, as long as the new label is consistent with the structure indicator and the hierarchy rules. Therefore, answer B is also incorrect. Changing the superior functional location via alternative labeling is possible, as alternative labeling allows you to assign different labels to the same functional location. Therefore, answer C is also incorrect. References: Explaining Technical Asset Structures - SAP Learning, Organizational Elements and Structures | SAP Help Portal, and SAP Alternative Labeling of Functional Locations.

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]

 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”

The work center influences cost calculation in the maintenance order via the cost center and activity type, and via the activity type and hourly rate. The cost center and activity type are assigned to the work center in the master data, and they determine the planned costs of the work center. The activity type and hourly rate are used to calculate the actual costs of the work center based on the actual hours reported for the maintenance order operations.

Option A (Via cost center assigned to a personnel number) is incorrect, because the cost center assigned to a personnel number is not relevant for the cost calculation of the work center. Option C (Via organizational unit and personal hourly rate) is also incorrect, because the organizational unit and personal hourly rate are not used to calculate the costs of the work center.

References:

• Cost Centers and Activity Types
• Work Center Utilization

SAP Intelligent Asset Management is a cloud-based solution that comprises of five components1:

• SAP Asset Intelligence Network: A central repository for asset information that facilitates collaborative asset management and leverages the Internet of Things (IoT).
• SAP Predictive Maintenance and Service: A tool that combines sensor and business data, machine learning, and engineering simulations to optimize asset performance and reduce downtimes.
• SAP Asset Strategy and Performance Management: A tool that measures and improves asset performance and enhances maintenance strategies.
• SAP Predictive Engineering Insights: A tool that uses digital twin technologies and finite element analysis to monitor asset health and predict failures.
• SAP Service and Asset Manager (formerly SAP Asset Manager): A mobile app that provides online and offline access to asset management processes and data.

Among the given options, only B and D are components of SAP Intelligent Asset Management. A and C are not part of the cloud-based solution, but rather standalone applications that can be integrated with SAP S/4HANA Asset Management or other SAP solutions. References: 1: This Article Introduces SAP Intelligent Asset Management

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

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 business functions, 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

Phase-based maintenance processing is a new concept that was introduced in SAP S/4HANA Cloud 2011 and SAP S/4HANA 2021. It allows you to track the life cycle of the maintenance processes using predefined phases and sub-phases, instead of system and user statuses. Phase-based maintenance processing is activated in the SAP system through the following ways:

• Through Best Practices scope items 4HH and 4HI. These are the new scope items for reactive and proactive maintenance that use the phase model for maintenance requests and orders. You can activate these scope items using the SAP Activate methodology and the SAP Best Practices Explorer12.
• By manually activating the corresponding Business Feature in case Best Practices are not used. If you do not use the Best Practices scope items, you can still activate the phase model for maintenance requests and orders by using the Business Feature switch in the Customizing activity Define Settings for Maintenance Processing34.

Phase-based maintenance processing is not always active in all S/4HANA 2021 editions and above, as it depends on the scope items or the Business Feature switch. Therefore, answer B is incorrect. Phase-based maintenance processing is not activated by installing the corresponding enhancement pack and activating the related business function, as this is the old way of activating new features in SAP ERP. Therefore, answer C is also incorrect. References: SAP S/4HANA Cloud release of 2011 – Asset Management (Maintenance … and Highlights for Asset Management in SAP S/4HANA 2021 | SAP Blogs

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

 Strategic analysis is a type of analysis that provides a high-level overview of the business performance and trends, as well as the ability to drill down into the details and perform root cause analysis. Strategic analysis is typically performed by business analysts or managers who need to make strategic decisions based on the data. Strategic analysis requires a collection of tools that are not included with core SAP S/4HANA, such as SAP Analytics Cloud, SAP Business Planning and Consolidation, SAP Business Warehouse, and SAP Business Objects Business Intelligence. These tools enable the integration, transformation, modeling, and visualization of data from various sources, including SAP S/4HANA and other systems. Embedded analysis, on the other hand, is a type of analysis that provides real-time insights into the operational data within the SAP S/4HANA core system. Embedded analysis is typically performed by end users or operational managers who need to monitor and optimize the business processes and transactions. Embedded analysis relies on preconfigured Core Data Services (CDS) views that contain SQL views of the data in SAP S/4HANA. These views can be accessed by SAP Fiori apps, SAP Smart Business KPIs, or SAP Analysis for Microsoft Office. SAP Business Objects is not a part of SAP Business Warehouse, but a separate product that can connect to SAP Business Warehouse or other data sources. Therefore, option C is incorrect. References:

• SAP S/4HANA Asset Management - Analytics, section “Strategic Analysis”
• SAP S/4HANA Asset Management - Analytics, section “Embedded Analysis”
• SAP S/4HANA Asset Management - Analytics, section “SAP BusinessObjects Business Intelligence”

SAP Service and Asset Manager is a predictive asset management application that supports both maintenance and service technicians. Using this app, you can manage work orders, notifications, condition monitoring, material consumption, time management, and failure analysis1.

Some of the standard functionalities of SAP Service and Asset Manager are:

• Technical objects: You can view and edit technical objects such as functional locations, equipment, and measuring points. You can also create new technical objects or link existing ones to work orders or notifications2.
• Work orders and operations: You can view and edit work orders and operations assigned to you or your team. You can also create new work orders or operations, or confirm them as completed2.
• ESRI Maps: You can view the location of your work orders, notifications, and technical objects on an interactive map powered by ESRI. You can also use the map to navigate to your destination or search for nearby assets2.

The other options are not standard functionalities of SAP Service and Asset Manager. Cost analytics and breakdown analytics are features of SAP Intelligent Asset Management, which is a cloud-based solution that integrates with SAP Service and Asset Manager to provide advanced insights and recommendations for asset performance3. References: 1: SAP Service and Asset Manager Overview 2: SAP Service and Asset Manager User Guide 3: SAP Intelligent Asset Management Overview

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.