Results for “mtl_reservations_interface”

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

Overview

MTL_RESERVATIONS_INTERFACE is an Inventory (INV) module interface table that serves as the staging area for material reservation transactions in Oracle EBS 12.1.1 and 12.2.2. It accepts reservation records from external systems, Oracle sub-ledgers, or internal processes, then passes them through the reservation processing engine, which validates each row and either creates corresponding entries in MTL_RESERVATIONS or returns error information to the calling process. The table is essential to integrations that create, transfer, or release material reservations in bulk, particularly where material is committed against demands such as sales orders, work orders, or internal requisitions.

Under the heuristic Data Vault classification supplied with the ETRM metadata, this table is modeled as a link entity. It records relationships between a demand (source side) and a supply (destination side) across items, organizations, subinventories, and locators, rather than acting as a pure hub of business keys or a descriptive satellite.

Key Information Stored

The surrogate primary key is defined by the MTL_RESERVATIONS_INTERAFCE_PK index, composed of RESERVATION_BATCH_ID and RESERVATION_INTERFACE_ID. A redundant unique index, MTL_RESERVATIONS_INTERFACE_U1, holds the same two columns and is the documented business-key candidate. The most significant columns include:

• RESERVATION_BATCH_ID / RESERVATION_INTERFACE_ID — Composite identifier that groups and uniquely identifies each interface row.
• ORGANIZATION_ID / TO_ORGANIZATION_ID — Source and destination inventory organizations for the reservation.
• INVENTORY_ITEM_ID — The item being reserved, validated against MTL_SYSTEM_ITEMS_B and MTL_ITEM_REVISIONS_B.
• DEMAND_SOURCE_TYPE_ID / DEMAND_SOURCE_HEADER_ID / DEMAND_SOURCE_LINE_ID — The demand or consumption side of the reservation.
• SUPPLY_SOURCE_TYPE_ID / SUPPLY_SOURCE_HEADER_ID / SUPPLY_SOURCE_LINE_ID — The supply or fulfillment side.
• RESERVATION_QUANTITY / PRIMARY_RESERVATION_QUANTITY — Quantity to reserve, expressed in transaction and primary units of measure.
• SUBINVENTORY_CODE / LOCATOR_ID / LOT_NUMBER / SERIAL_NUMBER / REVISION — Source material attributes, validated against MTL_SECONDARY_INVENTORIES, MTL_ITEM_LOCATIONS, and MTL_LOT_NUMBERS.
• TO_SUBINVENTORY_CODE / TO_LOCATOR_ID / TO_LOT_NUMBER / TO_SERIAL_NUMBER — Destination material attributes.
• RESERVATION_ACTION_CODE — The operation to perform, such as reserve, unreserve, or transfer.
• ERROR_CODE / ERROR_EXPLANATION — Populated by the interface processor when validation fails.
• ROW_STATUS_CODE — Indicates whether the row has been processed successfully.
• REQUEST_ID / PROGRAM_ID / PROGRAM_APPLICATION_ID — Concurrency request metadata for traceability.

Common Use Cases and Queries

Typical scenarios include bulk reservation loading from external order management systems, reconciliation of pending versus processed interface rows, and diagnosis of reservation errors. A representative query to locate failed rows is:

• SELECT reservation_batch_id, reservation_interface_id, inventory_item_id, error_code, error_explanation FROM mtl_reservations_interface WHERE row_status_code = 'ERROR';
• Grouping pending rows by demand: SELECT demand_source_type_id, demand_source_header_id, COUNT(*) FROM mtl_reservations_interface GROUP BY demand_source_type_id, demand_source_header_id;
• Joining to MTL_SYSTEM_ITEMS_B on INVENTORY_ITEM_ID and ORGANIZATION_ID to report item descriptions alongside reservation quantities.
• Joining to MTL_SECONDARY_INVENTORIES and MTL_ITEM_LOCATIONS to validate subinventory and locator values before submission.

Related Objects

The FK metadata links MTL_RESERVATIONS_INTERFACE to the following significant objects:

• MTL_PARAMETERS — joined via ORGANIZATION_ID and TO_ORGANIZATION_ID to validate inventory organizations.
• MTL_SYSTEM_ITEMS_B — joined via INVENTORY_ITEM_ID and ORGANIZATION_ID.
• MTL_LOT_NUMBERS — joined via INVENTORY_ITEM_ID, ORGANIZATION_ID, LOT_NUMBER, and TO_LOT_NUMBER.
• MTL_SECONDARY_INVENTORIES — joined via SUBINVENTORY_CODE, TO_SUBINVENTORY_CODE, and ORGANIZATION_ID.
• MTL_ITEM_LOCATIONS — joined via LOCATOR_ID, TO_LOCATOR_ID, and ORGANIZATION_ID.
• MTL_TXN_SOURCE_TYPES — joined via DEMAND_SOURCE_TYPE_ID, SUPPLY_SOURCE_TYPE_ID, and their TO_ counterparts.
• MTL_ITEM_REVISIONS_B — joined via INVENTORY_ITEM_ID for revision validation.

The downstream target of successful processing is MTL_RESERVATIONS, and the standard processing routine is the Inventory reservation interface concurrent program.