Search Results object_detail_name

Overview

APPS.MTL_SHORT_SUMMARY_V is a supplementary Oracle EBS view owned by the APPS schema and registered under FND Design Data as INV.MTL_SHORT_SUMMARY_V. It is classified as a supplementary view used to simplify forms coding, and Oracle explicitly warns that it should not be queried or altered directly, as its definition may change dramatically in subsequent minor or major releases. The view presents a consolidated, cross-functional summary of shortage and supply/demand information, spanning inventory, work in process, and order management domains. Status is VALID in both 12.1.1 and 12.2.2.

The object surfaced in your search because it exposes a column named ITEM_CONCATENATED_SEGMENTS — the flexfield-concatenated item identifier that maps to MTL_SYSTEM_ITEMS_KFV. This makes the view convenient for ad hoc reporting where the user wants readable item keys rather than the raw numeric INVENTORY_ITEM_ID.

Underlying Base Objects

ETRM documents the following referenced base objects: FND_LANGUAGES, FND_PROFILE (package), MFG_LOOKUPS, MTL_SALES_ORDERS, MTL_SALES_ORDERS_KFV, MTL_SHORT_CHK_TEMP, MTL_SYSTEM_ITEMS_KFV, OE_INSTALL (package), OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_TRANSACTION_TYPES_TL, SO_HEADERS_ALL, SO_LINES_ALL, WIP_DISCRETE_JOBS, WIP_ENTITIES, WIP_LINES, and WIP_REPETITIVE_SCHEDULES.

The dependency graph reveals the view's purpose: it federates demand originating from sales orders (OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, SO_HEADERS_ALL, SO_LINES_ALL), supply and production from WIP (WIP_DISCRETE_JOBS, WIP_ENTITIES, WIP_LINES, WIP_REPETITIVE_SCHEDULES), and item master attributes (MTL_SYSTEM_ITEMS_KFV). MFG_LOOKUPS supplies Object Type and status meanings. FND_LANGUAGES and FND_PROFILE support NLS and profile-driven behavior, while MTL_SHORT_CHK_TEMP acts as the temporary staging table that drives the "shortage check" logic — the SHORT in the view name.

Key Columns

• ROW_ID / SEQ_NUM — Row identifier and sequence number for deterministic ordering.
• ORGANIZATION_ID — Warehouse/org context for the row.
• OBJECT_TYPE / OBJECT_TYPE_MEANING — Classifies the row (e.g., job, sales order) resolved via MFG_LOOKUPS.
• INVENTORY_ITEM_ID / ITEM_CONCATENATED_SEGMENTS — Item surrogate key and its flexfield-concatenated readable form.
• ITEM_DESCRIPTION, ITEM_PLANNER_CODE, UOM_CODE — Descriptive item attributes used for shortage reporting.
• QUANTITY_OPEN — Open quantity of the demand or supply line.
• OBJECT_ID / OBJECT_NAME / OBJECT_DETAIL_ID / OBJECT_DETAIL_NAME — Generic pointers to the source document (job, order, schedule) and its detail line.
• REP_LINE_CODE, ASSEMBLY_CONC_SEGMENTS — Repetitive line code and concatenated assembly identifier.
• JOB_START_DATE, JOB_COMPLETION_DATE, JOB_STATUS_TYPE, WIP_ENTITY_TYPE — Work-in-process scheduling and type attributes.
• CUSTOMER_ID, ORDER_TYPE_ID — Sales-order context.
• LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE — Standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios involve rapid shortage visibility across sales orders and WIP without joining each source table manually. A simple lookup by concatenated item segments:

• SELECT item_concatenated_segments, organization_id, quantity_open, object_type_meaning FROM apps.mtl_short_summary_v WHERE item_concatenated_segments = 'ITEM-100-01';
• SELECT object_name, object_detail_name, quantity_open, job_start_date FROM apps.mtl_short_summary_v WHERE organization_id = 204 AND wip_entity_type = 1 ORDER BY seq_num;
• SELECT customer_id, order_type_id, item_description, quantity_open FROM apps.mtl_short_summary_v WHERE customer_id IS NOT NULL;

Because Oracle does not certify this view for direct querying, production integrations should treat results as informational. For supported extracts, replicate the underlying joins against the base tables or use the shipped INV shortage diagnostics and Oracle-supplied APIs.