VA22 — Change Inquiry Transaction

VA22 opens an existing inquiry document for editing. An inquiry is a non-binding presales document (document category A) that captures what a customer is asking about before any order commitment exists. VA22 lets a consultant or sales rep update header data (sold-to, validity period, sales area), line items (material, quantity, plant), pricing conditions, and partner data on that document. The one structural fact that explains most confusion: an inquiry is not a commercial document, so many fields that look editable behave differently than on a quotation or order, particularly pricing redetermination and validity dates. Once a quotation has been created with reference to the inquiry, the copied items in the inquiry are effectively frozen from a business-status perspective, even though the transaction still lets a user open them.

VA22 is reached for whenever an inquiry already exists in the system and something on it needs correcting before it is converted, or while it is still being worked by sales support: wrong validity date, wrong quantity, added or removed line item, updated pricing condition, or a partner correction. It sits early in the O2C chain, before VA41 (create quotation) or VA01 (create order) reference the inquiry. In S/4HANA, the same change can be done through Manage Sales Documents style Fiori apps depending on configuration, but VA22 remains the direct route for consultants troubleshooting or doing mass corrections via variants. It is not used once the inquiry has served its purpose and a quotation or order has been created; at that point the inquiry is historical and changes to it do not propagate forward.

Start in VBAK filtered on the inquiry number and confirm VBTYP equals A and the document type matches the expected inquiry type. Cross-check VBUK-GBSTK (overall processing status) and VBUP-ABSTA (rejection status) at item level in VBUP joined on VBELN and POSNR from VBAP. To confirm whether a follow-up document exists, check VBFA (document flow) filtered on VBELV equal to the inquiry number and look at VBTYP_N for a quotation (B) or order (C); a populated VBFA row is the reason a change attempt is being rejected or a warning is thrown.

The transaction itself is unchanged on S/4HANA; VA22 still runs and updates the same underlying VBAK, VBAP, VBKD structure conceptually, though some fields are exposed through the newer sales document data model. The practical difference is that inquiry handling is increasingly done through Fiori apps for managing sales documents in organizations that have adopted them, but VA22 remains available and is frequently the faster tool for a consultant doing a targeted correction or working from a change history list.

This is a functional SD issue end to end; ABAP involvement is rare unless a user-exit or BAdI in pricing or partner determination is misbehaving. A good handover includes the inquiry number, the exact field that will not change, the VBUK/VBUP status values observed, and the VBFA document flow output showing whether a downstream document already exists.

Read VA21 first to understand what fields are set at creation and therefore what VA22 is actually overwriting. VA23 is useful for a side-by-side display when confirming a change actually saved. VA41 and VA42 matter because most inquiry lock issues trace back to a quotation created with reference to the inquiry. VOV8 is the configuration transaction behind the document type controls, item category determination, and copy control settings that explain why certain fields behave as read-only on VA22.