VA11 — Create Customer Inquiry

VA11 creates a sales document of type IN, the customer inquiry. It captures what a customer is asking about - materials, quantities, indicative pricing - before any commercial commitment exists. The structural fact that causes most confusion is that an inquiry is not delivery relevant and not billing relevant by design. Nothing downstream fires automatically when it is saved; it just sits in the document flow as a source that a quotation (VA21) or order (VA01) can reference and copy from via copy control. Many implementations never use VA11 at all and start the sales cycle directly at the quotation or order, so when it does appear it is usually because someone wants a formal presales pipeline record, or because a test is validating copy control and pricing determination for the earliest document type in the chain.

In a full presales-to-cash process, the inquiry sits before the quotation and the sales order. It is used where a company wants a documented, reportable trail of customer requests that have not yet become binding, typically for high-value or configurable products where the customer wants indicative pricing first. A consultant reaches for VA11 mainly during testing: verifying that item categories, pricing procedures, and copy control are correctly determined for the earliest possible entry point in the sales chain, or reproducing a defect that only shows up when a quotation or order is created with reference to an inquiry. Outside of testing, day-to-day users rarely touch it unless the business explicitly runs a presales tracking process; most O2C flows in production start at the quotation or order transaction instead.

In SE16, open VBAK and filter on VBTYP = 'A' and AUART equal to the inquiry document type, plus VKORG to scope to the relevant sales organization. Take the resulting VBELN values and join against VBAP to confirm item categories and quantities, and against VBKD to check pricing date and terms. If a follow-up quotation is expected but missing, check VBFA (document flow) filtered on VBELV equal to the inquiry number and VBTYP_N equal to the quotation type to see whether the reference link was actually created.

VA11 continues to work unchanged on S/4HANA; the underlying document type IN and its role as a non-billing, non-delivery presales document have not been restructured. There is no dedicated Fiori app that replaces the inquiry transaction directly; SAP's newer sales apps focus on quotations and orders, so presales inquiry handling in S/4HANA implementations that still use it remains largely SAP GUI based.

This is functional SD territory: document type configuration, item category determination, pricing procedure assignment and copy control all live in SD customizing owned by the SD consultant. ABAP involvement is limited to custom pricing routines or user exits if the business has extended standard determination logic. A good handover includes the document number, the sales area used, and whether the failure is on save, on pricing, or on the follow-up document copy.

Read VA21 next since it is the natural follow-up document that most inquiries feed into through copy control. VOV8 explains the document type configuration that governs pricing procedure and incompleteness behavior for IN. VK11 and VK13 are useful for confirming whether a pricing condition record actually exists behind a pricing failure. VD01 or the customer master sales view is the first place to check when the sales area error appears on entry.