FI / FICOintermediate

FICO Universal Journal Part 3: Extension Ledgers, Additional Currencies and Custom Fields

Key takeaway

Extend the universal journal without copying data: extension ledgers that store only delta postings on top of a base ledger, freely defined additional currencies, and custom fields added to the coding block so they flow into ACDOCA and reports.

Explanation

📌 KEY POINTS
✅ An extension ledger stores only adjustments on top of an underlying ledger; reports combine both.
✅ Use extension ledgers for management adjustments, simulations or different valuation views.
✅ Additional (freely defined) currencies can be added per ledger for reporting needs.
✅ Custom fields can be added to the coding block and ACDOCA using key-user extensibility.
⚠️ Extension ledgers are not full ledgers — they don't support every business process (e.g. not all sub-ledger postings).

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 configured standard ledgers. Now extensions.

━━━━━━━━━━━━━━━━━━━━
▶ 1. EXTENSION LEDGERS

Base ledger + delta postings; manual or allocation postings only.

━━━━━━━━━━━━━━━━━━━━
▶ 2. USE CASES

Management adjustments, simulation, reclassifications for reporting.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ADDITIONAL CURRENCIES

Freely defined currencies per ledger; conversion rules.

━━━━━━━━━━━━━━━━━━━━
▶ 4. CUSTOM FIELDS

Add to coding block (journal entry item) → available in postings and analytics.

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

Clear purpose per extension; reporting that combines ledgers correctly.

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

Create an extension ledger on 0L in a sandbox.
Post a management adjustment only to it.
Report 0L alone and 0L + extension.

✅ CHECKPOINT: the adjustment appears only in the combined view.

Code example

ABAP Code

===== CONFIG MAP =====Extension ledger ........ FINSC_LEDGER: ledger type "Extension Ledger", underlying ledger 0LAdditional currencies ... Currency settings per ledger and company codeCustom fields ........... Fiori "Custom Fields" app → business context: Accounting: Coding Block ===== EXAMPLE =====0L: revenue 1,000 | Extension ledger EX1: management reclass −100 → Report 0L+EX1 = 900

Real project scenario

A global manufacturing group needed a management-only allocation view without duplicating data. An extension ledger on 0L carried allocation deltas; management reports read 0L plus the extension while statutory reports read 0L only.

Common mistakes

Using standard ledgers for simple adjustments.
Custom fields without fill logic.
Reporting extension ledgers alone.
No ownership of extension postings.
Too many currencies.

Best practices

Choose extension ledgers for deltas.
Define custom field derivation.
Document ledger purposes.
Control who posts to extensions.
Add currencies only for real needs.

Interview angle

Questions: "What is an extension ledger?", "When use it instead of a standard ledger?", "How do you add a custom field to ACDOCA?"
Strong answer: delta concept, use cases and limits, additional currencies, coding block extensibility, governance.

Practice this lesson

Quick check

1. A custom field was added to the coding block but stays empty in postings. What is missing?

2. A group needs a management-only allocation view without duplicating data. What fits best?

3. What does an extension ledger store?

Interview questions

1. What are the most important design decisions, trade-offs, and best practices in Universal Journal?

Answer it in your own words first, then compare.

2. Management wants an extra reporting attribute (e.g. sales channel) on all journal entries and a separate view for adjustments. How do you deliver it?