Changing Bucket on Planning Level

[former_member593960]

Dear all,

I did a copy from SAPIBP1 to set up S&OP.

I'm trying to change the bucket of my planning levels from "week" to "day.

However, when I do this I got a failed activation. Have someone got this log before?

SQL Message: column store error: fail to create scenario: [34011] Inconsistent calculation model;calculationNode (4_241):Output table '4_241' has no column 'PERIODID0' in the signature of the main function,Details (Errors): - calculationNode (4_241): Output table '4_241' has no column 'PERIODID0' in the signature of the main function. - calculationNode (5_280): Output table '5_280' has no column 'PERIODID0' in the signature of the main function. - calculationNode (4_245): Output table '4_245' has no column 'PERIODID0' in the signature of the main function.

Thanks in advance!

Kind regards,

Lorena Fumian

[former_member242371 · Accepted solution]

Hi Lorena,

The error is due to some key figure calculation which PERIODID calculation defined in it. Changing the planning would level would have caused this calculation to be obsolete. Please try to identify the key figure from detailed application log and correct the calculation accordingly.

Thanks,

Rohit

[gurucharanscm]

Hi Lorena - I suggest to revert the planning area to last active version and try doing the steps again what you are intending to do. This time, please do a planning area 'check' post each step/change you carry out so you know where the problem is.

Thanks,

Regards - Guru

[ayanbishnu1981]

Hello Lorena

I dont think this issue has anything to do with transnational data deletion or reference to period id in any KF expression. I may be wrong, but i have faced similar issue few weeks back.

First of all, please tell me if you have added any new master data type in that particular planning level ? If yes, then remove that and try to activate the planning level. If not, then copy the planning level and give it a new name and then change the time bucket and activate it.

Let me know if it works.

[lingaiahvanam]

Hi Lorena,

Planning bucket (week to day) changing in the planning area affects the time profile (time periods), all key figures and planning levels associated with it.

While copying SAPIBP1 planning area which applications selected S&OP or all other planning applications?

If you copy S&OP application then identify the key figures and change the planning levels (make sure planning level root attributes) accordingly.

Once you done with changes then run the planning area check instead of activation and share the application log for further analysis.

Best Regards,

Lingaiah

[former_member593960]

Dear Guru,

Thanks for you answer!

I did everything, as you said. My time profile it's originally with day buckets.

I continue getting the same error. Any thoughts?

Kind regards,

Lorena

[former_member242371]

Hi Lorena,

As i mentioned in earlier reply, the error is likely due to missing PERIODID0 in key figure calculation which occurs due to change in base level from Week to Day. Please see the calculation of L-code key figures like SLFULFILLEDDMNDQTY, LSLWASTAGEQTY and SLREMBATCHQTY. All these are defined at WKPRODLOCCUSTBATCH and have PERIODID5(which represents tech week) in their L-code calculation.

If you change the root for this planning level from tech week to day, the calculation should also be updated to include PERIODID0 instead of PERIODID5.

Thanks,

Rohit

[gurucharanscm]

Hi Lorena -

If you are changing the root attribute, make sure all the dependencies are cleared out. Finally, do a purge with the check-box active on 'Delete planning objects'. Also, from what I can sense from the log, I probably would be thinking if I have the time periods generated for 'days' - hope you regenerated the time periods in the time profile if it didn't have days originally? In fact, this is a BIG change - having to have a new period (lower level) defined in the time profile.

Hope this helps,

Thanks,

Regards - Guru