Results for “bom_period_start_dates”

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

Overview

The BOM_PERIOD_START_DATES table resides in the BOM (Bills of Material) schema and stores workday calendar period start dates used by Oracle EBS manufacturing and scheduling functions. It maps calendar period boundaries to specific start dates and, implicitly, the sequence of work periods defined for a given manufacturing calendar. Each row associates a period with a calendar and an exception set, allowing the system to resolve working-day versus non-working-day boundaries that drive capacity planning, repetitive scheduling, and lead-time calculations.

Because the table is keyed on CALENDAR_CODE, EXCEPTION_SET_ID, and PERIOD_START_DATE, it functions as an associative structure joining calendar and exception-set context to discrete period dates. In Data Vault terms, the mined FK structure suggests a link classification: the table connects the BOM_CALENDARS hub and the BOM_EXCEPTION_SETS hub through period-date grain, with descriptive period attributes behaving as satellite-style payload.

Key Information Stored

The table contains 16 documented columns. The most significant are:

• CALENDAR_CODE — Identifier of the workday calendar to which the period belongs; part of the primary key and FK to BOM_CALENDARS.
• EXCEPTION_SET_ID — Identifier of the exception set applied to the calendar; part of the primary key and FK to BOM_EXCEPTION_SETS.
• PERIOD_START_DATE — The starting date of the period; part of the primary key and the primary business-key candidate.
• PERIOD_SEQUENCE_NUM — Ordinal position of the period within its calendar.
• PERIOD_NAME — Descriptive label for the period.
• NEXT_DATE and PRIOR_DATE — Adjacent period boundaries, enabling navigation across the calendar without self-joins.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit context.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard WHO audit columns.

The surrogate-style primary key is BOM_PERIOD_START_DATES_PK; the unique index BOM_PERIOD_START_DATES_U1 covers the same three columns, confirming the composite business key of calendar, exception set, and period start date.

Common Use Cases and Queries

Typical applications include generating workday calendars for repetitive manufacturing, resolving period boundaries for capacity and resource planning, and reporting on period coverage by exception set.

• Period range lookup: SELECT PERIOD_NAME, PERIOD_START_DATE FROM BOM_PERIOD_START_DATES WHERE CALENDAR_CODE = :code AND EXCEPTION_SET_ID = :set AND PERIOD_START_DATE BETWEEN :start AND :end ORDER BY PERIOD_SEQUENCE_NUM;
• Gap/sequence validation: compare PERIOD_SEQUENCE_NUM ordering against NEXT_DATE/PRIOR_DATE to detect missing or misaligned periods.
• Audit reconstruction: join on REQUEST_ID and PROGRAM_ID to trace which concurrent program populated or updated periods.
• Reporting: enumerate all exception sets defined for a calendar and count periods per set.

Related Objects

• BOM_CALENDARS — parent table; join on BOM_PERIOD_START_DATES.CALENDAR_CODE = BOM_CALENDARS.CALENDAR_CODE.
• BOM_EXCEPTION_SETS — parent table; join on BOM_PERIOD_START_DATES.EXCEPTION_SET_ID = BOM_EXCEPTION_SETS.EXCEPTION_SET_ID.
• Downstream scheduling and capacity modules consume period boundaries resolved through this table, making it a dependency for repetitive manufacturing and resource planning logic that relies on calendar periods.