Search Results msc_wip_job_schedule_interface




Overview
Explore in AI Chat

Overview

MSC_WIP_JOB_SCHEDULE_INTERFACE is an interface table owned by the MSC schema within the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold requests to create or modify WIP jobs and repetitive schedules. In the ASCP architecture, the planning engine generates and manages work orders and schedules in the planning server schema, and this table serves as the staging and transmission mechanism through which those planned jobs and schedules are pushed back to the execution system (Oracle Work in Process) or pulled into planning from external or legacy sources. Records are annotated with a LOAD_TYPE and PROCESS_STATUS so that concurrent programs can determine the operation requested (create or update), the direction of the load, and the outcome of each processing attempt.

From a modeling perspective, the mined Data Vault classification for this table is standalone. Following that heuristic, it would be treated as a standalone structure rather than decomposed into a hub, link, or satellite, reflecting the fact that it functions as a transient interface buffer rather than a normalized master entity.

Key Information Stored

The table contains 47 documented columns that span transactional identity, planning context, and processing control. The most significant include:

Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) provide audit tracking. No explicit surrogate primary key is documented in the metadata; in practice GROUP_ID combined with SOURCE_LINE_ID and ORGANIZATION_ID typically form the business-key candidates used to identify a unique interface record.

Common Use Cases and Queries

Typical usage centers on monitoring and troubleshooting the flow of planned jobs and schedules between ASCP and WIP. Common scenarios include reviewing failed or stuck interface records, reconciling planned quantities against created jobs, and auditing firm-planned orders before release.

  • Identify records awaiting processing: SELECT * FROM msc_wip_job_schedule_interface WHERE process_status != 'COMPLETED';
  • Group records by load batch and source: SELECT group_id, source_code, load_type, COUNT(*) FROM msc_wip_job_schedule_interface GROUP BY group_id, source_code, load_type;
  • Trace a specific organization's workload: filter by organization_id and join to items and organizations to produce a release-ready listing.
  • Compare planned versus firm jobs using firm_planned_flag and firm_flag.
  • Reconciliation reporting on last_update_date ranges to detect records that have not progressed.

Related Objects

  • WIP_SCHEDULE_GROUPS – joined via MSC_WIP_JOB_SCHEDULE_INTERFACE.SCHEDULE_GROUP_ID = WIP_SCHEDULE_GROUPS.SCHEDULE_GROUP_ID; the only documented foreign key relationship.
  • WIP_ENTITIES – the WIP job master, referenced through WIP_ENTITY_ID to reconcile interface records with created jobs.
  • MTL_SYSTEM_ITEMS – resolved through PRIMARY_ITEM_ID for item description and attribute lookups.
  • MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS – resolved through ORGANIZATION_ID for organization context.
  • MSC_WIP_JOB_SCHEDULE_INTERFACE processing is driven by ASCP concurrent programs, which consume these rows and post results to the execution side.
  • WIP_DISCRETE_JOBS and WIP_REPETITIVE_SCHEDULES – destination entities for the create/modify requests this table carries.

Together these relationships position MSC_WIP_JOB_SCHEDULE_INTERFACE as the transactional bridge between ASCP planning output and Oracle Work in Process execution.