ZARIXMM1 table growth - MM_MATBEL Archiving Object

[Former Member]

Dear Experts,

We are archiving material documents for past few months. By archiving we were able to restrict the MSEG table growth, but the respective SAP AS table ZARIXMM1 growing rapidly and occupying nearly 800 GB.

Is there any way to handle the growth the ZARIX tables.

Thanks,

Mahesh C

[JL23 · Accepted solution]

The Index is there to show important info of archived data without accessing the archive itself and allows a quick access to the record in the archive.

You need to define in your project together with the users if they need to access the archive at all, for which period they need a quick access and what data they want see immediately.

Based on the needs you can control what data you keep in the index. SAP is storing the index in its table system, so the benefit of archiving is not as big as it could be. SAP Partners offer solutions where the index is not in the table system (still it needs space too).

For many archives we only fill the info structures on special demand and empty it later again.

We had to migrate archives a couple years ago and missed to activate the indexes, and many month later a user asked a first time for a document. So we got to know that nobody really used the archived data (despite on their loud demand in the project meetings) and decided to only provide the data on request.

Analyze your situation, depending on the residence time in the production system you may have a higher or smaller demand.

if you just worry about the size, then you may want to consider partitioning: Example: Partitioning of an Infostructure - Data Archiving (CA-ARC) - SAP Library

[Former Member · Accepted solution]

Thanks Jurgen for the detailed information.