V/08 — Pricing Procedure Configuration
V/08 is used to configure the sequence of pricing condition types, subtotals, requirements, formulas and account keys in an SD pricing procedure. It is most useful when designing pricing or diagnosing why a condition is mandatory, statistical, excluded or posted differently. 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 V/08 — Pricing Procedure Configuration. 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· 633 words
Esta página aún no está disponible en español.
Purpose
configure the sequence of pricing condition types, subtotals, requirements, formulas and account keys in an SD pricing procedure. V/08 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
V/08 is typically used when designing pricing or diagnosing why a condition is mandatory, statistical, excluded or posted differently. 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
- Identify the procedure actually determined for the document.
- Review condition sequence and mandatory/statistical flags.
- Check requirements and formulas before moving steps.
- Validate account keys for billing-to-FI impact.
- Regression-test order, delivery-related pricing and billing scenarios.
Key data objects
These are the most useful anchors when working in V/08. 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.
- pricing procedure — verify the exact value, validity/date context and relationship to the affected process.
- step/counter — verify the exact value, validity/date context and relationship to the affected process.
- condition type — verify the exact value, validity/date context and relationship to the affected process.
- requirement/formula — verify the exact value, validity/date context and relationship to the affected process.
- subtotal/account key — 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
Pricing procedures remain fundamental in S/4HANA SD, with the same need to test commercial and accounting consequences. 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
- Editing the wrong pricing procedure because determination was not checked. Return to the exact object status and chronology before applying a workaround.
- Moving condition steps and breaking subtotals/formulas. Return to the exact object status and chronology before applying a workaround.
- Fixing a missing condition in V/08 when the real problem is the condition record/access. 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/v-08ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.