SAP Data Modeler – Identifying CDS Views Compatible with OneConnect Modeler

SAP Data Modeler – Identifying CDS Views Compatible with OneConnect Modeler

The purpose of this manual is to provide a simple and practical guide to identifying CDS views within SAP that are compatible with the OneConnect Data Modeler. It outlines the necessary steps in a clear and concise manner, allowing users to quickly locate and validate views suitable for integration with OneConnect's data modeling tools.


Considerations to Identify Compatible CDS Views and CDS View Entities.

The SAP Data Modeler is compatible with the following CDS Views and CDS View Entities
  1. Standard Views
  2. Custom Views
  1. Private Views (prefix P_*)
  2. Interface Views (prefix I_*)
  3. Consumption Views (prefix C_*)

While identifying compatible CDS views, it is important to ensure the following condition is met:

  • The CDS view must not be contain the authorization #PRIVILEGED_ONLY in their Data Definition (@AccessControl.authorizationCheck: #PRIVILEGED_ONLY)
To ensure that the CDS View or CDS View Entity does not have the #PRIVILEGED_ONLY authorization restriction, you can follow these steps:

Step 1: Access Transaction SE11

In the SAP GUI, open transaction SE11 (ABAP Dictionary). This transaction enables you to view and explore table structures, as well as browse and query table data directly within the SAP system.

Step 2: Select Data Type

Select the "Data Type" option and type the name of the CDS View and click on "Display"

Step 3: Inspect the Content

Select the "Content" tab and in the Data Definition section for the CDS view, identify that the value of the parameter "@AccessControl: authorizationCheck" is not marked as #PRIVILEGED_ONLY.
Values such as #CHECK, #NOT_REQUIRED or #MANDATORY are acceptable.


Optional: Identifying CDS Views/SQL Views Names that are compatible with the SAP Data Modeler

In addition to using CDS Views directly in the SAP data modeler, it is also possible to use the SQL table names of each view, if one has been defined. The SQL table name can be identified by following these steps:

Step 1: Access Transaction SE16

In the SAP GUI, open transaction SE16 (Data Browser). This transaction allows you to browse and query table data directly within SAP.

Step 2: Search the DD02L Table

In the Table Name field, enter DD02L and press Enter. This table contains metadata for all transparent tables and views defined in the system, including CDS views.

Step 3: Apply Search Criteria

In the search criteria screen for table DD02L, configure the following fields:
  • Table Name: Enter a search pattern using the following format:
    I<Module>(Optional)*<EntityName>*
    This pattern helps narrow down the list to CDS views following a specific naming convention (e.g., I*CUSTOMER* to find views related to customers).


  • Table Category: Select the value "VIEW".
    This ensures that only view objects (not transparent tables or other types) are included in the results.


Click the Execute button (or press F8) to run the search based on the criteria provided. The system will return a list of all view objects that match the specified pattern and are categorized as "VIEW".
From the results, locate the desired CDS view by reviewing the entries and identifying its Table Name, which typically corresponds to the SQL View Name defined for the CDS view.


Step 5: Use the Table Name in OneConnect Data Modeler

Take the identified Table Name (SQL View Name) and enter it into the OneConnect Data Modeler exactly as shown.
For further guidance on how to use this view within OneConnect, please refer to the following manual.

For further support with modeling or configuration in OneConnect, please contact the Onibex team.
    • Related Articles

    • SAP Data Modeler - Entity Creation and Main Customizing

      Introduction This document provides a step-by-step guide for creating and configuring an entity within Onibex's SAP Modeler using transaction ZONT_ONECM. It outlines the essential processes, including selecting the appropriate domain and data type, ...
    • Onibex SAP Data Modeler - Functionalities

      Introduction The following table outlines key functionalities offered by the SAP Data Modeler, highlighting features designed to enhance data extraction, customization, and integration within SAP environments. No Function Description 1 Direct Data ...
    • OneConnect V2 SAP Manual

      OneConnect V2 SAP Integration The following manual configuration considers the fact that you have installed the version 2 of OneConnect in SAP, please make sure that you are using this version Install the Transport Install the transport request sent ...
    • SAP Data Modeler - Customizing Parameters

      OneConnect Parameter Adjustments The OneConnect solution includes a parameter table used for sending information—especially real-time data. It is important to configure this table beforehand, prior to sending any data, to ensure proper communication ...
    • SAP Data Modeler - Working with the entity "ANY"

      Introduction This document provides a step-by-step guide for creating and configuring an entity within Onibex's SAP Modeler using transaction ZONT_ONECM. It outlines the essential processes, including selecting the appropriate domain and data type, ...