Search Results planning party




The MSC.MSC_SUP_DEM_ENTRIES table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical data structure within the Oracle Advanced Supply Chain Planning (ASCP) module. It serves as a repository for supply and demand entries, which are fundamental to the planning engine's ability to generate optimized supply chain plans. This table stores transactional data that represents both supply (e.g., purchase orders, work orders, on-hand inventory) and demand (e.g., sales orders, forecasts, dependent demands) records, which are processed during the planning cycle to determine net requirements and recommend replenishment strategies.

Key Attributes of MSC.MSC_SUP_DEM_ENTRIES

The table contains several important columns that define the nature of supply and demand records:
  • PLAN_ID: Identifies the specific planning run associated with the entry.
  • TRANSACTION_ID: A unique identifier for each supply or demand record.
  • INVENTORY_ITEM_ID: Links to the item master (MTL_SYSTEM_ITEMS_B) to identify the product.
  • ORGANIZATION_ID: Specifies the inventory organization where the supply or demand is recorded.
  • SUPPLY_DEMAND_TYPE: Distinguishes between supply (e.g., 1 for purchase orders) and demand (e.g., 2 for sales orders) types.
  • QUANTITY: The amount of supply or demand for the item.
  • NEW_DATE: The date when the supply or demand is expected or required.
  • SR_INSTANCE_ID: Indicates the source instance for distributed planning scenarios.

Functional Role in ASCP

The MSC.MSC_SUP_DEM_ENTRIES table acts as an intermediary between transactional systems (like Oracle Inventory, Order Management, and Purchasing) and the planning engine. During a planning run:
  1. Data Collection: The planning manager populates this table with supply and demand data extracted from source systems via the MSC_SUPPLIES and MSC_DEMANDS interfaces.
  2. Processing: The ASCP engine reads these entries to perform netting (matching supply against demand), apply constraints (like lead times or capacity), and generate planned orders.
  3. Output Generation: Results are written to output tables (e.g., MSC_PLANNED_ORDERS), while the original entries may be archived or purged post-run.

Integration and Customization

This table is integral to Oracle's Supply Chain Planning architecture and interacts with:
  • Demand Planning (DP): Forecast data flows into MSC_SUP_DEM_ENTRIES as demand records.
  • Manufacturing Execution (WIP): Work order supplies are captured here for capacity planning.
  • Global Order Promising (GOP): Uses this data for ATP checks.
Customizations often involve extending the table with user-defined attributes (via descriptive flexfields) or creating triggers to enforce business rules during data insertion.

Performance Considerations

Given its transactional volume, the table requires careful indexing (typically on PLAN_ID, ORGANIZATION_ID, and INVENTORY_ITEM_ID) and partitioning strategies in large implementations. Oracle recommends periodic purging of historical data using MSC_SUP_DEM_ENTRIES_PKG procedures to maintain performance. In summary, MSC.MSC_SUP_DEM_ENTRIES is a cornerstone of Oracle ASCP, enabling the synchronization of supply chain data across disparate systems to drive actionable planning recommendations. Its design reflects Oracle's commitment to scalable, integrated supply chain optimization within EBS.