Free SAP C_TS470_2412 Practice Exam with Questions & Answers | Set: 2

Amaintenance itemin a maintenance plan specifies details about the maintenance activity. The correct answers are:

Call horizon (A):Defines the lead time (as a percentage or days) before the planned date when the call object is generated.

Object list (B):Lists the technical objects (e.g., equipment, functional locations) subject to maintenance.

Service interval (E):Specifies the frequency or cycle (e.g., every 6 months) for the maintenance activity.

Service order type (C):This is defined at the maintenance plan level or call object, not the maintenance item.

Service contract item (D):This relates to contracts, not maintenance items directly.

"A maintenance item includes information such as the call horizon, object list, and service interval to define the scope and timing of maintenance activities."

Work centers in SAP S/4HANA Service (and Plant Maintenance) define execution locations and capacities:

Task list usage: Specifies which task lists (e.g., service or maintenance) the work center can use, assigned in the work center master data (transaction CR01).

Capacity category: Defines the type of capacity (e.g., labor, machine) available at the work center, critical for scheduling.

Planner group: Assigned to technical objects or orders, not directly to work centers.

Maintenance planning plant: A work center is assigned to a plant during creation, but the plant itself isn’t assigned to the work center as a customizable attribute.These settings are configured in the work center master record."Assign task list usage and capacity categories to a work center to define its operational scope." (SAP Help Portal, Work Center Master Data).

In across-plant planning scenario, maintenance activities span multiple plants. The correct answer isB. Let’s unpack this.

Cross-Plant Planning Context:

One planning plant oversees maintenance for multiple maintenance plants (where technical objects reside).

Why Several Maintenance Plants to a Planning Plant?

The planning plant is the central hub for scheduling and resource allocation. Maintenance plants (e.g., Plant 0001, Plant 0002) are assigned to it (e.g., Plant 1000) in customizing (SPRO → Enterprise Structure → Assignment → Plant Maintenance). This ensures a single point of control for work orders and plans across plants.

Why Not the Others?

A:Planner groups are assigned within a plant, not across plants directly.

C:Multiple planning plants for one maintenance plant is illogical.

D:Planner groups operate within a planning plant, not across multiple.

Example:

Planning Plant 1000 manages maintenance for Plants 0001 and 0002.

"In cross-plant planning, several maintenance plants are assigned to a planning plant to centralize maintenance scheduling."

To apply product-specific prices from a service contract to a service order:

Maintain price agreements: Price agreements in the contract (e.g., condition type PR00) define product-specific prices, which are copied to linked service orders during creation or item entry.

Maintain billing plan: Controls billing timing, not pricing.

Maintain contract price: A general term, not a specific mechanism.

Maintain price lists: Used in sales, not contract-specific pricing in service.This is part of pricing condition configuration in scope item 3MO."Price agreements in the service contract ensure product-specific prices are applied to service orders." (SAP Help Portal, Service Pricing).

In SAP S/4HANA Cloud Private Edition, Service,price agreementsin a service contract define specific pricing conditions (e.g., discounts, fixed rates) for services or spare parts. The primary purpose isto automatically adjust the service order prices(Option D).

When a service order is created and linked to a service contract, the system applies the price agreements from the contract to the order’s items, ensuring consistent and contract-specific pricing without manual intervention. This automation enhances efficiency and accuracy in billing.

A and B:Defining yearly or monthly prices might be part of the contract’s billing plan, not the purpose of price agreements specifically.

C:Price agreements are not "selected" in the service order; they are automatically applied based on the contract.

"Price agreements in a service contract are maintained to automatically adjust prices in associated service orders, ensuring that contract-specific conditions are consistently applied."

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

Item category configuration in SAP S/4HANA Service defines item behavior:

Billing plan type: Specifies if and how billing plans (e.g., periodic, milestone) are applied to the item.

Billing relevance: Determines whether the item is billable (e.g., A for order-related billing) and how it’s processed in billing documents.

Contract item filter by product list: Not a standard function in item category configuration.

Product type: Defined in material/service master data, not item category.This is set in Customizing under Service → Transactions."Item category configuration defines billing plan type and billing relevance for service items." (SAP Help Portal, Item Category Configuration).

Scheduling amaintenance plan(e.g., via IP10) generates call objects. The correct answers arestart (A),manual call (D), anddelete call (E). Let’s break this down.

Start (A):Initiates scheduling, calculating call dates (e.g., "Start Scheduling" in IP10).

Manual call (D):Creates a call outside the schedule (e.g., "Manual Call" button), for urgent needs.

Delete call (E):Removes a scheduled call (e.g., via "Delete" in IP10), adjusting the plan.

Why Not the Others?

Scheduling (B):A process, not a function.

Dispatch call (C):Not a standard scheduling function; relates to resource assignment.

"Functions when scheduling a maintenance plan include start, manual call, and delete call."

Creating service contracts in SAP S/4HANA Cloud Private Edition, Service can be time-consuming if done from scratch. To streamline this process, SAP provides tools to reuse existing data. The correct answer isservice contract templates(Option D).

A service contract template is a predefined structure that includes standard data such as items, pricing conditions, billing plans, and service objects. When creating a new service contract, you can select a template and adapt it to the specific customer or scenario, significantly reducing manual entry and ensuring consistency.

Service contract quotations (A):These are preliminary documents used to propose a contract to a customer, but they are not designed for reuse as templates for contract creation.

Service order templates (B):These are used to standardize service orders, not service contracts, and thus do not apply here.

Product bundles (C):These group products or services together but are not templates for creating contracts; they are more relevant to sales or service items.

"Service contract templates enable the rapid creation of new contracts by providing reusable structures with predefined data, such as items and conditions, which can be adjusted as needed."

Service with Advanced Executionenhances recurring service processes with detailed execution and billing. The correct answers areA, B, D. Let’s unpack this.

Both resource-related and fixed-price billing are available (A):This scenario supports flexible billing—resource-related (based on actual effort/materials) or fixed-price (predefined rates), configured via the dynamic item processor profile.

The maintenance confirmation describes the actual effort and spare parts used (B):Confirmations (e.g., via IW41) detail hours worked and parts consumed, feeding into billing and cost tracking.

Billable maintenance orders are generated (D):Recurring services generate maintenance orders (mapped to service order types) that are billable, unlike simpler Customer Service orders.

Why Not the Others?

C:"Customer Service orders" is a legacy term; advanced execution uses maintenance orders.

E:Invoices are created via billing runs, not automatically per call object completion.

Example:

A maintenance plan generates a billable order, confirmed with 5 hours and parts, billed resource-related.

"Recurring services in Advanced Execution feature resource-related and fixed-price billing, maintenance confirmations for effort/parts, and billable maintenance orders."