Search Results gl_access_set_norm_assign_v




Overview
Explore in AI Chat

Overview

GL_ACCESS_SET_NORM_ASSIGN_V is a reporting view owned by the APPS schema in Oracle E-Business Suite General Ledger (GL). It exposes the normalized assignment records that define how data access sets are granted across ledgers, presenting a denormalized, join-ready projection of the underlying assignment table joined to GL_LEDGERS so that the ledger name accompanies each assignment row. In EBS 12.1.1 and 12.2.2 the object carries a VALID status and is registered as a VIEW. Its principal role is to support reporting, diagnostics, and integration queries related to data access set security — determining which ledgers a given access set may reach and under what privilege.

The view is particularly relevant when searching for all_segment_value_flag, a column it surfaces directly from the base assignment table. Because the view reconstructs the ROWID as ROW_ID and joins to the ledger definition, it is a convenient entry point for queries that must resolve an access set assignment to a human-readable ledger name without manually joining GL_LEDGERS.

Underlying Base Objects

The documented view text is a two-table join over two APPS synonyms:

  • GL_ACCESS_SET_NORM_ASSIGN (alias GAA) — the normalized assignment table holding segment-value-level access rules for access sets. GAA.ROWID is projected as ROW_ID.
  • GL_LEDGERS (alias GLL) — the ledger definition table, joined on GLL.LEDGER_ID = GAA.LEDGER_ID, supplying LEDGER_NAME.

All columns other than LEDGER_NAME originate from GL_ACCESS_SET_NORM_ASSIGN. The join is an equi-join on LEDGER_ID with no outer join, so assignment rows must resolve to a ledger to appear. The view exposes the WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), the DFF context and ATTRIBUTE1–15, and the LINK_ID/REQUEST_ID integration keys.

Key Columns

  • ROW_ID — ROWID of the base assignment row, used for row-level reference.
  • ACCESS_SET_ID — the data access set to which the assignment belongs.
  • LEDGER_ID / LEDGER_NAME — the ledger targeted by the assignment and its descriptive name.
  • ALL_SEGMENT_VALUE_FLAG — indicates whether the assignment grants access to all segment values for the given segment, rather than a specific SEGMENT_VALUE.
  • SEGMENT_VALUE_TYPE_CODE — categorizes the segment value type for the assignment.
  • ACCESS_PRIVILEGE_CODE — the privilege granted (for example, read versus write).
  • SEGMENT_VALUE — the specific segment value when the assignment is not an all-values grant.
  • STATUS_CODE, START_DATE, END_DATE — lifecycle and effective-dating of the assignment.
  • RECORD_ID, LINK_ID, REQUEST_ID — identifiers supporting record-level tracking and concurrent request linkage.
  • CONTEXT and ATTRIBUTE1–15 — descriptive flexfield content.

Common Use Cases and Queries

Typical scenarios include auditing which ledgers a data access set covers, identifying assignments using the all-segment-value flag, and feeding access-set metadata into custom reports or integrations.

SELECT access_set_id, ledger_id, ledger_name,
       all_segment_value_flag, segment_value,
       access_privilege_code, status_code
  FROM apps.gl_access_set_norm_assign_v
 WHERE access_set_id = :p_access_set_id
 ORDER BY ledger_name;

To isolate broad grants:

SELECT ledger_name, segment_value_type_code
  FROM apps.gl_access_set_norm_assign_v
 WHERE all_segment_value_flag = 'Y'
   AND status_code = 'A';

Referencing LEDGER_NAME directly avoids a manual join to GL_LEDGERS, and the ATTRIBUTE/context columns allow filtering on flexfield-defined classifications.