About Planning Data Entry Errors
If you encountered an error message when entering data in a table in SAP Analytics Cloud, check here for solutions and suggestions.
In some tables with advanced filters or multiple restricted measures and filters, you might see the following message after trying to enter data:
Sorry, we couldn’t carry out your data entry because all leaf member combinations for this cell are excluded by filters. Please check any advanced filters or restricted members on the account or cross calculation dimensions, or contact the story owner.
There are a few possible reasons that data entry didn’t work for a specific cell:
-
The table has two or more restricted accounts or measures whose filters don’t overlap at all. For example, a cell with a restricted account that shows 2021 data and a restricted measure that shows 2022 data.
A restricted account or measure excludes members but those cells still appear in the table because they are included for other accounts or measures.
-
An advanced filter excludes a cell but the cell still appears in your table because of the structure of the filter. For example, the filter includes 2019 plan data and 2020 forecast data, and you enter data on the 2019 forecast cell.
For details about advanced filters, see Advanced Filtering.
You entered planning data into a table and an error message appeared telling you to check if cells are blocked by validation rules or cell locks, or if your data changes conflict with each other.
If the aggregation type of the account dimension for this story is of type None, an error message appeared telling you that some member values couldn't be assigned the correct value due to dimension combination rules, cell locks, or other technical reasons.
| Possible Reason | How to resolve this issue |
|---|---|
| There's a dimension combination rule that defines this data cell as an invalid member combination for data entry. | Please ask your planning modeler to check the dimension combination rules defined for this model. See: Define Valid Member Combinations for Planning Using Validation Rules |
| One or more child cells are locked by cell locks and prevent you from entering data to this parent data cell. | Please check the cell locks in the table and unlock the affected cells. Then it will be possible to assign the member value and the parent cell can be updated with your data entry. See: About Value Lock Management |
When entering planning data into a table or triggering a planning action, such as a data action or multi action, you may received an error message telling you that the data is outside of the planning area for that version.
Data can’t be changed because it is outside of the planning area for this version.
The planning area is the data in a version that can be used for planning actions. When editing a public version or creating a private version, you may have the option to use a recommended planning area to edit a defined subset of data. If you choose to use the recommended planning area, or you filter the data copied to your private version, only the data within this range can be changed.
To change data outside of the recommended planning area on a public version, you will need to publish your changes and restart edit mode on All Version Data. Permission requirements for publishing changes will still apply.
For details about planning on public versions or creating private versions, see Planning on Public Versions and Creating Versions. For more information about the recommended planning area, see Optimize Planning Models Using the Planning Area.
A model with measures can contain decimal measures or integer measures. Different restrictions apply to each data type, and data entry and other planning operations need to meet these restrictions:
| Data Type | Value Range | Decimal Places |
|---|---|---|
| Integer | Between -2^31 to 2^31 (that is, 2,147,483,647) | None |
| Decimal | Up to 15 digits, including decimal places | Up to seven, depending on how it’s set up in the model |
If a planning operation enters unsupported data for a measure, a message will appear.
-
When an integer measure receives a decimal value:
This data entry wasn’t carried out because it booked a decimal value to a cell that requires an integer. Try entering a different value.
-
When an integer measure receives a value that’s outside the supported value range:
Sorry, we couldn’t carry out your data entry because the entered number isn’t within the allowed range of values. Try entering a different value.
-
When a decimal measure receives a value that’s outside the supported value range or has too many decimal places:
This data entry wasn’t carried out because the entered value has more than 15 digits or more than <X> decimal places. Try entering a different value.
(<X> represents the number of decimal places that the measure supports.)
-
For decimals, the restrictions don’t apply to trailing zeros. For example, 100.00 counts as a single digit with no decimal places.
-
If you’re using scale suffixes, the restrictions apply to the actual value that’s booked to the cell. For example, entering 1.1 million results in a value with no decimal places.
Dimension attributes give you additional details about each dimension member, like the color of a product or the employee responsible for a region. There are two ways to add attributes to a table:
-
Display the attribute of each dimension member without changing the table’s structure.
-
Add attributes to the rows or columns like a dimension (this can add new cells to the table).
Each dimension member has only a single value for each attribute. However, if you’re showing unbooked data and you add attributes to the rows or columns, your table may show cells that don’t exist in your model.
For example, in the image below each customer has a single customer status (shown in the italicized Customer Status column), but cells are available for all three customer statuses. This is because customer status is added to the table’s columns, too.
If you try to enter data in one of the cells highlighted in yellow, you’ll see the following message:
Sorry, we couldn’t carry out your data entry because the combination of dimension members and attribute values is not valid for the cell that you tried to change. Please check your filters or contact the story owner.
To avoid this problem, consider removing either the dimension or the attribute from the table rows and
columns. If you remove the attribute, you can still display it by selecting 
Properties
for the dimension in the Builder panel and choosing the property.