SAP PP Tolerance Keys: Overdelivery, Underdelivery and OMR6
sap pp tolerance key
Also searched as
- sap production order overdelivery tolerance
- sap underdelivery tolerance production order
- sap OMR6 tolerance key
- sap confirmation tolerance
Short answer
In SAP PP, over- and underdelivery tolerances are set in the Work Scheduling view of the material master and can be overridden on the order, confirmation tolerances are set in the shop floor control IMG, and tolerance keys proper (DQ, PP, ST and others) belong to invoice verification in OMR6.
Applies to: SAP ECC 6.0 and S/4HANA; IMG node names vary slightly by release
How to set and check tolerances
- 1For goods receipt from a production order, open the material in MM02, Work Scheduling view, and set Underdelivery Tolerance and Overdelivery Tolerance in percent.
- 2Set the Unlimited Overdelivery flag only where you accept any surplus, for example by-products.
- 3Check the order: in CO02 the goods receipt tab on the order header shows the tolerances copied from the material and lets you adjust them before receipt.
- 4For confirmations, open SPRO and search for confirmation tolerance settings under Production, Shop Floor Control, Operations, Confirmation. Define the limits for yield, scrap and time variance there.
- 5For invoice verification, run OMR6 and maintain the tolerance key per company code, for example DQ for quantity and PP for price variance.
- 6Test with a goods receipt above the tolerance. The system should issue a message or block, which proves the setting applies.
Where tolerances live in PP
Delivery tolerance is a material and order-level control. The material master supplies the default, the order stores its own copy, and the goods receipt in MIGO or COR6N checks the received quantity against it. If the receipt exceeds the over-tolerance, the system warns or errors, depending on the message control.
Confirmation tolerances are configuration. They define how much the confirmed yield or time may deviate from the planned values before a message appears. They apply to CO11N and CORK style confirmations.
There is no single tolerance key table for PP. People often mean either the delivery tolerance, the confirmation settings or the OMR6 keys. Know which one before you change anything.
OMR6 tolerance keys for invoice verification
OMR6 is the transaction for invoice verification tolerances. Each tolerance key covers one kind of difference: DQ for quantity variance, PP for price variance, ST for date variance, BD for small differences, and others for amounts and percentages on item or order price quantity.
Each key has a lower and upper limit as absolute value or percent. If the invoice difference is within limits the invoice posts, otherwise it is blocked and appears in MRBR.
These keys matter to PP only when production consumes purchased materials or subcontracting, but people searching for tolerance keys often land here. Setting them too loose hides real vendor billing errors.
How to choose limits
Base delivery tolerances on process reality: yields in chemical or machining processes, packaging multiples, and contractual overrun on customer orders. Over-tolerance on a make-to-order item should respect the customer agreement.
Review the limits when scrap rates change. A tolerance set long ago can hide a drift in yield that planners should see.
Record changes with the reason and approver, because tolerance changes are audit-relevant for inventory and variances.
Try it here, free
SAP Invoice Verification Tolerance Calculator
Simulates the price and quantity variance checks behind MIRO invoice blocks so you can test tolerance limits before changing OMR6.
Common pitfalls
- !Changing the material master tolerance does not change existing orders. Their copy was made at creation.
- !Unlimited overdelivery removes the safeguard on goods receipt entirely.
- !OMR6 tolerances are per company code. A new company code starts with none, and every difference blocks.
- !Exact IMG node names vary by release. Use the SPRO search rather than a remembered path.
- !Confirmation tolerances and delivery tolerances do not influence each other.
How an ERP-grounded AI assistant handles this
A grounded assistant can read tolerance settings from the material master, the order and the configuration tables and answer why a given receipt was blocked or allowed, listing which tolerance applied. It can also summarise how often orders exceed tolerance, which is a signal for planners. Use it read-only, and keep configuration changes under normal change control.
Frequently asked questions
Where do I set overdelivery tolerance for a production order?
In the material master, Work Scheduling view, as underdelivery and overdelivery tolerance percentages. The order copies them and you can adjust them on the order.
What does OMR6 do?
OMR6 maintains invoice verification tolerance limits per tolerance key and company code. It decides when a supplier invoice posts and when it is blocked.
What are the main OMR6 tolerance keys?
Common keys include DQ for quantity variance, PP for price variance, ST for date variance and BD for small differences. Your system may have more.
Why is my goods receipt blocked above tolerance?
The received quantity exceeds the order's overdelivery tolerance. Increase the tolerance on the order if justified, or receive in a second order or correct the quantity.
Related
SAP CO11N Confirmation Errors and How to Fix Them
CO11N (time ticket confirmation for production/process orders) throws several distinct errors: deviation from the standard value is too large, goods movement not possible for a component, or the order/operation status does not allow confirmation. Each has a specific cause in order status, routing tolerance settings, or component availability, not a single generic fix.
How-toHow to Create a Control Key in SAP PP (OPJ8)
A control key tells SAP what an operation is allowed to do: be scheduled, costed, confirmed, printed, sent for external processing. Create one with transaction OPJ8 (or SPRO > Production > Basic Data > Routing > Operation Data > Define Control Key), copy a standard key such as PP01, change the indicators, and assign it in the routing or work center.
How-toSAP PP End to End Configuration: Steps, IMG Paths and Process Flow
SAP PP configuration runs in a fixed order: enterprise structure (plant, storage location, planning plant), master data (material, BOM, work center, routing, production version), MRP and planning, production order types and scheduling, confirmation, then costing and settlement. Get the order right because each layer depends on the one before it. The IMG node is Production in SPRO, plus Materials Management for plant and MRP basics.
Error fixSAP MM Errors and Solutions: The Common Ones, by Process Step
Most SAP MM errors fall in five places: purchasing document creation and release (ME21N), goods movements (MIGO), period control, invoice verification (MIRO) and account determination. This page lists the ones that come up most, what causes each, and the first fix, with links to detailed pages for the biggest ones.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
AI for ERPAI Agents for SAP Production Planning, MRP, and Exception Triage
AI agents that triage SAP MD04 exceptions, explain predictive MRP shortages, and draft planned-order actions, grounded on your own SAP data, deployed on-prem.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
Stuck on SAP ERP / S/4HANA?
Talk to engineers who work inside SAP ERP / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP Invoice Verification Tolerance CalculatorSimulates the price and quantity variance checks behind MIRO invoice blocks so you can test tolerance limits before changing OMR6.
- SAP PP Database Tables ReferenceA lookup of the main SAP PP database tables, what each holds and the key fields to join on.
- SAP Three-Way Match and Invoice Tolerance CalculatorEnter PO price, received quantity, invoice quantity and price, and tolerance to see price and quantity variances and whether the invoice would block.
ERP fixes and how-tos
- SAP MIRO: invoice blocked for price variance, and how to release it in MRBRWhy SAP MIRO blocks an invoice for price or quantity variance, how tolerance keys in OMR6 decide it, and how to release or reject it in MRBR safely.
- SAP PP End to End Configuration: Steps, IMG Paths and Process FlowSAP PP end to end configuration in order: organizational structure, master data, MRP, order types, confirmation, costing and settlement, with IMG paths and tcodes.
- How to Create a Control Key in SAP PP (OPJ8)Create and configure a routing control key in SAP PP with OPJ8: what each indicator does, which ones matter for confirmation and costing, and how to test it.