Results for “priority_value”

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

Overview

PM_ROUT_DTL is a Process Manufacturing Process Execution (GME) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores batch routing steps. Each row represents one step within the routing of a specific batch, capturing the operation to be performed, planned and actual quantities, scheduling dates, and the current step status. Because a batch executes a routing composed of an ordered sequence of steps, PM_ROUT_DTL functions as the operational backbone linking a batch header to the individual steps that drive shop-floor execution, material consumption, and dependency sequencing.

From a dimensional modeling perspective, the mined foreign-key structure classifies this table as hub-leaning. PM_ROUT_DTL itself behaves as a hub keyed by the composite (BATCH_ID, BATCHSTEP_NO), while it is referenced by several dependent detail tables (PM_ROUT_MTL, PM_ROUT_DEP, PM_OPRN_DTL, PM_OPRN_WIP) that act as satellites or link structures. This classification is a heuristic suggestion rather than a documented physical designation, and implementers should validate it against the actual access patterns in their installation.

Key Information Stored

The table is defined in the GME schema with 56 documented columns in 12.2.2. The most operationally significant are:

• BATCH_ID — foreign key to PM_BTCH_HDR; identifies the parent batch.
• BATCHSTEP_NO — the sequence number of the step within the batch routing. Together with BATCH_ID, this forms the primary key PM_ROUT_DTL_PK.
• ROUTINGSTEP_ID — foreign key to FM_ROUT_DTL, tying the batch step back to its master routing definition.
• OPRN_ID — foreign key to FM_OPRN_MST, identifying the operation performed at this step.
• PLAN_STEP_QTY and ACTUAL_STEP_QTY — planned versus actual quantity processed at the step.
• BACKFLUSH_QTY — quantity consumed through backflush logic.
• PLAN_START_DATE, ACTUAL_START_DATE, DUE_DATE, EXPCT_CMPLT_DATE, ACTUAL_CMPLT_DATE, STEP_CLOSE_DATE — the scheduling and completion timeline of the step.
• STEP_STATUS and STEPRELEASE_TYPE — control flags governing release and progress.
• TEXT_CODE — foreign key to PC_TEXT_HDR for step-level instructions.
• DELETE_MARK and IN_USE — standard Oracle soft-delete and concurrency indicators.

The composite primary key (BATCH_ID, BATCHSTEP_NO) is the true unique business key; there is no separate surrogate sequence column documented. The ATTRIBUTE1–30, ATTRIBUTE_CATEGORY, and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) provide the extensibility and audit framework.

Common Use Cases and Queries

Typical scenarios include batch status reporting, shop-floor dispatch, and step-dependency resolution. A common pattern retrieves all steps for a batch in execution order:

• SELECT BATCHSTEP_NO, OPRN_ID, STEP_STATUS, PLAN_STEP_QTY, ACTUAL_STEP_QTY FROM PM_ROUT_DTL WHERE BATCH_ID = :p_batch AND NVL(DELETE_MARK,0) = 0 ORDER BY BATCHSTEP_NO;

To trace a batch step against its master routing definition, join to FM_ROUT_DTL on ROUTINGSTEP_ID. To identify open versus completed steps for a work-center view, filter on STEP_STATUS and compare ACTUAL_CMPLT_DATE to EXPCT_CMPLT_DATE. Reporting on step-level material consumption joins PM_ROUT_MTL on (BATCH_ID, BATCHSTEP_NO), while dependency analysis joins PM_ROUT_DEP on the same composite key.

Related Objects

• PM_BTCH_HDR — parent batch header; joined on BATCH_ID.
• FM_ROUT_DTL — master routing step definition; joined on ROUTINGSTEP_ID.
• FM_OPRN_MST — operation master; joined on OPRN_ID.
• PM_ROUT_MTL — step-level material requirements; joined on BATCH_ID, BATCHSTEP_NO.
• PM_ROUT_DEP — step dependencies; joined on BATCH_ID, BATCHSTEP_NO.
• PM_OPRN_DTL — operation detail; joined on BATCH_ID, BATCHSTEP_NO.
• PM_OPRN_WIP — work-in-process operation records; joined on BATCH_ID with BATCHSTEP_NO and TRANSFER_STEP_NO.
• PC_TEXT_HDR — step text/instructions; joined on TEXT_CODE.