Search Results gma_actdata_wf




Overview
Explore in AI Chat

Overview

GMA_ACTDATA_WF is a table owned by the GMA schema within the Oracle E-Business Suite Process Manufacturing Systems (OPM) product family. It stores the actual data values associated with a workflow role association, capturing the specific set of data that a user-role assignment is scoped to. In practical terms, the table holds the "row-level" or "range-level" filter values that determine which records a given role-association activity is permitted to act upon, expressed as name-value pairs across up to ten configurable slots.

Within Oracle EBS 12.1.1 and 12.2.2, this table is closely tied to the Process Manufacturing workflow role-association framework, where an activity (a role association) is bound to a discrete set of qualifying data. The ETRM metadata classifies the object heuristically as standalone under a Data Vault modeling lens, meaning no foreign-key relationships to other tables were mined. From a Data Vault modeling suggestion perspective, this object behaves most like a satellite: it carries descriptive, bounded attribute values (COLUMN_NAME*n* / COLUMN_VALUE*n* pairs) keyed to an activity identifier rather than acting as a hub of distinct business entities or as an associative link between two hubs. The absence of documented FK relationships supports treating it as a standalone descriptive child of the activity concept.

Key Information Stored

The table contains 29 documented columns. The most important are summarized below.

  • ACTIVITY_ID — The activity identifier that ties each data row back to its role association. It forms the leading component of the composite unique key.
  • ROLE — Identifies the workflow role to which the associated data set applies.
  • COLUMN_NAME1 through COLUMN_NAME10 — Ten slots naming the data attribute being scoped (for example, an entity name or qualification column).
  • COLUMN_VALUE1 through COLUMN_VALUE10 — Ten matching slots holding the actual value for the corresponding named column, forming the name-value pairing that defines the role's data scope.
  • SORT_ORDER — Controls sequencing when multiple rows or qualifications are presented or applied.
  • ENABLE_FLAG — Indicates whether the row's data qualification is active.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last changed each row and when.

The documented surrogate/business key is the unique index GMA_ACTDATA_WF_UK, a composite over ACTIVITY_ID and COLUMN_VALUE1 through COLUMN_VALUE10. This means the ten value slots act collectively as the business-key discriminator in addition to their descriptive role, while no separate single-column surrogate primary key is documented.

Common Use Cases and Queries

Typical uses involve auditing or reporting which data sets a role association governs, and debugging why a role sees or is denied specific process manufacturing records. A simple retrieval of all qualifications for a given activity:

  • SELECT activity_id, role, column_name1, column_value1, enable_flag FROM gma.gma_actdata_wf WHERE activity_id = :activity_id ORDER BY sort_order;
  • SELECT * FROM gma.gma_actdata_wf WHERE role = :role AND enable_flag = 'Y';
  • Reporting distinct scoped values: SELECT DISTINCT column_value1 FROM gma.gma_actdata_wf WHERE column_name1 = 'ENTITY_NAME';

Because the data is stored positionally, queries frequently pivot or unpivot the name-value pairs to reconstruct the effective filter for an activity.

Related Objects

The provided metadata records no foreign keys and no dependent child tables for GMA_ACTDATA_WF, and the heuristic classification is standalone. Consequently there are no documented join columns to other objects. Functionally, the object is expected to be referenced by the Process Manufacturing workflow role-association definitions that supply ACTIVITY_ID and ROLE, and by workflow activity/role metadata used by the OPM role-association engine. Any joins should be validated against the live data dictionary, since the documented relationship data does not identify explicit referencing objects or join columns for this table.