Skip to Content
Author's profile photo Caetano Almeida

CO41: Changes introduced by note 1901579

Note 1901579 was recently released (and introduced on support packages for the latest releases) to correct a program error that could lead to inconsistent results when changing the planned order quantity after jumping to MD04. Many users were used with the old behavior, therefore, I’m writing this blog to clarify why this change was necessary.

When calling transaction CO41 to run the collective conversion of planned orders, system allows you to select a line and jump to transaction MD04.


On transaction MD04, you can select a planned order and click the pencil to edit it on MD12:


Here, we can change the planned order details, such as the quantity, and save the results:


PROBLEM: After changing the order quantity and getting back to transaction CO41, the planned orders were not selected again from the database table PLAF, therefore, the new quantity was not update on CO41. Therefore, the planned orders would be converted with the old quantity, before the changes made when jumping to transaction MD04.

In order to avoid the conversion of orders with an incorrect quantity, note 1901579 was created. For design reasons, it is not possible to send the new quantity from MD12 back to CO41. Therefore, the planned orders must be selected again from the database when you come back from transaction MD04.

It means that, if you have changed the quantity of a planned order on CO41, before jumping to MD04, this change will lost when you jump back to CO41, since the order will be selected from the database again.

This is the new system standard behavior, as of the following support packages, and it was designed to prevent the conversion of a planned order with and incorrect quantity:

Software Component Release Support Package

If note 1901579 is implemented on your system, you should also implement note 1918330, so that system can memorize the manually excluded planned orders and exclude them again after re-selecting the updated planned orders.

Best regards

Caetano Almeida

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Kiran Madhurakavi
      Kiran Madhurakavi

      Thanks for Sharing This Caetano.

      Author's profile photo Mariano Cabalen
      Mariano Cabalen

      Thanks Caetano!!

      Author's profile photo Eric Chen
      Eric Chen

      many thanks Caetano.

      Author's profile photo Former Member
      Former Member

      Thanks for sharing this

      Author's profile photo Fiorenzo Di Marco
      Fiorenzo Di Marco

      Hello, I need help
      We did upgrade to EHP7 (SAP_APPL = 617/0011)
      and it has come back this problem, but we can not apply this note! Has anyone had the same problem ? Fiorenzo

      Author's profile photo Caetano Almeida
      Caetano Almeida
      Blog Post Author


      What is exactly the behavior observed on your system? If you have any pilot note implemented before the upgrade, you must implement it again.


      Author's profile photo Fiorenzo Di Marco
      Fiorenzo Di Marco

      Hello, I had no particular pilot note, was made to update EHP7 and does not work now refresch (the “F8”) within the transaction CO41. 

      Author's profile photo Fiorenzo Di Marco
      Fiorenzo Di Marco

      we opened an "incident" on the SAP portal :

      The problem is perfectly described on this page:

      The note mentioned 1901576 is obviously applied in our systems, since is included in a lower support package, but the issue is always present. 

      we await the answer of "SAP"