Search Results item_planning_method




Overview
Explore in AI Chat

Overview

ICX_CHV_SCHEDULE_LINES_V is an APPS-owned database view within the Oracle iProcurement (ICX) product family, present in Oracle E-Business Suite releases 12.1.1 and 12.2.2. ETRM classifies the object with a status of VALID but a description of "Obsolete," indicating that although the view still exists and resolves within the data dictionary, it is no longer part of the strategic functional path for iProcurement. Historically, the view served as a reporting and integration surface for supplier scheduling data managed through the Collaborative Hosted Vendor (CHV) module, exposing schedule item details joined to item master, purchasing, and supplier list attributes.

Underlying Base Objects

The view is defined over a join of several base objects. The driving table is CHV_SCHEDULE_ITEMS (aliased CSI), which is joined to CHV_SCHEDULE_HEADERS (CSH) on SCHEDULE_ID. Item attributes are drawn from MTL_SYSTEM_ITEMS (MSI) and MTL_SYSTEM_ITEMS_KFV (MSIK), joined on ORGANIZATION_ID and ITEM_ID, with MTL_PARAMETERS (MTP) supplying the organization code. Purchasing context is provided by PO_HEADERS_ALL (POH) and PO_LINES (POL). Supplier authorization and vendor data come from PO_ASL_ATTRIBUTES (PAA) and PO_APPROVED_SUPPLIER_LIST (PAS). Buyer names are resolved from PER_PEOPLE_F (PPF2 via an outer join on MSI.BUYER_ID, and PPF1 for scheduler names), and PO_LOOKUP_CODES (PLC) supplies lookup display values. The documented dependency list also references the CHV_INQ_SV package along with FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY, reflecting the security and localization logic embedded in the view lineage.

Key Columns

The view exposes schedule identifiers (SCHEDULE_ID, SCHEDULE_ITEM_ID), organizational keys (ORGANIZATION_ID, ORGANIZATION_CODE), and item keys (ITEM_ID, CONCATENATED_SEGMENTS, DESCRIPTION). For planning and procurement, notable columns include FULL_LEAD_TIME, MINIMUM_ORDER_QUANTITY, MAXIMUM_ORDER_QUANTITY, FIXED_LOT_MULTIPLIER, ITEM_PLANNING_METHOD, and BUYER_ID with the corresponding buyer FULL_NAME. Cumulative and authorization quantities are surfaced through STARTING_CUM_QUANTITY, STARTING_AUTH_QUANTITY, and their primary-unit counterparts (STARTING_CUM_QTY_PRIMARY, STARTING_AUTH_QTY_PRIMARY). The view also carries purchasing unit-of-measure and primary unit-of-measure, PO header and line references (PO_HEADER_ID, SEGMENT1, END_DATE, PO_LINE_ID, LINE_NUM), authorization controls (ENABLE_AUTHORIZATIONS_FLAG, SCHEDULER_ID), confirmation state (REBUILD_FLAG, ITEM_CONFIRM_STATUS), the primary vendor item (PRIMARY_VENDOR_ITEM), and the standard 15 descriptive flexfield ATTRIBUTE columns.

Common Use Cases and Queries

Because the object is marked obsolete, current implementations typically query it only for historical reconciliation or legacy report migration. A representative query retrieving lead time and order constraints for a schedule is shown below.

  • SELECT schedule_id, organization_code, concatenated_segments, full_lead_time, minimum_order_quantity, maximum_order_quantity FROM icx_chv_schedule_lines_v WHERE schedule_id = :p_schedule_id;
  • SELECT item_id, buyer_id, full_name, primary_vendor_item FROM icx_chv_schedule_lines_v WHERE organization_id = :p_org_id AND item_planning_method IS NOT NULL;
  • SELECT po_header_id, segment1, po_line_id, line_num, starting_auth_quantity FROM icx_chv_schedule_lines_v WHERE enable_authorizations_flag = 'Y';

Queries referencing FULL_LEAD_TIME should account for the obsolete status and validate results against the supported supplier scheduling views before relying on them for operational decisions.