Search Results msc_job_op_resources




Overview
Explore in AI Chat

Overview

MSC.MSC_JOB_OP_RESOURCES is a transactional planning table within the Oracle Advanced Supply Chain Planning (ASCP) module. It stores the resource-level detail associated with planned manufacturing job operations, capturing how resources are assigned to operations across a planning run. Each row represents a resource assignment for a discrete job or repetitive schedule operation, holding recommended and assigned resource quantities, scheduling attributes, and planning identifiers such as plan, instance, and organization.

The table is populated by the ASCP planning engine during plan generation and refreshed on each planning cycle. Rows are keyed by transaction, plan, and source instance, allowing the planner to track resource loading at the operation level. The heuristic Data Vault classification for this object is standalone, meaning it does not act as a pure hub, link, or satellite but functions as an independent transactional fact table that carries its own business key and descriptive attributes.

Key Information Stored

The table contains 55 documented columns. The unique business key is defined by MSC_JOB_OP_RESOURCES_U1: PLAN_ID, SR_INSTANCE_ID, TRANSACTION_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, RESOURCE_ID, and ALTERNATE_NUM. Because the table is treated as standalone, no surrogate primary key is documented separately; the composite unique index serves as the business-key candidate.

Among the most significant columns:

  • PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID — identify the plan, source application instance, and inventory organization context.
  • TRANSACTION_ID — links the resource row to the originating job or schedule transaction.
  • OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM — sequence the operation and resource within the job.
  • RESOURCE_ID — the resource being assigned; DEPARTMENT_ID references BOM_DEPARTMENTS.
  • RECOMMENDED, RECO_START_DATE, RECO_COMPLETION_DATE — planning engine recommendations for the resource.
  • ASSIGNED_UNITS, USAGE_RATE_OR_AMOUNT, UOM_CODE, BASIS_TYPE — resource quantity, usage, and unit basis.
  • SETUP_ID — references BOM_SETUP_TYPES, capturing setup-related resource data.
  • ALTERNATE_NUM — distinguishes alternate resource assignments within the same operation.
  • REFRESH_NUMBER — indicates the planning refresh in which the row was generated.

Standard audit columns (CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID) plus ATTRIBUTE1–15 provide extensibility.

Common Use Cases and Queries

Typical reporting scenarios include resource capacity analysis, overloaded resource identification, and comparison of recommended versus assigned units across a plan. A common query pattern retrieves resource loading for a specific plan and organization:

  • Filter by PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID to isolate a planning scope.
  • Aggregate ASSIGNED_UNITS and USAGE_RATE_OR_AMOUNT by RESOURCE_ID or DEPARTMENT_ID to view loading.
  • Compare RECO_START_DATE and RECO_COMPLETION_DATE to identify scheduling bottlenecks.
  • Join to BOM_DEPARTMENTS and BOM_SETUP_TYPES to enrich resource and setup attributes.

Such queries underpin resource utilization dashboards, constraint-based capacity planning reports, and plan comparison analyses. Filtering on REFRESH_NUMBER supports trend comparison across successive planning runs.

Related Objects

The documented foreign keys tie this table to master resource reference data:

  • BOM_DEPARTMENTS — joined via MSC_JOB_OP_RESOURCES.DEPARTMENT_ID.
  • BOM_SETUP_TYPES — joined via MSC_JOB_OP_RESOURCES.SETUP_ID.

In practice, the table is also read alongside other ASCP planning tables such as MSC_JOB_OP_RESOURCES siblings (job operation header/detail), MSC_PLAN tables for plan metadata, and MSC_SYSTEM_ITEMS or MSC_ORG tables for item and organization context. The planning engine itself (MSC_ENGINE) populates this table, and planners query it through ASCP workbenches and resource planning reports. These relationships make MSC_JOB_OP_RESOURCES central to resource-level plan analysis.