The SAP HANA database provides a special time selection partitioning scheme, referred to as aging. Time selection or aging permits SAP Business Suite application data to be horizontally partitioned into different temperatures like hot and cold. The partitioning of tables which contribute in Data Aging is managed on the ABAP layer (Transaction DAGPTM).
The partitions are not transportable, therefore partitioning needs to be done in each system individually. Similarly Partition Ranges can be upheld in customizing under SAP Netweaver > Application Server > Basis Services > Data Aging > Maintain Partition Ranges. Partition Objects have to be stated for combining many tables which should be partitioned together as per the same schema (Transaction DAGPTC). Typically, SAP applications offer partitioning objects which can be applied. All participating tables belong to the data aging objects and improvements must be assigned to a partitioning object. A table is allocated to exactly one partitioning object and cannot take place in more than one partitioning object. If the assignment of a table to a partitioning object is not fulfilling the customers’ requirements, then without making any changes, they can create customer-specific partitioning groups. Incase, a partitioning object as well as a partitioning group contains the same table, then the Partitioning Groups override the assignment of tables to partitioning objects.
The partitioning is activated only post the next Data Aging Run.