Skip to Content
0

Source type of ODS view not supported in CalcScenario

Dec 01, 2017 at 12:20 PM

208

avatar image

Hi,

We have created a datasource with an ODP - ABAP CDS view and want to create an open ODS view (facts) based on this datasource.

All assignments to infoobject work fine, but upon activation we get the error

"Source type of ODS view <name of our ODS view> not supported in CalcScenario"

What is causing this problem and how can we fix this?

Many thanks in advance,

Eddy

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

avatar image
Former Member
Dec 04, 2017 at 01:34 PM
0

Hi Eddy.

Please check info regarding the limitations in the note 2198480 - FAQ: BW Open ODS View - Query Execution:

12: Consumption of CDS Views in Open ODS Views

An ABAP CDS View is a semantically rich ABAP Repository Object. This ABAP object creates corresponding artifacts on the HANA Database. The deployment of ABAP CDS Views implies a number of limitations that usually prevents the correct usage of the database artifacts within the Open ODS View.

  • ABAP CDS Views with Parameters: ABAP CDS view that contain parameters are not created as SQL-Views, but as a table function in the HANA Database. Table functions can not be consumed by Open ODS Views, and are also not supported by HANA Smart Data Access.
  • Client-Dependent ABAP CDS Views with annotation "ClientHandling" have an additional session variable available called CDS_CLIENT. This CDS_CLIENT can currently not be set for a Database user, instead it is set by the ABAP SQL interface. The Open ODS View can therefore not read data from another ABAP Client, nor via HANA Smart Data Access from another system.

To overcome the above mentioned limitations, it is recommended to consume remote CDS View with the dedicated BW Source System type ODP-CDS, which is available as of SAP BW 7.50 SP05. In addition, please apply SAP Note 2495379 in both the S/4 system as well as the target BW system.

Kind regards,

Andrey Farzatinov

Share
10 |10000 characters needed characters left characters exceeded
Eddy De Clercq Dec 08, 2017 at 02:57 PM
0

Hi,

Thanks for pointing that out. We are indeed using parameters, but that is more imposed by the fact that filtering on current date is only possible for the moment via params (see also

https://blogs.sap.com/2015/11/25/abap-news-for-release-750-environment-information-in-abap-cds/).

On the other hand, I don't fully understand what's said in the note. The CDS is on the same system but, despite that we are 'only' at SAP_BASIS level 750 SP03, resides already as a datasource in a ODP (ABAP) CDS view source system.

Furthermore, note 2495379 can't be implemented according to SNOTE, without giving a clear reason. I guess we need to implement the prereq. notes first.

Cheers

Eddy

Show 3 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Eddy,

do you use this scenario for the extraction or for the reporting?

in case you use it for the extraction you can directly extract data without Open ODS by ODP, in case you use it for reporting you can filter the data in the upper level(query)

Kind regards,

Andrey

0

Hi,

The scenario is that a CDS view reads infoproviders on the system data. An ODP - ABAP CDS Datasource is create. Based on this DS, an open ODS view is created. This open ODS is read by a Bex query, which is then used by a Webi report.


Cheers

Eddy

0
Former Member

Hi Eddy,

according to https://help.sap.com/doc/abapdocu_750_index_htm/7.50/en-US/abencds_f1_date_functions.htm:

It is not currently possible to access the current system date directly in a CDS view. Instead, a CDS view can be given an appropriate input parameter. The special annotation @Environment.systemField makes it possible to pass the value of the ABAP system field sy-datum to this parameter.

But that is only for 750

Also, there is a different way you can try:

https://archive.sap.com/discussions/thread/3771755

However, I would suggest creating variable on a Bex level, for sure that could increase memory consumption on a HANA level, but still worth trying.

Kind regards,

Andrey

0