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?
Correct Answer: A
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.References: SAP Help Portal - "Catalog Profiles in QM"; SAP S/4HANA QM Customizing Guide - "Catalog Management".
Question 17
During which of the following steps in a business process does a dynamic modification rule change severely
Correct Answer: A
Question 18
An inspection plan group includes multiple inspection plans with different group counters. What determines the selected inspection plan when you create an inspection lot?
Correct Answer: D
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 directlydetermine 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.References: SAP Help Portal - "Inspection Planning with Task Lists"; SAP S/4HANA QM User Guide - "Inspection Lot Creation".
Question 19
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.
Correct Answer: C,D
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".
Question 20
What master data can you integrate into a task list for a production order?
Correct Answer: A,C
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".
