Search Results gl_access_set_norm_assign




Overview
Explore in AI Chat

Overview

GL_ACCESS_SET_NORM_ASSIGN is a General Ledger table in the Oracle E-Business Suite that stores data access set privilege assignments. A data access set defines the ledgers, balancing segment values, and management segment values that a user or responsibility may access, together with the read/write privilege granted for each. This table is the normalized storage of those grants, holding one row for each combination of access set, ledger, segment value scope, and access privilege. It is a core component of the Oracle EBS security model for financial data, determining which accounting data a user can query and which data the user can post to.

The table resides in the GL schema and is documented in ETRM 12.2.2 with 33 columns. Its primary key, GL_ACCESS_SET_NORM_ASSIGN_PK, is a composite key spanning ACCESS_SET_ID, LEDGER_ID, ALL_SEGMENT_VALUE_FLAG, SEGMENT_VALUE_TYPE_CODE, and ACCESS_PRIVILEGE_CODE. Under the heuristic Data Vault classification supplied in the metadata, this object is modeled as standalone. This should be read as a modeling suggestion only; because the table carries its own descriptive and audit attributes (dates, status, segment values), it behaves in practice as a multi-active satellite with embedded foreign-key references rather than a pure hub or link.

Key Information Stored

The five columns of the primary key form the business identity of each privilege grant. ACCESS_SET_ID identifies the data access set to which the grant belongs. LEDGER_ID identifies the ledger within that access set. ALL_SEGMENT_VALUE_FLAG indicates whether the grant covers all segment values or only a specific value. SEGMENT_VALUE_TYPE_CODE identifies the segment type (for example, balancing or management segment) to which the grant applies. ACCESS_PRIVILEGE_CODE records the privilege granted, typically distinguishing full read/write access from read-only access.

There is no separate single-column surrogate primary key; identity is derived entirely from the composite business key described above.

Common Use Cases and Queries

The most common requirement is to report which ledgers and segment values a given data access set exposes, and with what privilege. A representative query joins this table to the access set definition and to GL_LEDGERS:

  • SELECT a.access_set_id, a.ledger_id, a.segment_value_type_code, a.segment_value, a.access_privilege_code FROM gl_access_set_norm_assign a WHERE a.access_set_id = :p_access_set_id AND TRUNC(SYSDATE) BETWEEN a.start_date AND NVL(a.end_date, TRUNC(SYSDATE));
  • Filtering on ALL_SEGMENT_VALUE_FLAG = 'Y' isolates grants that apply to the entire ledger rather than to individual segment values.
  • Joining to GL_LEDGERS on LEDGER_ID resolves ledger names for security audit reports.
  • Joining to FND_RESPONSIBILITY and the data access set assignment tables shows which responsibilities inherit a given privilege.

Typical reporting uses include access certification reviews, segregation-of-duties analysis, and impact assessment before changing ledger or segment value hierarchies.

Related Objects

The following objects are the most significant references and dependencies. Join columns are identified from the documented key structure.

  • GL_ACCESS_SETS — the parent access set definition; join on ACCESS_SET_ID.
  • GL_LEDGERS — ledger definition; join on LEDGER_ID.
  • FND_ACCESS_SET_USAGE or the access set assignment tables that map responsibilities and users to access sets.
  • GL_ACCESS_SET_NORM_ASSIGN references segment value types defined by the key flexfield structure, linking indirectly to FND_ID_FLEX_STRUCTURES and FND_ID_FLEX_SEGMENTS.
  • Application programming interfaces and concurrent programs that maintain data access sets write to this table when privileges are created or changed.

Because the object is classified as standalone in the metadata, no enforced foreign keys are documented; relationships above are logical joins driven by the composite key.