Search Results bom_cal_week_start_dates




Overview
Explore in AI Chat

Overview

The BOM_CAL_WEEK_START_DATES table is a core data structure within the Oracle E-Business Suite Bills of Material (BOM) module. It functions as a supporting table for the workday calendar system, specifically designed to define the weekly pattern of operations. Its primary role is to store the designated start date for each week within a manufacturing or work calendar. This table is essential for accurate scheduling, capacity planning, and lead-time calculations, as it provides the temporal framework against which workday exceptions and shifts are applied. The data in this table, in conjunction with the BOM_CALENDARS and BOM_EXCEPTION_SETS tables, enables the system to model complex, non-continuous work schedules that reflect real-world operational patterns in manufacturing and supply chain execution.

Key Information Stored

The table stores a unique combination of identifiers and a date to define a week's commencement within a specific calendar context. The primary key is a composite of three columns, ensuring each record is uniquely identifiable. The critical columns are:

  • CALENDAR_CODE: A foreign key referencing BOM_CALENDARS. This identifies the specific workday calendar to which the week start date belongs.
  • EXCEPTION_SET_ID: A foreign key referencing BOM_EXCEPTION_SETS. This links the week start date to a defined set of non-working day exceptions (e.g., holidays, plant shutdowns).
  • WEEK_START_DATE: The specific date that marks the beginning of a work week for the associated calendar and exception set. This is typically a recurring day, such as Monday.

Common Use Cases and Queries

This table is primarily accessed indirectly through the BOM calendar APIs and scheduling engines. A common use case is generating a schedule report that outlines the work weeks for a production line. For instance, a query might retrieve all week start dates for a given calendar to validate the calendar setup or to feed into a custom planning dashboard. A typical SQL pattern would involve joining to the parent tables for descriptive information:

SELECT bc.calendar_code, bc.description, bes.exception_set_name, bcwsd.week_start_date
FROM bom_cal_week_start_dates bcwsd,
bom_calendars bc,
bom_exception_sets bes
WHERE bcwsd.calendar_code = bc.calendar_code
AND bcwsd.exception_set_id = bes.exception_set_id
AND bc.calendar_code = 'PROD_CAL_2024'
ORDER BY bcwsd.week_start_date;

This data is fundamental for backward scheduling from a due date, as the system traverses the calendar, using the defined week start dates and associated exceptions to count only valid working days.

Related Objects

The BOM_CAL_WEEK_START_DATES table has defined foreign key relationships with two key parent tables in the BOM calendar hierarchy, as documented in the ETRM metadata:

  • BOM_CALENDARS: The table is linked via the CALENDAR_CODE column. This relationship ensures every week start date is associated with a valid, defined workday calendar.
  • BOM_EXCEPTION_SETS: The table is linked via the EXCEPTION_SET_ID column. This relationship ties the weekly pattern to a specific collection of non-working days, allowing for flexible calendar modeling.

This table is a foundational component referenced by the BOM calendar engine and is integral to the functionality of modules that depend on accurate time-phased data, including Manufacturing, Planning, and Supply Chain Management.