OVKK — Pricing Procedure Determination
OVKK is used to determine the SD pricing procedure from sales area, customer pricing procedure and document pricing procedure. It is most useful when a sales document uses the wrong pricing procedure or reports that pricing procedure cannot be determined. Start from the exact business object, organizational scope and status, then prove the result through document flow, logs or master data before applying a corrective action.
This ERPClimb practitioner page covers OVKK — Pricing Procedure Determination. It focuses on the transaction's real operational role, the parameters that matter, the evidence needed to diagnose problems, S/4HANA context, and the mistakes that cause most support rework.
Published 19 Sept 2026· 634 words
Esta página aún no está disponible en español.
Purpose
determine the SD pricing procedure from sales area, customer pricing procedure and document pricing procedure. OVKK is most useful when treated as part of an end-to-end process rather than a shortcut. The object status you see here is usually influenced by upstream master data, configuration, planning or document history, so capture those inputs before changing anything.
When it is used
OVKK is typically used when a sales document uses the wrong pricing procedure or reports that pricing procedure cannot be determined. It is also valuable during project testing because it exposes a repeatable state that can be compared before and after configuration or master-data changes. In production, narrow the population first and distinguish display/analysis from actions that post, approve, replicate or change status.
How to use it in practice
- Capture the sales area and order type from the failing document.
- Read customer pricing-procedure indicator from master data.
- Read document pricing-procedure indicator from the sales document type.
- Check the exact OVKK key combination.
- Maintain only the intended combination and retest pricing.
Key data objects
These are the most useful anchors when working in OVKK. Capture them in screenshots, test evidence and incident handovers so another consultant can reproduce the same result and identify whether the issue is data, configuration, status or integration.
- sales organization — verify the exact value, validity/date context and relationship to the affected process.
- distribution channel — verify the exact value, validity/date context and relationship to the affected process.
- division — verify the exact value, validity/date context and relationship to the affected process.
- customer pricing procedure — verify the exact value, validity/date context and relationship to the affected process.
- document pricing procedure — verify the exact value, validity/date context and relationship to the affected process.
How to prove it in the data
Build an evidence chain rather than relying on one message: identify the source requirement or master record, show the transaction status or worklist entry, then show the resulting document, posting, warehouse object, planning element or replication log. Use the same date and organizational scope throughout. That makes the diagnosis repeatable and separates a true fix from a coincidental retry.
ECC vs S/4HANA
OVKK remains core S/4HANA SD configuration for classic condition-technique pricing. Where a Fiori app or cloud service becomes the strategic user experience, the SAP GUI transaction can still remain valuable for support, migration and deep technical analysis, but it should not be used to justify a legacy design for new work.
Common pitfalls and how to diagnose them
- Changing condition records before confirming the correct procedure was determined. Return to the exact object status and chronology before applying a workaround.
- Creating a broad fallback entry that hides bad master data. Return to the exact object status and chronology before applying a workaround.
- Testing with a customer/order type different from the production scenario. Return to the exact object status and chronology before applying a workaround.
Whose problem this is
Primary ownership is the SD O2C team, with adjacent functional, Basis, Security or integration teams joining when the evidence crosses system boundaries. Escalate with the object/document number, organization, date/time, expected result, actual status and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ovkkERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.