3730786 - CO_TRANS archive deletion: commit counter behavior and number of commits during delete run

During deletion of archive data for archiving object CO_TRANS with program RSARCHD, customers want to understand how the commit counter influences runtime and how many database commits are executed during the delete process.

Typical questions include:

• Why does one delete run appear faster or slower than another when different commit counter values are used?
• Does a higher commit counter always improve performance?
• Does the commit counter refer to the number of archive objects in the archive file?
• If multiple archive files are processed and the commit counter limit is not reached, is the commit executed once across all files or separately for each file?
• Can CO_TRANS archiving and deletion be processed monthly instead of by fiscal year?

• Controlling (CO)
• SAP S/4HANA Finance
• SAP S/4HANA
  
  
  

CO_TRANS, RSARCHD, archive deletion, commit counter, number of commits, archive object, file-by-file commit, OBJNR, AOBJ, SAT trace, runtime comparison, fiscal year archiving, ACDOCA , KBA , CO-OM , Overhead Cost Controlling , Problem