Skip to Content

Data slice disable affects work status

Hi all,

In one of the planning sequence , we are disabling data slice for our requierement but this is causing inconsistency in work status . Although work status is approved and noone can change the approved data via input form ( which is as expected), still the planning sequence can post the approved data pattern.

Is this the expected behaviour ? I was expecting work status would lock the data and there would be no way of by passing this via even disabling data slice.

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Best Answer
    Posted on Jul 24, 2020 at 07:27 AM

    Hi Gunes,

    what is the client you are using, Analysis Office? William was asking whether you have set the Environment/Model information in the workbook.Without this setting you get BW-IP and not BPC Embedded behavior.

    I wonder what you mean with

    ... in one of the planning sequence, we are disabling data slice for our requirement ...

    Observe that work status in BPC Embedded at run time is a data slice, so using the flag 'No Data Slice Check' you will also switch off work status check. This is why this flag exists.

    Regards,

    Gregor

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 23, 2020 at 11:56 PM

    Is planning squence executed with context of BPC model?

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 24, 2020 at 07:14 AM

    Hi William,

    Thank you for your reply. What do you mean by "context of BPC Model". We are running this planning sequence from the input form passing selected scenario and version from the variables of the input form . But there are also 2 more work status dimension that we are not passing and we are able to post data to the locked data region

    When I open the input form itself, I see that posted data region is locked by work status

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 24, 2020 at 08:17 AM

    Hi Gregor,

    Yes we have. Otherwise work status wouldn't work in the input form but it is locking the data region. This statement is what I was looking for :

    so using the flag 'No Data Slice Check' you will also switch off work status check

    Then I think Work status = data slice in terms of not the logic but the technical locking mechanism. Therefore, we disabled also work status by disabling data slice through planning function. Isnt' there any workaround that we can apply? Other than checking work status table in the code - which is a big effort- before posting the data

    Thank you

    One update : We disabled data slice but still calculation posts the same data pattern in the input form. Which means work status works properly for input form, but we are able to change the data in the input form via planning function. In the workbook , we are selecting the same BPC planning model with the work status but it is still posting data although we disable data slice

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 24, 2020 at 01:27 PM

    Hi Gunes,

    the flag 'No Data Slice Check' was invented to be able to run planning sequences in a kind of 'administrator mode', all data slices are only temporarily disabled just for the planning sequence, all other planning objects are still take data slices incl. work status into account.

    If you want to disable only modeled data slices 'sometimes' then I recommend to implement a data slice of type exit where you have full control when something is checked.

    The thread

    https://blogs.sap.com/2010/04/12/integrated-planning-how-to-activatedeactivate-data-slice-at-runtime/

    might be helpful.

    Regards,

    Gregor

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.