The Report Malfunction app allows the maintenance technician to perform the following steps when

reporting a malfunction of a technical object:

Display the current location of the technical object. The app shows the geographical location of the

technical object on a map, if the Geographical Enablement Framework is activated. This helps the

technician to locate the technical object and plan the travel route1

Add a URL to provide further information. The app allows the technician to attach a URL to the

malfunction report, such as a link to a video or a website that shows the problem or the

solution. This helps the technician to provide additional information and documentation for the

malfunction1

View details of the technical object by navigating to the Asset Viewer. The app allows the technician

to access the Asset Viewer app from the malfunction report, where they can view the technical

object details, such as the structure, documents, history, and measurements. This helps the

technician to gather information about the technical object and its condition1

The Report Malfunction app does not allow the maintenance technician to perform the following

steps when reporting a malfunction of a technical object:

Select and print the maintenance order shop papers. The app does not provide the option to select

and print the maintenance order shop papers. The technician can use a different app, such as

“Manage Maintenance Orders”, to print the shop papers2

Input estimated costs for repair malfunction. The app does not provide the option to input estimated

costs for repair malfunction. The technician can use a different app, such as “Manage Maintenance

Orders”, to enter the planned costs for the maintenance order2

Reference: 1: Report and Repair Malfunction | SAP Help Portal 2: Manage Maintenance Orders | SAP

Help Portal

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. Reference: PM - General maintenance task

list and Set up your SAP S/4HANA system for EAM Inspection Checklists in SAP Help Portal.

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. Reference: 1: What’s New in SAP S/4HANA 2021 - SAP

Online Help 2: How to Configure SAP S/4HANA Asset Maintenance Subcontracting - SAP PRESS

Material planning in the maintenance order is the process of determining the type, quantity, and

availability of the materials required for carrying out the maintenance tasks. There are some

considerations regarding material planning in the maintenance order, such as:

Material can be assigned at the operation level or the sub-operation level, but not at the order

header level. This is because the material requirement is linked to the specific work that needs to be

done in the order. Therefore, option A is incorrect1.

For stock material, you always need a reservation to ensure that the material is available when

needed. A reservation is a request to the warehouse to keep a certain amount of material ready for

withdrawal at a certain time. Therefore, option B is correct1.

A goods issue is the physical withdrawal of material from the warehouse. It can be entered for both

planned and unplanned material in the maintenance order. Planned material is the material that is

specified in the order before the actual execution of the work. Unplanned material is the material

that is added to the order during or after the execution of the work. Therefore, option C is correct2.

The pick list is a document that lists all the materials that are required for a maintenance order. It can

be printed after the order release, not before. The order release is the step that confirms that the

order is ready to be executed and the materials can be withdrawn from the warehouse. Therefore,

option D is incorrect3.

Reference: 1: Modelling Maintenance Processing - SAP Learning 2: [Manage Maintenance Orders -

SAP Help Portal] 3: SAP S/4HANA Asset Management: Plants from a Maintenance … - SAP PRESS

SAPUI5 apps are web applications that use the SAPUI5 framework to create user interfaces for SAP

business applications. SAPUI5 apps can be integrated into the SAP Fiori Launchpad, which is a shell

that hosts SAP Fiori apps and provides them with services such as navigation, personalization,

embedded support, and application configuration1.

To implement SAPUI5 apps in the SAP Fiori Launchpad, two mandatory elements are catalogs and

tile groups.

Catalogs are collections of tiles and target mappings that define the SAPUI5 apps that can be

launched from the SAP Fiori Launchpad. Tiles are the entry points to the SAPUI5 apps, and target

mappings define the semantic objects and actions that are used to navigate to the SAPUI5 apps.

Catalogs are created and maintained by administrators in the SAP Fiori Launchpad Designer.

Tile groups are collections of tiles that are displayed on the SAP Fiori Launchpad home page. Tile

groups are created and maintained by end users or administrators in the SAP Fiori Launchpad. Tile

groups allow users to organize and access the SAPUI5 apps that are relevant for their roles and tasks.

The other options are incorrect because:

Web Dynpro Apps are web applications that use the Web Dynpro framework to create user

interfaces for SAP business applications. Web Dynpro Apps are not SAPUI5 apps, and they require a

different integration approach to be launched from the SAP Fiori Launchpad.

Transactions are executable programs in the SAP system that perform specific business functions,

such as creating a sales order or posting a goods receipt. Transactions are not SAPUI5 apps, and they

require a different integration approach to be launched from the SAP Fiori Launchpad.

Reference: 1: SAPUI5 - Overview - Tutorialspoint : SAP Fiori Launchpad - SAP Help Portal : Integrating

Web Dynpro ABAP Applications into the SAP Fiori Launchpad - SAP Help Portal : Integrating SAP GUI

for HTML (WebGUI) Applications into the SAP Fiori Launchpad - SAP Help Portal