Search Results chv_schedule_items

Overview

POS_CHV_ITEM_ORDERS_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. It consolidates scheduling agreement item order information held in the CHV (Sourcing/Procurement) scheduling tables and joins that data to the corresponding released purchasing documents in the PO schema. The view is used to report on item-level supply commitments generated against scheduling agreements and to reconcile those commitments with the purchase orders and releases that fulfil them.

In the ETRM 12.2.2 repository the object is registered as a VALID view owned by APPS. A user searching on the synonym CHV_SCHEDULE_ITEMS is frequently directed to this view because the schedule identifier and schedule item identifier from CHV_SCHEDULE_ITEMS form the primary correlation key between the two CHV tables and the PO document tables. The view therefore serves as the bridging layer between schedule-level planning data and transactional purchasing documents.

Underlying Base Objects

The documented base objects referenced by POS_CHV_ITEM_ORDERS_V are: CHV_ITEM_ORDERS (synonym), CHV_SCHEDULE_ITEMS (synonym), FND_GLOBAL (package), PO_DOCUMENT_TYPES (synonym), PO_DOCUMENT_TYPES_ALL_TL (synonym), PO_HEADERS_ALL (synonym), PO_LINES_ALL (synonym), PO_LINE_LOCATIONS_ALL (synonym), PO_LOOKUP_CODES (view), PO_RELEASES_ALL (synonym), PO_REQUISITION_HEADERS (synonym), and PO_REQUISITION_LINES (synonym).

The view text is a UNION over at least two branches, differentiated by SUPPLY_DOCUMENT_TYPE. The first branch is filtered to SUPPLY_DOCUMENT_TYPE = 'RELEASE' and drives the release-specific joins; a second branch repeats the column list for the remaining document types. The core driver table is CHV_ITEM_ORDERS (aliased CIO), which supplies the schedule identifiers, order quantities, units of measure, and descriptive flexfield attributes. CHV_SCHEDULE_ITEMS (CSI) is joined on SCHEDULE_ID and SCHEDULE_ITEM_ID to validate the schedule line. PO_RELEASES_ALL (POR), PO_HEADERS_ALL (POH), PO_LINES_ALL (POL), and PO_LINE_LOCATIONS_ALL (PLL) supply the release number, revision number, line number, and shipment number. PO_LOOKUP_CODES is joined twice — once for AUTHORIZATION STATUS and once for SCHEDULE_DOCUMENT_TYPE — to resolve lookup meanings. PO_DOCUMENT_TYPES_ALL_TL provides the language-specific release document subtype, restricted to LANGUAGE = USERENV('LANG').

Key Columns

• SCHEDULE_ID, SCHEDULE_ITEM_ID, SCHEDULE_ORDER_ID — Identifiers linking the record back to the CHV scheduling hierarchy.
• SUPPLY_DOCUMENT_TYPE — Classifies the supply document; 'RELEASE' identifies the release branch of the UNION.
• ORDER_QUANTITY, PURCHASING_UNIT_OF_MEASURE, PRIMARY_UNIT_OF_MEASURE — Quantity and unit conversion data for the scheduled order.
• DUE_DATE — Scheduled delivery or requirement date.
• PO_RELEASE_ID, REVISION_NUM — Release identity and revision from PO_RELEASES_ALL; the view concatenates SEGMENT1 and RELEASE_NUM to present a human-readable release reference.
• DOCUMENT_LINE_ID, LINE_NUM, DOCUMENT_SHIPMENT_ID, SHIPMENT_NUM — Purchase order line and shipment identifiers and their display numbers.
• DISPLAYED_FIELD — Lookup meaning text supplied twice: for document type and for authorization status.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — Descriptive flexfield context and segments carried from CHV_ITEM_ORDERS.
• LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_UPDATE_DATE — Standard audit and concurrent program tracking columns.

Common Use Cases and Queries

Typical scenarios include reporting released quantities against scheduling agreement items, auditing authorisation status of releases, and reconciling CHV schedule data with PO shipment records. A representative query retrieving released item orders with their authorisation status is:

SELECT schedule_id, schedule_item_id, order_quantity, due_date, document_line_id, line_num, shipment_num, displayed_field FROM apps.pos_chv_item_orders_v WHERE supply_document_type = 'RELEASE' ORDER BY schedule_id, due_date;

To filter to a specific schedule and item, constrain on the CHV keys:

SELECT schedule_id, schedule_item_id, order_quantity, purchasing_unit_of_measure, due_date, po_release_id, revision_num FROM apps.pos_chv_item_orders_v WHERE schedule_id = :schedule_id AND schedule_item_id = :schedule_item_id;

Because the view joins PO_RELEASES_ALL, PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL, it should be queried with the appropriate organisation filter applied through the underlying PO security views or by joining to the operating unit context in the calling report. Performance is best when queries supply SCHEDULE_ID, SCHEDULE_ITEM_ID, or PO_RELEASE_ID predicates that allow the optimiser to drive from CHV_ITEM_ORDERS.