Symptom
- The customer is experiencing an issue with data disaggregation based on data locking in SAP Analytics Cloud.
- When entering data at one specific year level , the system throws an error "Data can't be changed because it is for one or more members that are outside of the planning area of this version. The members come from the following dimension: Date" instead of disaggregating the data across the remaining 11 months.
- one month is locked for data entry, and the model-level setting "Data disaggregation based on Data locking" is enabled.
- The table becomes non-functional upon attempting data entry at the year level.
Environment
SAP Analytics Cloud
Reproducing the Issue
- Enter data at one specific year level
- Ensure that at least one month is locked.
- Observe that the system throws an error instead of disaggregating the data across the remaining months.
Cause
The disaggregation algorithm in SAP Analytics Cloud is designed to distinguish between booked and unbooked data.
When editing booked data, if all potential disaggregation candidates are locked, invalid due to validation rules, or restricted due to data access control, no unbooked candidates are considered, even if they are otherwise editable.
Resolution
- This behaviour is consistent with the current system design.
- When data is locked in the table, entering a value in a parent cell does not disaggregate the value to unbooked child cells that are empty. Disaggregation works as expected only when child cells already contain data.
See Also
Keywords
sap analytics cloud, data disaggregation, data locking, year-level data entry, disaggregation error, planning table, locked data, unbooked data, disaggregation algorithm, sap help guide, SAC, , KBA , LOD-ANA-PL-DIS , Distribute, Spreading, Assign, Copy & Paste , Problem
SAP Knowledge Base Article - Public