Search Results capacity_change




Overview
Explore in AI Chat

Overview

APPS.BOM_RESOURCE_CHANGES_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes resource capacity change records maintained by the Bills of Material (BOM) module. The view presents one row per resource capacity adjustment, capturing the department, resource, shift, effective date and time window, and the magnitude of the capacity change. It is most commonly encountered during capacity planning, simulation set management, and integration of shop-floor capacity data into external systems or custom reports.

A distinguishing characteristic of this view is that its final SELECT column is not a stored column but a derived expression built with DECODE over ACTION_TYPE and CAPACITY_CHANGE. This means the view exposes an action classification value that is computed at query time, allowing consumers to distinguish additions, deletions, and modifications without needing to interpret ACTION_TYPE directly. Because the view is defined as a thin projection over a single base table, it performs efficiently and carries no aggregation or join overhead.

Underlying Base Objects

The view is defined solely over BOM_RESOURCE_CHANGES, accessed through a synonym owned by APPS. There are no joins to other tables in the documented definition. All columns exposed by the view map one-to-one to base table columns, with the single exception of the trailing ACTION_TYPE-derived expression. This single-table lineage means the view is essentially a filtered presentation layer: it inherits the row-level security, concurrency, and transaction semantics of the base table, and any change written to BOM_RESOURCE_CHANGES is immediately visible through the view.

Key Columns

  • DEPARTMENT_ID / RESOURCE_ID — Identify the department and the specific resource whose capacity is being altered.
  • SHIFT_NUM — The shift to which the change applies within the resource's calendar.
  • FROM_DATE / TO_DATE — The effective date range during which the capacity change is in force.
  • FROM_TIME / TO_TIME — The time window within a day for the change, supporting intra-day capacity modeling.
  • CAPACITY_CHANGE — The numeric magnitude of the change. Its sign and relationship to its absolute value drive the derived ACTION_TYPE expression.
  • SIMULATION_SET — Marks records belonging to a simulation scenario rather than live production capacity.
  • Derived ACTION_TYPE — Computed as 3 (fixed), 1, or, for ACTION_TYPE = 2, a DECODE over whether CAPACITY_CHANGE equals ABS(CAPACITY_CHANGE), yielding 0 or 2. This classifies the nature of the change.
  • REASON_CODE / DOWNTIME_GROUP_ID — Provide the business justification and optional downtime grouping for the change.
  • ATTRIBUTE1–15 — Descriptive flexfield segments for extensibility.
  • REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATE_DATE — Concurrency and audit fields identifying the concurrent program that created or updated the record.

Common Use Cases and Queries

The view is typically queried to audit capacity overrides for a resource, to report simulated versus actual capacity changes, and to feed external scheduling tools. A representative query lists current changes for a resource:

SELECT resource_id, department_id, shift_num, from_date, to_date,
       capacity_change
  FROM apps.bom_resource_changes_v
 WHERE resource_id = :resource_id
   AND simulation_set IS NULL
 ORDER BY from_date, from_time;

To isolate positive versus negative capacity adjustments, filter on the sign of CAPACITY_CHANGE. To compare a simulation against baseline capacity, constrain SIMULATION_SET to the scenario identifier of interest and join the results back to a resource capacity query. Because the view is thin and unindexed at the view level, tuning should target the underlying BOM_RESOURCE_CHANGES indexes, particularly on RESOURCE_ID, DEPARTMENT_ID, and SIMULATION_SET.