Search Results gma_procdef_wf_pk




Overview
Explore in AI Chat

Overview

GMA.GMA_PROCDEF_WF is a table in the Process Manufacturing Systems (GMA) product of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. Its documented purpose is to store workflow process definitions that participate in the generic approval process configuration framework, together with a flag indicating whether each process is currently enabled or disabled. In practice the table acts as the registry that the generic approval framework consults to determine which item types and workflow processes are eligible for approval routing, allowing administrators to turn individual approval processes on or off without modifying the underlying workflow definitions.

The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning no parent-child dependencies were detected in the documented schema. As a modeling suggestion, the table is best treated as a small reference or configuration entity rather than a hub, link, or satellite: its natural business key is the item type and process name pair, and its descriptive and audit attributes hang directly off that key.

Key Information Stored

The documented physical schema consists of nine columns in the GMA schema. The most significant are:

  • WF_ITEM_TYPE — the workflow item type that anchors the approval process, such as the item type registered for a GMA approval flow. This column forms part of the primary key.
  • PROCESS_NAME — the workflow process name within that item type. Together with WF_ITEM_TYPE it forms the composite business key of the table.
  • ENABLE_FLAG — indicates whether the referenced approval process configuration is enabled or disabled, providing the runtime switch used by the generic approval framework.
  • COLUMN_DATA_SQL — stores SQL fragments used to derive column-level data for the process configuration, supporting dynamic attribute resolution during approval processing.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle Applications Who columns that record row provenance and the most recent DML activity.

The surrogate primary key is defined by the GMA_PROCDEF_WF_PK constraint on (WF_ITEM_TYPE, PROCESS_NAME). No additional unique indexes are documented, so this composite constraint is the sole business-key candidate. Because the key is purely business-meaningful, there is no separate meaningless surrogate identifier.

Common Use Cases and Queries

Typical usage centers on verifying and reporting which approval processes are active. A common query lists all enabled processes for a given item type:

  • SELECT process_name, enable_flag, last_update_date FROM gma.gma_procdef_wf WHERE wf_item_type = :item_type AND enable_flag = 'Y';
  • Audit reporting: compare ENABLE_FLAG values against expected configuration to detect processes inadvertently disabled after a patch or migration. Filter on LAST_UPDATED_BY and LAST_UPDATE_DATE to attribute changes.
  • Migration and cloning validation: extract the full row set for an item type and reconcile counts between source and target instances, using (WF_ITEM_TYPE, PROCESS_NAME) as the matching key.
  • Troubleshooting approval routing: when an approval does not launch, confirm that the corresponding row exists and that ENABLE_FLAG is set to enabled.

Related Objects

The documented relationship data classifies this table as standalone, with no foreign keys mined from the schema. Consequently, related objects are best identified through the workflow and approval framework rather than through declarative constraints:

  • WF_ITEM_TYPES (Workflow) — joined on WF_ITEM_TYPE to resolve item type display names and persistence information.
  • WF_PROCESS_ACTIVITIES and WF_ACTIVITIES — joined on WF_ITEM_TYPE and PROCESS_NAME to enumerate the activities within each registered process.
  • GMA_PROCDEF_WF_PK — the primary key constraint that governs uniqueness of (WF_ITEM_TYPE, PROCESS_NAME).
  • Generic approval framework configuration tables in the GMA schema that consume ENABLE_FLAG and COLUMN_DATA_SQL at runtime.
  • Workflow Engine APIs such as WF_ENGINE for programmatic validation of item type and process name values stored here.