Results for “bucket_pattern_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ICX_SHIP_SCHEDULE_HEADERS_V is a VALID view owned by the APPS schema in Oracle E-Business Suite, belonging to the ICX — Oracle iProcurement product family. It was designed to select schedule and vendor information for shipment schedules, exposing the header-level attributes of supplier shipping schedules to iProcurement and related reporting and integration flows. The view consolidates data that would otherwise require joining supplier master data, schedule headers, bucket patterns, organization parameters, and lookup codes, presenting a single denormalized row set for each schedule header.

The view is present in both 12.1.1 and 12.2.2 environments, and the ETRM documentation records it as valid with the same column projection and join structure across those releases. Because it is a read-only projection, it does not carry DML semantics and is intended purely for query access.

Underlying Base Objects

The documented base objects are CHV_BUCKET_PATTERNS (SYNONYM), CHV_SCHEDULE_HEADERS (SYNONYM), FND_GLOBAL (PACKAGE), FND_PROFILE (PACKAGE), HR_EMPLOYEES (VIEW), HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), MTL_PARAMETERS (SYNONYM), PO_LOOKUP_CODES (VIEW), PO_VENDORS (VIEW) and PO_VENDOR_SITES (VIEW). The core driver is CHV_SCHEDULE_HEADERS (aliased CSH); the vendor name and hold flag come from PO_VENDORS, and the site code from PO_VENDOR_SITES. MTL_PARAMETERS supplies the organization code, CHV_BUCKET_PATTERNS supplies the bucket pattern name and description, and PO_LOOKUP_CODES is joined three times (PLC1, PLC2, PLC3) to decode schedule type, schedule subtype and schedule status into displayed field values. HR_EMPLOYEES supplies the schedule owner's full name using the HR name and security packages.

All joins are inner joins except the MTL_PARAMETERS join, which is outer-joined on ORGANIZATION_ID, and the lookup joins, which are also outer-joined. This design ensures schedule header rows are retained even when an organization parameter record or a matching lookup code is absent.

Key Columns

The view exposes the primary key SCHEDULE_ID together with VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE_CODE and HOLD_FLAG, providing complete supplier context. Scheduling attributes include SCHEDULE_TYPE, SCHEDULE_SUBTYPE, SCHEDULE_NUM, SCHEDULE_REVISION, SCHEDULE_HORIZON_START and SCHEDULE_HORIZON_END. The CONFIRM_DATE column, which is frequently queried, records the confirmation date associated with the schedule header.

Other notable columns include SCHEDULE_OWNER_ID and FULL_NAME, BUCKET_PATTERN_ID, BUCKET_PATTERN_NAME and DESCRIPTION, ORGANIZATION_ID and ORGANIZATION_CODE, PRINT_COUNT, LAST_PRINT_DATE, EDI_COUNT, LAST_EDI_DATE, the MPS, MRP and DRP compile designators, SCHEDULE_STATUS, INQUIRY_FLAG and INCLUDE_FUTURE_RELEASES_FLAG. Fifteen ATTRIBUTE columns plus the standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and concurrent request columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also included.

Common Use Cases and Queries

Typical uses include iProcurement supplier schedule inquiries, schedule release reporting, and EDI transmission auditing. A common query filters on the confirmation date and organization:

• SELECT schedule_id, schedule_num, vendor_name, confirm_date FROM apps.icx_ship_schedule_headers_v WHERE TRUNC(confirm_date) >= TRUNC(SYSDATE)-30;
• SELECT vendor_name, vendor_site_code, schedule_num, schedule_status FROM apps.icx_ship_schedule_headers_v WHERE organization_code = 'M1' AND schedule_type = 'SHIP_SCHEDULE';
• SELECT schedule_id, full_name, last_print_date, last_edi_date FROM apps.icx_ship_schedule_headers_v WHERE inquiry_flag = 'Y';

Because the view inherits HR security logic through HR_EMPLOYEES, results may be constrained by the querying user's security profile. Queries should therefore be tested under the intended responsibility before being embedded in custom reports or integrations.