Results for “ship_schedule”

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

Overview

APPS.POS_SHIP_SCHEDULE_HEADERS_V is a reporting and inquiry view in Oracle E-Business Suite that consolidates supplier scheduling header information. It exposes the denormalized content of CHV_SCHEDULE_HEADERS — the base table that stores the header records for supplier ship schedules, planning schedules, and releases generated by the Oracle Supplier Scheduling module — joined to descriptive attributes from vendors, vendor sites, organizations, bucket patterns, owners, and lookup values. The view presents one row per schedule header, identified by ROWID and SCHEDULE_ID, with the foreign keys resolved into human-readable codes and names. Its role in EBS 12.1.1 and 12.2.2 is primarily as a query and reporting layer: it supports supplier scheduling inquiry forms, concurrent program output, and downstream integration extracts that need schedule header context without navigating multiple tables. Because it embeds PL/SQL package references (FND_GLOBAL, HR_GENERAL, HR_SECURITY) in the underlying segment of the definition, the view is also subject to organization-level and security-based filtering behavior typical of ETRM objects.

Underlying Base Objects

The view is defined over the following documented base objects:

• CHV_SCHEDULE_HEADERS — the driving table holding schedule header records.
• PO_VENDORS — supplies VENDOR_NAME and HOLD_FLAG.
• PO_VENDOR_SITES_ALL — supplies VENDOR_SITE_CODE.
• ORG_ORGANIZATION_DEFINITIONS — supplies ORGANIZATION_CODE and ORGANIZATION_NAME; joined with the outer (+) operator, making it an optional join.
• CHV_BUCKET_PATTERNS — supplies BUCKET_PATTERN_NAME and DESCRIPTION for the schedule's bucket pattern.
• PER_ALL_PEOPLE_F — supplies FULL_NAME for the schedule owner, date-effectively joined on SYSDATE.
• PO_LOOKUP_CODES — three aliases (PLC1, PLC2, PLC3) resolve SCHEDULE_TYPE, SCHEDULE_SUBTYPE, and SCHEDULE_STATUS into DISPLAYED_FIELD values, each with the outer (+) operator.
• FND_GLOBAL, HR_GENERAL, and HR_SECURITY packages — referenced in the full definition for session and security context.

Only PO_LOOKUP_CODES and ORG_ORGANIZATION_DEFINITIONS are themselves views; the remaining objects are accessed through synonyms in the APPS schema.

Key Columns

The view exposes the complete header column set of CHV_SCHEDULE_HEADERS plus resolved descriptions. Significant columns include:

• SCHEDULE_ID and SCHEDULE_NUM / SCHEDULE_REVISION — primary identifier and user-facing schedule number/revision.
• VENDOR_ID, VENDOR_NAME, HOLD_FLAG, VENDOR_SITE_ID, VENDOR_SITE_CODE — trading partner identification and hold status.
• BATCH_ID, SCHEDULE_TYPE, SCHEDULE_TYPE displayed field, SCHEDULE_SUBTYPE and its displayed field — classification of the schedule.
• SCHEDULE_HORIZON_START / SCHEDULE_HORIZON_END — planning horizon boundaries.
• SCHEDULE_OWNER_ID and FULL_NAME — the owner of the schedule.
• BUCKET_PATTERN_ID, BUCKET_PATTERN_NAME, DESCRIPTION — the time-bucket definition applied to the schedule.
• ORGANIZATION_ID, ORGANIZATION_CODE, ORGANIZATION_NAME — the owning inventory organization.
• CONFIRM_DATE, PRINT_COUNT, LAST_PRINT_DATE, EDI_COUNT, LAST_EDI_DATE — transmission and confirmation tracking.
• MPS_SCHEDULE_DESIGNATOR, MRP_COMPILE_DESIGNATOR, DRP_COMPILE_DESIGNATOR — planning compile context.
• SCHEDULE_STATUS and its displayed field, INQUIRY_FLAG, INCLUDE_FUTURE_RELEASES_FLAG — status and behavior flags.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF-enabled descriptive flexfield columns.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the concurrent request columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical uses include identifying all schedules for a supplier, reporting schedules exceeding their horizon end, and extracting EDI/print activity for a review window. Because the view already joins vendors, sites, owners, and lookups, it is well suited to ad-hoc reporting in Discoverer, BI Publisher, or SQL*Plus.

• Schedules for a specific supplier: SELECT SCHEDULE_NUM, VENDOR_NAME, SCHEDULE_STATUS FROM APPS.POS_SHIP_SCHEDULE_HEADERS_V WHERE VENDOR_ID = :p_vendor_id;
• Schedules by organization and horizon: SELECT SCHEDULE_NUM, ORGANIZATION_CODE, SCHEDULE_HORIZON_START, SCHEDULE_HORIZON_END FROM APPS.POS_SHIP_SCHEDULE_HEADERS_V WHERE ORGANIZATION_ID = :p_org_id AND TRUNC(SCHEDULE_HORIZON_END) < TRUNC(SYSDATE);
• EDI transmission activity: SELECT SCHEDULE_NUM, EDI_COUNT, LAST_EDI_DATE FROM APPS.POS_SHIP_SCHEDULE_HEADERS_V WHERE EDI_COUNT > 0 ORDER BY LAST_EDI_DATE DESC;
• Open schedules on hold: SELECT SCHEDULE_NUM, VENDOR_NAME, HOLD_FLAG FROM APPS.POS_SHIP_SCHEDULE_HEADERS_V WHERE HOLD_FLAG = 'Y';

When querying, note that PO_VENDORS and the lookup joins apply outer-join semantics in places, and that PER_ALL_PEOPLE_F restricts results to owners whose effective date range covers the current date. Reports relying on the owner name should therefore be validated against historical data expectations.