How to add two aDSO's to Composite Provider for planning

[former_member539392]

Hi Experts,

I'm working on report with a planning fuctionality. Now I stucked on an issue: I'm using two aDSO's (for fact and for planning) which combined by one Composite Provider. Further I've created an Aggregation level and after - query. aDSO's have the same structure (LocationID, ArticleID, BrandID) and have only one difference - first one aDSO have key figure "fact", second one - "plan". In a query I've made all the input ready settings for "plan" key figure and I expected to see in Analysis a possibility to input data. But Plan column is greyed and Planning panel on Excel ribbon also greyed. What I've missed? What wrong i've did?

Thanks, Alex.

[gregor_dieckmann · Accepted solution]

Hi Alex,

Erdem is right: the characteristics 0INFOPROV (and currency, unit characteristics) have to uniquely defined in input-ready cells. In your query you aggregated with respect to 0INFOPROV, this is why the cells are not input-ready. Restrict 'Actual Data' by the part provider used for actual data and 'Plan Data' by the part provider used for planning data. This is the standard way to model these kind of queries.

Regards,

Gregor

[gregor_dieckmann]

Hi Alexander,

here are some possible reasons

- query was opened in display mode (check in Design Panel, tab Components, DataSource setting: Planning: Open Data Source Input-Enabled

- planning provider is in load-mode (you should get a corresponding message)

- query view is aggregated with respect to aggregation level and no disaggregation setting is used

- bug, cf. notes 2710664, 2729461

Regards,

Gregor

[erdempekcan]

Hi Alex,

I'm sorry, I didn't notice your workaround was working.

I think you might have already tried but did you try to create a restricted keyfigure and filter the InfoProvider for actual and plan separetely?

[former_member539392]

Hi guys! You're awesome! Thank you very much, now it works!!!

As you suggested I added a restriction to each key figure (actual & plan) by a relevant infoprovides:

Many thanks again!

Alex

[erdempekcan]

Hi Alex,

You're very close to the result. There some "sneaky" options to set. Then everything should be fine.

Regards,
Erdem

[former_member539392]

Hi Erdem,

thanks for responce!

Actually I have that checkbox is already ticked so I think I made all "sneaky" tricks:) Seems to be some basic setting is missed.

Regarding Change/Display Mode - my planning ribbon is already on change mode, I can only switch to Display mode. Please see that on screenshot below.

Thank you,

Alex

[former_member539392]

Hi Gregor,

thank you for responce.

I've checked all the possible reasons which you propose above.

- query was opened in display mode (check in Design Panel, tab Components, DataSource setting: Planning: Open Data Source Input-Enabled

I have checked Start Query in Input Mode in a Planning window of Query. So the query should open for Planning (at least it works on another example when I have only one aDSO in Composite Provider):

- planning provider is in load-mode (you should get a corresponding message)

I've switched a aDSO to planning Mode (sorry for russian interface):

- query view is aggregated with respect to aggregation level and no disaggregation setting is used

if I understand you properly I have to do dissagregation settings directly for planning key figure. If I'm right - I did it:

- bug, cf. notes 2710664, 2729461

I don't think so cause I have working example with the same data model but with one aDSO in Composite Provider.

Today I'm looking for a solution and found something.

I left only planning aDSO as a restriction in a filter in Query and I've got a possibility to input data in Excel cells in Analysis. But I didn't see Actual data as expected due to filter restictions:

After recalculation I could save data - it works fine. But without Actual Data I think that kind of planning is incomplete for customer. Next I've add Actual Data aDSO to filter directly IN ALANYSIS and got the Actual data:

It looks like a workaround but I feel there should be another way how to implement it.

What do you think, gregor.dieckmann ? Hope it's not too much difficulty explained:)

Thank you,

Alex