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

Changing the primary key of a functional location means changing the label of the functional location. The label is the unique identifier of the functional location and it consists of a structure indicator and a functional location identification. The structure indicator defines the allowed characters and the hierarchy levels of the functional location structure. The functional location identification is the actual name of the functional location. When you change the primary key of a functional location, you can either change the structure indicator or the functional location identification, or both. If you change the structure indicator, you need to adjust the functional location identification accordingly. If you change the functional location identification, you need to decide whether the functional location is assigned to a new superior functional location or not. A superior functional location is the functional location that is directly above the current functional location in the hierarchy. For example, if you have a functional location FL-01-02-03, where FL is the structure indicator, 01 is the first level, 02 is the second level, and 03 is the third level, you can change the primary key to FL-01-02-04, which means changing the functional location identification within the same level. In this case, you need to decide whether the functional location is still assigned to FL-01-02 as the superior functional location or not. Alternatively, you can change the primary key to FL-01-03, which means changing the functional location identification to a different level. In this case, you need to decide whether the functional location is still assigned to FL-01 as the superior functional location or not.

The user does not need to define a new labelling system for the new primary key, as the labelling system is defined by the structure indicator, which can be reused for different functional locations. Therefore, answer A is incorrect. The functional location can be assigned to a new superior functional location when the new label is entered, as long as the new label is consistent with the structure indicator and the hierarchy rules. Therefore, answer B is also incorrect. Changing the superior functional location via alternative labeling is possible, as alternative labeling allows you to assign different labels to the same functional location. Therefore, answer C is also incorrect. References: Explaining Technical Asset Structures - SAP Learning, Organizational Elements and Structures | SAP Help Portal, and SAP Alternative Labeling of Functional Locations.

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

 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

 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 Maintenance Planning Overview app allows the planner to analyze critical factors in a chosen reference period, such as outstanding notifications, maintenance orders, purchase requisitions, and purchase orders. The app displays the data in multiple cards that show the number of objects and their status. The planner can use the default filters or adapt them according to their needs.

The activities that the planner can perform by using the app with the default filters are:

• Display approved purchase requisitions for which NO purchase orders have been generated. This is shown in the card “Purchase Requisitions Not Released” which displays the number of purchase requisitions that have been approved but not converted into purchase orders. The planner can navigate to the list of purchase requisitions and take further actions, such as creating purchase orders or changing the requirement date.
• Analyze overdue maintenance orders that have NOT been finally confirmed. This is shown in the card “Overdue Orders” which displays the number of maintenance orders that have been released but not completed within the planned end date. The planner can navigate to the list of overdue orders and check the status of the operations, confirmations, and goods movements.
• Analyze maintenance orders that are still in planning and have NOT been released. This is shown in the card “Orders in Planning” which displays the number of maintenance orders that have not been released for execution. The planner can navigate to the list of orders in planning and complete the planning activities, such as assigning task lists, materials, and resources.

The activities that the planner cannot perform by using the app with the default filters are:

• Display approved purchase requisitions for which purchase orders have been generated. This is not shown in any of the cards in the app. The planner can use the app “Manage Purchase Requisitions” to display this information.
• Analyze confirmed maintenance orders that have NOT been settled. This is not shown in any of the cards in the app. The planner can use the app “Maintenance Order Costs Analysis” to display this information.

References:

• SAP S/4HANA : New app in Plant Maintenance (Asset Management) – Maintenance Planning Overview
• Highlights for Asset Management in SAP S/4HANA 2021
• Maintenance Management | SAP Help Portal

The Preparation and Scheduling phase within phase-based maintenance is the phase where the maintenance planner divides the maintenance effort into manageable groups, levels out the workload over several weeks, determines the concrete time period for the requested maintenance work, and checks the availability of all the resources, spare parts and services needed1.

Option B (The order moves to the Preparation phase once it is approved and released) is correct, because the approval and release of the order is the last step of the previous phase (Approval phase)2. Once the order is approved and released, it is ready for preparation and scheduling.

Option D (The configuration of the order type decides whether you use Resource Scheduling or not) is also correct, because the order type determines whether the order is relevant for resource scheduling or not2. Resource scheduling is an optional step in the Preparation and Scheduling phase, where the planner can assign and dispatch the orders and operations to the technicians using the Resource Scheduling apps2.

Option A (If you use the Resource Scheduling apps, you always dispatch orders and operations) is incorrect, because the Resource Scheduling apps allow the planner to either dispatch or assign the orders and operations2. Dispatching means that the planner assigns a specific technician and a specific time slot for the order or operation, while assigning means that the planner assigns only a technician or a team, but not a specific time slot2.

Option C (Maintenance Planning Buckets give you a list of non-approved notifications) is also incorrect, because the Maintenance Planning Buckets app gives the planner a list of approved and released orders that are ready for preparation and scheduling2. The non-approved notifications are handled in the previous phase (Screening phase)2.

