Search Results required_date

Overview

The APPS.INVBV_INVENTORY_RESERVATIONS view is a retrofitted Oracle Inventory (INV) reporting object that presents active material reservations held against demand in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a read-only, security-enabled view defined over MTL_DEMAND and MTL_SYSTEM_ITEMS, and it exposes reservation detail by organization, item, demand source, and requirement date. In EBS, the view primarily serves on-hand / available-to-promise (ATP) inquiries, shipping and order-management reporting, and integration extracts where downstream systems require visibility of what inventory has been hard-reserved but not yet issued. The view is registered with status VALID and is owned by APPS, meaning it is accessible to custom concurrent programs, Oracle Reports, OAF pages, and BI Publisher templates that run with APPS-equivalent privileges, subject to the organization-level security predicate embedded in its definition.

Underlying Base Objects

According to the documented metadata, the view references three objects: the package INV_CONVERT (specifically the INV_UM_CONVERT function), and the synonyms MTL_DEMAND and MTL_SYSTEM_ITEMS, which resolve respectively to the base tables MTL_DEMAND and MTL_SYSTEM_ITEMS. The join is an equi-join on ORGANIZATION_ID and INVENTORY_ITEM_ID, ensuring each reservation row is enriched with the item's PRIMARY_UOM_CODE for unit-of-measure conversion. The WHERE clause restricts the result set to RESERVATION_TYPE = 2 (hard reservations) and to demand sources of 2, 8, 12 (sales order related), 3 (account), 6 (account alias), 13, or any source type greater than 99 (custom/external demand). A further filter excludes rows where PRIMARY_UOM_QUANTITY minus COMPLETED_QUANTITY is not greater than zero, so fully issued reservations are omitted. A security predicate of the form '_SEC:M.ORGANIZATION_ID' IS NOT NULL enforces organization access, and the view is declared WITH READ ONLY.

Key Columns

• DEMAND_ID — Primary identifier of the MTL_DEMAND row backing the reservation.
• ORGANIZATION_ID / INVENTORY_ITEM_ID — Reservation context; the inventory organization and item.
• REQUIRED_DATE — Requirement date from MTL_DEMAND.REQUIREMENT_DATE, the column most commonly searched (e.g., "required_date").
• DEMAND_SOURCE_TYPE / DEMAND_SOURCE_HEADER_ID — Classifies the source and identifies its header.
• SALES_ORDER_ID, ACCOUNT_ID, ACCOUNT_ALIAS_ID — Decoded from DEMAND_SOURCE_HEADER_ID for source types 2/8/12, 3, and 6 respectively.
• DEMAND_SOURCE_NAME — Populated only for source types outside the known set.
• UOM, RESERVED_QUANTITY, ISSUED_QUANTITY, PENDING_ISSUE_QUANTITY — Quantity and conversion metrics; ISSUED_QUANTITY applies INV_UM_CONVERT to COMPLETED_QUANTITY, and PENDING_ISSUE_QUANTITY is the residual.
• REVISION, LOT_NUMBER, SUBINVENTORY, LOCATOR_ID, USER_LINE_NUM — Material control and line identification.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Audit columns.

Note that the column list includes REQUIRED_DATE and organization/locator names, which the internal view text maps from REQUIREMENT_DATE, SUBINVENTORY, and LOCATOR_ID.

Common Use Cases and Queries

Typical scenarios include reservation aging by required date, open reservations for a sales order, and pending-issue reporting by subinventory. A representative query filtering on required date:

SELECT organization_id, inventory_item_id, required_date, sales_order_id, reserved_quantity, issued_quantity, pending_issue_quantity
FROM apps.invbv_inventory_reservations
WHERE required_date BETWEEN :p_from AND :p_to
AND organization_id = :p_org
ORDER BY required_date;

Reservations tied to a specific sales order can be retrieved by SALES_ORDER_ID or by DEMAND_SOURCE_HEADER_ID. Because the view is security-enabled and read-only, it is safe for ad hoc and packaged reporting, though large extracts should be filtered by organization and date range to limit the impact of the MTL_DEMAND scan.