Results for “bom_resource_changes_v”

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

Overview

The BOM_RESOURCE_CHANGES_V view is a reporting object owned by the APPS schema within the Oracle E-Business Suite Bills of Material (BOM) product family. It surfaces resource capacity modifications recorded against manufacturing resources and departments, exposing shift-level changes to available capacity over defined date and time ranges. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the primary read interface for capacity-change data used by capacity planning, simulation, and scheduling reports.

A distinguishing characteristic of this view is the presence of the SIMULATION_SET column and a derived ACTION_TYPE expression. The SIMULATION_SET column allows capacity changes to be grouped into named simulation scenarios, permitting planners to model "what-if" capacity adjustments independently of approved production data. The ACTION_TYPE value is computed inline via a DECODE expression that reconciles an explicit action flag against the sign of CAPACITY_CHANGE, yielding a normalized status code (for example, values representing add, update, or delete semantics).

Underlying Base Objects

The view is defined over a single base object, the BOM_RESOURCE_CHANGES table (referenced through a synonym from the APPS schema). The view is a straightforward projection: it selects an explicit column list from the base table and applies the DECODE transformation to produce ACTION_TYPE. Because it is a non-joining, single-table view, it inherits the row granularity of the base table — one row per department/resource/shift capacity change per effective date range — and carries no aggregation. Standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and concurrent-program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) pass through unchanged.

Key Columns

• ROW_ID — The base table ROWID, providing a unique physical identifier for each row.
• DEPARTMENT_ID / RESOURCE_ID / SHIFT_NUM — Identify the department, resource, and shift to which the capacity change applies.
• FROM_DATE / TO_DATE / FROM_TIME / TO_TIME — Define the effective date and time window during which the capacity modification is active.
• CAPACITY_CHANGE — The magnitude (and sign) of the capacity adjustment for the resource shift.
• SIMULATION_SET — The simulation grouping to which the change belongs; NULL or a default set typically denotes production capacity data.
• ACTION_TYPE — A derived code computed by DECODE from the base action flag and the sign of CAPACITY_CHANGE, normalizing the nature of the change.
• REASON_CODE / DOWNTIME_GROUP_ID — Reference the reason for the change and any associated downtime grouping.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — The standard DFF (descriptive flexfield) columns for extensible attributes.

Common Use Cases and Queries

Typical use cases include capacity simulation reporting, shift capacity auditing, and integration extracts feeding scheduling systems. Because the user search term was simulation_set, a frequent query filters capacity changes by simulation group:

• Retrieve all simulated capacity changes for a specific scenario.
• Compare simulated adjustments against approved (non-simulated) capacity changes.
• Extract changes effective within a date window for a given resource or department.

Sample SQL:

SELECT resource_id, department_id, shift_num, from_date, to_date,
    capacity_change, simulation_set, action_type
 FROM apps.bom_resource_changes_v
 WHERE simulation_set = :p_simulation_set
 AND from_date >= :p_from_date;

For approved (production) data, callers typically filter where SIMULATION_SET IS NULL. All access should respect the view's read-only nature and appropriate security/operating-unit context.