Determining Archiving Objects

[Former Member]

Hi all,

I have identified some large tables within SAP, and I'm looking at archiving possibilities.

Checking transaction SARA > Database Tables > Archiving Objects > Objects for Table, some tables have a 1-1 relationship with an archiving object while others have many archiving objects available.

Take for example Table COEP, when entered this lists many archiving objects.

Is there a way to determine which is the most appropriate archiving object to use, to remove the most records within the table?

Any advice appreciated.

Many Thanks.

[former_member190120 · Accepted solution]

Hello,

For the CO tables, SAP has provided the following reports to use to analyze which archive objects are most relevant to your CO data.  They are:

RARCCOA1 - creates an extract of the CO data

RARCCOA2 - evaluates the data in the extract

Depending on the size of your tables, you may want to run these reports in a system that is a recent copy of your production system (if you have one).

Hope this helps.

Best Regards,

Karin Tillotson

[Former Member · Accepted solution]

Hi Karin,

Thank you for the guidance, I will take a look at these.

Do you know if there are any similar reports for other areas, MM, FI for example?

Also 'change' tables such as CDCLS

Kind regards

[former_member201157 · Accepted solution]

A good place to start looking for various possibilities is the SAP Data Volume Management Guide..

You can find most of the important tables and information on options available (summarization, prevention, deletion, archiving).

Infact we design a complete solution paper for house keeping and Archiving project based on Information in this document.

This should be a ready reckoner for anyone who is working on archiving or similar activities (managing data volumes).

Just search with the table name and you can find good information on the table.

https://websmp103.sap-ag.de/~sapidb/011000358700005044382000E/DM_Guide_69_Final.pdf

[former_member201157 · Accepted solution]

For table CDCLS...check this OSS note

1257133 - CD: Archiving options for CDCLS

[JL23]

It is true that many tables show several archiving objects in DB15, but that does not necessarily mean that you can use them alternatively.

CO internal orders, production orders and process orders for example are all using the table AUFK, but you cannot archive internal orders with the object PP_ORDER, you would need to use CO_ORDER for internal orders. Each of those objects archives only their individual part from AUFK table.

The same happens with purchase requisitions that are stored in table EBAN, here you see archiving objects MM_EBAN, PP_ORDER etc.

MM_EBAN will archive the the neutral requistions, requisitions that have no specific order relation, while PP_ORDER includes the requisitions with order relation.

Coming back to the CO tables, if you archive the CO items independently then you will not be able to see those details from an archived sales order. You are breaking the direct relation.

It might be a quick win with table space, but a bigger effort for the users if they have to investigate CO item details from an archived sales order.

Same issue with archiving of change history. Not everything what is technically possible does make sense from a business point of view.

[former_member201157]

with reference to this question,

Is there a way to determine which is the most appropriate archiving object to use, to remove the most records within the table?

In addition to mapping the tables with archive objects, TAANA analysis should also be run on the tables in question to identify various document types within the concerned table and the volume (in numbers) for each of the document types per fiscal years.

once you have the information in hand, the as-is business process has to be studied and understand the process flow within your systems.

there could also be cross-functional and cross-system dependencies, all this is basically where the functional study begins so that we can come up with a solution plan (which archive objects to implement with the various transaction types).

an ideal example in this case is CRM system where there is one header table "CRMD_ORDERADM_H"  and all service and sales related data like (service reqiests, sales orders, service orders, incidents , opportunities ) are all coming out of this table.

after doing a TAANA , we were able to find 7 key archiving objects .

[Claudia_Semmler]

Hello,

another option is to run a Data Volume Management Self-Service on your Solution Manager system. During this self-service the managed system (i.e. the system in question) is analyzed and the saving / archiving potential per archiving object / table determined.

For further information you may look into the presentation 'DVM WoC (Masterslide deck) which can be found on

http://wiki.scn.sap.com/wiki/display/TechOps/Data+Volume+Management in the section 'Useful Links' on the lower left of the page.

The information on the Self-Service starts at page 44.

Best regards,

Claudia