How to improve performance of DP related processes
During support projects we face a lot of pain points where DP process, data extraction, time series objects, process chains take too much time to complete along with Live Cache inconsistencies. In this document I would like to present the necessary steps to improve performance of APO DP processes based on my experience.
Performance bottlenecks in APO Demand Planning (DP) can manifest themselves in a number of ways. End users may experience longer refresh times for planning book data. Such performance bottlenecks result in longer planning cycles and reduce DP's effectiveness. Bad DP performance can have ripple effects.
As consultants we specialize in APO implementations, Bug fixes, Change Requests etc. It is also required to optimize our system for better performance. A similar way as we do in our personal computers.
Performance bottlenecks in APO Demand Planning (DP) can manifest themselves in a number of ways.
The following are a few thoughts identified to help mitigate sizing and performance obstacles:
Check the log file size via the table /SAPAPO/LISLOG and Delete Old Logs via /SAPAPO/MC8K
In our project, we reduced the database size by 4 TB, by deleting the following logs on a regular basis (by putting them in a process chain)
By using the below programs, we deleted the old data in the system
Usage of reports RSSTATMAN_CHECK_CONVERT_DTA and RSSTATMAN_CHECK_CONVERT_PSA
This report build fast access tables (reports RSSTATMAN_CHECK_CONVERT_DTA and RSSTATMAN_CHECK_CONVERT_PSA)
To improve performance when displaying requests (in InfoProvider administration, for example) and loading data, in SAP NetWeaver 7.0, the administration information for requests is stored in special tables (RSSTATMANPART and RSSTATMANPARTT for InfoProviders and RSSTATMANPSA and RSSTATMANPSAT for PSA tables). This allows quicker access to the information. These quick access tables are part of the status administration that makes managing requests easier. The reports RSSTATMAN_CHECK_CONVERT_DTA and RSSTATMAN_CHECK_CONVERT_PSA write available request information for existing objects to the new tables to enable quicker access.
To archive request older than 3 months
To create delete jobs for ARCHIVE FILES of valid but incomplete archiving sessions for an archiving object.
Please provide me your valuable inputs and suggestions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
4 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |