- You have removed instances of a specific architecture (Machine type (Platform ID)) from your system landscape for which an ABAP Load (bytecode) was generated and you now wish to cleanup this redundant load 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 you retire the x86_64 hardware 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.
- Solaris on SPARC Hardware: Platform ID 370, for which bytecode exits for 400,799 reports in the table Repoload.
- Solaris on x86_64 Hardware: Platform ID 372, for which bytecode exists for 471,678 reports in the table Repoload.
REPOLOAD, large table size, DELETE_OLD_LOAD_FORMAT, RS_LOAD_FORMAT_ADM, Platform ID, machine type, , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-ABA-LA , ABAP Syntax, Compiler, Runtime , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.