C_TS470_2412 SAP Certified Associate - SAP S/4HANA Cloud Private Edition Service Questions and Answers

Theactual durationin a service confirmation (e.g., IW41) records time spent on a task. The correct answers areA, C, D.

Capturing the technician’s working time (A):Actual duration (e.g., 5 hours) logs the technician’s effort.

Creation of a CATS entry (C):Transfers time to CATS for payroll/HR integration.

Calculation of internal costs (D):Multiplies duration by rate (e.g., $50/hour) for cost posting.

Why Not the Others?

B:Capacity updates are planning-based, not from confirmations.

E:Customer price uses billing rates, not just duration.

"Actual duration in a service confirmation captures working time, creates CATS entries, and calculates internal costs."

SAP S/4HANA Cloud Private Edition, Service provides specific frameworks for defining organizational structures:

Enterprise Organizational Model: This is the modern, integrated approach in S/4HANA to define organizational units (e.g., company codes, plants, service organizations) for service processes.

Enterprise Service Organization: This specifically refers to the service-specific organizational structure, including service organizations, teams, and employees, tailored for service management.

Maintenance and Service Planning: This is a process, not an organizational structure definition option.

Organizational Management (Legacy): Refers to older SAP ERP HCM structures, not the primary method in S/4HANA Cloud Private Edition.These options are part of the organizational setup in SAP S/4HANA Service."Define your organizational structure using the Enterprise Organizational Model and Enterprise Service Organization for service processes." (SAP Help Portal, Organizational Structure Setup).

Atask listin SAP S/4HANA Cloud Private Edition, Service defines standard maintenance or service procedures. Theheadercontains general data applicable to the entire task list. The correct answers areplanner group (B)andmaintenance strategy (C). Let’s explore this in detail.

Task List Header Overview:

The header (e.g., in transaction IA05/IA06) includes fields like task list type, group, and planning data, setting the context for all operations.

Planner group (B):The planner group (e.g., "PLG1") is assigned in the header to indicate the team responsible for planning the task list’s use (e.g., in maintenance plans). It’s entered in the "Planner Group" field and links to organizational data (e.g., Plant Maintenance structure). For example, "PLG1" might be the North Region planners.

Maintenance strategy (C):The maintenance strategy (e.g., "STR1") is assigned in the header for strategy-based task lists. It defines the packages (e.g., 3M, 6M) that operations will follow when the task list is used in a strategy plan. This is set in the "Strategy" field and ties the task list to scheduling logic.

Why Not the Others?

Production resources and tools (A):PRTs (e.g., tools) are assigned to individual operations, not the header, in the operation details tab.

Components (D):Components (e.g., spare parts) are also assigned at the operation level, not the header, via the components tab.

Practical Example:

Task list "TL001": Header assigns Planner Group "PLG1" and Strategy "STR1" (3M, 6M). Operations then specify tasks and resources.

Additional Insight:

The header data ensures consistency across all operations and integrates with maintenance plans for scheduling.

"In a task list header, you can assign a planner group and maintenance strategy to define planningand scheduling parameters."

Arecurring inspectionin SAP S/4HANA Cloud Private Edition, Service uses a maintenance plan to schedule periodic checks. The correct steps areAandB. Let’s explore this in detail.

Recurring Inspection Overview:

This process involves scheduling inspections via a maintenance plan, generating service orders, and completing them to update the plan.

A completion marks a service order and its corresponding planned date in the maintenance plan as finished (A):When a service order (the call object) is completed (e.g., status "Technically Completed"), the system updates the maintenance plan, marking the corresponding planned date as finished. This shifts the scheduling to the next cycle (e.g., via transaction IP10).

A service order is automatically generated by scheduling the maintenance plan for the inspection (B):Scheduling the maintenance plan (e.g., via IP10 or a background job) generates a service order based on the plan’s cycle and call horizon. This order contains theinspection tasks.

Why Not the Others?

C:Accepting a quotation creates a contract or order, not a maintenance plan, which is a separate planning object.

D:Activating a maintenance plan sets it up but doesn’t generate orders; scheduling does that.

Detailed Flow:

Maintenance plan created with inspection cycle (e.g., every 6 months).

Scheduling (IP10) generates a service order when the call date is reached.

Order completed → Plan updated, next call scheduled.

