Search Results bom_period_start_dates_pk

Overview

The BOM_PERIOD_START_DATES table is a core data structure within the Bills of Material (BOM) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as the master repository for workday calendar period start dates. This table is essential for defining and maintaining manufacturing and planning calendars, which are critical for scheduling production, calculating lead times, and performing capacity planning. By storing the specific start dates for defined periods within a calendar, it enables the system to model work schedules accurately, accounting for non-working days and exceptions. Its integrity is maintained through primary and foreign key relationships with other foundational BOM calendar tables.

Key Information Stored

The table stores a unique combination of identifiers and a date to define each calendar period. The primary key is a composite of three columns, ensuring uniqueness for each period entry. The CALENDAR_CODE identifies the specific workday calendar to which the period belongs. The EXCEPTION_SET_ID links to a set of predefined exceptions (e.g., holidays) that apply to this calendar. The PERIOD_START_DATE column holds the actual calendar date that marks the beginning of a specific period within the defined calendar and exception set. Together, these columns allow the system to precisely map any operational date to its correct working calendar context.

Common Use Cases and Queries

This table is primarily queried for scheduling and reporting purposes within manufacturing and supply chain planning functions. A common use case is to validate or list all period start dates for a given production calendar to generate a shop floor schedule. For instance, planners may run a query to ascertain the working periods for the next fiscal quarter. A typical SQL pattern involves joining to the BOM_CALENDARS table to get calendar descriptions:

• SELECT bp.CALENDAR_CODE, bc.CALENDAR_DESC, bp.PERIOD_START_DATE FROM BOM.BOM_PERIOD_START_DATES bp, BOM.BOM_CALENDARS bc WHERE bp.CALENDAR_CODE = bc.CALENDAR_CODE AND bc.CALENDAR_CODE = 'MFG_CAL_2024';

Another critical use is in lead time calculations, where the system references this table to count only valid working days between two dates, skipping periods defined as non-working by the associated exception set.

Related Objects

The BOM_PERIOD_START_DATES table has defined foreign key relationships with two other key BOM tables, forming the backbone of the calendar data model. It references the BOM_CALENDARS table via the CALENDAR_CODE column. This relationship ensures that every period date is associated with a valid, predefined calendar. Secondly, it references the BOM_EXCEPTION_SETS table via the EXCEPTION_SET_ID column. This link attaches a specific set of non-working day exceptions (like company holidays) to the calendar periods. These relationships are critical for data integrity; the table's primary key (BOM_PERIOD_START_DATES_PK) is itself a foreign key to these parent tables.