Search Results gl_access_set_ledgers




Overview
Explore in AI Chat

Overview

GL_ACCESS_SET_LEDGERS is a General Ledger configuration table in the APPS schema that maps individual ledgers to the access sets defined in Oracle EBS. An access set is a named grouping of ledgers and ledger sets that determines which ledgers a responsibility, user, or application can read and post to. The GL_ACCESS_SET_LEDGERS table supplies the ledger-level membership and privilege detail for each access set, making it the authoritative source for ledger assignment and privilege scope within the General Ledger security model.

Under the heuristic Data Vault classification supplied in the ETRM metadata, this object is modeled as standalone. It is effectively a link (junction) table whose foreign key ACCESS_SET_ID points to GL_ACCESS_SETS, with LEDGER_ID resolving to the ledger definition. It carries descriptive attributes such as privilege code and effective dates, giving it a lightweight link-with-attributes shape rather than a pure satellite. This classification is a modeling suggestion; in the EBS native schema it is a standard relational intersection table.

Key Information Stored

The table contains 10 documented columns. The most significant are:

  • ACCESS_SET_ID — Foreign key to GL_ACCESS_SETS; identifies the access set to which the ledger assignment belongs. Together with LEDGER_ID and ACCESS_PRIVILEGE_CODE, it forms the unique business key.
  • LEDGER_ID — Identifies the ledger being granted to the access set. This is the operational link to the ledger definition.
  • ACCESS_PRIVILEGE_CODE — Defines the level of access granted (for example, read versus read/write/post) for the ledger within that access set.
  • START_DATE and END_DATE — Define the effective date range during which the ledger assignment is active.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created, updated, and last accessed the row.

The unique index GL_ACCESS_SET_LEDGERS_U1 on (ACCESS_SET_ID, LEDGER_ID, ACCESS_PRIVILEGE_CODE) enforces the business-key uniqueness, distinct from any single-column surrogate key. There is no separate documented surrogate primary key column beyond these.

Common Use Cases and Queries

Typical scenarios include reporting which ledgers are visible to a given responsibility, auditing ledger privilege assignments, and troubleshooting "ledger not accessible" errors. A common query joins the table to GL_ACCESS_SETS and the ledger definitions:

  • List all ledgers and privileges for a named access set, filtering by effective dates.
  • Determine which access sets include a specific LEDGER_ID, to trace responsibility access.
  • Audit rows where END_DATE has passed or is null, to detect stale assignments.
  • Reconcile security changes during period-close or multi-ledger consolidation projects.

A representative pattern:

SELECT l.ledger_id, l.name, asl.access_privilege_code, asl.start_date, asl.end_date FROM gl_access_set_ledgers asl, gl_access_sets a, gl_ledgers l WHERE asl.access_set_id = a.access_set_id AND asl.ledger_id = l.ledger_id AND a.name = :access_set_name;

Related Objects

The principal related objects are:

  • GL_ACCESS_SETS — Parent access set definition; joined on ACCESS_SET_ID.
  • GL_LEDGERS — Ledger master; joined on LEDGER_ID.
  • GL_LEDGER_SETS — Broader ledger grouping used alongside access sets.
  • GL_ACCESS_SET_LEDGER_SETS — Sibling table that assigns ledger sets rather than individual ledgers.
  • FND_RESPONSIBILITY and access-set assignment tables linking responsibilities to access sets.

These objects collectively govern ledger visibility and posting authority across Oracle General Ledger responsibilities.