Search Results last_receipt_quantity




Overview

The view APPS.CHV_CUM_ITEMS_HISTORY_V presents cumulative (cum) receipt history information for supplier items associated with Approved Supplier List (ASL) sourcing rules. It consolidates vendor, vendor site, item, organization, and cumulative receipt period data into a single queryable structure, exposing metrics such as cumulative quantity received, cumulative period boundaries, and the details of the most recent receipt. The view is classified as a supplementary view used to simplify Oracle Forms coding.

The view includes a documented warning that Oracle does not recommend querying or altering data through it, because its definition may change dramatically across minor or major releases. This means the view is intended primarily as a Forms support mechanism rather than a stable integration interface. In Oracle EBS 12.1.1 and 12.2.2 the same caution applies; organizations that require a supported reporting interface should extract directly from the underlying base objects or use approved ETRM-documented views.

Underlying Base Objects

The view is defined over a set of base objects spanning purchasing, human resources, and cumulative receipt period tables. The documented dependencies are:

The view is not referenced by any other database object, confirming it is a terminal, presentation-layer view.

Key Columns

Common Use Cases and Queries

Typical use is reporting on cumulative receipt activity against ASL items, examining the last receipt recorded in each cum period, and validating cumulative quantity thresholds for supplier agreements. The following sample returns last receipt information per item and vendor:

  • SELECT vendor_name, item_num, cum_period_name, cum_quantity_received, last_receipt_number, last_receipt_date, last_receipt_quantity FROM apps.chv_cum_items_history_v WHERE org_id = :org_id ORDER BY vendor_name, item_num;
  • SELECT vendor_site_code, item_num, last_receipt_quantity FROM apps.chv_cum_items_history_v WHERE last_receipt_date BETWEEN :from_date AND :to_date;

Because the view is flagged as not recommended for direct querying, consumers should treat results as informational and confirm behavior against the base objects CHV_CUM_PERIODS, PO_VENDORS, and MTL_SYSTEM_ITEMS_KFV before building production integrations.