Search Results wip_net_available_view




Overview
Explore in AI Chat

Overview

WIP_NET_AVAILABLE_VIEW is an Oracle E-Business Suite database view owned by the APPS schema and delivered as part of the Work in Process (WIP) product. Its stated purpose is to report "Job/schedule material requirement subinventory quantities" — that is, it consolidates, by organization and inventory item, the material requirements raised against jobs and repetitive schedules together with the on-hand quantities held in the subinventories that supply them. The view therefore acts as a net availability reporting layer that joins shop-floor demand (WIP requirement operations) to inventory supply (on-hand quantity detail) and classifies that supply by subinventory availability type (nettable versus non-nettable).

In Oracle EBS 12.1.1 and 12.2.2 the view is delivered in VALID status and is intended for reporting and integration consumers rather than for online transaction processing. Because it aggregates at the organization/item level and includes item descriptive attributes, buyer information, and planner codes, it is suited to inquiries that support material availability analysis, shortage investigation, and planning review. It exposes no maintenance interface; all data originates in transactional WIP and inventory tables, making it read-only by nature.

Underlying Base Objects

The view is defined over a documented set of base objects spanning manufacturing lookups, inventory, WIP, and human resources:

In the delivered 12.2.2 installation, several of these are referenced through synonyms, but they resolve to the standard MTL and WIP base tables.

Key Columns

The view exposes the following principal columns:

Common Use Cases and Queries

Typical uses include material shortage review, subinventory availability analysis, and feeding custom reports or interfaces that require a job-versus-stock position.

  • Total net availability per item in an organization.
  • Items where open requirements exceed nettable on-hand.
  • Buyer- or planner-based material position reporting.

Sample query:

SELECT organization_id, inventory_item_id, item_number, planner_code,
REQUIRED_QUANTITY, QUANTITY_ISSUED, QUANTITY_OPEN,
NETTABLE_QUANTITY_ON_HAND, NET_AVAILABLE_QUANTITY
FROM apps.wip_net_available_view
WHERE organization_id = :org_id
AND NET_AVAILABLE_QUANTITY < REQUIRED_QUANTITY
ORDER BY planner_code, item_number;

Because the view performs aggregation with outer-join-like normalization (DECODE(COUNT(...),0,1,...)), consumers should apply filters on ORGANIZATION_ID to keep result sets manageable.