Archive BSIS table in Dev environment

[Former Member]

Hi,

We have created our deveopment system by taking the copy of our production system. Now we would like to run archiving in the development system to reduce the datebase size. One of the largest tables in the system is the BSIS table which is around 150 GB. As this table contains the "open items" we assume that the archiving job may not pick records from this table.

Since this is a development environment, we don't need the data from the previous years. Is there a way to reduce the size of this table?

For e.g. by clearing all the open items in the BSIS table so that they are moved to BSAS and then we can go ahead with the archiving. Also, is there a program to do this?

Anybody with archiving knowledge please advise us on this.

Thanks,

Arun

Edited by: Arun Brelvi on Mar 24, 2010 2:38 PM

[Former Member]

Created the table via Se11 by taking the copy of BSIS.

[Former Member]

Hi,

We had created our Development system about 6 months back. Hence theres quite a lot of development work on that client in the system. But we are currently facing a problem with a custom program which accesses the BSIS table. It takes a very long time to fetch the data from this table and which is due to all the old open items still present in the table. Once these open items are closed, they would be automatically moved to the BSAD table. We would like to know any method/transaction that could clear all the open items at one go. Since its a Dev system, we just need the open items to be closed directly but we are unable to figure out how. Also, the BSIS table takes up about 132 GB and has around 390 million records.

Thanks and Regards,

Arun

[Former Member]

Hi my friend

If transaction data(application data) is not needed in this case, you could simply do a local client copy with profile SAP_CUST, which enables you to copy a "shell" client with customizing data only without bringing AP data over.

Compare to convenient client copy, archiving of object FI_DOCUMNT takes longer and more complicated, not to mention data doesn't clean up completely since it needs to leave some "trace" for retrieving or reloading data back.

Usually DEV shouldn't be touched or overwritten because it contains all original configuration as of the very beginning......

Regards,