Results for “access_set_id”

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

Overview

GL_ACCESS_SET_ASSIGNMENTS is a General Ledger reference table in the GL schema that stores the flattened privilege assignments associated with data access sets. A data access set defines the scope of financial data—particular ledgers, balancing segment values, and management segment values—that a user or responsibility may read or post against. Whereas the parent definition tables describe the access set at a summary level, GL_ACCESS_SET_ASSIGNMENTS materializes the effective, denormalized result: one row for each combination of access set, ledger, and segment value, together with the privilege granted. This flattened design allows the application to resolve security scope quickly at runtime without repeatedly traversing the hierarchical definition of the access set.

Under a heuristic Data Vault classification derived from its key structure, the table is modelled as a standalone object rather than as a hub, link, or satellite. This is a modelling suggestion only: the table behaves as a presentation or flattened privilege store whose composite key combines three business dimensions, and its properties are best approached operationally rather than as a normalized Data Vault construct.

Key Information Stored

The physical schema documented for 12.2.2 contains twelve columns, but a smaller subset carries the substantive meaning:

• ACCESS_SET_ID — identifies the data access set to which the assignment belongs; part of the primary key and the principal join back to the access set definition.
• LEDGER_ID — the ledger whose data is being granted; part of the primary key.
• SEGMENT_VALUE — the balancing or management segment value included in the grant; part of the primary key.
• ACCESS_PRIVILEGE_CODE — the privilege conveyed, typically distinguishing read-only access from read-and-write (post) access.
• PARENT_RECORD_ID — a self-referencing pointer that ties a flattened record back to the record from which it was derived, supporting regeneration of the flattened assignment set.
• START_DATE and END_DATE — the effective window during which the assignment is valid, enabling date-sensitive security evaluation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard Oracle EBS audit columns recording who created and last changed each row and when.

The surrogate primary key is GL_ACCESS_SET_ASSIGNMENTS_PK, defined over the composite of ACCESS_SET_ID, LEDGER_ID, and SEGMENT_VALUE. These three columns therefore also function as the business-key candidates, since the unique index that enforces the primary key is exactly the combination that identifies a distinct flattened privilege.

Common Use Cases and Queries

Typical uses include diagnosing why a user can or cannot post to a given ledger, and reporting the complete scope of a data access set for audit or segregation-of-duties review. A representative query enumerates the ledgers and segment values granted by an access set:

• Filter by ACCESS_SET_ID to list every LEDGER_ID and SEGMENT_VALUE assignment, ordered by ledger and segment, showing ACCESS_PRIVILEGE_CODE.
• Join to the access set definition tables on ACCESS_SET_ID to translate identifiers into descriptive names.
• Apply the effective-date predicate, comparing the current date to START_DATE and END_DATE, to return only currently active assignments.
• Count distinct LEDGER_ID values per access set to summarize breadth of access, or group by ACCESS_PRIVILEGE_CODE to distinguish read versus write scope.

Because the table is a flattened store, direct DML is not recommended; it is normally maintained through the standard access set definition and assignment processes in the General Ledger setup, so reporting queries should treat it as read-only.

Related Objects

The most significant dependencies relate to the data access set definition and to ledger and segment value reference data. Although the documented relationship data classifies the table as standalone, the following objects are the natural counterparts referenced through the key columns:

• Access set definition tables in the GL schema, joined on ACCESS_SET_ID, provide the header context for each flattened assignment.
• GL_LEDGERS, joined on LEDGER_ID, supplies ledger names and attributes for reporting.
• Segment value reference tables (for example the GL segment value definitions), joined through SEGMENT_VALUE, resolve the granted value to its description.
• PARENT_RECORD_ID links a row back to the record from which the flattened privilege was generated, supporting internal regeneration logic.
• Access set assignment setup and validation routines within Oracle General Ledger depend on the table when computing and enforcing user security scope.