Results for “database_in_sync”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BOM_CALENDARS is the master definition table for workday calendars in Oracle EBS Bills of Material (BOM). Each row defines a named calendar — identified by CALENDAR_CODE — that describes which days are working days versus non-working days, along with the calendar's effective start and end dates, working/off-day patterns, quarterly characteristics, and descriptive text. The table is owned by the BOM schema and resides in the BOM product module.
Functionally, BOM_CALENDARS acts as a reusable reference object: manufacturing, inventory, and shipping processes select a calendar by code and then use it to schedule work, compute lead times, plan cycle counts, or determine valid shipping and receiving dates. In Oracle EBS 12.1.1 and 12.2.2, this table is populated and maintained through the BOM workday calendar maintenance forms and concurrent programs.
Based on the foreign-key structure mined from the ETRM metadata, the heuristic Data Vault classification for this object is hub-leaning. In Data Vault terms, CALENDAR_CODE behaves as a stable business key representing a single calendar entity, with the surrounding BOM_CALENDAR_DATES, BOM_CALENDAR_SHIFTS, and BOM_WORKDAY_PATTERNS rows acting as satellite-style children describing the calendar's detail and patterns. This classification is a modeling suggestion inferred from the FK topology, not an Oracle-documented designation.
Key Information Stored
BOM_CALENDARS is documented with 33 physical columns. The most significant for application and reporting purposes are listed below.
- CALENDAR_CODE — the business key and primary key (BOM_CALENDARS_PK, enforced by unique index BOM_CALENDARS_U1). This is the value other tables store as the calendar reference.
- DESCRIPTION — human-readable name/description of the calendar.
- CALENDAR_START_DATE and CALENDAR_END_DATE — the effective date range over which the calendar is valid.
- DAYS_ON and DAYS_OFF — the working-day and off-day counts, typically reflecting the standard workday pattern per period and its complement.
- QUARTERLY_CALENDAR_TYPE — flag describing the calendar's quarterly built-in pattern behavior.
- DATABASE_IN_SYNC — indicator of whether the denormalized detail tables are consistent with the parent record.
- REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent-program audit columns recording which request last maintained the row.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive-flexfield key and segments for extensibility.
No surrogate database-generated identifier is documented; the natural business key CALENDAR_CODE serves as the primary key, which is characteristic of a hub-style reference table.
Common Use Cases and Queries
The principal use cases center on resolving a calendar code to its working-day definition and then applying it in scheduling logic. Cycle counting in inventory uses a calendar to determine when counts are due; shop-floor scheduling uses day on/off information to project completion dates; shipping uses assigned calendars to validate ship dates.
Typical queries include retrieving calendar headers for a picker, joining to workday patterns, or validating that a calendar is currently effective:
- List effective calendars:
SELECT calendar_code, description, calendar_start_date, calendar_end_date FROM bom.bom_calendars WHERE SYSDATE BETWEEN calendar_start_date AND calendar_end_date; - Resolve a parameter's default calendar: join MTL_PARAMETERS.CALENDAR_CODE to BOM_CALENDARS.CALENDAR_CODE.
- Identify calendars referenced by cycle-count headers: join MTL_CYCLE_COUNT_HEADERS.CYCLE_COUNT_CALENDAR to CALENDAR_CODE.
- Audit maintenance activity: filter on PROGRAM_UPDATE_DATE or REQUEST_ID to trace concurrent-program changes.
Because detail is spread across the child tables, reporting that requires actual working-day dates must join BOM_CALENDAR_DATES, while shift-level reporting joins BOM_CALENDAR_SHIFTS.
Related Objects
The ETRM metadata documents ten tables that reference BOM_CALENDARS via CALENDAR_CODE. The most significant are:
- BOM_CALENDAR_DATES — individual workday/non-workday dates for the calendar (join on CALENDAR_CODE).
- BOM_CALENDAR_EXCEPTIONS — date-specific exceptions to the standard pattern.
- BOM_CALENDAR_SHIFTS — shift definitions associated with the calendar.
- BOM_WORKDAY_PATTERNS — the repeating weekly working pattern.
- BOM_CAL_WEEK_START_DATES and BOM_CAL_YEAR_START_DATES — week and year boundary definitions.
- BOM_PERIOD_START_DATES — period boundary definitions.
- MTL_PARAMETERS — inventory organization defaults pointing at a calendar via CALENDAR_CODE.
- MTL_CYCLE_COUNT_HEADERS — cycle count schedules referencing CYCLE_COUNT_CALENDAR.
- WSH_CALENDAR_ASSIGNMENTS — shipping/warehouse calendar assignments via CALENDAR_CODE.
Together these children and consumers make BOM_CALENDARS a central hub for time-based scheduling across manufacturing, inventory, and shipping.
-
Workday calendars
-
Workday calendars
-
VIEW: BOM.BOM_CALENDARS# 12.2.2
-
VIEW: BOM.BOM_CALENDARS# 12.2.2
-
TABLE: BOM.BOM_CALENDARS 12.2.2
-
TABLE: BOM.BOM_CALENDARS 12.1.1
-
eTRM - BOM Tables and Views 12.1.1
Table to map wip transactions to their corresponding event types.
-
eTRM - BOM Tables and Views 12.2.2
Table to map wip transactions to their corresponding event types.