3743227 - Managing Growth of Several ATP Tables and Ensuring System Performance

• Several tables used by available-to-promise (ATP) are growing to hundreds of millions of records and rank among the largest tables in the system.
  
  
• Affected tables observed include:

Table                              Description                                                       
ATP_CONF_BEFORE         ATP pre‑confirmation runtime snapshot
ATP_SELD_RQMT            Selected requirements during ATP evaluation
ATP_PROCD_RQMT         Processed requirements after ATP logic
ATP_EXCLD_RQMT          Excluded requirements during ATP processing
ATP_CONF_CMPSTN        ATP confirmation composition (header‑level)
ATP_CONF_CMPSTNI      ATP confirmation composition (item‑level)

• To prevent the system from running into possible performance issues based on increasing database sized, the following questions have been raised: 
  • Are these ATP tables considered technical/runtime tables by SAP?
  • Is there official SAP guidance on 'Data retention periods'; 'Supported cleanup or deletion strategies'; 'Housekeeping jobs or reports'? 
  • Is it supported and safe to delete historical records from these tables in non‑production systems?
  • Are there any SAP Notes, KBAs, or best practices that specifically address ATP runtime table growth in S/4HANA?

• SAP S/4 Hana 
• Advanced ATP (aATP)
• SAP Backorder Processing (BOP)

bop log, bop run, deletion, cleanup, bop results, ATP_CHECK_LOG, ATP_RESULT_DEL_DISPLAY, backorder processing, sap s/4hana, advanced available to promise, data growth, table size, aATP, data retention, runtime tables, housekeeping jobs, deletion strategies, historical records, system performance, ATP table growth, BOP monitor, aATP cleanup, technical tables, ATP evaluation, ATP logic, excluded requirements, processed requirements, confirmation composition , KBA , CA-ATP , Available to Promise (ATP) , CA-ATP-BOP , ATP: Backorder Processing , CA-ATP-PAC , ATP: Product Availability Check , How To