Search Results nonnettable_quantity_on_hand




Overview
Explore in AI Chat

Overview

APPS.WIP_NET_AVAILABLE_VIEW is an internal Oracle Applications view owned by the APPS schema (FND Design Data: WIP.WIP_NET_AVAILABLE_VIEW, object type VIEW, status VALID). It presents a consolidated material-availability picture for components used on discrete jobs and repetitive schedules, combining item master attributes, buyer and planner information, open work-in-process (WIP) demand, and on-hand balances. It is used primarily by Oracle Work in Process and related planning and shop-floor programs to determine whether sufficient nettable material exists to satisfy open component requirements.

The view carries an explicit Oracle Internal Use Only warning: Oracle Corporation does not support access to applications data through this object except from standard Oracle Applications programs. The view is documented with the object type "Internal" and referenced by design data in the WIP product family. In EBS 12.1.1 and 12.2.2 the definition is stable and is not intended as a public integration interface; customers who query it directly must accept that its columns and logic may change without notice. The column NONNETTABLE_QUANTITY_ON_HAND — the term the user searched for — reports component quantity residing in subinventories flagged as nonnettable, i.e. stock that is physically present but excluded from netting against requirements by Oracle planning and WIP logic.

Underlying Base Objects

The view is defined over a mix of base tables (referenced through APPS synonyms), views, and HR packages. The documented referenced objects are: HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), MFG_LOOKUPS (VIEW), MTL_EMPLOYEES_VIEW (VIEW), MTL_ITEM_FLEXFIELDS (VIEW), MTL_ONHAND_QUANTITIES_DETAIL (SYNONYM), MTL_SECONDARY_INVENTORIES (SYNONYM), MTL_SYSTEM_ITEMS_B (SYNONYM), WIP_DISCRETE_JOBS (SYNONYM), WIP_REPETITIVE_SCHEDULES (SYNONYM), and WIP_REQUIREMENT_OPERATIONS (SYNONYM).

The demand side derives from WIP_DISCRETE_JOBS, WIP_REPETITIVE_SCHEDULES, and WIP_REQUIREMENT_OPERATIONS, which together supply the count of open requirements, required quantity, issued quantity, and open quantity per component. The supply side derives from MTL_ONHAND_QUANTITIES_DETAIL joined with MTL_SECONDARY_INVENTORIES, so that on-hand quantities can be split into nettable and nonnettable portions based on the subinventory's netting attribute. Item and organization context come from MTL_SYSTEM_ITEMS_B and MTL_ITEM_FLEXFIELDS; buyer and planner display values are resolved through MTL_EMPLOYEES_VIEW and the HR packages (HR_GENERAL, HR_PERSON_NAME, HR_SECURITY), which also enforce HR security on employee-related columns. MFG_LOOKUPS supplies decoded lookup meanings.

Key Columns

Common Use Cases and Queries

Typical usage is diagnostic: identifying components whose nettable supply cannot cover open WIP demand, or quantifying how much of a component's stock sits in nonnettable subinventories and is therefore unavailable for netting. The latter directly answers the "nonnettable_quantity_on_hand" search, since that column isolates stock in subinventories excluded from netting.

Sample query — components with shortfalls, showing where stock is held:

  • SELECT organization_id, inventory_item_id, item_number, planner_code,
  •        nettable_quantity_on_hand, nonnettable_quantity_on_hand,
  •        total_quantity_on_hand, quantity_open, net_available_quantity
  •  FROM apps.wip_net_available_view
  •  WHERE organization_id = :org_id
  •    AND net_available_quantity < 0
  •  ORDER BY net_available_quantity;

Sample query — items with material trapped in nonnettable subinventories:

  • SELECT item_number, nonnettable_quantity_on_hand, nettable_quantity_on_hand
  •  FROM apps.wip_net_available_view
  •  WHERE organization_id = :org_id
  •    AND nonnettable_quantity_on_hand > 0
  •  ORDER BY nonnettable_quantity_on_hand DESC;

Because the object is Oracle Internal Use Only and its definition may change between point releases, such queries should be treated as diagnostic rather than as a supported integration interface; where a supported substitute exists, standard WIP and Inventory inquiry windows or documented public APIs should be preferred.