Search Results high_date




Overview
Explore in AI Chat

Overview

APPS.MTL_ROUTING_REV_HIGHDATE_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its FND Design Data reference is INV.MTL_ROUTING_REV_HIGHDATE_V, confirming that it belongs to the Oracle Inventory (INV) product family. The view exposes routing revision and effectivity information for inventory items, including a synthetic "high date" boundary that marks the upper limit of a revision's effective range. Because it carries the standard Oracle internal-use warning, it is intended for consumption by Oracle Applications programs and by extensions that follow supported development standards rather than for ad-hoc end-user reporting.

The object is documented as VALID and has an "Internal" view type. It is a lightweight, denormalized projection: the query text simply selects six columns from an underlying synonym. Its main architectural value is that it isolates the high-date logic for routing revisions, allowing downstream views and concurrent programs to reuse a consistent definition of revision validity windows instead of recoding the range boundary each time.

Underlying Base Objects

The documented dependency for MTL_ROUTING_REV_HIGHDATE_V is the base object MTL_RTG_ITEM_REVISIONS, exposed to APPS through a SYNONYM. MTL_RTG_ITEM_REVISIONS is the Inventory table that stores routing revisions and their effectivity dates for items and organizations. The view does not introduce joins to additional tables; it derives entirely from that single source, which keeps its row cardinality identical to the qualifying rows in the base table while adding the HIGH_DATE column presentation.

The view is referenced by several dependent objects, notably MRP_VALIDATE_FLOW_SCHEDULE, WIP_FLOW_ASSEMBLIES_V, WIP_FLOW_ASSEMBLY_EVENTS_V, WIP_PCB_FLOW_ASSEMBLIES_V, and WIP_PCB_FLOW_ASSEMBLY_EVENTS_V. This dependency pattern shows that the view serves as a common revision-validity access point for both material planning (MRP) validation logic and Work in Process (WIP) flow assembly reporting, including flow manufacturing and printed circuit board variants.

Key Columns

  • ORGANIZATION_ID (NUMBER) — Identifies the inventory organization in which the routing revision is defined. This is the primary partitioning key for multi-organization queries.
  • INVENTORY_ITEM_ID (NUMBER) — The item for which the routing revision applies. Joins to MTL_SYSTEM_ITEMS_B on INVENTORY_ITEM_ID and ORGANIZATION_ID.
  • PROCESS_REVISION (VARCHAR2) — The revision code or version label of the routing, used to distinguish successive routings for the same item.
  • EFFECTIVITY_DATE (DATE) — The date on which the revision becomes effective.
  • HIGH_DATE (DATE) — The upper boundary date of the revision's effective range. This is the column that gives the view its name and its purpose: it defines when a revision ceases to be the active one, supporting point-in-time revision resolution.
  • IMPLEMENTATION_DATE (DATE) — The date the revision was implemented, which may differ from the effectivity date and is useful for audit and change-history analysis.

Common Use Cases and Queries

Typical scenarios include determining which routing revision was active for an item on a given manufacturing date, validating that a flow schedule references a revision within its effective window, and auditing revision histories for engineering change control. The view is also a convenient substitute for direct access to MTL_RTG_ITEM_REVISIONS when only effectivity and high-date fields are required.

To list all routing revisions for a specific item and organization, ordered by effective date:

SELECT organization_id, inventory_item_id, process_revision, effectivity_date, high_date, implementation_date FROM apps.mtl_routing_rev_highdate_v WHERE organization_id = :org_id AND inventory_item_id = :item_id ORDER BY effectivity_date;

To identify the revision effective on a specific date, filter such that the target date falls between the effectivity and high dates:

SELECT process_revision, effectivity_date, high_date FROM apps.mtl_routing_rev_highdate_v WHERE organization_id = :org_id AND inventory_item_id = :item_id AND :as_of_date BETWEEN effectivity_date AND NVL(high_date, TO_DATE('4712-12-31','YYYY-MM-DD'));

Because the object is flagged for Oracle internal use, custom SQL should treat it as a read-only source, avoid DDL or direct DML, and be revalidated after patching or upgrades, since dependent WIP and MRP objects may change the underlying definition in future releases.