Issue related to planning file entries.

[Former Member]

Daily around 50,000 materials are getting flagged with the planning file entries ( NETCH , NETPL & BOM Expl ) in around 10 - 20 sec .

As this is imapcting the MRP run , we need to now the reason why these planning file entries are created .

Note :-

*)   All these materials has been linked to the configurable material in MRP view

*)   There are no changes in these materials

*)   There are no changes in the config mat , BOM , routing .

*)   There are no batch jobs or Idocs processed at the specific time when planning file entries are created

     Assuming that the Time stamp of last update for planning file entry in DBVM is in UTC (Universal time)

*)   We have also execute the program for consistency check of planning file entries , however even this did not help

[Former Member]

Hi ,

On further analysis of the issue , we have come across the following .

There are around 25000 to 30000 materials linked to a configurable material .

So if incase , we change the configurable BOM ; all 30,000 materials variants are flagged with the NETCH , NETPL & Bom exp indicator in the planning file .

As this was not the case prior to upgrading from 4.6b to ECC6  ; could you please let me know whether this is the standard behaviour of the SAP system .

Also it would be of great help if anyone suggest how to fix it .

[Caetano]

Hi Abhijeet

There are several differences between 4.6B and ECC6. Many bugs were corrected and maybe you have implemented a modification that is missing after the upgrade.

I suggest you to look for notes on the SAP Service Marketplace, in order to check if there was any change on this topic or if there is any modification available to control the system behavior.

BR

Caetano

[Former Member]

Hi Saurabh

*)   Yes around 50,000 materials are getting flagged daily .

*)   All these materials are relevant for only one plant ..

[former_member185379]

Hi, One guess, Is it going for Total planning? Is it planning for total plant? May be, it has been set up the scope of plan with plant. Thanks

[Former Member]

Hi ,

RMMRP00 is scheduled as a batch job with only one plant .

[former_member215620]

Dear ABHIJEET GOJE,

Do you mean any 50000 materials are getting flagged. Do these materials are extended in another plant and these plant generate the requirement for these materials.

Regards,

Saurabh

[Former Member]

Hi Arpan

*) MDAB has not been scheduled in the background .

*) We have already executed MDRE , however it did not help .

[Former Member]

Dear Abhijeet ,

As per my understanding Please have a check that the MDAB Transaction making the planning file entries in background or not .

Also have a checks  for the planning file entries through MDRE.

[Former Member]

Hi,

As long as the material planning file entry was set up, the system will automatically modify the planning file entry of materials that have undergone a change relevant to MRP (E.g. requirement date or quantity changed, MRP data changed in material master data and so on).

And the planning file is used to limit the scope of the planning run for the total planning run. For this purpose, all materials that have been assigned a valid MRP type are automatically entered in the planning file. So from my point of view, the planning file is very helpful to improve the efficiency of MRP run, no any impact.

Regards

Tao

[Anupam1143]

Hi

Check these reports RMMDMONI and RMMDPERF for the MRP performance as per SAP note 1865330.

Also check SAP note  204517 for the same.

Regards,

Anupam Sharma

[Former Member]

Hi Anupam

We just upgraded from 4.6 to ECC.

In 4.6 , the number of entries flagged with NETCH per day was around 3000 & the MRP run was taking around 30 min to finish .

After upgrade the MRP run is taking around 8 hrs to finish

As per our analysis , the main reason for the MRP performance is the number of planning file entries flagged with NETCH , NETPL & BOM re-explode indicator .

When we checked the update time stamp in table DBVM for all the 50,000 entries , we observed that all these entries were updated within a time duration of 15 - 20 sec.

In this paticular time duration , we checked whether there were any batch job or idocs getting procesed , but there were none .

As these entries are updated almost daily & there is no centain time when this happens , we need to know whether there is a mechanish with which we can find the specific program which created the planning file entries .

If we find the program , we can debug it .

As planning file entries are created in a number of cases ( may be creation /changing of master data or transaction data ) , we are totally clueless which standard program or Z program is causing the issue