In SAP Plant Maintenance (PM), activities are used within a notification to document the work that has been performed. These activities are recorded using predefined codes from a catalog (Catalog Type 'A'). This catalog-based approach ensures standardized documentation of completed work steps, which is essential for subsequent analysis and reporting. The technician documents the finished work in the activity section of the notification header.

B. A text in the subject long text screen: This is a free-text field and is not catalog-based. It lacks the structured, codifiable data entry required for standardized reporting.

C. A task in the notification item: Tasks (Catalog Type '2') are used to document work that needs to be performed in the future, not work that has already been finished.

D. An entry in the object list: The object list is used to specify the technical objects (e.g., equipment) affected by the notification, not to document the work performed on them.

1. SAP Help Portal - Activities in Notifications: "You can use activities to document the work that has been performed for a notification. You record the activities that have been performed using codes from the relevant catalogs." This source directly confirms that activities are for documenting performed work and are catalog-based.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/3757ad8f954240c8a348d35e15065549/4d8b9b535c38b44ce10000000a174cb4.html (Version: SAP S/4HANA 2020)

2. SAP Help Portal - Tasks in Notifications: "You can use tasks to document the work that is to be performed for a notification." This source differentiates tasks (for future work) from activities (for completed work).

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/3757ad8f954240c8a348d35e15065549/4d8b9a535c38b44ce10000000a174cb4.html (Version: SAP S/4HANA 2020)

3. SAP Help Portal - Catalogs (CS-CZ): This documentation outlines the different catalog types used in Plant Maintenance

including 'A' for Activities and '2' for Tasks

confirming the catalog-based nature of both but reinforcing their distinct purposes.

URL: https://help.sap.com/docs/SAPERP/e249928668a64180952b898322b5f526/5f4b9b535c38b44ce10000000a174cb4.html (This ERP link is still valid for the core concept in S/4HANA).

The SAP Fiori app "Create Technical Object" (F1643) is designed to streamline the creation of functional locations and equipment. During the creation process for a new functional location, the app provides several integrated functions. Users can directly define the object's classification and assign characteristic values. They can also link relevant documents, such as technical drawings or manuals, through the integrated Document Management System (DMS). Furthermore, it is possible to create necessary measuring points and counters to prepare the functional location for condition monitoring and preventive maintenance from the outset.

B. Change a reference location: You can use a reference location as a template to copy data from, but you cannot change the master data of the reference location itself within this creation transaction.

C. Assign a subordinate piece of equipment: Installing equipment onto a functional location is a separate process (e.g., using the "Install Equipment" app) that is performed after the functional location has been successfully created and saved.

1. SAP Fiori Apps Reference Library

App ID F1643 "Create Technical Object": The official documentation lists the key features of this app. It explicitly states that a user can "Classify the functional location

" "Assign documents

" and "Create measuring points and counters for the functional location." It does not mention installing equipment as part of the creation flow.

URL: https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F1643')/S27 (Access the "Features" section for S/4HANA 2020).

2. SAP Help Portal

S/4HANA 2020

"Functional Locations": The documentation on creating functional locations confirms that classification

document assignment

and measuring points are integral parts of the object's master data

which are defined during creation. The installation of equipment is described as a separate business process.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/3757ad8f950b46a5b3472334c47299d9/4d76b8535c38b44ce10000000a174cb4.html?version=2020.000 (This section on Functional Location master data details the various data segments

including classification

documents

and measuring points).

The SAP BusinessObjects Business Intelligence (BI) platform is a suite of front-end applications designed for reporting, data visualization, and analysis. SAP Crystal Reports is a long-standing, core component of this suite, used for creating highly formatted, pixel-perfect reports. SAP Lumira is the tool within the portfolio focused on self-service data discovery and creating interactive dashboards and data visualizations. Both are key client tools that operate on the SAP BusinessObjects BI platform.

B. SAP QuickViewer: This (Transaction SQVI) is a basic, ad-hoc query tool embedded within the SAP ERP or S/4HANA core system, not a component of the separate SAP BusinessObjects BI platform.

C. Plant Maintenance Information Systems (PMIS): This is a standard information system within the Logistics Information System (LIS) specific to the Plant Maintenance module in SAP S/4HANA, providing operational reports, not a tool in the BOBJ BI portfolio.

1. SAP Help Portal

