Results for “mtl_count_status”

8 results




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

Overview

APPS.MTL_REPLENISH_HEADERS_VIEW is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data INV.MTL_REPLENISH_HEADERS_VIEW. It belongs to the Oracle Inventory (INV) module and is used to simplify Oracle Forms coding around replenishment header processing. The view documents replenishment count headers — records that describe a replenishment counting session executed against a specific inventory organization and subinventory. Because the object type is a VIEW, it stores no data of its own; all data is rendered at runtime from its underlying base objects.

Oracle explicitly warns that this is a supplementary view and that querying or altering data through it is not recommended, since its definition may change significantly between minor or major releases. Practitioners should therefore treat it as a reporting and forms-support interface rather than as a stable integration contract. Its status is documented as VALID in both 12.1.1 and 12.2.2.

The user's search term "delivery_location" maps directly to two columns exposed by this view: DELIVERY_LOCATION_ID (NUMBER, length 15) and DELIVERY_LOCATION (VARCHAR2, length 60). These describe the ship-to or delivery destination associated with a replenishment header, typically resolved from the HR locations model.

Underlying Base Objects

The documented dependency list shows that MTL_REPLENISH_HEADERS_VIEW references four objects:

  • MTL_REPLENISH_HEADERS (SYNONYM) — the primary transactional base table supplying the replenishment header rows, identifiers, processing flags, and concurrency columns.
  • HR_LOCATIONS_ALL (SYNONYM) — the source of location attributes used to derive DELIVERY_LOCATION and DELIVERY_LOCATION_ID.
  • MFG_LOOKUPS (VIEW) — provides the lookup meaning used for STATUS_MEANING.
  • HR_GENERAL (PACKAGE) — a helper package used in formatting or lookup resolution within the view definition.

The view is not referenced by other documented objects, confirming its role as a leaf-level forms helper rather than a shared dependency.

Key Columns

Common Use Cases and Queries

Typical use is reporting on replenishment counts and their delivery destinations, and troubleshooting concurrent replenishment requests. Because delivery location is a commonly filtered attribute, queries frequently join on DELIVERY_LOCATION.

  • Locate replenishment headers by delivery location name for a given organization and subinventory.
  • Report count activity by date, status meaning, and processing outcome.
  • Diagnose failed replenishment requests using ERROR_FLAG and REQUEST_ID.

Sample query:

SELECT REPLENISHMENT_COUNT_NAME, COUNT_DATE, ORGANIZATION_ID, SUBINVENTORY_CODE, DELIVERY_LOCATION, DELIVERY_LOCATION_ID, STATUS_MEANING, PROCESS_STATUS FROM APPS.MTL_REPLENISH_HEADERS_VIEW WHERE DELIVERY_LOCATION = :p_location AND ORGANIZATION_ID = :p_org_id ORDER BY COUNT_DATE DESC;

Given Oracle's stated caution, production integrations should prefer the base table MTL_REPLENISH_HEADERS joined to HR_LOCATIONS_ALL rather than depending directly on this view.