Search Results pos_chv_schedule_items_v




Overview
Explore in AI Chat

Overview

POS_CHV_SCHEDULE_ITEMS_V is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the POS (iSupplier Portal) product. As documented in the ETRM repository for both 12.1.1 and 12.2.2, the view is one of the views used to select schedule related information. It consolidates scheduling line data from the Supplier Scheduling / Collaborative Planning capability and presents it alongside descriptive item, organization, sourcing, buyer, and receipt attributes in a single flattened projection. Rather than forcing a report or integration to join the fragmented underlying scheduling and purchasing tables manually, the view exposes a denormalized result set suited to supplier-facing schedule queries, Authorization to Ship (ATS) calculations, and inbound integration extracts.

Because the object resides in the APPS schema, it is secured through standard EBS data access mechanisms, including organization-level and HR security, since the definition references FND_GLOBAL, HR_GENERAL, and HR_SECURITY in addition to the CHV_INQ_SV package. In 12.2.2 the object carries a VALID status, confirming it remains an active, supported deliverable.

Underlying Base Objects

The view is defined over a large join across scheduling and purchasing base objects. Its documented referenced objects include CHV_SCHEDULE_ITEMS and CHV_SCHEDULE_HEADERS, the core schedule line and header tables; PO_HEADERS_ALL and PO_LINES_ALL for the associated purchase order context; PO_APPROVED_SUPPLIER_LIST and PO_ASL_ATTRIBUTES for sourcing and authorization settings; MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV for item attributes and concatenated segment display; ORG_ORGANIZATION_DEFINITIONS for organization code and name; PER_ALL_PEOPLE_F for scheduler and buyer names; PO_LOOKUP_CODES for displayed field resolution; and RCV_SHIPMENT_HEADERS plus RCV_TRANSACTIONS for receipt history. The view also references the CHV_INQ_SV, FND_GLOBAL, HR_GENERAL, and HR_SECURITY packages, which supply inquiry logic and session/security context.

The join is anchored on CHV_SCHEDULE_ITEMS (aliased CSI) and extends outward to CHV_SCHEDULE_HEADERS (CSH) for the schedule number, to the PO tables for header and line identification, and to the receiving tables for the last receipt details. This design means the view returns one row per schedule item, enriched with header, sourcing, item, and receipt data.

Key Columns

Identity columns include SCHEDULE_ID, SCHEDULE_ITEM_ID, and SCHEDULE_NUM, which uniquely locate a schedule line within its header. ORGANIZATION_ID, ORGANIZATION_CODE, and ORGANIZATION_NAME describe the inventory organization context. Item identification is provided by ITEM_ID, CONCATENATED_SEGMENTS, and DESCRIPTION, while planning attributes such as FULL_LEAD_TIME, MINIMUM_ORDER_QUANTITY, MAXIMUM_ORDER_QUANTITY, FIXED_LOT_MULTIPLIER, ITEM_PLANNING_METHOD, PRIMARY_UNIT_OF_MEASURE, and PURCHASING_UNIT_OF_MEASURE support replenishment logic.

Common Use Cases and Queries

Typical scenarios include building supplier schedule dashboards, reconciling ATS quantities, extracting schedule data for external planning systems, and auditing receipt history against open schedules. The following query returns active schedule lines with their PO and receipt context:

  • SELECT schedule_num, segment1, line_num, concatenated_segments, item_confirm_status, starting_auth_quantity, quantity, transaction_date FROM pos_chv_schedule_items_v WHERE organization_code = :org AND item_confirm_status = 'CONFIRMED';
  • SELECT schedule_item_id, concatenated_segments, full_name AS buyer, enable_authorizations_flag, primary_unit_of_measure FROM pos_chv_schedule_items_v WHERE buyer_id = :buyer_id ORDER BY schedule_num;
  • SELECT schedule_num, segment1, maximum_order_quantity, minimum_order_quantity, fixed_lot_multiplier FROM pos_chv_schedule_items_v WHERE item_id = :item_id;

Because the view already resolves organization, item, buyer, and vendor descriptions, reports can avoid additional joins to MTL_SYSTEM_ITEMS_KFV and ORG_ORGANIZATION_DEFINITIONS. Filtering by ORGANIZATION_ID and BUYER_ID is recommended to limit result sets and respect security context supplied through FND_GLOBAL.