Results for “bom_workday_patterns”

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

Overview

BOM.BOM_WORKDAY_PATTERNS is a manufacturing foundation table in Oracle E-Business Suite that defines the on/off workday patterns associated with manufacturing calendars and their shifts. It is the detail-level child of the calendar definition model, where a calendar establishes the overall production calendar and its constituent shifts, and the workday pattern rows specify which sequences of days within those shifts are considered working days (DAYS_ON) versus non-working days (DAYS_OFF). This drives capacity loading, scheduling, and resource availability calculations throughout the Bills of Material and Work in Process modules.

The table is owned by the BOM schema and is present in both Oracle EBS 12.1.1 and 12.2.2. Its primary key, BOM_WORKDAY_PATTERNS_PK, is composed of CALENDAR_CODE, SHIFT_NUM, and SEQ_NUM. Foreign keys reference BOM_CALENDARS and BOM_CALENDAR_SHIFTS. The Data Vault classification heuristic, mined from the foreign key structure, suggests this object behaves as a link — it connects a calendar and a calendar shift to an ordered pattern of on/off days. This is offered as a modeling suggestion rather than a mandated design.

Key Information Stored

The table contains 31 documented columns. The most significant are described below.

• CALENDAR_CODE — Business identifier of the parent manufacturing calendar. Part of the composite primary key and a foreign key to both BOM_CALENDARS and BOM_CALENDAR_SHIFTS.
• SHIFT_NUM — Ordinal identifying a shift within the calendar. Part of the primary key.
• SEQ_NUM — Sequence number defining the ordering of the workday pattern. Part of the primary key and the discriminator for the pattern row.
• DAYS_ON — Number of consecutive days the calendar/shift is defined as working.
• DAYS_OFF — Number of consecutive days the calendar/shift is defined as non-working.
• DESCRIPTION — Free-text description of the pattern.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard EBS flexfield descriptive attribute columns available for customer-defined extensions.
• Who-audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.
• Concurrent request audit columns: REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

The surrogate primary key is the composite BOM_WORKDAY_PATTERNS_PK. No standalone surrogate ID column is documented; the business-key candidates are the same columns that form the primary key. There is no separately documented unique index beyond the primary key.

Common Use Cases and Queries

Typical uses include verifying that a manufacturing calendar and shift have a valid on/off pattern, reporting shift availability for capacity planning, and auditing calendar configuration before capacity changes. A representative query retrieves the active pattern rows for a given calendar:

• SELECT CALENDAR_CODE, SHIFT_NUM, SEQ_NUM, DAYS_ON, DAYS_OFF, DESCRIPTION FROM BOM.BOM_WORKDAY_PATTERNS WHERE CALENDAR_CODE = :w_calendar_code ORDER BY SHIFT_NUM, SEQ_NUM;
• Joining to BOM_CALENDARS and BOM_CALENDAR_SHIFTS to confirm the pattern rows align with the defined shift records.
• Aggregating total working versus non-working days per shift to support capacity-load validation.

Because the table is maintained through the manufacturing calendar setup forms, direct DML is not recommended; reporting and integration queries should be read-only.

Related Objects

The principal related objects, per the documented foreign key relationships and module context, are listed below.

• BOM_CALENDARS — Parent calendar definition; joined on CALENDAR_CODE.
• BOM_CALENDAR_SHIFTS — Shift definition; joined on CALENDAR_CODE and SHIFT_NUM.
• BOM_CALENDAR_DATES — Calendar exception dates used alongside the pattern to derive actual working days.
• BOM_RESOURCES — Resources whose availability is derived from the associated calendar.
• Open interfaces and APIs that load manufacturing calendar data, typically including BOM calendar and resource management concurrent programs.

Together these objects form the calendar-to-shift-to-pattern hierarchy that underpins capacity and scheduling in Oracle Manufacturing.