VA23 — Display Sales Quotation

VA23 displays an existing sales quotation. It renders the identical header, item overview, and item detail screens used by VA21 (create) and VA22 (change), but every input field is greyed out and no save is possible. The structural fact that drives most confusion: because the screen looks exactly like the change transaction, users who cannot type into a field assume their authorization is broken, when in fact VA23 simply has no maintenance authority by design. The quotation itself carries a validity window (valid-from and valid-to dates) and a binding indicator that governs whether pricing quoted to the customer can still be honoured, but VA23 does not enforce or warn on that window; it only shows it.

VA23 is reached for after a quotation has been sent to the customer, whenever someone needs to confirm what was actually quoted: the net price, the validity period, delivery terms, or which items were included. It is the standard first stop when a customer disputes the price on a sales order that referenced a quotation, or when a rep wants to confirm a quote is still binding before creating the order. It is also used to walk the document flow forward, checking whether a follow-on sales order or billing document was created and for what quantity. For read access from a Fiori-first environment the equivalent app is a quotation management or sales document overview tile, but consultants troubleshooting pricing or copy-control behaviour still go to VA23 directly because it exposes the underlying document exactly as VA21/22 produced it.

In SE16 or SE16N, query VBAK filtered on the quotation number or on document type equal to the quotation type, and pull the validity fields alongside the document date. Join to VBAP on VBELN to see item-level status and net price. Cross-check VBFA (document flow) filtered on VBELV equal to the quotation number to see every order, delivery, or billing document generated from it, and compare the quantity fields to confirm whether the quotation is fully or partially referenced.

VA23 works unchanged on S/4HANA; the underlying tables VBAK and VBAP are the same structures used across the SD document family. There is no functional change to how the quotation is displayed. Fiori coverage exists for browsing and managing quotations from a worklist, but that app is a convenience layer on top of the same document; anyone chasing pricing logic, copy control, or document flow still ends up back in the classic transaction or its data.

Functional SD territory. A handover to configuration should include the quotation number, the affected order or billing document number, the copy control combination involved (source and target document types), and whether the discrepancy is a pricing value, a validity date, or a missing follow-on document. Escalate to Basis only if the actual issue is a missing authorization on VA22, confirmed separately from VA23 behaviour.

VA21 and VA22 are the create and change counterparts and are the transactions to open once VA23 confirms what needs correcting. VOV8 is where the copy control and document type settings that explain pricing redetermination between quotation and order live. VK11 is where the condition records sit if the discrepancy turns out to be a changed price rather than a copy control setting.