Search Results wsh_calendar_assignments




Overview

The WSH_CALENDAR_ASSIGNMENTS table is a core data object within the Oracle E-Business Suite (EBS) Shipping Execution (WSH) module. Its primary function is to manage the association of working calendars to specific business entities involved in the shipping and fulfillment process. In EBS, working calendars define operational days and shifts, which are critical for calculating accurate delivery dates, lead times, and scheduling pickups. This table acts as a junction, linking calendars from the Bills of Material (BOM) module to vendors, customers, and specific shipping locations, thereby enabling precise and entity-specific scheduling logic throughout the order-to-cash cycle.

Key Information Stored

The table's structure centers on linking a calendar code to a specific entity. The primary identifier is the CALENDAR_ASSIGNMENT_ID. The key foreign key columns define the scope of the assignment: CALENDAR_CODE references the BOM_CALENDARS table, which holds the actual calendar definition. The entity being assigned a calendar is identified by one of three columns: VENDOR_ID (linking to PO_VENDORS), CUSTOMER_ID (linking to RA_CUSTOMERS), or LOCATION_ASSOCIATION_ID (linking to PO_LOCATION_ASSOCIATIONS for specific ship-to or bill-to locations). This design allows for granular control, enabling different calendars for different vendors, customers, or even specific customer sites.

Common Use Cases and Queries

A primary use case is determining the working calendar for a given shipping transaction to calculate a promised or scheduled ship date. For instance, when creating a delivery for a customer order, the system queries this table to find the calendar assigned to the customer's ship-to location, ensuring the scheduled date falls on a valid working day. Common reporting needs include auditing calendar coverage to identify vendors or customers without an assigned calendar, which can lead to scheduling errors. A sample query to find all calendar assignments for a specific vendor would be:

  • SELECT wca.calendar_assignment_id, wca.calendar_code, pv.vendor_name
  • FROM wsh_calendar_assignments wca, po_vendors pv
  • WHERE wca.vendor_id = pv.vendor_id
  • AND pv.segment1 = 'VENDOR123';

Related Objects

As indicated by its foreign keys, WSH_CALENDAR_ASSIGNMENTS has direct dependencies on several fundamental EBS tables. It draws its calendar definitions from BOM_CALENDARS. The entity assignments are validated against PO_VENDORS for suppliers, RA_CUSTOMERS for customers, and PO_LOCATION_ASSOCIATIONS for detailed address-level assignments. This table is integral to the shipping engine's scheduling APIs and is referenced by various shipping and planning processes that require date calculations based on entity-specific working days. Its primary key constraint, WSH_CALENDAR_ASSIGNMENTS_PK, ensures the uniqueness of each assignment record.