Results for “pos_plan_schedule_headers_v”

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

Overview

APPS.POS_PLAN_SCHEDULE_HEADERS_V is a reporting view in the iSupplier Portal (POS) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to "select schedule and vendor info for planning schedules." It joins planning schedule header records from the Supply Chain Planning foundation (CHV tables) with supplier master data, operating unit organization definitions, bucket pattern definitions, employee/owner identification, and several lookup code displays. The view is primarily consumed by the iSupplier Portal planning schedule pages and by related concurrent programs and EDI publishing logic, allowing suppliers and internal planners to view schedule headers that are either published to the portal or transmitted via EDI.

The view is a security-sensitive construct because it is built over PO_VENDORS, PO_VENDOR_SITES_ALL and PER_ALL_PEOPLE_F, and ETRM metadata shows it references HR_SECURITY, HR_GENERAL and FND_GLOBAL, indicating row-level access controls and session context (user, responsibility, org) are applied at runtime.

Underlying Base Objects

The view text references the following base objects, consistent with ETRM 12.2.2 metadata:

• CHV_SCHEDULE_HEADERS (SYNONYM) — the driving table holding schedule header records.
• CHV_BUCKET_PATTERNS (SYNONYM) — bucket pattern definition joined on BUCKET_PATTERN_ID.
• PO_VENDORS (VIEW) and PO_VENDOR_SITES_ALL (VIEW) — supplier and supplier site attributes.
• ORG_ORGANIZATION_DEFINITIONS (VIEW) — operating unit details, outer-joined with (+).
• PER_ALL_PEOPLE_F (SYNONYM) — schedule owner name, date-effective filtered.
• PO_LOOKUP_CODES (VIEW) aliased three times (PLC1, PLC2, PLC3) for displayed field values of schedule type, subtype and status.
• FND_GLOBAL, HR_GENERAL, HR_SECURITY (PACKAGES) — session and security context invoked by the view's predicate logic.

Key Columns

• SCHEDULE_ID, SCHEDULE_NUM, SCHEDULE_REVISION — unique schedule identifier and revision.
• VENDOR_ID, VENDOR_NAME, VENDOR_NUMBER, HOLD_FLAG, VENDOR_SITE_ID, VENDOR_SITE_CODE — supplier identity and hold status.
• SCHEDULE_TYPE, SCHEDULE_SUBTYPE, SCHEDULE_STATUS with corresponding DISPLAYED_FIELD values from PO_LOOKUP_CODES.
• SCHEDULE_HORIZON_START, SCHEDULE_HORIZON_END — planning horizon boundaries.
• EDI_COUNT, LAST_EDI_DATE, PRINT_COUNT, LAST_PRINT_DATE — transmission and print audit counters, central to the user's edi_count search.
• CONFIRM_DATE, INQUIRY_FLAG, INCLUDE_FUTURE_RELEASES_FLAG — acknowledgement and visibility controls.
• MPS_SCHEDULE_DESIGNATOR, MRP_COMPILE_DESIGNATOR, DRP_COMPILE_DESIGNATOR — planning compilation identifiers.
• ORGANIZATION_ID, ORGANIZATION_CODE, ORGANIZATION_NAME — operating unit context.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1…ATTRIBUTE15, and audit columns (CREATED_BY, LAST_UPDATE_DATE, etc.).

Common Use Cases and Queries

A frequent use case is identifying published suppliers, requiring EDI_COUNT values:

SELECT SCHEDULE_NUM, VENDOR_NAME, VENDOR_SITE_CODE,
       SCHEDULE_STATUS, EDI_COUNT, LAST_EDI_DATE
FROM   APPS.POS_PLAN_SCHEDULE_HEADERS_V
WHERE  EDI_COUNT > 0
ORDER BY LAST_EDI_DATE DESC;

Another is listing schedules not yet transmitted:

SELECT SCHEDULE_NUM, VENDOR_NAME, SCHEDULE_HORIZON_START, SCHEDULE_HORIZON_END
FROM   APPS.POS_PLAN_SCHEDULE_HEADERS_V
WHERE  EDI_COUNT = 0
AND    ORGANIZATION_CODE = :p_org;

Planners also join this view to bucket lines and confirmations to reconcile acknowledgements, and to CHV_SCHEDULE_HEADERS via SCHEDULE_ID to derive additional header detail. Because HR_SECURITY predicates are applied, results are automatically filtered to the supplier and operating unit scope of the caller.