Results for “pos_ship_schedule_headers_v”

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

Overview

POS_SHIP_SCHEDULE_HEADERS_V is an APPS-owned database view in Oracle E-Business Suite, delivered as part of the POS (iSupplier Portal) product family. Its documented purpose is to select schedule and vendor information for shipment schedules, exposing the header-level attributes that drive supplier-facing shipment scheduling in the iSupplier Portal. The view is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2, and its definition is identical in structure across those releases, drawing on the same CHV scheduling tables and PO vendor views. It functions as a reporting and integration surface rather than a transactional entity: no data is stored in the view itself, and all attributes are inherited from the underlying scheduling, vendor, organization, and HR objects. For the user search term "ship_schedule", this view is the most directly relevant header-level object, since it consolidates the schedule identifiers, vendor identifiers, status lookups, bucket pattern, and organization context needed to report on or extract released shipment schedules.

Underlying Base Objects

The view is defined over the following documented base objects, joined on the conditions shown below:

• CHV_SCHEDULE_HEADERS (aliased CSH) — the driving table, supplying schedule identity, horizon, status, batch, revision, and the descriptive flexfield (ATTRIBUTE1–15) columns.
• PO_VENDORS (POV) — joins on VENDOR_ID to supply VENDOR_NAME and HOLD_FLAG.
• PO_VENDOR_SITES_ALL (PVS) — joins on VENDOR_SITE_ID to supply VENDOR_SITE_CODE.
• ORG_ORGANIZATION_DEFINITIONS (ORG) — outer-joined on ORGANIZATION_ID (marked with the (+) operator) to supply ORGANIZATION_CODE and ORGANIZATION_NAME.
• CHV_BUCKET_PATTERNS (CBP) — joins on BUCKET_PATTERN_ID to supply BUCKET_PATTERN_NAME and DESCRIPTION.
• PER_ALL_PEOPLE_F (PRF) — joins on SCHEDULE_OWNER_ID = PERSON_ID, constrained by the effective-date range (TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE) to return the current owner name in FULL_NAME.
• PO_LOOKUP_CODES (PLC1, PLC2, PLC3) — three aliased instances used to translate SCHEDULE_TYPE, SCHEDULE_SUBTYPE, and SCHEDULE_STATUS into readable DISPLAYED_FIELD values.
• FND_GLOBAL, HR_GENERAL, and HR_SECURITY are referenced by the view metadata, typically supporting multi-org and HR security predicates applied at runtime in 12.2.2.

The view therefore inherits the security and multi-org behavior of ORG_ORGANIZATION_DEFINITIONS and the effective-dated person logic of PER_ALL_PEOPLE_F.

Key Columns

• SCHEDULE_ID, SCHEDULE_NUM, SCHEDULE_REVISION — the unique identifiers and document numbering for the shipment schedule header.
• VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE_CODE, HOLD_FLAG — supplier identity and current hold status.
• SCHEDULE_TYPE, SCHEDULE_SUBTYPE, SCHEDULE_STATUS — raw lookup codes, with their translated values exposed through the DISPLAYED_FIELD columns from PLC1, PLC2, and PLC3.
• SCHEDULE_HORIZON_START, SCHEDULE_HORIZON_END — the planning horizon dates applied to the schedule.
• BUCKET_PATTERN_ID, BUCKET_PATTERN_NAME, DESCRIPTION — the bucket pattern that determines how demand is grouped within the schedule.
• ORGANIZATION_ID, ORGANIZATION_CODE, ORGANIZATION_NAME — the owning inventory organization.
• SCHEDULE_OWNER_ID, FULL_NAME — the current owner of the schedule, resolved through PER_ALL_PEOPLE_F.
• CONFIRM_DATE, PRINT_COUNT, LAST_PRINT_DATE, EDI_COUNT, LAST_EDI_DATE — publication and confirmation audit attributes indicating how and when the schedule was communicated.
• INQUIRY_FLAG, INCLUDE_FUTURE_RELEASES_FLAG — control flags affecting supplier visibility.
• MPS_SCHEDULE_DESIGNATOR, MRP_COMPILE_DESIGNATOR, DRP_COMPILE_DESIGNATOR — designators identifying the planning compilation that produced the schedule.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns for customer-defined data.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus REQUEST_ID and PROGRAM_ID/PROGRAM_APPLICATION_ID for concurrent program traceability.

Common Use Cases and Queries

Typical uses include supplier-facing schedule reporting in iSupplier Portal, reconciliation of released schedules against confirmations, and extraction of schedule headers for EDI or middleware integration. The view is commonly queried by organization and vendor to surface open schedules with translated status.

Sample query returning schedule headers with translated type and status:

• SELECT schedule_num, schedule_revision, vendor_name, vendor_site_code, organization_code, schedule_horizon_start, schedule_horizon_end, last_print_date, last_edi_date FROM pos_ship_schedule_headers_v WHERE organization_code = :org AND schedule_status = :status ORDER BY schedule_num;

Because the view joins PER_ALL_PEOPLE_F on the current effective date, queries execute within the session's effective HR context; results for schedule owners may change as person records are date-tracked. Organizations using multi-org security will also see only organizations permitted by their MOAC profile, since the ORG join and HR security packages apply at runtime.