Search Results latest_delivery_date

Overview

APPS.WIP_EAM_OSP_V is a Work in Process (WIP) view that consolidates outside processing (OSP) resource requirements with their associated requisition and purchase order documentation. As stated in the ETRM metadata, the view "shows all the resources for outside processing along with the requisitions and purchase orders information." It is defined in the APPS schema and carries a VALID status in Oracle EBS 12.1.1 and 12.2.2.

The view is structured as a UNION of two distinct query blocks. The first block retrieves outside processing resource lines directly from approved requisitions that have not yet been placed on a purchase order. The second block retrieves the same resource context once a purchase order exists, joining purchase order distributions back to requisition and purchase order headers. This dual-block design allows reporting on the complete outside processing lifecycle — from requisition creation through purchase order placement and delivery — within a single query surface. The view is commonly used in Enterprise Asset Management (EAM) work order contexts, where outside processing operations require visibility into procurement status.

Underlying Base Objects

The documented base objects for the view are:

• PO_REQUISITION_LINES_ALL and PO_REQUISITION_HEADERS_ALL — the requisition line and header records.
• PO_LINE_TYPES — used to filter on OUTSIDE_OPERATION_FLAG = 'Y'.
• MTL_UNITS_OF_MEASURE — supplies the unit of measure code for the resource.
• PO_VENDORS — an outer-joined view supplying vendor name and vendor number.
• PO_DISTRIBUTIONS_ALL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_REQ_DISTRIBUTIONS_ALL — joined in the second UNION block to tie deliveries and receipts back to the requisition and purchase order.

All base objects are referenced through APPS synonyms. The view therefore depends on the standard Purchasing and Inventory table structures and inherits their referential relationships.

Key Columns

The view projects a large column set that aligns requisition data with purchase order data. Notable columns include:

• WIP_ENTITY_ID, WIP_OPERATION_SEQ_NUM, WIP_RESOURCE_SEQ_NUM — identify the EAM work order and the specific outside processing operation and resource.
• ORG_ID / DESTINATION_ORGANIZATION_ID — the destination inventory organization for the OSP line.
• REQ_NUMBER (RQH.SEGMENT1) and PO_NUMBER (POH.SEGMENT1) — human-readable requisition and purchase order numbers.
• ITEM_DESCRIPTION, UOM_CODE, UNIT_PRICE, CURRENCY_CODE — descriptive and pricing attributes of the OSP item.
• REQ_LINE_QTY / QUANTITY and PO_LINE_QTY — ordered quantities at the requisition and purchase order levels.
• QUANTITY_DELIVERED, QUANTITY_ORDERED, QUANTITY_CANCELLED — delivery and disposition quantities derived from PO_DISTRIBUTIONS_ALL (aggregated with SUM).
• VENDOR_NAME and VENDOR_NO — supplier identification from PO_VENDORS.
• CLOSED_CODE and AUTHORIZATION_STATUS for both the requisition and the purchase order line/header — lifecycle status indicators.

Because the two UNION blocks supply the same column positions, columns that are not populated in a given branch appear as TO_DATE(NULL) or TO_NUMBER(NULL) placeholders. In the metadata excerpt, the position corresponding to the latest delivery or promised delivery date is populated with a NULL placeholder in both visible branches, which is significant for users searching on "latest_delivery_date": the view exposes a delivery-related numeric or date column, but in the documented excerpt that column is not populated from a base table in either block.

Common Use Cases and Queries

The view supports reporting on OSP work order operations, procurement status of outside operations, and vendor delivery progress. A typical query identifies OSP resources for a work order along with their requisition and PO details:

• Listing all OSP resources for a given WIP_ENTITY_ID with requisition and PO numbers, vendor name, ordered and delivered quantities.
• Identifying OSP requisitions that have no purchase order yet (first UNION branch, where PO columns are NULL).
• Tracking outstanding delivered versus ordered quantities per vendor and operation.
• Reconciling outside processing commitments against closed and cancelled lines.

A representative query follows:

SELECT wip_entity_id, wip_operation_seq_num, wip_resource_seq_num, req_number, po_number, vendor_name, item_description, quantity, quantity_delivered, quantity_cancelled
FROM apps.wip_eam_osp_v
WHERE wip_entity_id = :p_wip_entity_id
ORDER BY wip_operation_seq_num, wip_resource_seq_num;

Because date-related columns (including the "latest_delivery_date" position) are populated with NULL placeholders in the documented view text, users requiring promised or latest delivery dates should derive them from the purchase order schedule and distribution tables referenced by the view's second UNION branch, rather than relying on the view's own date column.