Defect Recording

Interview questions covered

• In a delivery inspection scenario integrated with EWM, defects are recorded during results recording but the warehouse team reports they cannot see defect details on the physical inventory or quality inspection document in EWM. How do you address this integration gap?
• During in-process inspection of a semi-finished product, an operator records a defect indicating a dimensional out-of-tolerance condition, and the material is later required to be shipped with a quality certificate referencing the batch's inspection results. How should defect recording and certificate generation be coordinated to ensure the certificate accurately reflects the nonconformance?
• During a catalog restructuring project, defect codes from a legacy selection set were merged into a new catalog code group, but historical usage decision reports now show inconsistent defect descriptions across inspection lots created before and after the change. How would you diagnose and prevent this?
• During a rollout, business users report that the same defect type catalog is showing irrelevant codes for both incoming inspection notifications and customer complaint notifications. How would catalog profiles be restructured to fix this cross-contamination?
• A quality organization is consolidating defect catalogs after a merger and finds overlapping code groups with slightly different meanings for the same defect type across legacy systems. How would you approach redesigning the catalog and code group structure to support consistent reporting?
• Design a defects recording architecture for final inspection lots that must support root-cause analytics across multiple plants feeding a common SD delivery process, while avoiding master data duplication.
• An architect is troubleshooting a recurring issue where defects recorded during incoming inspection are not appearing in the vendor evaluation score despite correct usage decisions. What root causes should be investigated?
• During in-process inspection at a production order's final operation, an operator records a defect for a minor cosmetic nonconformance, but the certificate of analysis for the batch still needs to be generated and shipped with the product since the defect does not affect functional specifications. How would you configure defect and certificate handling to support this?
• A quality manager wants to introduce a new defect classification scheme for customer complaints without disrupting existing usage decision codes and historical reporting. How would you approach catalog and code group design?
• Supplier quality analytics show that a large percentage of notifications are being closed with a generic 'other' defect code, making root-cause trend reporting meaningless. How would you diagnose and correct this at a configuration level?
• During a customer complaint investigation, defects recorded against a sales-return inspection lot (origin 06) are not appearing in the QM defect analysis reports that procurement and production teams rely on for supplier and process quality metrics. As the architect, how would you diagnose and resolve this cross-functional visibility gap?
• After a catalog profile change was deployed, quality analysts report that when creating new complaint notifications, the defect code fields on the item are now blank/unavailable, breaking their analytics extracts. What would you check to diagnose and resolve this?
• During incoming inspection (lot origin 01) a goods receipt is inspected and defects are found on several sample units. What is the standard SAP QM process for recording these defects at the inspection lot level, and how do defects relate to the results recording of the associated inspection characteristics?
• A production nonconformance notification must classify a defect by defect location, defect type, cause, and action taken. How should the catalog structure be designed to support this?
• When configuring defect recording for delivery inspections integrated with EWM, what configuration decisions must be made to ensure defects captured during results recording are properly linked to the inspection lot and visible for corrective action tracking?
• During in-process inspection of a PP order, an operator records results for a sub-lot but the follow-up action for defect recording is not triggering the expected quality notification. Walk through how you would diagnose this in the inspection lot.
• During a sales returns inspection, an inspector records a defect against a characteristic but the defect data isn't showing up correctly linked to the returned batch when the warehouse team later checks the WM transfer order history. What could cause this disconnect and how would you fix it?
• When defects are recorded during results recording for a delivery-based inspection lot integrated with EWM, what configuration decisions determine how defect data is structured and linked back to the inspection lot?
• A QM team wants inspectors recording results at goods receipt to see only a short, relevant list of defect codes for a given material category, while the full code group retains dozens of codes used across multiple material types shared with MM master data reporting. How would you use a selected set to solve this without duplicating the code group, and what MM reporting impact should you validate?
• During in-process inspection of a production order, an operator records a defect against a dimensional characteristic, and the batch must later be accompanied by a certificate that accurately reflects this nonconformance before the next PP confirmation step proceeds. How would you design this?

Related topics