Results for “fii_source_ledger_groups”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FII_SOURCE_LEDGER_GROUPS is a Financial Intelligence (FII) reference table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definitions of source ledger groups, where each group carries a name, description, and an intended usage classification. In the FII architecture, this table acts as the master registry that governs how sets of source ledgers are organized and consumed by downstream financial consolidation, budgeting, and reporting processes.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as standalone based on its foreign key structure. This heuristic indicates that FII_SOURCE_LEDGER_GROUPS is a self-contained reference entity rather than a true hub, link, or satellite in a conventional Data Vault sense. It can nevertheless be treated as a source for a hub-style construct keyed on SOURCE_LEDGER_GROUP_ID, or as a reference/satellite-style table for descriptive attributes such as NAME, DESCRIPTION, and USAGE_CODE.

Key Information Stored

The table is owned by the FII schema and contains ten documented columns. The most significant include:

• SOURCE_LEDGER_GROUP_ID — the surrogate primary key, uniquely identifying each source ledger group. It is enforced by the FII_SOURCE_LEDGER_GROUPS_PK constraint and also appears in the unique index FII_SOURCE_LEDGER_GROUPS_U1.
• NAME — the business-facing identifier of the group, enforced by the unique index FII_SOURCE_LEDGER_GROUPS_U2. This makes NAME a business-key candidate alongside the surrogate ID.
• USAGE_CODE — indicates the intended usage of the group, distinguishing how the group is applied across FII functionality.
• DESCRIPTION — a free-text field describing the purpose or scope of the group.
• STATUS_CODE — the lifecycle or activation state of the ledger group definition.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO (audit) columns capturing creation and modification metadata.

Common Use Cases and Queries

Typical queries retrieve the set of active source ledger groups or resolve a group by name. For example, to list all groups with their usage and status:

• SELECT source_ledger_group_id, name, usage_code, status_code FROM fii.fii_source_ledger_groups WHERE status_code = 'A';
• SELECT * FROM fii.fii_source_ledger_groups WHERE name = :group_name;
• SELECT g.name, a.source_ledger_group_id FROM fii.fii_source_ledger_groups g JOIN fii.fii_slg_budget_asgns a ON g.source_ledger_group_id = a.source_ledger_group_id;

These are commonly used in budget assignment reporting, validation of ledger group configuration, and auditing which groups have been assigned to budget processes.

Related Objects

The principal dependent object documented is FII_SLG_BUDGET_ASGNS, which references FII_SOURCE_LEDGER_GROUPS via SOURCE_LEDGER_GROUP_ID. This child table records the assignment of source ledger groups to budget constructs, making FII_SOURCE_LEDGER_GROUPS the parent lookup for those assignments. Reporting queries frequently join these two tables on SOURCE_LEDGER_GROUP_ID to surface both the group definition and its budget linkage. No further foreign keys are documented, consistent with the standalone classification.