Results for “gmf_order_types_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMF_ORDER_TYPES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Process Manufacturing Financials (GMF) product family and exists exclusively to back the Oracle Forms value set GMF_ORDER_TYPES. Rather than exposing a broad transactional data model, the view provides a constrained, language-sensitive list of order transaction types suitable for use in a list of values (LOV) or flexfield-driven selection prompt within Process Manufacturing windows.

Because its definition embeds A.TRANSACTION_TYPE_CODE='ORDER', the view returns only those transaction types whose code is literally "ORDER," together with a single synthetic row of empty and zero values injected via a UNION with DUAL. That synthetic row gives the value set a blank, "no selection" entry, which is a common requirement for optional Form fields. The view is therefore a presentation-layer construct rather than an analytical source; it feeds validation and selection logic, not reporting aggregates.

Underlying Base Objects

The documented view text resolves three referenced objects, each exposed in APPS through a synonym:

• OE_TRANSACTION_TYPES_ALL (SYNONYM) — the Order Management base table holding transaction type definitions, including TRANSACTION_TYPE_ID and TRANSACTION_TYPE_CODE. It supplies the ID and code columns and is the target of the code filter.
• OE_TRANSACTION_TYPES_TL (SYNONYM) — the translation table for transaction types, holding the language-dependent NAME and DESCRIPTION. It joins to the ALL table on TRANSACTION_TYPE_ID and is restricted to the session language via T.LANGUAGE = USERENV('LANG').
• DUAL (SYNONYM) — the standard single-row dummy table, used here solely to append the placeholder row (NAME = '', DESCRIPTION = '', TRANSACTION_TYPE_ID = 0, LANGUAGE = '', TRANSACTION_TYPE_CODE = '').

The relationship among these objects is a two-table inner join filtered by code and language, unioned to a constant row. The view is thus a thin projection of OE_TRANSACTION_TYPES_ALL and OE_TRANSACTION_TYPES_TL; it introduces no independent storage.

Key Columns

• NAME — the translated transaction type name from OE_TRANSACTION_TYPES_TL.TL; displayed to the user in the value set LOV.
• DESCRIPTION — the translated description from the TL table, available for informational display or tooltips.
• TRANSACTION_TYPE_ID — the numeric identifier shared by the ALL and TL tables; the value typically stored when the user makes a selection. Returns 0 for the placeholder row.
• LANGUAGE — the language code from the TL row, matching USERENV('LANG') for real rows and empty for the placeholder.
• TRANSACTION_TYPE_CODE — sourced from OE_TRANSACTION_TYPES_ALL; since the view filters to the 'ORDER' code, this column is effectively constant for real rows and empty for the placeholder row.

Common Use Cases and Queries

The principal use case is populating the GMF_ORDER_TYPES value set attached to Process Manufacturing Financials forms, ensuring the user can only pick the standard Order transaction type (or leave the field blank). A secondary use is diagnostic verification that the value set resolves as expected in a given language.

Listing all selectable values for the value set:

SELECT name, description, transaction_type_id, language, transaction_type_code FROM apps.gmf_order_types_v ORDER BY transaction_type_id;

Excluding the placeholder row to inspect only real Order types:

SELECT transaction_type_id, name, description FROM apps.gmf_order_types_v WHERE transaction_type_id > 0;

Reconciling the view back to its base tables to confirm translation coverage across installed languages:

SELECT a.transaction_type_id, t.language, t.name FROM apps.oe_transaction_types_all a, apps.oe_transaction_types_tl t WHERE t.transaction_type_id = a.transaction_type_id AND a.transaction_type_code = 'ORDER' ORDER BY t.language;

Because the view exposes only code 'ORDER', it should not be used to enumerate all order management transaction types; queries against OE_TRANSACTION_TYPES_ALL are required for that broader purpose. Administrators troubleshooting a missing value should confirm that an Order-code row exists in OE_TRANSACTION_TYPES_ALL and that a matching TL row exists for the session language.