Search Results msc_sup_dem_entries

Overview

The MSC_SUP_DEM_ENTRIES table is a core transactional data repository within Oracle E-Business Suite's Advanced Supply Chain Planning (ASCP) module. It serves as the primary storage entity for supply and demand transaction data utilized by Oracle Collaborative Planning. This table is fundamental to the planning engine's ability to process and synchronize detailed operational data, such as purchase orders, sales orders, and planned orders, between trading partners in a supply chain network. Its role is to act as the system of record for granular transaction entries that feed the planning calculations, enabling the creation of synchronized production and distribution plans.

Key Information Stored

The table's structure is designed to uniquely identify and describe each planning transaction. The primary key is a composite of TRANSACTION_ID and PLAN_ID, ensuring uniqueness within the context of a specific planning run. The PLAN_ID column is a foreign key to MSC_PLANS, linking each entry to a specific planning instance or scenario. A critical foreign key relationship exists via the INVENTORY_ITEM_ID column, which references ICX_POR_ITEMS, thereby connecting planning transactions to the master item catalog. While the provided metadata specifies these key columns, typical transactional data stored includes quantities, dates (schedule ship, need-by, promise), transaction types (e.g., demand, supply), source organization, and partner identifiers, forming a complete record for collaborative planning analysis.

Common Use Cases and Queries

Primary use cases involve troubleshooting planning data integrity, auditing transaction flow, and building custom analytical reports. For instance, a common query pattern is to investigate transaction details for a specific item within a plan to validate data submission from a collaborative partner. A sample SQL pattern to achieve this would join to the item master and plan tables:

• SELECT msde.*, mpi.plan_name, ipi.item_number FROM msc_sup_dem_entries msde, msc_plans mpi, icx_por_items ipi WHERE msde.plan_id = mpi.plan_id AND msde.inventory_item_id = ipi.inventory_item_id AND mpi.plan_name = '<Plan_Name>' AND ipi.item_number = '<Item_Number>';

Data from this table is also frequently extracted for custom performance dashboards that track the volume and status of collaborative transactions over time, measured by transaction type or partner.

Related Objects

MSC_SUP_DEM_ENTRIES is centrally connected to several key planning objects. Its most direct relationship, as defined by its foreign keys, is with ICX_POR_ITEMS (for item master data) and MSC_PLANS (for plan context). It is a foundational source table for various planning engine processes and is likely referenced by numerous MSC_% views that present aggregated or formatted planning data to the application's user interface. While not listed in the metadata, it is logically related to other transactional staging and snapshot tables within the MSC schema, such as MSC_ST_SUP_DEM_ENTRIES, and serves as input for critical planning packages that generate supply chain plans.