inconsistency in planning file

 

Planning File entries can be set manually for each material or using a batch job using T.Code MD20/MDAB.

 

 

 

Consistency check for the planning file: Since the entries in the planning file are permanent, you must check their MRP

relevancy regularly. If, for example, a plant is subsequently excluded from material requirements planning, its materials will still

be included in the planning file. The same applies for materials that are subsequently flagged with the MRP type No MRP and are

thus excluded from MRP. In such cases, you should delete the entries in the planning file.

 

As per  Members comment, planning file entries created automatically during Goods issue GRN,MRP,

1.Check whether such materials having movement means good receipt & good issue through MB51.

2.may be such materials are directly upload by 561 Movement, later having no movement,

3.may be MRP type change to ND

4.Check plant stock on current date through MB5B,tally movement of such materials.

 

*********

Problem as mentioned by Business

There are several materials that customers had processed PRs to intercompany vendor, we can see the requests in MD04, but no further
requirement create although the stock is 0.

      Solution or Findings

For material *

When we check MD05 for given materials, requirement was created as per MRP run and PR * was created by system.

But PR is deleted by below user , because of this its not showing in MD04.

check last MRP run via trx.MD05

 

In case of material *, despite the MRP relevant change in the Material (Stock movement) the planning file entry had not happened. 

To counter act such uncertain behavior SAP has provided one program RMMDVM10 (Consistency Check of planning file entries) to settle the inconsistency.

 

Run the above program for * plant MRP area 2900 or a periodic job can be scheduled for the same through transaction MDRE transaction. 

You can set variant for plant(on MRP area if needed) in MDRE.