Skip to Content
Author's profile photo Caetano Almeida

PP-MRP Hot Note – “MRP does not plan any materials” and further clarifications about planning file entries

After the upgrade for releases 616 and 617 some customers are observing that, after the MRP run system does not plan any material.

The problem is observed after the MRP execution on MD01, MDBT or by program RMMRP00 and it happens because the planning file entries do not exist anymore. In addition, the problem is only observed on systems where the planning file entry is stored on the old table MDVM and where report RMMDVM10 is executed frequently.

The issue happens because of a program error on report RMMDVM10 causes the deletion of the planning file entries from table MDVM. Without planning file entries, MRP will not select any material for planning.

If you are facing this issue on your system, the following note should be implemented, in order to correct the error on report RMMDVM10:

1988257 – MRP does not plan any materials

After that, transaction MDAB (or report RMMDVM20) should be executed, in order to rebuild the planning file entries.

In addition, some clarifications are necessary regarding reports RMMDVM10 and RMMDVM20, as there is a lot of misunderstanding and misusage of these reports.

1 – Report RMMDVM10 runs a consistency check for the planning file entries. It can catch inconsistencies on the low-level code and delete unnecessary planning file entries, however, this report DO NOT check the flags NETCH and NETP for existing entries.

2 – Report RMMDVM20 is generally used to build the planning file entries, before the first MRP execution for a plant. This report will create the planning file entries when they do not exist, however, if the planning file entry already exists, the report WILL NOT check the flags NETCH and NETPL.

I have seen many users running those reports, expecting to have the flags NETCH and NETPL checked, therefore, it’s very important to reinforce that this is not the purpose these reports.

Both reports were created for very specific purposes and they were not originally designed to be used regularly. It means that it’s not necessary to run any of these reports on a daily or weekly basis on your system.

Running those reports regularly on your system or even before the MRP executions is generally a waste of resources and it will only contribute to increase the total MRP background jobs runtime.

The following KBA also provides more details about the frequent issues related to planning file entries and it may be useful for further reference:

1890440 Materials are not planned by MRP

Assigned Tags

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


      Thanks for getting this info to us,It is very useful from MRP perspective,


      Author's profile photo Nancy Guo
      Nancy Guo

      Hi Caetano,

      The note says the issue occurs on 616 and 617.  You may need to change the affected releases in your first sentense. 🙂



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

      Thanks for the pointing that Nancy!