Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert

Note 2237251 was released to correct a program error on Long Term Planning and it causes a side-effect that can lead to several problems on Long Term Planning. After the implementation of this note, Long Term Planning does not consider Planned Independent Requirements when it is executed on transaction MS01 or by transaction MSBT in background, and LTP will not create planned orders to cover those Planned Independent Requirements.

This issue was resolved with the following correction note:

2256211 - Different planning results using MS01 or MSBT and MS02

However, It may be difficult to identify the issue, as it seems that the material was not planned at all by Long Term Planning and, when LTP is executed on transactions MS02 or MS03, the material is correctly planned. Therefore, the issue seems like a problem on the update of the planning file entries. Therefore, this blog explains under which circumstances this note is necessary and how to check if this issue is observed on your system.

How to identify the issue?

The issue was already described with the following symptoms:

  • Materials are not planned by LTP;
  • LTP does not generate planned orders;
  • LTP deletes planned orders;
  • LTP planning file is not updated;

The trick is to compare the MRP list (transaction MS05) just after the LTP execution with the Stock/Requirements List (transaction MS04).

On the Stock/Requirements List, all the PIRs will be correctly listed, as shown on the figure below:

On the MRP List, however, there will be not PIRs, even though they exist during the LTP run:

We can even confirm running LTP on transaction MS03 and observing that the PIRs will be correctly considered and that LTP will create planned orders to cover those PIRs:

The note which causes this side-effect was delivered on the following Support Packages, therefore, if your system is running one of these support packages, this issue will be probably observed and the implementation of note 2256211 is strongly recommended:

Software Component  Release  Support Package