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

You can see the results of the material availability check for maintenance orders in two places: within a maintenance order and in the list editing (single-level) for maintenance orders.

Within a maintenance order, you can see the material availability status for each component in the Components tab. The status can be one of the following: Available, Not Available, Partially Available, or Not Checked. You can also see the availability date, which is the date on which the component can be fully available. You can access the maintenance order from the Manage Maintenance Orders app or the Change Maintenance Order app1.

In the list editing (single-level) for maintenance orders, you can see the material availability status for each order in the Material Availability column. The status can be one of the following: Available, Not Available, Partially Available, or Not Checked. You can also see the availability date, which is the date on which all the components for the order can be fully available. You can access the list editing from the List Editing (Single-Level) for Maintenance Orders app2.

References: 1: Checking the Material Availability Status 2: [List Editing (Single-Level) for Maintenance Orders]

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

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

 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 accepted or 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)

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