Variant BOM already exists for this material

[ruud]

Hi,

I had a variant bom FOR MY FINISHED PRODUCT.
In CS05 I saw my products with is components.
I deleted this product from the variant BOM.

Now in CS05 I don't see my product but, when I try to create a BOM for this product with CS01 I receive the following message:

Variant BOM already exists for this material

What I can do?

Thanks
ruud

[CrazyIvan]

Using the CS02 menu, you have to select File > Delete. (sorry, I don't have SAP in front of me. Maybe its not "file". Its the left most menu option in CS02, and then "Delete"). If you just delete the items and then save, that doesn't delete the BOM. And setting the deletion indicator doesn't delete it either [immediately]. Many companies only schedule a maintenance deletion run once a quarter, once a year, or in the case of my company, never. So with the deletion indicator, the BOM alternative will sit out there forever.

[alara10]

Hi Ivan, do yo know if exist a transaction, program o whatever in where it can be massively marked with the delete indicator the BOMs? or it can only be done in CS02?

Thanks in advance,

[CrazyIvan]

I'm still searching for a better deletion technique myself.

The only front end transaction that I'm aware of is CS02. CEWB won't do it. However, I created an Access VBA program to process these types of deletions as well as other mass maintenance functions. The program draws from a simple MATNR-WERKS table in Access. It searches for open window "CS02: Change BOM" or whatever the title of the SAP window is (don't have it in front of me), then passes a series of keystrokes (delete 8 to clear MATNR, then enters MATNR, then {tab} to WERKS field, delete 4 to clear, then enter works, {enter}, etc). The process works fairly well and but its not a real interface. Its just blidly passing keystrokes. It took a little of trial and error and I had to modify the code a couple times so it tests the current window title. There were situations that arose occasionally (e.g. mult BOM alternatives, or warning that its linked to a production verison, etc). I've used it for processing thousands of deletions at a time.

You might be able to set the deletion indicator with CEWB and then have your administrator schedule a deletion run.

More recently, I've just been using CEWB to just strip off a paricular assembly that I manage rather than deleting the entire BOM. This leaves a lot of dead BOM carcasses sitting out there, but its also a lot faster than running the VBA script (which runs about as fast as the worlds fastest keyboarder). Sometimes our operations want to re-activate a dead material and I found that, by just stripping off the assembly, it saved me time having to restore the BOM structure.

[alara10]

Hi Ivan, thank you very much for your response.
I use CEWB and I can mark with the delete indicator all the BOMs that I was going to delete.

Then, I do the archiving for that BOMs.

Regards,

[CrazyIvan]

Hi Alara, What transaction do you use for archiving? That could save me a lot of time.

[alara10]

Hi Ivan, I use the transaction SARA, with the object "CS_BOM".
There, I create a variant with these parameters:

In Control Parameters: Archive w/out direct deletion
In Selection Type: Selection by del. indicator (this, because with CEWB I mark the deletion indicator).
BOM Categories for Archiving: Archive material BOMs
Additional restrictions to the archived BOMs: The restrictions that you need for select the BOMs

I execute the archive and review the results. Then I proceeded to execute the deletion.

I hope the information be useful, regards!