SAP BusinessObjects Business Intelligence Platform 4.3. This official documentation lists the client tools that are part of the platform. It explicitly includes "SAP Crystal Reports 2020" and "SAP Lumira

designer and discovery editions" as key components.

URL: https://help.sap.com/docs/SAPBUSINESSOBJECTSBUSINESSINTELLIGENCEPLATFORM/ (Navigate to version 4.3 -> "What's New" or "Client Tools" sections for component lists).

2. SAP Help Portal

SAP S/4HANA

ABAP-Based Tools for Querying and Reporting. This documentation describes QuickViewer (SQVI) as a tool for creating simple lists within the ABAP environment

distinguishing it from the BusinessObjects suite.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/a25c97ac633a461fb8f69465737750a2/4f43a3e7b2571014b335c4a129f04822.html

3. SAP Help Portal

SAP S/4HANA

Logistics Information System (LIS). This source details the structure of LIS

where PMIS resides as a standard information system for the PM application

separate from the BOBJ BI product family.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/333733395a2a40389342395723255169/2c5a87533763b44ce10000000a174cb4.html

When configuring a new maintenance plan category in SAP S/4HANA (transaction OMP2), several key parameters are defined to control the behavior of maintenance plans assigned to it. These include the Call object, which specifies what is generated when a maintenance call is due (e.g., a maintenance order or a notification). If the call object is an order, the Order type must be specified. Additionally, scheduling parameters are set, such as the "Completion requirement" indicator, which determines if the actual Completion date of the preceding order is mandatory for scheduling the next call, thus making it a critical control parameter.

B. Maintenance activity type: This is defined in the header of the maintenance task list, which is then assigned to a maintenance item in the plan, not in the maintenance plan category itself.

E. Change documents: The activation of change documents for maintenance plans is a general system setting for the object class and is not a parameter configured within the maintenance plan category definition.

1. SAP Help Portal - Maintenance Plan Category: "In Customizing for Plant Maintenance and Customer Service

you can define the maintenance plan categories you require... For each maintenance plan category

you must specify which call object the system should generate for a maintenance call." This confirms the Call object parameter.

Source: SAP S/4HANA Documentation

"Maintenance Plan Category".

2. SAP Help Portal - Configure Maintenance Plan Categories: The configuration settings for a maintenance plan category explicitly require an Order type if the call object is a maintenance order.

Source: SAP S/4HANA Implementation Guide (IMG)

Path: Plant Maintenance and Customer Service -> Maintenance Plans

Work Centers

Task Lists and PRTs -> Maintenance Plans -> Configure Maintenance Plan Categories.

3. SAP Help Portal - Scheduling Parameters for a Maintenance Plan: "Completion requirement: If you set this indicator

the preceding maintenance call object (for example

maintenance order) must be completed before the system can generate the next maintenance call object." This setting

available in the plan and often defaulted from the category

makes the Completion date a key controlling parameter.

Source: SAP S/4HANA Documentation

"Scheduling Parameters for a Maintenance Plan".

The SAP Fiori app "Maintenance Planning Overview" (F2311) provides the maintenance planner with a dashboard of key figures and tasks. The default cards on this overview page are designed to highlight critical areas within the planner's direct responsibility. These include pre-execution planning, ensuring prerequisites are met, and overseeing the order's financial closing.

- (B) The "Purchase Requisitions for Non-Stock Items" card shows approved requisitions awaiting purchase order creation, a key task for the planner to monitor for timely procurement.

- (C) The "Unreleased Orders" card directly reflects the planner's core workload of orders that are prepared but not yet ready for execution.

- (E) The "Orders to be Settled" card shows technically complete orders awaiting financial settlement, which is the final step in the maintenance order lifecycle that the planner oversees.

A: The app focuses on bottlenecks. It shows purchase requisitions for which purchase orders have not been generated, not those that have already been processed into POs.

D: While the "Overdue Orders" card exists, this task is more closely aligned with the role of a maintenance supervisor who oversees active execution, rather than the primary role of a planner.

1. SAP Fiori Apps Reference Library

App ID F2311 (Maintenance Planning Overview): The official documentation lists the default cards available on the overview page.

"Unreleased Orders: Displays the number of maintenance orders that are still in the planning phase and have not yet been released." (Supports option C)

"Purchase Requisitions for Non-Stock Items: Displays the number of approved purchase requisitions for which no purchase orders have been created yet." (Supports option B)

