Results for “chv_schedule_items”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The CHV_SCHEDULE_ITEMS table, owned by the PO schema, is a core transactional object within the Oracle E-Business Suite Supplier Scheduling (CHV) module. It stores the item-level detail lines that make up the supplier schedules generated and maintained by Oracle Supplier Scheduling. Each record represents a single scheduled item associated with a supplier schedule header, capturing the planning method, item identifiers, purchase order references, cumulative quantities, and receipt information that drive communication of demand to suppliers. In Oracle EBS 12.1.1 and 12.2.2, this table is central to the scheduling, confirm, and purge processes that keep supplier-facing schedules synchronized with internal planning data.

From a Data Vault modeling perspective, the metadata's heuristic classification identifies this object as standalone. This suggests the table functions as an independent hub-like entity in a dimensional or Data Vault model, rather than being modeled as a pure link or satellite. Practitioners designing analytical models may therefore treat SCHEDULE_ITEM_ID as a business key of a hub, with the descriptive and quantity columns modeled as satellite attributes.

Key Information Stored

CHV_SCHEDULE_ITEMS contains 43 documented columns. The most significant are:

• SCHEDULE_ITEM_ID — surrogate primary key; enforced by the unique index CHV_SCHEDULE_ITEMS_U1 and the only documented business-key candidate.
• SCHEDULE_ID — associates each item line with its parent schedule header.
• ORGANIZATION_ID — the inventory organization context for the scheduled item.
• ITEM_ID — the inventory item being scheduled; ITEM_PLANNING_METHOD defines how the item is planned.
• PO_HEADER_ID and PO_LINE_ID — link the schedule item back to the originating purchase order and line.
• STARTING_CUM_QUANTITY, STARTING_AUTH_QUANTITY and their _PRIMARY counterparts — opening cumulative and authorized quantities, captured in both purchasing and primary units of measure (PURCHASING_UNIT_OF_MEASURE, PRIMARY_UNIT_OF_MEASURE).
• LAST_RECEIPT_TRANSACTION_ID — the last receipt transaction relevant to the schedule item.
• ITEM_CONFIRM_STATUS, ITEM_CONFIRM_FLAG, REBUILD_FLAG, ITEM_PURGE_STATUS — status and control flags governing confirmation, rebuild, and purge behavior.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit context.
• Standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and ATTRIBUTE1–15 (with ATTRIBUTE_CATEGORY) for descriptive flexfield storage.

Common Use Cases and Queries

Typical scenarios include reporting schedule content by item, reconciling cumulative quantities against receipts, and identifying schedule items flagged for rebuild or purge. A representative query retrieves all items for a given schedule:

SELECT schedule_item_id, schedule_id, organization_id, item_id,
       item_planning_method, starting_cum_quantity
FROM   po.chv_schedule_items
WHERE  schedule_id = :p_schedule_id;

To find items awaiting confirmation, filter on ITEM_CONFIRM_STATUS. For purge maintenance, join to the referenced CHV_PURGE_SCHEDULE_LIST via SCHEDULE_ITEM_ID to determine which items are slated for removal. Analytics commonly aggregate STARTING_AUTH_QUANTITY by ITEM_ID and ORGANIZATION_ID to project supplier demand.

Related Objects

The primary documented relationship is the foreign key from CHV_SCHEDULE_ITEMS.SCHEDULE_ITEM_ID to CHV_PURGE_SCHEDULE_LIST, supporting purge processing. Beyond this, the table is joined to its parent schedule header (via SCHEDULE_ID), to purchase order headers and lines (via PO_HEADER_ID and PO_LINE_ID), and to inventory master items and organizations through ITEM_ID and ORGANIZATION_ID. Supplier Scheduling integration APIs and concurrent programs that generate, rebuild, confirm, or purge schedules read from and write to this table, making it a focal point for outbound supplier communication and inbound receipt reconciliation.