As of ABAP release 7.55, a new type of CDS view has been released: the CDS view entity. CDS view entities are an improvement over the “classic” CDS DDIC-based views.
For details, see:
Now, a new migration tool is available that automates many steps of a migration from a CDS DDIC-based view to a CDS view entity. But that’s not the only helper to facilitate a migration. The following support has been released:
Tool name | Technical name | Available since |
ADT migration wizard | ABAP 7.58 | ABAP Platform 2023 | |
Program that lists all usages of CDS-managed DDIC views | RUT_WHERE_USE_SQLVIEW | SAP Note 3201681 |
Program for migration analysis | RUTDDLS_MIGRATION_CANDIDATES | ABAP 7.56 | ABAP Platform 2021 |
Manual migration | ABAP 7.56 | ABAP Platform 2021 | |
Program for tool-based migration | RUTDDLSV2MIGRATION | ABAP 7.56 | ABAP Platform 2021 |
ADT migration wizard | ABAP quarterly release 7.91 |
This blog post first provides some general information about migration and then gives details on each helper tool.
Continued support for CDS DDIC-based views
SAP will continue to support classic CDS DDIC-based views. CDS DDIC-based views will not be retired, and customers will not be forced to use CDS view entities. SAP protects investments.
The following policies apply:
View entities are by design incompatible with DDIC-based views.
The advantages of CDS view entities can only be realized based on incompatible changes to the concepts and implementation of existing CDS views. The most prominent example is the deletion of the CDS-managed DDIC view, that means, the ABAP Dictionary view that is attached to each DDIC-based view. This DDIC view is deleted during a migration to a CDS view entity and all scenarios which rely on the DDIC view no longer work.
No automatic migration will take place.
During migration, semantics of a view might change. Because of this, each developer needs to decide whether they want to migrate their views.
Reverse migration
Reverse migration is not possible by yourself. If necessary, open a support ticket on component BC-DWB-DIC.
An ADT migration wizard is available as of ABAP 7.58 (on premise) | 7.91 (quarterly releases), which corresponds to S/4 release 2302.
It covers exactly the same steps and it processes the same rules as the migration tool RUTDDLSV2MIGRATION. It is also available for cloud systems, for example, Steampunk, Embedded Steampunk, and ABAP Cloud systems.
As a first step, you can create a new repository tree that lists all CDS DDIC-based views in a system as follows: right-click on a package and select Derive New Tree.
In the Derive Tree window, you can configure the tree:
Result: You have created a package that lists all CDS DDIC-based views.
Now you can select one or more of the views, make a right-click, and select Migrate to CDS View Entity ...
The migration wizard then guide you through the same steps as the migration tool RUTDDLSV2MIGRATION. See the section below for more details.
SAP Note 3201681 provides a tool that lists all usages of CDS-managed DDIC views in ABAP coding. Using CDS-managed DDIC views has been declared obsolete since ABAP release 7.56. If CDS views are migrated to CDS view entities, the corresponding CDS-managed DDIC views are deleted and all objects that use these CDS-managed DDIC views get error messages. This tool helps in adapting your coding to be prepared for CDS view entities.
When planning a large-scale migration of many views at once, all usages of CDS-managed DDIC views should be replaced by the name of the CDS view as preparation.
Tool name: RUT_WHERE_USE_SQLVIEW.
Since ABAP On-Premise Release 7.56, an ABAP program is available that evaluates whether a migration from a CDS DDIC-based view to a CDS view entity is possible:
RUTDDLS_MIGRATION_CANDIDATES
You can select DDLS sources to be analyzed directly by name or indirectly by original system, person responsible, package, and so on.
As a result, all DDLS sources specified are classified into one of the following categories (column Overall Status):
Moreover, details on the sources of the errors are provided. Currently, the following aspects are checked for each migration candidate:
For more information on an error, including how to solve it, select an error category and click F1.
Video clip that demonstrates the migration analysis tool:
Since ABAP 7.56, ABAP Platform 2021, manual migration from a CDS DDIC-based view to a CDS view entity is supported. To perform a manual migration, follow these steps:
A migration tool is available since ABAP 7.56, ABAP Platform 2021:
RUTDDLSV2MIGRATION
The migration tool automatically performs many adjustments that are required for a migration and creates an inactive version of the migrated DDLS. It also includes many checks and in case of issues, indicates which lines of the migration candidate must be changed before a migration is possible. The last step of the migration – the final activation of the CDS view entity – must be done by the developer.
When using the migration tool, follow these steps:
The migration consists of four phases:
Note: To see the embedded help, double-click on one of the prechecks.
The same checks are performed as with the migration analysis report RUTDDLS_MIGRATION_CANDIDATES. See the explanation above.
The tool provides an overview of the differences between the CDS view before the migration and the CDS view entity after the migration. It also gives feedback on each phase and indicates errors that must be solved manually (if applicable).
5. Activate the view entity.
The following list explains the rules that are applied to a CDS view to turn it into a CDS view entity in chronological order:
Video clip that demonstrates the migration tool:
Keep in mind: Migration is voluntary and “classic” CDS DDIC-based views are still supported, but not further developed.
You are welcome to leave comments and ask questions right here.
Official documentation of the ADT Migration Wizard: Migrating CDS DDIC-Based Views to CDS View Entities | SAP Help Portal
Embedded help of the migration reports:
Blog posts about CDS view entities:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
13 | |
11 | |
10 | |
9 | |
7 | |
7 | |
7 | |
7 | |
6 |