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

 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

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

SAP Service and Asset Manager is a cloud-based mobile app that provides the following capabilities:

• SAP Service and Asset Manager is available for SAP S/4HANA and SAP ERP. This means that the app can integrate with both systems and access the data and processes related to asset management and service operations12
• SAP Service and Asset Manager can be used offline. This means that the app can store data locally on the device and synchronize it with the backend system when the network connection is available. This enables the users to work in remote areas or in situations where the network is unreliable12
• SAP Service and Asset Manager can run on smart watches. This means that the app can leverage the features of wearable devices such as voice control, notifications, and sensors. This enhances the user experience and productivity of the field technicians13

SAP Service and Asset Manager does not provide the following capabilities:

• SAP Service and Asset Manager does not provide single sign-on functionality. This means that the app requires the users to enter their credentials to log in to the app and the backend system. The app does not support any other authentication methods such as biometric or token-based2
• SAP Service and Asset Manager is not available only for the iOS platform. This means that the app can run on both iOS and Android devices. The app supports the native features and user interface of both platforms12

References: 1: SAP Service and Asset Manager | Mobile Asset Management iOS & Android App 3: SAP Service and Asset Manager | Mobile asset management 2: SAP Service and Asset Manager Overview | 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

To have several plan dates calculated in a maintenance plan, you use the scheduling period parameter. The scheduling period defines the time interval for which the system calculates the planned dates for the maintenance plan. For example, if you enter 12 months as the scheduling period, the system calculates the planned dates for the next 12 months from the current date. You can also specify the end date for scheduling, which is the last date for which the system calculates the planned dates. The scheduling indicator determines how the system calculates the planned dates based on the cycle, the shift factor, and the tolerance. The call horizon defines the percentage of the cycle that must be expired before the system generates a call object (such as a maintenance order or notification) for the planned date.

References: 1: Scheduling Maintenance Plans - SAP Learning 2: Maintenance Plan Scheduling Parameters - SAP Online Help

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]

A SAP Fiori tile group is a subset of apps from one or more catalogs that are displayed on the user’s entry page of the SAP Fiori launchpad1. A tile group has the following characteristics:

• It is based on an SAP Fiori tile catalog. A catalog is a logical group of apps or tiles that defines the set of all tiles that users can use to personalize the home page2. A group can contain apps from different catalogs, depending on the user’s role and authorization1.
• It can be assigned directly to the user via personalization. The user can personalize the entry page by adding or removing apps to pre-delivered groups or self-defined groups2. The user can also reorder the groups and tiles according to their preference1.
• It does not provide only HTML5-based apps. A tile group can contain apps that are based on different technologies, such as SAPUI5, Web Dynpro ABAP, or SAP GUI transactions1.
• It is not assigned via a portal role. A tile group is assigned to the user’s role via the SAP Role Maintenance transaction PFCG2. A portal role is a different concept that is used in the SAP Enterprise Portal to define the access rights and content for portal users.

References: Configure the Fiori Launchpad Tiles using Catalogs & Groups, Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad, [Portal Roles]

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)

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

The Report and Repair Malfunction app supports the maintenance technician in the following steps:

• Plan repair work for the responsible work center: The app allows the technician to assign the work items to the work center that is responsible for the repair work. The work center can be a person, a group of persons

 The Customizing for the functional location category includes the following settings: usage period, object information, and status profile.

• The usage period defines the start and end dates of the functional location’s usage. It can be used to control the validity of maintenance plans and orders, and to calculate the age of the functional location. You can define the usage period in the Customizing activity Define Functional Location Categories1.
• The object information defines the additional data that can be entered for the functional location, such as manufacturer, construction type, serial number, and equipment number. You can define the object information in the Customizing activity Define Functional Location Categories1.
• The status profile defines the user statuses that can be assigned to the functional location. The user statuses can be used to control the business transactions that are allowed for the functional location, such as creating orders, notifications, or measuring documents. You can define the status profile in the Customizing activity Define Status Profile2.

References: 1: Define Functional Location Categories 2: Define Status Profile

 When planning maintenance work that is to be carried out by an external company, you have to consider the following aspects:

• If you assign a control key with indicator “Service” for an external service, you have to enter the actual values via the service entry sheet. This is because the service entry sheet is used to record the services performed by the external company and to verify the invoice. The service entry sheet is linked to the purchase order and the maintenance order operation.
• For the maintenance order type, you have to assign the Enhanced Procurement Mode. This is because the Enhanced Procurement Mode enables you to use lean services and enhanced limits for external services. Lean services are intended for the procurement of small or highly specialized services that are carried out by external suppliers as part of an internal or external operation. They can be maintained in the material master as service products. Enhanced limits allow you to define a maximum amount for the external service without specifying the service specifications in advance.
• If you assign a control key for an external order operation, the actual values must always be entered as a goods receipt in the system. This is not true, because the goods receipt is only required for external materials, not for external services. For external services, the service entry sheet is used instead.
• In the control key assigned to the order operation, the “Service” indicator must always be activated. This is not true, because the “Service” indicator is only required for external services, not for external operations. For external operations, the “External Processing” indicator must be activated instead. References: External Services Management (MM-SRV) | SAP Help Portal, Highlights for Asset Management in SAP S/4HANA 2021 | SAP Blogs.

The SAP Fiori app “Create Technical Object” allows you to create a new functional location and perform the following actions:

• Edit classification data and characteristics. You can assign a class to the functional location and enter values for the characteristics of the class. This helps you to categorize and search for functional locations based on their attributes1
• Assign documents. You can attach documents to the functional location, such as drawings, manuals, or certificates. This helps you to provide additional information and documentation for the functional location1
• Assign a subordinate piece of equipment. You can assign an existing piece of equipment as a subordinate object to the functional location. This helps you to establish a hierarchical structure of technical objects and show the relationship between them1

The SAP Fiori app “Create Technical Object” does not allow you to perform the following actions:

• Create a task list for functional location. You cannot create a task list for the functional location using this app. You need to use a different app, such as “Manage Task Lists”, to create and maintain task lists for technical objects2
• Change a reference location. You cannot change the reference location of the functional location using this app. You need to use a different app, such as “Change Functional Location”, to modify the reference location of an existing functional location3

References: 1: Create Technical Object | SAP Help Portal 2: [Manage Task Lists | SAP Help Portal] 3: [Change Functional Location | SAP Help Portal]

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

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