APO - extreme growth of EBAN table

[former_member192550]

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

[Damean]

My 2 cents is to take a look at why is there such a high volume of PReq.  I know of several companies  that generates more than 18 months worth of PReq in APO and send all of them to ERP. Most of them has now redesign their process .... The original reason they want to do so is because some vendors required 18 months worth of forecast for collaboration purposes; these could have been easier to achieve via an SNP reporting cube.