SAP SD Transaction Codes Reference
SD consultants and key users keep a mental map of transaction codes. This searchable list groups the main ones by process area, from pre-sales to billing and configuration, so you can find the right t-code quickly.
| T-code | Area | Description |
|---|---|---|
VA01 | Sales order | Create sales order |
VA02 | Sales order | Change sales order |
VA03 | Sales order | Display sales order |
VA05 | Sales order | List of sales orders |
VA11 | Pre-sales | Create inquiry |
VA21 | Pre-sales | Create quotation |
VA31 | Sales order | Create scheduling agreement |
VA41 | Sales order | Create contract |
VKM1 | Credit and blocks | Blocked SD documents |
VL01N | Delivery | Create outbound delivery with reference to sales order |
VL02N | Delivery | Change outbound delivery, post goods issue |
VL03N | Delivery | Display outbound delivery |
VL04 | Delivery | Process delivery due list collectively |
VL06O | Delivery | Outbound delivery monitor |
VL09 | Delivery | Cancel goods issue for delivery |
VL10 | Delivery | Create deliveries from sales orders due |
VT01N | Shipment | Create shipment |
VF01 | Billing | Create billing document |
VF02 | Billing | Change billing document |
VF03 | Billing | Display billing document |
VF04 | Billing | Process billing due list |
VF11 | Billing | Cancel billing document |
VFX3 | Billing | Billing documents blocked for accounting release |
VK11 | Pricing | Create condition records |
VK12 | Pricing | Change condition records |
VK13 | Pricing | Display condition records |
VBO1 | Rebates | Create rebate agreement |
VBO2 | Rebates | Change rebate agreement |
VBO3 | Rebates | Display rebate agreement |
XD01 | Customer master | Create customer (centrally, classic) |
VD01 | Customer master | Create customer (sales view, classic) |
BP | Customer master | Maintain business partner (S/4HANA) |
VOFM | Configuration | Maintain requirements and routines |
VOPA | Configuration | Maintain partner determination |
VOV8 | Configuration | Define sales document types |
VOV4 | Configuration | Assign item categories |
VOV6 | Configuration | Define schedule line categories |
VOFA | Configuration | Define billing types |
V/08 | Configuration | Maintain pricing procedures |
OVKK | Configuration | Pricing procedure determination |
VTAA | Copy control | Copy control, sales document to sales document |
VTLA | Copy control | Copy control, sales document to delivery |
VTFA | Copy control | Copy control, sales document to billing document |
VTFL | Copy control | Copy control, delivery to billing document |
NACE | Output | Output control, application and condition types |
Codes are standard SAP transactions. Availability depends on release and fiori or GUI setup. Some classic transactions such as XD01 are replaced by BP in S/4HANA.
Ask your SAP data in plain language
Optional: see how Netray adds read-only natural language lookups on top of your ERP.
Optional. The tool and every export work without this. No spam.
How to use the list
Type part of a code or a description in the search box, for example billing, rebate or copy. The table filters as you type. Export to Excel or PDF for onboarding packs, or paste a column into a cheat sheet for your team. Enter any code in the command field of SAP GUI, or prefix with /n to open it from another transaction.
How the codes are organised
Daily work in SD follows the order to cash chain: inquiry and quotation, sales order, delivery, goods issue, billing. Master data and pricing sit alongside it with customer, material and condition records. Configuration t-codes start with V, O or V/ prefixes and are used by consultants in customising rather than by business users.
- VA transactions: sales documents
- VL and VT: delivery and shipment
- VF: billing
- VK: pricing conditions
- VBO: rebates
Reading the list in S/4HANA
Many classic transactions still work in S/4HANA, but several have Fiori apps that replace them, and some master data transactions such as XD01 redirect to the business partner. List reports such as VA05 have newer equivalents. The code is useful for troubleshooting and for authorisations, because roles are still built around transaction and authorisation objects.
Common mistakes
Users often change documents in the wrong transaction, for example editing a billing document without understanding its accounting effect, or reversing goods issue when a delivery should be cancelled. Another is giving configuration transactions in production to business users. Keep VOFM, VOV8 and V/08 for transports from development only.
Frequently Asked Questions
What are the most used SAP SD transaction codes?
VA01, VA02 and VA03 for sales orders, VL01N and VL02N for deliveries, VF01 and VF04 for billing, VK11 for condition records and XD01 or BP for customers. These cover most daily work.
How do I find the t-code for a screen?
In SAP GUI, open System, Status, and read the transaction field. In Fiori, the app details show the related transaction or semantic object. You can also search in table TSTC or via SE93.
Are these codes different in S/4HANA?
Most still exist. Some are replaced by Fiori apps or redirected, such as customer master transactions going to the business partner. Always verify in your own system and release.
What does the /n prefix do?
Typing /n before a code in the command field closes the current transaction and opens the new one in the same session. Typing /o opens the new transaction in a new session window.
If users struggle to find the right screen or report in SAP, Netray can add a natural language layer over your ERP data, read-only, for lookups and status questions.
Related Tools
SAP SD Copy Control Design Worksheet
Plan every copy control path in your order to cash flow: source document, target document, item category, copy requirements and pricing type.
SAPSAP SD Condition Record Load Worksheet
Prepare price and discount condition records row by row, check the per-unit value and export to Excel for LSMW, migration cockpit or manual VK11 entry.
SAPSAP SD Rebate Agreement Request Form Template
A request form for creating a volume rebate agreement in SAP SD: who qualifies, what is measured, scale, accrual treatment and approval.
SAPSAP SD Enhancement Functional Specification Template
A fill-in functional spec for SD enhancements: requirement, trigger point, logic rules, data touched, test cases and sign-off. Exports to PDF or Word.
SAPSAP SD Partner Determination Design Template
Document your partner functions, partner determination procedures and sources per document level, then export a design page for review.