Results for “mtl_replenish_lines”

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

Overview

MTL_REPLENISH_LINES is an Inventory (INV) module table in the Oracle E-Business Suite that stores replenishment line information. It holds the detail records underlying replenishment activity, sitting beneath the replenishment header as the transactional grain of the replenishment process. Each row represents a single replenishment line, capturing the item, organization, quantity, unit of measure, and sourcing attributes required to move or reorder material.

The table is owned by the INV schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. It is a child of MTL_REPLENISH_HEADERS, tied by the REPLENISHMENT_HEADER_ID column, and it references master item, organization, subinventory, and locator definitions via a well-defined set of foreign keys. Given the mined Data Vault classification of link, this table is best modeled as a link/association table: it resolves and records the relationship between a replenishment header and the inventory item (and organization) being replenished, rather than acting as a standalone hub or a descriptive satellite. This classification should be treated as a heuristic modeling suggestion derived from the FK topology, not as a physical database constraint.

Key Information Stored

The table contains 31 documented columns. Its surrogate primary key is REPLENISHMENT_LINE_ID, which uniquely identifies each line. The unique index MTL_REPLENISH_LINES_U1 covers the composite of REPLENISHMENT_HEADER_ID and REPLENISHMENT_LINE_ID, establishing the business-key candidate that ties each line unambiguously to its parent header. The most significant columns include:

• REPLENISHMENT_HEADER_ID — the parent header this line belongs to.
• INVENTORY_ITEM_ID — the item being replenished.
• ORGANIZATION_ID — the inventory organization context for the line.
• COUNT_TYPE_CODE — the type of count associated with the replenishment.
• COUNT_QUANTITY, COUNT_UOM_CODE — counted quantity and its unit of measure.
• SUPPLY_QUANTITY — the quantity available or supplied for the line.
• SOURCE_TYPE — indicates the source (e.g., subinventory, organization) for the replenishment.
• SOURCE_ORGANIZATION_ID, SOURCE_SUBINVENTORY — the originating organization and subinventory.
• REORDER_QUANTITY — the quantity to reorder or move.
• PRIMARY_UOM_COUNT_QUANTITY, PRIMARY_UOM_CODE — quantities expressed in the primary UOM.
• SECONDARY_UOM_COUNT_QUANTITY, SECONDARY_UOM_CODE — quantities in the secondary UOM.
• LOCATOR_ID — the item location (locator) for the line.
• ERROR_FLAG, REQUEST_ID, PROGRAM_ID — processing and concurrent-program status fields.

Standard audit columns (LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

Typical uses include reporting replenishment line detail, auditing replenishment runs, reconciling counted versus reordered quantities, and tracing lines to their source subinventory or organization. A common query joins lines to headers and items:

• Retrieve all lines for a given header: SELECT * FROM MTL_REPLENISH_LINES WHERE REPLENISHMENT_HEADER_ID = :header_id;
• Resolve item descriptions: join INVENTORY_ITEM_ID to MTL_SYSTEM_ITEMS_B.
• Identify lines with errors: filter on ERROR_FLAG or REQUEST_ID to trace the concurrent program that generated the replenishment.
• Report replenishment demand by source: group on SOURCE_TYPE, SOURCE_ORGANIZATION_ID, and SOURCE_SUBINVENTORY.

Related Objects

• MTL_REPLENISH_HEADERS — parent table, joined on REPLENISHMENT_HEADER_ID.
• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID for item attributes.
• MTL_PARAMETERS — joined on ORGANIZATION_ID and SOURCE_ORGANIZATION_ID.
• MTL_SECONDARY_INVENTORIES — joined on SOURCE_SUBINVENTORY (and organization).
• MTL_ITEM_LOCATIONS — joined on LOCATOR_ID (and organization).

These foreign-key relationships define the referential integrity of the replenishment line and provide the primary join paths for reporting and integration.