Search Results secondary_reservation_quantity

Overview

MTL_RESERVATIONS_ALL_V is an APPS-owned Inventory (INV) view that presents material reservation information in a flattened, report-friendly format. It is built over the MTL_RESERVATIONS transactional table and enriches each reservation row with descriptive details from MTL_LOT_NUMBERS and MTL_TXN_SOURCE_TYPES. In Oracle EBS 12.1.1 and 12.2.2 the view is the standard reporting layer used by Inventory, Order Management, Shipping, and Work in Process personnel to examine which material has been soft-reserved (allocated) against specific demand and supply sources. Rather than forcing developers and analysts to join the reservation table to demand/supply type lookups manually, MTL_RESERVATIONS_ALL_V exposes descriptive source information in a single SELECT, making it well suited for ad hoc queries, Discoverer or BI Publisher reports, and custom inbound/outbound integration interfaces. Because it is a view rather than a table, it is read-only and inherits the security and grants applied to its base objects.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over three documented base objects, all exposed to APPS through synonyms: MTL_RESERVATIONS, MTL_LOT_NUMBERS, and MTL_TXN_SOURCE_TYPES. MTL_RESERVATIONS supplies the primary reservation facts — quantity, UOM, organization, item, demand/supply identifiers, and reservation/shipping attributes. MTL_LOT_NUMBERS is joined to resolve lot details, notably the LOT_NUMBER derived from LOT_NUMBER_ID. MTL_TXN_SOURCE_TYPES provides the descriptive names behind DEMAND_SOURCE_TYPE_ID and, where applicable, the supply source type. The view therefore sits logically one layer above MTL_RESERVATIONS, functioning as a denormalized projection that decodes technical foreign keys into human-readable source descriptions while preserving the underlying RESERVATION_ID as its unique identifier.

Key Columns

The view exposes the full reservation column set. The most frequently referenced columns include:

• RESERVATION_ID — Unique primary key of each reservation record.
• ORGANIZATION_ID / INVENTORY_ITEM_ID — Inventory organization and item being reserved.
• DEMAND_SOURCE_TYPE_ID, DEMAND_SOURCE_NAME, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE_ID — Identify the originating demand, such as a sales order or work order, with the source type decoded via MTL_TXN_SOURCE_TYPES.
• SUPPLY_SOURCE_TYPE_ID, SUPPLY_SOURCE_NAME, SUPPLY_SOURCE_HEADER_ID, SUPPLY_SOURCE_LINE_ID, SUPPLY_SOURCE_LINE_DETAIL — Identify the supplying document or entity.
• RESERVATION_QUANTITY, PRIMARY_RESERVATION_QUANTITY, SECONDARY_RESERVATION_QUANTITY — Reserved amounts in reservation, primary, and secondary UOMs; PRIMARY_UOM_CODE, SECONDARY_UOM_CODE, RESERVATION_UOM_CODE describe the corresponding units.
• SUBINVENTORY_CODE, LOCATOR_ID, LOT_NUMBER, LOT_NUMBER_ID, REVISION — Physical stock placement and lot/revision detail, with LOT_NUMBER sourced from MTL_LOT_NUMBERS.
• REQUIREMENT_DATE, PICK_SLIP_NUMBER, EXTERNAL_SOURCE_CODE, EXTERNAL_SOURCE_LINE_ID, AUTODETAIL_GROUP_ID — Demand timing, shipping, and external integration context.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus ATTRIBUTE1–15 (descriptive flexfields) and REQUEST_ID/PROGRAM_ID for concurrent request traceability. Note that the documented view text does not include a STAGED_FLAG column; that attribute belongs to MTL_RESERVATIONS in the 12.2 schema and is not exposed here.

Common Use Cases and Queries

Typical scenarios include auditing on-hand allocations, reconciling reservations to sales or work orders, and extracting reservation data for warehouse or planning reports. A representative query lists all reservations for a given organization and item:

• SELECT reservation_id, organization_id, inventory_item_id, demand_source_name, demand_source_line_id, subinventory_code, locator_id, lot_number, reservation_quantity, reservation_uom_code, requirement_date FROM mtl_reservations_all_v WHERE organization_id = :org AND inventory_item_id = :item;

To trace demand-source distribution, aggregate by DEMAND_SOURCE_NAME. Because STAGED_FLAG is not present in this view, users requiring staged-versus-picked reservation status must query the base MTL_RESERVATIONS table directly or use a related view that exposes that flag (for example WIP or WMS reservation views). Analysts should also note that the view is not secured by organization; organization-level restriction must be applied explicitly in the WHERE clause to enforce data isolation in custom reports.