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

ADSO as BPC Model in BPC Web Admin

Former Member
0 Kudos
667

Hi All,

We are working on a brand new BPC 10.1 Embedded environment. And in DataWarehousing workbench, I have ADSOs (of type Planning) and Real Time InfoCubes. I even created Aggregates on both ADSOs and Real Time InfoCubes. However, when I was trying to create a Model in BPC Web Admin client, I do not see ADSOs as an option. All I can see is Real Time InfoCubes as an option to select as BPC Model. I am just curious to know whether there are any additional settings to be done so that I can see ADSO also as an option.

SAP BW System details:

SAP_BW 757 SP03.

Looking forward for your response.

Best Regards

Vijay Nandipati

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member196060
Contributor
0 Kudos

You need to be on BW7.5 as per note 221530. Assuming you are on NW7.4 with BPC 10.1 embedded, right?

PavelRamanouski
Participant
0 Kudos

Hello all!

About two weeks ago, I create SAP ticket about mentioned issue. I asked, whether aDSO must be availble for model creation in BPC web-client or not. And I got answer from SAP: "No, this is by design".

P.S. We have BW 7.5 SP03

Former Member
0 Kudos

Hi,

SAP BW 7.5 SP04 - I can choose an aDSO as InfoProvider.

Also the local querys are working on the aDSO provider.

Regards

Former Member
0 Kudos

May be helpful.....

Refered from above blog....

Beginning with 7.50 SP0 it will now be possible to use cube like aDSO for planning (flag ‘All Charachterisitcs are Key, Reporting on Union of Inbound and Active Table’ is marked).  As for real time cubes we have still limitations which are limited to planning only and not to general use cases in reporting and WhM. Therefore they are still allowed in the general modelling of an aDSO but not in context of planning. Those are


  • the flag ‘All Characteristics are Key, Reporting on Union of Inbound and Active Table’ is marked
  • all characteristics have to be mapped to BW info objects
  • InfoObjects cannot be of high cardinality
  • stockcover is not supported
  • constant target should not be filled

The rest of the modelling of the planning artifacts is also very similar to the cube.For example in:

  • RSPLAN: You can also use aDSO flagged for planning like a cube as base provider to create aggregation levels on top or to assign CRs
  • In transaction RSA1 you switch ‘load behaviour’ between planning and staging
  • In process chains we adapted the existing variant for cubes to support also aDSOs

The rest is as usual. With 7.50 SP0 we do not yet support the HANA optimized runtime with PAK but this will come with 7.50 SP1. It is also planned to support direct update like aDSO in a following support package.

Regards,

JP

former_member186338
Active Contributor
0 Kudos

Just for the same:

Former Member
0 Kudos

Vadim,

If I understand correctly, what you are saying there is no setting that we have to do and ADSOs are not an option to define as BPC Model. If this is correct then I have to live with Real Time Infocubes otherwise I cannot liverage  Work status or BPFs.. functionalities..

Best Regards

Vijay Nandipati

former_member186338
Active Contributor
0 Kudos

I am saying nothing Just pointed to the discussion a few days ago...