Is there any archiving object that is client-dependent?

[Former Member]

Gurus:

The systems that I have done archiving have only one client that needs to be archived.

If a DEV system has more than one client to be archived, should the archiving objects be customized/run for each client?

I have this question because the variants for archiving objects usually do not have a "MANDT" (i.e. client) field.

Thanks!

[Former Member · Accepted solution]

Hi Laura,

I'm assuming you are archiving for the production system, in that case there will be only one client. Same is true for your QA environment.

Generally speaking from a development/configuration process, you should configure the object in Client 100 of your Dev environment, then release the transport to Client 300 for your unit testing, before transporting the object to QA then Production.

Hope that helps.

Wayne

[christoph_hopf]

Hi Laura,

from DMS point of view the archiving object is CV_DVS. Regarding the archiving of document info records I can only suggest you to use the transaction SARA. Here you can also do some customizing.

Best regards,

Christoph