Search Results bucket_pattern_name

Overview

ICX_PLAN_SCHEDULE_HEADERS_V is a VALID APPS-owned view in Oracle E-Business Suite (12.1.1 and 12.2.2) that belongs to the ICX – Oracle iProcurement product. According to the ETRM reference metadata, its purpose is to select schedule and vendor information for planning schedules. The view consolidates scheduling headers, supplier master data, organization parameters, bucket pattern definitions, and lookup-code display values into a single denormalized result set suitable for reporting, iProcurement planning-schedule pages, and integration extracts. Because planning schedules drive supplier collaboration through ship, master production, and distribution schedule releases, the view serves as a convenient access layer over the underlying CHV_SCHEDULE_HEADERS data. The inclusion of CONFIRM_DATE, PRINT_COUNT, EDI_COUNT, and their associated date columns makes it particularly relevant for tracking supplier acknowledgements and release transmission history.

Underlying Base Objects

The view is defined over a fixed join of the following documented base objects: CHV_SCHEDULE_HEADERS (the driving synonym for schedule header records), PO_VENDORS, PO_VENDOR_SITES, MTL_PARAMETERS, PO_LOOKUP_CODES (aliased three times for SCHEDULE_TYPE, SCHEDULE_SUBTYPE, and SCHEDULE_STATUS display values), CHV_BUCKET_PATTERNS, and HR_EMPLOYEES. The join predicates link VENDOR_ID to PO_VENDORS, VENDOR_SITE_ID to PO_VENDOR_SITES, ORGANIZATION_ID to MTL_PARAMETERS (outer join), SCHEDULE_TYPE and SCHEDULE_SUBTYPE to PO_LOOKUP_CODES (outer joins), BUCKET_PATTERN_ID to CHV_BUCKET_PATTERNS, and SCHEDULE_OWNER_ID to HR_EMPLOYEES. The documented metadata additionally lists FND_GLOBAL, FND_PROFILE, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY as referenced objects, which reflects the HR security and name-formatting dependencies used at runtime rather than direct textual references.

Key Columns

• SCHEDULE_ID – Primary key of the planning schedule header; the anchor for downstream schedule line and detail queries.
• CONFIRM_DATE – The date on which the planning schedule was confirmed; the attribute most commonly searched in supplier collaboration and acknowledgement reporting.
• VENDOR_ID / VENDOR_NAME / VENDOR_SITE_ID / VENDOR_SITE_CODE / HOLD_FLAG – Supplier identification and site-level attributes joined from PO_VENDORS and PO_VENDOR_SITES.
• SCHEDULE_TYPE / SCHEDULE_SUBTYPE / SCHEDULE_STATUS – Encoded schedule classifications, with DISPLAYED_FIELD values provided by the PO_LOOKUP_CODES instances PLC1, PLC2, and PLC3.
• SCHEDULE_NUM / SCHEDULE_REVISION – Schedule number and revision for external communication.
• SCHEDULE_HORIZON_START / SCHEDULE_HORIZON_END – Effective horizon dates of the schedule.
• BUCKET_PATTERN_ID / BUCKET_PATTERN_NAME / DESCRIPTION – Bucket pattern used to group schedule quantities across time fences.
• ORGANIZATION_ID / ORGANIZATION_CODE – Inventory organization context from MTL_PARAMETERS.
• PRINT_COUNT / LAST_PRINT_DATE / EDI_COUNT / LAST_EDI_DATE – Release transmission metrics used to monitor whether schedules have been printed or transmitted via EDI.
• MPS_SCHEDULE_DESIGNATOR / MRP_COMPILE_DESIGNATOR / DRP_COMPILE_DESIGNATOR – Planning designators linking the schedule to MPS, MRP, or DRP compilations.
• INQUIRY_FLAG / INCLUDE_FUTURE_RELEASES_FLAG – Behavioral flags governing schedule visibility and release scope.
• ATTRIBUTE1–ATTRIBUTE15, REQUEST_ID, PROGRAM_ID, WHO columns – Standard EBS descriptive flexfield and audit columns.

Common Use Cases and Queries

Typical uses include supplier-facing schedule inquiries, acknowledgement tracking via CONFIRM_DATE, transmission auditing through PRINT_COUNT and EDI_COUNT, and organization-level schedule reporting. A representative query filtered on the user's searched column follows:

SELECT schedule_id, schedule_num, vendor_name, vendor_site_code, schedule_status, confirm_date, last_edi_date FROM apps.icx_plan_schedule_headers_v WHERE confirm_date >= SYSDATE - 30 ORDER BY confirm_date DESC;

Additional patterns include restricting by organization (WHERE organization_id = :p_org_id), joining to CHV_SCHEDULE_LINES for quantity detail on SCHEDULE_ID, and using the lookup display fields for status dashboards. Because the view is not secured by row-level supplier access, suppliers querying through iProcurement should be scoped by vendor and site identifiers supplied by the application layer.