Search Results icx_chv_schedule_items_v




Overview
Explore in AI Chat

Overview

ICX_CHV_SCHEDULE_ITEMS_V is an Oracle E-Business Suite XL transaction view owned by the APPS schema and validated under the ICX (Oracle iProcurement) product family. It is documented as the Schedule Lines View and exposes supplier scheduling line detail together with the item, planning, purchasing document, receipt, and authorization context required to render that detail in the iProcurement and supplier scheduling user interfaces. The view is a read-only query structure: it does not store data of its own, but flattens the relationship between schedule headers, schedule items, approved supplier list attributes, master item definitions, purchase order documents, and receipt history into a single denormalized row per scheduling line. Because the object is a view rather than a table, it functions primarily as a reporting and integration surface — it supports ad hoc SQL, custom concurrent programs, and downstream interface extracts that need schedule line visibility without navigating the individual CHV and PO base objects directly. In 12.1.1 and 12.2.2 the object remains a standard APPS-owned view; the 12.2.2 ETRM metadata lists it as VALID with the same column set and join structure, so custom code written against the 12.1.1 definition continues to resolve in an upgraded environment subject to the usual 12.2 Online Patching editioning considerations for views layered over editioned tables.

Underlying Base Objects

The view is defined over a mix of synonymed base tables, an APPS view, and a lookup view, joined on schedule header, organization, item, and purchasing document keys. Documented referenced objects include:

  • CHV_SCHEDULE_HEADERS and CHV_SCHEDULE_ITEMS — the primary scheduling tables supplying the driving schedule line, revision, cumulative quantities, authorization quantities, purchasing unit of measure, receipt references, and descriptive flexfield attributes CSI.ATTRIBUTE1 through CSI.ATTRIBUTE15.
  • MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV — master item definition and the concatenated segment key, providing item description, lead time, minimum and maximum order quantity, fixed lot multiplier, buyer, and primary unit of measure.
  • MTL_PARAMETERS — resolves the inventory organization code from the schedule line organization identifier.
  • PO_ASL_ATTRIBUTES — supplies the approved supplier list authorization flags, the scheduler identifier, and the enable-authorizations indicator.
  • PO_HEADERS and PO_LINES — provide the purchase order number (SEGMENT1), end date, line number, and vendor product number.
  • PO_LOOKUP_CODES, joined twice as PLC and PLC2 — supplies displayed field values used in the scheduling UI.
  • RCV_SHIPMENT_HEADERS and RCV_TRANSACTIONS — provide the last receipt number, transaction date, and received quantity.
  • PER_PEOPLE_F, joined twice as PPF1 and PPF2 — resolves the scheduler and buyer display names.
  • CHV_INQ_SV, FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY — supporting packages referenced for inquiry and security processing around the query.

Key Columns

Common Use Cases and Queries

Typical usage includes supplier scheduling dashboards, authorization review reports, receipt-versus-schedule reconciliation, and custom outbound interfaces feeding supplier portals. Because the view is not secured by row-level organization security in itself, queries are usually constrained by organization and item.

Schedule lines for a specific organization and item:

  • SELECT schedule_id, schedule_item_id, concatenated_segments, starting_cum_quantity, starting_auth_quantity, item_planning_method FROM apps.icx_chv_schedule_items_v WHERE organization_code = 'M1' AND concatenated_segments LIKE 'AS%';

Lines awaiting authorization together with buyer and scheduler names:

  • SELECT schedule_id, segment1, line_num, vendor_product_num, starting_auth_quantity FROM apps.icx_chv_schedule_items_v WHERE enable_authorizations_flag = 'Y' AND item_confirm_status IS NOT NULL ORDER BY segment1, line_num;

Most recent receipt per schedule line:

  • SELECT schedule_item_id, receipt_num, transaction_date, quantity FROM apps.icx_chv_schedule_items_v WHERE organization_id = :org_id AND last_receipt_transaction_id IS NOT NULL ORDER BY transaction_date DESC;

These queries illustrate the view's principal value: a single query returns scheduling, planning, purchasing, and receiving attributes that would otherwise require joins across at least nine base objects.