VA01 — Create Sales Order
VA01 is the SAP transaction used to create a sales document — most often a standard sales order. You supply the order type and the sales area (sales organisation, distribution channel, division), then the sold-to party, materials and quantities. Saving writes the header, items and schedule lines and returns the sales document number.
A practitioner reference for VA01, the create-sales-order transaction at the front of the order-to-cash process. It covers where VA01 sits in O2C, what the initial screen is actually asking for, which data objects the save writes, the diagnostic categories behind the errors consultants meet most often, and how VA01 coexists with Fiori sales-order apps on S/4HANA.
Reviewed by an ERPClimb SAP consultant on 13 Sept 2026· 1,245 words
Purpose
VA01 creates a sales document. Despite the everyday name "create sales order", the transaction is generic: the document category behind the order type decides whether you are creating a standard order, a rush order, a free-of-charge delivery, a credit or debit memo request, or a quotation-driven follow-on document. That single fact explains a lot of confusion in projects — two users can both be "in VA01" and be creating documents that behave completely differently downstream, because the order type carries the pricing procedure determination, the item categories, the schedule-line behaviour and the copy control rules.
For a consultant, VA01 is therefore less a screen than a configuration mirror. Almost everything that goes wrong in it is really a statement about master data or customising: the sales area does not exist, the customer is not extended to it, the material is not maintained for that sales organisation, or the condition records behind the pricing procedure are missing. Treating VA01 as the place where configuration becomes visible is the fastest way to debug it.
When it is used in order-to-cash
VA01 sits at the entry point of the order-to-cash value stream. A commercial agreement — a phone order, an EDI message, a quotation, a contract release, or a manual entry by an internal sales representative — becomes a sales document here. Everything downstream inherits from it: delivery creation reads the schedule lines, picking and goods issue reduce the confirmed quantity, billing copies items and conditions, and revenue and receivables land in finance against the resulting billing document.
In practice you will use VA01 manually for one-off and internal-sales scenarios, for testing configuration in development and quality systems, and for reproducing a business incident that arrived as "the order will not save". High-volume order intake normally arrives through interfaces or Fiori apps rather than keystrokes, but the same determination logic runs underneath, which is why reproducing a failure in VA01 is such a reliable diagnostic step: it shows you the message in a context where you can drill into the analysis tools.
How to use it in practice
- On the initial screen, enter the order type and the organisational context: sales organisation, distribution channel and division. In a standard-order flow the order type is OR. Leaving the sales area blank works only where it can be derived unambiguously — supply it explicitly when you are testing configuration.
- Enter the sold-to party. Partner determination fills the ship-to, bill-to and payer from the customer master unless the order type or customer setup overrides it; check these before blaming pricing, because taxes and many condition records depend on the ship-to.
- Enter materials and quantities in the item overview. Item category determination, schedule lines and requirement transfer happen as you enter, not at save — this is why availability and delivery-date proposals appear immediately.
- Review the pricing result at header and item level before saving. A zero net value or an unexpected condition almost always means a missing or date-invalid condition record rather than a defective procedure.
- Save. The document is written and the sales document number is issued. Incompleteness rules may allow a save while still blocking the delivery, so a successful save is not proof that the order is deliverable.
- For an existing document, change and display run through the sibling change and display transactions rather than VA01 — VA01 always starts a new document.
Key data objects
The save distributes the document across a small set of well-known tables. Knowing them turns a vague functional complaint into a query you can actually run.
- VBAK — sales document header: order type, sales area, sold-to, document date, and the header-level status information.
- VBAP — sales document items: material, item category, order quantity, and the item-level pricing reference.
- VBEP — schedule lines: confirmed and requested quantities with their dates, which is where availability and delivery scheduling become visible.
- Pricing results are stored against the document's condition record reference rather than inside the item row itself, which is why pricing analysis in the document is the right tool for "why is this value wrong" questions.
- Partner and status information hang off the header and items too, so an order that saves but never delivers is usually a status or incompleteness question, not a data-loss question.
Common pitfalls and how to diagnose them
Errors in VA01 fall into a handful of diagnostic categories. Classify first, then investigate — chasing individual messages without classifying them is what turns a twenty-minute fix into a two-day one.
- Organisational and master-data category: the sales area combination is not defined, the customer is not extended to it, or the material is not maintained for that sales organisation and distribution channel. Symptom: the order will not even open, or the item is rejected on entry.
- Pricing category: net value is zero, a condition is missing, or a value looks wrong. Investigate through the document's pricing analysis, then the condition records and their validity dates, then the procedure determination — in that order.
- Item and schedule-line category: an unexpected item category, a missing schedule line, or no requirement passed to planning. This is copy control and item-category determination, not a bug in the transaction.
- Availability and date category: confirmed quantity is zero or the confirmed date is far out. This is an availability-check and scheduling question involving the checking rule, the plant, and the transportation and loading times.
- Business-check category: credit limits, blocks, output determination and incompleteness. These often permit the save and then quietly stop the delivery, so always inspect document status after a "successful" order.
- Custom-code category: where the project has added validations at save time, a rejection that no standard configuration explains is usually custom logic. Confirm with the functional owner before changing configuration.
S/4HANA context
VA01 remains available on S/4HANA, and reproducing an issue in it is still a legitimate support technique. Alongside it, the Fiori sales-order applications give internal sales representatives a task-oriented experience: from Manage Sales Orders (F1873) a user can reach the Create Sales Order — VA01 capability directly, so the two are best understood as a single flow with two entry points rather than as old and new.
What this means for a project is a UX and enablement decision more than a technical one. Treat the Fiori apps as the intended day-to-day surface for order intake and monitoring, and treat the classic transaction as the deep-configuration and troubleshooting surface. Avoid telling stakeholders that the transaction is obsolete: the wording matters in adoption workshops, and an inaccurate claim erodes trust in the rest of your advice.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Learn this properly
Lessons and topics
Interview questions on this object
1. You must add a validation in VA01 saving. Which enhancement technique first?
ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.