"Orders to be Settled: Displays the number of maintenance orders that have been technically completed but not yet settled." (Supports option E)

Direct URL: https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F2311')/S25OP/S25OP) (Access the "Key Features" section).

2. SAP Help Portal

SAP S/4HANA 2020

"Maintenance Planning Overview": This documentation confirms the purpose and default features of the app

distinguishing between planning

execution

and closing phases of a maintenance order. The planner's role encompasses the full lifecycle

with a focus on planning (unreleased orders)

prerequisites (PRs)

and closing (settlement).

Direct URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/3757ad8f950b4611a133513501348a4b/498ce45769934138e10000000a4450e5.html?version=2020.009

SAP Intelligent Asset Management (IAM) is a suite of cloud-based solutions designed to manage the entire asset lifecycle. The core components of this suite include SAP Asset Manager, the mobile application for maintenance technicians, and SAP Predictive Maintenance and Service (now part of SAP Predictive Asset Insights), which uses IoT data and machine learning for predictive analytics. These solutions are natively built on the SAP Business Technology Platform and are central to the IAM portfolio for optimizing asset performance and maintenance strategies.

A. SAP Work Manager: This is an older mobile application primarily designed for on-premise SAP ERP systems (ECC and S/4HANA) and is not a native component of the cloud-based SAP Intelligent Asset Management suite.

B. Worker safety applications: This is a general category of software. While SAP offers solutions for worker safety (e.g., SAP EHS), it is not a specific, named component within the SAP Intelligent Asset Management solution portfolio itself.

1. SAP Help Portal

SAP Intelligent Asset Management: The official documentation outlines the solutions that comprise the suite. It lists SAP Asset Manager and SAP Predictive Asset Insights (which evolved from SAP Predictive Maintenance and Service) as key parts.

URL: https://help.sap.com/docs/SAPASSETINTELLIGENCENETWORK (The landing page for IAM often links to the constituent products like Asset Manager and Predictive Asset Insights).

2. SAP Product Page

SAP Intelligent Asset Management: This page details the portfolio

explicitly mentioning the capabilities provided by predictive maintenance and mobile asset management.

URL: https://www.sap.com/products/scm/intelligent-asset-management.html (Navigate to "Solutions" or "Capabilities" section).

3. SAP Product Page

SAP Asset Manager: This page confirms that SAP Asset Manager is the mobile solution for SAP Intelligent Asset Management.

URL: https://www.sap.com/products/scm/asset-manager.html

The "Object information" function is a standard feature within SAP Enterprise Asset Management that provides a comprehensive, consolidated view of data for the technical object (e.g., Equipment or Functional Location) referenced in a transactional document. This feature is explicitly available in both Maintenance Notifications (transactions IW21/IW22/IW23) and Maintenance Orders (transactions IW31/IW32/IW33). It allows users to quickly access master data, classification details, measurement readings, and linked documents without navigating away from the notification or order screen.

A. In master record of technical object: The master record is the source of the information, but the "Object information" screen is a specific function used within other transactions to display that data.

B. In document: While Document Information Records (DIRs) can be linked to a technical object and viewed, the "Object information" feature itself is not a function within the document display transaction (CV03N).

1. SAP Help Portal - Displaying Object Information: "You can display information for the reference object of a notification or order... From the notification or order

choose Goto -> Information -> Object information." This official documentation explicitly confirms the availability of this function in both Maintenance Notifications and Orders. (Source: SAP S/4HANA Documentation

Asset Management)

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/3757ad8f954240c8a348323b11645a14/46889058a53e433de10000000a1553f7.html (Path: SAP S/4HANA -> Enterprise Business Applications -> Asset Management -> Maintenance Processing -> Displaying Object Information)

The structure indicator is a key in SAP Plant Maintenance that defines the edit mask for creating functional location labels. This edit mask serves two primary purposes. First, it determines the number of hierarchy levels and the length of the identifier for each level. Second, it specifies the types of characters allowed for each position within the label, such as alphabetic, numeric, or alphanumeric characters. This ensures a consistent and logical naming convention across the entire functional location hierarchy.

B. It can have a maximum length of 50 characters.

This is incorrect. The structure indicator ID itself is a short key (e.g., 4 characters). The functional location label it defines has a maximum length of 40 characters, not 50.

D. It defines which data is transferred to the lower levels of the hierarchy.

