Archive Material BOM issue

[Former Member]

Hi everyone

I wanna archive all material BOM in a client server.

The client server only contain the material and BOM data.

I am using transaction code :CS28 and using object " CS_BOM " . The archive steps are:

1. actions->write

2. create a variant called "BOM"

3. in "BOM" variant maintainence screen,

select "archive with direct deletion" ,

select "selection by delete indicator" ,

select " archive material BOM"

4. add description attribute for BOM variant.

5. save variant and execute the job.

However, when i saw the job overview , the created job is in complete status within several seconds. And i go to CS03 , there is still BOM record existed.

Do anyone know the correct way of archiving material BOM?

Thx~

[Former Member]

Archive with direct deletion has some limitations on deleting the data from database ->

<b>Note

If a data record is used in another alternative BOM, then it is not physically deleted from the database.

Dependencies

In the Archive Customizing object CS_BOM, you select whether the deletion run starts automatically when you connect to the archiving run.

The deletion run is only carried out when the start automatically indicator is set in Archive Customizing for the archiving object CS_BOM.</b>

Please Check your customizing .

Cheers.

[Former Member]

Thx Sanjay. Actually, this client server only upload material and material BOM by using LSMW. It should not has alternative BOM.

I have tried to select all BOM for archiving including material BOMs, document structures, equip. BOM , Locatoin BOM, SO BOM, standard BOM, WBS BOMs.

And i also have checked the customizing setting. "The Delete jobs start automically " is selected.

However, it seems still not working...

Is it related to the problem of "addional restrictions to the archived BOMs? I dont input anything in this selection area.

[Former Member]

You selected "Selection By Del Indicator".

Are your BOMs marked for deletion. Check table STKO, field LOEKZ.

Also check if archive file is being written and the problem in only database deletion is not occuring. This will give a clue whether the problem is in database deletion only or in writing the archive file also.

Cheers.

[Former Member]

Hi Sanjay,

actually I have tried selected "Selection By Del Indicator" and "selection by date validity".

When i select "selection by date validity ( date: 03.11.2005)"

,execution of the job will spend more time (28 seconds).

But it still nothing happened after completed.

I have checked the table STKO. all records(1024 records) of LOEKZ is not marked.

The problem may be on the archive file.

And, does any other approaches are available to delete material BOM?

for example, using FM 'CSAP_MAT_BOM_DELETE'?

I dont try to use it before. could it do the same thing to delete all mat BOM?

[Former Member]

"selection by date validity" will work only if you can give a date after the BOM validity dates. Check what is the validity dates in all your BOMs . If it is 31.12.9999 then this option will not work.

The only other option you have is to mark the deletion flag in all the BOMs and then use "Selection By Del Indicator".

If you have access to OSS , check note number 376650 , which give a program code which can set the deletion flag in all the BOMs. After this if you choose "Selection By Del Indicator" then I guess the BOMS should be removed from database.

Archiving has two actions - writing data to arcive file and delete data from database. You have not mentioned thus far that you file is written . If file is written correctly and data not deleted from database then problem is with deletion program.

If file also is not written ( is blank ) then your problem can be solved in the two ways I mention above, as then the problem lies with no BOMs selected for deletion/ archiving. Is the spool of your batch job blank.

Btw you are using the correct method of archiving BOMs . However there is a report RCBOMDEL which will delete all the BOM records from a client without archiving.

Cheers.

[Former Member]

Hi Sanjay,

I have tried to mark the deletion flag and it works now.

Thank very much~