Data slice disable affects work status

[former_member551125]

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.

[former_member551125]

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