"Recurring inspections involve scheduling a maintenance plan to automatically generate service orders, with completion updating the plan’s planned dates."

TheService Actualsapp in SAP S/4HANA Cloud Private Edition, Service is a Fiori app for analyzing service-related financial data (e.g., costs, revenues). The correct answers arecreation of variants (A),dynamic adjustment of dimensions (B), andnavigation to related SAP Fiori apps (E). Let’s break this down.

App Purpose:

Service Actuals provides insights into actual costs and revenues from service orders, contracts, and confirmations, supporting profitability analysis.

Creation of variants (A):Users can save custom filter settings (e.g., specific plants, periods) as variants for reuse. In the app, you select filters (e.g., Plant 1000, 2025-Q1), save as "Variant1," and recall it later, streamlining reporting.

Dynamic adjustment of dimensions (B):The app allows real-time changes to analysis dimensions (e.g., by cost center, order type). You can drag and drop fields (e.g., switch from "Order" to "Customer") to pivot data dynamically, enhancing flexibility.

Navigation to related SAP Fiori apps (E):From Service Actuals, you can navigate to apps like "Manage Service Orders" or "Event-Based Revenue Recognition" via links or context menus, improving workflow efficiency.

Why Not the Others?

Upload of Microsoft Excel file (C):This app is for viewing data, not uploading; Excel uploads are for data entry apps.

Creation of SAP Analytics Cloud stories (D):SAC stories are built in SAP Analytics Cloud, not this app, though data might feed into SAC.

Example Use Case:

A manager creates a variant for 2025 service costs, adjusts dimensions to view by customer, and navigates to a service order for details.

"The Service Actuals app features variant creation, dynamic dimension adjustment, and navigation to related Fiori apps."

Service contract determinationlinks a service order to an applicable contract for pricing or SLA. The correct answer isDefine Settings for Transaction Types (C), found in SPRO → Service → Transactions. Let’s explore.

Why This Activity?

In "Define Settings for Transaction Types," you configure the service order type (e.g., "ZSER") to automatically determine a service contract. This includes settings like "Contract Determination" (e.g., by sold-to party, object) and the determination procedure. For example, a rule might check the equipment in the order against active contracts.

Why Not the Others?

A & D:Item category settings focus on item-level behavior, not contract determination.

B:Defines the transaction type structure, not its determination logic.

Example:

Service order type "ZSER" set to determine contract "C001" based on equipment "E001."

"Service contract determination for service orders is defined in the ‘Define Settings for Transaction Types’ activity."

In SAP S/4HANA Service contracts (scope item 3MO), the object list for a contract item specifies covered objects:

Equipment: Individual equipment (e.g., serialized assets) can be assigned to track service coverage.

Product: Materials or service products covered under the contract are listed.

Functional location: Locations where services are performed can be included in the object list.

Equipment bill of material: BOMs are referenced separately, not directly in the object list.

Document: Documents are managed via Document Management System (DMS), not as contract objects.This is configured in the service contract item details."Assign equipment, products, and functional locations to the object list of a service contract item." (SAP Help Portal, Service Contract Management).

In SAP S/4HANA Cloud Private Edition, Service, shipping service parts to a customer beforeservice execution (e.g., for on-site repair) involves follow-up documents created automatically uponservice order release. The correct answers aregoods issue document (A),sales order (C), andreservation (E). Let’s dive into each.

Scenario Context:

A service order might include spare parts to be sent to the customer in advance. Releasing the order triggers logistics and inventory processes.

Goods issue document (A):This records the physical shipment of parts from the warehouse to the customer. Upon release, if the service order includes deliverable items (e.g., via item category with delivery relevance), the system posts a goods issue (e.g., via transaction MIGO or automatically). This updates inventory and triggers accounting postings.

Sales order (C):For billable parts, a follow-up sales order can be created automatically to handle the commercial aspect (e.g., via a sales order type linked to the service order). This integrates with SD for pricing and delivery.

Reservation (E):This reserves stock in the warehouse for the service order’s parts requirements. Upon release, the system generates a reservation (e.g., movement type 261) to ensure availability before goods issue.

Why Not the Others?

Invoice (B):Invoices are created later, typically after goods issue or service confirmation, not automatically upon release.

Purchase requisition (D):This is for procuring parts from a vendor, not shipping to a customer.

Process Flow Example:

