Results for “bom_resource_changes”

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

Overview

BOM_RESOURCE_CHANGES is a BOM (Bills of Material) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model that records modifications to manufacturing resource capacity. Each row captures a deviation from the baseline capacity defined for a resource shift, expressed across a defined date and time window, and qualified by an action type that identifies whether the change represents a completely closed period, a change in available capacity, or a simulation. In this sense the table functions as a change journal layered over the recurring shift definition, allowing capacity planners and scheduling engines to override nominal resource availability without altering the underlying shift records.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. The table is keyed by a composite that identifies a resource shift context (department, resource, shift number) together with an effective date and time range and an action type. This structure is characteristic of a satellite attached to the resource shift hub, carrying descriptive, time-varying capacity attributes rather than introducing a new business entity or representing a many-to-many association.

Key Information Stored

The primary key BOM_RESOURCE_CHANGES_PK is composed of DEPARTMENT_ID, RESOURCE_ID, SHIFT_NUM, FROM_DATE, TO_DATE, FROM_TIME, TO_TIME, ACTION_TYPE, and SIMULATION_SET. Because these same columns also appear in the unique index BOM_RESOURCE_CHANGES_U1, they effectively serve as the business key rather than as an artificial surrogate; the table has no single-column generated identifier.

• DEPARTMENT_ID, RESOURCE_ID, SHIFT_NUM — identify the department, the resource, and the specific shift whose capacity is being modified. Together they form the foreign key to BOM_RESOURCE_SHIFTS and establish the context of every change.
• FROM_DATE, TO_DATE — the effective date range over which the capacity modification applies.
• FROM_TIME, TO_TIME — the daily time window within that range during which the modified capacity is in effect.
• ACTION_TYPE — classifies the nature of the modification, such as a capacity adjustment, a downtime/closure entry, or a simulation marker.
• CAPACITY_CHANGE — the quantitative capacity value associated with the change.
• SIMULATION_SET — identifies a simulation scenario, allowing hypothetical capacity studies to coexist with production data.
• REASON_CODE and DOWNTIME_GROUP_ID — provide the business justification and optional downtime grouping for the change.
• DOWNTIME_GROUP_ID — links related downtime events that should be reported or applied as a unit.

The table also carries the standard EBS WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), the concurrent request audit columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), and the fifteen generic ATTRIBUTE and ATTRIBUTE_CATEGORY columns used for descriptor flexfield extension.

Common Use Cases and Queries

Typical usage centers on capacity reporting and scheduling. Planners query capacity changes to determine real available hours for a resource over a planning horizon, or to reconcile planned versus baseline capacity. The ACTION_TYPE column frequently filters reporting, for example separating actual downtime from simulation entries. Because SIMULATION_SET distinguishes scenarios, reports must normally constrain it to the production value to avoid double-counting hypothetical data.

A representative query joining back to the shift definition is:

SELECT c.DEPARTMENT_ID, c.RESOURCE_ID, c.SHIFT_NUM,
       c.FROM_DATE, c.TO_DATE, c.ACTION_TYPE, c.CAPACITY_CHANGE
FROM   BOM.BOM_RESOURCE_CHANGES c
WHERE  c.DEPARTMENT_ID = :dept
AND    c.RESOURCE_ID   = :resource
AND    c.TO_DATE      >= :horizon_start
ORDER BY c.FROM_DATE, c.FROM_TIME;

Audit-style queries use PROGRAM_ID and REQUEST_ID to trace which concurrent program created or last modified a capacity change, supporting compliance and troubleshooting. Downtime analysis groups rows by DOWNTIME_GROUP_ID to aggregate the total capacity lost across multiple shifts or resources.

Related Objects

• BOM_RESOURCE_SHIFTS — the parent table; the foreign key maps DEPARTMENT_ID, RESOURCE_ID, and SHIFT_NUM from BOM_RESOURCE_CHANGES into this table, which holds the nominal shift definition.
• BOM_RESOURCES — reached via RESOURCE_ID to obtain resource descriptions and standard rate information.
• BOM_DEPARTMENTS — reached via DEPARTMENT_ID to resolve the owning department.
• BOM_RESOURCE_CHANGES_U1 — the unique index that enforces business-key uniqueness on the change set.
• MTL_SIMULATION_SETS — the conceptual source of SIMULATION_SET values used to separate scenario data.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to attribute each change to the concurrent process that produced it.

Because the table is a satellite over resource shifts, most functional queries retrieve rows by the shift key and filter on the effective date/time window, making the composite business key the dominant access path in both application logic and custom reporting.