Search Results row_status_flag




Overview

APPS.MTL_RESERVATIONS_VIEW is a reporting and integration view within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes active material reservations against demand records. It is defined over the MTL_DEMAND base table and is designed to return a consolidated, presentation-ready set of reservation rows without requiring consuming applications or reports to reapply the underlying filtering logic. In effect, the view acts as a stable, read-only interface that surfaces only those demand rows that represent genuine, outstanding reservations.

The view is particularly relevant where applications or interfaces need to identify reserved quantities linked to a sales order, a work order component, or an internal requisition. Because the view encapsulates the filter predicate on ROW_STATUS_FLAG, querying it avoids common pitfalls associated with manual queries against MTL_DEMAND, where the analyst must independently determine which demand rows are currently active.

Underlying Base Objects

The documented metadata identifies MTL_DEMAND (accessed via a SYNONYM in the APPS schema) as the sole referenced base object. MTL_DEMAND is the central repository for demand and reservation records in Oracle Inventory, capturing both the requirement side and the associated supply-side references. MTL_RESERVATIONS_VIEW does not aggregate, join, or transform this table beyond column aliasing and numeric conversion; it is a filtered projection.

Four predicates define the view’s contents: RESERVATION_TYPE = 2 (restricting output to reservations), ROW_STATUS_FLAG = 1 (restricting output to active rows, excluding soft-deleted or inactive records), PARENT_DEMAND_ID IS NOT NULL (excluding top-level demand and returning only child reservation rows), and PRIMARY_UOM_QUANTITY - COMPLETED_QUANTITY != 0 (excluding fully satisfied or zero-balance reservations).

Key Columns

The view exposes the following principal columns:

Common Use Cases and Queries

The ROW_STATUS_FLAG predicate is the most frequent point of investigation for users searching this object, since its value determines whether a reservation appears at all. A typical query to find all active reservations for a specific item and organization is:

SELECT organization_id, inventory_item_id,
       demand_source_header_id, demand_source_line_id,
       primary_reservation_quantity, subinventory_code, locator_id
FROM   apps.mtl_reservations_view
WHERE  organization_id = :org_id
AND    inventory_item_id = :item_id;

To trace reservations tied to a specific sales order line, filter on DEMAND_SOURCE_HEADER_ID and DEMAND_SOURCE_LINE_ID. To identify reserved material sitting in a particular subinventory or locator, add SUBINVENTORY_CODE or LOCATOR_ID predicates.

Because the view already excludes zero-balance and inactive demand rows, it is commonly used in custom reporting, alert queries, and integration extracts where only currently outstanding reservations are meaningful. Analysts should note that any demand record with ROW_STATUS_FLAG other than 1 will be invisible through this view, so troubleshooting a “missing reservation” should always begin by querying MTL_DEMAND directly against that flag.