Search Results gl_defas_assignments




Overview
Explore in AI Chat

Overview

GL_DEFAS_ASSIGNMENTS is a General Ledger (GL) table in Oracle E-Business Suite, owned by the GL schema. Its documented purpose is to store definition access set privilege assignments. Definition Access Sets (DAS) are the security construct in Oracle General Ledger that governs which users or responsibilities may view, use, or modify specific GL definitions — such as recurring journals, allocations, budgets, and other accounting definitions — rather than restricting access at the ledger level alone. GL_DEFAS_ASSIGNMENTS is therefore the assignment component of that model, binding a definition access set to the individual definition objects it controls and recording the privilege levels granted on each.

Under the heuristic Data Vault classification derived from its foreign key structure, the object is treated as standalone — it holds no documented parent or child foreign keys within the shipped schema. In modeling terms, this suggests GL_DEFAS_ASSIGNMENTS behaves primarily as a satellite-like structure attached to the definition access set header, capturing the per-definition privilege attributes, with the set identifier functioning as the effective parent reference.

Key Information Stored

The table records the three privilege flags that define the scope of access granted to each assigned definition object:

  • DEFINITION_ACCESS_SET_ID — Identifier of the definition access set to which the assignment belongs; part of the composite primary key.
  • OBJECT_TYPE — Classifies the definition object being secured (for example, the type of GL definition such as a recurring journal or allocation). Part of the primary key.
  • OBJECT_KEY — The key value identifying the specific definition object within its type. Part of the primary key.
  • VIEW_ACCESS_FLAG — Indicates whether the assignee may view the definition.
  • USE_ACCESS_FLAG — Indicates whether the assignee may use the definition, such as submitting it in a journal or allocation process.
  • MODIFY_ACCESS_FLAG — Indicates whether the assignee may modify the definition.
  • STATUS_CODE — Lifecycle status of the assignment row; included in the unique index.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
  • CREATION_DATE, CREATED_BY — Row creation audit.
  • REQUEST_ID — Concurrent request that last touched the row.
  • CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segment columns for extensibility.

The surrogate-style primary key is GL_DEFAS_ASSIGNMENTS_PK over (DEFINITION_ACCESS_SET_ID, OBJECT_TYPE, OBJECT_KEY). A business-key candidate is documented in the unique index GL_DEFAS_ASSIGNMENTS_U1, which extends those three columns with STATUS_CODE, allowing the assignment record to be versioned by status while preserving uniqueness.

Common Use Cases and Queries

Typical reporting scenarios include auditing which definitions a given access set secures, verifying that a privilege combination exists before migration, and reconciling access sets across environments.

To list the definitions secured by a specific access set:

  • SELECT OBJECT_TYPE, OBJECT_KEY, VIEW_ACCESS_FLAG, USE_ACCESS_FLAG, MODIFY_ACCESS_FLAG FROM GL.GL_DEFAS_ASSIGNMENTS WHERE DEFINITION_ACCESS_SET_ID = :set_id AND STATUS_CODE = 'A';

To identify every definition with modify privilege granted under a set:

  • SELECT a.DEFINITION_ACCESS_SET_ID, a.OBJECT_TYPE, a.OBJECT_KEY FROM GL.GL_DEFAS_ASSIGNMENTS a WHERE a.MODIFY_ACCESS_FLAG = 'Y' AND a.STATUS_CODE = 'A' ORDER BY a.DEFINITION_ACCESS_SET_ID, a.OBJECT_TYPE;

Because the table has no documented foreign keys, joins to definition tables are performed on OBJECT_TYPE and OBJECT_KEY values rather than enforced referential constraints, so type filtering is essential.

Related Objects

The documented relationship classification is standalone, indicating no shipped foreign keys. The practical relationships are: