Implementing Data Locking to Control Data Access in a Story

When using data locking, there are two related settings for data tables in stories:

1. Data Disaggregation: The data disaggregation settings provide more control over how values are spread from parent members to leaf members. Enabling the following options will change how data disaggregation will occur and prevent disaggregation to those locked (by data locking) or invalid (due to relationship validation) leaf members that would otherwise normally receive values.
2. Security: Some restrictions automatically make cells appear as read-only in a table, while other restrictions allow you to edit the values in restricted cells but won’t allow you to publish changes to restricted members.

In a story, you can set and view data locks by cell.

The statuses include:

• Open: Any user with the appropriate authorization can change the data.
• Locked: No one can change the data.
• Mixed State: A combination of open and locked statuses, for example, a parent will have a mixed state if one of its children has a different status.

Turn the indicators on or off in a story by going to More Actions→Show/Hide→Data Locks from the story table.

If a user is logged on as the owner, they can change Restricted data.

If a user is logged on as a non-owner:

• Assuming they have the Planner Reporter role, they can’t change the data lock status.
• They can set the cell to ignore data locks and change the data but they can't publish it.

In order to use data locking, non-owners require a role that includes Read access to the Data Locking activity (in a role).

Visit the SAP Help Portal for more information on Permissions.