Search Results wip_cur_net_available_view




Overview
Explore in AI Chat

Overview

WIP_CUR_NET_AVAILABLE_VIEW is an APPS-owned database view within the Work in Process (WIP) product of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. Its documented purpose is to present current job and schedule material requirement subinventory quantities — that is, a consolidated picture of on-hand supply and open production requirements at the subinventory level for items used on discrete jobs and repetitive schedules.

Because the view exposes materials planning attributes alongside transactional availability figures, it is frequently referenced in WIP material shortage reports, shop floor availability inquiries, and custom integrations that need to evaluate whether a component item can satisfy outstanding job requirements. The user search term "planning_make_buy_code" maps directly to the PLNML.MEANING column, which the view sources from MFG_LOOKUPS to translate the internal planning make/buy code into a user-readable meaning. This makes the view a convenient single source for planners who need to distinguish make items, buy items, and externally processed items within a WIP availability context, rather than joining MTL_SYSTEM_ITEMS_B to MFG_LOOKUPS manually.

Underlying Base Objects

The documented base objects underlying the view span transactional and reference data across Inventory and WIP. They include WIP_REQUIREMENT_OPERATIONS (the core source of open requirement and issued quantities), WIP_*DISCRETE_JOBS* and WIP_*REPETITIVE_SCHEDULES* (the job and schedule headers that give the WIP context), MTL_*ONHAND_QUANTITIES_DETAIL* and MTL_*SECONDARY_INVENTORIES* (on-hand balances and subinventory availability attributes), MTL_*SYSTEM_ITEMS_B* and MTL_*ITEM_FLEXFIELDS* (item master and concatenated item number), MTL_*EMPLOYEES_VIEW* (buyer employee number and name, resolved through HR*GENERAL*, HR_*PERSON_NAME*, and HR_*SECURITY*), and MFG_*LOOKUPS* (which supplies the planning make/buy meaning). Note that MTL_*ONHAND_QUANTITIES_DETAIL*, MTL_*SECONDARY_INVENTORIES*, MTL_*SYSTEM_ITEMS_B*, WIP_*REQUIREMENT_OPERATIONS*, WIP_*DISCRETE_JOBS*, and WIP_*REPETITIVE_SCHEDULES* are referenced as synonyms, while MFG_*LOOKUPS*, MTL_*EMPLOYEES_VIEW*, and MTL_*ITEM_FLEXFIELDS* are referenced as views. The HR packages support the employee name and security logic embedded in the MTL_*EMPLOYEES_VIEW definition.

Key Columns

Common Use Cases and Queries

Typical scenarios include component shortage analysis for discrete jobs, make/buy planning reviews, and shop floor availability dashboards. The following query lists items with their planning make/buy meaning and net availability:

  • SELECT organization_id, inventory_item_id, item_number, planner_code, planning_make_buy_code, net_available_quantity, quantity_open FROM wip_cur_net_available_view WHERE net_available_quantity < 0;
  • SELECT item_number, planning_make_buy_code, nettable_quantity_on_hand, nonnettable_quantity_on_hand, total_quantity_on_hand FROM wip_cur_net_available_view WHERE organization_id = :org_id;
  • SELECT planner_code, buyer_name, SUM(required_quantity - quantity_issued) open_demand FROM wip_cur_net_available_view WHERE planning_make_buy_code = 'Buy' GROUP BY planner_code, buyer_name;

These queries demonstrate how the view streamlines reporting that would otherwise require joining WIP requirement, on-hand, item, and lookup tables manually.