on 07-04-2018 6:01 AM
We are trying to decide between Key-figure & Account model for a CO-PA based gross-profit planning.. The planning will be at a higher level than SKU (Category equivalent).
1) Key figure model = 40 Key figures X 18 Periods X 10 versions X 3 years X 500 (Sub categ) = 270K rows in the DSO (direct update) , every time user enters a layout - they are likely to bring about 18 periods X1 version X 100 (Sub categ) = 1,800 rows
2) in the Account model = 40 Accounts X 7 Key figures X 18 periods X 10 versions X 3 years X 500 (Sub categ) = 10 MM rows. For user-session = 18,000 rows (10X key figure model)
We are leaning towards key-figure model as we expect the planning functions and layouts to perform better, but aDSO-direct update keyfigure model will lock-all key-figure & if we use aDSO-cube-like for Key-figure model- zero elimination is not supported. Business would like account-model as they can add new accounts without IT having to go-in and change the DSO every time they need a new key-figure
Would like to get your opinion/ any experience you can share , I came across an old BPS note, not sure if all the arguments apply to BW7.5Sp10 on HANA + AO 2.6
thanks
arvind
Just bear in mind that CO-PA going forward in S/4 is account based, so keeping your planning model account-based would simplify data comparison, master data usage, retraction (if any)... Without to mention that maintenance would be easier - for instance, adding a new account is way easier task than adding a new KF, considering your whole model objects: key figures, aDSOs, composite providers, aggregation levels, queries, workbooks...
Although volume is an important aspect of your decision, it would start to make a real impact in extreme cases where you have a very, very high volume (hundreds of millions) per process.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Arvind,
it's an old topic so here's a good old piece of documentation:
The general pros and cons still apply today but as Cornelia already wrote, there's no general best option.
Best,
Marc
SAP HANA Competency Center
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Arvind,
there is no general answer to this and in certain ways it´s a matter of personal preference.
I prefer account model - especially for data that comes from CO. from my point of view it´s more flexible.
account model is easier for some planning functions - on the "account char" you can set filters and / or conditions. If you use KF model, in many functions you have to specify the KF but it´s not flexible enough so you will define more functions for special purposes.
also standard copies can not be done between different key figures.
the point about "we can add new accounts without asking IT" might still not be so easy in planning - there functions and filters might still not select the newly created accounts, but even if IT will be doing it, I think it´s easier to do changes.
for the DSo to use - DO NOT use the direct update DSO for normal planning of KF that can be aggregated. These DSO need to have all char in key (or they need to be filled by derivation) and all char need to be filled with something different than #. This does not work for planning, or at least not for what I consider planning...
use the cube like DSO for this.
regards
Cornelia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you everyone.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Cornelia,
Thank you for your inputs. I agree that filters will be easier with account model - especially ability to lock different accounts during save.
The issue with cube-like-aDSO is "Zero elimination" is not yet supported. Each time you save, it will create a TSN & the volume in aDSO will grow.
Fortunately in our case, we will be able to fill all the key-fields in every planning scenarios i.e they will always plan by Sub-category & we will use nav-attribute brand for reporting
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
15 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.