If you’ve spent any time working in SAP Sales and Distribution, you already know how much of your day runs through transaction codes. You type one in, hit Enter, and you’re exactly where you need to be — no menus, no clicking around, no waiting. That’s the whole point of SAP SD T-Codes: they get you where you’re going fast.
This is a comprehensive reference for the SAP SD T-Codes you’ll actually use — and it’s the most complete SAP SD T-Codes guide — organized by function, with context around what each section does and why it matters. Whether you’re a functional consultant, a developer supporting the SD module, or someone who just got handed an SAP project and is figuring things out, this list is built for you.
The SAP Sales and Distribution module handles the entire order-to-cash cycle. Every stage of that process has SAP SD T-Codes supporting it — from the moment a customer inquiry comes in to the point where the invoice gets paid. That’s a wide scope, and the sap transaction codes that support it cover a lot of ground: master data, sales orders, deliveries, billing, configuration, EDI, workflow, and more. This guide covers all of it — every set of SAP SD T-Codes from area menus to obsolete transactions.
Area Menus
Before getting into individual SAP SD T-Codes, it helps to understand area menus. Area menus are one of the underappreciated parts of the SAP SD T-Codes ecosystem. Also known as SAP Easy Access, area menus give users a structured navigation path through the SAP system — organized by function rather than requiring you to already know the exact sap t code you’re looking for. They are great for rookie users or anyone who needs an overview of what’s available in a given module.
Transaction code SE43 is the one you’ll use to cook and maintain custom area menus. If your organization has built a custom navigation structure for SD users, that’s where it lives.
The core area menu sap t codes for Sales and Distribution are:
Transaction Code | Description | Application Component | Module |
VA00 | Initial Sales Menu | SD-SLS | Sales |
VC00 | Sales Support | SD-CAS | Sales Support |
VF00 | Billing | SD-BIL | Billing |
VI00 | Shipment Costs | SD-TBA | Transportation |
VL00 | Shipping | SD-SHP | Shipping |
VS00 | Sales Master Data | SD-MD | Master Data |
VT00 | Transportation | SD-TBA | Transportation |
VX00 | Foreign Trade / Customs | SD-FTT | Foreign Trade |
These aren’t codes you’ll use day in and day out, but knowing them matters when you’re orienting a new team member or setting up role-based navigation for an SD user group.
Master Data
Master data is the base everything else in SD sits on. If you get it wrong, problems ripple downstream into orders, deliveries, and billing. The sap customer master tcode and related codes here are some of the most frequently used in the entire module. These SAP SD T-Codes are the ones every SD consultant learns first.
Customer Master
The Customer Master holds everything SAP needs to know about a customer — contact details, address, payment terms, sales area assignments, and more. The sap customer tcode most people reach for first is XD01 to create a new customer centrally. The FD-series codes handle the accounting-side view of the same customer record.
If you’re looking for the sap customer list tcode, FD09 lets you confirm a customer list from the accounting side, while XD99 handles mass maintenance when you need to update multiple customer records at once. For anyone asking what is the tcode for viewing report screen of customer, FD10N is the customer balance display and one of the most-used reporting transactions in this group.
Transaction Code | Description | Module | Application Component |
XD01 | Create Customer (Centrally) | Sales & Distribution | SD-MD |
XD02 | Change Customer (Centrally) | SD | SD-MD |
XD03 | Display Customer (Centrally) | SD | SD-MD |
XD04 | Customer Changes (Centrally) | SD | SD-MD |
XD05 | Block Customer (Centrally) | SD | SD-MD |
XD06 | Mark Customer for Deletion (Centrally) | SD | SD-MD |
XD07 | Change Customer Account Group | SD | SD-MD |
XD99 | Customer Master Mass Maintenance | SD | SD-MD |
XDN1 | Maintain Number Ranges (Customer) | SD | SD-MD |
FD01 | Create Customer (Accounting) | Financial Accounting | FI-AR |
FD02 | Change of Customer (Accounting) | FI | FI-AR |
FD02CORE | Maintain Customer | FI | FI-AR |
FD03 | Display Customer (Accounting) | FI | FI-AR |
FD04 | Customer Changes (Accounting) | FI | FI-AR |
FD05 | Block Customer (Accounting) | FI | FI-AR |
FD06 | Mark Customer for Deletion (Accounting) | FI | FI-AR |
FD08 | Confirm Customer Individually (Accounting) | FI | FI-AR |
FD09 | Confirm Customer List (Accounting) | FI | FI-AR |
FD10 | Customer Account Balance | FI | FI-AR |
FD10N | Customer Balance Display | FI | FI-AR |
FD10NA | Customer Balance Display with Worklist | FI | FI-AR |
FD10NET | Customer Balance Display (Net) | FI | FI-AR |
FD11 | Customer Account Analysis | FI | FI-AR |
FD15 | Transfer Customer Changes: Send | FI | FI-AR |
FD16 | Transfer Customer Changes: Receive | FI | FI-AR |
FD24 | Credit Limit Changes | FI | FI-AR |
FD32 | Change Customer Credit Management | FI | FI-AR |
FD33 | Display Customer Credit Management | FI | FI-AR |
FD37 | Credit Management Mass Change | FI | FI-AR |
Vendor Master
The vendor master in SD comes up most often in procurement-related SD scenarios and intercompany processes. The XK-series codes mirror the XD-series for customers.
Transaction Code | Description | Module | Application Component |
XK01 | Create Vendor (Centrally) | Material Management | MM-MD |
XK02 | Change Vendor (Centrally) | MM | MM-MD |
XK03 | Display Vendor (Centrally) | MM | MM-MD |
XK04 | Vendor Changes (Centrally) | MM | MM-MD |
XK05 | Block Vendor (Centrally) | MM | MM-MD |
XK06 | Mark Vendor for Deletion (Centrally) | MM | MM-MD |
XK07 | Change Vendor Account Group | MM | MM-MD |
XEIP | Number range maintenance: EXPIMP | MM | MM-MD |
Material Master
The material master is what connects SD to the broader logistics world. Every product your organization sells needs a material master record before it can appear on a sales order.
Transaction Code | Description | Module | Application Component |
MM01 | Create Material | Material Management | MM-MD |
MM02 | Change Material | MM | MM-MD |
MM03 | Display Material | MM | MM-MD |
MM04 | Display Material Change Documents | MM | MM-MD |
MM06 | Flag Material for Deletion | MM | MM-MD |
MM17 | Mass Maintenance: Materials (Industry) | MM | MM-MD |
MM50 | Extend Material Views | MM | MM-MD |
Pricing Conditions
Pricing conditions define how prices, discounts, surcharges, and taxes are calculated. The VK-series codes are where you create and manage condition records — the actual pricing data that drives what customers are charged.
Transaction Code | Description | Module | Application Component |
VK11 | Create Condition Record Using Condition Type | AP | AP-PRC-PR |
VK12 | Change Condition Record Using Condition Type | AP | AP-PRC-PR |
VK13 | Display Condition Record Using Condition Type | AP | AP-PRC-PR |
VK31 | Create Condition Records | AP | AP-PRC-PR |
VK32 | Change Condition Records – Fast Entry | AP | AP-PRC-PR |
VK34 | Create Condition Records with Template | AP | AP-PRC-PR |
Customer-Material Info
These codes manage the link between a specific customer and a specific material — including customer-specific material numbers, descriptions, and delivery tolerances.
Transaction Code | Description | Module | Application Component |
VD51 | Maintain Customer-Material Info | SD & CRM | CRM-BTX-BF-IF |
VD52 | Maintain Customer-Material Info with Selection | SD & CRM | CRM-BTX-BF-IF |
VD53 | Display Customer-Material Info | SD & CRM | CRM-BTX-BF-IF |
VD59 | List of Customer-Material Info | SD & CRM | CRM-BTX-BF-IF |
Material Substitution
Transaction Code | Description | Module | Application Component |
VB11 | Create Material Substitution | AP | AP-PRC-PR |
VB12 | Change Material Substitution | AP | AP-PRC-PR |
VB13 | Display Material Substitution | AP | AP-PRC-PR |
Sales Documents
This is where most of the daily action happens in SAP SD. The sap sd transaction codes in this section cover the full sales document lifecycle. If there’s one group of SAP SD T-Codes worth memorizing, it’s this one — from the first customer inquiry through quotations, sales orders, contracts, and item proposals. VA01 is the sales order tcode in sap that everyone learns first coz it’s the onset of the entire order-to-cash process.
Inquiry
An inquiry is when a customer asks about availability or pricing before committing to an order. It marks the earliest stage of the sales process.
Transaction Code | Description | Module | Application Component |
VA11 | Create Inquiry | CRM | CRM-BTX-BF-IF |
VA12 | Change Inquiry | CRM | CRM-BTX-BF-IF |
VA13 | Display Inquiry | CRM | CRM-BTX-BF-IF |
VA14L | Sales Documents Blocked for Delivery | SD | SD-SLS |
VA15 | Inquiries List | SD | SD-SLS |
Quotation
A quotation takes the inquiry a step further — it’s a formal offer to a customer with binding prices and conditions.
Transaction Code | Description | Module | Application Component |
VA21 | Create Quotation | CRM | CRM-BTX-BF-IF |
VA22 | Change Quotation | CRM | CRM-BTX-BF-IF |
VA23 | Display Quotation | CRM | CRM-BTX-BF-IF |
VA25 | Quotations List | SD | SD-SLS |
VA26 | Collective Processing for Quotations | CRM | CRM |
Sales Order
The sales order t code in SAP is the centerpiece of the SD module. VA01 creates a new sales order. VA02 is for making changes. VA03 is display-only. These three are among the most-used sap transaction codes across any SD implementation. The sales order also integrates with availability checks (ATP), credit management, pricing, and output determination — making it one of the most complex documents in the entire SAP system.
The tcode for sales order reporting is VA05 for the standard list, though note that VA05N is marked obsolete in S/4HANA environments.
Transaction Code | Description | Module | Application Component |
VA01 | Create Sales Order | CRM | CRM-BTX-BF-IF |
VA02 | Change Sales Order | CRM | CRM-BTX-BF-IF |
VA03 | Display Sales Order | CRM | CRM-BTX-BF-IF |
VA05 | List of Sales Orders | SD | SD-SLS |
VA05N | List of Sales Orders (Obsolete with S/4HANA) | SD | SD-SLS |
VA06 | Sales Order Monitor | SD | SD-SLS |
VA07 | Compare Sales – Purchasing (Order) | CRM | CRM-BTX-BF-IF |
VA08 | Compare Sales – Purchasing (Org.Dt.) | CRM | CRM-BTX-BF-IF |
V.02 | List of Incomplete Sales Orders | SD | SD-SLS |
SDD1 | Duplicate Sales Documents in Period | SD | SD-SLS |
V.15 | Display Backorders | SD | SD-SLS |
V.26 | Sales Order Selection by Object Status | SD | SD-SLS |
VA71 | Output from Sales Orders | SD | SD-BF-OC |
Scheduling Agreement
Transaction Code | Description | Module | Application Component |
VA32 | Scheduling Agreement Change | CRM | CRM-BTX-BF-IF |
Contract
Contracts are long-term agreements with customers — value contracts, quantity contracts, and rental agreements all live here.
Transaction Code | Description | Module | Application Component |
VA41 | Create Contract | CRM | CRM-BTX-BF-IF |
VA42 | Change Contract | CRM | CRM-BTX-BF-IF |
VA42W | Workflow for Master Contract | CRM | CRM-BTX-BF-IF |
VA43 | Display Contract | CRM | CRM-BTX-BF-IF |
VA44 | Actual Overhead: Sales Order | CO (Controlling) | CO-OM |
VA45 | List of Contracts | SD | SD-SLS-GF |
VA46 | Collective Subsequent Processing for Contracts | CRM | CRM |
Item Proposal
Item proposals let you pre-define which materials to suggest when creating sales orders for specific customers — speeding up order entry significantly.
Transaction Code | Description | Module | Application Component |
VA51 | Create Item Proposal | CRM | CRM-BTX-BF-IF |
VA52 | Change Item Proposal | CRM | CRM-BTX-BF-IF |
VA53 | Display Item Proposal | CRM | CRM-BTX-BF-IF |
VA55 | List of Item Proposals | CRM | CRM-BTX-BF-IF |
VA88 | Actual Settlement: Sales Orders | CRM | CRM-BTX-BF-IF |
Delivery/Shipping
Once a sales order is confirmed, the delivery process begins. This section of SAP SD T-Codes covers everything from creating outbound deliveries to managing inbound ones, picking, goods issue, and full shipment tracking. The VL-series is the largest group of SAP SD T-Codes in the delivery area, because the logistics execution side of SD is genuinely complex — especially in organizations with high order volumes or multiple warehouses.
VL01N is the standard sap sd tcode for creating an outbound delivery with a sales order reference. VL06O is the outbound delivery monitor — the transaction most warehouse supervisors and logistics coordinators live in.
Transaction Code | Description | Module | Application Component |
VL01 | Create Delivery | CRM | CRM |
VL01N | Create Outbound Dlv. with Order Ref. | CRM | CRM |
VL01NO | Create Outbound Dlv. w/o Order Ref. | CRM | CRM |
VL02 | Change Outbound Delivery | CRM | CRM |
VL02N | Change Outbound Delivery | CRM | CRM |
VL03 | Display Outbound Delivery | CRM | CRM |
VL03N | Display Outbound Delivery | CRM | CRM |
VL04 | Process Delivery Due List | CRM | CRM |
VL06 | Delivery Monitor | CRM | CRM |
VL06C | List Outbound Dlvs for Confirmation | CRM | CRM |
VL06F | General Delivery List – Outbound Delivery | CRM | CRM |
VL06G | List of Outbound Dlvs for Goods Issue | CRM | CRM |
VL06I | Inbound Delivery Monitor | CRM | CRM |
VL06IC | Confirmation of put away inb. deliv. | CRM | CRM |
VL06ID | Inbound Deliveries for Distribution | CRM | CRM |
VL06IF | Selection inbound deliveries | CRM | CRM |
VL06IG | Inbound deliveries for goods receipt | CRM | CRM |
VL06IP | Inbound deliveries for put-away | CRM | CRM |
VL06L | Outbound Deliveries to be Loaded | CRM | CRM |
VL06O | Outbound Delivery Monitor | CRM | CRM |
VL06P | List of Outbound Dlvs for Picking | CRM | CRM |
VL06T | List Outbound Dlvs (Trans. Planning) | CRM | CRM |
VL06U | List of Unchecked Outbound Deliveries | CRM | CRM |
VL08 | Confirmation of Picking Request | CRM | CRM |
VL09 | Cancel Goods Issue for Delivery Note | CRM | CRM |
VL10 | Edit User-specific Delivery List | CRM | CRM |
VL10A | Sales Orders Due for Delivery | CRM | CRM |
VL10B | Purchase Orders Due for Delivery | CRM | CRM |
VL22N | Display Delivery Change Documents | CRM | CRM |
VL31N | Create Inbound Delivery | CRM | CRM |
VL32N | Change Inbound Delivery | CRM | CRM |
VL33N | Display Inbound Delivery | CRM | CRM |
VL34 | Generation of Inbound Deliveries | CRM | CRM |
VL71 | Output from Outbound Deliveries | CRM | CRM |
VT01N | Create Shipment | CRM | CRM-BF |
VT02N | Change Shipment | CRM | CRM-BF |
VT03N | Display Shipment | CRM | CRM-BF |
VT04 | Transportation Worklist | CRM | CRM-BF |
VT06 | Select Shipments: Materials Planning | CRM | CRM-BF |
VT07 | Collective run in the background | CRM | CRM-BF |
VT19 | Shipment Tendering Status Monitor | CRM | CRM-BF |
VT20 | Overall Shipment Process Monitor | CRM | CRM-BF |
VT70 | Output for Shipments | CRM | CRM-BF |
Billing
Billing is the end of the order-to-cash chain — and getting it right matters both for revenue recognition and for customer relationships. The SAP SD T-Codes in the VF-series handle everything from creating individual billing documents. These are the SAP SD T-Codes that close the loop on the order-to-cash cycle — managing invoice lists, handling blocked billing, and getting invoices out the door.
VF01 creates a billing document. VF04 is the billing due list — the transaction that shows everything ready to be billed based on deliveries and orders. VF31 handles output, which is how invoices actually get sent to customers. For sap sales report tcode needs in billing, VF05N gives you the full list of billing documents with filtering options.
Transaction Code | Description | Module | Application Component |
VF01 | Create Billing Document | AP | AP-PRC-PR |
VF02 | Change Billing Document | AP | AP-PRC-PR |
VF03 | Display Billing Document | AP | AP-PRC-PR |
VF04 | Maintain Billing Due List | AP | AP-PRC-PR |
VF05 | List Billing Documents (Use VF05N instead) | CRM | CRM |
VF05N | List of Billing Documents | SD | SD-SLS |
VF07 | Display Billing documents from the archive | AP | AP-PRC-PR |
VF11 | Cancel Billing Document | AP | AP-PRC-PR |
VF21 | Create Invoice List | AP | AP-PRC-PR |
VF22 | Change invoice list | AP | AP-PRC-PR |
VF23 | Display Invoice List | AP | AP-PRC-PR |
VF24 | Edit Work List for Invoice Lists | AP | AP-PRC-PR |
VF25 | List of Invoice Lists | CRM | CRM |
VF26 | Cancellation invoice list | AP | AP-PRC-PR |
VF27 | Display invoice list from archive | AP | AP-PRC-PR |
VF31 | Output from Billing Documents | CRM | CRM |
VFX2 | Display Blocked Billing Documents | AP | AP-PRC-PR |
VFX3 | List Blocked Billing Documents | AP | AP-PRC-PR |
VF_VPRS | Update Costs | AP | AP-PRC-PR |
Configuration (SD)
SD configuration is where functional consultants spend a significant portion of their project time. These SAP SD T-Codes cover the IMG settings that define how the module behaves. Getting configuration SAP SD T-Codes right at the start of a project pays dividends for years — sales document types, item categories, schedule lines, delivery types, and the entire pricing procedure setup. Getting configuration right in the beginning saves enormous amounts of rework later.
VOV8 is where sales document types are defined. V/08 is the pricing procedure configuration transaction — one of the most important in the entire SD configuration landscape.
Transaction Code | Description | Module | Application Component |
VOV8 | Define Sales document type (header) | CRM | CRM-BF |
OVAZ | Assigning Sales area to sales documents type | CRM | CRM-BF |
OVAU | Order reasons | CRM | CRM-BF |
VOV4 | Assign Item categories (Item cat determination) | CRM | CRM-BF |
VOV6 | Schedule line categories | CRM | CRM-BF |
OVAL | To assign blocks to relevant sales documents, type | CRM | CRM-BF |
OVLK | Define delivery types | CRM | CRM-BF |
V/03 | Create Condition Table (SD Price) | AP | AP-PRC-PR |
V/04 | Change Condition Table (Sales pr.) | AP | AP-PRC-PR |
V/05 | Display Condition Table: (Sales Pr.) | AP | AP-PRC-PR |
V/06 | Condition Categories: SD Pricing | AP | AP-PRC-PR |
V/07 | Maintain Access (Sales Price) | AP | AP-PRC-PR |
V/08 | Maintain pricing procedure | AP | AP-PRC-PR |
V/09 | Condition Types: Account Determin. | AP | AP-PRC-PR |
V/10 | Account Determination: Access Seqnc | AP | AP-PRC-PR |
V/11 | Conditions: Account Determin.Proced. | AP | AP-PRC-PR |
V/12 | Account Determination: Create Table | AP | AP-PRC-PR |
V/13 | Account Determination: Change Table | AP | AP-PRC-PR |
V/14 | Account Determination: Display Table | AP | AP-PRC-PR |
OVKP | Pricing proc determination | CRM | CRM-BF |
Accounting (A/R)
The Accounts Receivable side of SD is where finance and sales operations intersect. These t codes in sap sd handle everything from displaying customer invoices to generating dunning letters and processing payments. Most of these sit in the FI module but are used regularly by SD teams — especially in organizations where SD consultants have responsibility across the full order-to-cash cycle.
FBL5N is one of the most-used codes in this group — it displays customer line items and is the go-to for reconciling what’s been billed against what’s been paid. F150 generates dunning letters for overdue accounts.
Transaction Code | Description | Module | Application Component |
FBL5N | Display Customer invoices by line | FI | FI-AR |
FBL1N | Display Vendor invoices by line | FI | FI-AP |
F.03 | Controlling Total Debit/Credit bkgs | FI | FI-GL |
F.08 | Generate FI Account balance | FI | FI-GL |
F.02 | Generate Month-to-date Inv. register | FI | FI-GL |
FBZ1 | Process payments | FI | FI-AP/FI-AR |
FB12 | Rqst Individual Customer Corresp. | FI | FI-AR |
F.61 | Generate Customer Correspondence | FI | FI-AR |
FB07 | Enter Batch totals under Control ttl | FI | FI-GL |
FBL3N | Display G/L Acct. totals | FI | FI-GL |
FB08 | Reverse Posted Amounts | FI | FI-GL |
FBL6 | Customer Refunds | FI | FI-AR |
FB05 | Customer Refund to other than Payer | FI | FI-AR |
FB1D | Clearing Debit/Credit on Cust. acct. | FI | FI-AR |
F.23 | Customer Balance in Local Currency | FI | FI-AR |
FB01 | Create Invoice – legal entity adjust | FI | FI-GL |
F.27 | Generate Cust. Acct. statements | FI | FI-AR |
F150 | Generate Dunning Letters | FI | FI-AR |
Material Management & Inventory
SD doesn’t operate in isolation — it’s tightly connected to Materials Management and inventory. These sap sd tcodes bridge the two modules, handling stock overview, goods movements, and availability checks that directly affect whether a sales order can be fulfilled.
MMBE is the stock overview transaction — one of the first places to check when an availability issue is flagged on a sales order. CO09 gives a detailed availability overview that considers all planned and actual stock movements.
Transaction Code | Description | Module | Application Component |
MM01 | Create Material | MM | MM-MD |
MM02 | Change Material | MM | MM-MD |
MM03 | Display Material | MM | MM-MD |
CO09 | Availability Overview | PP/SD | PP-MRP |
MB51 | Material Document List | MM | MM-IM-GF |
MB52 | List of Warehouse Stocks on Hand | MM | MM-IM-GF |
MB5B | Stocks for Posting Date | MM | MM-IM-GF |
MBSM | Display Cancelled Material Documents | MM | MM-IM-GF |
MD04 | Display Stock Requirements Situation | PP | PP-MRP |
MMBE | Stock Overview | MM | MM-IM-GF |
LT12 | Adjusting Transfer Order – Confirmation Quantity | WM | LE-WM |
LT25 | Collectively Confirm Transfer Order | WM | LE-WM |
Bill of Materials (BOM)
Bill of Materials functionality in SD becomes important whenever you’re selling configurable products or kits where the final product is assembled from putting together multiple components. The CS-series is extensive — it covers creation, change, display, archiving, and mass maintenance of BOMs across multiple BOM categories.
Transaction Code | Description | Module | Application Component |
CS01 | Create Material BOM | PP | PP-BD-BOM |
CS02 | Change Material BOM | PP | PP-BD-BOM |
CS03 | Display Material BOM | PP | PP-BD-BOM |
CS00 | BOM Menu | PP | PP-BD-BOM |
CS05 | Change Material BOM Group | PP | PP-BD-BOM |
CS06 | Display Material BOM Group | PP | PP-BD-BOM |
CS07 | Allocate Material BOM to Plant | PP | PP-BD-BOM |
CS08 | Change Material BOM – Plant Allocation | PP | PP-BD-BOM |
CS09 | Display Allocations to Plant | PP | PP-BD-BOM |
CS11 | Display BOM Level by Level | PP | PP-BD-BOM |
CS12 | Multilevel BOM | PP | PP-BD-BOM |
CS13 | Summarized BOM | PP | PP-BD-BOM |
CS14 | BOM Comparison | PP | PP-BD-BOM |
CS15 | Single-Level Where-Used List | PP | PP-BD-BOM |
CS20 | Mass Change: Initial Screen | PP | PP-BD-BOM |
CS21 | Mass Material Change: Initial Screen | PP | PP-BD-BOM |
CS22 | Mass Document Change: Initial Screen | PP | PP-BD-BOM |
CS23 | Mass Class Change: Initial Screen | PP | PP-BD-BOM |
CS25 | Archiving for BOMs | PP | PP-BD-BOM |
CS26 | BOM Deletion | PP | PP-BD-BOM |
CS27 | Retrieval of BOMs | PP | PP-BD-BOM |
CS28 | Archiving for BOMs | PP | PP-BD-BOM |
CS31 | Create Class BOM | PP | PP-BD-BOM |
CS32 | Change Class BOM | PP | PP-BD-BOM |
CS33 | Display Class BOM | PP | PP-BD-BOM |
CS40 | Create a Link to Configurable Material | PP | PP-BD-BOM |
CS41 | Change Material Config. Allocation | PP | PP-BD-BOM |
CS42 | Display Material Config. Assignment | PP | PP-BD-BOM |
CS51 | Create Standard BOM | PP | PP-BD-BOM |
CS52 | Change Standard BOM | PP | PP-BD-BOM |
CS53 | Display Standard BOM | PP | PP-BD-BOM |
CS61 | Create Order BOM | PP | PP-BD-BOM |
CS62 | Change Order BOM | PP | PP-BD-BOM |
CS63 | Display Order BOM | PP | PP-BD-BOM |
CS71 | Create WBS BOM | PP | PP-BD-BOM |
CS72 | Change WBS BOM | PP | PP-BD-BOM |
CS73 | Display WBS BOM | PP | PP-BD-BOM |
CS74 | Create Multi-Level WBS BOM | PP | PP-BD-BOM |
CS75 | Change Multi-Level WBS BOM | PP | PP-BD-BOM |
CS76 | Display Multi-Level WBS BOM | PP | PP-BD-BOM |
CS80 | Change Documents for Material BOM | PP | PP-BD-BOM |
CS81 | Change Documents for Standard BOM | PP | PP-BD-BOM |
CS82 | Change Documents for Sales Order BOM | PP | PP-BD-BOM |
CS83 | Change Documents for WBS BOM | PP | PP-BD-BOM |
CS84 | Change Documents for Class BOM | PP | PP-BD-BOM |
CS90 | Material BOM Number Ranges | PP | PP-BD-BOM |
CS91 | Number Ranges for Standard BOMs | PP | PP-BD-BOM |
CS92 | Number Ranges for Sales Order BOMs | PP | PP-BD-BOM |
Output Management
Output management in SD handles how documents get generated and sent — invoices to customers, delivery notes to warehouse staff, shipping documents to carriers. The VV-series codes control output condition records, while NACE is the central transaction for configuring the entire output determination setup.
If a document isn’t printing or sending correctly, the investigation usually starts. Knowing these SAP SD T-Codes saves a ton of troubleshooting time — checking condition records, output types, and communication methods.
Transaction Code | Description | Module | Application Component |
VV11 | Create Output: Sales | SD | SD-BF-OC |
VV12 | Change Output: Sales | SD | SD-BF-OC |
VV13 | Display Output: Sales | SD | SD-BF-OC |
VV21 | Create Output: Shipping | SD | SD-BF-OC |
VV22 | Change Output: Shipping | SD | SD-BF-OC |
VV23 | Display Output: Shipping | SD | SD-BF-OC |
VV31 | Create Output: Transportation | SD | SD-BF-OC |
VV32 | Change Output: Transportation | SD | SD-BF-OC |
VV33 | Display Output: Transportation | SD | SD-BF-OC |
VV61 | Create Output: Billing | SD | SD-BIL-OC |
VV62 | Change output: Billing | SD | SD-BIL-OC |
VV63 | Display Output: Billing | SD | SD-BIL-OC |
VV71 | Create Output: Handling Units | LE | LO-HU |
VV72 | Change Output: Handling Unit | LE | LO-HU |
VV73 | Display Output: Handling Unit | LE | LO-HU |
NACE | Output Customizing | SD | SD-BF-OC |
Routes
Routes define the path goods take from your shipping point to the customer’s delivery address — including transportation zones, shipping conditions, and transit times. These SAP SD T-Codes are essential for organizations where accurate delivery dates and freight cost calculation matter. Route-related SAP SD T-Codes are often overlooked in initial implementations.
Transaction Code | Description | Module | Application Component |
OVLH | Routes Overview | SD | SD-TRA |
0VTC | Definition of Route Determination | SD | SD-TRA |
0VRF | Route definition | SD | SD-TRA |
VL51 | Create Route Schedule | SD | SD-TRA |
VL52 | Change Route Schedule | SD | SD-TRA |
VL53 | Display Route Schedule | SD | SD-TRA |
EDI Related Transactions
EDI (Electronic Data Interchange) enables automated document exchange between SAP and external trading partners — purchase orders coming in, advance shipping notifications going out, invoices transmitted electronically. These SAP SD T-Codes cover both the SD-specific EDI configuration and the broader IDoc framework that handles the actual message processing.
WE20 is where partner profiles are configured — the settings that define how IDocs are processed for each trading partner. BD87 is the one you’ll use when IDocs fail and need to be reprocessed.
Transaction Code | Description | Module | Application Component |
VOE1 | Translation between EDI categories and SD item categories | SD | SD-EDI |
VOE2 | Table EDSC view – Customer link to sales area detail | SD | SD-EDI |
VOE3 | Table view EDPVW – Add partner types transferred to IDoc | SD | SD-EDI |
VOE4 | Table view EDPAR – Link external partner number with internal | SD | SD-EDI |
WEDI | EDI Administrator Menu | BC | BC-MID |
BALE | IDoc Administration | BC | BC-MID |
WE09 / WE02 | IDoc lists according to content | BC | BC-MID |
WE05 | View IDocs | BC | BC-MID |
WE19 | EDI test tool | BC | BC-MID |
WE20 | Partner profile configuration | BC | BC-MID |
WE30 | Create IDoc extension type | BC | BC-MID |
WE31 | Segment create | BC | BC-MID |
WE57 | Assign function module to logical message and IDoc type | BC | BC-MID |
WE60 | IDoc type documentation tool | BC | BC-MID |
WE82 | Link Release detail to Extension IDoc Type | BC | BC-MID |
BD55 | Conversion rule user exit | BC | BC-MID |
BD87 | Reprocess IDocs in error | BC | BC-MID |
BALA | ALE Application Distribution | CA | CA-BFA-ABL |
BALM | ALE Master Data Distribution | CA | CA-BFA-ABL |
OVA9 | Create entries for sold-to customer EDI schedule releases | CRM | CRM-BTX-BF-IF |
OVAI | Create entries for Vendor/Partner description combination | CRM | CRM-BTX-BF-IF |
OVAJ | Post-schedule requirements using discrete dates only | CRM | CRM-BTX-BF-IF |
Workflow
SAP Workflow automates the routing of work items — approvals, notifications, exception handling — based on business rules. In SD, workflow is used for things like credit hold approvals, contract release, and order exception management. These sap transaction codes are used primarily by administrators and developers setting up or troubleshooting workflow scenarios.
Transaction Code | Description | Module | Application Component |
SWEAD | Event queue administration | BC | BC-BMT-WFM |
SWE2 | Event type linkages | BC | BC-BMT-WFM |
SWE3 | Event linkages | BC | BC-BMT-WFM |
PPOME | Organizational Unit Maintenance | BC | BC-BMT-OM |
SWE5 | Consistency Checks for Event Linkages | BC | BC-BMT-WFM |
SWUD | Workflow Diagnostic Tool | BC | BC-BMT-WFM |
General/Other
This section covers the utility and cross-functional SAP SD T-Codes that don’t fit neatly into one category but are indispensable in any SD environment but come up constantly in day-to-day SD work. SPRO is the main IMG (Implementation Guide) — the starting point for virtually all configuration work in SAP. VKM1 is the blocked SD documents list, which finance teams and credit managers check regularly. VOFM is where pricing formulas and requirements get configured — a critical tool for anyone doing advanced SD pricing work.
Transaction Code | Description | Module | Application Component |
SPRO | Enterprise IMG | BC | BC-CUS-TOL-IMG |
VKM1 | List of blocked SD documents | SD | SD-SLS |
VKM3, VKM4 | List of sales documents | SD | SD-SLS |
VD52 | Material Determination | SD | SD-MD |
OBB8 | Maintain Payment Terms | FI | FI-AR/FI-AP |
OVSG | Maintenance of Incoterms | SD | SD-BF |
VOFM | Configuration conditions, formulas, requirements | SD | SD-BF |
SE38 | ABAP Editor | BC | BC-ABA |
SM01 | Transaction list | BC | BC-SEC |
SHDB | Transaction recorder (BDC) | BC | BC-ABA |
CMOD | User exit/project tool | BC | BC-DWB |
SE16 | Table contents display | BC | BC-DWB |
SOST | View mails sent externally from SAP | BC | BC-SRV-COM |
SU53 | Check authorization object | BC | BC-SEC-USR |
SQVI | Table Quickviewer | BC | BC-DWB-QUE |
ST22 | ABAP Dump Analysis | BC | BC-ABA-LA |
ST01 | System trace | BC | BC-CST-LL |
ST11 | Display developer trace | BC | BC-CST-LL |
ST05 | SQL Trace | BC | BC-TWB-TST |
SM21 | System log | BC | BC-CCM-MON |
SM12 | Display locked entries | BC | BC-CST-EQ |
ME22N | PO Change | MM | MM-PUR |
ME57 | Create PO from purchase requisition | MM | MM-PUR |
MIGO | Post goods receipt | MM | MM-IM |
MB01 | Goods Movement | MM | MM-IM |
Obsolete/Replaced Transactions
SAP periodically retires transaction codes — especially during major releases like S/4HANA. Knowing which codes are done and dusted helps you avoid creating new processes around older releases.
Transaction Code | Description | Module | Application Component |
VA05N | List of Sales Orders — Obsolete with S/4HANA, use VA05 | SD | SD-SLS-GF |
SDO1 | Sales orders within a period — Obsolete with S/4HANA, use VA05 | SD | SD-SLS-GF |
A Note on Using the SAP SD T-Codes List Effectively
Having a sap t code list is only useful if you know how to find what you need in the moment. The full range of SAP SD T-Codes in this guide spans every functional area of the module. A few practical tips worth knowing.
The sap transaction codes list in this guide is organized by functional area, which reflects how most SD teams think about their work. But in practice, the fastest way to find a code you can’t remember is the SAP search function — from any SAP screen, you can use the command field at the top and type a partial description to search available transactions. In some SAP versions, the code SM01 gives you a full list of available transactions with descriptions you can browse or filter.
If you’re working across multiple areas of SD, it’s worth building a personal shortlist of the sap sd t codes you use daily. Most experienced SD practitioners have ten to fifteen codes they use constantly and a broader reference list — like this one — for everything else.
For teams managing roles and authorizations, the sap transaction codes assigned to each user role need careful attention. Not every SD user needs access to every code in this list. Segregation of duties means, for example, that the person creating sales orders (VA01) ideally shouldn’t also be the one releasing billing documents or maintaining pricing conditions.
FAQ on SAP SD T‐Codes
1. What are SAP SD T‐Codes?
SAP SD T-Codes — short for transaction codes — are shortcut commands used to directly navigate to specific functions within the SAP Sales and Distribution module. Instead of clicking through multiple menus to reach a function, a user can type the transaction code directly into the SAP command field and be there instantly. SAP SD T-Codes cover every function in the SD module: creating customers, processing sales orders, managing deliveries, generating invoices, configuring pricing, and more. They’re the primary way experienced SAP users navigate the system, and the SAP SD T-Codes in this guide represent the complete picture of what’s available in the module, and knowing the right ones for your role is one of the most practical skills you can develop when working with SAP.
2. Why are T‐Codes important in SAP SD?
SAP SD T-Codes matter because they make the system significantly faster and more efficient to use. Rather than navigating through layered menus — which can take many clicks even for routine functions — a user who knows the relevant sap t code can reach any function in the system in seconds. In high-volume environments where SD users process dozens or hundreds of transactions per day, that speed adds up meaningfully. That’s why knowing the right SAP SD T-Codes for your role really matters. It’s not just technical, it’s practical.
It helps you work faster, and it also ties into access control. In SAP, roles are set up around T-Codes, so people can only access what they’re supposed to.
3. How do I search for a T‐Code in SAP?
If you don’t know a T-Code, there are a few easy ways to find it.
Start with the SAP Easy Access menu. It’s the main screen after login and everything is grouped by module, so you can browse from there.
You can also use the search bar in SAP GUI. Just type a keyword or part of the name.
In some systems, you can type * followed by a keyword in the command field to see matching T-Codes.
For a broader sap transaction codes list lookup covering all SAP SD T-Codes, SE93 lets you display and search transaction code definitions with f
4. Can I customize T‐Codes for my role?
Yes — to an extent. SAP SD T-Codes are standard and can’t be changed since they’re delivered by SAP. But that doesn’t mean you’re stuck with them as-is.
There’s still plenty of flexibility. Using SE93, you can create your own custom transaction codes. They can point to an existing function, a program, or even something custom you’ve built.
Basically, you’re just creating shortcuts. Instead of jumping through multiple screens, users can go straight where they need. It also helps keep things cleaner, since different roles can have access to only what they actually use.
Area menus — maintained using SE43 — can also be customized to present only the SAP SD T-Codes relevant to a specific user group. This is a common approach in large organizations with distinct SD user roles, each needing a different subset of SAP SD T-Codes. What you can’t do is change the behavior of a standard SAP transaction code itself — those are locked SAP-delivered objects. Any customization happens on top of, or alongside, the standard code.
5. Which T‐Codes are used to create a customer master?
Among all SAP SD T-Codes, the customer master codes are some of the most-used. The most commonly used sap customer master tcode for creating a customer is XD01, which creates a customer centrally — meaning it creates both the general data and the sales area data in one transaction. If you only need to create the financial accounting view of a customer, FD01 handles that. Some organizations also use the Business Partner transaction BP, which is the S/4HANA-aligned approach that consolidates customer and vendor master maintenance into a single interface. For anyone looking for the sap customer tcode to maintain existing records, XD02 handles changes centrally and XD99 is the transaction for mass maintenance when you need to update multiple customer records at once.
