SAP Sales and Distribution (SD) is the module that manages everything related to selling products and services to customers — from the moment a customer places an order to the moment payment is received. It is tightly integrated with SAP MM (for inventory and delivery), SAP FI (for billing and revenue), and SAP PP (for production planning). For consultants working in any customer-facing business process, SD is unavoidable. This guide introduces the core concepts, the order-to-cash cycle, and the key configuration elements of SAP SD.
1The Order-to-Cash Cycle
The order-to-cash (O2C) process is the foundation of SAP SD. It moves from customer inquiry to delivery, billing, and finally payment collection.
The cycle begins with a Sales Order (VA01) — a binding commitment to deliver specific goods or services to a customer at an agreed price. Once the goods are ready, an Outbound Delivery (VL01N) is created, picking and packing instructions are generated, and the physical goods leave the warehouse. After delivery, a Billing Document (VF01) is created and sent to the customer. The billing document creates an accounting entry in FI (debit customer, credit revenue). Finally, when the customer pays, the open item is cleared in Accounts Receivable.
- VA01 — create sales order
- VL01N — create outbound delivery
- VF01 — create billing document
- VA05 — list of sales orders
- VF05 — list of billing documents
- VKM3 — release blocked sales orders (credit check)
2Organizational Structure in SAP SD
Before any SD transaction can be posted, the organizational structure must be defined. This is one of the most important configuration decisions in an SD implementation because it determines reporting capabilities and operational flexibility.
The key SD organizational units are: Sales Organization (responsible for sales transactions and legally liable for contracts), Distribution Channel (the channel through which products reach the customer: retail, wholesale, internet), and Division (a grouping of products for reporting). Together, these form the Sales Area — the central unit for SD transactions.
Each Sales Area is assigned to a Company Code (FI), a Plant (MM/PP), and a Shipping Point (logistics). This assignment chain ensures that a sales transaction flows correctly through all integrated modules.
3Master Data: Customers, Materials, and Pricing
SD relies on three main master data objects. The Customer Master (created in T-code BP in S/4HANA) stores all customer information: address, payment terms, credit limit, delivery priority, and sales area assignments. Like the material master, it is organized into views — General Data, Company Code data, and Sales Area data.
The Material Master in SD contains the Sales views: delivering plant, loading group, transportation group, and item category group (which controls how the material behaves in sales documents).
Pricing in SD is controlled by the Pricing Procedure — a sequence of condition types (price, discounts, surcharges, taxes) that determine the final price for a sales order line item. Condition records store the actual values: a price of €100 for material X sold to customer group A in Sales Organization 1000. The system finds the applicable condition records automatically when a sales order is created.
4Credit Management and Delivery Blocks
SAP SD has a built-in credit management function that compares a customer's outstanding receivables (including open orders and deliveries not yet billed) against their configured credit limit. If the limit is exceeded, the sales order is automatically blocked.
Blocked orders appear in the credit management worklist (VKM1) and must be manually released by an authorized user (VKM3) after reviewing the customer's credit situation. This is a critical internal control — without it, organizations can inadvertently extend unlimited credit to customers.
Delivery blocks can also be set for other reasons: incomplete data (missing delivery address), customer-specific hold, or seasonal embargo. The system checks for blocks during delivery creation and prevents processing until the block is removed.
5Integration with FI: Revenue Recognition and Account Determination
When a billing document is posted in SD, the system automatically determines which GL accounts to post to using Account Determination — a combination of the chart of accounts, the condition type, the account key, and the customer account assignment group and material account assignment group.
In S/4HANA, revenue recognition has been significantly enhanced. The new Revenue Accounting and Reporting (RAR) component implements IFRS 15 / ASC 606 requirements — revenue is recognized based on performance obligations, not just billing. This is particularly important for subscription businesses and long-term contracts.
For most standard product sales, the integration is straightforward: billing posts a debit to the customer reconciliation account (AR) and a credit to the revenue account determined by the account determination configuration.
Key Takeaway
SAP SD is a rich module that rewards consultants who understand the business processes it supports, not just the technical configuration. The order-to-cash cycle, pricing procedures, credit management, and FI integration are the areas where most SD projects spend the most time — and where the biggest business impact is delivered.