We display production planning Heuristics Logs in APO using the transaction /SAPAPO/RRPLOG1 transaction. Review and analysis of heuristics logs is an important activity which helps planners rectify many errors and make sure that planning results are very accurate.
But one problem we encounter in standard SAP is that often the planning logs are confusing. These are not very user friendly and often planners get confused if they try to understand the exact reason of the errors and sometimes also when they try to attribute a particular log to a particular location-product. Often SAP Consultants try to search for means by which they could improve the heuristics logs in SAP APO. I am sharing some helpful information in this small article.
There are some SAP Notes which help to improve the MRP logs. For example, two SAP Notes are as follows:
----------- ----------- ----------- ----------- ----------- ----------- ----------- ----------- -----------
SAP Note 1911427 - Improvements for the logging of the production planning run
Version 3 Validity: 16.10.2013 - active Language English
Header Data
Released On 21.10.2013 11:27:55
Release Status Released for Customer
Component SCM-APO-PPS Production Planning and Detailed Scheduling
Priority Correction with medium priority
Category Program error
Symptom
You use the production planning run. When you check its log information, you notice that some information is incomplete or not specific enough to identify the issue directly or to trace its cause directly. When you use parallelization in MRP planning runs, you also notice that log information is missing or cannot be directly assigned to a planning run in certain cases (for example, when triggered from process chains).
Other Terms
/SAPAPO/CDPSB0, /SAPAPO/BACKGROUND_SCHEDULING, MRP, material requirements planning
Reason and Prerequisites
In addition to functional gaps, the production planning run offers potential for optimization at certain points, which takes effect if it is not triggered directly from transaction /SAPAPO/CDPSB0 or the report /SAPAPO/BACKGROUND_SCHEDULING, for example.
Through the use of parallel processing during MRP runs in particular, the system splits datasets and processes them in parallel using separate tasks in order to optimize performance. Although the system writes logs within these tasks, specific information may become lost that is required to combine all relevant log data into one planning step for display purposes. This may give the impression that certain objects have not been planned or that problems with planning have not been identified.
Solution
Implement the attached correction instructions or import the Support Package relevant for your release.
The corrections in this SAP Note optimize the processes for creating, finding, and preparing logs in the context of planning runs.
----------- ----------- ----------- ----------- ----------- ----------- ----------- ----------- -----------
SAP Note 1920820 - Improvements for the logging of the production planning run (2)
Version 3 Validity: 16.10.2013 - active Language English
Header Data
Released On 21.10.2013 11:37:28
Release Status Released for Customer
Component SCM-APO-PPS Production Planning and Detailed Scheduling
Priority Correction with medium priority
Category Program error
Symptom
You use the production planning run. When you check its log information, you notice that some information is incomplete or not specific enough to be able to directly assign the issue or to directly identify its cause. When you use the parallelization of or in MRP planning runs, you further observe under certain conditions (for example, when triggering it from process chains) that log information is missing or cannot be directly assigned to a planning run.
Other Terms
/SAPAPO/CDPSB0, /SAPAPO/BACKGROUND_SCHEDULING, MRP, material requirements planning
Reason and Prerequisites
The production planning run sometimes not only has functional gaps but also potential optimisation possibilities. These weaknesses make themselves felt if you do not use transaction /SAPAPO/CDPSB0 or the report /SAPAPO/BACKGROUND_SCHEDULING to directly trigger the production planning run.
Due to parallel processing during MRP runs in particular, the system splits datasets and processes them in parallel using separate tasks in order to optimize the performance. The system writes logs within these tasks, but specific information may get lost that are actually needed for display purposes and to be able to assemble any relevant log data to form one planning step. This may suggest that certain objects have not been planned, or problems with planning are not identified.
Solution
Implement the attached correction instructions or import the Support Package relevant for your release.
The corrections of this SAP Note optimize the processes of creating, searching, and editing logs in the context of planning runs.
------------------------------------------------------------------------
|Manual Pre-Implement. |
------------------------------------------------------------------------
|VALID FOR |
|Software Component SCMAPO |
| Release 713 Until SAPK-71302INSCMAPO |
------------------------------------------------------------------------
Before you can implement the corrections of this SAP Note, you need to carry out the following manual steps. You can procure the required modification keys on SAP Service Marketplace. For this, contact your system administrator.
<Text clipped; for details please check out the SAP Note on support.sap.com>
----------- ----------- ----------- ----------- ----------- ----------- ----------- ----------- -----------
But you need to be aware that implementing these two SAP Notes may cause some system performance issues.
Are there any ways so as to implement these SAP Notes for improvements in planning logs and still avoid the performance issue? The answer is yes. To know “how” to do it, wait for the second part of this series. I shall also update this article with the link to the next part.
[Disclaimer: Written by Rahul. This article or post is written by the author based on his personal experience while working on SAP. Before implementing any solution you are advised to always do the analysis and adopt a solution only if it suits you and testing is successful.]
Next posts in the series:
Improvements in Production Planning Heuristics Logs in SAP APO (Part- 2/3)
Improvements in Production Planning Heuristics Logs in SAP APO (Part- 3/3)
