SAP SD Order to Cash Part 2: The Sales Order — Order Type, Item Category, Pricing and ATP

Key takeaway

What happens when a sales order is saved: order type controls, partner determination, item category and schedule line determination, pricing procedure, availability check and confirmation, credit check, incompletion and blocks — the order as the source for everything downstream.

Explanation

📌 KEY POINTS
✅ Order type controls number ranges, partner and pricing procedures, delivery/billing types and checks.
✅ Item category (VOV4) and schedule line category (VOV5) are determined per item and control what happens next.
✅ Pricing procedure (OVKK) calculates net value and tax.
✅ ATP confirms quantities and dates; credit and incompletion checks may block the order.
⚠️ Unconfirmed schedule lines or blocks stop deliveries silently — check status before escalating.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 showed the end-to-end flow. Now the order.

━━━━━━━━━━━━━━━━━━━━
▶ 1. ORDER TYPE

Document category, number range, reference rules, delivery and billing types.

━━━━━━━━━━━━━━━━━━━━
▶ 2. PARTNERS

Sold-to, ship-to, bill-to, payer via partner determination.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ITEMS

Item category from order type + item category group (+ usage, higher-level).
Schedule line category from item category + MRP type.

━━━━━━━━━━━━━━━━━━━━
▶ 4. PRICING

Procedure from sales area + document/customer pricing procedure.
Condition records, taxes.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CHECKS

ATP confirmation (dates via scheduling).
Credit check, incompletion log, delivery/billing blocks.

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

Create an order; check item category and schedule lines.
Review pricing analysis.
Check ATP result and status.

✅ CHECKPOINT: you can explain every determined value in the order.

Code example

ABAP Code

===== STEP 1: determinations =====VOV8 OR | VOV4 OR + NORM → TAN | VOV5 TAN + MRP type → CP | OVKK → RVAA01 ===== STEP 2: checks =====ATP: checking group + checking rule | credit: credit group + check rule | incompletion: procedure per document/item ===== STEP 3: status =====VA03 status overview: delivery status, credit status, incompletion, blocks

Real project scenario

A customer complained that orders were accepted but never shipped. The orders had no confirmed schedule lines because the material's checking group excluded planned receipts; users didn't check confirmation. Adjusting the checking rule and showing confirmation status to order entry users resolved it.

Common mistakes

Ignoring confirmation status.
Changing item categories manually without rules.
Missing partner functions.
Not reviewing incompletion.
Assuming saved means deliverable.

Best practices

Check confirmation and status after save.
Keep determinations rule-based.
Maintain partner procedures.
Use incompletion to enforce data.
Train users on blocks.

Interview angle

Questions: "What happens when a sales order is saved?", "How is the item category determined?", "Why isn't an order delivered?"
Strong answer: order type controls, partner determination, VOV4/VOV5, OVKK pricing, ATP confirmation, credit and incompletion, blocks and status.

Practice this lesson

Quick check

1. A material has physical stock, but the sales order confirms zero. What is the best first conclusion?

2. In pricing troubleshooting, what should you check before creating a new condition record?

3. An order is saved but never delivered. Which order data should you check first?

Interview questions

1. In a global MTO rollout, sales order items show a confirmed schedule line and TOR appears successful in VBBE, yet the production planner reports no planned/independent requirement visible in MD04 for that sales order's individual stock segment. As the architect, how would you systematically isolate whether this is a requirements class issue, special stock segregation issue, or MRP area configuration issue?

Answer it in your own words first, then compare.

2. What is the purpose of Transfer of Requirements (TOR) in SD, and how does it interact with MRP in materials planning?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.