C_S43_2022 Questions and Answers

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

 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

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

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

To set up a general maintenance task list for inspection rounds using the overall time confirmation as a simplified way to record measurement documents, you need to do the following steps:

• Assign a piece of equipment with an allocated measuring point to a task list operation. This will allow you to inspect the equipment and record the measurement readings for the measuring point during the inspection round. You can assign the equipment either manually or automatically using the object list in the task list header1.
• Assign a measuring point as a production resources/tools (PRT) to a task list operation. This will allow you to inspect the measuring point and record the measurement readings for it during the inspection round. You can assign the measuring point either manually or automatically using the PRT category 0010 (Measuring Point) in the task list operation1.
• You do not need to assign an inspection lot to the task list header, as this is not required for inspection rounds. Inspection lots are used for quality inspections that are triggered by events such as goods receipt, production order, or sales order2.
• You do not need to assign an inspection document as a PRT to the task list operation, as this is not supported for inspection rounds. Inspection documents are used for quality inspections that are based on inspection plans and inspection characteristics2. References: PM - General maintenance task list and Set up your SAP S/4HANA system for EAM Inspection Checklists in SAP Help Portal.

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

SAP BusinessObjects Business Intelligence is a suite of products that provides data reporting, visualization, and sharing capabilities. The current portfolio of SAP BusinessObjects Business Intelligence includes the following functionalities1:

• SAP Crystal Reports: A tool for creating pixel-perfect reports from various data sources, such as relational databases, OLAP cubes, XML files, and SAP applications. SAP Crystal Reports allows users to design, format, and distribute reports in various formats, such as PDF, HTML, Excel, and Word.
• SAP Lumira: A tool for creating interactive data visualizations, such as charts, maps, infographics, and stories. SAP Lumira allows users to explore, analyze, and share data insights using a drag-and-drop interface and a variety of data sources, such as spreadsheets, databases, SAP applications, and SAP HANA.
• SAP BusinessObjects Web Intelligence: A tool for creating ad hoc queries and reports from various data sources, such as relational databases, OLAP cubes, SAP applications, and SAP HANA. SAP BusinessObjects Web Intelligence allows users to access, analyze, and share data insights using a web browser or a mobile device.
• SAP BusinessObjects Analysis: A tool for performing multidimensional data analysis and creating analytical applications from various data sources, such as OLAP cubes, SAP applications, and SAP HANA. SAP BusinessObjects Analysis allows users to slice and dice data, create calculations and formulas, and build interactive dashboards and presentations.
• SAP BusinessObjects Design Studio: A tool for creating professional data visualizations and applications for desktop and mobile devices. SAP BusinessObjects Design Studio allows users to design, develop, and deploy applications using a graphical interface and a scripting language. The applications can be embedded in SAP portals, SAP BusinessObjects BI Launchpad, or SAP Fiori launchpad.
• SAP BusinessObjects Dashboards: A tool for creating interactive dashboards and scorecards from various data sources, such as spreadsheets, databases, SAP applications, and SAP HANA. SAP BusinessObjects Dashboards allows users to visualize key performance indicators, trends, and alerts using a variety of components, such as charts, gauges, maps, and selectors.

Plant Maintenance Information Systems (PMIS) and SAP Quick Viewer are not part of the current portfolio of SAP BusinessObjects Business Intelligence. PMIS is a component of SAP S/4HANA Asset Management that provides standard reports and analysis tools for plant maintenance processes2. SAP Quick Viewer is a tool for creating simple reports from SAP tables and views without any programming3. References: 1: SAP Help Portal, SAP BusinessObjects Business Intelligence Platform - SAP Online Help, Topic: SAP BusinessObjects Business Intelligence suite Features2: SAP Help Portal, SAP S/4HANA Asset Management, Learning Journey: SAP S/4HANA Asset Management, Topic: Plant Maintenance Information System3: SAP Community, SAP Quick Viewer.

• A maintenance order with status REL means that the order is released and ready for execution. At this stage, the following characteristics apply:

 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)

To set up Inspection Checklist processing, you need to customize the following settings:

• Maintain settings at plant level for usage decisions. This is required to define the default values for the usage decision codes and the follow-up actions for the inspection lots. You can do this by using the customizing activity ‘Default Setting at Plant Level’ under 'Quality Management→Quality Inspection→Inspection Lot Completion→Maintain Default Values for Usage Decisions’1.
• Assign an Inspection Type to a Maintenance Order Type and a Planning Plant. This is required to enable the creation of inspection lots for the maintenance orders. You can do this by using the customizing activity ‘Assign Inspection Type to Maintenance Order Type’ under 'Plant Maintenance and Customer Service→Maintenance and Service Processing→Maintenance and Service Orders→Functions and Settings for Order Types→Assign Inspection Type to Maintenance Order Type’2.

You do not need to create a control key which expects inspection characteristic assignments or assign an Inspection Type to a Maintenance Order Type only. These are not relevant settings for the Inspection Checklist processing. References:

• Set up your SAP S/4HANA system for EAM Inspection Checklists
• Explaining Inspection Checklists - SAP Learning

SAP S/4HANA Asset Management, Public Cloud Edition is a cloud-based solution that offers a simplified and standardized configuration of the system via the self-service configuration UI. You can use this UI to adjust the system settings according to your business needs. You do not have access to the SAP S/4HANA back-end system, as it is managed by SAP. SAP Asset Intelligence Network is a separate cloud-based solution that connects manufacturers, operators, and service providers of physical assets. You can use SAP Asset Intelligence Network to share and exchange asset information, but you cannot use it to configure SAP S/4HANA Cloud. References:

• SAP S/4HANA Cloud, Public Edition - SAP Learning
• SAP S/4HANA Cloud for Asset Management, Public Edition

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