Skip to content
Cette page existe aussi en français. Voir en français
SAP Module

SAP SD: the module explained

Sales and Distribution runs the whole sales cycle in SAP, from the customer order to the invoice. It is the commercial arm of the company, organised around one thread: order-to-cash, from order to payment. Here is what the module does, how that cycle runs, and where to start to train for it.

What exactly is SAP SD?

SAP SD, short for Sales and Distribution, is the module that runs the whole sales cycle, from the customer order to the invoice. It is the commercial arm of SAP: it records what the company sells, organises the shipping of the goods, then bills the customer. Everything rests on one thread called order-to-cash, from order to payment. In practice: a customer places an order, the system calculates the price and checks availability, an outbound delivery prepares shipping, the goods issue reduces stock, and an invoice goes to accounting.

Practically, SD rests on two pillars. First the sales area, meaning the sales organisation, the distribution channel and the division, which describes the angle from which the company sells. Then the condition technique, the engine that automatically calculates the price of an order line from condition records, with no re-keying. SAP says 77% of the world's transaction revenue runs through one of its systems (source: SAP). Behind that figure sits a simple reality: the sale is the point where money comes in, and SD is the module that drives it. That is what makes it a skill in high demand, right at the heart of company revenue.

The 30-second takeaway
  • SD runs the whole sales cycle, from the customer order to the invoice, around the order-to-cash thread.
  • Two pillars structure the module: the sales area and the condition technique that calculates prices.
  • Each step leaves a linked trace: order, outbound delivery, goods issue, invoice, payment.
  • SD is cross-functional: it talks to purchasing, finance, the warehouse, production and transport.

What SAP SD covers

Four areas, one thread: turning a customer's intent to buy into delivered goods and a settled invoice.

Master data and pricing

Condition record

The base: the customer record, the material record, and the condition records that drive the condition technique to calculate prices.

A poorly set customer record or price condition and every order behind it comes out wrong.

You prepare the data and prices before a single order is entered.
Transactions: VK11 VK12

Sales document

Sales order

The transactional heart: the quotation, the sales order and the contract, controlled by the document type, the item category and the schedule line category.

An incomplete order blocks what follows: the delivery or invoice will not trigger while the incompleteness check complains.

You record what the customer wants, in what quantity, at what price and for when.
Transactions: VA01 VA41

Shipping and delivery

Outbound delivery

The physical exit: the outbound delivery prepares shipping from a shipping point, picking pulls the goods, then the goods issue clears the stock.

Forgetting the goods issue keeps stock that no longer exists: the system and the dock no longer agree.

You turn a confirmed order into goods ready to leave, tracked down to the goods issue.
Transactions: VL01N VL02N

Billing

Billing document

The money coming in: the invoice is created from the delivery or the order, grouped through the billing due list, and posted to accounting.

A badly set account determination and the revenue lands on the wrong accounting account.

You bill what has been delivered and trigger the accounting entry for the revenue.
Transactions: VF01 VF04

The heart of SAP SD: the order-to-cash cycle

Almost all of SD fits into one sequence, from the customer's intent to buy to the cash collected. Each document flows from the previous one and keeps the link. Get this journey once, and the rest falls into place.

  1. Presales (quotation)

    It can all start before the order, with an inquiry or a quotation sent to the customer. This step is optional: on S/4HANA, you handle it in the sales inquiry and quotation apps. Once the customer agrees, the quotation turns into an order without re-keying everything.

  2. Sales order VA01

    The sales order is the pivot of the module: it says which material, in what quantity, at what price and for when. The condition technique calculates the price automatically, and an availability check confirms the possible date. You change it with VA02 and display it with VA03.

  3. Outbound delivery VL01N

    When the shipping date comes, the order becomes an outbound delivery, created with reference to the order from a shipping point. It is the document that drives the physical shipping. It can also be created in bulk through the delivery due list.

  4. Picking and goods issue VL02N

    The goods are picked, manually or through warehouse management, then the goods issue is posted on the delivery. This posting reduces stock and triggers the accounting entry for the movement. It is the moment the goods officially leave the company.

  5. Billing VF01

    The invoice is created from the delivery, or directly from the order for a service. It carries the prices, applies the billing type, and posts to accounting on the customer side. The billing due list (VF04) lets you bill in batches.

  6. Payment

    The invoice creates a customer receivable in accounting. Payment itself is handled on the finance side, where the incoming payment clears that receivable. The order-to-cash cycle is closed: the sale has turned into cash.

