Skip to Content
author's profile photo Former Member
Former Member

Selecting Time Periods when Linking Work Status with BPF Actions

A feature of BPC is that you can add an activity to a BPF to automatically set work status. This is great because it means the integrity of planning data is protected without users needing to use various confusing Excel screens, often requiring multiple clicks.

We currently use Work Status to protect TIME/VERSION/ENTITY combinations to prevent users modifying data that is historical or not intended for planning.

The result is that in the Forecast, 6 months may be Locked (by an Admin), and 6 months may be unlocked (for planning)..

Above: Example of locked periods, plus planning periods. Ignore middle periods.

When creating a BPF Instance you can only select a single Time hierarchy node or member, meaning either 2017.06 or BAS(2017.TOTAL) will be set upon clicking 'Submit' or 'Approve'.

This results in either only a single period (2017.06) being Submitted, or an error because the user cannot set periods that are Locked back to Submitted.

Although we do have 'First Plan Periods' and 'Last Plan Periods' maintained in the Version, these selection are not available without using an ABAP BADI.

One alternative is to model a 'Planning Time Periods' hierarchy for each Planning cycle and use this in the BPF Instance, meaning only time periods in this hierarchy are set.

Sharing of your experience with how you may have handled this scenario would be much appreciated,


Add comment
10|10000 characters needed characters exceeded

  • Yes, looks like the mechanism is useless for setting workstatus on number of months.

    Please don't create multiple hierarchies in TIME dimension - a lot of issues will be present.

  • Former Member Vadim Kalinin

    Can you please be more specific on the issues present?

    I have seen implementations where this has been configured without issue.

    Cheers - Nick

  • In the old days with BPC 7.0 and early 7.5 I think it was possible. But when the 3 hidden time hierarchies were introduced to speed up calculations - adding extra hierarchy resulted in issues.

0 Answers