Planning in Data Tables

Data entry is key to planning functionality. SAP Analytics Cloud's planning functionality makes it easy to enter data and perform calculations – from simple to robust – on that data and write it back to your database.

In the following example, you can see some of the key data entry features in SAP Analytics Cloud:

• Adjust plan by +/-, %, or absolute value
• Shortcut scaling characters to simplify input
• Automatic highlights of impacted and related cells
• Messages with number of records changed

Data tables in stories are automatically scaled to thousands or millions depending on the data. The scaling factor is displayed on the upper left of the data table.

It is also possible to set scaling for a table in the data region styles.

When you enter numeric values, the system automatically displays the scaling factor in the cell, as seen in the following example.

You can see in the following example that when there's a data change an asterisk appears in the affected column. The asterisk and the yellow markup mean that the data entry function is being used but not published.

Data entries can be tested before you save and publish them.

You can type an absolute value in a cell, or type a relative value such as *2 or +500 to perform simple mathematical calculations on existing data. For example, if the data value in a cell is 100, and you type *2 in the cell, the value will change to 200.

You can also include the scale when typing a value. For example, if you want to enter the value 1,000,000, you can simply type 1M, and SAP Analytics Cloud will interpret that entry as 1,000,000.

When data is entered for a parent member, the system will automatically disaggregate the data to the children of the parent equally or in proportion to existing values. This saves time for planners since they don't have to enter data for every base member.

Disaggregation can be controlled as follows:

• Filter the data table so that input cells only represent base members.
• You can control disaggregation by enabling Data Disaggregation - Data Locking and / or Data Disaggregation - Validation Rules in the planning model and also in the data table.

There are several terms that relate to disaggregation, such as allocation and distribution. In this context, we're using these definitions:

• Disaggregation: The system automatically disaggregated values entered for a parent to its children equally, or proportionally based on existing values.
• Allocation: This is based on explicit instructions in an allocation process.
• Distribute: This is an option in the planning panel used in stories.

In the following Disaggregation example, discounts are disaggregated:

1. Existing discounts: The children of the Discounts account in Feb (2025) contain existing values that total .8m. In Mar (2025) no values are posted for Discounts.
2. New discounts: Values of 1m for Discounts in Feb (2025) and in Mar (2025) are entered.
3. Discounts disaggregated:
   • The delta of .2m is spread proportionally to Pricing Adjustments and Sale Allowances. Since every dimension in the model is restricted to base members in the table filter, only two records are updated.
   • The 1m entered for Discounts in Mar (2025) is disaggregated equally to the four children accounts because they don’t contain any data.

When you enter a value in an unbooked cell with a hash character (-), the following rules are used to determine how to disaggregate the value along each dimension:

• If the unassigned member (#) is available as a leaf member of the source cell, this member receives the same value as the source cell, and other members of the dimension remain unbooked.
• The unassigned member may not be available and in these cases, the value is spread to base members based on the dimension's aggregation type. Some reasons why the unassigned member may not be available:
  • It's filtered out of the table.
  • It doesn't aggregate up to the source cell.
  • It doesn't exist for dimensions such as Time and Account. In these cases, the value is spread to base members based on the dimension’s aggregation type.

Visit SAP Help to find additional information about the disaggregation of values during data entry

Cell locks prevent data entry for specific table cells and are defined in the table. When you lock a table cell, the value in that cell won't be updated when you change the data.

When using cell locks, it's important to remember:

• Cells locks can be saved with the story.
• Cells locks are page-specific.
• Cells locks are story-specific.
• Cells locks apply to everyone who accesses the same page in the same story.

You can set locks individually in the table by right-clicking a cell and choosing Lock Cell or set locks on multiple cells by using the Value Lock Management panel. The Value Lock Management panel can be accessed from the main toolbar in the ...More option.

In the example below, five key elements for cell locking in the story and in the Value Lock Management panel are highlighted:

1. Lock a cell: Right-click on a specific cell and lock it. This prevents data entry and disaggregation won't update the cell.
2. View all locks: View existing locks and their priority in Value Lock Order.
3. Set new lock: Create a new lock by clicking the icon.
4. Clear locks: Clear all locks at once.
5. Reset priority: Reset the lock order.

To change a lock's priority, you can rearrange locks in the Value Lock Management panel. In the Value Lock Order, you can drag a lock to change the priority. After you move one lock, priority values appear for all locks in the list with their specific priority.

When you lock a table cell, the value in that cell won't be updated when you change the data. By default, data entry processes have lower priority than cell locks. If you want to give data entry processes higher priority, you can change the order of the locks.

Adding multiple values to a table can be time consuming when you've to wait for the system to update the data source after each entry.

Mass Data Entry allows you to enter multiple values in a table without waiting for the system to update between entries.

In order to use Mass Data Entry, follow these steps:

1. Switch to Mass Data Entry using the table's More Actions menu.
2. Enter data values.
3. Select Process Data to apply the changes and exit or select Exit Mass Data Entry to leave without applying changes.

By default, data values are entered using Fluid Data Entry Mode.

In Fluid Data Entry Mode, data values entered in a fast sequence will be processed together at the same time as a batch; you don’t need to wait for the system to update between entries.

To set or change the time interval for fluid data entry batches, go to System → Administration → System Configuration and update the value for Time interval of fluid data entry batches (in milliseconds).

Data values entered with time between every two successive data entries within this set time interval will be treated as belonging to the same fluid data entry batch. For example, you set the time interval to 500 milliseconds (0.5 seconds). If there's a 0.5 second of inactivity, a batch is processed, and the next data value you enter will be treated as the first one of a new fluid data entry batch.

You can define multiple Inverse Formula options in a given formula. When doing so, the order in which they are typed determines the priority.

Inverse Formulas require the following characters:

In some cases, it may not be possible to change the value for cost. For example, a cell lock can be applied to cost, or values can be entered for cost and profit simultaneously. To allow data entry in these cases, you can define a secondary Inverse Formula that assigns value to revenue:

[Revenue] – [Cost] | INVERSE([Cost] := [Revenue] – [Profit]) OR INVERSE([Revenue] := [Profit] + [Cost])

When the first Inverse Formula can't be applied, the data entry can be carried out using the secondary formula. As a result, the revenue value is adjusted.

Visit SAP Help for more information on Inverse Formulas