Start of Content Area

Function documentation Deleting or Changing an Archiving Object  Locate the document in its SAP Library structure

Features

When changing or deleting an archiving object for an InfoCube or an DataStore object, there are the following restrictions:

...

       1.      If data has already been archived, certain BI-specific properties of the archiving object can no longer be changed:

¡        The archiving method, that is, whether it is archiving with time slots or with free characteristic selection, can no longer be changed.

¡        Characteristics that were selected as selection characteristics or were selected for the definition of the data object cannot no longer be undone.

¡        The setting for area protection in a DataStore object can no longer be changed.       

       2.      An archiving object generated once can only be deleted together with the InfoProvider.

Workaround for Subsequent Changing of Archiving Objects

For DataStore objects with an active protection of already-activated data areas, the changeability can be restored when you completely reload the already executed archiving run using the appropriate function in the archive administration.

Workaround for Deleting Archiving Objects

Deleting an archiving object independently of the associated InfoProvider is not supported.

In exceptional cases you can delete an archiving object independent of the assigned DataStore object or InfoCube with the program RSARCH_ARCH_OBJ_DELETE (execute using transaction SE38 or SA38). However, all administrative data about already-generated archive files is also lost. The program, however, should only be used when you are sure that you no longer need the already-archived data or that you have already completely reloaded the data into the InfoProvider or an alternative InfoProvider.                                     

Recommendation

We strongly advise you not to delete an archiving object in production operation for data that has already been successfully archived.

Caution

Be especially careful when you execute the deletion program in a development system and then transport the associated InfoProvider into a production system. During import into the target system, there is no check, as to whether there are already archiving runs for the archiving object, and the reference to the InfoProvider for an archiving object that is already present is lost (the archiving object and its archiving runs are not deleted, however).

You should only delete an archiving object when the InfoProvider

·        was not yet transported further with the archiving object,

·        was not yet archived in the supplied target systems or

·        the archiving object was also deleted before in the target systems (under the restrictions listed above).

 

 

End of Content Area