Search Results gl_ledger_set_assignments_pk

Overview

GL_LEDGER_SET_ASSIGNMENTS is a General Ledger (GL) table in the Oracle E-Business Suite 12.1.1 / 12.2.2 schema owned by GL. Its documented description is "Flattened ledger set assignments." It stores the resolved mapping between a ledger set and the individual ledgers that belong to it, expanding the hierarchical membership of a ledger set into explicit, row-level assignments. This flattened representation allows applications and reports to determine quickly and unambiguously which ledgers constitute a given ledger set without traversing intermediate set hierarchies.

Under the heuristic Data Vault classification mined from its foreign-key structure, this table is modeled as a link. That classification is a modeling suggestion: the table has no natural descriptive payload of its own and exists to associate two principal entities (ledger sets and ledgers) that are both resolved through GL_LEDGERS. It is therefore best treated as an associative (junction) artifact rather than a hub or satellite.

Key Information Stored

The physical schema documented in ETRM 12.2.2 contains ten columns. The primary key, GL_LEDGER_SET_ASSIGNMENTS_PK, is composite and defined over two columns:

• LEDGER_SET_ID — identifies the ledger set to which the assignment belongs; also a foreign key to GL_LEDGERS.
• LEDGER_ID — identifies the individual ledger assigned to that set; also a foreign key to GL_LEDGERS.

Together LEDGER_SET_ID and LEDGER_ID form the surrogate/composite primary key and are the business-key candidates that uniquely identify each assignment row. The remaining documented columns capture effective dating, status, and standard EBS audit attributes:

• START_DATE and END_DATE — effective-dating range for which the assignment is valid.
• STATUS_CODE — indicates the current state of the assignment record.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard "who/when last changed" audit columns.
• CREATION_DATE and CREATED_BY — standard record-creation audit columns.

Common Use Cases and Queries

Typical uses include resolving ledger-set membership for multi-ledger reporting, validating which ledgers roll up into a given set, and driving security or data-access logic across ledgers. A representative query lists the ledgers assigned to a set:

SELECT LEDGER_ID, LEDGER_SET_ID, START_DATE, END_DATE, STATUS_CODE
FROM   GL.GL_LEDGER_SET_ASSIGNMENTS
WHERE  LEDGER_SET_ID = :p_ledger_set_id
ORDER BY LEDGER_ID;

A reverse lookup finds every ledger set containing a given ledger:

SELECT LEDGER_SET_ID
FROM   GL.GL_LEDGER_SET_ASSIGNMENTS
WHERE  LEDGER_ID = :p_ledger_id
AND    (STATUS_CODE IS NULL OR STATUS_CODE = 'A');

Effective-dated reporting can filter on the date range using START_DATE and END_DATE against the desired as-of date.

Related Objects

The documented foreign keys both point to GL_LEDGERS, which is the central object in this relationship:

• GL_LEDGERS — referenced twice: GL_LEDGER_SET_ASSIGNMENTS.LEDGER_SET_ID → GL_LEDGERS and GL_LEDGER_SET_ASSIGNMENTS.LEDGER_ID → GL_LEDGERS.
• GL_LEDGER_SET_ASSIGNMENTS_PK — the composite primary key constraint over (LEDGER_SET_ID, LEDGER_ID).
• GL_LEDGER_SETS (ledger set definition, by convention) — provides the ledger-set header resolved via LEDGER_SET_ID.
• GL_LEDGER_SET_NORM_ASSIGNMENTS (normalized assignments, by convention) — the non-flattened counterpart used during resolution.
• GL_LEDGERS / GL_LEDGER_CONFIGURATIONS — support ledger-level attributes used in assignment validation and reporting.

Because the table is a pure link between ledger-set and ledger identifiers, any application logic or report that needs flattened ledger-set membership should join through LEDGER_SET_ID and LEDGER_ID rather than querying it in isolation.