Search Results msc_atp_summary_so




Overview
Explore in AI Chat

Overview

MSC_ATP_SUMMARY_SO is a table in the MSC schema owned by Oracle Advanced Supply Chain Planning (ASCP), one of the core modules of the Oracle E-Business Suite Advanced Planning product family. The table stores ATP (Available-to-Promise) summary results at the sales-order level, aggregated across a planning run. During a planning cycle, the ASCP engine evaluates supply, demand, and allocation rules to determine available quantities for each item, organization, and demand date. The outcome of that calculation for sales-order demand is persisted in MSC_ATP_SUMMARY_SO, making it the primary staging structure for order-promising visibility, ATP inquiries, and downstream scheduling decisions.

The heuristic Data Vault classification for this object is standalone, meaning it does not exhibit strong foreign-key linkage to a surrounding hub-and-link topology in the mined metadata. From a modeling perspective, it is best treated as a satellite-like fact table anchored on the planning run (PLAN_ID) and the inventory item dimension, with the remaining key columns acting as combination identifiers rather than true parent references. This classification should be regarded as a suggestion, since the physical schema does not enforce the parent relationships through declared constraints.

Key Information Stored

The table documents 17 columns. The composite primary key is (PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, SD_DATE, DEMAND_CLASS). A separate unique index, MSC_ATP_SUMMARY_SO_U1, covers (SR_INSTANCE_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, SD_DATE, DEMAND_CLASS) and therefore represents the strongest business-key candidate, excluding the plan scope.

  • PLAN_ID — identifies the ASCP plan run that produced the ATP result.
  • SR_INSTANCE_ID — source instance identifier, distinguishing the originating EBS instance in multi-source or global planning configurations.
  • ORGANIZATION_ID — the inventory organization within which availability is evaluated.
  • INVENTORY_ITEM_ID — the planned item for which ATP quantities are calculated.
  • SD_DATE — the ship date or schedule date bucket to which the ATP quantity applies.
  • DEMAND_CLASS — classification of the demand driving the ATP calculation (for example, forecast versus sales-order demand).
  • SD_QTY — the ATP or scheduled quantity determined for that date and demand class; this is the principal numeric measure.
  • CUSTOMER_ID and CUSTOMER_CLASS — the customer and its classification used in allocation or prioritization rules.
  • SHIP_TO_SITE_ID — the ship-to destination associated with the demand.
  • PLANNING_GROUP — the planning group applied during the ATP calculation.
  • TASK_ID and PROJECT_ID — project and task references when project-level ATP is enabled.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS audit columns.

Common Use Cases and Queries

Typical usage centers on ATP inquiry reporting, plan validation, and reconciliation of order-promising results. A planner or analyst commonly queries by plan and item to inspect the time-phased ATP profile:

SELECT sd_date, demand_class, SUM(sd_qty)<br>FROM msc.msc_atp_summary_so<br>WHERE plan_id = :plan_id<br>AND organization_id = :org_id<br>AND inventory_item_id = :item_id<br>GROUP BY sd_date, demand_class<br>ORDER BY sd_date;

Other scenarios include detecting negative or zero ATP dates for expedite decisions, comparing ATP across demand classes, and validating that a completed plan populated the summary correctly. Because the table is rebuilt during planning runs, it is normally read within the context of the latest PLAN_ID.

Related Objects

Although the mined metadata classifies this table as standalone, it participates logically with several ASCP structures through shared planning and item keys: