Results for “default_ledger_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_ACCESS_SETS is a General Ledger (GL) schema table that stores data access set definitions within Oracle E-Business Suite. A data access set determines which ledgers and balancing segment values a responsibility or user can access, and controls the read and write privileges granted against those ledgers. First introduced with the Subledger Accounting and Multi-Organization Access Control architecture, data access sets are central to the security and reporting model of the GL module in both release 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the mined foreign key structure classifies GL_ACCESS_SETS as hub-leaning. This suggests it be treated as a reference or hub entity in a Data Vault design, with its surrogate key distributed to dependent transactional and history tables rather than carrying foreign keys outward to many parents. The table holds a single documented inbound reference to GL_MGT_SEG_UPGRADE_H, reinforcing its role as a relatively stable definition entity.

Key Information Stored

The table is documented with 32 columns. The most significant are:

• ACCESS_SET_ID — the surrogate primary key (GL_ACCESS_SETS_PK) and the value propagated to dependent tables as a foreign key.
• NAME — the business identifier of the access set; enforced unique by index GL_ACCESS_SETS_U2.
• DESCRIPTION — free-text description of the access set purpose.
• SECURITY_SEGMENT_CODE — identifies which accounting segment is secured by the access set.
• ENABLED_FLAG — indicates whether the access set is active and assignable.
• CHART_OF_ACCOUNTS_ID — the chart of accounts to which the secured segment belongs; documented as referencing GL_MGT_SEG_UPGRADE_H.
• SECURED_SEG_VALUE_SET_ID — the value set that defines the secured segment values.
• DEFAULT_LEDGER_ID — the ledger used by default when the access set is applied.
• PERIOD_SET_NAME and ACCOUNTED_PERIOD_TYPE — the accounting calendar characteristics associated with the access set.
• AUTOMATICALLY_CREATED_FLAG — distinguishes system-generated access sets from user-defined ones.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns for extensibility.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Note that GL_ACCESS_SETS_U1 enforces uniqueness on ACCESS_SET_ID while GL_ACCESS_SETS_U2 enforces uniqueness on NAME, making NAME a business-key candidate distinct from the surrogate key.

Common Use Cases and Queries

Typical scenarios involve auditing ledger security, resolving which ledgers a responsibility can reach, and reconciling implicit access sets assigned to ledgers. A common reporting pattern joins access sets to their default ledger:

• Listing enabled access sets and their secured segment: SELECT access_set_id, name, security_segment_code, enabled_flag FROM gl_access_sets WHERE enabled_flag = 'Y';
• Resolving the access set applied to a ledger via GL_LEDGERS.IMPLICIT_ACCESS_SET_ID.
• Identifying automatically created access sets versus manually maintained ones using AUTOMATICALLY_CREATED_FLAG.
• Validating the calendar configuration of an access set through PERIOD_SET_NAME and ACCOUNTED_PERIOD_TYPE.
• Tracing allocation history back to the originating access set through GL_AUTO_ALLOC_SET_HISTORY and GL_ALLOC_HISTORY.

Related Objects

The following objects reference or are referenced by GL_ACCESS_SETS through documented foreign keys:

• GL_LEDGERS — joined via GL_LEDGERS.IMPLICIT_ACCESS_SET_ID = GL_ACCESS_SETS.ACCESS_SET_ID; expresses the implicit access set assigned to a ledger.
• GL_AUTO_ALLOC_SET_HISTORY — joined via ACCESS_SET_ID; captures historical allocation set assignments.
• GL_ALLOC_HISTORY — joined via ACCESS_SET_ID; records allocation runs tied to an access set.
• GL_MGT_SEG_UPGRADE_H — referenced by GL_ACCESS_SETS.CHART_OF_ACCOUNTS_ID, supporting management segment upgrade processing.
• GL_ACCESS_SET_LEDGERS and the Data Access Set setup UI — the child assignment structure and form used to maintain ledger and balancing segment privileges.