Pricing, Shipping, Billing, Revenue and Credit

SD / O2Cbeginner

Pricing, Shipping, Billing and Credit Part 1: The Order-to-Cash Value Stream

Key takeaway

How the value-related SD functions fit together: pricing sets the value in the order, credit management protects exposure, availability and shipping deliver the goods, billing turns deliveries into receivables and revenue, output informs customers, and settlements/rebates adjust value afterwards — with pointers to the detailed tracks.

Explanation

📌 KEY POINTS
✅ Pricing determines the order value; the same value flows into credit exposure and billing.
✅ Credit checks protect exposure at order, delivery and goods issue.
✅ Shipping (delivery, picking, PGI) moves goods and posts COGS.
✅ Billing creates receivables and revenue; output sends documents; settlements adjust value later.
⚠️ A wrong value at pricing propagates to credit, billing, revenue and rebates — fix it at the source.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: The order-to-cash value stream
Part 2: Configuration and document flow across pricing, delivery, billing and credit
Detailed tracks: Pricing, Availability Check, Delivery, Picking & PGI, Billing, Credit, Output, Settlement.

━━━━━━━━━━━━━━━━━━━━
▶ 1. PRICING

Condition technique, pricing procedure, net value, tax.

━━━━━━━━━━━━━━━━━━━━
▶ 2. CREDIT

Exposure vs limit, blocks, releases.

━━━━━━━━━━━━━━━━━━━━
▶ 3. AVAILABILITY AND SHIPPING

ATP confirmation, delivery, picking, PGI (inventory → COGS).

━━━━━━━━━━━━━━━━━━━━
▶ 4. BILLING AND REVENUE

Invoice: receivable, revenue, tax; revenue recognition rules.

━━━━━━━━━━━━━━━━━━━━
▶ 5. AFTER-SALES VALUE

Output to customers, rebates/settlement, credit/debit memos, returns.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Create an order and follow its value from pricing to billing.
Check credit status and exposure.
Check FI postings after PGI and billing.

✅ CHECKPOINT: you can explain how one order's value appears in credit, inventory, AR and revenue.

Code example

ABAP Code

===== STEP 1: value path =====Order net value (pricing) → credit exposure (open order) → delivery/PGI (COGS) → invoice (AR, revenue, tax) → payment ===== STEP 2: detailed tracks =====Pricing (10) | Availability Check (10) | Delivery (5) | Picking & PGI (5) | Billing (10) | Credit (10) | Output (10) | Settlement (4)

Real project scenario

A mid-size distributor saw revenue, credit exposure and rebate accruals disagree for promotional orders. A manual discount was entered at billing instead of in the order, so credit and rebates used undiscounted values. Moving the discount to order pricing and blocking billing-only price changes aligned all downstream values.

Common mistakes

Fixing prices at billing.
Viewing functions in isolation.
Ignoring credit impact of pricing.
No end-to-end tests.
Treating output as an afterthought.

Best practices

Get value right at order pricing.
Test the full value chain.
Align credit with pricing values.
Reconcile revenue and rebates.
Use the detailed tracks for depth.

Interview angle

Questions: "Describe the O2C value flow", "How does pricing affect credit and billing?", "Where does COGS post?"
Strong answer: pricing → credit exposure → ATP/delivery/PGI (COGS) → billing (AR, revenue, tax) → payment; output and settlement; fix at source.

Practice this lesson

Quick check

1. During production readiness for Pricing, Shipping, Billing, Revenue and Credit, the team is validating Configuration and Document Flow Across Pricing, Delivery, Billing and Credit Management. Given the scenario "During a support ticket in an S/4HANA Private Cloud implementation, a customer's orders were unexpectedly blocked for credit even though their payment history was good", which choice best prevents a repeat failure?

2. Which step moves goods out of inventory and posts COGS?

3. A team proposes fixing wrong prices directly in invoices instead of orders. What is the risk?

Interview questions

1. A high-value order is blocked by credit management, and once released, the subsequent billing document fails with a revenue account determination error. As the architect, how do you diagnose which issue is the true root cause versus a symptom?

Answer it in your own words first, then compare.

2. Walk through the process by which values calculated in the pricing procedure become the basis for real-time credit exposure updates in SAP Credit Management, and explain the design considerations for a multi-entity global rollout.