Search Results msc_resource_changes_u1

Overview

MSC.MSC_RESOURCE_CHANGES is a transactional table in the MSC (Advanced Planning) schema of Oracle E-Business Suite. It stores information about capacity modifications for a resource on a shift within a department, functioning as a child table of MSC_RESOURCE_SHIFTS. The table is materialized physically in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is owned by the MSC schema. It is documented in the FND Design Data as MSC.MSC_RESOURCE_CHANGES. Because multiple capacity changes can be defined against a single shift, the table participates in a one-to-many relationship with its parent shift records.

From a Data Vault modeling perspective, the metadata heuristics classify this object as standalone, meaning it does not exhibit the dense multi-parent foreign-key pattern characteristic of a link table. The modeling suggestion is therefore to treat it as an event or transaction-style object anchored to a business key rather than as a classic hub or satellite. Its most qualified role is that of a satellite or detail record capturing time-bound capacity exceptions, keyed by the source instance, simulation set, action type, and the department/resource/shift/time composite.

Key Information Stored

The table contains 37 documented columns. The most operationally significant include:

• DEPARTMENT_ID and RESOURCE_ID — the department and resource unique identifiers that locate the capacity change.
• SR_INSTANCE_ID — the source application instance identifier, used to isolate data collected from different source systems.
• SHIFT_NUM — the shift number the modification applies to.
• FROM_DATE, TO_DATE, FROM_TIME, TO_TIME — the capacity exception window, expressed as date and numeric time bounds.
• CAPACITY_CHANGE — the magnitude of the capacity modification.
• ACTION_TYPE — the type of capacity modification applied.
• SIMULATION_SET and REFRESH_NUMBER — the simulation set identifier and the refresh number populated by the collection program.
• Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and the ATTRIBUTE1–15 descriptive flexfield segments, with ATTRIBUTE_CATEGORY defining the flexfield structure.

No separate single-column surrogate primary key is documented. Instead, the business-key candidate is the unique index MSC_RESOURCE_CHANGES_U1 (NORMAL, UNIQUE, stored in APPS_TS_TX_IDX), which spans the composite of SR_INSTANCE_ID, SIMULATION_SET, ACTION_TYPE, DEPARTMENT_ID, RESOURCE_ID, SHIFT_NUM, FROM_DATE, TO_DATE, FROM_TIME, and TO_TIME.

Common Use Cases and Queries

Typical usage centers on capacity exception reporting, constraint-based planning analysis, and reconciliation of collected capacity changes against source planning data. A common pattern joins capacity changes back to their parent shift records and filters by instance and simulation set:

• Listing all capacity modifications for a department/resource combination within a date range.
• Auditing exceptions by ACTION_TYPE to determine which changes were manually versus programmatically applied.
• Comparing simulation sets against the base plan by excluding or including rows for a specific SIMULATION_SET.
• Reconciling REFRESH_NUMBER values to confirm which collection run populated a given set of changes.

A representative query filters on the leading columns of the unique index to leverage MSC_RESOURCE_CHANGES_U1, for example selecting DEPARTMENT_ID, RESOURCE_ID, SHIFT_NUM, FROM_DATE, TO_DATE, and CAPACITY_CHANGE for a given SR_INSTANCE_ID, SIMULATION_SET, and ACTION_TYPE, ordered by FROM_DATE and FROM_TIME. Reporting overlays typically join to shift and department reference data to render human-readable capacity calendars.

Related Objects

The documented foreign key establishes a reference from MSC.MSC_RESOURCE_CHANGES.DEPARTMENT_ID to BOM_DEPARTMENTS, linking capacity changes to the department definition in the manufacturing schema. The immediate parent object is MSC_RESOURCE_SHIFTS, since this table is described as its child and inherits the shift context. Beyond these, the surrounding planning object family includes resource and shift definitions in the MSC schema as well as the collection program that populates REFRESH_NUMBER. The composite business key columns (SR_INSTANCE_ID, SIMULATION_SET, DEPARTMENT_ID, RESOURCE_ID, SHIFT_NUM) connect this table to instance, simulation, department, resource, and shift reference data, making these the principal join partners for reporting and reconciliation queries.