By utilizing the knowledge about the object’s life cycle, the application logic regulates when current data turns historical. The application logic authenticates the conditions at the object level from a business point of view which are based on the status, execution of existence checks, and verification of cross-object dependencies.
The data will be transferred during a Data Aging Run. Many tasks have to be fulfilled, for setting up an Aging Run.
Determining the data: For determining the data for which Data Aging is intended, one can use the application-specific runtime class. The SAP application allocates these runtime classes to the applicable Data Aging object to ensure the runtime class can be called and managed in a Data Aging run.
Managing Partitions: For transferring the data from the HOT partition of the database to the COLD partition(s) as per the specified partitioning objects and partitioning groups, all of the participating tables are required to be partitioned for Data Aging. You are required to define the partitions for corresponding tables of a Data Aging object (DAGPTM), for each system, and this setting is not transportable. Incase the conditions are not fulfilled, the Data Aging run is not started. There should be at least one cold partition covering todays date and for multiple partitions on one table there should be no gaps in the intervals.
Activating Data Aging Objects: post defining the partitions you need to select the transaction Data Aging Objects (DAGOBJ) for activating the Data Aging object. The system runs through several checks on each table, which belong to the Data Aging Object to make sure that the Data Aging object can be used for the run. (specific Settings for Data Aging Objects)
Managing Data Aging Groups: You can define Data Aging Groups via transaction DAGOBJ -> Goto -> Edit Data Aging Groups and choose all Data Aging Objects which has to be processed in one Group.
For scheduling Data Aging Runs, user needs to go to transaction DAGRUN and choose a Data Aging Group, Maximum Runtime and Start Date/Time to schedule the run. The same transaction can be utilized for monitoring Data Aging Runs as the initial screen displays a list of runs with the details, such as, Start date/time , duration, the Data Aging Groups and Job name.