VA13 — Display Sales Inquiry

VA13 opens a sales inquiry document created with VA11 in display mode. The screen structure - header, item overview, item detail tabs, conditions - is identical to VA11 and VA12, which is exactly why it causes confusion: a consultant clicks into a field expecting to correct something and nothing happens, because VA13 has no update logic behind it at all. There is no save, no BAPI call triggered from this transaction, no database write. Every symptom that looks like a VA13 problem is actually a symptom of the underlying document (VBAK/VBAP/VBEP) or of authorization, never of VA13 itself.

VA13 sits between inquiry creation and quotation creation in the pre-sales cycle. A sales rep or SD consultant reaches for it to confirm what a customer actually asked for - quantities, requested delivery dates, validity period, pricing conditions proposed at inquiry stage - before that inquiry is copied forward into a quotation with VA21. It is also the first stop when a customer disputes a quoted price: checking whether the inquiry itself already carried a manual price or discount that later flowed through copy control. For mass review across many inquiries, a list transaction or a Fiori analytical app is used instead; VA13 is strictly single-document lookup.

In SE16N on VBAK, filter VBTYP equal to B (inquiry) and sold-to partner or document number to confirm the inquiry exists and check the validity dates. Cross-check overall status in VBUK by the same document number - a closed or rejected status explains why the document looks complete with nothing left to action. To confirm whether the inquiry was ever converted, query VBFA with VBELV equal to the inquiry number and VBTYP_N equal to the target document type (quotation B or order C); an empty result means no follow-up document was ever created.

VA13 remains a valid sales-inquiry display transaction in S/4HANA. The important technical changes are in the SD data model: VBUK/VBUP status persistence was eliminated, with relevant status fields moved into the corresponding document header/item tables, and sales-document pricing persistence moved from KONV to PRCD_ELEMENTS. Use KONV only as an application structure concept where applicable, not as the S/4HANA pricing-result persistence table.

This is a functional SD issue in nearly every case: wrong document number, misunderstanding of display-only behaviour, or status confusion. Authorization failures route to security or Basis. A good handover states the inquiry number, the exact error or unexpected screen state, the sales organization and document type involved, and whether the issue is data visibility (functional) or access denial (security/Basis).

VA11 and VA12 are the create and change counterparts and should be read alongside VA13 to understand the full inquiry lifecycle. VA21 is the natural next step, since inquiries are typically copied forward into a quotation, and understanding copy control between the two explains most pricing and quantity discrepancies seen when comparing an inquiry in VA13 against its resulting quotation. VBFA-driven document flow tracing, learned through VA13, is the same technique used when investigating order and delivery chains further downstream in the O2C cycle.