cancel
Showing results for 
Search instead for 
Did you mean: 

Transient BEx query is invisible on CMC

Former Member
0 Kudos

Hello all,

I created CDS views with annotations as such:

1. Private view:

@AbapCatalog.sqlViewName: 'zcds_hier_p_M'

@ClientDependent: true

@AbapCatalog.compiler.compareFilter: true

@EndUserText.label: 'Private View for Hierarhcy'

@VDM.viewType: #BASIC

@Analytics.dataCategory: #DIMENSION

@Analytics.dataExtraction.enabled:true

@AccessControl.authorizationCheck: #NOT_REQUIRED

2. Interface view:

@AbapCatalog.sqlViewName: 'zcds_hier_I'

@ClientDependent: true

@EndUserText.label: 'Interface view for Hierarchy'

@AccessControl.authorizationCheck: #NOT_REQUIRED

@Analytics.dataCategory: #CUBE

@VDM.viewType: #COMPOSITE

@Analytics.dataExtraction.enabled: true

@Hierarchy.parentChild: [{name: 'Organization', recurse : {parent: 'Manager', child: 'name'}}]

3. Consumption view:

@AbapCatalog.sqlViewName: 'zcds_hier_c'

@ClientDependent: true

@EndUserText.label: 'Consumption view for Hierarchy'

@Analytics.query: true

@VDM.viewType: #CONSUMPTION

@Analytics.dataExtraction.enabled: true

@AccessControl.authorizationCheck: #NOT_REQUIRED

The architecture is as follows:

The consumption view 'zcds_hier_c' selects data from the interface view 'zcds_hier_i'.

The interface view 'zcds_hier_i' selects data from the private view 'zcds_hier_p_m' and the transaction table 'ztransactions'.

The private view 'zcds_hier_p' selects data from the master table 'zemployees_all'.

Both the table 'ztransactions' and 'zemployees_all' are custom development tables.

I was trying to test CDS annotations for Hierarchy, and I was hoping to see the analytics query from the BI client with those configurations above.

But what I see is the infoProvider of the Interface view '2CZCDS_HIER_I' and the other infoProvider of the Private view '2CZCDS_HIER_P_M'.

That's all and I cannot find the transient BEx query of the Consumption view '2CZCDS_HIER_C', which I was hoping very very much to see.

Are my annotations wrong? Or is there anything I should do with the custom tables if I want to expose a query with the data from those tables?

Or any other things that I should care about?

Anybody's helping hand would be really really appreciated...

Thank you very much in advance!!!

Bests,

MJ

Accepted Solutions (0)

Answers (1)

Answers (1)

János_at_SAP
Advisor
Advisor
0 Kudos

Hi Mj,

Check SAP KBA 1352535, you need to enable the Acces to the Quey by OleDB/OLAP engines.

BR,

János

Former Member
0 Kudos

Hi Janos,

but I thought the annotation "@Analytics.query: true" is supposed to expose the transient BEx query, which SAP analytic managers can consume. Isn't that true?

Because:

     1. transient BEx query should literally mean that it is a QUERY, not an INFOPROVIDER. So that this doesn't really have to go through another layer called "Query Designer".

     2. Out of a number of analytic CDSes that I have made, some of them actually succeeded in exposing a BEx query, so they could be consumed from BI tools like Design Studio. On the other hand, the rest of the analytic views failed to create BEx queries so they are not seen from CMC or Analysis Office, etc.

So until now, it just feels like a random process that sometimes, the CDS makes BEx query but in the other times they don't .

Another point that I think it gives some kind of a hint is attached here as a picture.

I searched the table "RSRREPDIR" which contains metadata of any kinds of report, and found that the record is a little strange.

As you may see here, COMPUID and COMPID of the strange record has an exclamation mark before its name. On another customer site, I even found such records with two exclamation marks. As far as I know, this kind of record means that this report is not created on the BEx query but is directly created on an InfoProvider. But in the other times, the records didn't really have any errors, you know.

I really wanna know the exact process and steps of exposing BEx query from a CDS view, but it seems like that lies very far from my side...

Thank you,

MJ

János_at_SAP
Advisor
Advisor
0 Kudos