One thread, from order to payment, where each document keeps the link to the previous one.

SAP SD in the SAP landscape

SD is the point where money comes in, so it touches almost everyone. Here are the modules it exchanges with constantly, and the direction of the exchange.

MM MM and SD

Purchasing and stock

MM is the mirror of SD: it buys when SD sells. Both share the material and the same condition technique logic for pricing.

FI SD to FI

Finance

Every SD invoice creates an accounting entry and a customer receivable in FI. SD sells, FI collects and tracks the revenue.

WM SD to WM

Warehouse

The SD outbound delivery triggers the physical picking in WM or EWM, which pulls the goods from the right bin before shipping.

PP SD and PP

Production

In make-to-order, a sales order can trigger a production order. PP makes what SD has sold, then SD ships.

TM SD to TM

Transport

Once the delivery is ready, transport takes over: TM plans and executes the shipment of the goods to the customer.

SD and the neighbouring modules: who does what

SD never works alone. Here are the modules around it, and the exact line where each one takes over.

ModuleWhat it handlesIts boundary with SD
MM (purchasing and stock)The purchasing cycle, from need to supplier payment.MM handles the inbound side (buying), SD the outbound side (selling); they are two symmetric processes.
FI (accounting)Accounting, customer receivables and incoming payments.SD stops at the invoice; FI takes over for the receivable, the payment and the revenue.
MM-IM (inventory movements)Stock movements and quantities at storage-location level.SD triggers the goods issue; IM records the stock movement and its posting.
WM / EWM (warehouse)Warehouse management down to the bin, picking included.SD creates the delivery; WM or EWM prepares it physically and picks the goods.
PP (production)Planning and manufacturing of products.In make-to-order, SD sells and triggers; PP manufactures before SD ships.
TM (transport)Transport planning and execution.SD prepares the delivery; TM organises the actual shipment to the customer.
Indicative scopes: they vary with each company configuration.

Is SAP SD right for you?

SD fits some profiles more than others. See which side sounds like you.

SD is a natural fit if

  • You come from sales, commerce, order management or customer service.
  • Customer relationships, orders, pricing and billing speak to you.
  • You like a module at the heart of revenue, where every sale leaves a trace from order to invoice.
  • You want a central, cross-functional module that touches finance, logistics and production.

SD will speak to you less if

  • You are after pure development: head toward ABAP.
  • Only the physical warehouse appeals to you: look at WM or EWM instead.
  • Purchasing and the supplier relationship motivate you more: aim for MM.
Setting the record straight

Three myths about SAP SD

What people often say about the module, and what it really looks like once your hands are in it.

01
Myth

SD is just entering orders.

People picture a module where you type orders all day.

02
Myth

SD is commercial, not technical.

People assume a sales module is for the sales team.

03
Myth

The price is entered by hand on each order.

People think you have to type an amount line by line.

01
Reality

The real SD is in the configuration.

Behind the order screen, the real work is design: the sales area, the document types, the item categories and the condition technique. Setting all that well is what makes an order turn into a delivery then an invoice without a hitch, across thousands of transactions a day.

02
Reality

It is a functional configuration module.

SD does not sell, it gets configured. You work on document control, the copy control that makes an invoice flow from a delivery, account determination and the pricing procedure. It is a demanding functional role, close to finance and logistics, more than to pure sales.

