Free Practice Questions for SAP C_TS414_2023 Exam

When a quality certificate is mandatory (set in the quality info record, transaction QI01) but no GR inspection lot is created (inspection type 01 inactive in the material master), the system handles the missing certificate as follows:

The Goods Receipt is Posted to Blocked Stock (B): If the certificate is required (e.g., "Certificate Check" active in QI01) and not received (transaction QC55), the GR (transaction MIGO) posts the material to blocked stock (movement type 103/105 process). This is standard behavior to prevent unrestricted use until the certificate is confirmed, even without an inspection lot (SPRO > QM > Quality Certificates > Procurement > DefineControl Keys).

Unrestricted Use Stock (A): This would occur only if no certificate check was enforced, contradicting the premise.

Quality Notification Created Automatically (C): Notifications require manual creation or specific Customizing (e.g., defect recording), not automatic generation here.

Missing Certificate Escalated (D): Escalation is not a standard SAP term or process in this context; it implies custom workflow not present in standard QM.

Thus, "The goods receipt is posted to blocked stock" is the correct answer.References: SAP Help Portal - "Certificate Processing at Goods Receipt"; SAP S/4HANA QM User Guide - "Stock Posting".

When inspection lots are created automatically for delivery items (inspection type 10) and the sample size isn’t calculated (status CRTD):

The System Cancels the Lot (B): If the delivery item is removed (e.g., via VL02N), the associated inspection lot is canceled automatically because its reference (the delivery item) no longer exists. The system updates the lot status to "CANC" (SPRO > QM > Quality Inspection > Inspection Lot Creation > Define Follow-Up Actions). This is standard behavior to maintain data consistency.

Posts a Usage Decision (A): UD (transaction QA11) requires sample calculation and results, which hasn’t occurred here.

Marks the Lot for Cancellation (C): The lot is fully canceled, not just marked, in this scenario.

Sends a Workflow Message (D): Workflow notifications require custom configuration andaren’t standard here.

Thus, "The system cancels the lot" is the correct answer.References: SAP Help Portal - "Inspection Lot Processing for Deliveries"; SAP S/4HANA QM User Guide - "Lot Cancellation".

Task lists (e.g., routings) for production orders in SAP integrate QM master data to enable inspections:

Material Specifications (A): Material specs (transaction QS61) can be referenced in routings (transaction CA01) to define inspection requirements for a material, integrating QM into production.

Master Inspection Characteristics (C): MICs (transaction QS21) are directly assigned to operations in routings or inspection plans, specifying what to inspect during production.

Classifications (B): Classifications (transaction CL01) are batch or material attributes, not directly integrated into task lists for production orders.

Control Indicators (D): These are settings within characteristics or plans, not standalone master data for integration.

Thus, "Material specifications" and "Master inspection characteristics" are the correct answers (assuming a multiple-choice intent, though only two are clearly correct based on standard SAP).References: SAP Help Portal - "QM Integration with PP"; SAP S/4HANA QM User Guide - "Task Lists".

Activity recording (e.g., time or cost) for inspection lots of origin 01 (Goods Receipt) requires:

Inspection Operations with Work Centers (B): Operations in the inspection plan (transaction QP01) must have work centers assigned, as these link to activity types (e.g., labor) for recording effort or costs during inspection (SPRO > QM > Quality Planning > Inspection Planning).

Inspection Lot with a QM Order (D): A QM order (e.g., created via Customizing or lot assignment) is required to capture activity data (e.g., via transaction QE51N or CO11N), linking costs to the inspection lot (SPRO > QM > Quality Inspection > Inspection Lot Creation > Define Inspection Types).

Inspection Specifications with Master Inspection Characteristics (A): MICs define what’s inspected but aren’t prerequisites for activity recording.

Inspection Specifications with Inspection Methods (C): Methods guide execution, not activity recording setup.

Thus, "Inspection operations with work centers" and "Inspection lot with a QM order" are the correct answers.References: SAP Help Portal - "Activity Recording in QM"; SAP S/4HANA QM User Guide - "Cost Management".

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.References: SAP Help Portal - "Status Profiles in QM Notifications"; SAP S/4HANA QM User Guide - "Notification Status".

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.References: SAP Help Portal - "Integration APIs in S/4HANA"; SAP S/4HANA Developer Guide - "Clean Core APIs".

Certificate profiles in SAP QM (transaction QC01) define the data included in outgoing quality certificates. The characteristic categories allowed are:

Master Inspection Characteristic (A): MICs (transaction QS21) are used in inspection plans and material specs, and their results can be included in certificate profiles to report quality data (e.g., measured values).

Class Characteristic (B): Class characteristics (from the Classification System, transaction CT04) are linked to batches or materials and can be included in certificate profiles to display classification data (e.g., batch properties).

Inspection Characteristic (C): This term refers to characteristics in an inspection lot/plan but is not a distinct category; it’s covered by MICs, so it’s not separately selectable.

Process Instruction Characteristic (D): Used in Process Industries (PI) for production, not applicable to QM certificate profiles in standard SAP.

Thus, "Master inspection characteristic" and "Class characteristic" are the correct answers.References: SAP Help Portal - "Quality Certificates - Certificate Profiles"; SAP S/4HANA QM User Guide - "Outgoing Certificates".

Sample-drawing items in the sample-drawing procedure (transaction QPV2) specify:

Number of Samples (B): Defines how many samples (e.g., 5 units) are drawn per item, a key field in the item details.

Sample Categories (D): Specifies the type (e.g., primary, reserve, pooled) for each sample-drawing item, a mandatory attribute.

Confirmation of Sample Drawing (A): Confirmation occurs in sample management (e.g., QPR2), not stored in the procedure item.

Sample Drawing Based on Number of Containers (C): This is a rule in the procedure header, not an item-specific detail.

Thus, "Number of samples" and "Sample categories" are the correct answers.References: SAP Help Portal - "Sample-Drawing Procedure"; SAP S/4HANA QM User Guide - "Sample Management".

In SAP S/4HANA QM, the action box in quality notifications (e.g., transaction QM02) triggersfollow-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.References: SAP Help Portal - "Action Box in Quality Notifications"; SAP S/4HANA QM User Guide - "Notification Processing".

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.References: SAP Help Portal - "Material Master in QM"; SAP S/4HANA QM User Guide - "QM View in Material Master".