You must assign a certificate profile for outgoing certificates to a key combination. What key
combination can be used without additional settings?
A
Explanation:
In SAP S/4HANA Cloud Private Edition, Quality Management, certificate profiles for outgoing
certificates (e.g., quality certificates issued to customers) are assigned to specific key combinations
that define the context in which the certificate is generated. The certificate profile determines which
characteristics and data are included on the certificate, typically for an outbound delivery process.
The key combination "Material/Customer" is the standard option that can be used without additional
configuration because it aligns with the default settings in SAP’s Quality Management (QM) module
for certificate processing.
Material/Customer: This combination links the certificate profile to a specific material and customer,
allowing the system to retrieve relevant inspection results and batch data for that pairing. It is
preconfigured in the standard SAP system under the certificate profile assignment in Customizing
(SPRO > Quality Management > Quality Certificates > Outgoing > Define Certificate Profiles). No
additional settings are required because this is a common business scenario where certificates are
tailored to customer-specific requirements for a material.
Material: Assigning a certificate profile only to a material requires additional settings to ensure the
system knows which customer or delivery context to apply it to, as certificates are typically
customer-facing. This option is valid but not default without further configuration.
Material Type: This is too broad and not directly supported as a standalone key combination for
certificate profiles without custom enhancements, as certificate profiles need more specific
granularity.
Customer: Assigning to just a customer lacks the material context, making it incomplete for
certificate generation without additional setup.
Thus, "Material/Customer" is the most straightforward and default-supported key combination.
Reference: SAP Help Portal - "Quality Certificates in QM" (Outgoing Certificates); SAP S/4HANA Cloud
Private Edition, Quality Management Certification Guide (C_TS414_2023).
To which of the following quality management basic data can you assign documents from the
document management system (DMS)? Note: There are 2 correct answers to this question.
A, D
Explanation:
The Document Management System (DMS) in SAP S/4HANA allows users to link documents (e.g.,
PDFs, drawings, or instructions) to various objects to provide additional context or instructions. In
Quality Management, certain basic data objects support this integration natively:
Inspection Methods (A): Inspection methods define how an inspection is performed (e.g., a test
procedure). You can assign DMS documents to inspection methods to provide detailed instructions or
reference materials (e.g., a calibration guide). This is configured in the inspection method master
data (transaction QK01/QK02) where a document link field is available.
Master Inspection Characteristics (D): Master inspection characteristics (MICs) define what is being
inspected (e.g., length, weight). DMS documents can be assigned to MICs to include specifications,
diagrams, or tolerances directly in the master data (transaction QS21/QS23). This is a standard
feature to enhance inspection planning and execution.
Codes from Code Groups (B): Codes and code groups are used for qualitative valuations (e.g., defect
types). They do not have a direct field for DMS document assignment in their master data
(transaction QS41/QS51), making this option incorrect.
Sampling Procedures (C): Sampling procedures determine how samples are drawn (e.g., fixed sample
size). While critical to inspection planning, they do not support direct DMS document assignment in
standard SAP configuration (transaction QDV1/QDV2).
Thus, the correct answers are "Inspection methods" and "Master inspection characteristics," as both
support DMS integration without additional customization.
Reference: SAP Help Portal - "Document Management in QM"; SAP S/4HANA QM Configuration
Guide - "Basic Data for Quality Management".
Working area settings are mandatory for inspection planning within the engineering workbench.
Which of the following are possible focuses for a working area? Note: There are 2 correct answers to
this question.
A, B
Explanation:
The Engineering Workbench (EWB) in SAP S/4HANA is a powerful tool for managing task lists,
including inspection plans, in a structured and efficient way. Working areas in the EWB define the
focus or scope of what users can edit or view during inspection planning. These settings are
mandatory to streamline workflows and ensure the correct level of detail is maintained:
Header (A): The header level refers to the overall inspection plan (e.g., plan group and group
counter). A working area focused on the header allows users to manage high-level attributes like
validity dates or usage. This is a standard focus in EWB (transaction CEWB).
Operation (B): Operations within an inspection plan define the steps or activities (e.g., "Measure
dimension"). A working area focused on operations allows detailed planning at this level, including
assigning control keys or work centers. This is another standard focus in EWB.
Inspection Characteristic (C): While inspection characteristics (e.g., specific measurements) are part
of an operation, they are not a standalone focus for a working area in EWB. They are managed within
the operation context, not as a separate working area.
Classification (D): Classification is used for categorizing objects (e.g., materials) but is not a focus for
working areas in inspection planning within EWB. It’s unrelated to this context.
Thus, "Header" and "Operation" are the correct focuses, aligning with EWB’s structure for inspection
planning.
Reference: SAP Help Portal - "Engineering Workbench in QM"; SAP S/4HANA QM User Guide -
"Inspection Planning with EWB".
Where do you define the procedure for calculation of the quality score at usage decision?
A
Explanation:
The quality score in SAP S/4HANA Quality Management reflects the quality performance of an
inspection lot, calculated at the usage decision (UD) stage. This score can influence subsequent
processes, such as supplier evaluation. The procedure for its calculation is defined as follows:
Usage Decision Code (A): The quality score calculation procedure is assigned to the usage decision
codes in Customizing (SPRO > Quality Management > Quality Inspection > Usage Decision > Define
Quality Score Procedure). Each UD code (e.g., "Accepted," "Rejected") can have a specific score or
formula linked to it, determining how the system computes the score based on inspection results.
This is the correct and standard location for this setting.
Procurement Data in the Quality Management View of the Material Master (B): This area
(transaction MM02, QM view) contains settings like inspection type or control keys but does not
define the quality score calculation procedure.
Quality Info Record: Procurement (C): The quality info record (transaction QI01/QI02) manages
supplier-specific QM settings (e.g., release status), but it does not configure the quality score
calculation procedure.
Inspection Type Settings in the Material Master (D): Inspection type settings (e.g., 01 for goods
receipt) in the material master activate QM processes but do not define the score calculation logic.
Thus, "Usage decision code" is the correct answer, as it directly ties the score calculation to the UD
process.
Reference: SAP Help Portal - "Quality Score and Usage Decision"; SAP S/4HANA QM Customizing
Guide - "Usage Decision".
An inspection plan group includes multiple inspection plans with different group counters. What
determines the selected inspection plan when you create an inspection lot?
D
Explanation:
In SAP S/4HANA QM, an inspection plan group contains multiple inspection plans, each identified by
a unique group counter. When an inspection lot is created (e.g., for goods receipt or production), the
system must select the appropriate plan from the group:
Lot Size (D): The lot size of the inspection lot is the primary determinant for selecting an inspection
plan. In the inspection plan header (transaction QP01/QP02), you define a "usage" and "lot size
range" for each plan within the group. The system matches the inspection lot’s size to the applicable
lot size range in the plan, ensuring the correct plan is chosen. This is standard behavior in QM (e.g.,
for inspection lot origin 01 or 03).
Sample Size (A): Sample size is determined by the sampling procedure within the inspection plan, not
the other way around. It doesn’t select the plan.
Material Type (B): Material type influences material master settings but does not directly determine
the inspection plan selection within a group.
Procurement Type of the Material (C): Procurement type (e.g., in-house vs. external) might influence
the inspection type, but it doesn’t select between plans in a group.
Thus, "Lot size" is the correct answer, as it aligns with SAP’s logic for task list selection.
Reference: SAP Help Portal - "Inspection Planning with Task Lists"; SAP S/4HANA QM User Guide -
"Inspection Lot Creation".
For which catalog types is it mandatory to valuate the codes in the selected set? Note: There are 2
correct answers to this question.
A, C
Explanation:
In SAP S/4HANA Quality Management, catalogs are used to manage predefined codes for qualitative
data recording, and selected sets are subsets of code groups used in specific contexts (e.g.,
inspection plans). Valuation of codes (assigning values like "Accepted" or "Rejected") is mandatory
for certain catalog types to ensure consistent processing:
Usage Decisions (A): Catalog type "3" (Usage Decisions) requires valuation in the selected set
because the usage decision (UD) determines the stock posting and quality score. In Customizing
(SPRO > Quality Management > Quality Inspection > Usage Decision > Define Selected Sets), codes
like "A" (Accepted) or "R" (Rejected) must be valuated to trigger specific system actions (e.g., goods
movement). This is mandatory for inspection lot completion.
Defect Types (C): Catalog type "9" (Defects) requires valuation in the selected set when used in
defect recording (e.g., transaction QS51). Defect codes (e.g., "Scratch," "Dent") need valuation to
classify severity or trigger follow-up actions like notifications, making it mandatory in quality
processes.
Characteristic Attributes (B): Catalog type "1" (Characteristic Attributes) is used for qualitative MICs.
Valuation is optional and depends on the characteristic’s settings (e.g., "Good/Bad"), not mandatory
in the selected set itself.
Activities (QM) (D): Catalog type "5" (Activities) is used for tasks or follow-ups in notifications.
Valuation is not mandatory in the selected set, as activities are typically descriptive rather than
evaluative.
Thus, "Usage decisions" and "Defect types" are the correct answers, as valuation is a required step in
their respective processes.
Reference: SAP Help Portal - "Catalogs and Selected Sets in QM"; SAP S/4HANA QM Customizing
Guide - "Catalog Management".
Which of the following must be assigned when you create an operation in an inspection plan?
B
Explanation:
When creating an operation in an inspection plan (transaction QP01/QP02), certain fields are
mandatory to define the operation’s purpose and execution in SAP S/4HANA QM:
Control Key (B): The control key is a mandatory field in the inspection plan operation. It determines
the operation’s behavior, such as whether inspection characteristics are required, whether it’s a
milestone, or if it triggers specific actions (e.g., QM01 for quality inspection). Defined in Customizing
(SPRO > Quality Management > Quality Planning > Inspection Planning > Define Control Keys), it
ensures the system knows how to process the operation. Without it, the operation cannot be saved.
Activity Type (A): This is relevant for cost accounting (e.g., in Production Planning or QM orders) but
is not mandatory in the inspection plan operation itself.
Work Center (C): The work center (e.g., a test station) is optional in QM inspection plans unless
specified by the control key. It’s common but not universally required.
Standard Text Key (D): This provides predefined descriptions for operations but is optional and not
required to create an operation.
Thus, "Control key" is the correct answer, as it’s the only mandatory assignment in standard SAP QM
for inspection plan operations.
Reference: SAP Help Portal - "Inspection Planning with Task Lists"; SAP S/4HANA QM User Guide -
"Operations in Inspection Plans".
The catalog profile contains a subset of code groups and codes from different catalog types. Where
can you assign the catalog profile? Note: There are 3 correct answers to this question.
A, B, C
Explanation:
A catalog profile in SAP S/4HANA QM defines a collection of code groups and codes from various
catalog types (e.g., defects, usage decisions) for use in quality processes. It can be assigned at
multiple levels:
In the Quality Management View of the Material Master (A): The catalog profile is assigned in the
QM view of the material master (transaction MM01/MM02, field QMAT-PROF) at the plant level.
This links it to inspection lots for that material, controlling defect recording or UD codes.
In the Customizing Settings for the Notification Type (B): In Customizing (SPRO > Quality
Management > Quality Notifications > Notification Creation > Define Notification Types), you can
assign a catalog profile to a notification type (e.g., Q1 for customer complaints). This determines the
codes available during notification processing.
In the Customizing Settings for the Inspection Type (C): In Customizing (SPRO > Quality Management
> Quality Inspection > Inspection Lot Creation > Maintain Inspection Types), a catalog profile can be
linked to an inspection type (e.g., 01 for goods receipt). This governs the codes used in inspection
lots of that type.
In the Master Inspection Characteristic (D): MICs (transaction QS21) use individual code groups or
selected sets, not catalog profiles directly.
In the Customizing Settings for the Report Type (E): Report types (used in defect recording layouts)
reference catalog profiles indirectly via other objects, not as a direct assignment.
Thus, the correct answers are "A, B, C," as these are the standard assignment points.
Reference: SAP Help Portal - "Catalog Profiles in QM"; SAP S/4HANA QM Customizing Guide -
"Notification and Inspection Types".
In the material master, at which organizational level do you assign a Catalog Profile?
D
Explanation:
The catalog profile in the material master determines the set of codes available for quality processes
like defect recording or usage decisions. Its assignment occurs at a specific organizational level:
Plant Level (D): In the material master (transaction MM01/MM02), the catalog profile is assigned in
the Quality Management view under the "Inspection Setup" section (field QMAT-PROF). This is done
at the plant level because QM processes (e.g., inspections) are plant-specific, and the catalog profile
must align with the plant’s quality requirements. This is standard SAP behavior, ensuring flexibility
across different plants for the same material.
Company Code Level (A): QM settings are not managed at the company code level, as this is a
financial organizational unit unrelated to inspection processes.
Client Level (B): Client-level settings are too broad and apply globally, whereas catalog profiles need
plant-specific granularity.
Business Area Level (C): Business areas are used for financial reporting, not QM organizational
assignments.
Thus, "Plant level" is the correct answer, reflecting SAP’s organizational structure for QM data.
Reference: SAP Help Portal - "Material Master in QM"; SAP S/4HANA QM User Guide - "QM View in
Material Master".
Coding from different catalogs can be used during defect recording or notification processing. Which
object can be used for the combination of code groups from several catalogs?
A
Explanation:
In SAP S/4HANA QM, combining code groups from multiple catalog types (e.g., defects, causes) into
a single object is necessary for processes like defect recording or notifications:
Catalog Profile (A): The catalog profile (maintained via transaction QPCD or Customizing) is designed
to group code groups from different catalog types (e.g., defect types, causes, activities) into a single
entity. It’s assigned to objects like material masters or notification types, enabling consistent use of
codes across processes like defect recording (e.g., in inspection lots) or notification processing (e.g.,
QN01). This is the standard object for this purpose.
Report Type (B): Report types (SPRO > QM > Quality Inspection > Define Report Types) define the
layout of defect recording but do not combine code groups from catalogs; they reference catalog
profiles instead.
Selected Set (C): A selected set (transaction QS51) is a subset of codes from one catalog type, not a
combination across multiple types.
Confirmation Profile (D): Confirmation profiles are used in production (e.g., PP) for operation
confirmations, not QM catalog management.
Thus, "Catalog profile" is the correct answer, as it’s the dedicated object for combining codes from
multiple catalogs.
Reference: SAP Help Portal - "Catalog Profiles in QM"; SAP S/4HANA QM Customizing Guide -
"Catalog Management".
Which of the following dynamic modification criteria can be used in the inspection plan? Note: There
are 3 correct answers to this question.
A, D, E
Explanation:
Dynamic modification in SAP S/4HANA QM allows the system to adjust inspection scopes (e.g., skip
lots, reduced inspection) based on quality performance. These criteria are defined in the inspection
plan (transaction QP01) or Quality Level settings and determine when modification occurs:
Material and Supplier (A): This is a standard dynamic modification criterion (e.g., for inspection type
01 - Goods Receipt). It tracks quality history for a material-supplier combination, commonly used in
procurement scenarios (SPRO > Quality Management > Quality Inspection > Dynamic Modification).
Material and Customer (D): Used in sales or production scenarios (e.g., inspection type 10 - Delivery),
this criterion adjusts inspections based on material-customer quality history, ensuring customer-
specific requirements are met.
Material (E): A standalone material criterion is valid across multiple inspection types (e.g., 03 -
Production), allowing modification based solely on the material’s quality history, regardless of
supplier or customer.
Material and Work Center (B): Work centers are linked to operations, not directly to dynamic
modification criteria in standard SAP QM. This is not a predefined option.
Material and Equipment (C): Equipment is relevant for plant maintenance (PM), not a standard QM
dynamic modification criterion for inspection plans.
Thus, "Material and supplier," "Material and customer," and "Material" are the correct answers,
reflecting standard SAP functionality.
Reference: SAP Help Portal - "Dynamic Modification in QM"; SAP S/4HANA QM Customizing Guide -
"Dynamic Modification Rules".
Which objects can be used as a reference when dependent characteristics specifications are created?
Note: There are 3 correct answers to this question.
C, D, E
Explanation:
Dependent characteristic specifications in SAP QM allow characteristics in an inspection plan to
inherit values (e.g., tolerances) from a reference object. This is configured in the inspection plan
(transaction QP01) under characteristic details:
Material and Customer (C): Used in sales-related inspections (e.g., inspection type 10), this reference
allows characteristics to be tailored to customer-specific material requirements, pulling data from
the material master or customer info records.
Material and Supplier (D): Common in procurement (e.g., inspection type 01), this reference links to
quality info records or material master data, enabling supplier-specific specs for a material.
Material (E): The material alone can serve as a reference, pulling general specifications from the
material master (e.g., QM view) or material specifications (transaction QS61), applicable across
scenarios.
Material and Control Key (A): Control keys define operation behavior, not characteristic
specifications, so this is not a valid reference.
Material and Work Center (B): Work centers are operation-specific and don’t store characteristic
specs for reference in standard SAP.
Thus, "Material and customer," "Material and supplier," and "Material" are the correct answers.
Reference: SAP Help Portal - "Dependent Characteristic Specifications"; SAP S/4HANA QM User
Guide - "Inspection Planning".
The sample size is determined using the sampling procedure. What assignments are mandatory in
the sampling procedure? Note: There are 2 correct answers to this question.
C, D
Explanation:
A sampling procedure in SAP S/4HANA QM (transaction QDV1) defines how samples are calculated
and valuated for an inspection lot. Mandatory assignments ensure the system can determine and
process the sample:
Sampling Type (C): This is a required field in the sampling procedure header. It specifies how the
sample size is determined (e.g., fixed sample, percentage, sampling scheme). Without it, the system
cannot calculate the sample size (e.g., "100% inspection" or "Attribute sampling").
Valuation Mode (D): Also mandatory, this defines how inspection results are evaluated (e.g., "Manual
valuation," "Attribute inspection nonconforming units"). It’s assigned in the sampling procedure and
ensures consistent acceptance/rejection rules.
Inspection Severity (A): This is optional and applies only to sampling schemes (e.g., normal,
tightened), not all sampling types.
Unit of Measure (B): The unit of measure is inherited from the material or characteristic, not a
mandatory assignment in the sampling procedure itself.
Thus, "Sampling type" and "Valuation mode" are the correct answers, as they are essential
components of every sampling procedure.
Reference: SAP Help Portal - "Sampling Procedures in QM"; SAP S/4HANA QM Customizing Guide -
"Sample Management".
Which QM basic data can be used in the material specification? Note: There are 3 correct answers to
this question.
A, C, E
Explanation:
Material specifications in SAP QM (transaction QS61) define inspection requirements directly in the
material master, independent of task lists. They integrate specific QM basic data:
Master Inspection Characteristics (A): MICs are the core of material specifications, defining what is
inspected (e.g., length, pH). They are assigned to the material spec to set tolerances or qualitative
codes.
Sampling Procedures (C): These determine the sample size for the material spec’s characteristics
(e.g., fixed sample of 5). They are assigned to MICs within the material specification.
Inspection Methods (E): Inspection methods (e.g., "Visual check") can be linked to MICs in the
material spec to specify how the inspection is performed.
Dynamic Modification Rule (B): This governs inspection scope changes (e.g., skip lots) and is assigned
to inspection types or plans, not material specs directly.
Selected Set (D): Selected sets are used for qualitative valuations (e.g., UD codes) but are not directly
assigned to material specs; they link via MICs instead.
Thus, "Master inspection characteristics," "Sampling procedures," and "Inspection methods" are the
correct answers.
Reference: SAP Help Portal - "Material Specifications in QM"; SAP S/4HANA QM User Guide - "Basic
Data".
Which dynamic modification levels can be set in the inspection plan? Note: There are 3 correct
answers to this question.
A, C, D
Explanation:
Dynamic modification levels in SAP QM determine the granularity at which inspection scope changes
(e.g., reduced to full inspection) are applied in an inspection plan (transaction QP01):
Characteristic Level (A): Modification can occur at the individual characteristic level within an
operation, allowing specific MICs to skip or intensify based on their quality history.
Inspection Lot Level (C): The entire inspection lot can be modified (e.g., skipped), based on the
quality level for the material or combination (e.g., material/supplier).
Operation Level (D): Modification can apply to an operation, adjusting all characteristics within it
based on performance (e.g., operation-specific skip).
Inspection Type Level (B): Inspection types define the process (e.g., 01 for GR), but dynamic
modification is not set at this level; it’s tied to plans or lots.
Work Center (E): Work centers are execution locations, not a level for dynamic modification in QM.
Thus, "Characteristic level," "Inspection lot level," and "Operation level" are the correct answers.
Reference: SAP Help Portal - "Dynamic Modification in Inspection Planning"; SAP S/4HANA QM
Customizing Guide - "Dynamic Modification".