How to prevent users from updating numbers where they have only read-access

[JefB]

With model option Data Privacy enabled, we have setup roles to define read and write access.

Even if a role has read access, users are still allowed to change data and 'play with the numbers' in their own private versions. When publishing, users will receive a warning message that some updates were not allowed. There is no indication which of the updates were allowed with write access or not allowed with read access.

Only the updates with 'write' access can ultimately be published.

To prevent this warning message and confusion with end users:

1. How can we disable users from updating 'read-only' numbers in private versions?
2. Or how can they see which updates (on read access) were not allowed?

[ThomasK]

Hi jefb , the incidents are still open. Currently development team is checking them. Will update you. BR Thomas

[JefB]

Hi Thomas, any news already?

[ThomasK]

Hi Jef, SAP says the behavior is as designed. Unfortunately they don´t want to understand the business case and how confusing it is for users to see masterdata which they have nothing to do with.

My only recommendation is: Use filters (or bookmarks) in the story whenever possible, because they are limiting the members visible in Add Member function and used in Dis-Aggregation of data.

My customer is very unhappy with SAP ... We try to convince them in a meeting with product management, but it takes all too long.

BR Thomas

PS: Thanks for your votes on the improvement requests

Improvement Request Details - Customer Influence (sap.com)

Improvement Request Details - Customer Influence (sap.com)

[ThomasK]

Hi Jef, have experienced the same. You mentioned the situation with publishing, but there are 2 more issues coming along with this:

a) Users see all members of a dimension when using the Add Member function
e.g. a sales representative is responsible for 200 customers but when using the Add member function to enter a new data combination he sees all (e.g. 5000 customers). For me this is a bug and I sent an incident to SAP.

b) The disaggregation function behaves in the same way. If the sales rep enters e.g. the value 1000 on level of all customers I´d expect it´s distributed to the 200 customers of him. But in fact the value is distributed to all 5000 customers. Later when publishing only the value for the 200 can be published (same behaviour as described by you). The wrong disaggregation is also a bug to me and I opened a further incident.

BR Thomas

[JefB]

Hi Thomas, have you got any replies/updates on your incidents?

[JefB]

Seems like there are some known issues or limitations that SAP is aware of when I look at this recently published KBA... where similar things happen with data locks:

2936738 - Data entry and publishing is possible via the cross-calculation on a locked data region in SAP Analytics Cloud (SAC) & SAP Digital Boardroom 2020.12.0
https://launchpad.support.sap.com/#/notes/2936738