Results for “pm_rout_mtl”

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

Overview

PM_ROUT_MTL is a table owned by the GME schema within Oracle E-Business Suite, belonging to the Process Manufacturing Process Execution product family. Its documented description is "Batch steps to batch lines relationships," which positions it as an associative entity that connects the routing (batch step) definition of a production batch to the material lines consumed or produced at those steps. In ETRM 12.1.1 and 12.2.2, this object serves as the operational bridge between how a batch is executed step-by-step and which material lines are associated with each step.

Under the heuristic Data Vault classification mined from its foreign key structure, PM_ROUT_MTL is modeled as a link. This is consistent with its role: the table does not describe a single business entity but instead records the relationship between a batch step (identified by BATCH_ID and BATCHSTEP_NO referencing PM_ROUT_DTL) and a batch line (identified by BATCHLINE_ID). Presenting it as a link table in a Data Vault model would allow the batch step and batch line hubs to be resolved independently while this table captures their association.

Key Information Stored

The table contains nine documented physical columns. The most significant are:

• BATCHLINE_ID — the surrogate primary key column defining the PM_ROUT_MTL_PK constraint. It uniquely identifies each batch step-to-line association row and is the primary join key used throughout the Process Execution module.
• BATCH_ID — the batch identifier that ties the record to the production batch. It participates in foreign keys to both PM_MATL_DTL and PM_ROUT_DTL, serving as a business-key candidate alongside BATCHSTEP_NO.
• BATCHSTEP_NO — the batch step number, forming the second component of the relationship to PM_ROUT_DTL. Together with BATCH_ID, it identifies the specific routing step associated with the batch line.
• TEXT_CODE — a foreign key reference to PM_TEXT_HDR, used to attach descriptive text or notes to the batch step-to-line relationship.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, which provide standard Oracle EBS audit trail information for each row.

While BATCHLINE_ID is the documented surrogate primary key, the combination of BATCH_ID and BATCHSTEP_NO functions as the practical business-key candidate that links the record back to routing and material detail records.

Common Use Cases and Queries

Typical reporting and integration scenarios involve resolving which material lines belong to which batch step, or tracing a text note back to its batch step-to-line association. Because the table's FK chain reaches PM_MATL_DTL, PM_ROUT_DTL, and PM_TEXT_HDR, queries frequently join across all three.

A representative pattern to list batch steps with their associated material lines:

• SELECT r.BATCH_ID, r.BATCHSTEP_NO, r.BATCHLINE_ID, m.MATERIAL_DETAIL_ID FROM PM_ROUT_MTL r JOIN PM_MATL_DTL m ON r.BATCH_ID = m.BATCH_ID WHERE r.BATCH_ID = :batch_id;
• SELECT r.BATCH_ID, r.BATCHSTEP_NO, t.TEXT_CODE FROM PM_ROUT_MTL r JOIN PM_TEXT_HDR t ON r.TEXT_CODE = t.TEXT_CODE WHERE r.BATCHLINE_ID = :batchline_id;
• SELECT r.* FROM PM_ROUT_MTL r JOIN PM_ROUT_DTL d ON r.BATCH_ID = d.BATCH_ID AND r.BATCHSTEP_NO = d.BATCHSTEP_NO WHERE r.BATCHLINE_ID = :batchline_id;

These patterns support shop-floor execution reporting, batch genealogy and traceability, and validation of material consumption against routing steps.

Related Objects

The following objects are the most significant references to PM_ROUT_MTL based on the documented foreign key relationships:

• PM_MATL_DTL — joined on PM_ROUT_MTL.BATCH_ID; provides the batch material detail lines associated with the step, and is the primary source of material consumption data.
• PM_ROUT_DTL — joined on PM_ROUT_MTL.BATCH_ID and PM_ROUT_MTL.BATCHSTEP_NO; supplies the routing or batch step definition that PM_ROUT_MTL associates with each batch line.
• PM_TEXT_HDR — joined on PM_ROUT_MTL.TEXT_CODE; holds the descriptive text header referenced by the association.

In practice, these tables appear together in Process Execution queries, and any ETL or reporting layer built for batch traceability should preserve the BATCH_ID, BATCHSTEP_NO, and BATCHLINE_ID keys to maintain row-level integrity across the GME schema.