SD / O2Cintermediate

SD Revenue Recognition Part 2: Classic SD Revenue Recognition Configuration (ECC Context)

Key takeaway

Understand the classic ECC SD revenue recognition setup you may meet in legacy systems: item category revenue recognition indicators, accrual period start rules, deferred revenue and unbilled receivables accounts, VF44 processing, VF45 reports and the tables involved — and what it means for S/4HANA migration.

Explanation

📌 KEY POINTS
✅ Classic SD revenue recognition is controlled by the item category (revenue recognition indicator, accrual period start).
✅ Revenue account determination includes deferred revenue and unbilled receivables accounts.
✅ VF44 posts revenue per recognition schedule; VF45 reports; data in VBREVK/VBREVE.
✅ This functionality exists in ECC; in S/4HANA it must be replaced (typically by RAR) before or during conversion.
⚠️ Open revenue recognition data must be migrated and reconciled carefully during S/4HANA conversion.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 introduced principles. Now the classic ECC setup you may inherit.

━━━━━━━━━━━━━━━━━━━━
▶ 1. ITEM CATEGORY SETTINGS

Revenue recognition indicator: time-based, service-based, billing-related (per option).
Accrual period start rules (e.g. contract start).

━━━━━━━━━━━━━━━━━━━━
▶ 2. ACCOUNTS

Deferred revenue and unbilled receivables accounts in revenue account determination.

━━━━━━━━━━━━━━━━━━━━
▶ 3. PROCESSING

Billing posts to deferred/unbilled accounts.
VF44 recognizes revenue per period/event.

━━━━━━━━━━━━━━━━━━━━
▶ 4. REPORTING

VF45 revenue report; reconciliation of balances.

━━━━━━━━━━━━━━━━━━━━
▶ 5. MIGRATION

S/4HANA: classic SD rev rec not supported → transition to RAR.
Migrate open items and balances; reconcile.

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

Review item categories with rev rec indicators in legacy system.
List open recognition items and balances.
Plan RAR migration.

✅ CHECKPOINT: you can list every legacy item category using SD revenue recognition and its S/4HANA replacement.

Code example

ABAP Code

===== STEP 1: legacy objects =====Item category (VOV7): revenue recognition indicator, accrual period startRevenue account determination: deferred revenue account, unbilled receivables accountTransactions: VF44 (revenue recognition processing), VF45 (revenue report)Tables: VBREVK (control), VBREVE (revenue lines), VBREVR (reference) ===== STEP 2: migration =====Inventory item categories with rev rec → design RAR POB types → migrate open contracts/balances → reconcile

Real project scenario

During an S/4HANA conversion readiness check, a company discovered 14 item categories using classic SD revenue recognition for service contracts. The conversion required transitioning to RAR first. The team designed RAR performance obligation types, migrated open contracts with balances, and reconciled deferred revenue before conversion.

Common mistakes

Assuming VF44 works in S/4HANA.
Missing open balances in migration.
No reconciliation of deferred revenue.
Leaving rev rec out of conversion scope.
No finance ownership.

Best practices

Inventory rev rec usage early.
Plan RAR transition as a finance project.
Reconcile balances before cut-over.
Keep audit documentation.
Test with real contracts.

Interview angle

Questions: "How is classic SD revenue recognition configured?", "What happens to it in S/4HANA?", "How do you migrate?"
Strong answer: item category indicators, deferred/unbilled accounts, VF44/VF45, tables; not supported in S/4HANA; move to RAR with open item migration and reconciliation.

Practice this lesson

Quick check

1. In classic ECC SD revenue recognition, which object controls whether an item uses revenue recognition?

2. Which balances must be reconciled when migrating classic SD revenue recognition?

3. Which transaction posted revenue in classic ECC SD revenue recognition?

Interview questions

1. Suppose you inherit an existing Revenue Recognition solution. How would you review it before making a change?

Answer it in your own words first, then compare.

2. How do you configure revenue account determination (VKOA) to ensure correct posting to FI-AR when integrating with revenue recognition scenarios like event-based revenue recognition in S/4HANA?