Search Results gl_asl

Overview

APPS.GL_ACCESS_SET_LEDGERS_V is a General Ledger (GL) view that presents the relationship between General Ledger access sets and the ledgers assigned to them. In Oracle EBS Release 12.1.1 and 12.2.2, an access set is a security and data-access construct that groups one or more ledgers and ledger sets so that specific responsibilities and users can access only the accounting data they are authorized to work with. This view bridges the access set definition (via GL_ACCESS_SET_LEDGERS) with descriptive ledger attributes (via GL_LEDGERS), producing a denormalized result that is convenient for reporting, integration, and security auditing.

The view exposes the access privilege code, effective date range, and standard audit columns, alongside descriptive fields such as the ledger name, currency code, and object type code. It is commonly used by reports, concurrent programs, and custom integrations that need to answer the question: "Which ledgers belong to which access set, and with what privilege?"

Underlying Base Objects

The view is defined over two documented base objects:

• GL_ACCESS_SET_LEDGERS (TABLE) — the core assignment table that records which ledger is associated with a given access set, including the access privilege and effective start/end dates.
• GL_LEDGERS (SYNONYM) — provides ledger descriptive and control attributes such as the ledger name, currency code, and object type code.

The join is performed on LEDGER_ID. The view text aliases GL_ACCESS_SET_LEDGERS as GL_ASL and GL_LEDGERS as LDG:

FROM gl_access_set_ledgers gl_asl, gl_ledgers ldg
WHERE gl_asl.ledger_id = ldg.ledger_id

Because the driving table is GL_ACCESS_SET_LEDGERS, the view returns one row for each ledger-to-access-set assignment that has a matching ledger definition. The ROWID of the GL_ACCESS_SET_LEDGERS row is surfaced as ROW_ID, and the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are carried through from the assignment table.

Key Columns

• ROW_ID — The ROWID of the underlying GL_ACCESS_SET_LEDGERS row, useful for identifying the physical assignment record.
• ACCESS_SET_ID — Identifier of the access set to which the ledger is assigned.
• LEDGER_ID — Identifier of the ledger that belongs to the access set. This is the join key to GL_LEDGERS.
• LEDGER_NAME — Descriptive name of the ledger, sourced from GL_LEDGERS.NAME.
• CURRENCY_CODE — Functional/ledger currency of the ledger, from GL_LEDGERS.CURRENCY_CODE.
• OBJECT_TYPE_CODE — Indicates whether the ledger is a primary ledger or a secondary ledger (or similar object designation), from GL_LEDGERS.OBJECT_TYPE_CODE.
• ACCESS_PRIVILEGE_CODE — The privilege granted for the ledger within the access set (for example, read or read/write style privileges).
• START_DATE / END_DATE — The effective date range during which the ledger assignment is valid within the access set.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture standard Oracle EBS WHO information for the assignment record.

Common Use Cases and Queries

The view is widely used for security analysis, data-access troubleshooting, and building pick lists of accessible ledgers. A typical query listing all ledgers for a given access set is:

SELECT access_set_id, ledger_id, ledger_name,
       currency_code, object_type_code,
       access_privilege_code, start_date, end_date
FROM   apps.gl_access_set_ledgers_v
WHERE  access_set_id = :p_access_set_id
ORDER BY ledger_name;

A second common pattern identifies which access sets reference a particular ledger:

SELECT access_set_id, ledger_name, access_privilege_code
FROM   apps.gl_access_set_ledgers_v
WHERE  ledger_id = :p_ledger_id;

Because the view joins the assignment and ledger-definition tables, it is a convenient single source for reports that must display meaningful ledger names alongside access-set grants, avoiding the need for custom joins in reporting or integration code. Analysts also use it to review effective-dated assignments and privilege levels when diagnosing why a user or responsibility can or cannot see a given ledger's data in General Ledger.