Search Results msc_demands

Overview

The MSC_DEMANDS table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It functions as the central table for storing all demand records considered during a planning run. This includes both independent demands, such as sales orders and forecasts, and dependent demands, which are the component requirements generated from planned orders. The table's primary role is to provide the planning engine with a comprehensive view of all demand requirements, enabling the calculation of net requirements and the generation of planned supply orders to fulfill them. Its structure and foreign key relationships are fundamental to the pegging and traceability features of the planning system.

Key Information Stored

The table's primary key is a composite of PLAN_ID, SR_INSTANCE_ID (representing the instance in a multi-instance planning setup), and DEMAND_ID. Beyond these identifiers, critical columns define the demand's nature and attributes. Key columns include INVENTORY_ITEM_ID, ORGANIZATION_ID, and USING_ASSEMBLY_ITEM_ID to identify the item and its usage context. The DISPOSITION_ID is a pivotal column; for dependent demands, it is a foreign key to MSC_SUPPLIES, linking the component requirement to its parent supply order. For independent MPS demands, it references MRP_SCHEDULE_DATES.MPS_TRANSACTION_ID. Other significant columns track quantities (QUANTITY, USING_REQUIREMENT_QUANTITY), dates (DEMAND_DATE), and sourcing details such as CUSTOMER_ID, CUSTOMER_SITE_ID, and SHIP_TO_SITE_ID. The PARENT_ID column supports hierarchical demand structures.

Common Use Cases and Queries

This table is essential for post-planning analysis, custom reporting, and data validation. Common use cases include analyzing demand pegging to understand the supply sources fulfilling a specific demand, validating the demand data loaded into a plan, and creating custom dashboards for demand visibility. A fundamental query retrieves all independent demands for a specific plan and item, filtering for a NULL or specific DISPOSITION_ID. For pegging analysis, a typical SQL pattern joins MSC_DEMANDS to MSC_FULL_PEGGING on DEMAND_ID and PLAN_ID to trace demand fulfillment. Another common query examines dependent demands by joining MSC_DEMANDS to MSC_SUPPLIES via the DISPOSITION_ID column to see the component requirements for a specific planned order.

Related Objects

MSC_DEMANDS has extensive relationships with other core planning tables. As indicated by its foreign keys, it is directly linked to:

• MSC_SUPPLIES: The primary relationship for dependent demand pegging via DISPOSITION_ID.
• MSC_SYSTEM_ITEMS: For item master attributes, linked via INVENTORY_ITEM_ID and USING_ASSEMBLY_ITEM_ID.
• MSC_TRADING_PARTNERS & MSC_TRADING_PARTNER_SITES: For customer and ship-to site information.
• MSC_PROJECTS & MSC_PROJECT_TASKS: For Project Manufacturing demands.
• MSC_DESIGNATORS: For schedule designator details.
• MSC_FULL_PEGGING & MSC_FORECAST_UPDATES: For detailed pegging analysis and forecast consumption tracking, respectively.

The table also has a self-referential foreign key to its own PARENT_ID, enabling demand hierarchies.