Search Results msc_available_to_promise




Overview
Explore in AI Chat

Overview

The MSC_AVAILABLE_TO_PROMISE table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It stores the calculated Available-to-Promise (ATP) information for master scheduled items, which is fundamental to order promising and supply chain visibility. ATP represents the uncommitted portion of inventory and planned supply that is available to fulfill new customer demand requests. This table is populated and maintained by the ASCP engine during a planning run, serving as the system of record for ATP queries that drive order management commitments, capable-to-promise checks, and supply chain analytics.

Key Information Stored

The table's primary key uniquely identifies each ATP record by the combination of PLAN_ID and TRANSACTION_ID. Key columns include identifiers for the planning context and the item in question: PLAN_ID links to the specific plan, SR_INSTANCE_ID identifies the source system instance, and ORGANIZATION_ID and INVENTORY_ITEM_ID (via a foreign key to MSC_SYSTEM_ITEMS) pinpoint the specific item and its location. The table holds quantitative ATP data, typically including fields for available quantities, bucket dates (like ATP_DATE), and the type of supply or demand transaction that defines the ATP horizon. It effectively captures a time-phased record of net available supply.

Common Use Cases and Queries

The primary use case is querying ATP quantities to support order promising. When a sales order is entered, the Order Management module can query this table to determine if and when an item can be delivered. Common reporting involves analyzing ATP over time to identify supply shortages or excess inventory. A typical query pattern involves filtering by item, organization, plan, and a date range.

  • Sample Query Pattern: SELECT inventory_item_id, organization_id, atp_quantity, atp_date FROM msc_available_to_promise WHERE plan_id = :p_plan_id AND inventory_item_id = :p_item_id AND organization_id = :p_org_id AND atp_date BETWEEN :p_date_from AND :p_date_to ORDER BY atp_date;
  • Use Cases: Real-time ATP checks in Order Management; Generating ATP reports for customer service; Feeding ATP data into business intelligence dashboards; Supporting Capable-to-Promise (CTP) and Production ATP (PATP) processes.

Related Objects

The MSC_AVAILABLE_TO_PROMISE table has defined relationships with other critical MSC schema tables, primarily through foreign key constraints that ensure data integrity.

  • MSC_SYSTEM_ITEMS: This is a directly documented foreign key relationship. The columns INVENTORY_ITEM_ID, PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID in MSC_AVAILABLE_TO_PROMISE reference the MSC_SYSTEM_ITEMS table. This join is essential for retrieving item-level attributes (like item name) when querying ATP data.
  • MSC_PLANS: While not explicitly listed in the provided metadata, the PLAN_ID column typically references MSC_PLANS.PLAN_ID, linking the ATP data to the specific planning run that generated it.
  • Dependencies: The table is the underlying source for ATP-related views and is heavily referenced by the planning engine's internal logic and by public APIs used for ATP inquiry within the Oracle EBS suite.