Results for “mtl_replenish_headers_view”

18 results




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

Overview

MTL_REPLENISH_HEADERS_VIEW is a seeded Oracle E-Business Suite view owned by the APPS schema and registered under the Inventory (INV) product module. It is a retrofitted view, meaning it was introduced or adapted to preserve backward compatibility within the ETRM (E-Business Suite Technical Reference Manual) data model across releases. The view presents replenishment count header information — the top-level records that govern replenishment counting activities within an inventory organization and subinventory — consolidating replenishment header attributes with status meaning derived from Oracle lookups and delivery location details.

The object referenced in the user's search, process_status, is a central column of this view. It operates as a foreign key to the MTL_COUNT_STATUS lookup type and drives the WORKFLOW/Concurrent Manager processing state of a replenishment count — for example whether a count is pending, in progress, completed, or in error. Because the view joins PROCESS_STATUS to MFG_LOOKUPS to return a human-readable MEANING, it is well suited to reporting and integration scenarios where status must be presented rather than decoded by the consumer.

Underlying Base Objects

The view is defined over the following documented base objects:

The view also carries ROWID from MTL_REPLENISH_HEADERS, enabling row-level addressing of the underlying table through the view in supported update paths.

Key Columns

  • REPLENISHMENT_HEADER_ID — primary identifier of the replenishment count header.
  • REPLENISHMENT_COUNT_NAME and COUNT_DATE — the user-assigned name and the scheduled/actual date of the count.
  • PROCESS_STATUS — the coded processing state, decoded against MTL_COUNT_STATUS.
  • STATUS_MEANING — the decoded, display-ready description of PROCESS_STATUS.
  • PROCESS_MODE — indicates how the count is processed.
  • ERROR_FLAG — signals whether the underlying concurrent process encountered an error.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context for the job that last processed the header.
  • ORGANIZATION_ID and SUBINVENTORY_CODE — the inventory organization and subinventory scope.
  • DELIVERY_LOCATION_ID and DELIVERY_LOCATION — the delivery location identifier and its decoded location code.
  • COUNT_MODE, DEFAULT_COUNT_TYPE_CODE, DEFAULT_LINE_ITEMS — counting behavior and defaults.

Common Use Cases and Queries

Because the view decodes status and location in a single query, it is commonly used for replenishment count monitoring, operational dashboards, and integration extracts.

  • Listing all incomplete or errored counts for an organization.
  • Reporting count progress by subinventory or delivery location.
  • Extracting concurrent program context to trace which request processed a header.

Representative query:

SELECT replenishment_header_id, replenishment_count_name, count_date, organization_id, subinventory_code, process_status, status_meaning, error_flag, request_id FROM apps.mtl_replenish_headers_view WHERE process_status != 'COMPLETE' AND organization_id = :p_org_id ORDER BY count_date DESC;

To find count records associated with a specific concurrent request, filter on REQUEST_ID. Because PROCESS_STATUS is populated from the base table while STATUS_MEANING is derived from MFG_LOOKUPS, querying the view guarantees consistent decoded status values without additional joins, making it the preferred interface for both custom reports and inbound/outbound integration logic.