SAP SD Order to Cash Part 5: Configuration and Integration with MM and FI

Key takeaway

The configuration objects that make O2C work and how they integrate: document types, item and schedule line categories, copy control, pricing and account determination, and the links to MM (availability, movement types, valuation) and FI (receivables, revenue, tax, credit).

Explanation

📌 KEY POINTS
✅ Document type, item category and schedule line category are the three control layers of every order.
✅ Copy control links order → delivery → billing and controls data and pricing transfer.
✅ MM integration: ATP, movement types (601), valuation class → COGS.
✅ FI integration: VKOA revenue, customer reconciliation account, tax codes, credit exposure.
⚠️ Configuration changes in one layer ripple across modules — test end to end.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–4 covered the process. Now its configuration and integration.

━━━━━━━━━━━━━━━━━━━━
▶ 1. CONTROL LAYERS

VOV8 order type, VOV7 item category, VOV6 schedule line category.

━━━━━━━━━━━━━━━━━━━━
▶ 2. COPY CONTROL

VTLA, VTFL, VTFA with requirements and data transfer routines.

━━━━━━━━━━━━━━━━━━━━
▶ 3. PRICING AND ACCOUNTS

Pricing procedure determination; VKOA with account keys.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MM INTEGRATION

Checking group, requirements transfer, movement type 601, valuation.

━━━━━━━━━━━━━━━━━━━━
▶ 5. FI INTEGRATION

Receivables, revenue, tax, credit management.

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

Map configuration for a standard order.
Trace postings in MM and FI.
Change one setting and test impact.

✅ CHECKPOINT: you can explain which configuration object causes each posting.

Code example

ABAP Code

===== STEP 1: layers =====VOV8 OR (delivery LF, billing F2) → VOV7 TAN (billing relevance A) → VOV6 CP (601, requirements) ===== STEP 2: copy control =====VTLA OR → LF | VTFL LF → F2 (pricing type, billing quantity) ===== STEP 3: integration =====MM: 601 → valuation class → COGS | FI: VKOA ERL → revenue; tax codes; reconciliation account; credit exposure

Real project scenario

A support ticket reported invoice values different from orders after a new order type was introduced. Copy control from delivery to billing redetermined prices for the new type. Aligning copy control pricing types and adding copy control to the new-type checklist fixed it.

Common mistakes

Changing layers without end-to-end tests.
Incomplete copy control for new types.
Ignoring MM/FI effects.
Missing VKOA entries.
No configuration documentation.

Best practices

Document the control layers.
Use checklists for new types.
Test across modules.
Keep copy control consistent.
Review postings in tests.

Interview angle

Questions: "What are the control layers of a sales document?", "How is SD integrated with MM and FI?", "What does copy control do?"
Strong answer: VOV8/VOV7/VOV6 layers, copy control, pricing and VKOA, MM (ATP, 601, valuation) and FI (AR, revenue, tax, credit), end-to-end testing.

Practice this lesson

Quick check

1. Which SAP SD object mainly controls whether a sales-order item is delivery-relevant and billing-relevant?

2. Interviewers frequently probe whether a candidate understands that item category and schedule line category are determined, not manually chosen at random, and whether the candidate can explain the SD-MM-FI integration chain triggered by goo. In the Sales Documents and End-to-End Order-to-Cash context, which answer shows the strongest practical judgment?

3. Which three configuration layers control a sales document item's behavior?

Interview questions

1. After a configuration change, invoices post revenue to the wrong account and some deliveries no longer create billing. How do you analyse the O2C configuration?

Answer it in your own words first, then compare.

2. What is the difference between sales document type, item category and schedule-line category in SAP SD?

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.