For the data behind these transactions, see our complete SAP SD tables list (VBAK, VBAP, LIKP, VBRK and friends). And if you also work on the procurement side, our SAP MM TCodes list follows the same format.
Sales Document TCodes
Sales documents — inquiries, quotations, orders, contracts — are the starting point of order-to-cash.
Sales Orders
| TCode | Description |
|---|---|
| VA01 | Create sales order |
| VA02 | Change sales order |
| VA03 | Display sales order |
| VA05 | List of sales orders (reporting) |
Inquiries and Quotations
| TCode | Description |
|---|---|
| VA11 | Create inquiry |
| VA12 | Change inquiry |
| VA13 | Display inquiry |
| VA21 | Create quotation |
| VA22 | Change quotation |
| VA23 | Display quotation |
Contracts
| TCode | Description |
|---|---|
| VA41 | Create contract (quantity or value contract) |
| VA42 | Change contract |
| VA43 | Display contract |
Pattern to remember: across SD, 1 = create, 2 = change, 3 = display (VA01/VA02/VA03, VA21/VA22/VA23, VL01N/VL02N/VL03N, VF01/VF02/VF03). Learn this once and you can guess most SD transaction codes.
Delivery and Shipping TCodes
| TCode | Description |
|---|---|
| VL01N | Create outbound delivery |
| VL02N | Change outbound delivery |
| VL03N | Display outbound delivery |
| VL10A | Delivery due list for sales orders (collective processing) |
| VL10B | Delivery due list for purchase orders |
| VL06O | Outbound delivery monitor (reporting) |
| VT01N | Create shipment |
| VT02N | Change shipment |
| VT03N | Display shipment |
VL10A is a daily workhorse in distribution centers — it lists every sales order item due for delivery so warehouse teams can create deliveries in bulk instead of one by one.
Billing TCodes
| TCode | Description |
|---|---|
| VF01 | Create billing document |
| VF02 | Change billing document |
| VF03 | Display billing document |
| VF04 | Billing due list (deliveries and orders due for billing) |
| VF05 | List of billing documents (reporting) |
| VF11 | Cancel billing document |
| VF21 | Create invoice list |
| VF22 | Change invoice list |
| VF23 | Display invoice list |
VF04 mirrors VL10A on the billing side — it shows everything ready to invoice so billing runs can be processed collectively.
Master Data TCodes
Customer Master
| TCode | Description |
|---|---|
| XD01 | Create customer (central) |
| XD02 | Change customer (central) |
| XD03 | Display customer (central) |
| VD01 | Create customer (sales area) |
| VD02 | Change customer (sales area) |
| VD03 | Display customer (sales area) |
| VAP1 | Create contact person |
| BP | Maintain Business Partner (S/4HANA — replaces XD01/VD01) |
Material Master (Sales Views)
| TCode | Description |
|---|---|
| MM01 | Create material master |
| MM02 | Change material master |
| MM03 | Display material master |
Customer-Material Info Records
| TCode | Description |
|---|---|
| VD51 | Create customer-material info record |
| VD52 | Change customer-material info record |
| VD53 | Display customer-material info record |
S/4HANA note: customer master maintenance moved to the Business Partner transaction (BP) with Customer-Vendor Integration. XD01/VD01 still appear in interviews and ECC systems, but new implementations use BP.
Pricing and Condition TCodes
| TCode | Description |
|---|---|
| VK11 | Create condition record (prices, discounts, surcharges) |
| VK12 | Change condition record |
| VK13 | Display condition record |
| VK14 | Create condition records with reference |
| V/LD | List prices per customer/material (reporting) |
VK11/VK12/VK13 are the pricing master data transactions — the equivalent of MM01 for prices. Every discount or surcharge in a sales order traces back to a condition record maintained here.
Credit Management TCodes
| TCode | Description |
|---|---|
| FD32 | Change customer credit limit (credit control area) |
| FD33 | Display customer credit limit |
| VKM1 | Blocked SD documents (credit block overview) |
| VKM2 | Release blocked SD documents |
When a sales order exceeds the customer’s credit limit, it lands in VKM1 for review — credit controllers release or reject it in VKM2.
General and Reporting TCodes
| TCode | Description |
|---|---|
| SE16N | Display table contents (e.g., VBAK, VBAP, VBFA) |
| SE11 | ABAP Dictionary — view table structures |
| VA05 | Sales order list |
| SDO1 | Sales document flow reporting |
Order-to-Cash Walkthrough: TCodes in Sequence
Here is how the TCodes above fit into one end-to-end sales cycle:
- VA11/VA21 — the customer sends an inquiry; sales responds with a quotation.
- VA01 — the quotation is converted into a sales order; pricing pulls condition records from VK11.
- VA02 — availability check runs; schedule lines confirm delivery dates.
- VL10A — the order appears on the delivery due list; VL01N creates the delivery.
- VL02N — picking quantities are entered and Post Goods Issue is posted; inventory drops.
- VF04 — the delivery appears on the billing due list; VF01 creates the invoice.
- VF02 — the billing document is released to accounting, posting revenue in FI.
- VA03 — document flow shows the complete chain: inquiry → quotation → order → delivery → invoice.
Walk through this chain in an interview and you show process mastery, not just memorized codes.
Tips for Cracking SD TCode Interviews
Interviewers test scenarios, not lists. Prepare these:
- “A customer calls asking where their order is.” — VA03 document flow (or VBFA in SE16N) shows whether it is picked, goods-issued, or billed — and the delivery/invoice numbers.
- “An invoice has the wrong quantity.” — Check VF03, trace back via document flow to the delivery (VL03N) and order (VA03); cancel with VF11 and rebill if needed.
- “A new discount needs to apply from next month.” — VK11 with a future validity date; existing orders keep old pricing unless repriced.
Always link the TCode to the scenario and the underlying tables (VBAK, LIKP, VBRK, VBFA) — that is what interviewers reward.
Frequently Asked Questions
Q1. What are the most important SAP SD TCodes to memorize?
VA01/VA02/VA03 (sales orders), VL01N/VL02N/VL03N (deliveries), VF01/VF02/VF03 (billing), VK11/VK12/VK13 (pricing), and SE16N (table display). These ten cover most daily SD work.
Q2. What is the TCode to create a sales order in SAP?
VA01. VA02 changes it, VA03 displays it, and VA05 lists sales orders. The 1/2/3 create/change/display pattern holds across nearly all SD transactions.
Q3. Which TCode is used for billing in SAP SD?
VF01 creates the billing document (invoice), VF02 changes it, VF03 displays it, and VF11 cancels it. VF04 shows the billing due list of everything ready to invoice.
Q4. What is the TCode for creating a credit memo in SD?
G2-related billing documents are created with VF01 using the appropriate billing type (G2 for credit memo, L2 for debit memo). Credit management blocks are reviewed in VKM1 and released in VKM2.
Q5. What is the difference between VL01N and VL10A?
VL01N creates a single outbound delivery with reference to one sales order. VL10A is the delivery due list — it shows all order items due for delivery so you can create many deliveries collectively.
Q6. Which TCode shows blocked orders for credit check?
VKM1 lists SD documents blocked by credit management; VKM2 releases them. Credit limits themselves are maintained in FD32 per customer per credit control area.
Conclusion
Master these SAP SD TCodes and the order-to-cash process becomes second nature: VA01 to take the order, VL01N to ship it, VF01 to bill it — with VK11 for pricing, VD51 for customer-specific data, and SE16N to inspect the tables underneath (see our SAP SD tables guide for those). In interviews, interviewers love the 1/2/3 pattern question — now you know the answer. Keep this list handy during your next project and the codes will become muscle memory within weeks.