Results for “bom_calendars_view”

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

Overview

BOM_CALENDARS_VIEW is a read-only database view owned by the APPS schema in Oracle E-Business Suite, residing in the Bills of Material (BOM) product module. It is documented as valid in both EBS 12.1.1 and 12.2.2. As its description states, the view presents the contents of the BOM_CALENDARS table, exposing manufacturing calendar definitions used throughout the BOM and Work in Process (WIP) modules. Unlike a simple synonym or a pass-through view, BOM_CALENDARS_VIEW applies a deliberate row-level filter, so it does not expose every row present in the base table. This filtering behavior is the defining characteristic for any report, interface, or concurrent program that consumes the view.

Underlying Base Objects

The view is defined exclusively over the single documented base object BOM_CALENDARS, referenced through the alias BCAL. There are no joins to other tables. The projection list mirrors the base table columns directly, and the restricting predicate governs which calendar records are returned:

• WHERE NVL(BCAL.CALENDAR_START_DATE, SYSDATE-1) <= SYSDATE
• AND NVL(BCAL.CALENDAR_END_DATE, SYSDATE+1) > SYSDATE

The practical effect is that the view returns only those calendars that are active "as of today." When CALENDAR_START_DATE is null, it is treated as SYSDATE-1, which allows the row to pass the first condition. When CALENDAR_END_DATE is null, it is treated as SYSDATE+1, allowing the row to pass the second condition. Because the filter references SYSDATE, the result set is date-sensitive and can change from one day to the next without any modification to the underlying data. No database link or external object is involved.

Key Columns

The view exposes the full column list of BOM_CALENDARS. The columns most relevant to reporting and integration are:

• CALENDAR_CODE — the unique identifier for the manufacturing calendar.
• CALENDAR_START_DATE and CALENDAR_END_DATE — the effective date range of the calendar; these two columns drive the view's row filter and are the columns most commonly referenced by users searching for calendar_start_date.
• DAYS_ON and DAYS_OFF — categorical values indicating which days are working days versus non-working days.
• QUARTERLY_CALENDAR_TYPE — classification of the quarterly calendar behavior.
• DESCRIPTION — free-text description of the calendar.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS flexfield descriptive columns available for client-specific extensions.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, which track the last concurrent request that updated the record.

Common Use Cases and Queries

Because the view is pre-filtered to currently active calendars, it is commonly used in reports and interfaces where only in-force calendars are relevant, such as shop-floor scheduling, capacity lookups, and validation routines. A representative query retrieves active calendars and their effective ranges:

• SELECT calendar_code, calendar_start_date, calendar_end_date, days_on, days_off FROM apps.bom_calendars_view WHERE calendar_code = :p_calendar_code;

Note that a query for historical or future-dated calendars will not return rows through this view, since the SYSDATE predicate excludes them. In such cases the base table BOM_CALENDARS must be queried directly. Developers should also account for the dynamic nature of the filter and avoid caching results, because the returned set changes at each calendar day boundary.