Search Results msc_resource_groups




Overview
Explore in AI Chat

Overview

The MSC_RESOURCE_GROUPS table is a core data object within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It serves as the master repository for defining logical groupings of manufacturing or operational resources. In the context of planning, a resource group aggregates individual resources (e.g., machines, labor, tooling) to enable higher-level capacity planning, load leveling, and constraint management. This abstraction allows planners to model and analyze capacity at a departmental or functional level, rather than solely at the granular resource level, which is critical for creating feasible and optimized production and distribution plans.

Key Information Stored

The table's structure, as indicated by its primary and foreign keys, is designed to support a multi-instance, multi-organization planning architecture. The primary key is a composite of SR_INSTANCE_ID and GROUP_CODE. The SR_INSTANCE_ID identifies the specific planning server instance, enabling data partitioning in complex deployment scenarios. The GROUP_CODE is the unique identifier for the resource group within that instance. While the provided metadata does not list all columns, the foreign key relationships imply the existence of columns like RESOURCE_GROUP_NAME. The table fundamentally stores the association between a group identifier and its descriptive name, forming the foundation for all subsequent resource-to-group assignments and planning rules that utilize these groupings.

Common Use Cases and Queries

This table is primarily accessed during plan setup, maintenance, and analysis. Common operational scenarios include validating resource group definitions before launching a plan, troubleshooting capacity constraints reported at the group level, and generating master lists of all configured groups. A typical query would join this table with related entities to analyze group composition or assignments. For example, to list all resource groups and their associated department resources, one might use a SQL pattern such as:

  • SELECT mg.GROUP_CODE, mg.RESOURCE_GROUP_NAME, md.DEPARTMENT_CODE
  • FROM MSC_RESOURCE_GROUPS mg, MSC_DEPARTMENT_RESOURCES md
  • WHERE mg.SR_INSTANCE_ID = md.SR_INSTANCE_ID
  • AND mg.GROUP_CODE = md.RESOURCE_GROUP_NAME;

Reporting often focuses on the utilization of resource groups within a specific plan, requiring joins to plan data tables.

Related Objects

As per the documented foreign keys, MSC_RESOURCE_GROUPS has direct relationships with several other critical planning tables. The MSC_DEPARTMENT_RESOURCES table references it, linking resource groups to specific manufacturing departments. This defines where the grouped resources are located. Furthermore, the MSC_ALLOCATION_ASSIGNMENTS table references it, which is pivotal for setting up planning rules that govern how material is allocated or scheduled against a pool of resources (the group) rather than individual ones. These relationships underscore the table's central role in the ASCP data model, acting as a nexus between departmental organization, physical resources, and planning execution rules.