SAP Reference
SDSales & Distribution
Covers sales orders, deliveries, billing, pricing, and customer master data
16 tables14 t-codes2 S/4HANA changes
Verified August 2026
In the business-problem map Customer Service & Fulfillment
Tables
Master Data · 4
Transactional · 12
- KONVConditions (Transaction Data)transactionS/4HANA status: Replaced · Compat View
- LIKPSD Document: Delivery Header Datatransaction
- LIPSSD Document: Delivery Item Datatransaction
- PRCD_ELEMENTSPricing Elements (S/4HANA)transaction
- VBAKSales Document: Header Datatransaction
- VBAPSales Document: Item Datatransaction
- VBBESales Requirements: Individual Recordstransaction
- VBEPSales Document: Schedule Line Datatransaction
- VBKDSales Document: Business Datatransaction
- VBPASales Document: Partnertransaction
- VBRKBilling Document: Header Datatransaction
- VBRPBilling Document: Item Datatransaction
Transaction Codes
- VA01Create Sales OrderCreate
- VA02Change Sales OrderChange
- VA03Display Sales OrderDisplay
- VA05List of Sales OrdersReport
- VF01Create Billing DocumentCreate
- VF02Change Billing DocumentChange
- VF03Display Billing DocumentDisplay
- VL01NCreate Outbound Delivery with Order ReferenceCreate
- VL02NChange Outbound DeliveryChange
- VL03NDisplay Outbound DeliveryDisplay
- VL06OOutbound Delivery MonitorList / Monitor
- XD01Create Customer (Centrally)CreateS/4HANA status: Replaced
- XD02Change Customer (Centrally)ChangeS/4HANA status: Replaced
- XD03Display Customer (Centrally)DisplayS/4HANA status: Replaced
S/4HANA Changes in SD
- KNA1→BUT000master data integration
Business Partner (BUT000) is the lead object in S/4HANA; KNA1 persists and is kept in sync via CVI (Customer-Vendor Integration). Create/update via Business Partner transactions
- KONV→PRCD_ELEMENTScompatibility view
SD pricing writes to PRCD_ELEMENTS; KONV remains for legacy/CRM scenarios, with V_KONV providing compatibility reads