Search Results schedule_document_type




Overview
Explore in AI Chat

Overview

APPS.POS_CHV_ITEM_ORDERS_V is a Purchasing (PO) module view that presents item-level order and release information for supply documents flowing through Oracle's Collaborative Planning / Supply Chain "CHV" schema. It joins the CHV item-order transactional tables with the standard Purchasing header, line, shipment, and release tables, resolving document-type and status codes through the Purchasing lookup framework. It is commonly used in scheduling, supplier collaboration, and supply-document reporting where a user needs to reconcile scheduled supply quantities against their originating releases and shipments.

The view is directly relevant to the search term schedule_document_type: the view joins PO_LOOKUP_CODES on the lookup type 'SCHEDULE_DOCUMENT_TYPE' and restricts on the lookup code 'RELEASE', effectively constraining the result set to release-type supply documents. The DISPLAYED_FIELD from that lookup supplies the human-readable description returned in the view.

Underlying Base Objects

The ETRM 12.2.2 metadata lists the view's referenced base objects as: CHV_ITEM_ORDERS, CHV_SCHEDULE_ITEMS, FND_GLOBAL, PO_DOCUMENT_TYPES, PO_DOCUMENT_TYPES_ALL_TL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_LOOKUP_CODES, PO_RELEASES_ALL, PO_REQUISITION_HEADERS, and PO_REQUISITION_LINES.

The view is a UNION of two branches. The first branch isolates releases (CIO.SUPPLY_DOCUMENT_TYPE = 'RELEASE') and joins CHV_ITEM_ORDERS to CHV_SCHEDULE_ITEMS, PO_RELEASES_ALL, PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL. The second branch mirrors the same structure for requisition-based supply, sourcing from PO_REQUISITION_HEADERS and PO_REQUISITION_LINES rather than releases. PO_DOCUMENT_TYPES_ALL_TL is joined with language = userenv('LANG') via FND_GLOBAL-style language resolution, and PO_LOOKUP_CODES appears twice — once for authorization status and once for SCHEDULE_DOCUMENT_TYPE.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling scheduled supply to releases, reporting quantities by due date, and auditing document-type code resolution.

  • List release-backed item orders: SELECT schedule_id, schedule_item_id, order_quantity, due_date, displayed_field FROM apps.pos_chv_item_orders_v;
  • Aggregate supply by due date: SELECT due_date, SUM(order_quantity) FROM apps.pos_chv_item_orders_v GROUP BY due_date;
  • Trace documents: SELECT po_release_id, document_line_id, document_shipment_id, line_num, shipment_num FROM apps.pos_chv_item_orders_v;
  • Filter by document type: SELECT * FROM apps.pos_chv_item_orders_v WHERE supply_document_type = 'RELEASE';

Note that results are gated by the SCHEDULE_DOCUMENT_TYPE lookup restriction, so queries predicated on other supply document types will not return rows from this view.