Results for “implement_instance_id”

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

Overview

MSC_PART_DEMANDS is a table in the MSC schema, owned by the Oracle Advanced Supply Chain Planning (ASCP) module. It stores the exploded, planning-level demand records that Oracle's planning engine generates from higher-level sources such as sales orders, forecasts, and dependent demand. In Oracle EBS 12.1.1 and 12.2.2, this object functions as the granular demand store within the MSC planning data model, holding one row per demand requirement per item, organization, and plan.

In terms of Data Vault modeling, the mined FK relationship (DISPOSITION_ID to AHL_PRD_DISPOSITIONS_B) suggests this table is best treated as a standalone structure rather than a tightly integrated hub or link. This heuristic classification should be regarded as a modeling suggestion: the table's own surrogate DEMAND_ID effectively acts as a hub-style identifier, while the non-key descriptive fields (dates, quantities, implementation flags) behave as satellite attributes. The single outbound FK to AHL_PRD_DISPOSITIONS_B reflects a loose association with disposition data rather than a core dependency.

Key Information Stored

The table contains 21 documented columns. The most operationally significant are listed below, distinguishing the surrogate key from business-key candidates:

• DEMAND_ID — The surrogate identifier for each demand row; a strong candidate for primary key or a unique-indexed surrogate.
• ORIG_DEMAND_ID — The originating demand reference, useful as a business-key candidate linking back to the source record.
• PLAN_ID — Identifies the ASCP plan under which the demand was generated; a natural composite-key component.
• ORGANIZATION_ID — The inventory organization in which the demand resides.
• INVENTORY_ITEM_ID — The item being demanded.
• QUANTITY — The demanded quantity for the row.
• DEMAND_TYPE — Classifies the nature of the demand (e.g., independent vs. dependent).
• ORIGINATION_TYPE — Indicates the source system or object that produced the demand.
• DESIGNATOR_TYPE and ITEM_TYPE_VALUE — Categorize the item/designator context of the demand.
• REQUEST_DATE and FINAL_USE_DATE — Demand scheduling dates.
• IMPLEMENT_DATE, IMPLEMENT_EARLIEST_DATE, and IMPLEMENT_FIRM — Implementation scheduling and firmness flags.
• IMPLEMENT_INSTANCE_ID, IMPLEMENT_ORG_ID, and IMPLEMENT_SHIP_DATE — Implementation routing and shipment details.
• USING_ASSEMBLY_ITEM_ID — The parent assembly consuming the component, relevant for dependent demand.
• DISPOSITION_ID — FK to AHL_PRD_DISPOSITIONS_B.

Common Use Cases and Queries

Typical usage centers on demand visibility, plan analysis, and supply-demand pegging. Analysts query this table to review demands by plan, item, or organization, and to reconcile planned demand against supply. A representative query retrieving open demands for a plan is:

• SELECT demand_id, inventory_item_id, organization_id, demand_type, quantity, request_date FROM msc_part_demands WHERE plan_id = :plan_id ORDER BY request_date;
• Aggregating total demand by item: SELECT inventory_item_id, SUM(quantity) FROM msc_part_demands WHERE plan_id = :plan_id GROUP BY inventory_item_id;
• Joining to disposition data: SELECT d.demand_id, d.quantity, p.* FROM msc_part_demands d LEFT JOIN ahl_prd_dispositions_b p ON d.disposition_id = p.disposition_id;

Reporting use cases include demand-versus-supply exception reporting, dependent demand explosion audits, and implementation scheduling for firm planned demands.

Related Objects

The following objects are most significant in relation to MSC_PART_DEMANDS:

• AHL_PRD_DISPOSITIONS_B — Referenced via DISPOSITION_ID (documented FK).
• MSC_PLANS — Joined on PLAN_ID to resolve plan context.
• MSC_SYSTEM_ITEMS / MTL_SYSTEM_ITEMS_B — Joined on INVENTORY_ITEM_ID for item descriptions.
• MSC_ORG_ORGANIZATIONS / ORG_ORGANIZATION_DEFINITIONS — Joined on ORGANIZATION_ID for organization names.
• MSC_SUPPLIES — Counterpart supply table for supply-demand netting.
• MSC_PEGGING — Links demands to their supply sources during pegging analysis.
• MSC_PART_DEMANDS interface/staging tables — Source and staging counterparts feeding the planning engine.