Search Results msc_st_job_operations




Overview
Explore in AI Chat

Overview

MSC_ST_JOB_OPERATIONS is a staging table within the MSC schema, belonging to the Advanced Supply Chain Planning (ASCP) module in Oracle EBS 12.1.1 and 12.2.2. It serves as the landing zone for work-in-process (WIP) job operation records that are collected from one or more source instances before being transformed, validated, and loaded into the ASCP planning engine's operational datastore. The "ST" prefix denotes a staging table, and rows here typically carry collection metadata such as batch identifiers, source instance codes, and processing flags that drive the ASCP data collection and refresh process.

Because the table is populated by the collections program and consumed downstream by the planning engine, it represents transient integration data rather than durable transactional master data. From a Data Vault modeling perspective, the metadata's heuristic classification is standalone—no hubs, links, or satellites are inferred from the documented foreign key structure. This suggests the table functions as a self-contained staging entity whose grain is defined by the WIP entity plus operation sequence, rather than by conformed business keys shared across a star schema.

Key Information Stored

The table contains 51 documented columns. The most significant are:

No formal surrogate primary key is documented in the supplied metadata; WIP_ENTITY_ID combined with OPERATION_SEQ_NUM and SR_INSTANCE_ID is the practical business-key candidate.

Common Use Cases and Queries

Typical uses include troubleshooting ASCP collection errors, validating that WIP operations were staged before a planning run, and reconciling recommended dates against source WIP schedules.

A common diagnostic query identifies rows that failed to process:

  • SELECT WIP_ENTITY_ID, OPERATION_SEQ_NUM, PROCESS_FLAG, ERROR_TEXT FROM MSC_ST_JOB_OPERATIONS WHERE PROCESS_FLAG = 'E';

To review staged operations for a specific organization and batch:

  • SELECT r.ROUTING_NAME, o.OPERATION_SEQ_NUM, o.DEPARTMENT_CODE, o.RECO_START_DATE, o.RECO_COMPLETION_DATE FROM MSC_ST_JOB_OPERATIONS o WHERE o.ORGANIZATION_ID = :org_id AND o.BATCH_ID = :batch_id ORDER BY o.WIP_ENTITY_ID, o.OPERATION_SEQ_NUM;

Reporting use cases include measuring operation lead-time percentages, analyzing cumulative yield by department, and comparing recommended versus actual start/end dates for plan adherence.

Related Objects

The documented foreign key relationship is:

  • BOM_DEPARTMENTS — joined on MSC_ST_JOB_OPERATIONS.DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_ID, supplying department attributes.

Functionally related objects within the ASCP staging and planning landscape typically include the WIP job headers staged in companion MSC_ST_JOB tables, the MSC collection interface tables that migrate staged rows into the planning datastore, and the standard WIP entities (WIP_ENTITIES, WIP_OPERATIONS, BOM_OPERATIONAL_ROUTINGS) that originate the source data. The ASCP collections concurrent programs drive the insert and update activity against this table, while exception reporting views surface the PROCESS_FLAG and ERROR_TEXT values for remediation.