To schedule a performance-based maintenance plan, you need to specify the start counter reading and the estimated annual performance of the equipment or functional location. The start counter reading is the initial value of the counter assigned to the maintenance plan. The estimated annual performance is the expected value of the counter for one year. These parameters are used to calculate the maintenance cycle and the due date for the maintenance plan. The scheduling period and the counter overflow reading are optional

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

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

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

• A maintenance order with status REL means that the order is released and ready for execution. At this stage, the following characteristics apply:

 When you settle a refurbishment order with the batches (valuation types) having price control standard price, the following effects occur:

• The effective costs are posted as a credit memo to a price difference account. This means that the difference between the actual costs of the refurbishment and the standard price of the batch is recorded as a variance in the accounting document. This ensures that the inventory value of the batch is not affected by the refurbishment costs1
• The goods receipt for the batch refurbished is posted with the value of the standard price. This means that the inventory value of the batch is updated with the predefined price that is maintained in the material master. This ensures that the inventory value of the batch is consistent and stable1

The other options are incorrect because:

• The effective costs are not posted to the respective batch (valuation type). The batch valuation is based on the standard price, not the actual costs of the refurbishment1
• The goods receipt for the batch refurbished is not posted with the value of the moving average price. The moving average price is only used for batches with price control moving average price, not standard price1

References: 1: Settlement Receiver | 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 personnel number is a unique identifier for an employee in the SAP system. A personnel number can be directly assigned to the following objects:
• A personnel number cannot be directly assigned to the following objects:

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

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]

 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”

 The goal of embedded analytics in SAP S/4HANA is to combine transactional and analytical processing in the same system. Embedded analytics enables real-time operational reporting and decision support within the SAP S/4HANA applications, without the need for data replication or separate data warehouses. Embedded analytics uses the SAP HANA platform capabilities, such as in-memory computing, columnar storage, and calculation views, to provide high-performance and flexible data access. Embedded analytics also leverages the SAP Fiori user interface and the SAP Analytics Cloud to deliver a rich and interactive user experience with predefined and custom analytical apps, dashboards, KPIs, and stories123.

The other options are incorrect because:

• Embedded analytics does not integrate BW Data Store Objects or BW Info Cubes. These are data structures that are used in SAP Business Warehouse, a separate analytical system that can be connected to SAP S/4HANA, but not embedded within it4.
• Embedded analytics does not allow both tactical and strategic analyses within the S/4HANA core. Tactical and strategic analyses are typically performed on historical and aggregated data that may come from multiple sources, not just the S/4HANA core. For these types of analyses, SAP S/4HANA can be integrated with SAP Analytics Cloud or SAP BW/4HANA, which provide more advanced and comprehensive analytical capabilities.

 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

Maintenance activity type is a key for the type of maintenance activity provided, such as repairs, shutdowns, regular activities, inspections, and so on. It is used to classify data according to the type of maintenance activity in cost evaluations, for example, total costs or number of orders for each technical object1.

Maintenance activity type can be used in the maintenance order header and the maintenance order operation. In the maintenance order header, it is used to specify the overall type of maintenance activity for the order. In the maintenance order operation, it is used to specify the type of maintenance activity for each operation within the order. The maintenance activity type in the operation can be different from the one in the header2.

Maintenance activity type cannot be used in the notification activity or the work center. Notification activity is a key for the type of activity performed in response to a notification, such as inspection, repair, or preventive maintenance. It is not related to the maintenance activity type. Work center is a key for the location where an operation is performed, such as a workshop, a laboratory, or a machine. It is also not related to the maintenance activity type.

References: 1: maintenance activity type (PM) (SAP Library - Glossary) 2: maintenance activity type in SAP - Everything you need to know : notification activity (PM) (SAP Library - Glossary) : work center (SAP Library - Glossary)

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