|
Created by: |
SAP |
|
Underlying SAP report: |
RDAAG_AGING_RUN |
|
Client-dependent: |
Yes |
|
Settings as variant: |
Yes |
|
Support for RecycleBin: |
No |
|
HANA-specific: |
Yes |
Data aging is one component for reducing the memory footprint of data in SAP® S/4HANA. Data aging keeps data in the HANA database of the SAP® S/4HANA system in a way that is optimized for a low-frequency of transactional read access. Data aging uses partitioning of the tables whose size should be reduced. Partitions are created and then data from the “hot” partition is moved to respective “cold” partition/s. Partitions that are “cold” are located outside of the HANA database. When the data from a cold partition is required, it is read from the remote database. However, this is transparent for the user, because it means the user or application that the user is using does not see any difference from the more performant HANA database. No application needs to be adjusted.
This task executes an aging run for a specified aging group. In order to use data aging, you generally need to do accomplish the following steps:
-
Activate the business function DAAG_DATA_AGING:
-
Start transaction RZ11 and change the parameter abap/data_aging to the value on.
-
Start transaction SFW5.
-
Find DAAG_DATA_AGING and check the planned status.
-
Click Activate changes.
-
-
-
Set partitions for relevant aging object tables:
-
Start transaction DAGPTM.
-
Choose the aging objects that you want and create a partition for them.
-
-
Activate the data aging object:
-
Start transaction DAGOBJ.
-
Select the desired object and click Activate.
-
You can find more sources here:
https://blogs.sap.com/2019/11/11/case-study-data-aging-in-sap-hana-and-s-4hana/
Settings are based on a variant of the report RDAAG_AGING_RUN. Depending on the release, the following parameters are available here:
-
Data Aging Group
-
Maximum Runtime (in minutes)
-
Enable Detail Log
Our recommendation is to execute this task once or twice a month.
