This repository contains several packages. Each package contains sample code snippets (ABAP, CDS, SQL) that has been presented in various educational online sessions.

• ABAP SQL – the art of accessing data
• A new generation of CDS views - CDS view entities
• Why aren't my tests stable? Test Isolation with the ABAP Unit Framework
• ABAP RESTful Application Programming Model - Fundamentals (planned)
• ABAP RESTful Application Programming Model - Entity Manipulation Language (planned)

In general see the requirements document for Workshops about the ABAP RESTful Application Programming Model (RAP).

For specific requirements see the readme documents that are part of the aforementioned packages.

Download the ABAP Development Tools as described here.

Import the source code either using the ABAPGIT report into on prem system or use the ABAPGit Plugin of ADT to import it into a Steampunk system.

Create a package (e.g. ``TEST_DSAG01orZ_DSAG01`) where the package name must not exceed 11 characters since the package uses prefix folder logic.

The package contains the examples / demos which have been demonstrated during the talk. The package can be installed with abapGit. After the installation you should be able to find the YBW_* classes and tables in your system. Please note that you need to load data into the YBW_... tables before executing the examples will produce valuable results. Data can be loaded by executing class YBW_LOAD_DATA in your ABAP in Eclipse editor. Just load the source code of the class with STRG+A. You can now execute the program by hitting the F9 key.

Session part 1:

• YBW_JOIN
• YBW_UNION
• YBW_INTERSECT
• YBW_EXCEPT
• YBW_CTE
• YBW_TIPPS0
• YBW_TIPPS1
• YBW_TIPPS2
• YBW_TIPPS3

Session part 2:

• YBW_WINDOWING0
• YBW_WINDOWING1
• YBW_WINDOWING2
• YBW_WINDOWING3
• YBW_WINDOWING4
• YBW_WINDOWING_ABAP
• YBW_CHAR_TO_NUMC_1
• YBW_CHAR_TO_NUMC_2
• YBW_CHAR_TO_NUMC_3
• YBW_CHAR_TO_NUMC_4
• YBW_CHAR_TO_NUMC_5
• YBW_CHAR_TO_NUMC_6
• YBW_TIPPS4
• YBW_TIPPS5
• YBW_TIPPS6
• YBW_CANDIDATE_MANAGER

The package contains the examples / demos which have been demonstrated during the talk. The package can be installed with abapGit. After the installation you should be able to find the Z_* CDS views and CDS tuning objects in your system.

Contents:

• z_classic_view: CDS DDIC-based view
• z_view_extension: CDS view extension
• z_demo_no_1: CDS view entity
• z_view_entity_extension: CDS view entity extension
• z_demo_entity_buffer CDS view entity for buffering
• z_demo_calculated_quantity: CDS view entity, demo for calculated quantity

Content (to be created manually):
A CDS entity buffer is a new kind of repository object of the technical type DTEB. This type of object is currently not supported in abapGit. To get the demo that was shown in the talk, proceed as follows:
• Right-click on the CDS view entity z_demo_entity_buffer and choose New Entity Buffer. • Insert a name, for example z_demo_entity_buffer, and type a description. • Paste the following source code:

define view entity buffer on z_demo_entity_buffer
       layer core
       type generic number of key elements 1
       

• Activate the entity buffer.

The subfolder src/test_isolation contains the examples which have been demonstrated during the presentations at DSAG and the global user groups. It will be also enhanced once there are new test frameworks available.

The idea of this folder is to show how to use any test environment, helper class and some common design patterns that help with isolating your code under test from its depended-on components.

If you want to isolate your code under test from the components it uses, you need to take a look at what your depended-on component is. Each isolation technique for a specific kind of depended-on component is used separate test class of the global class ZATI_CL_CODE_UNDER_TEST. The table below shows which test class uses which tool to isolate against which kind of depended-on component.

There are no known issues.

Create an issue in this repository if you find a bug or have questions about the content.

For additional support, ask a question in SAP Community.

If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.

Copyright (c) 2022 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.