cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Versioning in Analytic Data Model (SAC)

Artur3
Explorer
0 Likes
1,957

Hi All, 

I wanted to ask you if had a similar case or maybe you interpret guidence differently. 

I created an Analytic Data Model with Layout Measure in SAC. 

I created necessary dimensions, measures, calculations etc. 

One of the dimensions is Version. I defined this dimension, created relevant categories like Actual, Planning and Forecast. 

When the Data Model was completed, I decided to load the data via import from a file. 

I set up the import and I started preparing the data - according to documentation from SAP portal (Import and Prepare Fact Data for a Model with Measures | SAP Help Portal) I created Cateogry attribute which is relevant.

Artur3_1-1735909368051.png

The next step was "Map to FACTS". 
I noticed that the Version was automatically mapped to default value - Actual. I removed this assignment becasue I had Version defined in file which was imported so I finished mapping - everything finished successfully. 

Artur3_0-1735909171761.png

In step "Map properties" I was asked for Category assignment - I did it according to documentation from SAP portal. 

Artur3_2-1735909461592.png

This step was successfull as well.

The last step was validation before Import the data.
I received this notification:

Artur3_3-1735909626725.png

I went back to Mapping dimensions to Facts and removed mapping of the version. I assigned "default value" and I tried to validate once again. 

It worked without any notification. 

Can I understand that I cannot have more versions defined in Analytic Data Model even for Reporting purposes when I do not need planning activities? 

Perhaps I am doing something wrong that everything is fine until validation process. 
Have you had similar case? 

Versioning is very useful due to the calculations options available in the Story. Without that these options are not accessible.
I followed the information available on the SAP portal (link I shared above) but for me it's a bit misleading. 
In restriction section it's written that "There is only one Actuals in the model" and in the guide below it's mentioned that if we have multiple versions in the dataset we can assign these rows to multiple versions.

 

I would be grateful for your feedback.
Best regards,
Artur

 

 

 

 

Accepted Solutions (1)

Accepted Solutions (1)

Yogeshwar_M
Active Participant

Hi @Artur3 

I tried with same scenario I got same error as you mention "There is only one Actuals in the model"

But after changing version name in excel file as per version ID in model it works fine

1. Excel upload screenshot

Yogeshwar_M_0-1736172232733.png

2. Version Diamension

Yogeshwar_M_1-1736172361282.png

 

Yogeshwar_M_2-1736172600827.png

In below screenshot you need to be change Source ID should be same as Target ID.

Yogeshwar_M_3-1736172870000.png

 

Thanks.

 

 

 

Artur3
Explorer
0 Likes
Yes, this works. Thank you for the hint!

Answers (1)

Answers (1)

N1kh1l
Active Contributor
0 Likes

@Artur3 

I am not sure at what stage you got the error but Let me clarify few things.

You can have multiple versions Like Actual, Plan, Budget, Forecast in Analytic Model and also load the data to it. The restriction is that you cannot have more than one version with version category set as Actuals as shown below

N1kh1l_0-1736061962812.png

But As you can see I have a version called PL with category set as Planning and you can load data to this version without any issues.

While mapping the file just assign the version PL or any version which you have in your model as shown below.

N1kh1l_1-1736062131888.pngN1kh1l_2-1736062180600.pngN1kh1l_3-1736062219718.png

Hope this helps !!

Nikhil