Results for “gl_defas_assignments_u1”

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

Overview

The GL.GL_DEFAS_ASSIGNMENTS table is a core security and authorization object within the Oracle E-Business Suite General Ledger module. It stores the access privilege information that governs each Definition Access Set (DEFAS). A Definition Access Set is an administrative construct that allows organizations to grant or restrict specific user responsibilities and users from viewing, using, or modifying designated General Ledger definitions such as FSG row sets, FSG column sets, MassAllocations, and child Definition Access Sets.

Each row in GL_DEFAS_ASSIGNMENTS represents a single assignment of privileges to one secured object within one Definition Access Set. The table therefore acts as the junction between a Definition Access Set and the individual GL definitions that the set protects. Because the table participates in no foreign key relationships as a dependent or parent object in the documented schema, the heuristic Data Vault classification is standalone. In practice, however, analysts may model it as a link-style table bridging the access set (a hub-like entity) and the secured definition (another hub-like entity), while the privilege flags and the standard Who columns behave as satellite attributes. This classification should be treated as a modeling suggestion rather than a rigid constraint.

Key Information Stored

The table contains 29 documented columns. The most significant are:

• DEFINITION_ACCESS_SET_ID (NUMBER, 15) — The defining column that identifies the Definition Access Set to which the row belongs. It is part of the primary key and the leading column of the unique index.
• OBJECT_TYPE (VARCHAR2, 30) — The type of secured object, for example Child Definition Access Set, FSG row set, FSG column set, or MassAllocation.
• OBJECT_KEY (VARCHAR2, 240) — The defining column value for the secured object itself.
• VIEW_ACCESS_FLAG — Indicates whether view access is granted on the object.
• USE_ACCESS_FLAG — Indicates whether use access is granted on the object.
• MODIFY_ACCESS_FLAG — Indicates whether modify access is granted on the object.
• STATUS_CODE — The record status, used to distinguish active from inactive rows.
• REQUEST_ID (NUMBER, 15) — The concurrent program request identifier that created or last touched the row.
• CONTEXT (VARCHAR2, 150) and ATTRIBUTE1 through ATTRIBUTE15 (VARCHAR2, 150 each) — Descriptive flexfield context and segment columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard Who audit columns.

The primary key is GL_DEFAS_ASSIGNMENTS_PK, defined on (DEFINITION_ACCESS_SET_ID, OBJECT_TYPE, OBJECT_KEY). The unique index GL_DEFAS_ASSIGNMENTS_U1 extends that business key with STATUS_CODE, on (DEFINITION_ACCESS_SET_ID, OBJECT_TYPE, OBJECT_KEY, STATUS_CODE). This design permits multiple status versions of the same assignment to coexist, which is important when records are created and later end-dated or superseded. A non-unique index, GL_DEFAS_ASSIGNMENTS_N1, exists on OBJECT_KEY to support lookups by secured object. The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and both indexes reside in APPS_TS_TX_IDX.

Common Use Cases and Queries

The most common reporting need is to determine which privileges a given Definition Access Set grants. The following pattern joins the assignment rows to their access set:

• Retrieve all active assignments for a set: SELECT definition_access_set_id, object_type, object_key, view_access_flag, use_access_flag, modify_access_flag FROM gl_defas_assignments WHERE definition_access_set_id = :set_id AND status_code = 'A';
• Find all Definition Access Sets that secure a specific object: use the N1 index by filtering on OBJECT_KEY.
• Audit privilege grants by responsibility: join the assignments to the Definition Access Set and its responsibility assignments to identify which responsibilities translate into view, use, or modify rights.
• Identify rows orphaned or end-dated by comparing STATUS_CODE values, since the unique index includes this column.
• Track changes through the standard Who columns and REQUEST_ID for concurrent program lineage.

Related Objects

• GL_DEFINITION_ACCESS_SETS — The parent Definition Access Set table joined on DEFINITION_ACCESS_SET_ID.
• GL_DEFAS_RLSHP — Defines the relationship between Definition Access Sets and the responsibilities or users they apply to.
• FND_RESPONSIBILITY — Used to resolve which responsibilities receive the access defined through the set.
• FND_USER — Used to resolve user-level access when the set is assigned directly to users.
• GL_MASSALLOCATIONS, RG_ROW_SETS and RG_COLUMN_SETS — The underlying FSG and allocation definitions referenced through OBJECT_TYPE and OBJECT_KEY.
• FND_CONCURRENT_REQUESTS — Joined on REQUEST_ID to trace the concurrent program that created or updated assignment rows.

Because no foreign keys are physically documented on this table, referential integrity between the assignment rows and the secured objects is enforced at the application layer, and analysts should treat OBJECT_KEY as a polymorphic reference whose meaning depends on OBJECT_TYPE.