03
Reality

The condition technique calculates the price.

The price is almost never entered by hand. The condition technique looks up the right condition records, base price, discounts, surcharges and taxes, and applies a pricing procedure that stacks it all automatically. Mastering this engine is one of the most sought-after skills in the module.

Where to start with SAP SD

Four steps, from meaning to practice. You do not need to know everything before you touch the screen.

  1. 1
    Understand the role of the module

    Order, delivery, invoice, order-to-cash: get the vocabulary and the meaning before the screens.

  2. 2
    Set up the sales area

    Sales organisation, distribution channel, division: the frame before the transaction.

  3. 3
    Train, from free to paid

    Start with free resources, then structure things with a track that makes you practise.

  4. 4
    Run a full cycle

    One order taken from creation to invoice on a practice system beats ten tutorials read.

Careers and opportunities

SAP reports more than 400,000 customer companies in over 180 countries (source: SAP), and they all sell something. SD is therefore one of the most widespread modules, present wherever there is an order, a delivery and an invoice. So knowing SAP sales stays in demand, on both the business and the consulting side, right across the French-speaking market: Luxembourg, Belgium, France, Switzerland and Quebec.

On the business side, you find the SD key user, the order management lead or the order processor who masters the tool and bridges to IT. On the consulting side, the SD consultant works on very concrete topics: modelling the sales area, tuning the condition technique, making the order-to-invoice flow reliable, connecting SD to finance and the warehouse. Both paths start from the same base: understanding order-to-cash and document control.

In practice, a first SD assignment looks like this: setting up a clean sales organisation, configuring a pricing procedure that applies discounts and taxes with no manual step, configuring copy control so the invoice flows from the delivery, then making the incompleteness check reliable so no order stays blocked. Concrete work, as close as it gets to the money coming in.

For a career change, SD is a good entry point if customer relationships and sales appeal to you: the cycle is intuitive and each step has an obvious commercial meaning. If you are considering the move, the career-change track lays out the steps and the pace; and if you want to go all the way to the consultant role, see the SAP consultant training.

FAQ

Frequently asked questions

What does SD mean in SAP?

SD stands for Sales and Distribution. It is the module that runs the whole sales cycle in SAP, from the customer order to the invoice, including shipping the goods. It is often summed up by the order-to-cash process, from order to payment.

What is the order-to-cash process?

Order-to-cash is the full chain of the sale, from order to cash collected. In SAP, it runs through the sales order, the outbound delivery, picking and goods issue, the invoice, then the payment handled in finance. Each document flows from the previous one and keeps the link, which makes the whole flow traceable.

What is the difference between SAP SD and MM?

SD and MM are two symmetric processes. MM handles buying, the inbound side: from need to purchase order, through to paying the supplier. SD handles selling, the outbound side: from sales order to invoice, through to payment. Both share the material and the same condition technique for pricing, but in opposite directions. One sends money out, the other brings it in.

How does SAP calculate an order's price?

Through the condition technique. Rather than entering an amount by hand, SAP looks up condition records, the base price, discounts, surcharges and taxes, then applies a pricing procedure that stacks and calculates it all automatically on each line. It is one of the most important topics in the module, and one of the most sought-after skills.

Do you need to code to work on SAP SD?

No. SD is a functional module: you configure a sales area, document types, a pricing procedure and copy control rules. Development belongs to technical profiles such as ABAP. Your edge is understanding the sales process and the business logic that links order, delivery and invoice.

Is SAP SD a good module for a career change?

Yes, especially if sales and customer relationships appeal to you. The cycle is intuitive: each step, order, delivery, invoice, has an obvious commercial meaning, which helps you take it in. SD is also very widespread and cross-functional, so opportunities are plenty. Coming from sales, order management or customer service is a real plus.

Next step

Ready to train for SAP SD?

The career-change track covers the business basics and hands-on practice on SAP processes, from the sales cycle to master data.