Search Results chv_schedule_items_v




Overview
Explore in AI Chat

Overview

APPS.CHV_SCHEDULE_ITEMS_V is a Supplier Scheduling (CHV) view that consolidates schedule line data with item master, planning, purchasing, and supplier authorization attributes. In Oracle EBS 12.1.1 and 12.2.2, it serves as a denormalized read model over the CHV_SCHEDULE_ITEMS and CHV_SCHEDULE_HEADERS tables, enriched with descriptive and planning columns sourced from Oracle Inventory, Oracle Purchasing, and Oracle HR. Because the status is VALID and the object is a view rather than a table, no physical storage or DML is associated with it; all access is read-only.

The view is particularly relevant to suppliers and planners who need to review item-level scheduling attributes such as minimum and maximum order quantities, fixed lot multipliers, cumulative and authorized quantities, and purchasing unit of measure. The MAXIMUM_ORDER_QUANTITY column of interest is sourced from MTL_SYSTEM_ITEMS, making this view a convenient single source for order quantity constraints alongside schedule context.

Underlying Base Objects

The view is defined with inner joins across several base objects and outer joins for buyer and planner name resolution:

Key Columns

Common Use Cases and Queries

Typical scenarios include reviewing order quantity limits per supplier schedule, reconciling cumulative authorizations, and exporting schedule lines for supplier portals or EDI releases.

  • Identify items with a maximum order quantity set: SELECT SCHEDULE_ID, ITEM_ID, CONCATENATED_SEGMENTS, MINIMUM_ORDER_QUANTITY, MAXIMUM_ORDER_QUANTITY, FIXED_LOT_MULTIPLIER FROM APPS.CHV_SCHEDULE_ITEMS_V WHERE MAXIMUM_ORDER_QUANTITY IS NOT NULL;
  • List scheduled items for a specific organization with buyer names: SELECT ORGANIZATION_CODE, CONCATENATED_SEGMENTS, DESCRIPTION, FULL_NAME FROM APPS.CHV_SCHEDULE_ITEMS_V WHERE ORGANIZATION_ID = :org_id;
  • Join to headers for schedule detail: SELECT v.* FROM APPS.CHV_SCHEDULE_ITEMS_V v, APPS.CHV_SCHEDULE_HEADERS h WHERE v.SCHEDULE_ID = h.SCHEDULE_ID AND h.SCHEDULE_ID = :schedule_id;

Because buyer and planner name columns are resolved through effective-dated PER_PEOPLE_F outer joins, results reflect the person effective as of the query execution date.