As part of your SAP S/4HANA system conversion planning, there are multiple activities you can perform to reduce the size of your SAP HANA footprint to help with technical downtime, memory management, and cost of HANA infrastructure. Multiple factors influence the technical downtime of a system conversion. The first one involves the size of the source database. By reducing the footprint of the database, not only will the technical conversion runtime reduce, but you will also save on system resources (HANA memory, CPU, and disk storage) on your target SAP HANA database. In order to reduce the size of your source ECC database, you should focus on the implementation of Data Volume Management by archiving and removing data that is no longer required to run your business into an external content repository server. A full archiving project takes months and even years of planning. You will need to work with your business to determine which data is required to be stored in your database to run your business and for how long.
What can you do today without starting a full-blown archiving project? You can start with the quick wins by either implementing data cleanup from technical tables or adjust to more aggressive retention period if cleanup is already being conducted.
Examples include the following types of tables:
Since the data stored in these types of tables are typically not required for normal business purpose, you can archive and remove them from your system. For a full list of technical tables and activities to run, please refer to the following SAP note 2388483 - How-To: Data Management for Technical Tables
(note: This note gets updated frequently, with new information. Check the note for latest updates.)
This note does not deal with application tables and only covers the technical tables in your system and how to clean or remove the data. For a more comprehensive archiving overview you can check the Data Management Guide available in the Data Volume Management area. SAP Note 2243625 provides SAP Enterprise Support offerings in the context of data volume management.
SAP Note 2388483 is valid for all underlying databases and includes the following information:
To begin the process of technical table cleanup, you can leverage the SAP S/4HANA Sizing results to determine the large tables in the system:
Step 1: Run the SAP S/4HANA sizing report or use transaction DB02 to identify the largest tables in your system.
(In this example, we ran the SAP S/4HANA sizing report and have identified over 5 technical tables that are consuming majority of memory resources on our system.)
Step 2: Review SAP Note 2388483 and locate the row with the object identified.
Here we have identified the following technical tables, SWWCNTP0, EDID4, BALDAT, and D010TAB.
Step 3: Locate the tables in SAP note 2388483 and follow the SAP Note instructions for each table.
Remember, this note only covers technical tables within your system and does not include application tables. For application specific tables, we suggest bringing in Archiving consultant to manage application specific archiving. For more information on Data Archiving, refer to the following URL:
Data Archiving in the ABAP Application System
Thanks,
SAP S/4HANA RIG
What can you do today without starting a full-blown archiving project? You can start with the quick wins by either implementing data cleanup from technical tables or adjust to more aggressive retention period if cleanup is already being conducted.
Examples include the following types of tables:
- Communication
- Logging, tracing
- Administration
- Analysis
- Metadata
- Staging
- Auditing
Since the data stored in these types of tables are typically not required for normal business purpose, you can archive and remove them from your system. For a full list of technical tables and activities to run, please refer to the following SAP note 2388483 - How-To: Data Management for Technical Tables
(note: This note gets updated frequently, with new information. Check the note for latest updates.)
This note does not deal with application tables and only covers the technical tables in your system and how to clean or remove the data. For a more comprehensive archiving overview you can check the Data Management Guide available in the Data Volume Management area. SAP Note 2243625 provides SAP Enterprise Support offerings in the context of data volume management.
SAP Note 2388483 is valid for all underlying databases and includes the following information:
- Tables – Lists of technical tables and related data management options.
- Product / Stack – Product and stack information for related object (ABAP, AIF, BCS, BPC, BW, CA, CRM, DS, EM, HANA, Logistics, MDG, MDM, SLD, SolMan, SRM, TM, TRP, XI, etc…)
- Area – Application Area of data.
- SAP Note / reference – SAP Note with additional information and details on how to manage these objects.
- Details – High level information on how to handle data objects.
To begin the process of technical table cleanup, you can leverage the SAP S/4HANA Sizing results to determine the large tables in the system:
Step 1: Run the SAP S/4HANA sizing report or use transaction DB02 to identify the largest tables in your system.
(In this example, we ran the SAP S/4HANA sizing report and have identified over 5 technical tables that are consuming majority of memory resources on our system.)
Step 2: Review SAP Note 2388483 and locate the row with the object identified.
Here we have identified the following technical tables, SWWCNTP0, EDID4, BALDAT, and D010TAB.
Step 3: Locate the tables in SAP note 2388483 and follow the SAP Note instructions for each table.
| Tables | Product/Stack | Area | SAP Note | Details |
| SWFGPROLEINST, SWP_HEADER, SWPNODE, SWPNODELOG, SWP_NODEWI, SWPSTEPLOG, SWW_CONT, SWW_CONTOB, SWWCNTPADD, SWWCNTP0, SWWEI, SWWWIDEADL, SWWWIRET, SWWWIHEAD, SWWLOGHIST, SWWLOGPARA, SWWUSERWI, SWW_WI2OBJ, SWZAI, SWZAIENTRY, SWZAIRET | ABAP | Work items | 49545 1552169 | reports RSWWHIDE, RSWWWIDE, RSWWWIDE_DEP |
| EDI30C, EDI40, EDID4, EDIDC, EDIDOC, EDIDS | ABAP | IDOC | 40088 1574016 | reports RSEXARCA, RSEXARCB, RSEXARCD, RSEXARCL, RSEXARCR, RSETESTD |
| BALC, BALDAT, BALHDR, BALHDRP, BAL_INDX, BALM, BALMP | ABAP | Application log | 195157 2057897 | transaction SLG2, report SBAL_DELETE report SBAL_DELETE_ORPHAN_MESSAGES |
| DBTABLOG, DBTABPRT | ABAP | table logging | 2335014 2362854 | transaction SCU3, report RSTBPDEL report S_AUT_ARCH_STXL_CLEAN (orphan STXL entries) |
| D010TAB, REPOLOAD, REPOSRC | BW | ABAP repository | 1582301 | report RSDRI_INFOPROV_DELETE (be aware that beyond this special context it is usually not possible to clean these tables, because they contain ABAP source and load information) |
Remember, this note only covers technical tables within your system and does not include application tables. For application specific tables, we suggest bringing in Archiving consultant to manage application specific archiving. For more information on Data Archiving, refer to the following URL:
Data Archiving in the ABAP Application System
Thanks,
SAP S/4HANA RIG
- SAP Managed Tags:
5 Comments
