Results for “mtl_replenish_headers”

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

Overview

MTL_REPLENISH_HEADERS is the header-level table for the Oracle Inventory (INV) replenishment and replenishment counting process. It is owned by the INV schema and is classified as VALID in Oracle EBS 12.1.1 and 12.2.2. The table stores the control and status information that drives a replenishment count — a cycle-count-style process used to compare on-hand quantities against system records and to generate replenishment or requisition demand. Each row represents a single replenishment count event, identified by a surrogate key and by a user-defined count name.

Under the ETRM relationship metadata, MTL_REPLENISH_HEADERS is classified heuristically as satellite-leaning. In Data Vault modeling terms, this suggests the table functions primarily as a satellite describing the attributes of a replenishment count, while its foreign keys to organizational and location masters (MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, HR_LOCATIONS_ALL) anchor it to hub or link structures. The child table MTL_REPLENISH_LINES depends on this header, forming a classic header-detail parent relationship.

Key Information Stored

The table contains 23 documented columns. The most significant include:

• REPLENISHMENT_HEADER_ID — surrogate primary key (MTL_REPLENISH_HEADERS_PK); uniquely identifies each replenishment count header.
• REPLENISHMENT_COUNT_NAME — business-key candidate (unique index MTL_REPLENISH_HEADERS_U2); the user-facing name of the count event.
• ORGANIZATION_ID — foreign key to MTL_PARAMETERS; identifies the inventory organization in which the count is executed.
• SUBINVENTORY_CODE — foreign key to MTL_SECONDARY_INVENTORIES; scopes the count to a specific subinventory.
• DELIVERY_LOCATION_ID — foreign key to HR_LOCATIONS_ALL; the delivery location associated with the count.
• COUNT_DATE — the date on which the count is scheduled or performed.
• SUPPLY_CUTOFF_DATE — cutoff date governing which supply transactions are considered.
• REQUISITION_APPROVAL_TYPE — controls the approval routing for generated requisitions.
• COUNT_MODE and DEFAULT_COUNT_TYPE_CODE — define how the count is executed and its default counting type.
• DEFAULT_LINE_ITEMS — indicates whether default line items are generated.
• PROCESS_STATUS, PROCESS_MODE, ERROR_FLAG — track the processing lifecycle and outcome of the count.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context for the run that created or last processed the header.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include reconciling replenishment count activity for an organization/subinventory, monitoring concurrent request outcomes, and reporting on approval status and count mode.

Join the header to its lines:

• SELECT h.replenishment_count_name, l.* FROM mtl_replenish_headers h, mtl_replenish_lines l WHERE h.replenishment_header_id = l.replenishment_header_id;

Filter by organization and subinventory:

• SELECT * FROM mtl_replenish_headers WHERE organization_id = :org AND subinventory_code = :sub;

Check processing errors:

• SELECT replenishment_count_name, process_status, error_flag FROM mtl_replenish_headers WHERE error_flag = 'Y';

Related Objects

• MTL_REPLENISH_LINES — child table; joins on REPLENISHMENT_HEADER_ID.
• MTL_PARAMETERS — inventory organization master; joins on ORGANIZATION_ID.
• MTL_SECONDARY_INVENTORIES — subinventory master; joins on SUBINVENTORY_CODE.
• HR_LOCATIONS_ALL — delivery location master; joins on DELIVERY_LOCATION_ID.
• FND_CONCURRENT_REQUESTS — concurrent program context via REQUEST_ID.