Now each time MRP runs, we get exception #15 - delay the order until later (gives date). We don't change it and the planning file entry doesn't go away, even after the run.
Found a note that seemed to apply, but I guess it doesn't really.
"If the planning run terminates for a material with planning file entry on account of an error message, the planning file entry is not deleted if this is not explicitly set in customizing. In transaction OMDY, you can set for which errors (message number) you want the planning file entry being deleted."
I thought this was my answer. However, after looking in OMDY - the message #015 = Dates incorrect (start date > finish date). And message #15 = Enter value for version number increment (VersNumIncr.).
Neither of these defines my MRP List exception message 15 = "Postpone process (28.06.2012/26.06.2012)" - on a current date of 03/06/2012. It's CLOSE, but not the first message.
So if I set the field for the deletion of the planning file entry, it still wouldn't affect my real problem - trying to get this entry to 'go away' after doing what it was supposed to do.
Answer
Please Check CS15 - where used list. May be this material has been added to a BOM of a product/Assy, which has caused an entry in planning file.
Check MD04 for the source of reqt.
Also check MD63, if a PIR exists.
If not, delete from planning file. Try report RMMDVM10 - consistency check.
Notes
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.
The same can checked by running the batch job through scheduling it in T.Code MDRE.
Further Notes
On completion of the Planning run, the system deletes the appropriate indicator from the planning file.
1. The system deletes the NETCH Planning indicator and NETPL indicator for a regenerative Planning run and NETCH Planning run.
2. The system deletes only the NETPL Indicator for NETPL Planning run in the Planning Horizon.
If termination occurs when planning a material, the indicators for the materials remain in the planning file so that material is planned again.
