Search Results msc_st_resource_requirements




Overview
Explore in AI Chat

Overview

MSC_ST_RESOURCE_REQUIREMENTS is a staging table in the MSC schema, owned by Oracle Advanced Supply Chain Planning (ASCP). It serves as the landing area for resource requirement records extracted from source systems—primarily discrete manufacturing (WIP), bills of material routings, and shop floor execution—before the collection program validates, transforms, and loads them into the permanent planning table MSC_RESOURCE_REQUIREMENTS. The table stores 101 documented columns in ETRM 12.2.2, reflecting the wide grain of resource-level capacity data captured at the operation, resource, and job level.

From a Data Vault modeling perspective, the heuristic classification of MSC_ST_RESOURCE_REQUIREMENTS is standalone, meaning it does not participate in a strong foreign-key parent/child hierarchy within the mined relationship structure. Modeling judgement suggests it behaves more like a satellite-type staging entity: it carries descriptive and transactional attributes keyed to business entities such as resource, department, and organization, but it does not by itself define a durable hub or link. In practice, it is treated as a transient staging object rather than a persistent dimensional structure.

Key Information Stored

The table’s content centers on resource loading and capacity consumption for planned and released work orders. The most operationally significant columns include:

The metadata does not document a surrogate single-column primary key on this staging table. Business-key candidates include the composite of RESOURCE_ID, ORGANIZATION_ID, WIP_ENTITY_ID, and OPERATION_SEQ_NUM, but no unique index is documented in the supplied metadata.

Common Use Cases and Queries

Because this is a staging object, typical queries focus on monitoring collection health, diagnosing load failures, and verifying source-to-target reconciliation. A common pattern checks rows that failed validation:

  • List all rows with PROCESS_FLAG indicating an error and inspect ERROR_TEXT for load diagnostics.
  • Aggregate OPERATION_HOURS_REQUIRED by ORGANIZATION_ID and DEPARTMENT_ID to reconcile against MSC_RESOURCE_REQUIREMENTS after a collection run.
  • Join to BOM_DEPARTMENTS on DEPARTMENT_ID and to PN_COMPANIES_ALL on COMPANY_ID to enrich rejected rows with department and company descriptions.
  • Filter by SR_INSTANCE_ID and REFRESH_ID to isolate one collection cycle and measure rows-per-refresh trends.
  • Compare HOURS_EXPENDED against OPERATION_HOURS_REQUIRED to identify jobs whose actual resource consumption exceeds plan.

Reporting use cases include capacity-loading analysis by department, work-order resource utilization, and staging throughput dashboards consumed by planning administrators.

Related Objects

The following objects are most significant to MSC_ST_RESOURCE_REQUIREMENTS:

  • MSC_RESOURCE_REQUIREMENTS — the permanent target table; the collection program validates and writes staging rows here.
  • BOM_DEPARTMENTS — referenced via DEPARTMENT_ID; supplies department attributes.
  • PN_COMPANIES_ALL — referenced via COMPANY_ID; provides legal entity context.
  • BOM_SETUP_TYPES — referenced via SETUP_ID; identifies setup classification for the resource.
  • MSC_ST_* collection family — sibling staging tables loaded in the same collection run, sharing SR_INSTANCE_ID and REFRESH_ID.
  • WIP_ENTITIES — logical source for WIP_ENTITY_ID and WIP_ENTITY_NAME values.
  • BOM_OPERATION_RESOURCES — logical source for routing resource assignments.

Together these objects form the manufacturing resource-planning data flow from shop floor execution into ASCP planning.