V/06 — Pricing Condition Type Configuration
V/06 is used to configure SD pricing condition types such as calculation type, plus/minus sign, manual-entry and control behavior. It is most useful when implementing or troubleshooting how a price, discount, surcharge, freight or tax condition behaves inside pricing. 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/06 — Pricing Condition Type 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· 641 words
Esta página ainda não está disponível em português.
Purpose
configure SD pricing condition types such as calculation type, plus/minus sign, manual-entry and control behavior. V/06 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/06 is typically used when implementing or troubleshooting how a price, discount, surcharge, freight or tax condition behaves inside pricing. 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
- Start from the business meaning of the condition rather than copying a similar type blindly.
- Review calculation and control flags together.
- Check the assigned access sequence and procedure placement.
- Transport configuration through the landscape.
- Test pricing analysis on representative sales and billing documents.
Key data objects
These are the most useful anchors when working in V/06. 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.
- condition type — verify the exact value, validity/date context and relationship to the affected process.
- condition class/category — verify the exact value, validity/date context and relationship to the affected process.
- calculation type — verify the exact value, validity/date context and relationship to the affected process.
- plus/minus and manual-entry controls — verify the exact value, validity/date context and relationship to the affected process.
- access sequence assignment — 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
Classic pricing configuration still underpins many S/4HANA SD processes, even when condition maintenance is exposed through Fiori apps. 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 a standard condition type to fix a local requirement. Return to the exact object status and chronology before applying a workaround.
- Copying a condition without understanding statistical/accrual behavior. Return to the exact object status and chronology before applying a workaround.
- Testing only order pricing and not billing repricing/copy behavior. 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-06ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.