Question:
Hello,
I'm just implementing a batch input ABAP which deletes BOMs. The BOMs for deletion are listed in a table and the transaction CS02 is used. Problem is, I'm trying to delete thousands of BOMs and at the end of the run the batch input ABAP has not deleted about 10% of them. They can be deleted manually, and by batch input using mode A, but when running the ABAP on line or in background it's as though this 10% of them are just ignored. A subsequent run of the program will delete a load of those left behind first time, and after several re-runs most of them do get deleted.
What's happening - why are the BOMs not all getting deleted first time around?
Answer:
Hi,
HAve you checked for errors in SM35?
_________________
Kind Regards,
Ron Johns
Answer:
Good point bucka. Possibly there are errors caused by some kind of dependency. I only did some minor programming in this area a few years back, so I can be wrong, but perhaps SAP doesn't like you trying to delete a BOM for an article which is itself part of a BOM. So it could be a matter of re-arranging the order in which the BOM's are to be deleted.
_________________
So who died and made me tuly idiot ?!?
Answer:
I'll look at SM35, bu the funny thing is that if the ABAP is run a second or a third time the BOMs do eventually get deleted by it. This seems to indicate some system or performance related issue. Also, the BOMs can be deleted manually, and can be deleted using Mode A batch input. It's just when the ABAP kicks off with a large number to delete some of them get left behind. Could it be a record locking problem perhaps?
Thanks.