Search Results lov_table

Overview

GMA_PROCCOL_WF_VL is a documented Oracle E-Business Suite view owned by the APPS schema within the Process Manufacturing (GMA) product family. It exposes configuration metadata for Process Manufacturing workflow process columns — the definitions that describe how workflow-enabled process parameters and prompts are presented to users, including the list of values (LOV) sources used to populate those prompts. The view's name follows Oracle's standard convention for translated (multi-language) views, where the "_VL" suffix indicates that the view joins a base (non-translated) table to its translation table and filters rows by the session language. In this case the language filter is applied using USERENV('LANG') against the translated table GMA_PROCCOL_WF_TL.

Because it is a view rather than a table, GMA_PROCCOL_WF_VL carries no storage of its own; it is a read-only projection intended for reporting, inquiry, and integration use. In Oracle EBS 12.1.1 and 12.2.2 the object is registered as a VALID database object in the APPS schema and is referenced through the ETRM (E-Business Suite Technical Reference Manual) metadata for the GMA module.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to the APPS schema as synonyms:

• GMA_PROCCOL_WF_B — the base table holding the non-translatable attributes of each workflow process column, including the workflow item type, process name, table/column identifiers, and the LOV configuration columns.
• GMA_PROCCOL_WF_TL — the translation table holding the language-dependent prompt text (COLUMN_PROMPT) for each workflow column, keyed by language.

The join is established on the composite key of WF_ITEM_TYPE, PROCESS_NAME, TABLE_NAME, and COLUMN_NAME, ensuring that each base row is matched to its translation row. The USERENV('LANG') predicate restricts the translation side to the language of the current session, so the value returned in COLUMN_PROMPT is always the appropriately localized prompt. The B.CREATION_DATE, B.CREATED_BY, B.LAST_UPDATE_LOGIN, B.LAST_UPDATE_DATE, and B.LAST_UPDATED_BY columns preserve standard EBS audit trail information from the base table.

Key Columns

• ROW_ID — the ROWID of the base table row, exposed for reference and locking semantics.
• WF_ITEM_TYPE — the Oracle Workflow item type that the process column belongs to.
• PROCESS_NAME — the name of the workflow process containing the column.
• COLUMN_HIERARCHY — indicates the placement or hierarchy of the column within the process structure.
• TABLE_NAME / COLUMN_NAME — the underlying database table and column that the workflow column maps to.
• LOV_TABLE — the table (or view) name that supplies the values for the list of values associated with the column. This is the column most directly relevant to users searching on the term "lov_table".
• LOV_COLUMN — the column within LOV_TABLE from which the LOV values are drawn.
• COLUMN_PROMPT — the translated, language-specific prompt displayed for the column.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns inherited from the base table.

Common Use Cases and Queries

The view is typically queried to inspect or troubleshoot how Process Manufacturing workflow columns are configured, particularly the LOV definitions that drive user selection lists. A common query retrieves all columns for a given workflow item type together with their LOV sources:

• Listing LOV-backed columns for a workflow: SELECT WF_ITEM_TYPE, PROCESS_NAME, TABLE_NAME, COLUMN_NAME, COLUMN_PROMPT, LOV_TABLE, LOV_COLUMN FROM APPS.GMA_PROCCOL_WF_VL WHERE WF_ITEM_TYPE = :p_item_type;
• Finding all columns that reference a particular LOV table: SELECT PROCESS_NAME, COLUMN_NAME, LOV_TABLE, LOV_COLUMN FROM APPS.GMA_PROCCOL_WF_VL WHERE LOV_TABLE = :p_lov_table;
• Auditing recent configuration changes: SELECT WF_ITEM_TYPE, PROCESS_NAME, COLUMN_NAME, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM APPS.GMA_PROCCOL_WF_VL WHERE LAST_UPDATE_DATE > SYSDATE - 30;

Because the view applies the USERENV('LANG') filter, querying it under different language sessions returns the same configuration rows with COLUMN_PROMPT localized accordingly. Reports and integrations should therefore rely on the view rather than joining the base and translation tables directly, ensuring consistent multilingual behavior across EBS 12.1.1 and 12.2.2 environments.