Search Results assembly_primary_uom




Overview
Explore in AI Chat

Overview

APPS.WIP_OSP_REQS_POS_V is a VALID Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as WIP.WIP_OSP_REQS_POS_V. It consolidates Outside Processing (OSP) supply information sourced from both Purchasing and iProcurement requisitioning so that shop-floor users can review and revise the dates on which OSP components and services are expected to arrive for a discrete job or repetitive schedule. The view is documented as Oracle Internal Use Only; Oracle does not support direct access to application data through this object except from standard Oracle Applications programs. Its internal view type indicates it is intended to be consumed by Oracle's own OSP scheduling and rescheduling flows rather than by customer-written reports.

The view answers a specific operational question: for a given WIP entity, which purchase orders, releases, requisitions, and requisition lines are supplying the outside-processed operation, what quantity is still pending, and what are the current versus required need-by and promised dates? Because it unions requisition-based demand with purchase-order-based demand, the PO_REQ_TYPE column is the discriminator that distinguishes a purchase order row from a requisition row.

Underlying Base Objects

The documented metadata lists the following referenced base objects: BOM_CALENDAR_DATES, BOM_STANDARD_OPERATIONS, FND_GLOBAL (package), MTL_PARAMETERS, MTL_SYSTEM_ITEMS, PO_DISTRIBUTIONS_ALL, PO_DOCUMENT_TYPES_ALL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_LOOKUP_CODES (view), PO_RELEASES_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, WIP_ENTITIES, WIP_OPERATIONS, WIP_OPERATION_RESOURCES, and the WIP_OSP package.

Purchasing supply is assembled from PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_RELEASES_ALL, and PO_DISTRIBUTIONS_ALL, with PO_DOCUMENT_TYPES_ALL supplying document classification. Requisition supply is assembled from PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL. Shop-floor context comes from WIP_ENTITIES, WIP_OPERATIONS, and WIP_OPERATION_RESOURCES, tied to BOM_STANDARD_OPERATIONS and BOM_CALENDAR_DATES. MTL_SYSTEM_ITEMS and MTL_PARAMETERS provide item and organization attributes, PO_LOOKUP_CODES resolves approval-status codes, and FND_GLOBAL along with the WIP_OSP package supplies session context and business logic.

Key Columns

Common Use Cases and Queries

Typical usage centers on rescheduling OSP deliveries against shop-floor demand and on listing all requisition-sourced versus purchase-order-sourced supply for a job. A representative query filtering by requisition documents follows:

SELECT po_number, po_req_type, req_number,
       approval_status, old_need_by_date,
       new_need_by_date, assembly_qty_pending,
       operation_seq_num, wip_entity_id
  FROM apps.wip_osp_reqs_pos_v
 WHERE wip_entity_id = :p_wip_entity_id
   AND organization_id = :p_org_id
   AND po_req_type = 'REQUISITION'
 ORDER BY operation_seq_num, old_need_by_date;

Substituting po_req_type = 'PURCHASE ORDER' isolates firm purchasing supply; omitting the predicate returns the complete supply picture. Because the view is flagged internal, production use should be restricted to Oracle-supported OSP flows, and any custom consumption should be validated against the corresponding public APIs.