Search Results schedule_type_name




Overview
Explore in AI Chat

Overview

The APPS.CHV_SCHEDULE_HEADERS_ALL_V view belongs to the CHV (Supplier Scheduling) product within Oracle E-Business Suite and is documented as a retrofitted object in ETRM 12.1.1 and 12.2.2. It presents supplier schedule header information in a denormalized, human-readable form by joining the base schedule header table to vendor, vendor site, inventory organization, and lookup code sources. Rather than exposing raw identifiers alone, the view supplies descriptive attributes such as ORGANIZATION_CODE, VENDOR_NAME, VENDOR_SITE_CODE, and the decoded SCHEDULE_TYPE_NAME, which makes it particularly convenient for reporting, supplier-facing extracts, and integration interfaces that need to display schedule context without additional joins.

The status of the object is VALID in the APPS schema, and it is a standard public view available to reporting tools, concurrent programs, and custom PL/SQL in both the 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The view is defined over five documented base objects. The driving table is CHV_SCHEDULE_HEADERS (referenced through a synonym), which stores the schedule header rows themselves, including schedule number, revision, horizon start, organization, vendor, and schedule type. Supporting objects are joined as follows:

  • PO_LOOKUP_CODES (view) — outer-joined on LOOKUP_TYPE = 'SCHEDULE_TYPE' to resolve the code in SCHEDULE_TYPE to its displayed value.
  • PO_VENDORS (view) — supplies VENDOR_NAME for the schedule's vendor.
  • PO_VENDOR_SITES (view) — supplies VENDOR_SITE_CODE for the schedule's vendor site.
  • MTL_PARAMETERS (synonym) — supplies ORGANIZATION_CODE for the owning inventory organization.
  • FND_GLOBAL (package) — referenced in the documented dependency metadata, typically for multi-org and security context at runtime.

Because vendor, vendor site, and organization joins are driven from the header row, the view returns one row per schedule header, subject to the outer join behavior on lookup, organization, and related lookups.

Key Columns

  • SCHEDULE_NUM, SCHEDULE_REVISION — business identifiers for the supplier schedule and its revision.
  • SCHEDULE_ID — surrogate primary identifier, usable for joins back to CHV_SCHEDULE_HEADERS and schedule line tables.
  • ORGANIZATION_CODE — inventory organization code derived from MTL_PARAMETERS; the column that most directly answers the user's search for schedule_type_name context.
  • VENDOR_NAME, VENDOR_SITE_CODE — supplier and ship-to site descriptors.
  • SCHEDULE_HORIZON_START — the beginning date of the schedule horizon.
  • SCHEDULE_TYPE — the raw lookup code for the schedule type.
  • SCHEDULE_TYPE_NAME — the decoded displayed value from PO_LOOKUP_CODES, populated only when the lookup code matches an active SCHEDULE_TYPE lookup.

Common Use Cases and Queries

Typical uses include listing active supplier schedules for a vendor, filtering schedules by schedule type, and providing the schedule type description in supplier-facing reports or interfaces.

SELECT schedule_num,
       schedule_revision,
       vendor_name,
       vendor_site_code,
       organization_code,
       schedule_horizon_start,
       schedule_type,
       schedule_type_name
  FROM apps.chv_schedule_headers_all_v
 WHERE schedule_type_name = :p_schedule_type_name
 ORDER BY schedule_horizon_start DESC;

A vendor-scoped variant filters on VENDOR_NAME or VENDOR_SITE_CODE, while an organization-scoped query restricts on ORGANIZATION_CODE. Because SCHEDULE_TYPE is outer-joined to the lookup, queries restricted by SCHEDULE_TYPE_NAME implicitly exclude rows whose lookup value is not maintained in PO_LOOKUP_CODES, so validating lookup maintenance is advisable before relying on the name column in extracts.