Search Results msc_job_operations




Overview
Explore in AI Chat

Overview

MSC_JOB_OPERATIONS is a table in the MSC schema (Oracle Advanced Supply Chain Planning) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the operation-level detail belonging to planned or recommended job (work order) transactions generated by the planning engine. Each row represents a single routing operation within a planned job, carrying scheduling, quantity, yield, and departmental attributes that the planner or planning engine uses to evaluate and release recommendations.

The table is keyed around a planning transaction context. The unique index MSC_JOB_OPERATIONS_U1 on (PLAN_ID, SR_INSTANCE_ID, TRANSACTION_ID, OPERATION_SEQ_NUM) provides the business-key candidate, identifying one operation sequence within one planned job transaction in one plan, sourced from one source instance. The heuristic Data Vault classification mined from FK structure is standalone; from a modeling perspective this suggests the table behaves as a satellite-like store of operation detail rather than as a hub or link, since the only documented foreign key reference is DEPARTMENT_ID to BOM_DEPARTMENTS.

Key Information Stored

Common Use Cases and Queries

Planners and supply-chain analysts query MSC_JOB_OPERATIONS to inspect the routing operations behind planned work orders, to compare recommended versus actual dates, and to evaluate capacity loading per department.

  • List operations for a given planned job: 
    SELECT operation_seq_num, operation_code, department_id,
       reco_start_date, reco_completion_date, yield
  FROM msc.msc_job_operations
 WHERE plan_id = :plan_id
   AND transaction_id = :transaction_id
 ORDER BY operation_seq_num;
  • Capacity review by department and date window using RECO_START_DATE, RECO_COMPLETION_DATE, and MINIMUM_TRANSFER_QUANTITY to size load.
  • Yield variance reporting by joining DEPARTMENT_ID to BOM_DEPARTMENTS for departmental context and filtering on RECOMMENDED = 'Y' to isolate unreleased suggestions.
  • Reconciliation of network versus actual dates using NETWORK_START_END, ACTUAL_START_DATE, and ACTUAL_END_DATE.

Related Objects

  • BOM_DEPARTMENTS — joined via DEPARTMENT_ID (the documented FK) for department name and resources.
  • MSC_JOB_HEADERS / planned job / transaction tables — joined on TRANSACTION_ID, PLAN_ID, SR_INSTANCE_ID to obtain the parent job context.
  • MSC_PLANNED_ORDERS / MSC_SUPPLIES — planning output that references the same plan and transaction identifiers.
  • BOM_OPERATION_SEQUENCES / BOM_STANDARD_OPERATIONS — source routing definitions matching ORGANIZATION_ID and OPERATION_SEQUENCE_ID / STANDARD_OPERATION_CODE.
  • MSC_PLANS — joined via PLAN_ID to link operations to their planning scenario.
  • BOM_OPERATION_RESOURCES — consumed when operation-level resource load is derived from these operations.