Search Results last_edi_date

Overview

The APPS.POS_CHV_SCHEDULE_HEADERS_V view is a Purchasing (PO) module reporting and integration object that presents supplier release scheduling header information in a denormalized, join-ready form. Its name reflects its lineage: it belongs to the Supplier Scheduling component of Oracle Purchasing (historically known as the "CHV" application, now subsumed within PO). The view consolidates scheduling header records from the base table CHV_SCHEDULE_HEADERS together with vendor, vendor site, organization, bucket pattern, and employee attributes so that consumers can query fully described scheduling records without performing the multi-table joins themselves.

In Oracle EBS 12.1.1 and 12.2.2 the view remains a VALID object owned by APPS. Because it resolves foreign keys into descriptive columns such as VENDOR_NAME, VENDOR_SITE_CODE, and ORGANIZATION_CODE, it is well suited for operational reports, concurrent program output, EDI/release-advice integrations, and ad hoc data extraction related to supplier schedules, releases, and confirmations.

Underlying Base Objects

The view text joins the scheduling header table to several related objects using the ANSI/legacy join syntax standard in EBS views. The documented referenced base objects are:

• CHV_SCHEDULE_HEADERS — the driver table (aliased CSH) supplying schedule identity, horizon dates, counts, and status.
• PO_VENDORS (a view) — supplies supplier name and hold flag.
• PO_VENDOR_SITES_ALL (a view) — supplies the vendor site code, joined on VENDOR_SITE_ID.
• ORG_ORGANIZATION_DEFINITIONS (a view) — joined with an outer (+) operator on ORGANIZATION_ID to return organization code and name.
• CHV_BUCKET_PATTERNS — supplies bucket pattern name and description.
• PER_ALL_PEOPLE_F (a synonym) — joined with an outer (+) on SCHEDULE_OWNER_ID to return the owner's full name.
• PO_LOOKUP_CODES (a view) and package references FND_GLOBAL, HR_GENERAL, and HR_SECURITY — supporting lookup decoding and security/MOAC context.

The joins are predominantly inner joins on vendor, vendor site, and bucket pattern, with outer joins preserved for organization and person so that schedules without those references still appear.

Key Columns

• SCHEDULE_ID — primary identifier of the scheduling header.
• VENDOR_ID, VENDOR_NAME, HOLD_FLAG — supplier identity and whether the vendor is on hold.
• VENDOR_SITE_ID, VENDOR_SITE_CODE — ship-to/ordering supplier site.
• SCHEDULE_NUM, SCHEDULE_REVISION — the schedule number and revision level.
• SCHEDULE_TYPE, SCHEDULE_SUBTYPE (and their decoded _NAME columns) — classification of the schedule.
• SCHEDULE_HORIZON_START, SCHEDULE_HORIZON_END — planning horizon boundaries.
• CONFIRM_DATE — the date the schedule was confirmed, central to confirmation tracking and to the search term "confirm_date".
• PRINT_COUNT, LAST_PRINT_DATE, EDI_COUNT, LAST_EDI_DATE — transmission and print history.
• BUCKET_PATTERN_ID, BUCKET_PATTERN_NAME, DESCRIPTION — demand time-bucket definition.
• ORGANIZATION_ID, ORGANIZATION_CODE, ORGANIZATION_NAME — owning inventory organization.
• SCHEDULE_OWNER_ID, FULL_NAME — the schedule owner (buyer/planner).
• SCHEDULE_STATUS, INQUIRY_FLAG, INCLUDE_FUTURE_RELEASES_FLAG — processing state flags.
• Audit columns — LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, and related who/request columns.

Common Use Cases and Queries

A frequent requirement is to identify schedules confirmed within a date range, which maps directly to the CONFIRM_DATE column:

• Confirmation audit: SELECT SCHEDULE_ID, SCHEDULE_NUM, VENDOR_NAME, VENDOR_SITE_CODE, CONFIRM_DATE FROM APPS.POS_CHV_SCHEDULE_HEADERS_V WHERE CONFIRM_DATE >= :p_from_date AND CONFIRM_DATE < :p_to_date ORDER BY CONFIRM_DATE DESC;
• Release transmission monitoring: query LAST_EDI_DATE, EDI_COUNT, and SCHEDULE_STATUS to find schedules awaiting or failing transmission.
• Supplier-facing reporting: join to release lines by SCHEDULE_ID to produce a denormalized release report including vendor and site descriptions.
• Ownership and org analysis: aggregate by FULL_NAME, ORGANIZATION_CODE, or BUCKET_PATTERN_NAME for workload and planning views.

Because EBS enforces multi-org and HR security through the referenced packages, reports should be created within an appropriately configured responsibility so that organization and person security filters apply. The view is read-only and inherits data directly from its base objects, so results reflect the live scheduling tables at query time.