Integrating Data Import Job into Multi Actions

[SarauShen]

Introduction

As of today, data loading requires the work from IT.  You want to have some independence to load data into SAC with as little IT intervention as possible.
You want to use data loading (as data preparation) as the preparation of productive planning processes, which requires to orchestrate several steps: 1) load actual data into SAC, 2) forecast the budget, 3) allocate budget via data action, 4) and publish to Budget version. These steps usually should be executed sequentially and next step can only be executed when the previous step is completed successfully. You might need to run it regularly, but don't want to wait and then click separate buttons one by one.

SAP Analytics Cloud (SAC) introduced Multi Actions in the release of 2021.Q3, then integrated Predictive Scenario into Multi Actions in the release of 2022.Q1. In the release of 2022.Q3, SAC introduces a new feature Data Import step in Multi Actions, which enables user to control Data Import job in multi actions.
User now can organize data loading, predictive, data action and publish version within one multi action in a sequential way. End-user can execute multi action (which includes the sequence of different action steps) in story via multi actions trigger or schedule the multi action in calendar.

Scenario

In this blog, you will learn how to add data loading step into multi actions.
Assuming you are responsible to load actual data from other system to SAC, then generate predictive data into Forecast version, finally publish the Forecast version. You need to run this process every month.

Preparation before Multi Actions

Firstly, you need to create a data import job in Data Management of a model. I assume you are familiar with the creation of data import job. If no, refer to Import Data to you Model
Secondly, you need to create a predictive scenario. If you are not familiar with predictive scenario, refer to Predictive Scenario

Creating Multi Action

Now you have data import job and predictive scenario ready. It's time to create a multi action and integrate these steps seamlessly.

#1, open Multi Actions page, and create a new multi action.

 

#2, add data import step

There are 2 ways to add step in multi action:

1) add step from toolbar

or 2) add step from diagram

 

Select the model where the data import job is

 

Select the data import job from the job list of selected model

 

Data Import step is setup.

 

#3, add predictive step and version Publish step

For Predictive step, please refer to blog

For Version Publish step, please refer to blog

 

#4, save multi action

Now, a multi action containing data loading into SAC model and generating predictive data scheduled is ready.

 

Executing Multi Action

You are able to execute this multi action in story or calendar or analytics application.

Adding and executing multi action in story

If you would like to execute multi action in story interactively via one-click button, the blog explains how to add and execute multi action in story

Scheduled execution in Calendar

If you would like to schedule the execution of this multi action, then create a calendar task.
Assuming you would like to load data and generate predictive data on the 1st day of each month.

#1, open Calendar

 

#2, create a Multi Action task

 

#3, fill name for Multi Action task, set Start/End/Recurrence, and create this task

 

#4, after task is created, in the design panel, select the multi action

 

#5, save multi action task setting.

Congratulation, you now have the data loading into SAC model and then generating predictive data scheduled on the 1st day of each month.

Not supported

Parameterization

With multi action, user can set value dynamically during execution via parameters. However, data import step in multi actions doesn't support parameter.
For example, for data action step in multi action, assuming a parameter is created for Version dimension, end user can set target version dynamically when he/she executes multi action. For data import step in multi action, target version is defined in data import job as a fixed value, which can't be set by end user who triggers multi action.

Unsupported data source type

• Import Model From Local File is not supported


• Data import from Concur/ERP/Fieldglass/Dataset/SalesForce is NOT supported