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

 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

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

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.

Phase-based maintenance is a new concept introduced in SAP S/4HANA Cloud that allows you to track the life cycle of the maintenance processes using nine predefined phases and sub-phases. These phases are set up by SAP and you cannot change them. However, you can control the transition of phases using phase control codes. Phase-based maintenance is only applicable to the new order types Reactive Maintenance and Proactive Maintenance, which are delivered with the relevant Best Practices scope items. It is not mandatory for breakdown and preventive maintenance, nor can it be used with any existing order type. References: New Phase Model for the Maintenance Processes in S/4HANA Cloud, Phase Model for the Maintenance Process, Maintenance Process Phases, Explaining the Phase-based Process