How to use different versions of planning in a planning model in sap analytics cloud?

[jlopezm]

Hello SAP Analytics Cloud experts.

I'm stuck on something that I'm sure is idiotic, but I can't seem to figure out how it works.

I've watched hundreds of tutorials and videos where they explain how to use Planning versions within stories, but I can't get to the point of understanding how to load data in different versions or how to have them available in a model. When I create the model and then add the rest of the dimensions I only have Actuals available. And I can't add any of them.

If I delete the dimension table to create it again I get the “option” to create a new category, but it does not let me and I get the message: “only available if at least one source dimension exists”.

In the stories I create, the Version History option is always disabled.

I have tried, in the Import Jobs, to do data loads by selecting the version, but it never lets me choose any other than Actuals.

How can I use the versions in my models?

Thank you very much!!

[Mastan · Accepted solution]

Hi 

When building a model from scratch, starting with an empty model will automatically generate a version dimension containing only "Actual" as a member. If you delete this dimension table and attempt to create a new one, you'll find that it still restricts you to entering only the "Actual" member. This behavior is well-known and expected within SAC.

To include other versions such as Forecast or Planning, you have two methods:

1. Utilizing stories
2. Importing data into the model

For the first method:

Begin by creating a blank model according to your needs and then craft a story with a table widget. Utilizing version management within the story, you can then create additional versions (such as Forecast or Planning).

For the second Method:

To maintain the data integrity, ensure that the category property in the source corresponds to the version dimension. When importing the data, map the category appropriately. This process will generate additional versions within the model.

Hope this helps!

Best regards,

Mastan

[jlopezm · Accepted solution]

Thanks for the answer, the problem I had (which was solved, but I still don't know how) is that the option to use version management was not appearing in the history, with all the necessary permissions, selecting a table, etc. Likewise, the second option to load data I didn't know exactly how it worked, so thanks for the answer.