Search Results bom_calendars




Overview
Explore in AI Chat

Overview

The BOM_CALENDARS table is a foundational data object within the Oracle E-Business Suite (EBS) Bills of Material (BOM) module. It serves as the master repository for workday calendar definitions. These calendars are critical for modeling manufacturing and business operations, as they define the standard working days, shifts, and exceptions used for scheduling, capacity planning, lead time calculations, and inventory activities. The table's central role is evidenced by its numerous foreign key relationships across the BOM, Inventory (INV), and Shipping (WSH) modules, making it a key integration point for time-based functionality in the supply chain.

Key Information Stored

The table's primary identifier is the CALENDAR_CODE column, which is the unique key for each calendar definition. While the provided ETRM excerpt does not list all columns, standard implementation columns such as LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY are invariably present. The core business columns typically include a descriptive CALENDAR_NAME, an optional DESCRIPTION, and potentially a START_DATE_ACTIVE and END_DATE_ACTIVE to control the calendar's validity period. The specific workday patterns, shift details, and exception dates are not stored directly in this table but are defined in its related child tables, with BOM_CALENDARS acting as the header record.

Common Use Cases and Queries

This table is primarily referenced for setup validation, reporting, and as a constraint in transactional data entry. A common administrative query is to list all active calendars for a setup review. For example: SELECT calendar_code, description FROM bom_calendars WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);. In a manufacturing scheduling context, a query might join BOM_CALENDARS to BOM_CALENDAR_DATES to verify the workday pattern for a specific date range. Furthermore, integration points are often validated by checking if a calendar code referenced in MTL_PARAMETERS (the organization parameters) exists in BOM_CALENDARS, ensuring data integrity for inventory cycle counting and planning.

Related Objects

As documented in the ETRM, BOM_CALENDARS has a primary key relationship with numerous child and reference tables. The CALENDAR_CODE column is referenced by the following key objects: