Results for “detail_reserve_flag”

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

Overview

MTL_DEMAND_INTERFACE_V is an APPS-owned view in the Oracle E-Business Suite Inventory (INV) module. The ETRM documentation describes it succinctly as "10SC ONLY," indicating that its intended scope is limited rather than general-purpose. Functionally, the view is a reporting and integration convenience layer over the demand interface staging table, MTL_DEMAND_INTERFACE, which Oracle Inventory uses to stage external demand records (typically originating from order management, planning, or shipping processes) prior to validation, reservation, and transfer into the demand schema. By joining the staging columns of MTL_DEMAND_INTERFACE to descriptive lookup data and to master reference tables, the view presents demand interface rows in a human-readable form suitable for diagnostics, exception reporting, and interface monitoring.

Underlying Base Objects

According to the documented metadata, MTL_DEMAND_INTERFACE_V is defined over the following referenced base objects: MTL_DEMAND_INTERFACE (synonym), MTL_PARAMETERS (synonym), MTL_ATP_RULES (synonym), MTL_SYSTEM_ITEMS (synonym), MTL_TXN_SOURCE_TYPES (synonym), and MFG_LOOKUPS (view). The central driving object is MTL_DEMAND_INTERFACE, aliased MDI in the view text. The remaining objects provide enrichment joins: MTL_TXN_SOURCE_TYPES supplies the DEMAND_SOURCE_TYPE_DESCRIPTION via TRANSACTION_SOURCE_TYPE_NAME; MTL_ATP_RULES supplies ATP_RULE_NAME via RULE_NAME; MTL_SYSTEM_ITEMS contributes the ITEM_DESCRIPTION, and MTL_PARAMETERS and MFG_LOOKUPS supply organizational and lookup meaning columns (ACTION_CODE_DESCRIPTION, TRANSACTION_MODE_DESCRIPTION, PROCESS_FLAG_DESCRIPTION, ERROR_CODE_DESCRIPTION). Because these are synonyms or simple lookups, the view carries no independent storage; all data is read from the underlying demand interface staging table and its reference tables.

Key Columns

The view exposes the full staging column set of MTL_DEMAND_INTERFACE together with decoded descriptions. Key identifiers include SCHEDULE_GROUP_ID, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, and DEMAND_SOURCE_DELIVERY, which locate the originating external demand. Control and processing columns include ACTION_CODE, TRANSACTION_MODE, PROCESS_FLAG, LOCK_FLAG, ATP_CHECK, VALIDATE_ROWS, SINGLE_LOT_FLAG, DETAIL_RESERVE_FLAG, RESERVE_LEVEL, and CHECK_ATR, each with a corresponding *_DESCRIPTION decoded through MFG_LOOKUPS. Quantities and units are represented by LINE_ITEM_QUANTITY, LINE_ITEM_RESERVATION_QTY, PRIMARY_UOM_QUANTITY, RESERVATION_QUANTITY, and their associated UOM columns. Organizational context is provided by ORGANIZATION_ID, ORGANIZATION_CODE, and ORGANIZATION_NAME, while item context comes from INVENTORY_ITEM_ID, ITEM_DESCRIPTION, and the flexfield segments ITEM_SEGMENT1 through ITEM_SEGMENT20. Error handling columns include ERROR_CODE together with the derived ERROR_CODE_DESCRIPTION and ERR_EXPLANATION. Reservation and scheduling data include REQUIREMENT_DATE, RESERVATION_TYPE, ATP_RULE_ID, and ATP_RULE_NAME. Notably, the view text as documented does not expose a column named OLD_SERIAL_NUMBER; users searching that term should confirm whether the attribute resides in the underlying MTL_DEMAND_INTERFACE table or in a related serial-number interface object rather than this view.

Common Use Cases and Queries

Typical uses include monitoring pending demand interface rows, identifying rows in an error state, and auditing reservation activity for a given organization or item. For example, rows awaiting processing can be retrieved as follows:

• SELECT ORGANIZATION_CODE, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, ITEM_SEGMENT1, LINE_ITEM_QUANTITY, PROCESS_FLAG_DESCRIPTION, ERROR_CODE_DESCRIPTION FROM APPS.MTL_DEMAND_INTERFACE_V WHERE PROCESS_FLAG = 'N';

• SELECT ORGANIZATION_CODE, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, ITEM_SEGMENT1, LINE_ITEM_QUANTITY, PROCESS_FLAG_DESCRIPTION, ERROR_CODE_DESCRIPTION FROM APPS.MTL_DEMAND_INTERFACE_V WHERE ERROR_CODE IS NOT NULL;

• SELECT ORGANIZATION_CODE, ATP_RULE_NAME, RESERVATION_TYPE, RESERVATION_QUANTITY FROM APPS.MTL_DEMAND_INTERFACE_V WHERE ORGANIZATION_CODE = :org AND INVENTORY_ITEM_ID = :item;

Because the object is documented as "10SC ONLY," deployments should verify that the view is present and populated in the target environment before relying on it for integration or reporting, and any reference to old_serial_number should be traced through the parent serial interface tables rather than assumed present here.