BACK

SAP housekeeping best practice

Let’s talk about the activities that are necessary to be performed in order to clean up a SAP system from temporary data. This means regularly created data in a SAP system that looses its value quickly. We experienced that this data can pollute as much as 25% of your system size. It varies from application logs, RFC logs to not used change documents, PSA and ChangeLog’s in BW etc.

 Stated this, you should obviously focus on keeping your SAP system fit and running housekeeping activities regularly. Not only in your production system but also throughout your SAP landscape.

 

If the SAP housekeeping topic is new to you here are several options to start.

 

  • First option is to identify top 20 largest tables in your SAP system and search for SAP notes that are published in the area of housekeeping.
  • Second option is to check all published SAP housekeeping notes and apply them one by one.

 

Both options are not straightforward and are rather complicated to be performed. SAP recommended reports are spread over several housekeeping notes, SM37 jobs and jobs belonging to the application owners (e.g. Change log and PSA clean up). Finding out the documentation for them and taking responsibility to run these correctly is making this approach impossible for many customers. In addition, if the system is extremely polluted with a temporary data, running standard SAP jobs might take forever or could result in a memory short dump.

 

Our expertise brings the combination of experience and ABAP-based tools that turns this challenge into a smooth project. Our approach is to execute the project in following waves.

If you want to say goodbye to unnecessary data the easy way, then our Housekeeping tool automates most of the work for you, schedule and monitor all actions centrally from one place across your SAP system landscape.

 

Leave a Reply

Your email address will not be published. Required fields are marked *