Unable to perform, EDI40 Table Cleanup and Reoorganisation

[SwapnilkumarL1]

Hi Team,

Regarding table:- EDI40, in our Production ECC system, the size of this table is 1.2 TB,

It looks the old unwanted data has not been cleaned up hence the size is too large, We need to cleanup the old data untill June 2017.and then reoorg.

as per the note:-1574016 & 40088, it suggests to run the below multiple reports

RSEXARCA RSEXARCB RSEXARCD RSEXARCR RSETESTD RSEXARCL

It is time consuming,

Can some one confirm if i need to execute all 6 reports for the cleanup of old data in this table? is there a fastest method or 1 or 2 reports by running them we can optimize the process.

Thank you.

[JimSpath · Accepted solution]

The canonical note for EDI40 data volume management is:

apps.support.sap.com/sap/support/knowledge/en/2534069

Beyond that reference (which needs an SAP support account to view the details), the SAP Help site has more including specifics on managing through Solution Manager as well as BW data volume controls.

The definitive guide is aptly named "Data Management Guide for SAP Business Suite" and covers data volume and information lifecycle management. The most recent as of late 2020 is version 7.2 from January 2019 (223 pages). EDI, or IDOC document managed are included.

(Link as of November 2020: wiki.scn.sap.com/wiki/download/attachments/247399467/DVM_%20Guide_7.2.pdf )

The SAP community wiki has a good general knowledge page here:

wiki.scn.sap.com/wiki/display/EIM/Reduce+database+size+and+improve+performance+through+data+archivin...

The specific performance question you raised:

> ... execute all 6 reports for the cleanup of old data in this table? is there a fastest method or 1 or 2 reports by running them we can optimize the process.

Your data volume control approach should reveal dependencies so that headers and details don't get lost, etc. while your database team should review the deletion logic for possible tuning. Generally, you're stuck with single-threads and the incumbent locking mechanisms when purging large volumes.

[prithvirajr]

Hi Milind

You can achieve this by implementing IDOC archiving object in your system, this will keep the IDOCs tables in consistence state.

The reports mentioned by you are nothing but reports used in archiving for deletion, reading IDOC data.

Please, also go through below mentioned sap note if that helps.

1574016 - Deleting idocs with WE11/ RSETESTD

Regards,

Prithviraj