Search Results mrp_atp_details_temp




Overview
Explore in AI Chat

Overview

The MRP_ATP_DETAILS_TEMP table resides in the MRP schema and belongs to the Master Scheduling/MRP product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as a transient staging area that holds Available-to-Promise (ATP) result details generated by the planning engine, encompassing supply/demand matching, horizontal ATP calculations, and sourcing logic. Because ATP processing evaluates availability across time buckets and supply chain nodes, the table captures a wide, denormalized result set that downstream planning, order promising, and reporting processes consume within a planning or ATP session.

From a data modeling perspective, the heuristic Data Vault classification for this object is standalone, meaning it presents no strong hub, link, or satellite role relative to other tables in the mined FK structure. This reflects its nature as a session-scoped work table rather than a durable master or transactional entity. Rows are typically keyed and segmented by SESSION_ID, which represents the planning or ATP run that produced the results.

Key Information Stored

Of the 145 documented columns, the most operationally significant include:

No surrogate primary key is documented in the metadata; uniqueness is enforced logically through a combination of SESSION_ID and the specific supply/demand or bucketed record being represented. The documented FK references are PEGGING_ID → MRP_FULL_PEGGING and DEPARTMENT_ID → BOM_DEPARTMENTS.

Common Use Cases and Queries

ATP result analysis is the dominant use case: inspecting which orders were promised, on what date, and against which supply. A typical query retrieves bucketed availability for a session and item:

SELECT inventory_item_name, period_start_date, period_end_date,
       period_quantity, cumulative_quantity, allocated_quantity
  FROM mrp.mrp_atp_details_temp
 WHERE session_id = :session_id
   AND inventory_item_id = :item_id
 ORDER BY period_start_date;

Pegging and sourcing analysis joins to MRP_FULL_PEGGING to trace how a demand was satisfied through the supply chain. Allocation diagnostics compare ALLOCATED_QUANTITY against SUPPLY_DEMAND_QUANTITY to identify constrained items or shortfalls. Reporting on ATP rules (ATP_RULE_NAME) and lead-time components (FIXED_LEAD_TIME, VARIABLE_LEAD_TIME, PROCESSING_LEAD_TIME) supports lead-time and promise-date validation.

Related Objects

  • MRP_FULL_PEGGING — Joined on PEGGING_ID = MRP_FULL_PEGGING.PEGGING_ID to resolve pegging and sourcing chains.
  • BOM_DEPARTMENTS — Joined on DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_ID for capable-to-promise resource context.
  • MRP_ATP_RULES / ATP rule tables — Supply ATP_RULE_ID and ATP_RULE_NAME definitions.
  • MTL_SYSTEM_ITEMS_B — Resolves INVENTORY_ITEM_ID to item attributes.
  • MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — Resolves ORGANIZATION_ID to organization details.
  • PO_HEADERS_ALL / PO_LINES_ALL — Supply sources referenced through SUPPLY_DEMAND_SOURCE_TYPE.
  • OE_ORDER_LINES_ALL — Demand sources tied to sales order promising via ORDER_LINE_ID.

Because the object is a temporary staging table, its contents should be treated as session-scoped and not relied upon for durable history; the corresponding persistent ATP and planning tables should be queried for long-term reporting.