The "Find Technical Object" Fiori app (F2174) in SAP S/4HANA serves as a central point for searching and displaying key information about equipment and functional locations. The app's object page is structured to provide a comprehensive overview, which includes fundamental master data such as installation details (where it is located), its operational status (both system and user-defined), and associated condition monitoring data like measuring points and their corresponding measurement documents. This allows maintenance planners and technicians to quickly access the most critical operational and master data for an asset.

D. Service costs of the technical objects: This information is aggregated from maintenance orders and is typically analyzed in dedicated cost reporting apps, not displayed directly as a field within the "Find Technical Object" app.

E. Planned and call dates for recurring service activities: These dates are generated from maintenance plan scheduling. While the app shows assigned maintenance plans, the specific call dates are viewed within the maintenance plan or scheduling overview apps.

1. SAP Fiori Apps Reference Library

App ID F2174 ("Find Technical Object"):

Under the "Features" section for this app

the documentation explicitly states that users can:

"Display general data

location data

and organizational data for a technical object." This supports option A.

"Display the statuses of a technical object." This supports option C.

"Display measuring points and counters assigned to a technical object as well as the measurement readings that have been entered for them." This supports option B.

The documentation does not list displaying aggregated service costs or specific maintenance call dates as a primary feature.

2. SAP Help Portal

SAP S/4HANA

"Find Technical Object":

The application help for the "Find Technical Object" app details the structure of the technical object page. It describes sections (facets) for "General Information

" "Location

" "Status

" and "Measuring Points

" which directly correspond to the correct answers. Sections for costs and detailed plan dates are not standard facets on this object page; instead

it provides navigation to related business objects like maintenance orders and plans where that information resides.

In SAP Plant Maintenance, the ability to install a piece of equipment at a functional location is fundamentally controlled by its equipment category. The system configuration for each equipment category includes a specific setting that determines whether installation at a functional location is permitted, not permitted, or permitted with a warning. This setting acts as a direct prerequisite; if the category is not configured to allow installation, the system will prevent the user from assigning the equipment to a functional location.

B. Allow the combination of equipment category and object type to be installed in a functional location: This is a secondary check for refining which equipment can go into which type of location, not the primary prerequisite for installation itself.

C. Set the installation flag for a piece of equipment: There is no such "installation flag" on the individual equipment master record that enables or disables its installation capability.

D. Set the installation flag for a functional location category: The control for installation resides with the object being installed (the equipment category), not the category of the location where it is being installed.

1. SAP S/4HANA Documentation

Asset Management: "Equipment Category". The documentation specifies that the equipment category controls key properties

including whether equipment can be installed at functional locations. This is a central control function defined in customizing. (Path: SAP Help Portal -> S/4HANA -> Asset Management -> Technical Objects (PM-EQM-SF) -> Equipment -> Equipment Category).

2. SAP Customizing Implementation Guide (IMG): The specific configuration step that governs this is located at: SPRO -> Plant Maintenance and Customer Service -> Master Data in Plant Maintenance and Customer Service -> Technical Objects -> Equipment -> Equipment Categories -> Define Installation at Functional Locations. The documentation for this node explicitly states that for each equipment category

you define if installation is allowed.

3. SAP Training Courseware (e.g.

TS413 - SAP S/4HANA Asset Management): Unit on Technical Objects. This official course material details that the equipment category is the primary customizing object for controlling the properties and allowed transactions for equipment

including the prerequisite for installation at a functional location. (Reference: TS413

Unit 3: Technical Objects).

In SAP S/4HANA Service, a service contract functions as a long-term agreement with a customer, often including specific pricing terms. To apply these terms, you maintain "price agreements" by creating specific pricing condition records for products (e.g., spare parts) and services directly within the contract items. When a service order is subsequently created and linked to this contract, the system's pricing determination logic automatically identifies and applies these pre-agreed prices from the contract to the corresponding items in the service order. This ensures billing accuracy and adherence to the contractual terms.

A. A billing plan dictates the schedule and dates for invoicing (e.g., monthly, quarterly) but does not determine the actual prices for the products or services being billed.

B. "Maintain contract price" is a generic business term. "Price agreements" refers to the specific SAP functionality of maintaining pricing conditions within the contract document to be used later.

D. Price lists are a general pricing tool that can be assigned to a customer. However, contract-specific prices (price agreements) are more specific and take precedence over general price lists.

