How to Create Inquiry in SAP: VA11
โก Smart Summary
Inquiry creation in SAP, using transaction VA11, records a prospective customer’s request for product and price information. This resource explains what an inquiry is, how it differs from a quotation, and the steps to create and manage one.
What Is an Inquiry in SAP SD?
An inquiry is an internal pre-sales document in SAP Sales and Distribution that records a prospective customer’s request for information about a product. It is not a legal document; instead, it captures interest so the request can be circulated inside the company and answered efficiently. Because it sits at the very start of the sales cycle, an inquiry helps a business respond quickly without committing to anything.
The information captured is mainly the material and the quantity the customer is interested in. Further details can be added, but they are optional, which keeps the document light and fast to create. The main advantage of raising an inquiry is that it reduces the business overhead needed to prepare a reply to the customer, and it creates a record that can later be copied into a quotation or a sales order. The transaction code used to create an inquiry is VA11.
Inquiry vs Quotation in SAP
An inquiry and a quotation are both pre-sales documents, and they often appear one after the other. However, they play different roles, so it helps to know how they compare before you create one.
| Basis of comparison | Inquiry (VA11) | Quotation (VA21) |
|---|---|---|
| Purpose | Requests product and price information | Offers to supply at agreed terms |
| Legally binding | No | Yes, within its validity period |
| Typical trigger | Customer is exploring options | Customer wants a firm offer |
| Data captured | Material and quantity | Materials, prices, validity, and conditions |
| Position in the cycle | First pre-sales step | Follows an inquiry, precedes the order |
In short, an inquiry gathers interest, while a quotation turns that interest into a firm, binding offer. Many businesses create the inquiry first and then copy it into a quotation to save time and keep the data consistent. Both documents belong to the pre-sales phase, so neither one reserves stock or posts to accounting; they simply prepare the ground for a confirmed sales order.
Process to Create Inquiry in SAP
Follow these steps to create an inquiry in transaction VA11.
Step 1) Open VA11 and enter the header data.
- Enter T-code VA11 in the command bar field.
- Select the Inquiry Type from the help. In the screenshot, “IN” is selected for Inquiry.
- Enter the Sales Organization, Distribution Channel, Division, Sales Office, and Sales Group.
- Select the Sales icon.
Step 2) Enter the customer and item details.
- Enter the Sold-To Party and Ship-To Party (this is a partner function).
- Enter the Material code and Quantity.
- Click on the Save
button.
Step 3) A message “Inquiry 10000015 has been saved” is displayed.
Managing Inquiry Documents: VA11, VA12, and VA13
SAP uses a small family of transaction codes to manage an inquiry through its life. Each one opens the inquiry in a different mode, so changes stay controlled and traceable.
- VA11 – Create Inquiry: Raises a new inquiry for a customer and sales area.
- VA12 – Change Inquiry: Updates an existing inquiry, for example to adjust the material or quantity.
- VA13 – Display Inquiry: Opens the inquiry in read-only mode to review it without making changes.
For a list of inquiries across customers, you can use the list report VA15. As a habit, display an inquiry with VA13 before changing it with VA12, so that you confirm the current values first. This keeps pre-sales data accurate as it moves toward a quotation or a sales order. Because all three transactions act on the same inquiry number, any change made in VA12 is immediately visible in VA13, which makes review and audit straightforward.



