Search Results mtl_rtg_item_revisions

Overview

The MTL_RTG_ITEM_REVISIONS table is a core data repository within the Oracle E-Business Suite (EBS) Inventory (INV) module, specifically for releases 12.1.1 and 12.2.2. It serves as the master table for storing and managing revision-level information for item routings. A routing defines the sequence of manufacturing operations required to produce an assembly. This table enables the control and tracking of different versions or revisions of these routings over time, which is critical for managing engineering changes, maintaining production consistency, and ensuring accurate costing and scheduling in discrete manufacturing and flow manufacturing environments.

Key Information Stored

The table's primary key uniquely identifies a routing revision through a combination of INVENTORY_ITEM_ID, ORGANIZATION_ID, and PROCESS_REVISION. This structure allows multiple revisions of a routing to exist for the same item within a specific manufacturing organization. While the provided metadata does not list all columns, the foreign key relationships indicate the presence of critical fields. The CHANGE_NOTICE column links the routing revision to a specific engineering change order (ECO) documented in the ENG_ENGINEERING_CHANGES table, providing an audit trail for the revision's origin. Other implied columns would typically include metadata such as EFFECTIVITY_DATE (specifying when the revision becomes active), REVISION_DATE, and descriptive attributes for the revision.

Common Use Cases and Queries

The primary use case is to query the valid routing revision for a given item and organization, often for integration with manufacturing execution. This is essential when creating discrete jobs or flow schedules, as these manufacturing entities reference a specific routing revision. A common reporting need is to list all routing revisions for an item, including their effective dates and associated engineering change notices, to analyze the revision history. Sample SQL to retrieve the current effective routing revision for an item would join this table with item and organization master tables, filtering on the current date relative to the revision's effectivity. Another critical query involves validating that a routing revision referenced on an open work order (WIP_DISCRETE_JOBS or WIP_FLOW_SCHEDULES) still exists in this master table.

Related Objects

MTL_RTG_ITEM_REVISIONS is centrally connected to several key manufacturing and engineering tables. Its primary foreign key relationships are:

• ENG_ENGINEERING_CHANGES: Links a routing revision to its authorizing engineering change notice.
• MTL_PARAMETERS: Validates the ORGANIZATION_ID against defined inventory organizations.
• WIP_DISCRETE_JOBS: The routing revision specified on a discrete job must exist in this table, linked via PRIMARY_ITEM_ID, ORGANIZATION_ID, and ROUTING_REVISION.
• WIP_FLOW_SCHEDULES: Similar to discrete jobs, flow schedules reference a valid routing revision from this table.

This table is also the likely parent for detailed routing operation data stored in tables such as BOM_OPERATION_ROUTINGS, which define the specific steps within the revision.