FI / FICOadvanced

FICO Document Splitting Part 3: Runtime Flow, Zero-Balance Lines and Posting Errors

Key takeaway

Understand what happens at posting time — base item determination, active split, inheritance, defaults, passive split and zero-balance clearing — and troubleshoot the typical errors: missing mandatory characteristic, unbalanced segment, unassignable items and wrong document type classification.

Explanation

📌 KEY POINTS
✅ Runtime order: classify items → determine base items → split according to rule → inheritance → defaults → zero-balance lines.
✅ "Balancing field profit center/segment not filled" means a mandatory characteristic is empty after all steps.
✅ Unbalanced segments are fixed automatically only if zero balance is set for that characteristic.
✅ Simulate the general ledger view to see split lines before posting.
⚠️ Do not fix errors by removing the mandatory flag — find why the line had no assignment.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 configured splitting. Now runtime and support.

━━━━━━━━━━━━━━━━━━━━
▶ 1. RUNTIME FLOW

Item categories → base items → split → inherit → default → zero balance.

━━━━━━━━━━━━━━━━━━━━
▶ 2. TYPICAL ERRORS

Mandatory characteristic missing; wrong doc type variant; account not classified.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ANALYSIS

Simulate GL view; check classification of account and document type; check rule.

━━━━━━━━━━━━━━━━━━━━
▶ 4. CORRECTIONS

Fix master data (cost center → profit center), classification, or enter assignment on the line.

━━━━━━━━━━━━━━━━━━━━
▶ 5. PREVENTION

Validations on P&L lines; regression tests after configuration changes.

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

Reproduce the error in QA.
Simulate GL view; identify the unassigned line.
Check account/doc type classification and master data.
Fix and retest.

✅ CHECKPOINT: error cause documented with prevention.

Code example

ABAP Code

===== RUNTIME FLOW =====1 Classify items (item categories) → 2 Base items (expense/revenue) → 3 Active split per rule→ 4 Inheritance → 5 Default account assignment → 6 Zero-balance clearing lines ===== COMMON ERRORS → FIX ====="Balancing field Profit Center in line item … not filled" → missing cost object / defaultUnassignable document type → classify doc type to business transaction variantAccount without item category → classify GL account

Real project scenario

Month-end reclass journals failed with "balancing field segment not filled" because a new balance sheet account was not classified for splitting. Classifying the account and adding a checklist step for new accounts ended the errors.

Common mistakes

Removing mandatory flags.
Changing rules in production.
Not simulating.
Ignoring new accounts' classification.
No regression tests.

Best practices

Simulate GL view.
Classify new accounts/doc types.
Validate cost objects.
Regression test changes.
Document fixes.

Interview angle

Questions: "Walk through runtime splitting", "Why does 'balancing field not filled' occur?", "How do you troubleshoot splitting?"
Strong answer: runtime steps, error causes, analysis with simulation, fixes and prevention.

Practice this lesson

Quick check

1. A posting fails with "balancing field Profit Center not filled". What should you check first?

2. What is achieved by defining a "default account assignment" for a splitting characteristic in document splitting configuration?

3. Why is it necessary to assign a zero-balance clearing account in the document splitting configuration?

Interview questions

1. A production issue is reported in Document Splitting. What would you check first, and how would you troubleshoot it systematically?

Answer it in your own words first, then compare.

2. Suppose you inherit an existing Document Splitting solution. How would you review it before making a change?