VA22 — Change Sales Quotation
VA22 changes an existing sales quotation in SAP Sales and Distribution. SAP's current S/4HANA documentation names the app Change Sales Quotations - VA22. Use it to edit permitted quotation header and item data, pricing, partners, quantities, and validity information before or during quotation processing; VA12, not VA22, is the transaction for changing a sales inquiry.
VA22 is the change transaction for sales inquiries, the presales document that records a customer request for pricing or availability information without commitment. This page covers what actually gets updated on save, why changes get silently rejected once a follow-up quotation exists, and how to prove in the tables whether an inquiry is still open for editing.
Published 20 Sept 2026· 587 words
Esta página ainda não está disponível em português.
Purpose
VA22 opens an existing sales quotation for change. A quotation is a binding or commercially relevant presales offer according to the configured quotation type, validity, pricing, and follow-on rules. VA22 is the change counterpart to VA21 Create Sales Quotations and VA23 Display Sales Quotations. It is not the inquiry change transaction; inquiries are changed with VA12.
When it is used
Use VA22 when a quotation already exists and permitted commercial data must be updated before a follow-on sales order or before the quotation expires. Typical changes include validity dates, quantities, materials, partners, texts, pricing conditions, rejection reasons, and other fields allowed by document status and configuration.
How to use it in practice
- Enter the quotation number or navigate from a quotation worklist/object page.
- Review header status, validity, sold-to/ship-to partners, and document flow before changing values.
- Change only the required header or item fields and review pricing analysis when commercial values change.
- Check whether follow-on sales orders already reference the quotation items; referenced quantities/status can affect what changes are sensible or allowed.
- Save and verify the quotation again in VA23 or the relevant quotation app, then confirm any follow-on document is based on the intended version.
Key data objects
Sales quotations use the standard sales-document data model.
- VBAK — quotation header including sales area, sold-to party, validity, and header status fields.
- VBAP — quotation item data including material, quantity, item category, rejection reason, and item status fields.
- VBKD — business data such as payment terms, Incoterms, and pricing date.
- VBEP — schedule-line data where relevant to the quotation process.
- VBFA — document flow to follow-on sales orders or other documents.
- PRCD_ELEMENTS — S/4HANA persistence for document pricing elements; ECC used KONV persistence.
How to prove it in the data
Open the quotation in VA23 and confirm header/item values, pricing, validity, status, and document flow. For technical proof use VBAK/VBAP/VBKD/VBEP and VBFA with the same quotation/item keys. In S/4HANA, read status from the relevant document header/item structures rather than treating eliminated VBUK/VBUP tables as persistence, and use PRCD_ELEMENTS for pricing-result persistence.
ECC vs S/4HANA
SAP's current S/4HANA 2025 documentation explicitly provides Change Sales Quotations - VA22 and navigation from quotation management apps. S/4HANA also simplified SD status persistence and pricing persistence, but the VA21/VA22/VA23 quotation lifecycle remains recognizable.
Common pitfalls and how to diagnose them
- Confusing VA22 with inquiry change — VA12 changes inquiries; VA22 changes quotations.
- Changing a quotation after a follow-on order exists and expecting the copied order to update automatically.
- Repricing without understanding the pricing type and condition-record validity.
- Extending quotation validity without checking business approval and downstream commitments.
- Diagnosing a field as authorization-protected when document status or configuration actually makes it non-changeable.
Whose problem this is
Primary ownership is SD Sales/Quotation Management. Pricing owners join for condition issues, credit or workflow teams where approvals apply, and ABAP only when custom copy-control, pricing routines, exits, or BAdIs are proven to affect the quotation.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/va22ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.