Search Results gl_ledger_set_norm_assign_pk

Overview

GL_LEDGER_SET_NORM_ASSIGN is a General Ledger (GL) intersection table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model that stores ledger set assignments. It defines the many-to-many relationship between a ledger set and the individual ledgers or ledger sets that are members of that set. Each row associates one LEDGER_SET_ID with one LEDGER_ID, so the table functions as the membership roster underlying the Ledger Set feature. Ledger sets allow multiple ledgers sharing the same chart of accounts and accounting calendar to be processed, reported, and consolidated as a single logical grouping, and this table captures that grouping.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a link table. It resolves a relationship between two entities that both reference GL_LEDGERS, and carries no independent descriptive payload beyond its audit, effective-dating, and descriptive-flexfield columns. The classification is a modeling suggestion rather than an Oracle-mandated label.

Key Information Stored

• LEDGER_SET_ID — Identifies the ledger set (the parent container). Part of the composite primary key and a foreign key to GL_LEDGERS.
• LEDGER_ID — Identifies the member ledger or ledger set assigned into the set. Also part of the composite primary key and a foreign key to GL_LEDGERS.
• STATUS_CODE — Controls the active/inactive state of the assignment, governing whether the member ledger is treated as part of the set.
• START_DATE, END_DATE — Effective-dating columns that define the active window for the assignment, supporting date-effective membership.
• CREATION_DATE, CREATED_BY — Standard WHO audit columns recording row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent change and the login session.
• REQUEST_ID — Ties the row to the concurrent request that created or modified it, useful for batch-load tracing.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments reserved for customer-defined extensions.

The surrogate primary key is the composite GL_LEDGER_SET_NORM_ASSIGN_PK over (LEDGER_SET_ID, LEDGER_ID), which enforces uniqueness of each membership pairing. There is no documented alternate unique index, so the composite key itself serves as the business-key candidate for the assignment.

Common Use Cases and Queries

Typical use cases include reporting ledger set membership, resolving which ledgers roll into a given set for consolidation, and validating effective-dated assignments. A representative query returning active members for a ledger set is:

• SELECT a.LEDGER_ID FROM GL.GL_LEDGER_SET_NORM_ASSIGN a WHERE a.LEDGER_SET_ID = :p_ledger_set_id AND a.STATUS_CODE = 'A';
• Joining to GL_LEDGERS to retrieve ledger names and short names for the members of a set.
• Filtering on START_DATE/END_DATE to reproduce membership as of a given accounting period.
• Auditing changes by LAST_UPDATED_BY or tracing loads through REQUEST_ID.

Because both key columns reference GL_LEDGERS, membership joins must account for the possibility that a member is itself a ledger set, a characteristic of nested ledger set definitions.

Related Objects

• GL_LEDGERS — Referenced twice: GL_LEDGER_SET_NORM_ASSIGN.LEDGER_SET_ID → GL_LEDGERS and GL_LEDGER_SET_NORM_ASSIGN.LEDGER_ID → GL_LEDGERS.
• GL_LEDGER_SET_NORM_ASSIGN_PK — The primary key constraint enforcing unique (LEDGER_SET_ID, LEDGER_ID) pairings.
• Ledger set definition tables in the GL schema that store set names and attributes referenced by LEDGER_SET_ID.
• General Ledger standard APIs and concurrent programs that read and maintain ledger set membership during set maintenance.
• Consolidation and reporting components that consume ledger set membership to aggregate balances across member ledgers.

Together these objects form the ledger set framework, with GL_LEDGER_SET_NORM_ASSIGN acting as the definitive mapping between sets and their constituent ledgers.