Results for “quantity_backordered”

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

Overview

WIP_MATERIAL_SHORTAGES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined in the Work in Process (WIP) product. Its documented description is simply "Material shortage data." The view exposes component requirements that are currently in shortage for transactable discrete jobs and repetitive schedules, giving planners, shop-floor supervisors, and reporting integrations a consolidated picture of which operations are waiting on material. Because it is a view rather than a table, it contains no stored data of its own; it derives its rows at query time by joining requirement, entity, and item master tables. The presence of REPETITIVE_SCHEDULE_ID and REPETITIVE_LINE_ID in the definition reflects that the view serves both discrete and repetitive manufacturing, and it is this dual scope that makes the object a frequent target of searches for repetitive-line context.

Underlying Base Objects

The ETRM metadata for release 12.2.2 lists the referenced base objects as synonyms over WIP_ENTITIES, WIP_REQUIREMENT_OPERATIONS, WIP_DISCRETE_JOBS, WIP_REPETITIVE_SCHEDULES, WIP_PARAMETERS, and MTL_SYSTEM_ITEMS, all in APPS. The view is anchored on WIP_REQUIREMENT_OPERATIONS (WRO), which holds the component demand rows, joined to WIP_ENTITIES (WE) on WIP_ENTITY_ID. Outer joins to WIP_DISCRETE_JOBS and WIP_REPETITIVE_SCHEDULES supply discrete-job and schedule attributes respectively, and MTL_SYSTEM_ITEMS supplies the primary unit of measure. WIP_PARAMETERS is joined by ORGANIZATION_ID to resolve default pull supply subinventories and locators when no explicit supply location is defined on the requirement.

Key Columns

• WIP_ENTITY_NAME — the job or schedule name as known on the shop floor.
• WIP_ENTITY_TYPE — discriminates discrete job versus repetitive schedule, driving the entity logic in the view.
• REPETITIVE_SCHEDULE_ID / REPETITIVE_LINE_ID — the schedule header and the production line it belongs to; both are populated through WIP_REPETITIVE_SCHEDULES.
• OPERATION_SEQ_NUM, DEPARTMENT_ID — the operation and department at which the shortage occurs.
• INVENTORY_ITEM_ID, UOM_CODE — the short component and its primary UOM.
• QUANTITY_BACKORDERED — the outstanding quantity driving the shortage.
• SUBINVENTORY_CODE, LOCATOR_ID, WIP_SUPPLY_TYPE — where the material is expected to come from, with WIP_ISSUE_FLAG indicating push versus pull supply.
• DATE_REQUIRED — the date the component is needed.

Common Use Cases and Queries

Typical uses include shortage exception reports, supply/demand analysis for repetitive lines, and integration extracts feeding planning dashboards. For example, to list shortages by repetitive line:

• SELECT WIP_ENTITY_NAME, REPETITIVE_LINE_ID, OPERATION_SEQ_NUM, DEPARTMENT_ID, INVENTORY_ITEM_ID, QUANTITY_BACKORDERED, DATE_REQUIRED FROM APPS.WIP_MATERIAL_SHORTAGES_V WHERE REPETITIVE_SCHEDULE_ID IS NOT NULL ORDER BY REPETITIVE_LINE_ID, DATE_REQUIRED;

Alternatively, filter on a specific organization or operation for shop-floor dispatch boards, or join INVENTORY_ITEM_ID to MTL_SYSTEM_ITEMS_VL to display descriptions and concatenated segments alongside the shortfall quantity.