Service order released → Reservation created (stock reserved) → Sales order generated (if billable) → Goods issue posted (parts shipped).

"Upon service order release, follow-up documents such as goods issue documents, sales orders, and reservations can be created automatically to facilitate shipping service parts."

In SAP S/4HANA Cloud Private Edition, Service, astrategy planuses a maintenance strategy with multiplepackages(e.g., 3 months, 6 months) to schedule tasks. When two packages are due on the same date, the system must decide which operations from the associated task list are included in the generatedcall object(e.g., a service order). The correct answer isthe hierarchy of the packages (A). Let’s dive into this deeply.

Understanding Strategy Plans and Packages:

A strategy plan is linked to a maintenance strategy (e.g., "STR1") that defines packages with different intervals (e.g., Package 1: 3 months, Package 2: 6 months). Each package is assigned to specific operations in a task list (e.g., Operation 0010: oil change, Package 1; Operation 0020: full inspection, Package 2). Thehierarchyrefers to the priority or precedence of packages when their due dates overlap, as defined in the strategy’s configuration.

Why Hierarchy?

When two packages (e.g., 3 months and 6 months) align on a date (e.g., after 6 months, both are due), the system uses the package hierarchy to determine which operations are included in the call object. In SAP, the hierarchy is typically based on the package with thelongest cycletaking precedence, as it represents a more significant maintenance event. For example:

Task list: Operation 0010 (Package 1: 3M), Operation 0020 (Package 2: 6M).

On 2025-06-01 (6 months), both packages are due.

Hierarchy rule: Package 2 (6M) is higher, so Operation 0020 is included, and Operation 0010 might be skipped or combined based on settings.

Why Not the Others?

Sequence number (B):Sequence numbers order operations within a task list, not packages in a strategy.

Buffers (C):Buffers (e.g., tolerance) adjust call timing, not operation assignment.

Cycle length (D):Cycle length defines when packages are due, but hierarchy decides assignment.

Configuration Insight:

In SPRO → Plant Maintenance → Maintenance Plans → Define Maintenance Strategies, the hierarchy is implicitly set by package order or explicit rules (e.g., "highest cycle wins"). This ensures logical operation selection.

Practical Example:

Strategy: Package 1 (3M), Package 2 (6M). Task list: Op 0010 (P1), Op 0020 (P2). On 2025-06-01, Package 2’s higher hierarchy assigns Op 0020 to the call object.

"When multiple packages in a strategy plan are due simultaneously, the hierarchy of the packages determines which operations are assigned to the generated call object."

TheClean Core Dashboardis a tool provided by SAP to help customers monitor and maintain a clean core strategy in their SAP S/4HANA systems. A clean core approach ensures that the ERP system remains up-to-date, cloud-compliant, and free of unnecessary modifications, facilitating smooth upgrades and innovation adoption. This dashboard provides insights into system customizations, extensions, and compliance with clean core principles. Let’s evaluate each option based on official SAP documentation and functionality as of March 2025:

A. Customers can use the dashboard in the dev, test, and production tenants: The Clean Core Dashboard is primarily designed to monitor the clean core compliance ofproductiveSAP S/4HANA systems, as its purpose is to provide actionable insights into the live environment where business processes are executed. While development (dev) and test tenants are critical for building and validating extensions, the dashboard’s focus is on the production tenant to ensure operational stability and upgrade readiness. SAP documentation specifies that it targets productive systems (e.g., SAP S/4HANA Cloud Private Edition production tenants), and there’s no explicit mention of it being available across all tenant types (dev, test, production) in a unified manner. Thus, this option is not a confirmed feature.

B. It can be accessed by using SAP for Me: This is a key feature of the Clean Core Dashboard.SAP for Meis SAP’s customer portal, providing a centralized interface for accessing various tools, services, and insights related to SAP solutions. The Clean Core Dashboard is integrated into SAP for Me, offering customers a user-friendly way to view tiles and reports on their system’s clean core status (e.g., custom code usage, API compliance, and extension metrics). This accessibility aligns with SAP’s strategy to consolidate customer-facing tools in a single portal, making it a verified feature.

C. Customers can grant access to the dashboard to partners: This is another confirmed feature. SAP allows customers to share access to the Clean Core Dashboard with implementation partners or service providers via SAP for Me’s authorization management. This capability supports collaboration, enabling partners to assist in analyzing and optimizing the system for clean core compliance (e.g., during RISE with SAP engagements). The dashboard’s design facilitates transparency and joint efforts between customers and partners, making this a standard feature in the private cloud context.

