Results for “msc_job_requirement_ops_u1”

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

Overview

MSC.MSC_JOB_REQUIREMENT_OPS is a planning table in the Oracle EBS Advanced Supply Chain Planning (ASCP) schema, MSC. It stores operation-level component requirement rows that are generated or consumed by the MSC (Material Planning / Supply Chain Planning) engine. Each row represents a planned component requirement tied to a specific job, operation sequence, and component item within a planning run, identified across the tuple of PLAN_ID, SR_INSTANCE_ID, TRANSACTION_ID, OPERATION_SEQ_NUM, COMPONENT_ITEM_ID, PRIMARY_COMPONENT_ID, COMPONENT_SEQUENCE_ID, and SOURCE_PHANTOM_ID. The table is a subordinate data structure within the MSC planning data model, tightly coupled to the operation and component dimensions of a planned order.

The ETRM metadata classifies this object heuristically as standalone for Data Vault modeling purposes, and the only documented foreign key points to BOM.MSC_JOB_REQUIREMENT_OPS.DEPARTMENT_ID referencing BOM_DEPARTMENTS. This suggests the table behaves more like a detailed satellite of planning facts than a true hub or link, though the composite business key (the unique index U1) implies a grain-level association between plan, job, operation, and component.

Key Information Stored

The primary business key is defined by the unique index MSC_JOB_REQUIREMENT_OPS_U1 across PLAN_ID, SR_INSTANCE_ID, TRANSACTION_ID, OPERATION_SEQ_NUM, COMPONENT_ITEM_ID, PRIMARY_COMPONENT_ID, COMPONENT_SEQUENCE_ID, and SOURCE_PHANTOM_ID. That tuple identifies the exact requirement line. The non-unique index MSC_JOB_REQUIREMENT_OPS_N1 (PLAN_ID, SR_INSTANCE_ID, COMPONENT_ITEM_ID, ORGANIZATION_ID) supports component-centric lookups within a plan.

Important columns include: PLAN_ID and SR_INSTANCE_ID, identifying the plan and source instance; TRANSACTION_ID, tying the row to the originating job/transaction; OPERATION_SEQ_NUM, the routing operation; COMPONENT_ITEM_ID, PRIMARY_COMPONENT_ID, and SOURCE_PHANTOM_ID, defining component relationships and phantom sourcing; ORGANIZATION_ID, the inventory organization; COMPONENT_SEQUENCE_ID and COMPONENT_PRIORITY, controlling component ordering; and DEPARTMENT_ID, the routing department.

Quantitative attributes include QUANTITY_PER_ASSEMBLY, COMPONENT_YIELD_FACTOR, PLANNING_FACTOR, LOW_QUANTITY, HIGH_QUANTITY, and COMPONENT_SCALING_TYPE. Date attributes include EFFECTIVITY_DATE, DISABLE_DATE, and RECO_DATE_REQUIRED. Standard audit columns (LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REFRESH_NUMBER) and fifteen ATTRIBUTE columns round out the structure.

Common Use Cases and Queries

The table is typically queried to examine component-level planned requirements for operations within a plan. A representative query pattern follows:

SELECT op.PLAN_ID, op.TRANSACTION_ID, op.OPERATION_SEQ_NUM, op.COMPONENT_ITEM_ID, op.QUANTITY_PER_ASSEMBLY, op.RECO_DATE_REQUIRED FROM MSC.MSC_JOB_REQUIREMENT_OPS op WHERE op.PLAN_ID = :plan_id AND op.ORGANIZATION_ID = :org_id ORDER BY op.OPERATION_SEQ_NUM, op.COMPONENT_PRIORITY;

Common reporting scenarios include operation-level pegging analysis, component requirement explosion by plan, phantom component sourcing review, and exception reporting for missing or low-quantity planned components. The N1 index supports joins to item and organization masters, while the U1 index enforces uniqueness during planning data refresh and purge processes.

Related Objects

• BOM.BOM_DEPARTMENTS — referenced via DEPARTMENT_ID; join to resolve department name and routing details.
• MSC.MSC_JOB_REQUIREMENTS — parent requirement table (job-level) that feeds operation-level rows.
• MSC.MSC_OPERATIONS — defines routing operations used by OPERATION_SEQ_NUM.
• MSC.MSC_COMPONENT_SEQUENCES — provides COMPONENT_SEQUENCE_ID references.
• MSC.MSC_SYSTEM_ITEMS / MSC.MSC_ITEM_CATEGORIES — resolve COMPONENT_ITEM_ID and PRIMARY_COMPONENT_ID.
• MSC.MSC_PLAN_ORGANIZATIONS — links PLAN_ID and ORGANIZATION_ID context.
• BOM.BOM_COMPONENTS — supplies component and yield attributes used to compute requirements.
• MSC.MSC_SR_INSTANCES — resolves SR_INSTANCE_ID to the source instance.