Supersession history Realignment

[Former Member]

Hello Experts,

Assume that the business deals with around 50000 active products and 20000 Supersession chains. My MPOS or lowest possible planning level is: Product, Location and Customer. So, the requirement is realigning the keyfigures in demand planning from predecessor to successors, like history (every monthly load), planned keyfigures on predecessors to be moved on successors, etc.

I have thought of 4 different options. I would like to hear from the experts as well, about how you are handling or have handled in your projects. I would like to know, which way of realignment is better: in maintenance and performance aspects, also complexity of designing the solution.

History of 36 months and future planning keyfigures of 24 months. (so performance is a key factor)

1. Standard data realignment program provided by SAP. (Tcode - /SAPAPO/RLGCOPY)

2. Standard Lifecycle planning provided by SAP. But this is not suited for N:1 or M:N supersession, I guess. Also, if product A is replaced by B and after 2 months, product B is replaced by C, then this lifecycle planning is not possible to maintain manually as A ->C and B -> C, which requires another Z Program for doing the same.

3. First load history of 36 months to livecache. And other future planning keyfigures (from backup) to Livecache. Then, create CVCs for successor. Then use a custom program (z program), to copy the history and other keyfigures and summing up to successor product CVC in livecache.

4. Handling the same in Infoprovider of BI/BW itself. Store original/actual sales history on actual products in BW Infoprovider. Load it to another BW Infoprovider, and while loading it, have transformations to realign the history or planned keyfigures on successors. And then Load it to Livecache.

To my understanding, these are the possible options. Would like expert comments/reviews on these options in terms of performance, maintenance, simplicity of understanding and design complexity. If you have any other options as well, please add the same.

Thanks and Best Regards,

Suresh S

[former_member294172]

My thoughts:

Create a Ztable to capture your multi level supersessions and probably a z program to go with it for maintenance. Let the Zprogram also have the ability to run populate the standard Realignment tables based on the ztable that contains the supersession information. After that is done just run the standard realignment and it should be taken care of.

Mani