Search Results document_shipment_id

Overview

ICX_CHV_ITEM_ORDERS_V is an Oracle E-Business Suite view owned by the APPS schema and validated in the ETRM 12.2.2 repository. It belongs to the ICX product family, Oracle iProcurement, and forms part of the supplier scheduling and item-ordering reporting layer that iProcurement and related purchasing modules rely upon. The view presents a consolidated, denormalized picture of item order information tied to supplier schedule lines, linking each scheduled item to its originating purchasing document — most notably purchase order releases — along with descriptive lookup values, quantities, units of measure, due dates, and purchasing document identifiers.

Functionally, the object is a UNION of two SELECT branches. Both branches draw from CHV_ITEM_ORDERS and CHV_SCHEDULE_ITEMS and resolve descriptive fields through PO_LOOKUP_CODES. The first branch joins purchase order releases (PO_RELEASES), line locations (PO_LINE_LOCATIONS), headers (PO_HEADERS), lines (PO_LINES), and document types (PO_DOCUMENT_TYPES), restricting rows to RELEASE-type supply documents. This design lets Oracle iProcurement report scheduled item orders against releases without requiring consumers of the view to reconstruct the underlying PO joins.

Underlying Base Objects

The documented base objects for this view are:

• CHV_ITEM_ORDERS (synonym) — the primary fact source for schedule, item, order, and quantity data.
• CHV_SCHEDULE_ITEMS (synonym) — supplies schedule-to-item association and schedule context.
• PO_LOOKUP_CODES (view) — resolves authorization status and schedule document type lookup descriptions.
• PO_DOCUMENT_TYPES (synonym), PO_HEADERS (synonym), PO_LINES (synonym), PO_LINE_LOCATIONS (synonym), PO_RELEASES (synonym) — the purchasing document hierarchy joined to the schedule line.
• PO_REQUISITION_HEADERS (synonym) and PO_REQUISITION_LINES (synonym) — referenced by the second UNION branch, extending the view to internal requisition-based supplies.
• FND_GLOBAL (package) — used for session context such as the operating unit (ORG_ID), including within the view's logic.

The joins in the release branch are driven by CIO.SCHEDULE_ID = CSI.SCHEDULE_ID, CIO.SCHEDULE_ITEM_ID = CSI.SCHEDULE_ITEM_ID, CIO.DOCUMENT_HEADER_ID = PLL.PO_HEADER_ID, CIO.DOCUMENT_LINE_ID = POL.PO_LINE_ID, CIO.DOCUMENT_SHIPMENT_ID = PLL.LINE_LOCATION_ID, PLL.PO_RELEASE_ID = POR.PO_RELEASE_ID, and POR.PO_HEADER_ID = POH.PO_HEADER_ID. Authorization status is resolved via NVL(POR.AUTHORIZATION_STATUS,'INCOMPLETE') against the 'AUTHORIZATION STATUS' lookup, and the supply document type is constrained to 'RELEASE'.

h4>Key Columns

• SCHEDULE_ID, SCHEDULE_ITEM_ID, SCHEDULE_ORDER_ID — identifiers linking the order line back to the supplier schedule and schedule item; SCHEDULE_ORDER_ID sequences orders within a schedule.
• SUPPLY_DOCUMENT_TYPE — classifies the supply source; the release branch filters to 'RELEASE'.
• ORDER_QUANTITY, PRIMARY_UNIT_OF_MEASURE, PURCHASING_UNIT_OF_MEASURE — ordered quantity and its primary and purchasing UOM expressions.
• DUE_DATE — the scheduled due date for the item order.
• DOCUMENT_HEADER_ID, DOCUMENT_LINE_ID, DOCUMENT_SHIPMENT_ID — pointers into the PO document model (header, line, and shipment/line location).
• PO_HEADER_ID, PO_RELEASE_ID, REVISION_NUM, LINE_NUM, SHIPMENT_NUM — human-readable and surrogate purchasing document references.
• DISPLAYED_FIELD — one instance exposes the release authorization status description (via PLC1) and another the schedule document type description (via PLC2).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield columns carried from CHV_ITEM_ORDERS.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — standard WHO and concurrent-program audit columns.

Common Use Cases and Queries

Typical use cases include supplier schedule reporting in Oracle iProcurement, reconciliation of scheduled item orders to their authorizing purchase order releases, and extraction of order quantities and due dates for supply-planning or spend analysis. Because the view already resolves lookup descriptions and joins the PO hierarchy, it is frequently used as a source for custom concurrent programs, BI Publisher reports, and integrated extracts. A representative query follows:

SELECT schedule_id,
       schedule_item_id,
       document_line_id,
       order_quantity,
       primary_unit_of_measure,
       due_date,
       po_header_id,
       po_release_id,
       displayed_field
FROM   apps.icx_chv_item_orders_v
WHERE  due_date >= SYSDATE
ORDER  BY due_date;

A second common pattern filters by schedule or item to trace the purchasing document behind a scheduled order:

SELECT schedule_id, schedule_item_id,
       po_header_id, po_release_id,
       line_num, shipment_num,
       order_quantity, due_date
FROM   apps.icx_chv_item_orders_v
WHERE  schedule_id = :p_schedule_id
AND    schedule_item_id = :p_item_id;

When consuming the view, filter by the correct operating unit through the underlying PO_HEADERS organization context, and note that the release branch restricts supply document types to 'RELEASE', so non-release supply documents are only represented through the requisition-based UNION branch of the definition.