PP MRP Why Planning file entry still Exists?

Does anyone know why a planning file entry would exist for NETCH or NETPL when there has been NO activity on the material since the last planning run? No movements, no PO's created, no Orders taken, no activity whatsoever . . . and MRP ran, created a planned order, which was converted to a requisition and then a PO. This PO was converted for a date earlier than what MRP recommended.

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.2004/26.06.2004)" - on a current date of 03/06/2004. 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.

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.