Key Function

Objective

After completing this lesson, you will be able to discover Ad-Hoc Planningfucntion

Planning Features

SAP Analytics Cloud has many planning features that help you plan simpler and faster. These features are covered in detail in the Leveraging SAP Analytics Cloud Functionality for Enterprise Planning learning journey. Below, we will provide an overview of the following:

  • Data entry
  • Version management
  • Data locking
  • Data actions
  • Validation rules
  • Validation driver trees
  • Structured allocations

In addition, SAP Analytics Cloud can be integrated with on-premise SAP planning systems, allowing you to maintain your investment in an existing planning system and use SAP Analytics Cloud as the front-end for planning activities.

Let's go through each planning feature in more detail.

Data Entry

Data entry is based around the table, where you can type relative or absolute values into individual cells. You can copy cell values, along with all the data that aggregates up to the copied value. You can plan at any level of a hierarchy, and the data will automatically be rolled down to the lowest level.

When then data changes, the affected cells are shaded yellow, indicating the data entry function is being used but not saved. 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.

Version Management

When you are planning for all possibilities, it helps to understand how different plans relate to each other and to your actuals data. Version management helps you to complete tasks such as the following:

  • Carry out variance analysis, such as making sure that your working forecast is on budget.
  • Quickly explore, share, and publish different scenarios without losing sight of the original data or introducing unnecessary complexity.
  • Work on your own data until you are ready to publish.
  • Try a change and undo/redo.
  • Use the history to see what happened with the data.
  • Roll a private version back to a previous state if you need to take a different direction.
  • Revert all changes to the original values.
Example of the version management panel

Data Locking

With data locking, you can choose sections of data to lock when you are getting ready to close your books. Each section can also be delegated to owners who can lock the data themselves, or set the data to a restricted state where only the owners can edit it. You can then schedule changes to data locks in the Calendar.

Table with data locking tools dialog open

Data Actions

With data actions, you can model sequences of copy-paste operations, allocation steps, and advanced formulas. With advanced formulas, you model complex processes such as cash flow planning, depreciation, and carry-forward operations. You can build these formulas using a visual editor that does not require scripting knowledge, although a scripting engine is also available for fine-tuning.

Copy operations make it easy to move data from one part of a model to another, or to a different model. For example, if you have separate models for Headcount and Expense Planning, you can use a data action to copy data from those models into a central Finance model.

To make your data actions more flexible and easier to update, you can also add parameters that can be set while designing or running the data action. You can also run other data actions as steps within your data action, letting you quickly reuse common calculations.

Planning users can run data actions in a story. Alternatively, you can use the Calendar to schedule them to run automatically.

Story with data action play buttons and script dialog for the data action

SAP Analytics Cloud data actions are like planning functions and data manager packages in other SAP planning solutions.

Validation Rules

Validation rules let you define valid member combinations across dimensions to prevent improper data entry and planning operations in stories based on a specific planning model. For the dimensions you define in a dimension combination rule, only the member combinations that you specify as allowed combinations can pass validation.

For example, you might want to increase sales of certain products in specific locations. You create a validation rule between the product dimension and location dimension members. Planning users can do planning only for the allowed combinations of products and locations.

Value Driver Trees

Value driver trees let you take a driver-based planning model and turn it into a streamlined visualization for running simulations and making strategic decisions. For example, you might be discussing how vulnerable your business is to raw material prices, or which product line to grow over the next few years to increase profitability the most. Value driver trees allow you to book values to drivers and inputs, visualize the flow of value through the accounts, and see the overall impact on KPIs now and in the future.

You create value driver trees directly in the story. The option to add nodes automatically based the model’s account structure can help you get started quickly, but you can still add and customize nodes as needed. Features like undo and redo, search, and drag-and-drop node linking make it easy to get set up.

Example of a value driver tree

Structured Allocations

You can use structured allocations to establish reusable steps for allocating costs, such as allocating the cost of IT support across different departments by support hours used, or the cost of travel across different product groups based on cost-of-living rates for the customer location.

You build allocation steps using a visual tool that does not require scripting expertise, but that covers a range of different allocation workflows.

Example of structured allocations

Data Actions

Introduction

A data action is a flexible planning tool for making structured changes to planning data in SAP Analytics Cloud. Modelers design the data actions and planners run them in stories or schedule them in the calendar.

A data action is created based on a planning model and consists of one or more steps that are carried out on a public or private version.

Use Cases for Data Actions

Data actions are used to process mass amounts of data.

Some use cases for data actions include the following:

  • Carry out planning tasks automatically
  • Copy by model and across models
  • Allocations
  • Currency translation
  • Calculations

Key Features of Data Actions

Some features of data actions include the following:

  • Sequence data action steps
  • Embed data actions (just like an include)
  • Schedule or ad-hoc execution
  • Include prompts for flexibility
  • Integrate prompts and story filters

Access Data Actions

Data actions can be created from the Navigation Bar or from Files.

Recent data actions will also show in the Recent Files section of your home screen.

Where to access data actions. Start from the vertical menu or open existing data actions from My Files.

Data Action Processing

  • Steps in a data action are executed sequentially.
  • The result of one step is available for the subsequent steps.
  • For each step, the execution scope is defined via filters.
Diagram showing how data action processing works. Model data (right) is fetched to the working set and calculated to the result (middle). The write back functionality sends the data back as Result 1.

Types of Data Action Steps Available

Data action configuration. Advanced Formulas Step is selected in the list on the left and the configuration options are on the right of the screenshot. They are listed after this image.

The following types of action steps are available:

  • The copy action copies data within a model based on a set of rules, filters, and aggregation settings. For example, you can use it to copy data from 2018 to 2019 or Actual data to Budget data. With the Copy action, you copy a value from only one dimension member, but you can copy to multiple dimension members.
  • The cross-model copy action allows you to copy data from a different source planning model based on a set of filters and automatic or manual mapping between dimension members.
  • Each step of an advanced formulas action allows you to create calculations to apply to the data. For example, you can use scripting to calculate opening and closing balances of headcount based on hires and terminations, looping through the data by time.
  • An allocation action creates a new allocation or use an existing allocation step.
  • An embedded data action runs another data action as part of the one you’re working on. Combining these steps with dynamic parameters lets you reuse data actions with different source or target members.
  • A conversion data action is used for models with measures, conversion steps let you copy between measures while applying currency conversion.

Data Entry

Data entry is key to planning functionality. SAP Analytics Cloud's planning functionality makes it easy to enter data, perform calculations 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 being changed on the left, with the resulting changes showing on the right.

Data Scaling

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. When you enter numeric values, for example 10 as in the following example, the system automatically displays the scaling factor in the cell.

Example of data scaling highlighted in yellow in an SAP Analytics Cloud story table.

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

Data Change Indicator

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.

Data table with change indicator highlighted.

Values

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.

Relative Value Options

Relative Value Symbol

In this table, X represents a number.

Description
* XMultiply the value by X
/ XDivide the value by X
X% or - X%Increase or reduce the value by X percentage
+ XAdd X to the value
- XSubtract X from the value

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.

Scale Options

ScaleSingle LetterComplete WordShort Form
ThousandTThousandK
MillionMMillionM
BillionBBillionBn

Hint

You can also copy and paste values from a source such as Microsoft Excel or a flat file to develop your dataset.

Log in to track your progress & complete quizzes