--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Should we use Inspection 17 or Inspection Type 1701 for EWM integration with the SAP QM Module for Inspection Lot triggering for RR and UD?
Answer: Understanding Inspection type 17 and 1701
- Inspection type 17: Acts as a generic, externally triggered inspection origin category in Quality Management (SAP QM). It enables external modules—predominantly SAP EWM—to trigger and drive quality inspection lots in the backend ERP system.
- Inspection type 1701: A customized or specific sub-type derived from origin 17. It is mapped to manage goods receipt inspections coming from external vendors/purchase orders under an EWM-managed warehouse ecosystem.
- Both inspection type 17 and custom-copied variants like 1701 (tied to inspection lot origin 17) can be used for SAP Extended Warehouse Management (EWM) to SAP Quality Management (QM) integration.
Click below of using Inspection type 17 for EWM-QM integration but Inspection type 1701 can also be used (it was just as a variant to Inspection type 17 with slight parameter fine-tune):
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of the Basic Sampling Procedures in SAP QM.
Answer: In SAP Quality Management (QM), sampling procedure types (known as sampling types) dictate how the system calculates the required sample size from an inspection lot. Managed via transaction QDV1, the primary sampling types include:
- Fixed sample sizes
- Percentage-based sizing
- 100% inspections
- Rule-based sampling schemes (Lot-size dependent)
Click below link to review the step-by-step to create basic Sampling Procedure and Sampling Scheme:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of SAP Dynamic Modification Rule.
Answer: DMR stands for Dynamic Modification Rule.
- It is a control mechanism used to automatically adjust the inspection scope—such as sample sizes, testing frequencies, or skip lots based on the historical quality performance of a vendor, material, or manufacturing process.
- Key Purposes of DMR:
- Reduce Inspection Effort: Automatically skip or reduce testing for reliable suppliers or stable production lines with a strong track record of accepted lots.
- Increase Rigor on Demand: Automatically tighten or revert inspection intensity back to normal or stricter stages if a quality defect or rejection occurs.
- Save Time and Cost: Lower testing and administrative overhead on high-volume, routine goods receipts.
- a Dynamic Modification Rule (DMR) in SAP QM can be used with or without a sampling scheme. The DMR controls the stage changes (such as normal, reduced, tightened, or skip), while the sampling scheme is only required if you want the system to dynamically look up sample sizes based on lot sizes and AQL tables.
Click below link to review the step-by-step to create the Dynamic Modification Rule:
https://docs.google.com/DMR-in-action/
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of steps to create Qualitative and Quantitative Inspection Characteristics.
Answer: In SAP Quality Management (QM), a Master Inspection Characteristic (MIC) defines how a material property is inspected. A quantitative MIC deals with measurable, numerical values requiring units and tolerance limits (e.g., length, weight, pH), while a qualitative MIC involves descriptive, non-numeric attributes evaluated via catalogs or codes (e.g., color, surface finish, pass/fail).
- Quantitative MIC:
- Data format: Numerical values with specific decimal places.
- Key fields: Unit of measurement (UoM), target value, lower specification limit, and upper specification limit.
- Examples: Length (\(50\text{ mm} \pm 0.5\)), temperature, viscosity, or weight.
- Usage behavior: During results recording, the user enters an exact number, and SAP automatically valuates it as accepted or rejected based on the predefined tolerance limits
- Qualitative MIC:
- Data format: Descriptive text or attribute evaluations.
- Key fields: Code groups and selected sets instead of numerical tolerances.
- Examples: Visual appearance (Scratch/No scratch), color (Red/Green), or status (OK/Not OK, Pass/Fail).
- Usage behavior: During results recording, the inspector selects an evaluation code from a predefined dropdown catalog rather than typing a number.
Click below link to review the step-by-step to create the Dynamic Modification Rule:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review on 3 usages of Catalogs in SAP QM
Answers: There are 3 usages of Catalogs in SAP QM:
- Catalog type "1" for Qualitative Master Inspection Characteristics "Attributes".
- IMG - Quality Management - Quality Planning - Basic Data - Catalogs - Edit Catalogs for Inspection Characteristics.
- Catalog type "3" for Usage Decision "UD Codes".
- IMG - Quality Management - Quality Inspection - Inspection Lot Completion - Edit Code Groups and Codes of Usage Decisions.
- IMG - Quality Management - Quality Inspection - Inspection Lot Completion - Edit Selected Sets for Usage Decisions.
- Catalog type "
- IMG - Quality Management - Quality Notifications - Notification Creation - Notification Contents - Maintain Catalogs.
- IMG - Quality Management - Quality Notifications - Notification Creation - Notification Contents - Define Catalog Profile.
Click below link to review the Catalog Code Group, Codes, and Selection Set creations:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What is the purpose of Usage "000" in the QM Work Center?
Answer: Task list usage 000 stands for "No task list categories" or "No task list usage allowed." Its purpose is to act as a strict restriction that completely prevents the work center from being used in any production routing, master recipe, or quality inspection plan:
Key Characteristics of Usage 000:
- Blocking mechanism: Stops schedulers or planners from accidentally or intentionally assigning the work center to operations inside a task list.
- Master data protection: Used for administrative, phantom, or non-operational work centers that exist for costing or capacity purposes only, but should never host physical processing or inspection steps.
- Validation control: When the system checks task list operations during creation or saving, a work center marked with 000 triggers an error if referenced.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Why Reference MIC cannot update the Defect code changed in the Ref.MIC to the Inspection Plan?
Answer: As long as it is not unlocked and remain as reference characteristics, settings from the Control data, Attribute catalog assignment, defect code assignment (for Qualitative MIC) are referenced from the MIC to the Inspection Plan's MIC where it is assigned.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: DMR criteria difference at Inspection Type level vs Inspection Lot level?
Answer: The core difference between assigning a Dynamic Modification Rule (DMR) at the Inspection Type level versus the Inspection Lot (Task List Header) level centers on whether an Inspection Plan (Task List) is required to trigger the rules.
Recommendation:
Setting a Dynamic Modification Rule (DMR) at the
inspection lot level (via the inspection plan header) is generally recommended over the inspection type level in the material master. Lot-level setup gives you precise control to link rules to specific vendor-material combinations or task lists, whereas inspection type level applies a single rule globally to all receipts:
Why Inspection Lot Level is Preferred:
- Vendor Differentiation: Allows different skip or tightening rules for different suppliers providing the same material.
- Flexibility: Easily managed and modified inside the inspection plan header (QP01 / QP02) rather than changing core material master settings (MM01 / MM02).
- Targeted Scope: Better suited when you want to dynamically skip or inspect entire lots and all characteristics uniformly based on task list assignments.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Questions: issues of Results Recording via FIoir App "Record Inspection Results".
Answer: Updating issues in the SAP Fiori app for Quality Management (QM) results recording (such as app F1685 "Record Inspection Results") typically stem from the following
Technical Architecture Bottlenecks:
- Cache Desynchronization: UI5 metadata caches and browser caches often fail to clear automatically during transport updates, showing stale screen fields that reject inputs.
- Multi-Layered Caching Visual Bottlenecks: Fiori relies heavily on multiple caching layers to optimize application performance. When an inspector records a result, the backend might update perfectly, but the frontend app still displays old data or spinner loops because the UI caches are not synchronized.
- OData Metadata Cache: The Gateway server keeps a cached structure of the QM fields. If backend configurations change, the OData cache blocks the frontend from passing data.
- UI5 App Index & Browser Cache: Local network settings and outdated browser states frequently fail to pull the latest transactional data from the serve.
- OData and Gateway Failures: Front-end actions rely on multiple deep OData payload batches; if a single property mapping or CSRF token expires or errors out, the entire update rolls backs.
- OData Service and Authorization Timeouts: Fiori apps communicate via OData services which process user actions as stateless HTTP requests.
- Gateway Layer Timeouts: Large inspection lots with hundreds of quantitative characteristics force massive OData payloads. If the backend takes too long to validate the inspection specifications, the Gateway server times out, discarding the entered data.
- Missing DCL/CDS Authorizations: S/4HANA Fiori apps use Data Control Language (DCL) and CDS views to restrict data visibility. If an inspector has standard backend role permissions but lacks specific frontend catalog/group authorizations, updates will drop silently without showing a traditional SU53 error.
- Strict master data control indicators: that classic GUI transactions handle more forgivingly.
- Slow Internet Disrupts Data Entry: Slow internet directly causes SAP Fiori data entry issues. Because Fiori operates as a web-based interface relying heavily on continuous client-server communication, low bandwidth, high latency, or packet loss will disrupt the data entry workflow.
- HTTP Timeouts and Lost Drafts: If a network connection drops or data payloads take too long to send, the SAP Gateway or Web Dispatcher will trigger a PROCTIMEOUT or gateway timeout. This causes the submission to fail, often wiping out unsaved form data.
- Frozen UI and Sync Stalls: Fiori relies on background JavaScript libraries. Slow internet can stall asynchronous data validation (e.g., checking if a material number exists). This prevents users from clicking the "Save" or "Submit" buttons.
- Session Expiry (XSRF Token Failures): If a user takes too long to fill out a complex data entry form due to slow network lag, the background security token (XSRF) or the launchpad session may expire mid-entry. Submitting the form after this happens results in an "Unauthorized" 401 error.
Recommended Diagnostic and Troubleshooting:
- Check Chrome DevTools: Press F12 and navigate to the Network tab. Look for long-running OData calls ($batch requests) or red failed responses.
- Review Latency: Run a ping test to your SAP routing domain. Latency over 200ms frequently degrades the Fiori input experience.
- Clear Browser Cache: Ensure that core UI5 application libraries are fully cached locally so the internet connection is only used for raw data entries, not interface assets.
- Consider WTS/Citrix: If your remote location has permanently low bandwidth, access Fiori through a Windows Terminal Service (WTS) or Citrix environment located closer to the data center.
- Consult BTP experts: For expert troubleshooting and issue address, should consult the BTP experts as the above is only from the perspective of a non-technical person.
CLICK here to view Fiori App-based RR and UD:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of the 3 methods of Results Recording via SAP GUI.
Answer: There are basically 3 methods of RR Classic but SAP also provide enhanced RR via Fiori UX:
- QE51N.
- QA32.
- QE72 or QE73.
Click here for the step-by-step for enhanced Multi-MIC RR Form via Fiori App:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: QM Notification ACTION Box feature (Complaint to Vendor).
Answer: The Action Box in SAP Quality Management (QM) is a user-friendly toolbar inside quality notifications (like transactions QM02 or QM03) that lets users quickly execute follow-up tasks—such as sending emails, creating internal notes, triggering return deliveries, or calling custom ABAP function modules with a single click.
Click here to view the Presentation:
https://docs.google.com/ActionBoxMMReturntoVendor/
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: QM Activation Notification for Defect Recording from Inspection Lot.
Answer:
Defect Recording captures non-conformities when a material, product, or process fails inspection specs.
Key Recording Levels for Defect Recording:
- Inspection Lot Level: Applied broadly to the entire lot.
- Operation Level: Tied to a specific manufacturing step.
- Characteristic Level: Linked directly to a Master Inspection Characteristic (MIC).
Defect Recording can be activated and linked to a Quality Management (QM) notification in SAP. When a defect is logged either manually or automatically during results recording, it creates an initial defect record (status DEFR). This record can then be manually or automatically activated to trigger a full quality notification for task tracking and corrective actions.
Click here to view the Presentation:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review of Digital Signature basic setup and processing for QM Usage Decision.
Answer: A
Digital Signature in SAP Quality Management (QM) is an electronic tool that acts as a legally binding, forgery-proof equivalent to a handwritten signature. It records who approved a specific quality task, along with the exact date and time, ensuring data integrity in regulated manufacturing environments.
Key Areas in SAP QM for Digital Signature implementation:
- Results Recording: Enforces verification and sign-off by an authorized user when test or inspection results are entered and saved.
- Usage Decision (UD): Requires an authorized electronic signature before a final batch or lot usage decision can be approved and posted.
- Physical-Sample Drawing: Validates and documents the physical sample drawing and the release of initial physical samples.
- Quality Certificates: Authenticates inbound or vendor quality certificate processing within inspection lots.
Click here to view the Presentation:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review QM Appraisal Costing for Inspection Lot.
Answer: In SAP Quality Management (QM), a QM Order for Appraisal Costs is a specific internal cost collector used to track and measure the expenses incurred during quality inspections—such as labor, machine usage, or testing activities. These activity times are recorded during results recording and settled periodically into Controlling (CO).
Click here to view the Presentation:
https://docs.google.com/QM Order for Appraisal Cost/
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: Review QM Non-Conformance Costing for QM Notification.
Answer: SAP
QM Non-conformance Costing captures and tracks internal and external failure expenses such as scrap, rework, and labor using Quality Notifications tied to internal QM orders. Costs are accumulated via activity confirmations, material consumption, or direct postings to analyze financial losses tied to quality defects.
Click here to view the Presentation:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Question: What is SAP Auto-ID Infrastructure (AII)?
Answer: SAP Auto-ID Infrastructure (AII) is a Middle-ware that connects the RFID to SAP EWM system.
Click here to view the Presentation:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
_Blogged.jpg)
_Blogged%20(1).jpg)
_Blogged%20(2).jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
