FI / FICOadvanced

FICO FI Integration Part 5: FI-SD Revenue Account Determination and Posting Errors

Key takeaway

Configure and troubleshoot SD-to-FI postings: account determination procedure (KOFI), condition tables and access sequence, account assignment groups for customers and materials, account keys (ERL, ERS, ERF, MWS), billing documents not released to accounting, and common errors.

Explanation

📌 KEY POINTS
✅ Revenue accounts are found with the condition technique: account determination type (e.g. KOFI) and access sequence.
✅ Keys: application, condition type, chart of accounts, sales org, customer and material account assignment groups, account key.
✅ Pricing procedure assigns account keys to conditions (ERL revenue, ERS discounts, ERF freight, MWS tax).
✅ Billing documents with errors are not released (VFX3) — analyse the error log.
⚠️ Missing account assignment groups in customer/material master are the most common cause of release errors.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered strategy. Now SD-FI depth.

━━━━━━━━━━━━━━━━━━━━
▶ 1. CONDITION TECHNIQUE

KOFI, access sequence, tables.

━━━━━━━━━━━━━━━━━━━━
▶ 2. MASTER DATA

Customer AAG (billing tab), material AAG (sales org data).

━━━━━━━━━━━━━━━━━━━━
▶ 3. ACCOUNT KEYS

ERL, ERS, ERF, MWS in pricing procedure.

━━━━━━━━━━━━━━━━━━━━
▶ 4. RELEASE ERRORS

VFX3, error log, account determination analysis.

━━━━━━━━━━━━━━━━━━━━
▶ 5. FIXES

Maintain VKOA or master data; release billing.

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

Review VKOA entries.
Bill a document with a new material group.
Analyse and fix release errors.

✅ CHECKPOINT: billing releases with correct revenue accounts.

Code example

ABAP Code

===== VKOA STRUCTURE =====Application V | condition type KOFI | chart INT | sales org 1000 | customer AAG 01 (domestic) | material AAG 10 (goods) | account key ERL → 800000 revenueERS → 880000 discounts | ERF → 810000 freight revenue | MWS → tax (via tax account determination) ===== ERRORS =====VFX3 blocked billing → "account determination error" → check AAGs and VKOA → release

Real project scenario

A retail client onboarded a new business unit; billing documents failed release because customers lacked account assignment groups. Mass-maintaining the field and making it mandatory in customer creation solved it.

Common mistakes

Generic VKOA entries.
Missing AAGs.
Ignoring VFX3.
Wrong account keys in pricing.
No testing for new groups.

Best practices

Specific entries.
Mandatory AAGs.
Monitor VFX3 daily.
Validate pricing keys.
Test new groups.

Interview angle

Questions: "How is revenue account determined?", "What are account keys?", "Why is billing not released to accounting?"
Strong answer: condition technique, AAGs, account keys, release errors, fixes.

Practice this lesson

Quick check

1. A billing document is released to Accounting from SD, and document splitting is active. What is the primary purpose of document splitting in this integration scenario?

2. After onboarding a new business unit, billing documents aren't released to accounting. What is the most likely cause?

3. When integrating SD billing documents with FI, which configuration object uses the condition technique to determine which G/L accounts (e.g., revenue, discount, tax) should be posted to?

Interview questions

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

Answer it in your own words first, then compare.

2. Billing documents for a new product line aren't released to accounting. Walk through your FI-SD troubleshooting.