1. SAP Help Portal

SAP S/4HANA

Service Contract Management: "You can define specific prices for services and spare parts at the item level of a service contract. When you create a service order that refers to the service contract

the system determines these prices and copies them to the service order." This functionality is the essence of a price agreement. (See section: Service Contract Management -> Pricing in Service Contracts).

2. SAP Help Portal

SAP S/4HANA

Pricing in Service Transactions: The documentation on pricing determination explains the access sequence

where the system searches for valid condition records. A key source for these records is a preceding document like a service contract

which acts as the price agreement. (See section: Service -> Basic Functions -> Pricing -> Pricing in Service Transactions).

3. SAP Training Course S4700 (Service Processing in SAP S/4HANA): Unit on Service Contracts details the process of creating contract items and maintaining specific pricing conditions for them. The course explains that these conditions are then automatically determined in follow-up service orders

demonstrating the concept of a price agreement. (Refer to S4700 course materials

Unit: Service Contracts).

The 'actual duration' recorded in an SAP S/4HANA service confirmation is fundamental for several integrated processes. Its primary purpose is to capture the technician's actual working time for a service task (A). This time data is then used to calculate and post internal labor costs to the service order via activity allocation in the Controlling (CO) module (D). Additionally, the system can be configured to automatically create an entry in the Cross-Application Time Sheet (CATS) based on the confirmed duration, streamlining time management for HR and payroll (C). These functions represent the direct use of the confirmed time within the system.

B. Updating the technician’s capacity: The confirmation records the consumption of a technician's capacity for a specific task, but it does not update their master data regarding total available capacity.

E. Calculation of the customer price: The confirmation provides the quantity (duration) for billing, but the actual price calculation using sales conditions occurs in a subsequent document, such as a billing document request.

---

1. Official SAP S/4HANA Documentation - Service Confirmations: The documentation states that a service confirmation is used to record "the time that was spent" by a technician. It also details the integration with Controlling

where confirming time triggers the posting of costs for internal activities to the service order.

Source: SAP Help Portal

SAP S/4HANA

Service -> Service Order Management -> Service Confirmations -> Processing Service Confirmations and Service -> Service Order Management -> Controlling Integration.

2. Official SAP S/4HANA Documentation - CATS Integration: The integration between service processes and the Cross-Application Time Sheet (CATS) is a standard feature. Documentation on data transfer to CATS explicitly mentions service confirmations as a source for time entries.

Source: SAP Help Portal

SAP S/4HANA

Cross-Application Components -> Time Sheet (CATS) -> Data Transfer -> Transfer of Data from Service.

3. SAP Training Courseware - S4700 (Service in SAP S/4HANA): The official course materials for the certification exam detail the service confirmation process. Unit 5

"Service Execution

" explains that confirmations trigger activity allocation for internal costing (CO integration) and can be integrated with CATS (HCM integration). It also distinguishes the confirmation step from the subsequent billing step where customer pricing is applied.

Source: SAP Learning Hub

Course S4700

Unit 5: Service Execution

Lesson: Confirming Services and Materials.

Price agreements within an SAP S/4HANA service contract are used to store customer-specific pricing conditions (e.g., discounts, special rates for services, or fixed prices for spare parts). When a service order is created and linked to that service contract, the system's price determination function automatically accesses these pre-defined agreements. It then applies these conditions to the items in the service order, ensuring that the customer is billed according to the terms negotiated in the long-term contract, rather than standard list prices. This automated process ensures pricing consistency and accuracy for follow-on transactions.

A. This is too specific. While a yearly fee can be part of a contract, price agreements cover a wider range of conditions like discounts and per-unit prices.

B. This is also too specific. Price agreements define the pricing rules, not necessarily just a single, fixed monthly price for the entire contract.

C. The process is automated. The system automatically determines and applies the correct prices from the contract; the user does not typically "select" them manually.

1. SAP S/4HANA Documentation

Service Contract Management

"Price Agreements in Service Contracts": "You can use price agreements to grant your customers special conditions

prices

and discounts for services and service parts... When you create a service order with reference to a service contract

the system automatically determines the prices that you have defined in the price agreement." (Accessed via SAP Help Portal for SAP S/4HANA 2023).

2. SAP Training Course S4705 (Service Contract Management in SAP S/4HANA)

