SAC - Account Dimension with Multiple hiearrchy

[geeta2021]

Hello SAC experts,

In the FP&A stream always Account would have multiple hierarchies where as in SAC when we create Account it would accept only a single hierarchy. How to represent multi view on account hierarchy for planning purpose. Does any has any other solution which they have used in their project to represent this.

Thanks & Regards,

Geeta

[Former Member]

Thank you for visiting SAP Community to get answers to your questions. Since you're asking a question here for the first time, I recommend you to read this overview: https://community.sap.com/resources/questions-and-answers and to take our Q&A tutorial at: https://developers.sap.com/tutorials/community-qa.html.

With these tips you'll be able to prepare questions that draw responses from our members. The more details you provide, the more likely it is that members will be able to answer your question. Should you wish, you can revise your question by selecting Actions, then Edit. By adding a picture to your profile you encourage readers to respond: https://www.youtube.com/watch?v=46bt1juWUUM

Best,

Your SAP Community moderator

[geeta2021]

Hello Debjit,

Thank you . I saw that note . I know, I can use the GL Account as dimension but in a model it does not accept multiple account fields as this is restriction.

Measures are accepted as Account and it does not support multiple hierarchies. If I create as General Dimension then it does not acquired all Account dimension properties like Account Type, Exception , Formula etc. If I create these properties manually will that work similar way to account dimension properties need to be tested. I will test this.

I thought someone might have better option to support during design phase. I will try some options and see what are the results and update this msg .

Thanks & Regards,

Geeta

[DebjitSingha]

Hello geeta2021,

You can implement multiple hierarchy on GL account (Generic Dimensions). We have implemented similar scenario due to restriction and it is easy to implement with the data structure we receive from ERP system. Data structure from ERP/ S4 comes in GL based structure ( instead of Account/ measure based split). Data appears in multiple currencies from source system. Then at the reporting level different GL account and groups give transaction different meaning.

you can still apply restricted measures, exception, top n, hierarchical report setup etc. Not to mention Account Type can be left as a separate dimension or added as a property of GL Account dimensions (we left it as a separate dim as we are receiving this as part of ERP data extract) . In fact if you are consuming FI data from ERP/ BW/ S4 it is much more easier to use GL dim and subsequent hierarchical setup than transforming dimension data from source to measures/ SAC Accounts. Think about the amount of work required to transform a source data setup like this into account/ measure basted structure.

Let us know if you have any question around this topic? If not, appreciate if you up-vote and accept the answer helped you.

- Debjit

[DebjitSingha]

Good one.

At least now you know whom to follow and whom to avoid 🙂

[geeta2021]

Thank you Debijit. Our requirement is bit different where it would be difficult to use Account dimension as General Dimension as our data loads are Flat file loads and FI reports are bit complex because of the legal requirement.

Thanks & Regards,

Geeta

[DebjitSingha]

Thanks for your reply.

Usually you pick the answer poster earlier as “best answer” if they are on similar grounds or one have additional details compared to other. A bit odd...anyways!

Curious though - why flat files why not connect to ERP/ BW / BPC systems?
It would be better in terms of sustainability and support in long run.

If you have plans to connect SAC to one of the systems, then they must have GL Account concept and it would be easier to pull dats based on GL Account dimension based then creating Account dimension and then transforming source data. If you know what I am saying...

[geeta2021]

I am aware of GL Account concept. It was for Account Multiple hierarchies. Not always everyone would connect to SAP system. In case, in an given scenario flat file is must to be used ,then what?

Agree with the long term sustainability but that would be decided based on the architectural design and future roadmap of the client for which one is working for.

Thanks Regards,

Geeta

[DebjitSingha]

Not sure you understood my point. Your requirement of “multiple accounts hierarchy“ can easily be implemented using GL Account hierarchies. Your flat file setup will be more flexible ( multiple GL hierarchy) as well, keeping future transition in line. If your requirement demands multiple hierarchy, why stick to account setup , why not try some thing that is more flexible? Beside this will be one time setup, later on all you need is to reload your flat-file(via file server) and all your existing transformations will be be considered.

What I was trying to say, if you connect one of the SAP system in future then you will notice that it would be much easier to used multiple hierarchy on GL Account, than creating and maintaining account based / measure based hierarchy. Source data from SAP system do not comes in measure based hierarchy. Your setup then will require quite a bit of transformation. You can setup a common setup today so that if tomorrow you plan to connect SAP system you will have easy transition and you will be able to reuse your existing models and stories.

I understood your 2nd point, you may be in transition/ early phase of implementation.

Thanks,

Debjit

[regh76]

Hi Geeta,

As I could see, the only way to overcome this is to create the hierarchy manually in SAC on a public Account dimension and load it from the source, flat file or manually maintaining it in the master data hierarchy. I had the same issue, when tried creating a SAC data model based on a SAP BPC cube. It is mandatory to select the Account hierarchy when creating the data model and you must select the hierarchy from the source to load the data into SAC. When you want to load with the second hierarchy from the source, it will add the hierarchy master data under the same hierarchy column in SAC Account dimension, which causes huge issue and in principal is incorrect. It doesn't create another hierarchy column in in the SAC Account dimension.

Kind regards,

Reza Ghazvini

[William_Yu · Accepted solution]

Hi geeta2021,

SAP is working on this feature, it will be communicated once it's ready.

Best regards, William

[geeta2021 · Accepted solution]

Thank you William, if this is added then it would really add a value and user would be happy instead of hearing the limitation. Do you have any idea, when this would be ready - I know, I cannot ask more but just for the curiosity.

Thanks & Regards,

Geeta

[William_Yu · Accepted solution]

Hi geeta2021,

I don't have a detail timeline. The work already started.

Best regards, William

[former_member116555 · Accepted solution]

Hi William,

Do you have some news regarding this feature? its not only affecting SAC but due to this the AO feature is impacted. Looking forward to hearing from you

Regards

Nithin

[William_Yu · Accepted solution]

yes, it's release with 2022 QRC 1, check this blog post: https://blogs.sap.com/2022/02/02/whats-new-in-sap-analytics-cloud-and-sap-digital-boardroom-q1-2022/...