Results for “bom_cal_week_start_dates”

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

Overview

BOM_CAL_WEEK_START_DATES is a Bills of Material (BOM) schema table that stores weekly start dates for workday calendars in Oracle E-Business Suite. Its documented description is "Workday calendar weekly start dates," and it operates in close conjunction with the BOM_CALENDARS and BOM_EXCEPTION_SETS tables. In the Oracle EBS manufacturing and scheduling model, workday calendars define which days are working versus non-working, and this table records the designated start date of each week within a given calendar and exception set combination. This supports the generation of production schedules, lead-time calculations, and shop-floor dispatch across discrete, repetitive, or flow manufacturing environments.

From a Data Vault modeling perspective (a heuristic classification mined from the foreign key structure), this object is best treated as a link. Its role is principally associative: it connects calendar and exception-set entities to a weekly start date, carrying descriptive sequencing and audit attributes alongside those relationships.

Key Information Stored

The table contains 15 documented columns. The most significant are summarized below, distinguishing the composite primary key from business-key candidates.

• CALENDAR_CODE — Identifies the workday calendar; part of the composite primary key and a foreign key to BOM_CALENDARS.
• EXCEPTION_SET_ID — Identifies the exception set applied to the calendar; part of the composite primary key and a foreign key to BOM_EXCEPTION_SETS.
• WEEK_START_DATE — The effective weekly start date; part of the composite primary key.
• PRIOR_DATE and NEXT_DATE — Widen the adjacency context, indicating the preceding and succeeding week boundaries.
• SEQ_NUM — Sequence number supporting ordered traversal of weeks.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who changed the row and when.
• CREATION_DATE, CREATED_BY — Row creation audit metadata.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context, identifying the request that last touched the row.

The composite primary key is defined by BOM_CAL_WEEK_START_DATES_PK over (CALENDAR_CODE, EXCEPTION_SET_ID, WEEK_START_DATE). The unique index BOM_CAL_WEEK_START_DATES_U1 shares the same column list, confirming these three columns as the business-key candidate that guarantees uniqueness of each calendar/exception-set/week combination.

Common Use Cases and Queries

Typical scenarios include validating that a workday calendar has contiguous weekly coverage, reporting available working weeks for capacity planning, and reconciling exception-set application against calendar definitions.

• List weekly start dates for a specific calendar: SELECT CALENDAR_CODE, EXCEPTION_SET_ID, WEEK_START_DATE, PRIOR_DATE, NEXT_DATE, SEQ_NUM FROM BOM.BOM_CAL_WEEK_START_DATES WHERE CALENDAR_CODE = :cal AND EXCEPTION_SET_ID = :exc ORDER BY WEEK_START_DATE;
• Detect coverage gaps by comparing PRIOR_DATE/NEXT_DATE to ordered WEEK_START_DATE values across a calendar.
• Join to BOM_CALENDARS to enrich weekly start dates with calendar descriptions, and to BOM_EXCEPTION_SETS to label exception definitions.
• Audit recently modified rows via LAST_UPDATE_DATE and PROGRAM_ID for change tracking.

Related Objects

The following objects are the most significant dependencies identified from the documented FK and PK relationships:

• BOM_CALENDARS — parent of CALENDAR_CODE; primary relationship for calendar definition lookup.
• BOM_EXCEPTION_SETS — parent of EXCEPTION_SET_ID; defines exception behavior applied to weekly start dates.
• BOM_CAL_WEEK_START_DATES_PK / _U1 — indexes enforcing row uniqueness.
• BOM_CALENDAR_SHIFTS and related workday calendar tables — companion definitions sharing CALENDAR_CODE.
• Standard EBS concurrent programs referencing PROGRAM_ID/REQUEST_ID for calendar generation and maintenance.

Together these objects support the calendar infrastructure that schedules within Oracle Bills of Material and Manufacturing.