Search Results rep_line_code

Overview

MTL_SHORT_SUMMARY_V is an APPS-owned, VALID database view belonging to the Oracle Inventory (INV) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It is described in the ETRM metadata as a "Summary view of the material shortages temp table," meaning it presents a consolidated, user-facing projection of data staged in MTL_SHORT_CHK_TEMP. Its principal function is to support the Material Shortage Report and the shortage-checking UI within Oracle Work in Process, where planners and production supervisors review demand that cannot be met by current on-hand supply.

The view does not store data; it resolves the temporary shortage rows into a readable form by joining item, work order, lookup, and — for the repetitive branch of the union — line and repetitive schedule information. Two logical result sets are combined with UNION ALL, distinguished by OBJECT_TYPE, giving discrete job shortages and repetitive/line shortages a common column layout.

Underlying Base Objects

The view text is defined over the following core objects: MTL_SHORT_CHK_TEMP (the driving synonym for the shortage temp table), MFG_LOOKUPS (to resolve the OBJECT_TYPE code into a MEANING using lookup type MTL_SHORTAGE_OBJECT_TYPE), MTL_SYSTEM_ITEMS_KFV (joined twice, once as MSIK1 for the shortage item and once as MSIK2 for the work order primary item), WIP_ENTITIES and WIP_DISCRETE_JOBS for the discrete job branch, and WIP_LINES and WIP_REPETITIVE_SCHEDULES for the repetitive branch. The documented dependency list further includes WIP_LINES, MTL_SALES_ORDERS and MTL_SALES_ORDERS_KFV, OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_TRANSACTION_TYPES_TL, SO_HEADERS_ALL, SO_LINES_ALL, FND_LANGUAGES, the FND_PROFILE package and the OE_INSTALL package, reflecting the sales-order demand sources that can feed the shortage table. All are accessed through APPS synonyms, standard practice for seeded INV objects.

The outer joins on MSIK2 (MSIK2.ORGANIZATION_ID (+) = WE.ORGANIZATION_ID and MSIK2.INVENTORY_ITEM_ID (+) = WE.PRIMARY_ITEM_ID) allow shortages to be reported even when the work order's primary item cannot be resolved.

Key Columns

• SEQ_NUM, ROWID — surrogate row identifier and ordinal used by the calling form or report for stable ordering.
• ORGANIZATION_ID — inventory organization in which the shortage is evaluated; a mandatory filter for multi-org access.
• OBJECT_TYPE / MEANING — decoded shortage source (discrete job versus repetitive schedule) derived from MFG_LOOKUPS lookup type MTL_SHORTAGE_OBJECT_TYPE.
• INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, DESCRIPTION, PLANNER_CODE — the short item and its attributes, with concatenated segments supplied by MTL_SYSTEM_ITEMS_KFV.
• UOM_CODE, QUANTITY_OPEN — unit of measure and the unresolved shortage quantity.
• OBJECT_ID, WIP_ENTITY_NAME, ENTITY_TYPE — the consuming work order or schedule.
• LINE_CODE — populated in the repetitive branch from WIP_LINES; this is the rep_line_code element users search for when relating shortages to repetitive lines.
• SCHEDULED_START_DATE / SCHEDULED_COMPLETION_DATE (discrete) and FIRST_UNIT_START_DATE / LAST_UNIT_COMPLETION_DATE / STATUS_TYPE (repetitive) — dates and status for the originating job or schedule.
• OBJECT_DETAIL_ID — exposed in both numeric and character form via DECODE(SIGN(...)), NULL where not applicable.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically queried after a material shortage check has populated MTL_SHORT_CHK_TEMP, either from the WIP Material Shortage Report or a custom reconciliation query.

• List all shortages for an organization, ordered by quantity:

SELECT wip_entity_name, inventory_item_id, concatenated_segments,
       quantity_open, uom_code, meaning
FROM   mtl_short_summary_v
WHERE  organization_id = :org_id
ORDER  BY quantity_open DESC;

• Isolate repetitive schedule shortages by line code (the rep_line_code search term):

SELECT wip_entity_name, line_code, concatenated_segments, quantity_open
FROM   mtl_short_summary_v
WHERE  organization_id = :org_id
AND    line_code IS NOT NULL;

• Drive a planner expedite report by joining to MTL_PLANNERS on planner_code.
• Reconcile shortage quantities against WIP_DISCRETE_JOBS or WIP_REPETITIVE_SCHEDULES using OBJECT_ID and WIP_ENTITY_ID.

Because the underlying temp table is transient, results are only meaningful immediately after a shortage check is executed and should be treated as diagnostic rather than historical data.