Search Results gmd_operations_vl




Overview
Explore in AI Chat

Overview

GMD_OPERATIONS_VL is a seed data and validation view owned by the APPS schema in Oracle E-Business Suite. It belongs to the GMD product family, Process Manufacturing Product Development, and is available in both release 12.1.1 and 12.2.2. The view presents process manufacturing operations — reusable manufacturing steps that define how a product or intermediate is produced. Operations in Process Manufacturing carry routing information such as operation number, version, process quantity, unit of measure, operation class, and process operation control class.

The "_VL" suffix denotes a "translated value" or language view. It is the standard EBS idiom for joining a base table to its translation table so consumers see the description in the session's language rather than a single hard-coded language. For this reason, GMD_OPERATIONS_VL is defined over GMD_OPERATIONS_B (base) and GMD_OPERATIONS_TL (translations), returning the operation description (OPRN_DESC) filtered to USERENV('LANG'). Because it exposes only valid, language-resolved rows, it is the preferred object for reports, forms LOVs, concurrent programs, and integrations that must display operation text to end users.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, GMD_OPERATIONS_VL references two synonym objects owned by APPS: GMD_OPERATIONS_B and GMD_OPERATIONS_TL. GMD_OPERATIONS_B stores the operation header: identifiers, operation number and version, quantities, class codes, status, flexfield attributes, and WHO audit columns. GMD_OPERATIONS_TL stores the language-specific description keyed by OPRN_ID and LANGUAGE.

The view text joins these on B.OPRN_ID = T.OPRN_ID with T.LANGUAGE = USERENV('LANG'). Note that the view exposes B.ROWID as ROW_ID, which is a convenience for downstream consumers but not a key column, since the physical ROWID belongs to the base table.

Key Columns

  • ROW_ID — base table ROWID of GMD_OPERATIONS_B; useful for row-level addressing but not portable across reorganizations.
  • OPRN_ID — numeric primary key identifying the operation. Used in foreign key relationships with routing, recipe, and step tables.
  • OPRN_NO and OPRN_VERS — user-facing operation number and version; the combination drives operator entry and display.
  • PROCESS_QTY_UM and PROCESS_QTY_UOM — process quantity and its unit of measure, defining the basis on which operation parameters scale.
  • MINIMUM_TRANSFER_QTY — quantity threshold governing transfer behavior between operations.
  • OPRN_CLASS and POC_CTL_CLASS — operation class and process operation control class; these influence which parameters are applicable and how the step is controlled.
  • IN_USE, INACTIVE_IND, DELETE_MARK — status flags. Only rows with DELETE_MARK = 0 and INACTIVE_IND = 0 should be considered active for transactional use.
  • OPERATION_STATUS — workflow or lifecycle status of the operation definition.
  • OWNER_ORGANIZATION_ID — organization that owns the operation, enabling multi-org filtering.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-effective window for the record.
  • OPRN_DESC — translated description from GMD_OPERATIONS_TL, returned in the session language.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — flexible DFF columns for customer-defined extensions.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include operations listing reports, LOV population in Process Manufacturing forms, and integration extracts feeding MES or lab systems. Because the view resolves the session language automatically, it is preferred over querying the translation table directly. Filtering on DELETE_MARK = 0 and INACTIVE_IND = 0 is standard practice to exclude logically deleted or retired operations.

  • List active operations for an organization:

SELECT oprn_no, oprn_vers, oprn_desc, process_qty_um, process_qty_uom
FROM apps.gmd_operations_vl
WHERE delete_mark = 0 AND inactive_ind = 0
AND owner_organization_id = :org_id
ORDER BY oprn_no, oprn_vers;

  • Look up a single operation by number and version:

SELECT oprn_id, oprn_desc, operation_status
FROM apps.gmd_operations_vl
WHERE oprn_no = :oprn_no AND oprn_vers = :oprn_vers;

  • Join to routing or recipe tables for process build reports, using OPRN_ID as the join key. Always drive joins from the view's OPRN_ID to the transactional table's foreign key, and apply organization and status filters on the view to avoid including inactive definitions.

Because the view performs an inner join to the translation table, an operation lacking a row in the session language will not be returned. Plans relying on this object should confirm that all operations have translations for the languages in use.