Questions for the C-TS414-2023 were updated on : Dec 01 ,2025
Which of the following are features of the clean core dashboard? Note: There are 2 correct answers
to this question.
B, C
Explanation:
The clean core dashboard in SAP S/4HANA monitors system adherence to clean core principles:
Customers Can Use the Dashboard in the Dev, Test, and Production Tenants (B): The dashboard is
available across all system tenants (development, test, production) to assess clean core status
universally.
It Can Be Accessed by Using SAP For Me (C): SAP For Me (customer portal) provides access to the
clean core dashboard, a standard entry point as of 2025.
Customers Can Grant Access to Partners (A): Partner access isn’t a standard feature; it’s customer-
controlled.
It Can Be Used in All SAP S/4HANA Cloud Editions (D): Primarily for Cloud Private Edition and Public
Cloud, not guaranteed for all editions (e.g., on-premise specifics vary).
Thus, "Customers can use the dashboard in the dev, test, and production tenants" and "It can be
accessed by using SAP For Me" are the correct answers.
Reference: SAP Help Portal - "Clean Core Dashboard"; SAP S/4HANA Cloud User Guide - "SAP For
Me".
Which of the following API types does SAP recommend to use to achieve clean core integrations?
Note: There are 2 correct answers to this question.
A, D
Explanation:
For clean core integrations in SAP S/4HANA (minimizing custom code):
SOAP (A): SAP recommends SOAP APIs for robust, secure integrations (e.g., enterprise services),
supporting clean core by leveraging standard interfaces.
OData (D): OData is the preferred RESTful API type for S/4HANA, enabling flexible, standard
integrations (e.g., via SAP Gateway), a cornerstone of clean core.
RFC (B): Remote Function Calls are legacy and less favored for clean core due to tight coupling.
IDoc (C): IDocs are traditional EDI-focused, not prioritized for modern clean core integrations.
Thus, "SOAP" and "OData" are the correct answers.
Reference: SAP Help Portal - "Integration APIs in S/4HANA"; SAP S/4HANA Developer Guide - "Clean
Core APIs".
What are some SAP recommended guiding principles to achieve clean core operations? Note: There
are 3 correct answers to this question.
A, B, C
Explanation:
SAP’s clean core principles (as per S/4HANA Cloud strategy) aim for a standardized, upgrade-friendly
system:
Establish an Organizational Structure, Technical Foundation, and Transformation Methodology for
Clean Core (A): This foundational principle ensures governance and methodology (e.g., SAP Activate)
for clean core adoption.
Integrate Clean Core Practices in the End-to-End Value Process Chain (B): Embedding clean core into
business processes ensures minimal customization and maximum standard use.
Establish Regular Housekeeping Tasks and Procedures (C): Ongoing maintenance (e.g., data cleanup)
keeps the system lean and standard-compliant.
Establish Release Management (D): While important, it’s a broader IT practice, not a core clean core
principle.
Define Roles and Responsibilities as Part of a Process Transformation Office (E): Useful but not a
primary SAP-defined clean core principle.
Thus, "A, B, C" are the correct answers.
Reference: SAP Help Portal - "Clean Core Strategy"; SAP S/4HANA Cloud Best Practices - "Clean
Core".
Which of the following can you use to explore released APIs?
B
Explanation:
To explore released APIs in SAP S/4HANA:
SAP Business Accelerator Hub (B): Formerly SAP API Business Hub, this is the official platform
(https://api.sap.com) to explore, test, and access released APIs for SAP S/4HANA, including QM-
related APIs (e.g., Inspection Lot API). It’s the standard tool as of 2025.
SAP Application Interface Framework (A): AIF is for monitoring and managing interfaces, not
exploring APIs.
SAP Integration Suite (C): This is for building integrations, not a primary API exploration tool.
Thus, "SAP Business Accelerator Hub" is the correct answer (single-choice context assumed).
Reference: SAP Help Portal - "SAP Business Accelerator Hub"; SAP S/4HANA Developer Guide -
"APIs".
You create a complaint against a supplier with reference to the material document year, number, and
item. You create it from a goods receipt for the purchasing document. What information is copied to
the notification? Note: There are 3 correct answers to this question.
A, B, C
Explanation:
When creating a supplier complaint notification (e.g., Q2) from a goods receipt material document
(transaction QM01):
Purchasing Document Number and Item (A): The PO number and item are copied from the material
document (linked via MIGO), providing the procurement context.
Material Number (B): The material number is transferred to identify the affected product.
Inspection Lot Number (C): If an inspection lot (e.g., type 01) was created during GR, its number is
copied to link quality data (SPRO > QM > Quality Notifications > Integration with Inspection Lots).
Reference Quantity and Unit (D): Quantity is referenced but not automatically copied to the
notification header/item in standard SAP.
Advanced Shipping Number (E): ASN is logistics-related (e.g., inbound delivery), not typically copied
from a material document.
Thus, "Purchasing document number and item," "Material number," and "Inspection lot number" are
the correct answers.
Reference: SAP Help Portal - "Notification Creation from Goods Receipt"; SAP S/4HANA QM User
Guide - "Supplier Complaints".
You want to create a quality notification for the Complaint Against Supplier notification origin. Which
of the following documents are available as standard in SAP S/4HANA to use as reference
documents? Note: There are 2 correct answers to this question.
B, C
Explanation:
For a "Complaint Against Supplier" notification (e.g., type Q2, transaction QM01):
Material Document (B): Material documents (e.g., goods receipt via MIGO) are standard references,
linking the complaint to a specific receipt event (SPRO > QM > Quality Notifications > Notification
Creation).
Purchasing Document (C): Purchase orders (e.g., from ME21N) are commonly referenced to tie the
complaint to the supplier’s delivery or order.
WBS Element (A): Work Breakdown Structure elements are PS-related, not standard for supplier
complaints.
QM Order (D): QM orders track costs but aren’t reference documents for notification creation.
Thus, "Material document" and "Purchasing document" are the correct answers.
Reference: SAP Help Portal - "Reference Documents for Supplier Complaints"; SAP S/4HANA QM
User Guide - "Notification Creation".
During quality notification processing, the activities from the action box can be used. How can the
activities be documented in the quality notification? Note: There are 2 correct answers to this
question.
C, D
Explanation:
In SAP S/4HANA QM, the action box in quality notifications (e.g., transaction QM02) triggers follow-
up actions, which can be documented as:
As Task (C): Activities from the action box (e.g., "Send email") can be created as tasks in the
notification’s task tab, using catalog type 2 (Tasks). This is a standard option for actionable steps
(SPRO > QM > Quality Notifications > Define Action Box).
As Activity (D): Activities can be logged in the activities tab (catalog type 8) to record completed
actions (e.g., "Email sent"), documenting the execution of the action box entry.
As Cause (A): Causes (catalog type 5) describe why an issue occurred, not action box outcomes.
As Item (B): Items detail defects or problems, not action documentation.
Thus, "As task" and "As activity" are the correct answers.
Reference: SAP Help Portal - "Action Box in Quality Notifications"; SAP S/4HANA QM User Guide -
"Notification Processing".
You have entered a priority during creation of a notification. What action will this trigger in the
system?
C
Explanation:
Entering a priority (e.g., "High") in a quality notification (transaction QM01):
Calculate the Notification Start and Finish Dates (C): The priority (set in Customizing, SPRO > QM >
Quality Notifications > Define Priorities) triggers the system to calculate required start and end dates
based on response times linked to the priority (e.g., 24 hours for "High"). This is standard behavior
for time-sensitive notifications.
Create Activities Automatically (A): Activities are logged manually or via action boxes, not priority.
Create Tasks Automatically (B): Tasks require a response profile, not just priority.
Calculate Malfunction Dates (D): Malfunction dates are specific to equipment notifications (e.g., F2),
not driven by priority alone.
Thus, "Calculate the notification start and finish dates" is the correct answer.
Reference: SAP Help Portal - "Priorities in QM Notifications"; SAP S/4HANA QM User Guide -
"Notification Processing".
For which structure elements of a quality notification is the assignment of a status profile possible?
Note: There are 2 correct answers to this question.
B, D
Explanation:
Status profiles in SAP QM (defined in SPRO > QM > Quality Notifications > Status Management)
control the lifecycle of notification elements:
Header (B): The notification header (e.g., transaction QM01) can have a status profile assigned to
manage overall statuses (e.g., "Open," "Completed").
Tasks (D): Tasks within the notification (e.g., "Investigate") can have their own status profile to track
individual task progress (e.g., "Released," "Completed").
Activities (A): Activities log events but don’t support status profiles directly.
Items (C): Items (defect details) use catalog types, not status profiles.
Thus, "Header" and "Tasks" are the correct answers.
Reference: SAP Help Portal - "Status Profiles in QM Notifications"; SAP S/4HANA QM User Guide -
"Notification Status".
You want to create a quality notification for the Customer Complaint notification origin. Which of the
following documents are available as standard in SAP S/4HANA to use as reference documents?
Note: There are 2 correct answers to this question.
A, D
Explanation:
For a customer complaint notification (type Q1, transaction QM01), standard reference documents
include:
Delivery (A): Outbound delivery documents (e.g., from VL01N) are commonly referenced, linking the
complaint to a shipped item (SPRO > QM > Quality Notifications > Notification Creation).
Sales Order (D): Sales orders (e.g., from VA01) can be referenced to trace the complaint back to the
original customer order.
Quotation (B): Quotations are pre-sales documents and not standard references for QM notifications.
Material Document (C): Material documents (e.g., GR) are procurement-related, not typical for
customer complaints.
Thus, "Delivery" and "Sales order" are the correct answers.
Reference: SAP Help Portal - "Reference Documents in QM Notifications"; SAP S/4HANA QM User
Guide - "Customer Complaints".
Which partner function is mandatory when creating a quality notification for the Customer
Complaint notification origin?
B
Explanation:
For a quality notification with origin "Customer Complaint" (e.g., type Q1, transaction QM01):
Sold-to Party (B): The sold-to party (customer) is mandatory because it identifies who raised the
complaint, a key field in the notification header linked to SD data (SPRO > QM > Quality Notifications
> Notification Creation > Define Notification Types). Without this, the notification cannot be saved.
Interested Party (A): Optional, used for additional stakeholders.
Contact Person (C): Optional, specifies a customer contact but isn’t required.
Author (D): The creator (system user) is auto-filled, not a mandatory partner function.
Thus, "Sold-to party" is the correct answer.
Reference: SAP Help Portal - "Customer Complaint Notifications"; SAP S/4HANA QM User Guide -
"Partner Functions".
Which of the following are possible starting points for the internal problem-solving process using the
8D methodology? Note: There are 2 correct answers to this question.
A, C
Explanation:
The 8D methodology in SAP QM is an internal problem-solving process triggered by quality issues:
Defects Recording for an Inspection Lot (A): Recording defects in an inspection lot (e.g., transaction
QE51N) can initiate an 8D process via a linked notification (e.g., Q2), a standard starting point (SPRO
> QM > Quality Notifications > 8D Methodology).
Item of a Quality Notification (C): The notification item (e.g., in QM01) directly supports 8D by
documenting the problem (D1) and subsequent steps, a primary entry point.
Defect of Defect Category Generic Defect (B): "Generic Defect" isn’t a standard category; defect types
are specific (e.g., production, supplier).
Defect of the Defect Category Production Defect (D): While relevant, it’s the act of recording (A) or
notification (C) that starts 8D, not the category alone.
Thus, "Defects recording for an inspection lot" and "Item of a quality notification" are the correct
answers.
Reference: SAP Help Portal - "8D Methodology in QM"; SAP S/4HANA QM User Guide - "Problem
Solving".
You can assign objects to the item of a quality notification. Which of the following object categories
are supported in the SAP S/4HANA standard system? Note: There are 3 correct answers to this
question.
A, C, E
Explanation:
In SAP S/4HANA QM, the item of a quality notification (transaction QM01) can reference specific
objects:
Material (A): Materials are a standard object category, linking the notification to a specific material
number (e.g., in the "Reference Object" section).
Batch (C): Batches (LO-BM) can be assigned to track batch-specific issues, a common QM feature.
Serial Number (E): Serial numbers (e.g., for equipment or materials) are supported to pinpoint
individual units, especially in industries like electronics.
Delivery Item (B): Delivery items are referenced in SD notifications but not directly assigned as
objects in the item structure in standard QM.
Purchase Order Item (D): POs are reference documents, not directly assignable objects in the
notification item.
Thus, "Material," "Batch," and "Serial number" are the correct answers.
Reference: SAP Help Portal - "Reference Objects in Quality Notifications"; SAP S/4HANA QM User
Guide - "Notification Items".
For which structure elements of a quality notification is the assignment of a catalog type possible?
Note: There are 3 correct answers to this question.
A, D, E
Explanation:
In SAP S/4HANA QM, quality notifications (e.g., transaction QM01) use catalog types to classify data
in specific structure elements:
Defect Locations (A): Catalog type "A" (Defect Location) can be assigned to specify where a defect
occurred (e.g., "Surface"), configured in the notification item (SPRO > QM > Quality Notifications >
Catalogs).
Defect Types (D): Catalog type "9" (Defect Type) is assigned to classify the nature of the defect (e.g.,
"Scratch"), a standard field in the notification item.
Tasks (E): Catalog type "2" (Tasks) is used to define actions (e.g., "Repair") in the tasks tab of the
notification.
Assigned Objects (B): Objects (e.g., material, batch) are referenced but don’t use catalog types
directly.
Defect Causers (C): Causers (e.g., "Machine") use catalog type "5" (Causes), but this isn’t listed as
"Defect causers" in standard terms; it’s typically "Causes."
Thus, "Defect locations," "Defect types," and "Tasks" are the correct answers based on standard
structure elements.
Reference: SAP Help Portal - "Catalogs in Quality Notifications"; SAP S/4HANA QM User Guide -
"Notification Structure".
You want to complete a quality notification, but an error message appears during the status check.
What could be the cause?
B
Explanation:
Completing a quality notification (e.g., transaction QM02, status NOCO) requires all dependent
objects to be closed:
Open Tasks (B): Open tasks (e.g., "Investigate issue") prevent completion because they indicate
unresolved actions. The system checks task status (e.g., TSOS) and blocks completion if any remain
open (SPRO > QM > Quality Notifications > Define Status Profiles).
Open Defects (A): Defects are recorded in lots or notifications but don’t directly block completion
unless tied to tasks.
Open Activities (C): Activities are logged events, not blockers unless configured as tasks.
Open Causes (D): Causes describe problems but don’t prevent completion unless linked to open
tasks.
Thus, "Open tasks" is the correct answer.
Reference: SAP Help Portal - "Notification Completion in QM"; SAP S/4HANA QM User Guide -
"Status Management".