References:

• Phase Model for the Maintenance Process
• New Phase Model for the Maintenance Processes in S/4HANA Cloud
• Explaining the Phase-based Process
• Maintenance Process Phases

 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

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

The structure indicator is a key that defines the allowed characters and the hierarchy levels of the functional location structure. It consists of an edit mask and a hierarchy indicator. The edit mask defines the allowed characters for each position of the functional location identification. The hierarchy indicator defines the hierarchy levels of the functional location structure and the number of characters for each level. For example, a structure indicator with the edit mask ANNNN-NNNN and the hierarchy indicator 5-4 means that the functional location identification can have up to 9 alphanumeric characters, divided into two levels with 5 and 4 characters respectively, separated by a hyphen. The structure indicator does not limit the types of characters to alpha and numeric, as it can also include special characters, such as hyphens, slashes, or dots. Therefore, answer A is incorrect. The structure indicator also does not restrict the number of hierarchical levels to no more than 6, as it can have up to 10 levels. Therefore, answer B is also incorrect. References: Explaining Technical Asset Structures - SAP Learning and Organizational Elements and Structures | SAP Help Portal.

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]

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]

An equipment category defines the technical characteristics of an equipment and the views that are available for it. A view profile is a set of views that can be assigned to an equipment category. The views that can be assigned to an equipment category via a view profile are:

• Basic data
• Classification
• Location
• Organization
• Partner
• Status
• Structure
• Warranty
• Manufacturer data
• Measurement document
• History
• Permits
• Documents
• User fields
• Serial data
• Configuration
• Object links
• Time-dependent data
• Linear data
• Geographical data
• Maintenance plan
• Maintenance item
• Maintenance task list
• Maintenance order
• Maintenance notification
• Service order
• Service notification
• Service contract
• Service confirmation
• Service quotation
• Service request
• Service plan
• Service item
• Service task list
• Service product
• Service product allocation
• Service product structure
• Service product location
• Service product partner
• Service product status
• Service product classification
• Service product documents
• Service product permits
• Service product user fields
• Service product serial data
• Service product configuration
• Service product object links
• Service product time-dependent data
• Service product linear data
• Service product geographical data

Among these views, the ones that match the options given in the question are Warranty and Manufacturer data. Therefore, the correct answers are A and D.

References:

• SAP Help Portal - Equipment Category
• SAP Help Portal - View Profile

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

A cycle set sequence is a feature that allows you to combine several multiple counter plan cycles in a set and determine the order in which the system considers the cycle sets for scheduling. A multiple counter plan is a maintenance plan that is based on one or more performance-based or time-based cycles1.

In this case, you can create a cycle set sequence with two cycles:

• Cycle 1: Every 3 MON: pump inspection
• Cycle 2: Every 24 MON: pump replacement

You can assign a different maintenance item and task list to each cycle, and specify the repetition factor for each cycle. The repetition factor determines how many times the cycle is repeated before the next cycle in the sequence is considered. For example, if you set the repetition factor of cycle 1 to 8, the system will schedule the pump inspection 8 times before scheduling the pump replacement.

By creating a cycle set sequence, you can achieve the requirement that when replacing the pump, the operation pump inspection will be ignored. The system will only generate a call object for the maintenance item that is assigned to the current cycle set. Therefore, when the pump replacement is due, the system will not generate a call object for the pump inspection.

The other options are incorrect because:

• Assign different hierarchy levels: Hierarchy levels are used to structure the task list operations into groups and subgroups. They do not affect the scheduling of the task list operations.
• Set the lead float: Lead float is a time buffer that is added to the start or finish date of a task list operation. It does not affect the scheduling of the task list operations.
• Create a task list hierarchy: A task list hierarchy is a structure that contains several task lists that are linked together by a superior task list. It does not affect the scheduling of the task list operations.

References: 1: Cycle Set Sequence in Multiple Counter Plan - SAP Help Portal

•  This is required to define the inspection scope and the checklist type for the technical object. The inspection plan must be classified with the same class as the technical object and have matching characteristic values1.
• Classification data assigned to a technical object: This is required to identify the relevant inspection plan and checklist type for the technical object. The technical object must be classified with the same class as the inspection plan and have matching characteristic values1.

The other options are not correct because:

• Inspection point type assigned to the task list header: This is not a prerequisite for inspection checklist processing, but an optional setting that allows the user to define inspection points for the checklist items2.
• Master inspection characteristics assigned to PM task list operations: This is not a prerequisite for inspection checklist processing, but an optional setting that allows the user to use master inspection characteristics as checklist items2.

References:

1: Explaining Inspection Checklists - SAP Learning 2: Generating Inspection Checklists | SAP Help Portal

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