Results for “demand_source_type_description”

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

Overview

MTL_RESERVATIONS_INTERFACE_V is an APPS-owned view in the Oracle E-Business Suite Inventory (INV) module. It is defined over the MTL_RESERVATIONS_INTERFACE table, the staging table used by the material reservation interface import process, and it presents that staging data in a denormalized, reporting-friendly form. The view enriches the raw interface rows with descriptive attributes resolved from related Inventory and organization master data, so that pending or errored reservation interface records can be inspected without joining multiple lookups manually. It is valid in both 12.1.1 and 12.2.2 and remains a stable object across those releases.

The view is read-oriented. Records are inserted and processed through the reservation interface APIs and concurrent programs that operate on MTL_RESERVATIONS_INTERFACE; the view simply exposes those rows with their resolved code and name columns. It is therefore relevant to integration monitoring, interface error diagnosis, and reporting on inbound reservation requests originating from external systems, order management, or other Oracle modules.

Underlying Base Objects

The documented base objects referenced by the view are:

• MTL_RESERVATIONS_INTERFACE — the driving synonym supplying the interface rows and the ROWID.
• MTL_PARAMETERS — joined for organization context, giving the organization code.
• HR_ALL_ORGANIZATION_UNITS — joined for the organization name (from and to organization).
• MTL_SYSTEM_ITEMS — joined on INVENTORY_ITEM_ID to supply the item description.
• MTL_TXN_SOURCE_TYPES — joined against demand, to-demand, supply, and to-supply source type IDs to resolve transaction source type names.
• MFG_LOOKUPS — referenced for lookup translations.

These joins mean the view returns internal IDs alongside their human-readable counterparts, which is the primary reason it exists separately from the base table.

Key Columns

The view exposes the full interface column set, including the following categories:

• Identifiers and dates: RESERVATION_INTERFACE_ID, RESERVATION_BATCH_ID, REQUIREMENT_DATE, ROWID.
• Organizations: ORGANIZATION_ID with ORGANIZATION_CODE and organization NAME, plus TO_ORGANIZATION_ID with its code and name.
• Item segments: INVENTORY_ITEM_ID, MSI.DESCRIPTION, and ITEM_SEGMENT1 through ITEM_SEGMENT20. The searched term LOC_SEGMENT20 corresponds to the locator flexfield columns; the view also exposes LOC_SEGMENT1 through LOC_SEGMENT5 and the related LOCATOR_ID, mirroring the ITEM_SEGMENT pattern of concatenated segment columns.
• Demand and supply sources: DEMAND_SOURCE_TYPE_ID, DEMAND_SOURCE_NAME, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE_ID, and the parallel TO_DEMAND_*, SUPPLY_SOURCE_*, and TO_SUPPLY_SOURCE_* columns, each with a resolved TRANSACTION_SOURCE_TYPE_NAME.
• Quantities and UOMs: PRIMARY_UOM_CODE/ID, RESERVATION_UOM_CODE/ID, RESERVATION_QUANTITY, PRIMARY_RESERVATION_QUANTITY, SECONDARY_UOM_CODE/ID, SECONDARY_RESERVATION_QUANTITY.
• Location detail: SUBINVENTORY_CODE, SUBINVENTORY_ID, LOCATOR_ID, REVISION.
• Status: ERROR_CODE and ERROR_EXPLANATION for failed rows, plus EXTERNAL_SOURCE_CODE and EXTERNAL_SOURCE_LINE_ID.

Common Use Cases and Queries

Typical uses include identifying failed interface rows before reprocessing, reporting pending reservations by organization, and validating that source documents and item/locator flexfields resolved correctly.

Listing errored interface records:

SELECT reservation_interface_id, organization_code, item_segment1,
reservation_quantity, error_code, error_explanation
FROM apps.mtl_reservations_interface_v
WHERE error_code IS NOT NULL;

Reporting pending reservations by item and subinventory:

SELECT organization_code, item_segment1, subinventory_code, locator_id,
reservation_quantity, reservation_uom_code
FROM apps.mtl_reservations_interface_v
WHERE reservation_batch_id = :batch_id;

Inspecting item and locator segment values, including the LOC_SEGMENT columns:

SELECT reservation_interface_id, item_segment1, loc_segment1,
loc_segment2, locator_id
FROM apps.mtl_reservations_interface_v
ORDER BY reservation_interface_id;