The following behavior occurs in SAP Analytics Cloud for Planning (SAC):
- A model is enabled with the data locking.
- Dimension A is one of the driving dimensions of the data locking.
- Dimension A has the following hierarchy and data locking states:
- You move member A1 from under A to under B and expect the lock state of A1 to change from open to Locked.
However, you find the lock state of A1 remains Open.
- SAP Analytics Cloud (Enterprise) 2022.8.17
The data locking always defines and stores locks on the leaf members level. This means that the lock state of a higher level member is computed based on the locks of its children (LOCKED/OPEN if all children are LOCKED/OPEN, MIXED if it has children with different lock states).
When a lock state is directly set on a higher level node, the state is propagated down the hierarchies of the driving dimensions to the leaf members and persists only there.
So this is the designed behavior that even if you change the hierarchy of a leaf member, its lock state does not change.
Currently, we do not have support for having a node “inherit” the locks state of its parent when moved (or added new) under a node with a given lock state.
The only option would be to manually re-set the locks on the parent member.
If you would like to see different behavior, you can raise an enhancement request on the SAP Customer Influence Site for SAC: https://influence.sap.com/sap/ino/#/campaign/884
SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Sac, Acquisition, Model, Connect, Story, Tenant, Import, Failed, Using, Working, restricted, base, node, nodes, hierarchical structure , KBA , LOD-ANA-PL-DLK , Data Locking , How To