Search Results enforce_step_dependency

Overview

GMD_ROUTINGS_VL is a dictionary-defined view owned by the APPS schema in Oracle E-Business Suite, belonging to the Process Manufacturing Product Development (GMD) module. It presents routing header information by joining the base routing table with its translation table, and it is the standard read-only interface used by Oracle Forms, concurrent programs, reports, and custom code to retrieve routing header records in the language of the current session. Because it is a "_VL" view (base plus translation), it surfaces both the language-independent attributes stored on the base table and the language-dependent routing description, which is the column most commonly targeted by users searching for "routing_desc." The view is documented as VALID in ETRM 12.2.2 and is present in 12.1.1 and 12.2.2 with the same definition and column list.

Underlying Base Objects

The view's SQL text is defined over two synonyms referencing the underlying GMD tables:

• GMD_ROUTINGS_B — the base (language-independent) routing header table, aliased B. It supplies routing identifiers, versioning, UOM, status, DFF attributes, and WHO columns.
• GMD_ROUTINGS_TL — the translation table, aliased T. It supplies ROUTING_DESC for the session language.

The join condition is B.ROUTING_ID = T.ROUTING_ID AND T.LANGUAGE = USERENV('LANG'). The USERENV('LANG') predicate restricts the translation row to the language of the current runtime session, so a single row is returned per routing for the logged-in language. The view also exposes B.ROWID as ROW_ID for row identification.

Key Columns

The view presents the full set of routing header columns plus the translated description:

• ROUTING_ID — primary key linking the base and translation tables; the join key for routing steps and other dependent entities.
• ROUTING_NO, ROUTING_VERS — routing number and version, together identifying the specific routing revision.
• ROUTING_DESC — the language-dependent description from GMD_ROUTINGS_TL; the column matched by the user's search term.
• ROUTING_CLASS, ROUTING_STATUS, INACTIVE_IND, IN_USE, DELETE_MARK — classification and lifecycle/status flags.
• ROUTING_QTY, ITEM_UM, ROUTING_UOM — base quantity and units of measure for the routing.
• OWNER_ORGANIZATION_ID, OWNER_ID, PROJECT_ID — organizational and project ownership context.
• CONTIGUOUS_IND, ENFORCE_STEP_DEPENDENCY, PROCESS_LOSS — process execution attributes governing step sequencing and yield loss.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — date-effectivity range.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE30 — descriptive flexfield segments.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — WHO audit columns.

Common Use Cases and Queries

The view is primarily queried to obtain the routing description alongside header attributes, since ROUTING_DESC does not reside on the base table. A typical lookup by description:

SELECT routing_id, routing_no, routing_vers, routing_desc, routing_status
FROM apps.gmd_routings_vl
WHERE routing_desc LIKE '%BLEND%'
AND inactive_ind = 'N';

Retrieving a specific routing header for a report or interface:

SELECT routing_no, routing_vers, routing_desc, routing_uom,
      effective_start_date, effective_end_date
FROM apps.gmd_routings_vl
WHERE routing_id = :p_routing_id;

Because the view filters on USERENV('LANG'), queries return the description in the caller's session language without additional translation joins. Reports and interfaces should always select through GMD_ROUTINGS_VL rather than joining the _B and _TL tables directly, ensuring consistent language handling and alignment with Oracle's supported data access path.