Skip to Content
avatar image
Former Member

In IBP 1705, Planning area activation fails when KF base planning levels are changed

Hi Experts,

During IBP 6.3 upgrade there was an issue with few KF's that were used in forecating models. On creating an OSS ticket, SAP suggested that for now we change the time profile root attribute from "PERIODID" to "PERIODID0" in the base planning level for those KF's while they are working on the fix. Hence we created new planning levels same as the original ones expect that we made the time profile root as "PERIODID0" and assigned to the KF's that were part of forecasting models and worked fine.

Now we upgraded to 1705 and SAP fixed the issue. When trying to change the planning levels back to the original one, planning area activation fails with the following error:

E - Key figures have been deleted, or their base PL has been changed.

E - Planning level MSNA1PRODSOLDTOSHIPTO is not used as the base planning level of any stored KF

E - However, key figure values still exist at this planning level.

E - To keep the model consistent with the data, delete the KF values at PL MSNA1PRODSOLDTOSHIPTO

E - Activation failed.

(Here "MSNA1PRODSOLDTOSHIPTO" is the planning level that needs to be deleted and changed back to "SNA1PRODSOLDTOSHIPTO")

From the above error messages, my understanding is that KF values have to be deleted before changing the planning levels. If this change needs to be transported to PRD, we do not want to delete the KF values or copy it to a KF or anything like that. Any suggestions as to how to go about this? This issue was never in IBP 4.0.

Thanks in advance!!

Regards,

Sowmya

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Sep 20, 2017 at 05:23 AM

    Hi Sowmya

    As you have updated the planning level with new PERIODID, the system won't know how to manage data with this new PL for a give KF and that is the reason it will give you the error during activation.

    I know you don't want to copy KF value, but that is the only way to keep your data safe in production by creating new KF1@MSNA1PRODSOLDTOSHIPTO and copy it before you change the planning level. Once KF1 is updated with the data, change PL. TO copy back, you can use COPYDISAGG operator to copy back values to your original KF OR have your HCI team to copy those values from the backend directly.

    Regards

    Ankur

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 21, 2017 at 06:14 AM

    Hi Sowmya,

    I had the same problem earlier, changing of key figures base planning level is not that easy in IBP and if data associated with that key figure is very difficult and not recommendable option also.

    Simple way is to...

    1. Take backup of key figure

    2. Create the new key figure or change the planning level

    3. Reload the data via copy operator

    Let me know still this issue not resolved.

    Best Regards,

    Lingaiah

    Add comment
    10|10000 characters needed characters exceeded