Search Results osp_item_qty_ordered

Overview

WIP_OSP_REQS_POS_V is a Work in Process (WIP) reporting view owned by the APPS schema. Its documented purpose is to expose requisition and purchase order information associated with outside processing (OSP) operations on a job or repetitive schedule. In Oracle EBS, outside processing allows a discrete job or repetitive schedule to send material to a supplier for a value-added operation; the supplier relationship is governed by sourcing rules that generate requisitions, which are then converted into purchase orders and their distributions. This view consolidates those downstream procurement artifacts and links them back to the originating WIP entity, operation, and resource.

The view is primarily consumed by Oracle's own OSP workflow and by custom reporting. It is not a transactional entry point; it is a denormalized read layer that joins WIP execution data to purchasing data so that applications and reports can answer the question of what has been ordered against a given OSP operation, at what price, and with what delivery expectation. The presence of the QUANTITY_ORDERED column and the conversion of open ordered quantity into the item's primary unit of measure makes it directly relevant to searches such as osp_item_qty_ordered.

Underlying Base Objects

The documented base objects include MTL_SYSTEM_ITEMS (twice, once for the item and once for the destination organization's primary UOM), WIP_ENTITIES, WIP_OPERATIONS (again referenced twice to resolve first-unit-start and last-unit-completion dates), WIP_OPERATION_RESOURCES, BOM_STANDARD_OPERATIONS, BOM_CALENDAR_DATES, MTL_PARAMETERS, and the core purchasing tables PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_DOCUMENT_TYPES_ALL, PO_LOOKUP_CODES, PO_RELEASES_ALL, PO_REQUISITION_HEADERS_ALL, and PO_REQUISITION_LINES_ALL. The APPS.WIP_OSP package, specifically the CONVERTTOPRIMARYMOVEQTY function, and FND_GLOBAL also participate.

Joins are anchored on PO_DISTRIBUTIONS_ALL, which carries the WIP_ENTITY_ID, WIP_REPETITIVE_SCHEDULE_ID, WIP_OPERATION_SEQ_NUM, and WIP_RESOURCE_SEQ_NUM that tie a purchasing distribution back to the OSP operation. PO_LINE_LOCATIONS_ALL supplies schedule dates, PO_LINES_ALL supplies the item and UOM, and PO_HEADERS_ALL supplies the segment and authorization status. The WIP side validates the operation and resource sequence numbers so that only valid OSP associations are returned.

Key Columns

• SEGMENT1 — the purchase order number from PO_HEADERS_ALL.
• TYPE_LOOKUP_CODE, DISPLAYED_FIELD, AUTHORIZATION_STATUS — document type and status context for the PO.
• NEED_BY_DATE, PROMISED_DATE — schedule dates from the line location.
• QUANTITY_ORDERED — the ordered quantity on the distribution, the core value referenced by the osp_item_qty_ordered search.
• Converted open quantity — computed as GREATEST(QUANTITY_ORDERED − QUANTITY_DELIVERED − QUANTITY_CANCELLED, 0), passed through WIP_OSP.CONVERTTOPRIMARYMOVEQTY to express the open balance in the item's primary UOM.
• PRIMARY_UNIT_OF_MEASURE — the destination organization's primary UOM.
• WIP_ENTITY_ID, WIP_REPETITIVE_SCHEDULE_ID, WIP_OPERATION_SEQ_NUM, WIP_RESOURCE_SEQ_NUM — the WIP keys linking the order to the job, schedule, operation, and resource.
• PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, PO_DISTRIBUTION_ID — purchasing identifiers for drill-down.
• OPERATION_CODE — the standard operation code from BOM_STANDARD_OPERATIONS.
• CANCEL_FLAG — indicates whether the line location is cancelled.

Common Use Cases and Queries

Typical usage is to report open OSP commitments for a job, to reconcile ordered versus delivered quantities on an OSP operation, or to feed a dashboard that shows purchase orders supporting shop floor work. The following illustrates retrieving ordered and open quantities per job and operation:

• SELECT wip_entity_id, wip_operation_seq_num, wip_resource_seq_num, SEGMENT1, QUANTITY_ORDERED, PRIMARY_UNIT_OF_MEASURE FROM wip_osp_reqs_pos_v WHERE wip_entity_id = :job_id;
• Filter on AUTHORIZATION_STATUS and CANCEL_FLAG to isolate live orders.
• Aggregate QUANTITY_ORDERED by item and operation to answer "how much has been ordered for this OSP item."

Because the view derives quantities through a PL/SQL conversion function, queries returning large result sets should be constrained by WIP entity or organization to avoid unnecessary function calls.