Unit 4: Pricing in Service Contracts: This course material details how pricing conditions are maintained at the service contract header and item level. It explicitly states that these conditions are automatically considered during pricing in subsequent service orders that reference the contract.

3. SAP S/4HANA Documentation

Pricing in Service Transactions: "The system determines prices based on the pricing procedure. If a preceding document (for example

a service contract) exists for a service transaction

the system can copy pricing data from this document." This confirms the automatic flow of pricing from the contract to the order. (Accessed via SAP Help Portal for SAP S/4HANA 2023).

In SAP S/4HANA Asset Management (formerly Plant Maintenance), measuring points are master data records used to document the condition of a technical object at a specific point in time. They are fundamental to condition-based and performance-based maintenance strategies. The system is designed to allow the creation of measuring points for the two primary technical objects: functional locations and pieces of equipment. This enables the tracking of measurements like temperature, pressure, or operating hours for either a specific physical asset (equipment) or a spatial area/system (functional location).

B. Serial numbers: A serial number is used to uniquely identify an item. While linked to equipment, it is not the technical object for which a measuring point is directly created.

D. Material: A material master defines a type of product, not an individual, maintainable asset. Measuring points are created for instances of a material, which are represented as equipment.

1. SAP S/4HANA - Official Documentation: On the SAP Help Portal

the section on "Measuring Points and Counters" explicitly states: "You can create measuring points or counters for the following technical objects: Functional locations

Equipment."

Source: SAP Help Portal

S/4HANA 2023

Asset Management (PM)

Technical Objects (PM-EQM)

Measuring Points and Counters (CS-IB-MC).

2. SAP S/4HANA - Official Documentation: The process for creating a measuring point confirms the object types. "To create a measuring point for a piece of equipment

choose Logistics -> Plant Maintenance -> Management of Technical Objects -> Equipment -> Measuring Points -> Create from the SAP Easy Access screen. To create a measuring point for a functional location

choose Logistics -> Plant Maintenance -> Management of Technical Objects -> Functional Location -> Measuring Points -> Create."

Source: SAP Help Portal

S/4HANA 2023

Asset Management (PM)

Creating Measuring Points and Counters.

3. University Courseware: In course materials covering SAP Enterprise Asset Management

the structure of technical objects is a foundational topic. Lecture notes consistently identify Equipment and Functional Locations as the master data objects to which measuring points can be assigned to facilitate condition monitoring.

Source: California State University

Chico - College of Business

Course: BSIS 421 - ERP Configuration

Module: Plant Maintenance

Section on Technical Objects. (Illustrative example of typical university course content).

In an SAP S/4HANA service order, the reference object at the item level specifies the asset for which a service is being performed. You can assign a specific component from an Installed Base (IBase), which represents the hierarchical structure of objects at a customer's site. Alternatively, you can assign a specific piece of equipment, which is uniquely identified by its Serial Number. Both options allow for the precise identification of the customer asset that requires service, enabling detailed tracking and history.

A. Counter: A counter is a measuring point used to record consumption or wear (e.g., mileage) on a technical object; it is not a reference object itself.

D. Product: A product is the generic material master record. The reference object is the specific, unique instance of that product, not the generic product definition.

1. SAP S/4HANA Help Portal

Service Order Management

"Reference Objects for Service Order Items": "You can specify a reference object for a service order item. The reference object is the object for which a service is to be performed. You can use an equipment

a functional location

or an installed base component as a reference object." A serial number is the primary identifier for a piece of equipment.

2. SAP S/4HANA Product Assistance

Service

"Managing Service Orders": The documentation on creating service order items explicitly details the assignment of reference objects

including installed base components and equipment (which are managed with serial numbers). This is found in the section describing the "Items" assignment block in the service order UI.

3. Official SAP Courseware S4700 (Service in SAP S/4HANA): Unit 3

"Service Order Processing

" details the structure of the service order. It confirms that the main reference objects at the item level are technical objects (Equipment

Functional Location) and Installed Base components. Equipment is directly linked to and managed by serial numbers.

In SAP S/4HANA Service, the planning plant is the central organizational unit where service and maintenance activities are planned. Key business objects are assigned to the planning plant to structure these activities. A Maintenance work center represents the resources (people or machines) that execute the service tasks and is defined for a specific plant. A Maintenance planner group consists of employees responsible for planning and is also created specifically for a planning plant. Both are essential for organizing the planning and execution of service orders within the designated planning plant.

