Search Results msc_sales_orders




Overview
Explore in AI Chat

Overview

The MSC_SALES_ORDERS table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It functions as the central staging and processing table for all sales order demand and reservation data imported from source transactional systems, such as Oracle Order Management. Its primary role is to serve as the input for the planning engine's demand schedule, enabling ASCP to generate supply plans that account for actual customer orders, reservations against specific supply, and related demand types. The data within this table is typically populated via the planning data collection process from source application instances, which are identified by the SR_INSTANCE_ID.

Key Information Stored

The table stores comprehensive attributes for each sales order demand line. The primary key is a composite of DEMAND_ID and SR_INSTANCE_ID, ensuring uniqueness across multiple source system instances. Based on standard ASCP table structures and the provided metadata, key columns include:

  • DEMAND_ID: The unique identifier for the demand line within the planning server.
  • SR_INSTANCE_ID: Identifies the source application instance from which the data was collected.
  • PARENT_DEMAND_ID: References a parent demand record, often used for modeling hierarchical demand structures like orders and their schedule lines.
  • Other typical columns (inferred from common schema) would include ITEM_ID, ORGANIZATION_ID, ORDER_NUMBER, REQUEST_DATE, QUANTITY, USING_ASSEMBLY_DEMAND_DATE, and STATUS codes to indicate whether the demand is firm, planned, or being consumed by a forecast.

Common Use Cases and Queries

This table is pivotal for demand analysis, plan validation, and troubleshooting data collection issues. Planners and analysts often query it to verify that sales orders have been successfully transferred into the planning system and to examine demand details before or after a planning run. A common reporting use case involves joining with item and organization master tables to create a demand visibility report. A typical SQL pattern would extract open sales order demands for a specific item and instance:

SELECT mso.order_number,
mso.ordered_item,
mso.request_date,
mso.order_quantity
FROM msc_sales_orders mso
WHERE mso.sr_instance_id = 1
AND mso.inventory_item_id = :p_item_id
AND mso.organization_id = :p_org_id
AND mso.request_date BETWEEN SYSDATE AND SYSDATE+30;

Another critical use case is investigating demand pegging relationships, where the PARENT_DEMAND_ID foreign key relationship is traversed to understand demand hierarchies.

Related Objects

MSC_SALES_ORDERS has intrinsic relationships with several key planning tables. As indicated by the metadata, it contains a self-referencing foreign key on (PARENT_DEMAND_ID, SR_INSTANCE_ID) to itself. Crucially, it is a primary source for the MSC_DEMANDS table, which consolidates various demand streams for the planning engine. It is also closely related to master data tables such as MSC_ITEMS and MSC_ORGANIZATIONS. The table is populated and maintained via the MSC planning data collection concurrent programs and associated base tables (e.g., MSC_ST_SALES_ORDERS). For transactional integrity and performance, operations on this table are typically managed through published ASCP APIs rather than direct DML.