Dataaging of Change Documents

[former_member467198]

Hello All,

We are in the process of implementing Data Ageing of Change Documents. The data ageing object BC_CHDO has been activated. Data residence is 366 days. Entries in CDHDR is more than 6.6 miliion records while in CDPOS is more than 2.8 billion records. The job is running for more than 15days now. So far only 20% of the records have been migrated to the Cold Partition. The job is distributed among the 3 application server work processes. We have explored the parallelization of the job but there is no option to put the package size in the customizing of BC_CHDO. We need your expertise to make the execution of the job faster.

[former_member212218 · Accepted solution]

Hello Team ,

We do not recommend Dataaging enablement for customers anymore . Native storage extension (NSE) is supported for HANA customers on HANA 2.0 SPS 4&Up ( SPS 5 is preferred) and recommended approach for customers looking for HANA WARM DATA Storage option. Please refer SAP Note 2799997 - FAQ on NSE for more information. Please reach out SAP support team in case of any issues .

Hope this helps !

Swetha

[Nico1966]

I have implemented the same for different objects last year for one of my clients and faced similar issues.

If you read SAP note 2869647 - Guidance for use of Data in SAP S/4HANA you will see that SAP basically recommends for these kind of SAP tables to implement NSE instead of DA.
Therefore I reversed the DA objects (reloading aged partitions to memory can take quite some time) and implemented NSE with the basis team.
I recommend you (based on the mentioned SAP note) to implement NSE instead for these tables.
Some good suggestions on using NSE can be found here: https://blogs.sap.com/2021/10/25/hana-nse-part-i-tech.-details-qa/.

Hope this helps you further.
best regards, Nico Kuijper