SAP C_S43_2022 Dumps

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 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

 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 material BOM is a list of components that make up a material. It can be used to describe the structure and composition of a product or a spare part. A material BOM can be assigned to one or more technical objects, such as equipment or functional locations, to define the materials required for maintenance activities1.

One way to assign a material BOM to a piece of equipment is via the field construction type in the equipment master. The construction type is a material number that identifies the material BOM for the equipment. By entering the construction type in the equipment master, the system automatically assigns the material BOM to the equipment2.

The other options are incorrect because:

• Via field model number in the equipment master: The model number is a material number that identifies the material of the equipment itself, not the material BOM. It is used to create an equipment BOM, which is a list of components that are installed on the equipment. An equipment BOM can be different from a material BOM, as it can reflect the actual configuration of the equipment2.
• Via material BOM header in the serialization data: The serialization data is a view in the material master that contains information about the serial numbers of the material. It is not related to the material BOM or the equipment assignment3.
• Via creation of an equipment BOM: The creation of an equipment BOM is a different process from the assignment of a material BOM. An equipment BOM can be created from a material BOM, but it does not automatically assign the material BOM to the equipment. An equipment BOM can also be created manually or copied from another equipment2.

References: 1: Using Bills of Materials (BOMs) - SAP Learning 2: SAP PM Bills of Material Tutorial - Free SAP PM Training - ERProof 3: Serialization Data (SAP Library - Material Master (LO-MD-MM))

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 need to 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]

• 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

 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

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]

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 action log is a function that allows you to view the changes that were made to fields during the processing of an order or a piece of equipment. The action log shows you the date, time, user, sub-object, field name, old value, and new value of each change. To enable entries in the action log of a piece of equipment, you need to activate the change documents for the equipment category. The equipment category is a classification of equipment that determines the data that can be maintained for the equipment. The change documents are records of the changes that are made to the data of the equipment. You can activate the change documents for the equipment category in the Customizing for Technical Objects under Equipment Define Equipment Categories . You do not need to define history related fields in the usage period customizing, as this is only relevant for the equipment history. The equipment history is a function that allows you to view the usage periods of the equipment, such as the installation, removal, or transfer dates. The history related fields are fields that are relevant for the equipment history, such as the functional location, the maintenance plant, or the cost center. You can define the history related fields in the Customizing for Technical Objects under Equipment Define History-Related Fields for Usage Periods . You do not need to define or activate the change documents for the equipment reference category, as this is only relevant for the equipment reference. The equipment reference is a function that allows you to link a piece of equipment to another object, such as a material, a serial number, or a document. The equipment reference category is a classification of equipment references that determines the data that can be maintained for the equipment reference. You can define the equipment reference category in the Customizing for Technical Objects under Equipment Define Equipment Reference Categories . You can activate the change documents for the equipment reference category in the Customizing for Technical Objects under Equipment Define Change Documents for Equipment Reference Categories . References:

• Display of the Action Log, section “Use”
• Equipment Categories, section “Change Documents”
• History-Related Fields for Usage Periods, section “History-Related Fields”
• Equipment Reference Categories, section “Change Documents”

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

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

 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”

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

 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

 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: SAP Help Portal - Cycle Modification Factor