ABAP Cloud Developer Trial 2025

Assuming Docker Desktop is running on your WINDOWS OS machine installation can be performed from web browser at hub.docker.com site:

https://hub.docker.com/r/sapse/abap-cloud-developer-trial/tags

Click at docker pull command opens the docker desktop itself. Here confirmation of image pull and run operation needs to be done.

After approximately 1 hour (in my case quite old machine with intel i7 CPU and SATA hard drive) icon of Run image is enabled in the docker Desktop.

After clicking on the run assign container name e.g. A4H and hit Run button again.

Notice that your host OS machine name has to be vhcala4hci. If that is not the case the image won’t run.

Once the container runs you should see something like below in its log:

Then just open SAP GUI, SAP HANA Studio (Eclipse) or Visual Studio Code and log into the ABAP Cloud Developer Trial 2025. You can use following credentials for user DEVELOPER (password ABAPtr2025#SP00). Afterwards you can create your own user.

In closing I would like to thank whole team at SAP that delivered this trial edition. After sudden announcement of unavailability of ABAP Cloud Developer Trial on Docker - all versions in February 2026 this edition was very much awaited.

 

Useful links:

Official ABAP Cloud Developer Trial 2025 announcement

ABAP Platform Trial Image FAQ

T-code RSDSD - DataSource Documentation

There is t-code RSDSD available in BW system dated back to year 2005. That was a time when BW 3.x was the king of data ware house market at SAP shops. The t-code was probably created even in BW’s version 3.0B.

The description of the t-code says DataSource Documentation. However, functions that it covers never made it to mainstream usage. From observing the t-code it is dare to say that its functionality is to display, check, and generate technical documentation for DataSources directly within the SAP GUI. Knowledge Warehouse (KW) API are used to store the documentation by generating so called doculinks. As per the KW terminology these are so called Information Workbench (IWB) objects.

Also seems that the tool was originally meant for SAP internal use only. I judge this as the code of the t-code is checking whether the BW system type is SAP or CUSTOMER one (by a call of FM TR_SYS_PARAMS). If the system type is set to CUSTOMER the t-code even doesn’t bother to start.

S416* suite of data browser related t-codes in BW system

In my last post I wrote about a suite of Data Browser related tcodes. Those SE16* tcodes exits in SAP systems that runs on S/4HANA Foundation such as SAP S4/HANA. This is because they are part of software layer SAP_APPL  or SAP_FIN. However, the tcodes mentioned were ported to other software layer - SAP_ABA. Thus, are available in BW (as well as SCM, CRM, Solution Manager, etc.)  systems as well.

What is different is actually the particular tcodes it self. In S/4 they follow SE16* but in other systems they follow S416* or S4H16* names.

SAP_APPL name	corresponding SAP_ABAP name	description
SE16N	S416N and S4H16N	GTB
SE16H	S416H and S4H16H	Enhanced GTB
SE16D	S416D and S4H16D	GTB Display Mode
SE16S	S416S	GSS
SE16S	S4H16S	GSS Multi Text
SE16SL	S416SL	GSS Column Based
SE16SL	S4H16SL	GSS Depend Read
SE16N_ROLE	S416N_ROLE	GTB Role Maintenance
SE16J	S416QL	GTB Query Launcher
SE16S_CUST	S416S_CUST	GSS: Maintenance of Search Patterns
n/a	S416S_DEP	GSS: Maintenance of Dependencies
n/a	S416CD	GTB: Display Change Documents

 

GTB stands for Generic Table Display

GSS stands for Generic Smart Search

 

More information:

2140828 - GTB: Documentation of generic table display functions

1636416 - CO-OM tools: Functions of transaction SE16H

2124497 - Downport of the SE16* transactions to the software layer SAP_ABA

 

S416CD               GTB: Display Change Documents

S416D                Generic Table Browser Display Mode

S416H                Enhanced Generic Table Browser

S416N                Generic Table Browser

S416N_ROLE           GTB: Role Maintenance

S416QL               GTB: Query Launcher

S416S                Generic Smart Search: Text Input

S416S_CUST           GSS: Maintenance of Search Patterns

S416S_DEP            GSS: Maintenance of Dependencies

S416SL               Generic Smart Search (column based)

S4H16D               Generic Table Browser Display Mode

S4H16H               Enhanced Generic Table Browser

S4H16N               Generic Table Browser

S4H16S               Generic Smart Search: Multi Text

S4H16SL              Generic Smart Search: dependent read

SE16* suite of data browser related t-codes

T-code SE11 and SE16 was here for ages within every SAP Basis/NetWeaver/ABAP Platform based SAP system. The very basics function of the SE16 was to browse for the data in the tables, views. With an SAP S4/HANA system there were a new t-codes delivered related to data browser.

SE16*

SE16T – Umbrella t-code from where the others can be ran.

SE16N – Comprehensive version of SE16, enables selection criteria to be specified immediately upon request, output is in the ALV Grid, etc. In a nutshell more convenient for the user.

SE16N_EMERGENCY – Allows editing data in the tables.

SE16H - HANA DB optimized table display and analysis. Has more less same features as the SE16N t-code. Enables analysis on how table entries are distributed across specific fields.

SE16J – Dedicated SE16* t-code for table joins. Allow making a database joins (query data with joins).

SE16S - Generic table and value search. E.g. in case a search in DB tables needs to be performed on multiple tables.

SE16S_CUST – Allows to setup predefined searches for t-code SE16S.

SE16SL - Searching content.

Side note: SE16S and SE16SL can be used to find any values in any tables. Difference between them is how the selection is done. A search term is sought in all tables in SE16S, the search in SE16SL is limited to the found tables that match the entered field description. That makes SE16SL is theoretically faster.

TAANA - Detailed table analysis for functional tables. Covers scenarios like: record count, record distribution per time period (e.g. year), company code, plant, document type, any other business related objects.

KOBJ - used to search for any objects in any tables.

KTABL - i used to search for tables and table names.

KTRAN - used to search for transactions.

 

More information:

1636416 - CO-OM tools: Functions of transaction SE16H

3529563 - Functions of transaction SE16J

2002588 - CO-OM Tools: Documentation for SE16S, SE16SL, and SE16S_CUST

ABAP Program to report on DTPs - RSBK_DTP_PROPERTIES

ABAP program RSBK_DTP_PROPERTIES is a standard program in BW  used to analyze and retrieve various properties related to Data Transfer Processes (DTPs).

 

Here are some details about the DTP properties the program deals with:

1. Retrieving DTP Properties in Bulk:

   - The report fetches and displays various technical properties of one or more DTPs.

   - It allows administrators to interactively check DTP-specific settings across a system.

2. Supporting Operational and Debugging Tasks:

   - You can use this program to troubleshoot data transfer issues by verifying the settings of related DTPs.

   - It helps in scenarios where a specific DTP is not performing as expected, such as issues in extraction, transformation, or loading (ETL).

3. Custom Analysis and Automation:

   - Developers can use ABAP enhancements or custom versions of the report for bulk analysis, monitoring, or automation of property adjustments.

4. Useful in Migration or Upgrade Projects:

   - During upgrades, migration, or system consolidation, this report can help identify and document all DTP properties to ensure consistent configurations.

 

The DTP properties retrieved vary depending on the system setup and DTP configuration. However, here are some important properties included:

1. General DTP Attributes:

   - DTP Technical Name and Description

   - Source and Target InfoProviders

   - Extraction Mode (`FULL`, `DELTA`, etc.)

   - Activation and Deletion Flags

2. Execution Settings:

   - Data Extraction Mode (e.g., `Serialized`, `Parallel Processing`)

   - Maximum Parallel Processing Options (Number of Processes/Packages)

   - Error Handling Settings (e.g., `Terminate After n Errors`)

3. Filter and Transformation Details:

   - Active Filters and Filters Fields

   - Associated Transformations (e.g., Start Routine, End Routine)

   - Semantic Key Settings

4. Error Handling:

   - Settings related to error handling, such as error handling mode (`No Reporting for Errors`, `Request Green After Errors`, etc.).

   - Error Stack Activation and Management Parameters

5. Monitor and Logging Details:

   - Log Retention Settings

   - Update Mode (`Insert`, `Overwrite`, etc.)

6. Special Runtime Properties:

   - Runtime Modes

   - Data Package Sizes

   - Threshold Limits for Data Records

 

Program selection screen:

Program output: