Show TOC

Create a DDL Source for CDS View Locate this document in the navigation structure

Prerequisites

You need the standard developer authorization profile to create ABAP development objects.

Context

A DDL source represents an ABAP development object used to define an ABAP CDS entity (for example, a CDS view). With the DDL source you have the appropriate development object for the CDS view, which you can use to directly access the standard ABAP Workbench functionality, such as syntax check, activation, or connecting to the Transport Organizer.

Procedure

  1. Launch the ABAP Development Tools.
  2. In your ABAP project, select the relevant package node in the Project Explorer.
  3. Open the context menu and choose Start of the navigation path New Next navigation step Other ABAP Repository Object Next navigation step Core Data Services Next navigation step DDL Source End of the navigation path to launch the creation wizard.
  4. In addition to the Project and Package, enter the Name (with due regard to your namespace) and the Description for the DDL Source to be created.
    Note

    The maximum length for names of DDL sources is 30 characters.

    First wizard page when creating a DDL source
    Figure 1: First wizard page when creating a DDL source
  5. Choose Next.
  6. Assign a transport request and choose Next.
  7. Select the Define View template to speed up the view definition.
    Selecting template for CDS view with single data source
    Figure 2: Selecting a template for CDS view with single data source
  8. Choose Finish.

Results

In the selected package, the ABAP back-end system creates an inactive version of a DDL source and stores it in the ABAP Repository. As a result of this creation procedure, the DDL source editor will be opened. The generated source code already provides you with the necessary view annotations and adds placeholders for names of the Dictionary SQL view, the actual CDS view, and for the data source for query definition.

The generated template code in the DDL editor
Figure 3: The generated template code in the DDL editor