Search Results fii_ou_ledger_v

Overview

FII_OU_LEDGER_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Financial Intelligence (FII) product family. It exposes a lightweight mapping between a ledger, the ledger's functional currency, and the operating unit associated with the legal-entity accounting context. The view is documented in ETRM as VALID and present in both 12.1.1 and 12.2.2 environments. Its purpose, per the FII documentation, is to "contain information about the Currency corresponding to a Ledger" — a frequent requirement in financial reporting, where a query must resolve a ledger identifier to its currency code without joining directly to the General Ledger tables.

In the EBS architecture, a ledger is defined and stored in GL_SETS_OF_BOOKS, and its currency is the functional currency used for all journal entries and balances in that ledger. The FII view surfaces that currency — the LEDGER_CURRENCY_CODE column — alongside the operating unit, enabling reporting and integration components to resolve currency context by operating unit in a single query. For the user search term ledger_currency_code, this view is the canonical FII access point: the column is named LEDGER_CURRENCY_CODE and maps directly to GL_SETS_OF_BOOKS.CURRENCY_CODE.

Underlying Base Objects

The view is defined over two base tables, as documented in the ETRM view text:

• GL_SETS_OF_BOOKS (alias SOB) — the source of the ledger identifier and currency code. The view selects SET_OF_BOOKS_ID and CURRENCY_CODE from this table. In 12.1.1 and 12.2.2, GL_SETS_OF_BOOKS functions as the ledger definition table, with SET_OF_BOOKS_ID acting as the ledger surrogate key.
• HR_ORGANIZATION_INFORMATION (alias ORGI) — the source of the operating unit association. The view filters on ORG_INFORMATION_CONTEXT = 'LEGAL ENTITY ACCOUNTING' and uses ORG_INFORMATION1 to carry the ledger identifier. The operating unit is captured through ORGANIZATION_ID.

The join between the two tables is expressed as SOB.SET_OF_BOOKS_ID = ORGI.ORG_INFORMATION1 (+), an outer join on the HR organization side, with an additional outer-join restriction on the ORG_INFORMATION_CONTEXT value. The outer join means ledgers without a matching legal-entity accounting organization record still appear, with a null OPERATING_UNIT_ID.

Key Columns

• LEDGER_ID — alias of GL_SETS_OF_BOOKS.SET_OF_BOOKS_ID. Uniquely identifies the ledger.
• LEDGER_CURRENCY_CODE — alias of GL_SETS_OF_BOOKS.CURRENCY_CODE. The ledger's functional currency (ISO 4217 code, e.g. USD, EUR, GBP). This is the column sought by the search term ledger_currency_code.
• OPERATING_UNIT_ID — alias of HR_ORGANIZATION_INFORMATION.ORGANIZATION_ID for the LEGAL ENTITY ACCOUNTING context. Associates the ledger to an operating unit; null when no such organization information exists.

Common Use Cases and Queries

The view is typically used to resolve ledger currency for a given operating unit, to enrich financial extracts with currency, and to validate currency assignments in reporting joins.

• Resolve currency by operating unit: SELECT operating_unit_id, ledger_id, ledger_currency_code FROM apps.fii_ou_ledger_v WHERE operating_unit_id = :p_ou;
• List all ledger currencies: SELECT ledger_id, ledger_currency_code FROM apps.fii_ou_ledger_v ORDER BY ledger_currency_code;
• Find ledgers without an operating unit: SELECT ledger_id, ledger_currency_code FROM apps.fii_ou_ledger_v WHERE operating_unit_id IS NULL;

Because the view contains only three columns and no aggregation, it is inexpensive to join to fact-style reporting queries. It should not be used to derive transaction currency; it returns the ledger functional currency only. Where multi-org security is required, callers should still apply MOAC filters, since this view does not itself enforce operating unit access.