Symptom
Some materials are not planned by MRP even if the processing key NEUPL is applied in the total planning transaction code MD01 or program
RMMRP000, but it can be planned in single planning transaction codes like MD02 or MD03.

 

Reproducing the Issue
1. Run transaction code MD01 or program RMMRP000, or schedule a MRP job by transaction code MDBT.
2. Check the result in transaction code MD04 or MD05, no changes in the result though there should be.

 

Cause
The planning file entry of the material has not been created, this can be checked in transaction code MD21. Normally, the planning file entry should
be  created automatically when the material master is created if the MRP type of that material is MRP related (It is not MRP type ND.) and MRP is
activated for the plant, but there are some exceptions as following.
l As note 327735 describes, if materials are created by direct input program RMDATIND and the field 'Update planning file entries' is not
selected in the intial screen of that program, the planning file entries of the materials are not created. Program RMDATIND can be called in
transaction code LSMW or directly by users.
l As note 97405 describes, it may happen if the materials has been existing before MRP was activated for the plant.

Resolution
Run transaction code MD20 to create the planning file entry individually or run transaction code MDAB to create collectively for a plant, MDAB can
find the missing planning file entries of materials and create automatically.
Additionally, if the planning file entry exits but no planning flags are set in that by stock changes of inventory management so that the materials are
not planned, please refer to note 27153, that describes on how and when the flags are set against different scenarios like reorder point and others.
As that mentioned, not all stock changes set the flags, but it can be realized by customization as well

 

posted on 2017-07-25 10:14  闻歌  阅读(155)  评论(0)    收藏  举报