Connect · how it links to the rest of SAP
nothing works in isolation

Standard Sales Order — How it Connects

SAP is an ERP — one system, every function joined up. So a sales order isn't a form on its own: it leans on data other teams own, runs checks against other modules as you build it, and the moment you save, it sets a chain in motion across the business. Seeing that web is the difference between clicking the process and understanding the system.

1 · What the order leans on

Before the order can be right, these must be right. The order pulls from master data and configuration that other teams own — get those wrong and every order inherits it.

Customer master · SD/FI

Who, where, on what terms

Name, ship-to address, partner functions, Incoterms, payment terms — and the link to their credit profile. The Sold-To entry pulls all of it.

Material master · MM

The product's identity

Description, unit of measure, division. The item line takes the product's identity from here — not its price.

Condition records · SD

Where the price actually lives

The net price is determined from condition records via the condition technique — not the order, not the material master.

Credit master · FI / FSCM

The customer's credit limit

The customer's limit and risk class — the data the credit check reads to pass or block the order.

Availability rules · aATP

How "available" is decided

Product allocation and supply protection settings the availability check applies when it works out a date.

2 · The checks it runs — live, as you build it

Each check is the sales order asking another part of SAP a question and acting on the answer — in real time, while you key the order.

Availability · aATP / Inventory

Can we meet the date?

Reaches into inventory and supply to return full, partial (a later date), or zero — which drives the backorder branch.

Credit check · FI / FSCM

Can they pay?

Reaches into Credit Management to check the limit and risk — clear, or credit-blocked (then it's communicate + escalate).

Free goods · SD pricing

Is a freebie owed?

The condition technique adds a free-of-charge line automatically when the quantity meets the free-goods condition record.

3 · What it sets in motion — downstream

Save the order and value flows across Sales, Logistics, Inventory and Finance — each document feeding the next. One save, four functions.

SD

Sales Order

The promise — what, for whom, at what price and date.

LE / Shipping

Outbound Delivery

The order becomes a shipment the warehouse can act on.

EWM / Inventory

Pick & Goods Issue

Stock is picked and issued — inventory drops, the cost posts.

SD Billing

Billing Document

The invoice — revenue is recognised against the delivery.

FI / AR

Accounting

A receivable and revenue post to the books; payment clears it.

This is why accuracy upstream matters so much.

A wrong price, a missed credit flag, a bad ship-to — it doesn't stay in the order. It rides the whole chain into delivery, billing and the books, and someone downstream pays for it. Understand the web, and you understand why a sales order is a promise the whole company keeps — not a form one person fills in. Get it right at the source and the whole chain runs clean: fewer mistakes downstream, less time fixing, more time running the business.

NeoKnova · Connect · Standard Sales Order · v2026-06-10
← Dashboard