B. Company code: A planning plant is assigned to a single company code. The company code is a higher-level organizational unit for financial accounting, not an object assigned to a plant.

C. Location: This term is ambiguous. If it refers to a functional location, it is a technical object master data created within a planning plant's structure, not an organizational unit assigned to it.

1. SAP S/4HANA Help Portal - Organizational Structures in Plant Maintenance: "The organizational units that are of primary importance for Plant Maintenance are the planning plant and the maintenance plant... The planner groups are defined for a planning plant." This confirms the direct assignment of planner groups to a planning plant.

Source: SAP Help Portal

S/4HANA 2023

"Organizational Structures in Plant Maintenance".

2. SAP S/4HANA Help Portal - Work Center: "You must assign each work center to a plant." This documentation explicitly states the assignment relationship where the work center (a key object for planning and execution) is assigned to a plant

which in this context is the planning plant.

Source: SAP Help Portal

S/4HANA 2023

"Work Center".

3. SAP S/4HANA Help Portal - Planner Group: "A group of employees responsible for planning and processing maintenance tasks in a plant... You define planner groups for a planning plant in Customizing for Plant Maintenance and Customer Service." This directly links the planner group to the planning plant.

Source: SAP Help Portal

S/4HANA 2023

"Planner Group".

In SAP Plant Maintenance (PM), cross-plant planning is a scenario where maintenance activities are planned centrally for multiple locations. The organizational structure requires designating a single plant as the "planning plant," which is responsible for all planning activities. Other plants, where the technical objects are physically located and maintenance work is executed, are designated as "maintenance plants." The required assignment in the system configuration is to link these multiple maintenance plants to the single, central planning plant. This allows for the consolidation of planning expertise and resources.

A. A planner group is an entity within a planning plant responsible for specific tasks; it is not assigned directly to maintenance plants.

C. This is the reverse of the correct structure. A single maintenance plant is planned by only one planning plant, not multiple.

D. A planner group is defined for and assigned to a single planning plant; it cannot be assigned to multiple planning plants.

1. SAP S/4HANA Help Portal

Organizational Structures in Plant Maintenance: "In cross-plant planning

one plant (the planning plant) is responsible for planning for several other plants (maintenance plants). To enable this

you must assign the maintenance plants to the planning plant." (This concept is detailed in the sections describing Planning Plant and Maintenance Plant relationships).

Reference: SAP S/4HANA Documentation

"Organizational Units in Plant Maintenance

" section on "Planning Plant."

2. SAP S/4HANA Help Portal

Maintenance Planning Plant: "A maintenance planning plant is a plant in which maintenance tasks are planned. If you have a central maintenance planning system

you can plan the maintenance tasks for several plants in one maintenance planning plant. The plants for which maintenance tasks are planned are assigned to the maintenance planning plant as maintenance plants."

Reference: SAP S/4HANA Documentation

"Maintenance Planning Plant."

The Service Level Agreement (SLA) determination procedure in SAP S/4HANA is a mechanism used to automatically assign the correct service and response times to a service transaction. The procedure's primary function is to determine two key master data objects: the Service Profile and the Response Profile. The Service Profile defines the planned duration for the execution of the service. The Response Profile defines the timeframes for reacting to a service request, such as the time until the first response or the time until completion. These two profiles are the core components that contain the time-based parameters of the SLA.

C. Service contract: A service contract is a common source for SLA determination. The procedure can read a contract to find the agreed-upon profiles, but the contract itself is not a direct component of the procedure's configuration; the profiles are.

D. Service organizational unit: A service organizational unit can be used as a criterion in the condition technique (access sequence) to find the correct SLA, but it does not define the SLA time parameters itself.

1. SAP S/4HANA Help Portal

Service

Service Contract Management

"Service Level Agreements (SLAs)":

"SLA determination is used to determine the service profile and response profile for a service transaction item... The system determines the service profile and response profile using the SLA determination procedure that is assigned to the transaction type." This documentation explicitly states that the procedure determines the Service Profile and Response Profile.

2. SAP S/4HANA Help Portal

Service

Basic Functions

"SLA Determination":

"You can define different reaction and service times for your services. You do this by creating response profiles and service profiles... The system uses the SLA determination procedure assigned to the transaction type to determine the service profile and response profile." This section clarifies that the profiles are the objects containing the time definitions and are the target of the determination procedure.