APO - extreme growth of EBAN table

Hi All

We do planning in APO using SNP-CTM. We run net change planning daily and regenerative planning weekly.

The solution is live for little more than a year. We are currently experiencing a state where the EBAN table in ECC (PRs) has around 45 million records. This is creating a problem in system performance. This growth is because of the PRs created from APO.

Kindly let us know the best practices to handle this issue. We know archiving can be a potential solution but we are looking for some other solution to contain the table growth/ PR creation.

Thanks,

Anand Solomon