Search Results mtl_item_revisions_b




Overview
Explore in AI Chat

Overview

The MTL_ITEM_REVISIONS_B table is a core data repository within the Oracle E-Business Suite Inventory (INV) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master table for storing all revision-level information for inventory items. The table's primary role is to manage the lifecycle of an item by tracking its engineering or manufacturing revisions, enabling precise control over which specific revision of an item is used in transactions, planning, and costing. Its existence is critical for organizations in manufacturing, engineering, and discrete industries where product designs and specifications evolve over time.

Key Information Stored

The table's structure is centered on uniquely identifying a revision for a specific item within an organization. The primary key is a composite of INVENTORY_ITEM_ID, ORGANIZATION_ID, and REVISION_ID, ensuring each revision record is distinct. Key columns include REVISION (the alphanumeric revision code, e.g., 'A', 'B', '1.1'), EFFECTIVITY_DATE (the date from which the revision becomes active), and IMPLEMENTATION_DATE (the date the revision was implemented). The table also links to engineering change orders via the CHANGE_NOTICE column, which references the ENG_ENGINEERING_CHANGES table. This establishes a formal audit trail from engineering change to item revision.

Common Use Cases and Queries

A primary use case is validating and controlling item revisions during material transactions, such as issues, receipts, and transfers. The system consults this table to ensure the revision used is effective for the transaction date. Common reporting needs include listing all revisions for an item or identifying the current effective revision. Sample queries include fetching all revisions for a specific item:

  • SELECT revision, effectivity_date FROM mtl_item_revisions_b WHERE inventory_item_id = 12345 AND organization_id = 101 ORDER BY effectivity_date;

Another critical use is in interfaces and data loads, where the MTL_ITEM_REVISIONS_B table must be populated via the appropriate Oracle APIs (e.g., INV_ITEM_REVISION_PUB) before transactional data referencing a new revision can be processed successfully.

Related Objects

As indicated by the foreign key relationships, MTL_ITEM_REVISIONS_B is integral to numerous transactional and planning processes. It has a fundamental foreign key relationship to MTL_SYSTEM_ITEMS_B, anchoring each revision to a master item. Key dependent tables include:

This extensive integration underscores the table's central role in ensuring revision control propagates consistently across manufacturing, inventory, planning, and service modules.