Search Results pm_rout_dep




Overview
Explore in AI Chat

Overview

The PM_ROUT_DEP table is a core data object within the GME (Process Manufacturing Process Execution) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves a critical function in defining and managing dependencies between steps in a non-standard manufacturing batch. Unlike standard routings, which have predefined step sequences, non-standard batches often require flexible, ad-hoc process flows. This table explicitly stores the relationships and constraints that dictate the order and conditions under which batch steps must be executed, enabling complex process scheduling and ensuring that production workflows adhere to necessary operational and safety protocols.

Key Information Stored

The table's primary key structure highlights the core data it manages, uniquely identifying a dependency for a specific batch step. The essential columns include:

  • BATCH_ID and BATCHSTEP_NO: These columns, part of the primary key, link the dependency to a specific step within a specific production batch, as recorded in the PM_ROUT_DTL table.
  • DEP_TYPE and DEP_STEP_NO: These complete the primary key. DEP_TYPE classifies the nature of the dependency (e.g., start-start, finish-start), while DEP_STEP_NO identifies the specific batch step number upon which the current step depends.
  • TEXT_CODE: A foreign key to PM_TEXT_HDR, this column allows for attaching descriptive notes or instructions to the dependency.
  • TRANSFER_UM: A foreign key to SY_UOMS_MST (Unit of Measure), this column is relevant for dependencies that involve material transfers between steps, specifying the unit of measure for the quantity to be transferred.

Common Use Cases and Queries

This table is central to batch scheduling and process control. A primary use case is generating a step execution schedule for a batch, where the Process Execution engine queries PM_ROUT_DEP to understand precedence rules before releasing steps to the shop floor. For reporting and analysis, common queries involve listing all dependencies for a batch to audit process flow or troubleshooting scheduling bottlenecks. A sample query to retrieve dependency details for a specific batch would be:

SELECT batchstep_no, dep_type, dep_step_no, text_code
FROM gme.pm_rout_dep
WHERE batch_id = :p_batch_id
ORDER BY batchstep_no;

Another critical scenario is validating data during batch step creation or modification via the GME forms, where the application checks for circular dependencies or invalid step references by querying this table.

Related Objects

PM_ROUT_DEP has integral relationships with other key GME tables, as defined by its foreign keys:

  • PM_ROUT_DTL: This is the primary parent table. PM_ROUT_DEP.BATCH_ID and .BATCHSTEP_NO reference PM_ROUT_DTL, ensuring every dependency is anchored to a valid batch step. This table holds the master list of steps for a batch.
  • PM_TEXT_HDR: The relationship via TEXT_CODE allows for storing extensive textual descriptions or instructions related to the dependency condition.
  • SY_UOMS_MST: The relationship via TRANSFER_UM ensures that any transfer quantity associated with the dependency uses a valid, defined unit of measure from the system's master list.