FI / FICOarchitect

FICO Universal Journal Part 4: Migration, Extensibility and Long-Term Governance

Key takeaway

Architect the move to the universal journal: the finance data migration steps in a conversion, reconciliation before and after, decisions on ledgers, currencies and document splitting, custom code impact, and the governance that keeps ACDOCA clean over years.

Explanation

📌 KEY POINTS
✅ In a conversion, finance data is migrated into ACDOCA in defined steps (cost elements, line items, balances, assets, material ledger) with reconciliation checks.
✅ Close all open issues before: period close complete, reconciliation clean, asset and ML data consistent.
✅ Decide ledgers, currencies and document splitting before the project baseline — later changes are expensive.
✅ Custom code reading old tables must be adapted; prefer released CDS views.
⚠️ Skipping pre-checks moves inconsistencies into ACDOCA, where they are much harder to fix.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 3 extended ACDOCA. Now migration and governance.

━━━━━━━━━━━━━━━━━━━━
▶ 1. PRE-CONVERSION

Readiness checks, simplification items, finance consistency checks, clean period close.

━━━━━━━━━━━━━━━━━━━━
▶ 2. FINANCE DATA MIGRATION

Guided steps: migrate cost elements, enrich and migrate line items, balances, assets, material ledger; reconcile each.

━━━━━━━━━━━━━━━━━━━━
▶ 3. DESIGN DECISIONS

Ledgers, currencies, document splitting (often a later subsequent implementation), new asset accounting.

━━━━━━━━━━━━━━━━━━━━
▶ 4. CUSTOM CODE AND REPORTS

ATC findings; replace totals-table logic with CDS-based reporting.

━━━━━━━━━━━━━━━━━━━━
▶ 5. GOVERNANCE

Master data rules for dimensions, ownership of custom fields and extension ledgers, change control.

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

Run readiness and finance consistency checks.
Execute migration in a sandbox and reconcile.
Fix root causes, repeat mocks.

✅ CHECKPOINT: balances before and after migration match per ledger, company code and account.

Code example

ABAP Code

===== CONVERSION FLOW (simplified) =====Readiness check → simplification item checks → custom code analysis (ATC)Pre-checks in ECC: close period, reconcile FI/CO/AA/MLTechnical conversion (SUM) → finance data migration steps → reconciliation reports → sign-off ===== GOVERNANCE CHECKLIST =====Ledger & currency owner | dimension derivation rules | custom field owners | extension ledger usage policy

Real project scenario

A multinational manufacturer doing a phased S/4HANA rollout found asset and GL balances differed in the first mock conversion. Root cause: old manual postings to asset reconciliation accounts. Correcting them in ECC and adding a pre-check to the runbook made the second mock reconcile cleanly.

Common mistakes

Skipping mock conversions.
Late ledger decisions.
Ignoring custom code on totals tables.
No reconciliation sign-off.
Unowned custom fields.

Best practices

Run multiple mocks.
Decide design early.
Adapt code to CDS views.
Reconcile and sign off.
Govern extensions.

Interview angle

Questions: "How is finance data migrated to ACDOCA?", "What must be clean before conversion?", "How do you govern the universal journal?"
Strong answer: readiness and consistency checks, migration steps with reconciliation, early design decisions, custom code, governance.

Practice this lesson

Quick check

1. What should be done before converting finance data to the universal journal?

2. Why prefer released CDS views for custom finance reports after conversion?

3. First mock conversion shows GL and asset balances differing. What is the right approach?

Interview questions

1. A multinational is converting ECC to S/4HANA in phases. How do you plan the finance data migration to the universal journal?

Answer it in your own words first, then compare.

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