Results for “enforce_step_dependency”

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

Overview

GMD_ROUTINGS_B is the routing header base table in the Oracle EBS Process Manufacturing Product Development (GMD) module. It stores the master definition of a routing: the ordered sequence of process steps, operations, and resource requirements used to manufacture a product, intermediate, or by-product in a process manufacturing environment. Every routing recorded in this table is uniquely identified by a surrogate primary key, ROUTING_ID, generated via the GMD_ROUTINGS_B_PK index. The table is owned by the GMD schema and contains 60 documented columns in release 12.2.2, of which a significant proportion are descriptive ATTRIBUTE1 through ATTRIBUTE30 flex columns and DFF-related fields.

The ETRM metadata classifies this object heuristically as hub-leaning within a Data Vault model. As a modeling suggestion, this reflects its role as a central business entity whose identity (ROUTING_ID) is stable and independent, while its foreign-key dependencies to classification and text headers sit on satellite or reference dimensions. Note however that downstream transactional tables such as FM_ROUT_DTL, PM_BTCH_HDR, and GMP_FORM_EFF reference it heavily, so in practice it behaves as a hub with multiple dependent links.

Key Information Stored

The most operationally significant columns are:

• ROUTING_ID — surrogate primary key; the internal identifier propagated to all dependent tables.
• ROUTING_NO — user-visible routing number; combined with ROUTING_VERS forms the business key candidate GMD_ROUTINGS_B_UC1.
• ROUTING_VERS — version number, enabling multiple revisions of the same routing to coexist.
• ROUTING_CLASS — foreign key to GMD_ROUTING_CLASS_B, grouping routings into logical classes.
• ROUTING_QTY and ROUTING_UOM — the batch quantity and unit of measure on which the routing is based.
• ITEM_UM — the item’s primary unit of measure.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — date range during which the routing is valid.
• ROUTING_STATUS and INACTIVE_IND — lifecycle and activity flags.
• IN_USE — indicates whether the routing is currently referenced.
• PROCESS_LOSS, FIXED_PROCESS_LOSS, and FIXED_PROCESS_LOSS_UOM — planned yield and loss parameters.
• ENFORCE_STEP_DEPENDENCY and CONTIGUOUS_IND — step sequencing behavior controls.
• TEXT_CODE — foreign key to FM_TEXT_HDR, linking narrative text.
• OWNER_ORGANIZATION_ID and OWNER_ORGN_CODE — owning organization identification.
• OWNER_ID and PROJECT_ID — ownership and project association.
• DELETE_MARK — logical deletion indicator.

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are also present. The distinction between the surrogate key (ROUTING_ID) and the business-key candidate (ROUTING_NO with ROUTING_VERS) is important for de-duplication and integration logic.

Common Use Cases and Queries

Typical scenarios include locating the active routing for a given item and date, tracing routing usage across batches, and reporting yield parameters.

• Retrieve active routing headers by number and version:
  SELECT ROUTING_ID, ROUTING_NO, ROUTING_VERS, ROUTING_QTY, ROUTING_UOM FROM GMD.GMD_ROUTINGS_B WHERE ROUTING_NO = :no AND ROUTING_VERS = :vers AND NVL(DELETE_MARK,0)=0;
• List routings effective on a given date:
  SELECT ROUTING_ID, ROUTING_NO FROM GMD.GMD_ROUTINGS_B WHERE :dt BETWEEN EFFECTIVE_START_DATE AND NVL(EFFECTIVE_END_DATE, :dt+) AND INACTIVE_IND='N';
• Join to routing steps via FM_ROUT_DTL.ROUTING_ID for a step-by-step report.
• Join to PM_BTCH_HDR.ROUTING_ID to associate production batches with the routing used.
• Filter by ROUTING_CLASS using GMD_ROUTING_CLASS_B to report routings by process category, or by OWNER_ORGANIZATION_ID for organization-specific reporting.

Related Objects

• FM_ROUT_DTL — routing detail/steps table; FK column ROUTING_ID references GMD_ROUTINGS_B. The most direct child of the header.
• PM_BTCH_HDR — batch header; FK column ROUTING_ID links executed batches to their defining routing.
• GMP_FORM_EFF — formula/process effectiveness; FK column ROUTING_ID.
• GL_ACCT_MAP — GL account mapping; FK column ROUTING_ID.
• FM_TEXT_HDR — referenced by GMD_ROUTINGS_B.TEXT_CODE for narrative text.
• GMD_ROUTING_CLASS_B — referenced by GMD_ROUTINGS_B.ROUTING_CLASS for routing classification.

Together these relationships establish GMD_ROUTINGS_B as the anchor of the process routing entity, with dependent detail, batch, effectiveness, and accounting tables negotiating its lifecycle.