D. It can be used in all SAP S/4HANA Cloud editions: This is not entirely accurate. The Clean Core Dashboard is specifically tailored forSAP S/4HANA Cloud Private Editionand, to some extent, SAP S/4HANA on-premise systems, where customizations and extensions are more prevalent and need monitoring. InSAP S/4HANA Cloud Public Edition, the system is inherently clean by design (no source code modifications are allowed, only extensions via SAP BTP or in-app tools), reducing the need for such a dashboard. While clean core principles apply across all editions, the dashboard’s functionality is most relevant to Private Edition and on-premise deployments, where customers have greater control over customizations. SAP documentation highlights its use in Private Edition contexts (e.g., RISE with SAP), not universally across all editions.

The correct answers, B and C, reflect the dashboard’s accessibility via SAP for Me and its collaborative feature with partners, as outlined in SAP’s clean core strategy resources. These features enhance its utility in maintaining a modern, flexible, and cloud-compliant ERP system, particularly in SAP S/4HANA Cloud Private Edition.

Extract from SAP Documentation: "The Clean Core Dashboard, accessible via SAP for Me, provides transparency on system customizations and allows customers to collaborate with partners to ensure clean core compliance in productive SAP S/4HANA Cloud Private Edition systems." (SAP Community,10 Steps to Clean Core for SAP S/4HANA Cloud Private Edition for Customers, 2024).

The in-house repair process (scope item 3XK) in SAP S/4HANA Cloud Private Edition, Service involves handling customer repair requests and processing returned objects. Key steps include:

Perform a pre-check for an in-house repair and make a decision: A pre-check assesses the repair object’s condition to decide whether to proceed with repair, reject it, or take other actions. This is a standard initial step.

Post a goods receipt for a returned object: When a customer returns a defective item, a goods receipt is posted (e.g., via transaction MIGO or a service order), creating a repair object in the system.

Create an in-house repair for a repair request from a customer: This step involves creating a repair order (e.g., transaction type REPA) based on a customer’s request, initiating the process.

Generate a repair object based on the repair order status: Repair objects are not generated from order status; they are created upon goods receipt or manually.

Create an in-house repair after a pre-check for a repair object: While a pre-check precedes repair, the repair order is typically created first, not after the pre-check as a separate step.These steps align with the SAP Best Practices for in-house repair."The in-house repair process includes performing a pre-check, posting goods receipt for returns, and creating a repair order based on customer requests." (SAP Signavio Process Navigator, In-House Repair).

SAP S/4HANA Cloud Private Edition, Service provides capabilities to proactively manage and notify users about critical events, such as expiring contracts. The correct feature is:

Situation monitoring: This capability uses predefined rules and thresholds to detect situations (e.g., a contract nearing its expiration date) and proactively notifies relevant users via alerts or messages in SAP Fiori apps. It’s part of the embedded analytics and service management overview, enabling real-time awareness of issues.

Issue monitoring: This is a more general term and not a specific SAP capability for proactive notifications about contract expirations.

Issue handlingandSituation handling: These refer to reactive processes for addressing identified problems, not proactive notifications.Situation monitoring is a key feature in service contract management (scope item 3MO) and analytics, ensuring timely action on critical events."Situation monitoring proactively informs users about critical situations, such as expiring service contracts, through real-time alerts." (SAP S/4HANA Service, Analytical Applications).

In thein-house repair process, proposed actions (e.g., repair, replace, return) for a repair item are determined by thelife cycle user statuses of the repair objects(Option C).

The repair object (e.g., equipment or material returned for repair) has a status profile defining its life cycle (e.g., Received, In Repair, Completed). User statuses within this profile trigger specific actions based on the current state, configured in customizing. For example, a status of "In Diagnosis" might propose "Perform Diagnosis."

A:Item categories influence billing or structure, not action proposals.

B:Release status affects the repair order, not individual action proposals.

D:The process step overview profile organizes steps, not action determination.

"Proposed actions for in-house repair items are assigned to the life cycle user statuses of the repair object, driving the process based on status transitions."

