Search Results msc_wip_job_dtls_interface




Overview
Explore in AI Chat

Overview

MSC_WIP_JOB_DTLS_INTERFACE is a staging and interface table in the MSC schema of Oracle E-Business Suite, owned by the Advanced Supply Chain Planning (ASCP) product. It serves as the inbound conduit for requests to add, delete, or modify material and resource requirements for discrete jobs, repetitive schedules, and flow schedules before those requests are validated and applied to the production execution layer. The table is populated by planning engines, external systems, and custom collections that need to feed supply chain planning changes back into Oracle Work in Process (WIP) and Oracle Bills of Material (BOM).

From a heuristic Data Vault modeling perspective, this object is classified as standalone, meaning it does not depend on strong parent-child FK hierarchies within the planning schema. A modeling suggestion would be to treat it as a satellite-like staging area keyed by INTERFACE_ID, since it captures transient change requests rather than durable master data.

Key Information Stored

The table contains 82 documented columns. The most operationally significant include:

Common Use Cases and Queries

Typical usage involves monitoring pending interface rows, diagnosing failed loads, and reporting on planned material substitutions.

  • Identify unprocessed requests: SELECT INTERFACE_ID, GROUP_ID, WIP_ENTITY_ID, PROCESS_STATUS FROM MSC.MSC_WIP_JOB_DTLS_INTERFACE WHERE PROCESS_STATUS IS NULL;
  • Trace all component changes for a job: filter by WIP_ENTITY_ID and ORGANIZATION_ID and compare INVENTORY_ITEM_ID_OLD to INVENTORY_ITEM_ID_NEW.
  • Audit resource substitutions by joining RESOURCE_ID_OLD and RESOURCE_ID_NEW to BOM resources.
  • Reconcile submitted requests back to concurrent programs using REQUEST_ID and PROGRAM_ID.
  • Refresh or purge stale rows via GROUP_ID after the WIP import concurrent program completes.

Related Objects

The table maintains referential relationships with several master objects and is consumed by planning import processes: