Search Results msc_atp_summary_sd




Overview
Explore in AI Chat

Overview

MSC_ATP_SUMMARY_SD is a table in the MSC schema (Advanced Supply Chain Planning) in Oracle EBS 12.1.1 and 12.2.2. It stores summarized available-to-promise (ATP) supply and demand data used by the planning engine to support order promising and scheduling decisions. Specifically, the "_SD" suffix indicates this is the "supply/demand" summary, aggregated by date and demand class. The Advanced Supply Chain Planning module uses it to hold the intermediate results of ATP calculations so that planners can promise delivery dates and quantities against available supply.

Based on the FK structure mined from the documented schema, this object is heuristically classified as standalone in Data Vault modeling terms. The table has no documented foreign key relationships to other objects; rather, it appears to be a denormalized summary table whose rows are keyed entirely by business identifiers (plan, source instance, organization, item, date, and demand class). In a Data Vault design this would typically be modeled as a satellite attached to a hub/link representing the item-organization-plan combination, but the metadata indicates no explicit FK constraints were mined.

Key Information Stored

The table contains 17 documented columns. Its primary key, MSC_ATP_SUMMARY_SD_PK, is a composite business key rather than a surrogate — consisting of PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, SD_DATE, and DEMAND_CLASS. A unique index, MSC_ATP_SUMMARY_SD_U1, mirrors this same column set, confirming it as the business-key candidate. There is no single surrogate/sequence-generated primary key column documented.

  • PLAN_ID — Identifier of the Advanced Supply Chain plan that produced this summary row.
  • SR_INSTANCE_ID — The source instance (source system) from which planning data was collected.
  • ORGANIZATION_ID — Inventory organization to which the ATP summary applies.
  • INVENTORY_ITEM_ID — The item being planned/promised.
  • SD_DATE — The date bucket for the supply/demand summary; a core time dimension.
  • DEMAND_CLASS — Demand class used to segregate ATP by priority/customer commitment category.
  • SD_QTY — The summarized supply/demand quantity for the keyed combination (the primary measure).
  • CUSTOMER_CLASS / CUSTOMER_ID — Optional customer classification and specific customer tied to the demand.
  • SHIP_TO_SITE_ID — Ship-to site for the demand record.
  • PLANNING_GROUP / PROJECT_ID / TASK_ID — Planning group, project, and task dimensions for project-driven demand.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include reviewing ATP quantities by item, organization, and date for a given plan; analyzing demand-class allocation; and reconciling planning-engine output with order promising. A representative query:

  • SELECT plan_id, organization_id, inventory_item_id, sd_date, demand_class, SUM(sd_qty) FROM msc.msc_atp_summary_sd WHERE plan_id = :plan AND organization_id = :org GROUP BY plan_id, organization_id, inventory_item_id, sd_date, demand_class ORDER BY inventory_item_id, sd_date;

Additional patterns: filtering by SR_INSTANCE_ID when multiple source instances feed the same plan; joining to item/organization master views for descriptions; and using CUSTOMER_ID / SHIP_TO_SITE_ID to attribute ATP consumption to specific customers. Because the table holds summarized (not transactional) data, it is well suited to reporting and dashboards rather than order-level detail.

Related Objects

The MSC_ATP_SUMMARY_SD table therefore functions as a key planning-side summary of ATP supply and demand, organized by plan, organization, item, date, and demand class, supporting reporting and ATP analysis in Advanced Supply Chain Planning.