For which objects can you define measuring points? Note: There are 2 correct answers to this
question.
A, C
Explanation:
In SAP S/4HANA Cloud Private Edition, Service, measuring points are used to record quantitative or
qualitative data (e.g., temperature, mileage) for technical objects to monitor their condition or
performance. The correct answers are:
Functional locations (A): Measuring points can be defined for functional locations to track conditions
at specific sites or areas within a plant.
Pieces of equipment (C): Measuring points are commonly assigned to equipment to monitor
operational parameters, supporting preventive maintenance.
Serial numbers (B): Serial numbers identify individual instances of materials but are not technical
objects themselves; measuring points are not directly assigned to them.
Material (D): Materials represent stock items or products, not technical objects, so measuring points
are not applicable.
"Measuring points can be created for functional locations and pieces of equipment to capture
measurement data, enabling condition-based maintenance strategies."
Where are service contract pricing procedures and conditions defined?
B
Explanation:
In SAP S/4HANA Cloud Private Edition, Service, service contract pricing procedures and conditions
are defined within the SAP S/4HANA Sales module (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 general service 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."
When using a configurable service product in the service contract, which condition type is used to
reflect the price of the selected configuration?
B
Explanation:
In SAP S/4HANA Cloud Private Edition, Service, a configurable service product in 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 type VA00 (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."
To which of the following can you assign maintenance packages? Note: There are 2 correct answers
to this question.
C, D
Explanation:
In SAP S/4HANA Cloud Private Edition, Service, maintenance packages define the intervals or cycles
(e.g., every 6 months, 1,000 hours) at which maintenance activities are performed within a
maintenance plan. They are assigned to:
Task list (C): Maintenance packages can be linked to operations in a task list to specify when each
operation is due.
Maintenance strategy (D): A maintenance strategy groups multiple packages (e.g., time-based or
performance-based cycles) and is assigned to a maintenance plan, which then applies the packages.
Service technician (A): Technicians are assigned to operations, not maintenance packages directly.
Work schedule (B): This is not a standard object in SAP for assigning maintenance packages.
"Maintenance packages are assigned to task lists and maintenance strategies to define the
scheduling intervals for maintenance activities in a plan."
How do you create billing document requests (BDRs) for service contracts?
C
Explanation:
In SAP S/4HANA Cloud Private Edition, Service, billing document requests (BDRs) are intermediate
documents used to prepare billing data from service transactions (e.g., service contracts, service
orders) before generating final billing documents like invoices. For service contracts (scope item 3MO
- Service Contract Management), BDRs are created as part of the billing process to handle periodic or
value-based billing. Let’s evaluate each option based on the standard process:
A . Generate BDRs via report: While reports (e.g., custom ABAP reports or transaction VF04 for billing
due list in on-premise systems) can be used to trigger billing in some scenarios, this is not the
standard method for service contracts in SAP S/4HANA Cloud Private Edition. The service contract
billing process relies on automated or app-based mechanisms rather than standalone reports. No
specific standard report is documented for generating BDRs directly from service contracts.
B . Create BDRs in the Create Billing Document Requests app: There is no standard SAP Fiori app
named "Create Billing Document Requests" in SAP S/4HANA Cloud Private Edition. The closest
related app is "Create Billing Documents" (Fiori App ID F0796), but this app is used to generate final
billing documents (e.g., invoices) from existing BDRs, not to create BDRs themselves. BDR creation
happens upstream in the process, not via a dedicated creation app.
C . Create BDRs as follow-up documents: This is the correct method. In the standard service contract
process, BDRs are created automatically as follow-up documents from the service contract based on
the billing plan assigned to the contract items. The billing plan (e.g., periodic or milestone-based)
defines when billing events occur, and the system generates BDRs (transaction type typically F2 or a
custom type) when the billing date is reached. This process is triggered via the "Release for Billing"
action in the "Manage Service Contracts" app (Fiori App ID Fiori App F2178) or through background
jobs (e.g., job template "Service Contract Billing"). Once released, the BDRs are available for further
processing into invoices, making this the standard and documented approach.
D . Generate BDRs via Manage Billing Document Requests: The "Manage Billing Document Requests"
app (Fiori App ID F2179) is used to monitor, edit, and release existing BDRs for billing, not to
generate them initially. This app allows users to review and correct BDRs before they are converted
into final billing documents, but the creation of BDRs happens earlier in the process as follow-ups
from the service contract, not within this app.
The creation of BDRs as follow-up documents aligns with SAP’s service contract billing workflow,
where the billing plan drives the generation of BDRs automatically or semi-automatically upon
release. This process is tightly integrated with the service contract’s configuration (e.g., billing plan
type, item category settings) and ensures accurate billing for recurring or value/quantity-based
services.
Extract from SAP Documentation: "Billing document requests (BDRs) for service contracts are created
as follow-up documents based on the billing plan, triggered by the release action in the Manage
Service Contracts app or via scheduled billing jobs." (SAP Help Portal, Service Contract Management -
Billing Process, SAP S/4HANA Cloud Private Edition).
What are examples of information contained in a maintenance item of a maintenance plan? Note:
There are 3 correct answers to this question.
A, B, E
Explanation:
A maintenance item in 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."
How are the actions that are proposed for an in-house repair item determined?
C
Explanation:
In the in-house repair process, proposed actions (e.g., repair, replace, return) for a repair item are
determined by the life 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."
You are a consultant on an SAP S/4HANA Cloud brownfield project. In a meeting, the customer
decides to remodel an existing business process in accordance with clean core principles. Which of
the following SAP Signavio solutions can be used for the remodeling?
B
Explanation:
For remodeling a business process in an SAP S/4HANA Cloud brownfield project to align with clean
core principles (minimal customizations, standard processes), SAP Signavio Process Manager (Option
B) is the appropriate tool.
SAP Signavio Process Manager is a modeling tool that allows consultants to design, visualize, and
optimize business processes using BPMN (Business Process Model and Notation). It supports
remodeling by enabling the creation of process models that adhere to SAP’s best practices, ensuring
a clean core approach.
A: Process Governance focuses on workflow execution and compliance, not remodeling.
C: Process Insights provides analytics, not process design.
D: Process Intelligence analyzes process performance, not remodeling.
"SAP Signavio Process Manager enables the remodeling of business processes to align with clean
core principles by providing a platform for process design and optimization."
What are the prerequisites when creating a configurable product? Note: There are 2 correct answers
to this question.
A, D
Explanation:
A configurable product in SAP S/4HANA Cloud Private Edition, Service allows customization via
variant configuration. The prerequisites are:
Assigning a variant class to a product (A): A variant class defines the configurable characteristics (e.g.,
size, color) and is assigned to the product master.
Creating a configuration profile (D): The configuration profile links the product to its variant class and
defines the configuration logic (e.g., dependencies).
B: Characteristics are defined separately and linked via the variant class, not directly as a
prerequisite.
C: Characteristics are not assigned to serial numbers; serial numbers track instances, not
configurations.
"Creating a configurable product requires assigning a variant class to the product and creating a
configuration profile to enable variant configuration."
Which of the following steps are required when creating a product bundle? Note: There are 2 correct
answers to this question.
B, C
Explanation:
A product bundle in SAP S/4HANA Cloud Private Edition, Service groups multiple products or services
into a single offering. The required steps are:
Create a bundle product (B): A product master record is created with an item category group
supporting bundles (e.g., LUMF).
Assign components or component groups to a product bundle (C): Components (e.g., materials or
services) are added to the bundle via a bill of material (BOM) or similar structure.
A: Rules are optional for dynamic bundles, not a mandatory step.
D: A BOM might be used internally, but the step is assigning components, not the BOM itself.
"Creating a product bundle involves defining a bundle product and assigning components or
component groups to it, typically via a BOM structure."