In SAP S/4HANA Cloud Private Edition, Service, integration betweenControlling (CO)andCross-Application Time Sheet (CATS)allows time entries to be posted as costs to service orders. Replication of certain characteristics ensures accurate cost allocation. The correct answers areitem categories (A)andvaluation types (C). Let’s explore this in depth.

Context of CO-CATS Integration:

CATS captures employee time (e.g., hours worked on a service order), which is transferred to CO for cost posting. Replication ensures consistency between service and financial data.

Item categories (A):These define the type of service order items (e.g., service, expense). They must be replicated to CO to map time entries to the correct cost objects (e.g., a service item linked to a cost center). For example, item category "SERV" might trigger labor cost postings. This is set in customizing (e.g., SPRO → Service → Integration → CO).

Valuation types (C):These specify how costs are valuated (e.g., hourly rate, fixed cost). In CATS, valuation types determine the cost rate applied to time entries (e.g., $50/hour for a technician). Replicating them ensures CO uses the same rates for cost calculation.

Why Not the Others?

Valuation methods (B):This refers to broader accounting methods (e.g., FIFO), not specific to CATS integration.

Item category groups (D):These are material master settings for grouping, not directly relevant to service order time postings.

Practical Example:

A technician logs 5 hours in CATS for a service order item (category "SERV"). The valuation type "TECH1" ($40/hour) is replicated to CO, posting $200 to the order’s cost object.

Additional Detail:

Replication is configured via the CATS profile and CO account assignment rules, ensuring seamless data flow. Errors in replication can lead to cost mismatches, making this a critical setup step.

"For Controlling and CATS integration, item categories and valuation types must be replicated to enable accurate cost posting from time entries."

In SAP S/4HANA Cloud Private Edition, Service, aconfigurable service productin a service contract uses variant configuration to allow customization (e.g., selecting specific service options). The pricing for the selected configuration is reflected using the condition typeVA00 (Variant Price)(Option B).

VA00 is a standard condition type in SAP’s pricing framework that adjusts the base price based on the chosen configuration variants. It is linked to the variant configuration profile and updates the contract item price dynamically.

VASE (A):This is not a standard SAP condition type; it seems to be a typo or misinterpretation.

871 (C):This is not a recognized condition type for configurable products in service contracts.

PSI1 (D):This might relate to service contract items but is not specific to configurable product pricing.

"The condition type VA00 (Variant Price) is used in service contracts with configurable products to reflect the price adjustments based on the selected configuration."

Serial numbers in SAP S/4HANA Cloud Private Edition, Service are used to uniquely identify individual items, particularly in equipment and material tracking:

Tracking material items as pieces of equipment: This process requires serial numbers to monitor specific material items (e.g., spare parts or assets) as equipment throughout their lifecycle, including repairs or replacements. This is common in in-house repair or field service scenarios where serialized items are managed.

Installing and dismantling pieces of equipment: While equipment may have serial numbers, the process itself doesn’t inherently require them unless specified.

Creating a service order for an on-site service process: Serial numbers may be referenced but are not a requirement for the process.

Tracking the warranty of a technical object: Warranties can be tracked without serial numbers, though they may be used optionally.This aligns with SAP’s equipment management and logistics integration."Serial numbers are required to track material items as pieces of equipment in service and repair processes." (SAP Help Portal, Equipment Management).

In thein-house repair processin SAP S/4HANA Cloud Private Edition, Service, the "Release for Billing" step initiates the billing process for repair activities. The correct answer isC: "The system creates a billing document request for each selected repair confirmation item."

Arepair confirmation(e.g., transaction type REPC) records the work done, and when released for billing, the system generates abilling document request (BDR)for each confirmed item that is billable. The BDR is a preliminary document that can later be converted into a billing document(e.g., an invoice) via the billing due list.

A:Billing due list entries are an outcome of BDRs, not directly created per repair object.

B:Billing documents are not created immediately; BDRs are created first.

D:Completion status is separate from billing release.

"Upon executing ‘Release for Billing’ in an in-house repair process, the system generates a billing document request for each selected repair confirmation item, enabling subsequent invoicing."

In SAP S/4HANA Cloud Private Edition, Service, whenitem-based accountingis activated, revenue recognition and monitoring for service orders are handled through specific capabilities. The correct answer isevent-based revenue recognition(Option C). Let’s break this down step-by-step to understand why this is the case and explore the broader context.

What is Item-Based Accounting?

