cancel
Showing results for 
Search instead for 
Did you mean: 

Cleanup of archive tables ADMI_RUN and ADMI_FILES after system copy

Former Member
0 Kudos

We have performed IDOC and some MM document archives in our production system.

When we perform a system copy to our Dev/QA systems the info in tables ADMI_RUN and ADMI_FILES etc is copied, therefore containing info on the production archive runs.

This of course is of no use in the Dev/QA systems.

Is there a method of safely purging unnecessary data from these tables?

Accepted Solutions (0)

Answers (2)

Answers (2)

JL23
Active Contributor
0 Kudos

Any other data like sales orders, purchase orders is copied as well. What is the issue with having copied this 2 files?

Let me guess, you want test archiving in DEV/QA and you want prevent that the test archiving goes to the same archive, correct?

Then you have to change the path in customizing of the object you want archive. You still can see the entries from ADMI_RUN and ADMI_FILES, however if the path is changed you cannot access those archives

Former Member
0 Kudos

The BC_ARCHIVE sounds like what I need.

Jurgen, not quite what I was meaning.

My Dev/QA/Prod archives each goto separate repositories.

When Prod gets copied to Dev/QA I don't copy the archive repositories.

Therefore Dev/QA data in ADMI_RUN / ADMI_FILES (copied from prod) is irrelevant.

Former Member
0 Kudos

Hi,

The best option is to archive the unnecessary data from ADMI tables using the object BC_ARCHIVE.

[BC_ARCHIVE|http://help.sap.com/saphelp_erp2005vp/helpdata/en/4a/e440376d0baf43e10000009b38f839/content.htm]

Hope this helps

Cheers!

Samanjay