Search Results document_shipment_number

Overview

CHV_ITEM_ORDERS_V is an APPS-owned database view in the Oracle E-Business Suite Supplier Scheduling (CHV) product family. It exposes the association between supplier schedule items, schedule orders, and the purchasing release documents that fulfill them. The view is retrofitted, meaning it is layered over an existing scheduling data model to present a denormalized, user-friendly projection of order and shipment detail suitable for concurrent programs, forms, and reporting.

The view answers a specific question that drives supplier scheduling reconciliation: for a given schedule line item, which purchase order release (or release shipment) satisfies the demand, and what are the identifying attributes of that document? The user search term document_shipment_number is central to this purpose — the view resolves the internal DOCUMENT_SHIPMENT_ID surrogate key into the human-readable SHIPMENT_NUM drawn from the purchasing line location, and pairs it with the release number constructed as PO_HEADERS.SEGMENT1 || '-' || PO_RELEASES.RELEASE_NUM.

Because it joins scheduling records to purchasing documents and decodes lookup values into display strings, the view is typically consumed read-only: by supplier scheduling reports, by the release-generation workflow, and by any integration extracting scheduled shipments to a supplier portal or external planning system.

Underlying Base Objects

The documented base objects accessed by the view are: CHV_ITEM_ORDERS, CHV_SCHEDULE_ITEMS, PO_DOCUMENT_TYPES, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS, PO_LOOKUP_CODES, PO_RELEASES_ALL, PO_REQUISITION_HEADERS_ALL, and PO_REQUISITION_LINES, plus the FND_GLOBAL package for session context.

The view text joins the scheduling tables CHV_ITEM_ORDERS (alias CIO) and CHV_SCHEDULE_ITEMS (CSI) on SCHEDULE_ID and SCHEDULE_ITEM_ID. From there it links to purchasing entities: CIO.DOCUMENT_HEADER_ID = PLL.PO_HEADER_ID, CIO.DOCUMENT_LINE_ID = POL.PO_LINE_ID, and CIO.DOCUMENT_SHIPMENT_ID = PLL.LINE_LOCATION_ID. PO_RELEASES_ALL bridges to PO_HEADERS_ALL, while PO_LINES_ALL and PO_LINE_LOCATIONS supply line and shipment numbers. PO_LOOKUP_CODES is joined twice — once aliased PLC1 for authorization status and once as PLC2 for schedule document type. The predicate CIO.SUPPLY_DOCUMENT_TYPE = 'RELEASE' and the PO_DOCUMENT_TYPES filter restrict the UNION branch to release documents. A UNION with a requisition-oriented branch extends the same shape to non-release supply documents, which is why PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES appear in the base object list.

Key Columns

• SCHEDULE_ID / SCHEDULE_ITEM_ID / SCHEDULE_ORDER_ID — Identifiers tying the row back to the supplier schedule and its item/order context.
• SUPPLY_DOCUMENT_TYPE — Categorizes the supply source; the primary branch is hard-coded to 'RELEASE'.
• DOCUMENT_SHIPMENT_ID and SHIPMENT_NUM — The internal shipment key and its displayed shipment number sourced from PO_LINE_LOCATIONS, directly matching the document_shipment_number lookup.
• DOCUMENT_LINE_ID and LINE_NUM — Purchase order line identifier and its display number from PO_LINES_ALL.
• PO_RELEASE_ID and the concatenated release number — POH.SEGMENT1 || '-' || POR.RELEASE_NUM uniquely names the release document.
• ORDER_QUANTITY, PURCHASING_UNIT_OF_MEASURE, PRIMARY_UNIT_OF_MEASURE — Scheduled quantity and units of measure.
• DUE_DATE — The required date for the scheduled order.
• DISPLAYED_FIELD (×2) — Decoded lookup values for authorization status and schedule document type.
• REVISION_NUM — Revision of the release document.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 — Descriptive flexfield columns.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The most frequent use is retrieving the shipment number for a scheduled order so that planners and suppliers can reconcile a schedule line against the release shipment that authorized it.

SELECT schedule_id, schedule_item_id, document_line_id,
       document_shipment_id, shipment_num,
       po_release_id, order_quantity, due_date
FROM   apps.chv_item_orders_v
WHERE  schedule_item_id = :p_schedule_item_id;

Locating a release by its shipment number supports reverse lookup — for example, tracing a supplier-advised shipment back to the schedule that generated it:

SELECT schedule_id, schedule_item_id, document_line_id,
       document_shipment_id, shipment_num
FROM   apps.chv_item_orders_v
WHERE  shipment_num = :p_shipment_number;

Reporting scheduled quantities by due date and release supports supplier-facing extracts:

SELECT po_release_id, shipment_num, due_date,
       SUM(order_quantity) AS scheduled_qty
FROM   apps.chv_item_orders_v
WHERE  due_date BETWEEN :p_from AND :p_to
GROUP  BY po_release_id, shipment_num, due_date;

Because the view performs internal joins across the purchasing and scheduling schemas, callers should rely on it rather than reconstructing the joins manually, and should treat it as read-only.