Results for “mtl_replenishment_error”

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

Overview

APPS.MTL_REPLENISH_LINES_VIEW is a reporting and integration view over the replenishment line data maintained by Oracle Inventory in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents replenishment line records at the item, organization, and source level together with descriptive attributes that are not stored directly on the transaction table, including item segment, item description, and lookup meaning. The view is significant in the context of the search term "mtl_replenishment_error" because it exposes the ERROR_FLAG column of the underlying MTL_REPLENISH_LINES table and resolves that flag to a human-readable value through MFG_LOOKUPS using the lookup type MTL_REPLENISHMENT_ERROR. This makes it the primary object through which replenishment processing failures can be diagnosed from a query or concurrent program.

The view is defined as a UNION ALL of two branches. The first branch filters records where LOCATOR_ID IS NULL, and the second branch handles records with a locator assigned. This structure reflects the distinction between items not under locator control and items maintained within specific locators, allowing both categories of replenishment lines to be reported through a single interface.

Underlying Base Objects

ETRM documentation for 12.2.2 identifies the referenced base objects as MTL_REPLENISH_LINES (synonym), MTL_SYSTEM_ITEMS (synonym), MFG_LOOKUPS (view), and MTL_ITEM_LOCATIONS (synonym). The view joins MTL_REPLENISH_LINES to MTL_SYSTEM_ITEMS on both INVENTORY_ITEM_ID and ORGANIZATION_ID, which enforces that the item definition and the replenishment line belong to the same inventory organization. MFG_LOOKUPS is joined with an outer join (LOOKUP_TYPE (+) = 'MTL_REPLENISHMENT_ERROR' and LOOKUP_CODE (+) = ERROR_FLAG), so lines without an error still return and simply yield a null meaning. MTL_ITEM_LOCATIONS is used in the locator-based branch of the union, where LOCATOR_ID is not null.

Key Columns

• REPLENISHMENT_LINE_ID / REPLENISHMENT_HEADER_ID — Identifiers linking the line to its replenishment header.
• ORGANIZATION_ID / INVENTORY_ITEM_ID — Organization and item keys, with SEGMENT1 and DESCRIPTION supplied from MTL_SYSTEM_ITEMS.
• COUNT_TYPE_CODE, COUNT_QUANTITY, COUNT_UOM_CODE, PRIMARY_UOM_COUNT_QUANTITY, PRIMARY_UOM_CODE — Count results and UOM information recorded against the line.
• SUPPLY_QUANTITY, REORDER_QUANTITY — Replenishment quantities calculated for the line.
• SOURCE_TYPE, SOURCE_ORGANIZATION_ID, SOURCE_SUBINVENTORY — The supply source used for replenishment.
• EXPENSE_ACCOUNT, ENCUMBRANCE_ACCOUNT — Accounting references associated with the line.
• ERROR_FLAG and MEANING — The error code and its resolved lookup meaning; central to troubleshooting "mtl_replenishment_error".
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent request and program audit columns identifying the process that last wrote the row.
• LOCATOR_ID, TASK_ID, REFERENCE — Locator, task, and reference context for the line.

Common Use Cases and Queries

The most frequent use is identifying lines that failed during replenishment processing, since the view resolves the error flag to descriptive text.

• Linking replenishment errors to their concurrent request for root cause analysis.
• Reporting replenishment demand and supply by organization, item, or subinventory, including item descriptions without a separate join.
• Auditing lines by accounting references (EXPENSE_ACCOUNT, ENCUMBRANCE_ACCOUNT).
• Filtering by locator-controlled versus non-locator-controlled lines across the two union branches.

Sample query returning failed replenishment lines with descriptive error text:

SELECT organization_id,
       segment1,
       description,
       inventory_item_id,
       error_flag,
       meaning,
       request_id,
       program_id,
       program_update_date
FROM   apps.mtl_replenish_lines_view
WHERE  error_flag IS NOT NULL
ORDER BY program_update_date DESC;