Results for “pm_rout_dep”

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

Overview

PM_ROUT_DEP is a GME (Process Manufacturing Process Execution) table that stores non-standard dependencies between batch steps on a routing. In Oracle EBS 12.1.1 and 12.2.2, it is owned by the GME schema and carries a VALID status. The table captures conditional relationships that govern how one batch step must wait for, rework from, or transfer quantities to another step — logic that goes beyond the standard linear sequencing recorded in PM_ROUT_DTL.

Under the heuristic Data Vault classification mined from its foreign key structure, PM_ROUT_DEP is modeled as a link. This suggests the table functions as an associative entity connecting a routing detail (the owning batch step) to a dependent batch step, enriched with type and timing attributes. The composite primary key PM_ROUT_DEP_PK, defined over BATCH_ID, BATCHSTEP_NO, DEP_TYPE, and DEP_STEP_NO, reinforces this interpretation.

Key Information Stored

The table contains 16 documented columns. The most significant are the following:

• BATCH_ID — Identifies the batch or routing instance to which the dependency belongs; part of the primary key and a foreign key to PM_ROUT_DTL.
• BATCHSTEP_NO — The batch step that owns the dependency; part of the primary key and a foreign key to PM_ROUT_DTL.
• DEP_TYPE — The dependency type (the value the user searched for). It discriminates the kind of non-standard relationship, such as rework or transfer, and forms part of the composite primary key.
• DEP_STEP_NO — The dependent batch step referenced by the relationship; completes the primary key.
• REWORK_CODE — Classifies rework behavior associated with the dependency.
• STANDARD_DELAY, MIN_DELAY, MAX_DELAY — Timing thresholds controlling how long the dependent step may or must wait.
• TRANSFER_QTY and TRANSFER_UM — Quantity and unit of measure moved between steps; TRANSFER_UM is a foreign key to SY_UOMS_MST.
• TEXT_CODE — Foreign key to PM_TEXT_HDR, linking free-form descriptive text to the dependency.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — Standard audit columns.

The surrogate primary key is PM_ROUT_DEP_PK. Because it spans BATCH_ID, BATCHSTEP_NO, DEP_TYPE, and DEP_STEP_NO, those columns collectively act as the business key; no separate single-column uniqueness is documented.

Common Use Cases and Queries

Typical scenarios include identifying rework loops, validating delay tolerances between steps, and reporting quantity transfers across a routing. A representative query lists dependencies by type for a given batch:

SELECT batch_id, batchstep_no, dep_type, dep_step_no, rework_code, standard_delay, min_delay, max_delay FROM gme.pm_rout_dep WHERE batch_id = :batch_id AND dep_type = :dep_type;

Additional patterns join to PM_ROUT_DTL to resolve step descriptions, to SY_UOMS_MST to decode TRANSFER_UM, and filter on TRANSFER_QTY to analyze material movement. Reporting use cases include dependency matrices for scheduling and exception reports on missing or conflicting delay ranges.

Related Objects

• PM_ROUT_DTL — Referenced via PM_ROUT_DEP.BATCH_ID and PM_ROUT_DEP.BATCHSTEP_NO; the primary parent of routing steps.
• PM_TEXT_HDR — Referenced via PM_ROUT_DEP.TEXT_CODE for descriptive text.
• SY_UOMS_MST — Referenced via PM_ROUT_DEP.TRANSFER_UM for unit-of-measure validation.

These foreign key relationships define the core dependency graph around PM_ROUT_DEP and should guide joins in any custom reporting or extension built on this table.