Search Results column_value1

Overview

GMA_PROCDATA_WF is a Process Manufacturing (GMA) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores user-defined process customization data. Its rows determine the approval process behavior exercised by Oracle Workflow and are consumed by an approval-checking API to decide whether approval is required for a given data set. In practical terms, the table acts as a configuration matrix: each row pairs a workflow item type and process name with a set of up to ten descriptive column names and their corresponding values, plus presentation and enablement attributes such as ROLE, ENABLE_FLAG, and SORT_ORDER. Because the row content drives conditional branching in the approval flow, the table is best understood as customer-controlled configuration rather than transactional data.

The provided metadata documents a heuristic Data Vault classification of standalone; that is, the table has no mined foreign-key relationships to other objects in the documented schema. As a modeling suggestion, this object is most naturally treated as a satellite-like or reference/configuration entity keyed by its own business key, rather than as a hub or link in a Data Vault model.

Key Information Stored

The table contains 30 documented columns. The primary key is a unique index, GMA_PROCDATA_WF_UK, which is composite over WF_ITEM_TYPE, PROCESS_NAME, and COLUMN_VALUE1 through COLUMN_VALUE10. This means the entire set of values participates in uniqueness; there is no single-column surrogate primary key in the documented schema, so the business key is the primary key here. Important columns include:

• WF_ITEM_TYPE — the Oracle Workflow item type identifying the approval workflow the customization applies to.
• PROCESS_NAME — the workflow process within that item type whose behavior is being customized.
• COLUMN_NAME1 … COLUMN_NAME10 — the names of the attributes or criteria columns being evaluated, supplied in pairs with their values. These drive the actual matching logic applied by the approval API.
• COLUMN_VALUE1 … COLUMN_VALUE10 — the corresponding values for those named columns. Because they form part of the unique key, they also define row identity.
• ROLE — the responsibility or role context in which the customization applies, allowing different approval behavior by role.
• ENABLE_FLAG — indicates whether the customization row is active; disabled rows are typically ignored by the approval-checking logic without being deleted.
• SORT_ORDER — controls evaluation or display sequence when multiple matching rows exist.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS who-columns providing audit and concurrency information.

Common Use Cases and Queries

Typical usage centers on determining why an approval was or was not triggered for a given item type, process, and role. Administrators query the table to review active customizations before or after a change, and to identify rows that may conflict or should be disabled rather than removed.

• Listing active customizations for a workflow: SELECT WF_ITEM_TYPE, PROCESS_NAME, ROLE, SORT_ORDER FROM GMA.GMA_PROCDATA_WF WHERE ENABLE_FLAG = 'Y' ORDER BY WF_ITEM_TYPE, PROCESS_NAME, SORT_ORDER;
• Finding who last changed a customization: select the who-columns alongside the business-key columns and order by LAST_UPDATE_DATE.
• Locating rows for a specific process and role to trace unexpected approval routing.
• Reporting on customizations by role to assess whether approval rules are uniformly applied.
• Auditing rows with ENABLE_FLAG = 'N' that remain in the table and could be re-enabled accidentally.

Related Objects

The documented relationship data classifies GMA_PROCDATA_WF as standalone, with no mined foreign keys to other tables. Dependencies are therefore functional rather than declarative, and the following objects are the most significant points of interaction:

• Oracle Workflow runtime tables — WF_ITEM_TYPES and WF_PROCESSES, joined on WF_ITEM_TYPE and PROCESS_NAME respectively, establish the workflow context each row customizes.
• Approval-checking API — the documented consumer that reads this table to decide whether approval is required for a data set.
• GMA process configuration and event tables — the broader Process Manufacturing configuration surface whose approval behavior is governed by these rows.
• FND_USER and FND_RESPONSIBILITY — used to resolve CREATED_BY / LAST_UPDATED_BY and the ROLE values for auditing and reporting.

Because no formal constraints link this table to those objects, joins are performed on the business-key columns described above, and referential integrity is maintained by application logic rather than by the database.