See how SAP Analytics Cloud Multi Actions change the way that you do planning
Let me guess… You’ve experienced this before.
- You got lost when you had to run several data actions on an SAP Analytics Cloud story. For example, you got forgot which data actions you ran and which ones you didn’t.
- You wanted to execute certain logics automatically after publishing, but discovered that’s not supported. Instead, you had to select Publish Data first then select the data action trigger to execute the logics.
- You wanted to run a cross-model copy, but you couldn’t add several cross-model copy steps to one data action when the target model was different.
I would like to share that we have just released a new planning feature: Multi Actions. This feature will help you overcome the situations listed above, and I believe it will boost your planning experience.
So what are multi actions?
Data actions versus multi actions
If you are familiar with data actions and have played around with multi actions a little bit, you may find that multi actions and data actions are similar in some ways. They both consist of a sequence of steps that you set up in a separate designer. When they’re ready, users can run them in stories or analytic applications using a planning trigger.
However, the focuses are different.
- Focus on core planning calculation capabilities including data manipulation, advanced formulas, allocation engine, and currency conversion.
- Data actions are a single SAP Analytics Cloud component which include the full design time for each supported calculation capability.
- An individual data action result can only be applied to one model and one version.
- Focus on the orchestration of various SAP Analytics Cloud components that can be tied together in a way that simplifies a task for planning users.
- Multi actions don’t include the design time for any individual component, but instead focus on logically bringing the different components together into an end-to-end workflow and providing a specific or common context to execute against.
- The execution scope can range across multiple models and versions.
Technology behind the scenes (optional to read)
I know some of you are still not convinced. You may wonder: why not extend the capability of data actions so they can execute across multiple models and versions? The answer is that the transaction data processing is fundamentally different between data actions and multi actions.
- The data engine behind data actions only allows one target model and one target version.
- All data action steps run on a single transaction, which means that all changes roll back if any of the steps fail. So, in the Version History panel, you only see one change unless the data action result is published. Users can only revert the whole data action, even if the data action includes several embedded steps.
- Multi actions leverage the planning process engine to orchestrate the execution of each data action step. Using this approach, the limitations can be overcome. Multi actions can handle multiple models and versions.
- The transaction of each step is executed and committed separately. One step failure will not roll back the previous successfully executed ones (this will also allow more flexibility when we further enhance multi actions). In the Version History panel, you can see multiple changes, generated by each data action. Users have the chance to revert the results of each data action in the multi action.
When to use multi actions
Consider using multi actions if your planning process involves running data actions on multiple versions or models, or publishing data between data actions. Some typical scenarios are mentioned at the beginning of this blog article.
You can also refer this table to determine whether to use a data action or a multi action:
|Use case||Example||Object type|
|Run a data action multiple times on the same version, and then publish it afterwards||You want to run depreciation calculations on several fixed assets for a single budget version.||Data Action or Multi Actions|
|Run data actions on multiple different target versions||You plan on multiple versions simultaneously and you want to populate all of them with initial data.||Multi Actions|
|Run data actions on multiple different target models||You need to copy data from a strategic planning model to multiple models such as workforce, sales, and finance models.||Multi Actions|
|Run a data action, publish data, and then run another data action||You want to copy initial data to a version, publish it, and then run an advanced formulas calculation on the version to prepare for planning.||Multi Actions|
How to create a multi action
Let’s use the second scenario mentioned at the beginning as an example. In this example: a user adds data in a table. They publish the data, but they also want to execute advanced formula logic (for example, increasing the amount by 10%) automatically.
Let’s assume we already created a data action with advanced formula logic. (Again, multi actions don’t provide the design time for individual components, but instead focus on logically bringing different components together into an end-to-end workflow.)
Step 1: Open multi actions and create a new multi action
Step 2: Add a version management step
Step 3: Add a data action step
(Tips: If you will be adding multiple data actions based on the same model and version, it is recommended to embed these data actions into a new data action first. You can then add the new embedded data action to your multi action to improve performance)
Step 4: Save the multi action
Step 5: Add a multi action trigger to a story
Step 6: Now…show time! Let’s see how multi actions work its magic.
Further enhancements are coming soon to make multi actions even more powerful
We plan to integrate many SAC components in multi actions, such as smart predict, model data import and export, data locking, etc.
I hope you enjoy working with multi actions and leverage this feature to improve the planning experience for your business users. We are looking forward to your comments and would love to hear which features you want to bring into multi actions next.