Search Results igi_cbr_primary_ledger_v

Overview

APPS.GL_ACCESS_SET_LEDGERS is a General Ledger security assignment table in Oracle E-Business Suite (R12.1.1 and R12.2.2) that maps a General Ledger Access Set to the individual ledgers (and ledger sets) it controls, together with the privilege level granted for each. It is the junction entity that gives an access set its meaning: without rows in this table, an access set has no ledgers under its scope. The FND Design Data reference is SQLGL.GL_ACCESS_SET_LEDGERS and the object resides in the APPS_TS_SUMMARY tablespace with PCT FREE 10. The table is classified as VALID in the ETRM repository for release 12.2.2.

From a Data Vault modeling perspective, the metadata's heuristic classification is standalone, meaning the object is not treated as a strict hub, link, or satellite within the mined foreign-key structure. In practice, however, the table behaves as a link-style association resolving the many-to-many relationship between GL_ACCESS_SETS and GL_LEDGERS, with START_DATE and END_DATE lending it a satellite-like temporal quality.

Key Information Stored

The table contains 10 documented columns. The critical business columns are:

• ACCESS_SET_ID — Foreign key to APPS.GL_ACCESS_SETS; identifies the access set to which the ledger assignment belongs. This is the only documented FK relationship.
• LEDGER_ID — The ledger (or ledger set) made visible through the access set.
• ACCESS_PRIVILEGE_CODE — The privilege granted, typically distinguishing read versus read/write (entry) access to the ledger.
• START_DATE and END_DATE — Effective dating that bounds the validity of the assignment, permitting historical or future-dated security changes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns used for audit and concurrency control.

The unique index GL_ACCESS_SET_LEDGERS_U1 — the object the user searched for — is defined on (ACCESS_SET_ID, LEDGER_ID, ACCESS_PRIVILEGE_CODE). This is the business-key candidate that guarantees a given access set cannot hold duplicate privilege rows for the same ledger. It is a NORMAL, UNIQUE index located in APPS_TS_SUMMARY, and it is the index most frequently hit by security-resolution queries at runtime.

Common Use Cases and Queries

The most common use is resolving which ledgers a user may access after access sets are assigned to responsibilities and users. A typical reporting query joins the table back to its parent:

• List all ledgers in a given access set: SELECT ledger_id, access_privilege_code FROM gl_access_set_ledgers WHERE access_set_id = :id.
• Find access sets containing a specific ledger: SELECT access_set_id FROM gl_access_set_ledgers WHERE ledger_id = :ledger.
• Audit effective-dated privileges using START_DATE and END_DATE against SYSDATE.
• Reconcile orphaned assignments by verifying ACCESS_SET_ID exists in GL_ACCESS_SETS.
• Performance diagnostics on the GL_ACCESS_SET_LEDGERS_U1 index when security checks are slow.

Because the row set is small and highly cached, this table is rarely a bottleneck, but incorrect or duplicate rows directly affect data visibility in journals, consolidation, and reporting.

Related Objects

The table is referenced by a broad set of GL, financial-vault, and localization objects:

• GL_ACCESS_SETS — parent table via ACCESS_SET_ID.
• GL_ACCESS_SET_LEDGERS_V and GL_ACCESS_SET_SECURITY_PKG — view and package providing the functional security API.
• GL_SECURITY_PKG and GL_PERIOD_STATUSES_PKG — runtime security resolution logic.
• GLXJEENT_PKG — journal entry validation that honors ledger-level privileges.
• Financial-vault views FV_FACTS_TB_V, FV_FACTS_TRX_V, and FV_TBAL_BY_TS_V.
• Subledger and consolidation views such as GL_JE_BATCHES_POST_V, GL_CONSOLIDATION_HISTORY_V, and IGI_CBR_PRIMARY_LEDGER_V.