SAC-P - Multiple users planning same data set

[sunny888]

Hello Experts,

I have a scenario where multiple users will be planning on same data at same time, how to prevent data overwrite in this case? Is there an option in SAC-P where if one user is planning on a particular data set other users gets message that data is locked or any other option to prevent data entry at same time from 2 different users and prevent data loss.overwrite, something like in BW planning.

example

2 users planning Planned Revenue at same time for same Region and , same period, same company code.

Thanks

[William_Yu]

Hi sunny888,

Pessimistic data lock like BW-IP or BPC embedded is not supported at SAC yet. There is already a related customer influence, you may vote there.

https://influence.sap.com/sap/ino/#idea/288514

Best regards, William

[JefB]

Thanks for referring William.

Most use cases people just need to input and plan at the same time with many other users (collaborative planning). Delaying the merge of changes to the publish event is often not wanted/needed, and causing more issues then benefits.

If the whole implicit edit mode 'feature' in SAC can just be disabled, then optimistic data lock can work much better i.m.h.o. with no need for pessimistic data locking.

If users really want to simulate, let them create an explicit private version, and they will even feel more in control.

[William_Yu]

Thank you for your input Jef.

[sunny888]

Hello,

The need that is felt more often is the ability to have exclusive data lock set on the selection a user has selected to plan data if more than 1 user has access to plan on same dataset. The issue with Private version is that a person working on Private version has to go back and forth to see what changes have been published and how figures have changed and might have to adjust the figures again and this has lead to more confusions and data loss and delay in the overall planning process. This where Private versions have a drawback. Now we can discuss as why multiple users are responsible for same data set for planning but is quite common. This where BW-IP had advantage.

[JefB]

william.yu so now the influence request got closed suddenly... but I don't see the real issue tackled yet.

[William_Yu]

jefbaey, I think it's related to new feature for 2023 QRC3 https://blogs.sap.com/2023/07/28/whats-new-in-sap-analytics-cloud-release-2023.15/#14, of course it's not going the pessimistic data lock approach

[michele_medaglia5]

Hi SAC Friends

I have switched on the new feature regarding paralleling planning.

I connected with a colleague using two different users and planning at the same time on the same data region and we don't get any message

thanks for your help

[N1kh1l]

sunny888

When you make edits to a public version, the version is put into Edit Mode. This creates a private version of the public version that only you can see until the changes are published.

You can leave edits unpublished to resume later, however, it is best to publish changes often when editing public versions. If other users are editing the same version, your changes could overwrite theirs when you publish because the most recent update will overwrite previous states. So users can plan in parallel but the user publishing the data last will overwrite the previous data.

You can also use Version Management APIs to publish, delete or revert data from planning versions even if the table is not planning-enabled. For more information, see Use Version Management APIs on SAP Analytics Cloud Data Models

https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/b6e3d093988e4c3eba7eb...

PLease upvote/accept if this helps

Nikhil

[sunny888]

Hello Nikhil, Thank you for the response. What you shared above exactly the problem statement that there is no way for other users to know if another user is already planning I mean has public version in the edit mode to prevent data from being overwritten. When a user edits a public version then it creates a private copy and there is no way other users can know about this. Only way to prevent is if and only if only 1 user is responsible for a particular dataset and a with a very strict calendar workflow which could be cumbersome and time consuming.

Thanks