Search Results confirm_date




Overview
Explore in AI Chat

Overview

CHV_SCHEDULE_HEADERS_VAL_V is a validation view owned by the APPS schema in Oracle E-Business Suite, defined within the CHV (Supplier Scheduling) product family. It is documented as a retrofitted object, meaning its definition was migrated to conform to later release standards across the 12.1.1 and 12.2.2 code lines. The view presents a consolidated, grouped picture of supplier schedule headers that have reached the CONFIRMED status, joining each header to its vendor, vendor site, inventory organization, and schedule type lookup description.

Because the view filters on CSH.SCHEDULE_STATUS = 'CONFIRMED', it exposes only authoritative, supplier-acknowledged schedules rather than draft or pending revisions. Its role is primarily reporting and validation: it supplies a single denormalized row per schedule so that downstream forms, concurrent programs, or integration extracts do not have to repeat the multi-table join logic. The presence of CONFIRM_DATE and SCHEDULE_REVISION as aggregated columns makes the view particularly relevant to queries that track when a schedule was confirmed and which revision it represents.

Underlying Base Objects

The view is defined over the following documented base objects:

The documented reference list also includes FND_GLOBAL (package), which supports multi-organization security context during execution. The join structure is inner throughout, so a schedule row only appears when a matching vendor, vendor site, organization parameter record, and schedule type lookup all exist.

Key Columns

  • CONFIRM_DATE — the maximum confirmation date across the rows aggregated under each schedule; commonly the target column when searching for "confirm_date".
  • SCHEDULE_REVISION — the maximum schedule revision, indicating the highest revision level for the grouped schedule.
  • SCHEDULE_ID, SCHEDULE_NUM — the internal key and user-facing identifier of the schedule header.
  • VENDOR_NAME, VENDOR_SITE_CODE — supplier and supplier site descriptive values.
  • ORGANIZATION_CODE — inventory organization code derived from MTL_PARAMETERS.
  • MULTI_ORG_FLAG — a DECODE expression returning 'Y' when CSH.ORGANIZATION_ID is null and 'N' otherwise, indicating whether the schedule is defined across multiple organizations.
  • SCHEDULE_HORIZON_START — the start of the scheduling horizon for the header.
  • SCHEDULE_TYPE, SCHEDULE_TYPE_NAME — the lookup code and its displayed description.

Common Use Cases and Queries

Typical use cases include confirmed-schedule reporting, supplier acknowledgement tracking, and identifying the latest confirmation timestamp per schedule. The following query returns confirmed schedules with their confirmation dates:

  • SELECT schedule_num, vendor_name, vendor_site_code, schedule_revision, confirm_date, schedule_type_name FROM chv_schedule_headers_val_v WHERE confirm_date IS NOT NULL ORDER BY confirm_date DESC;
  • SELECT schedule_num, confirm_date FROM chv_schedule_headers_val_v WHERE confirm_date >= :p_from_date AND confirm_date < :p_to_date;
  • SELECT organization_code, COUNT(*) FROM chv_schedule_headers_val_v GROUP BY organization_code;

Because CONFIRM_DATE and SCHEDULE_REVISION are produced by MAX aggregates and the outer query groups by schedule ID, vendor, site, organization, horizon start, and schedule type, results reflect one row per logical confirmed schedule. Consumers should therefore avoid expecting item-level or distribution-level detail from this view and instead join back to CHV_SCHEDULE_HEADERS or CHV_SCHEDULE_ITEMS when line-level granularity is required.