SAP Knowledge Base Article - Preview

2324429 - Manually cleaning the ABAP Load table (Repoload).


  • Instances of a specific architecture were removed (Machine type (Platform ID)) from the system landscape for which an ABAP Load (bytecode) was generated and now redundant load should be cleaned up to free up space.
  • Example: Your landscape consists of a mix of instances running Solaris on SPARC hardware and Solaris on x86_64 hardware, due to a landscape consolidation the x86_64 hardware was retired but the table Repoload will contain ABAP/4 Load for both machine types.
  • The number of objects for which an ABAP load has been generated can be determined using the Data Browser (SE16) by entering the table name "Repoload" and selecting the "Number of Entries" button. In our example system there is 872477 reports in table Repoload.
  • SE16 Blank.jpg


  • Solaris on SPARC Hardware: Platform ID 370, for which bytecode exits for 400,799 reports in the table Repoload.
  • 370M.jpg


  • Solaris on x86_64 Hardware: Platform ID 372, for which bytecode exists for 471,678 reports in the table Repoload.
  • 372M.jpg



REPOLOAD, large table size, DELETE_OLD_LOAD_FORMAT, RS_LOAD_FORMAT_ADM, Platform ID, machine type, , KBA , BC-ABA-LA , Syntax, Compiler, Runtime , BC-UPG-TLS-TLA , Upgrade tools for ABAP , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.