Results for “msc_st_wo_task_hierarchy”

34 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_ST_WO_TASK_HIERARCHY is a staging table within the MSC schema, owned by the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. It serves as an intermediate landing structure used during the collection and processing of work order task hierarchy data from source systems into the ASCP planning engine. In the context of Oracle EBS 12.1.1 and 12.2.2, staging tables of this type receive raw records from external or upstream instances before validation, transformation, and ultimate loading into the planning operational tables.

The table captures parent-child relationships between work order tasks, including precedence constraints and separation timing between successive operations. This structure is essential for modeling sequenced manufacturing activities where task dependencies and inter-task timing influence scheduling outcomes.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure identifies MSC_ST_WO_TASK_HIERARCHY as a standalone table. This suggests it functions independently within the collection pipeline rather than acting as a conventional hub, link, or satellite. The single documented foreign key to AHL_TASK_LINKS indicates a referential relationship that supports task-link resolution during the staging process.

Key Information Stored

The table contains 33 documented columns in the 12.2.2 physical schema. The most significant columns include:

No explicit surrogate primary key is documented in the provided metadata; the table appears to rely on composite business keys formed from task link, instance, and entity identifiers.

Common Use Cases and Queries

Typical usage centers on monitoring and troubleshooting the collection of work order task hierarchies into ASCP. Common reporting scenarios include identifying records that failed processing, verifying completeness of collected hierarchies, and auditing precedence constraint data before it feeds the planning engine.

A representative query to inspect unprocessed records:

  • SELECT TASK_LINK_ID, CURR_WIP_ENTITY_ID, NEXT_WIP_ENTITY_ID, PRECEDENCE_CONSTRAINT, PROCESS_FLAG, ERROR_TEXT FROM MSC.MSC_ST_WO_TASK_HIERARCHY WHERE PROCESS_FLAG = 'ERROR';

Another common pattern joins staged data back to the source instance to reconcile collected versus expected task links, filtering by SR_INSTANCE_CODE, ORGANIZATION_ID, and REFRESH_ID. Administrators frequently query by BATCH_ID to isolate a specific collection run. These queries support data quality checks and root-cause analysis when ASCP planning results reflect missing or incorrect task dependencies.

Related Objects

The most significant related object is the referenced table identified by the documented foreign key:

  • AHL_TASK_LINKS — joined via MSC_ST_WO_TASK_HIERARCHY.TASK_LINK_ID = AHL_TASK_LINKS.TASK_LINK_ID; provides the master task-link definition that the staging record populates.

Beyond the documented FK, the table logically interfaces with other ASCP staging and operational tables such as MSC_ST_WORK_ORDERS, MSC_ST_SUPPLIES, and the ASCP planning tables (MSC_WO_TASK_HIERARCHY equivalents) that receive the validated output. Collection programs within the MSC module, including the ASCP data collection concurrent programs, write to and read from this staging table, making it a critical node in the end-to-end supply chain planning data flow.