Item-based accounting means that financial postings and revenue recognition are tracked at the individual item level within a service order, rather than at the order header level. This granularity is crucial for service processes where different items (e.g., labor, spare parts) may have different billing or revenue recognition rules.

Why Event-Based Revenue Recognition?

Event-based revenue recognition (EBRR) is a method where revenue is recognized based on specific events or milestones, such as the completion of a service confirmation, goods issue, or billing document creation. In the context of service orders with item-based accounting, EBRR allows the system to post revenue for each item as soon as a predefined event occurs (e.g., when a technician confirms the service). This ensures accurate, real-time revenue tracking aligned with the actual progress of the service work. The system uses apps like "Event-Based Revenue Recognition - Service Documents" to monitor and adjust these postings.

Why Not the Other Options?

Order-based revenue recognition (A):This approach recognizes revenue at the order level, not item-by-item, which conflicts with item-based accounting’s requirement for granular tracking. It’s more suited to simpler scenarios where the entire order is treated as a single unit.

Order-based revenue accounting (B):This is not a standard SAP term in this context. It might imply accounting at the order level, but it lacks the event-driven specificity of EBRR and isn’t used for item-based scenarios.

Event-based revenue reporting (D):This sounds like a reporting function, not a posting ormonitoring capability. Reporting might follow recognition, but it’s not the mechanism for posting revenue.

Practical Example:

Imagine a service order with two items: a repair service (Item 1) and a spare part (Item 2). With item-based accounting and EBRR, revenue for Item 1 is posted when the technician confirms the repair (event), and revenue for Item 2 is posted when the part is issued or billed. This ensures precise financial tracking per item, which is critical for profitability analysis.

"When item-based accounting is active, event-based revenue recognition is utilized to post and monitor service order revenue at the item level, triggered by events such as service confirmation or billing."

The in-house repair process (scope item 3XK) has specific characteristics:

Advanced Returns Management (ARM) can be used for customer returns: ARM integrates with in-house repair to manage return authorizations and goods receipt.

Items can be added to repair orders using service order templates: Templates streamline adding standard repair items to orders.

Credit checks can be executed in repair orders and repair quotations: Credit management is supported to ensure customer creditworthiness.

For each repair object, a service contract item must be assigned: Contracts are optional, not mandatory for repair objects.

An in-house repair process requires the Service with Advanced Execution scenario: Advanced execution is an enhancement, not a requirement for basic in-house repair.These align with SAP’s in-house repair design."In-house repair supports ARM for returns, templates for order items, and credit checks." (SAP Signavio Process Navigator, In-House Repair).

In SAP S/4HANA Cloud Private Edition, Service,service contract pricing procedures and conditionsare defined within theSAP S/4HANA Salesmodule (Option B). This module handles pricing for sales and service processes, including service contracts. Pricing procedures determine how prices are calculated (e.g., base price, discounts), while conditions store the specific price values or rules (e.g., fixed rates, surcharges). These are configured in the Sales and Distribution (SD) component of SAP S/4HANA, which integrates with service management.

SAP CPO (A):This is not a recognized SAP module; it might be a typo (e.g., for SAP C/4HANA), but it’s irrelevant here.

SAP Billing and Revenue Innovation Management (C):This is a separate solution for advanced billing scenarios, not the standard location for service contract pricing.

SAP Subscription Billing (D):This focuses on subscription-based models, not generalservice contract pricing in S/4HANA.

"Pricing procedures and conditions for service contracts are defined in SAP S/4HANA Sales, leveraging the SD pricing framework to manage contract-specific pricing."

A responsible work center in SAP S/4HANA Service defines where work is performed and is assigned to operational objects:

Maintenance order operation: In the Service with Advanced Execution scenario (scope item 63Q), a work center is assigned to operations within a maintenance order linked to a service order, specifying the execution location.

Service order item: In standard service order processing (scope item 3D2), a work center isassigned to a service item to indicate where the service task is executed (e.g., in-house or field).

Maintenance item: This refers to maintenance plan items, which do not directly accept work center assignments; work centers are linked via orders.

Functional location master record: Work centers are not assigned to functional locations; they are linked to equipment or orders instead.This is configured in the work center master data and order Customizing."Assign a responsible work center to maintenance order operations or service order items to define execution responsibility." (SAP Help Portal, Work Center Configuration).