Search Results mrp_atp_schedule_temp

The MRP_ATP_SCHEDULE_TEMP table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical temporary table used within the Material Requirements Planning (MRP) and Available-to-Promise (ATP) modules. It serves as a staging area for processing ATP and scheduling data before it is committed to permanent tables. This table is primarily utilized during ATP inquiry and scheduling operations to store intermediate results, allowing the system to perform complex calculations and validations before finalizing the output. ### **Purpose and Functionality** The MRP_ATP_SCHEDULE_TEMP table acts as a transient repository for ATP and scheduling data during runtime. When users execute ATP inquiries or scheduling processes, Oracle populates this table with temporary records that include demand, supply, and availability information. The table facilitates real-time ATP checks by storing intermediate results, such as: - **Demand-Supply Matching:** Temporary records of demand (sales orders, forecasts) and supply (inventory, purchase orders, work orders). - **Scheduling Data:** Tentative schedules for production or procurement before final commitment. - **ATP Calculations:** Preliminary availability results based on business rules (lead times, sourcing rules, allocation policies). ### **Key Columns and Structure** The table contains columns that capture essential ATP and scheduling attributes, including: - **REQUEST_ID:** Unique identifier for the ATP or scheduling request. - **INVENTORY_ITEM_ID:** Item being checked for availability. - **ORGANIZATION_ID:** Inventory organization where the item resides. - **SCHEDULE_DATE:** The date for which ATP is being calculated. - **QUANTITY:** Available or required quantity. - **SOURCE_TYPE:** Indicates whether the record is from demand (sales order) or supply (purchase order). - **ATP_FLAG:** Marks whether the item is ATP-enabled. - **STATUS:** Temporary processing status (e.g., 'PENDING', 'PROCESSED'). ### **Integration with ATP and MRP Modules** The MRP_ATP_SCHEDULE_TEMP table interacts with several Oracle EBS modules: 1. **Order Management (OM):** When checking ATP for sales orders, OM populates this table with demand data. 2. **Inventory (INV):** Supplies on-hand and in-transit quantities for ATP calculations. 3. **Purchasing (PO) and Manufacturing (WIP):** Captures supply data from purchase orders and work orders. 4. **MRP Engine:** Uses this table for temporary storage during planning runs. ### **Temporary Nature and Cleanup** Since this table is transient, Oracle automatically purges records after processing. However, in cases of system failures or incomplete transactions, orphaned records may persist, requiring periodic cleanup via concurrent programs or SQL scripts. Administrators should monitor its size to ensure optimal performance. ### **Performance Considerations** Due to its role in high-frequency ATP checks, the MRP_ATP_SCHEDULE_TEMP table must be indexed properly. Key performance optimizations include: - **Indexing:** Columns like REQUEST_ID, INVENTORY_ITEM_ID, and ORGANIZATION_ID should be indexed. - **Partitioning:** For large implementations, partitioning by SCHEDULE_DATE or ORGANIZATION_ID can improve query performance. - **Purging:** Regular maintenance to remove stale records prevents table bloating. ### **Conclusion** The MRP_ATP_SCHEDULE_TEMP table is a foundational component in Oracle EBS for ATP and scheduling operations. Its temporary storage mechanism enables efficient demand-supply matching, ensuring accurate availability checks and scheduling decisions. Proper management of this table is essential for maintaining system performance and data integrity in MRP and ATP processes.