This is incorrect. The transfer of master data to lower-level functional locations is controlled by separate configuration settings for data transfer, not by the structure indicator.

1. SAP Help Portal

"Structure Indicator for Functional Locations": "The structure indicator is a key that you use to specify the edit mask for the functional location label... The edit mask determines: The characters that are allowed for the label (letters

numbers

or both)... The number of hierarchy levels." This source directly supports options A and C.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/3757ad8f954240489435564472261e46/1b39c353b677b44ce10000000a174cb4.html

2. SAP Help Portal

"Changing the Functional Location Structure": "The structure of the functional location label is controlled using a structure indicator... The structure indicator determines... how many hierarchy levels the functional location label can have... which character types are permitted for the individual blocks." This documentation reinforces that the structure indicator's role is to define hierarchy levels and allowed characters.

URL: https://help.sap.com/docs/SAPERP/69d34b76f5f14b21a21211112335e05a/1c39c353b677b44ce10000000a174cb4.html

3. SAP Help Portal

"Data Transfer": "You can specify for individual master data fields that the system should copy the entries from the higher-level functional location to the functional location you are creating." This describes a separate functionality

confirming that data transfer is not managed by the structure indicator.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/3757ad8f954240489435564472261e46/2039c353b677b44ce10000000a174cb4.html

The statement is false. In SAP S/4HANA Asset Management, a piece of equipment can be directly linked to a material master record. This is a standard and fundamental feature used for several purposes. The two primary methods for this link are:

1. Construction Type: The "Construction type" field on the equipment master record is used to link it to a material. This is beneficial when multiple pieces of equipment are of the same type (e.g., same model of pump), allowing them to share common data from the material master.

2. Material Serialization: When a material is managed with a serial number profile, an equipment master record can be created automatically upon goods movement. This creates a direct link between the specific serial number of the material and the individual piece of equipment, ensuring synchronized data.

The statement claims a link is impossible. This is incorrect because the "Construction Type" field and the process of material serialization are standard functionalities designed specifically to create this link between equipment and material master data.

1. SAP Help Portal - S/4HANA 2020

Equipment Master Record: The official documentation details the fields of the equipment master record. On the "Structure" tab

it explicitly lists the "Construction type" field

which is defined as a link to a material master record.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/3757ad8f954ce247001000000a4450e5/4a64b953d5a24762e10000000a174cb4.html?version=2020.000

Section: Equipment Master Record -> Structure Data. This section describes how the "Construction type" field links the equipment to a material.

2. SAP Help Portal - S/4HANA 2020

Serial Number Management: This documentation explains the integration between serialized materials and equipment. It states

"You can create a piece of equipment for a material with a serial number... The system ensures that the data for the material and the piece of equipment is always synchronized."

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/3757ad8f954ce247001000000a4450e5/4a6cb953d5a24762e10000000a174cb4.html?version=2020.000

Section: Serial Number Management (LO-MD-SN) -> Master Data in Serial Number Management. This section details the automatic creation and linking of equipment from serialized materials.

Confidence Level: HIGH

The statement accurately describes a core functionality of the integration between the SAP Document Management System (DMS) and SAP Asset Management. Users can create a Document Info Record (DIR) in the DMS, which can house various file types such as technical drawings, safety notes, or repair instructions. This DIR can then be linked directly to a maintenance order at the header level or to a specific operation within that order, making the relevant documentation readily accessible for maintenance execution.

This is a "True or False" question; there are no incorrect options to evaluate. The provided statement is factually correct based on standard SAP S/4HANA functionality.

1. SAP Help Portal

SAP S/4HANA

"Document Management in Plant Maintenance": This official documentation states

"You can use the SAP document management system to... Link these documents to the technical objects

maintenance and service notifications

and orders relevant for Plant Maintenance." This confirms the ability to attach documents to maintenance orders.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/3757ad8f9542404894355640784a100e/4c5bd453088f4308e10000000a174cb4.html

2. SAP Help Portal

SAP S/4HANA

"Assignment of Documents to PM/CS Objects": This page explicitly lists the objects to which documents can be assigned. The list includes "Order header" and "Operation for the order

" directly confirming both parts of the question's claim.

URL: https://help.sap.com/docs/SAPS4HANAON-PREMISE/3757ad8f9542404894355640784a100e/4c5bd553088f4308e10000000a174cb4.html

Confidence Level: HIGH