Page tree
Skip to end of metadata
Go to start of metadata


In the following we discuss some technical details of a transient provider(and transient query) based on an ABAP CDS View. The delivered information(under Tips&Tricks) should help you to check/analyze such providers in case they do not work as expected.

General Information to this Topic


Identify objects for transient queries/provider based on CDS views


In RSRT by displaying the technical information important information can be gathered (see also CDS Naming Conventions):

The DDL source of the query is found under Query Definition: C_REVENUEFROMINVOICEQRY.

The transient provider (TRPR) and its DDL source can found under General Data: 2CISDBILLGDOCITMC and I_BILLINGDOCUMENTITEMCUBE.

With the report RUTDDLSSHOW2 in SE38 the definition of the query and provider can be displayed quickly also in the SAP GUI:

The query CDS view itself has no transient provider, so nothing can be found in transaction RSRTS_ODP_DIS for C_REVENUEFROMINVOICEQRY.

With the SQLVIEWNAME the transient provider can be idenitifed in transaction RSRTS_ODP_DIS:

  • TransientProvider 2CISDBILLGDOCITMC
  • Software Component: VDM_SD_ANALYTICS, 
  • SQLviewName: ISDBILLGDOCITMC 'Billing Document Item Cube'

The connection between DDLSOURCENAME and SQLVIEWNAME can also be found in table RSODPABAPCDSVIEW


Check whether query is run in the correct client

As described in the example of CDS Access Controls, when a query based on a CDS view is executed, the system automatically adds a filter with the client the user is logged onto. It is not possible to restrict a BW query based on a client dependent CDS View, on another client that the one the user is logged onto.

Check the restrictions derived by authorizations assigned to the user

If the authorization check is active for a CDS view (@AccessControl.authorizationCheck: #CHECK), the authorized values are added to the WHERE clause of the SQL statement. This can lead to unexpected query results, see CDS Access Controls for further details on how to check such queries.

Using TransientProviders based on CDS Views in Query Designer

TransientProviders based on CDS Views using the data category annotation #CUBE (@Analytics.dataCategory: #CUBE) can be opened using either the BEX Query Designer or the Modeling Tools Query Designer. This Wiki page explains where the technical names and descriptions shown in Query Designer come from and how it is possible to control this behavior.

Important SAP Notes and KBAs

2274570Performing the "DCL Initial Load"

SAP Online Documentation

  • No labels


  1. Is there any official guide as to how to create transient provider using ABAP CDS syntax? Esp. those ones that supports typical BW features like time-dependent navigation attribute, hierarchy, etc?



  2. Hi Shady,

    the following link to the online documenation gives an overview of all CDS annotaions, in particular also of Analytic Annotaions which can be interpreted by the Analytic Engine:

    CDS Annotations

    best regards,


  3. Hi Nora & Peter,

    There're two DDL sources in this sample. One is for query and the other is for TRPR; but it's also mentioned that CDS view has no TRPR.

    I guess the complete structure is not very easy to follow up. Could you please update with a grapical display in order to show the flow and connections?

    Thank you!

    1. Hi Erdem,

      a CDS view (C_REVENUEFROMINVOICEQRY  in our sample) with the @Analytics.query = true feature is no TransientProvider and thus not displayed in RSRTS_ODP_DIS.

      However, this query is based on another/second CDS view with the data category CUBE (in our sample I_BILLINGDOCUMENTITEMCUBE) which then actually has a transient provider 2CISDBILLGDOCITMC that can be displayed in the RSRTS_ODP_DIS. It can also be used to build regular queries in the Bex/Eclipse query designer.

      We will check how to simplify this page in the next few weeks!

      Thanks and regards,


      1. Hi Nora,

        I noticed that openning a CDS view by "Dependency Analyzer" or "Graphical Editor" is quite helpful. However, I'd like to see the relation between DDL, TRPR, SQLViewName for a better understanding.

        Thank you!