SAP Community - SAP BTP, ABAP environment

Free SAP BTP - Free ABAP System instance

2025-04-01T10:50:57.011000+02:00

This article will show how you can create a Free ABAP environment.

After all, run the SFlight loading ABAP program to load data into the Hana database tables.

To accomplish all these and you can follow without fear, it will have a lot of print screens, so, long article.

At your Global account level, select the Boosters section.

In the filter, search for ABAP:

Calm down!! 🧘, I know you want to click on "Prepare an Account for ABAP Development (Free-tier)" but, there is a requirement for SAP BTP ABAP Environment, "Landscape Portal".

We need to create it first, selecting the "Landscape Portal for SAP BTP ABAP Environment (Free-Tier)".

We will hit 2 or 3 walls, sending us back a few steps, but I will help with screens shots!

Click on the tile, it will open a section showing the description, components, resources, bla bla bla... Press the start

In the coming screen, the booster will check settings a permission, it should show up like below:

If it is not like mine (all green and done), follow the instructions on how to fix the authorizations and entitlements and come back here.

Clicking NEXT should show a screen like this one.

NOTE: If you want to create it manually without using the Booster, notice this trick.... the landscape portal not shows up in the list of entitlements!! in order to show up in the list, you need to edit the entitlements and add it.

After the deployment finishes, now it is time to create ABAP instance. Go to Global account and select boosters, then filter by ABAP. Click on tile "Prepare an Account for ABAP Development (Free-Tier)"

After you read all info (Overview, Components,Additional), click on start. If there are some Authorization or Entitlements missing, fix them first. ( the entitlement error can be fixed adding it like shown up in the manual creation of Landscape portal)

In the next screen, we already created the Subaccount, so, don't need to create new one.

select proper Subaccount and space. Next screen is auto explanatory.

Choose the ABAP system id and review your choices.

The creation will take a few hours, it's normal / common. Stay calm 🧘 and after it finishes, you will receive an email like this one.

Congratulations!! 🎊 Now you have your personal ABAP Cloud Environment (the best of it, it's FREEEEEEEEE)

RAP: Augmentation

2025-04-03T15:48:59.320000+02:00

Augmentation:

used to enhance the modify request, before it reaches transactional buffer.
augmentation is available for projection bdefs only.
the augment methods are called before the create, update method.

Note:

it is not possible to set a field in augment which was already set for the original instance. For example, values set in the original request cannot be changed. Only fields which are unset in the original request can be added.
it is not possible to set fields in augment that are defined as read only .

The following operations can be augmented:

create
update
create by association

ABAP EML - MODIFY AUGMENTING ENTITY:

In the augmentation method, it's not recommended to use read, modify eml, as the data has not been moved into the transactional buffer yet. so we need to use a special variant of modify entity, entities, which is only possible in the context of projections bo.

for the eml statements, no response parameters can be specified, i.e., the additions failed, mapped, or reported cannot be used.
an abap eml modify statement using the addition augmenting must not overwrite fields of the original request. if done, a dump will be thrown.

Flow of augmentation method in interactive phase:

Difference between augmentation and determination:

Both Augmentation and determination are similar concept, as both are used to modify the request based on some standard trigger condition. But here are some differences.

Steps to develop precheck:

1. Add precheck in standard operation in bdef projection.

2. Implement the logic for precheck in abap behavior pool.

Use case:

Requirement: If the user doesn’t provides value for field “name”, Then it should be assigned with an default value “test”, in modify request.

To achieve this, we have added a augmentation in the update operation. Before executing the update method, the entry will beassigned with default value in augmentation method. In the Augmentation method, If the name is empty, we fill default value name using modify augmentation eml.

Code for augmentation in abap behavior pool:

Entities importing parameter:

Reference table for augmenting:

Connecting Multiple Databases and OData Services to SAP BTP using BAS

2025-04-03T15:51:13.956000+02:00

Introduction

In this post, I will explain how to connect multiple databases and OData services to SAP BTP using BAS . This guide covers configuring UI5 applications to consume multiple OData services from both SAP S/4HANA (on-premise) and SAP BTP ABAP environment, ensuring seamless data integration.

Summary

I aim to integrate three different OData services from different database sources :

On-Premise S/4HANA OData V2 Services

ZPR_EMP_DETAILS_SRV : Fetches employee details.
ZFI_TEST_ODATA_SRV : Fetches financial data.

SAP BTP ABAP Environment OData V4 Service

ZUI_TAB_TRAVDAT_O4_AKS_001: Fetches travel-related data using the RAP Model.

Steps to Connect Multiple OData Services

Step 1: Add Data Sources in UI5 Application

Create a UI5 application in VS Code.
While creating the application, provide the service URL to configure an OData service automatically.
Navigate to webapp/manifest.json.
Modify the dataSources section to include multiple OData services as follows:

"dataSources": {
  "mainService": {
    "uri": "/sap/opu/odata/sap/ZPR_EMP_DETAILS_SRV/",
    "type": "OData",
    "settings": {
      "odataVersion": "2.0"
    }
  },
  "subService": {
    "uri": "/sap/opu/odata/sap/ZFI_TEST_ODATA_SRV/",
    "type": "OData",
    "settings": {
      "odataVersion": "2.0"
    }
  },
  "rapService": {
    "uri": "/sap/opu/odata4/sap/zui_tab_travdat_o4_aks_001/",
    "type": "OData",
    "settings": {
      "odataVersion": "4.0"
    }
  }
}

Step 2: Configure Models in manifest.json

Each model corresponds to an OData service:

"models": {
  "": {
    "dataSource": "mainService",
    "preload": true,
    "settings": {}
  },
  "subModel": {
    "dataSource": "subService",
    "preload": true,
    "settings": {}
  },
  "rapModel": {
    "dataSource": "rapService",
    "preload": true,
    "settings": {
      "operationMode": "Server",
      "autoExpandSelect": true,
      "earlyRequests": true
    }
  }
}

Step 3: Configure ui5.yaml for Backend Connections

In ui5.yaml, configure the destinations for OData services:

server:
  customMiddleware:
    - name: ui5-middleware-simpleproxy
      afterMiddleware: compression
      configuration:
      ui5:
          path:
            - /resources
            - /test-resources
          url: https://ui5.sap.com
        backend:
# On-premise SAP System Destination 1 - Replace with your URL
        - scp: true
        path: /sap/opu/odata/sap/ZPR_EMP_DETAILS_SRV/
        url: https://your-onpremise-system-hostname:port/
        destination: SAHANA_CONN
        client: 'your client ID'
        authenticationType: BasicAuthentication

  # On-premise SAP System Destination 2 - Replace with your URL  
        - scp: true
        path: /sap/opu/odata/sap/ZFI_TEST_ODATA_SRV
        url: https://your-onpremise-system-hostname:port/
        destination: SAHANA_CONN
        client: 'your client ID'
        authenticationType: BasicAuthentication

  # SAP BTP ABAP Environment Destination - Replace with your instance URL
        - scp: true
        path: /sap/opu/odata/sap/zui_tab_travdat_o4_aks_001/
        url: https://your-abap-instance-guid.abap.region.hana.ondemand.com
        destination: abap-cloud-default_abap-trial-9a87acc7trial-dev
        client: 'your client ID'
        authenticationType: OAuth2UserTokenExchange

Note :

Destination :

S4HANA_CONN is used for two OData V2 services hosted in the on-premise S/4HANA system as shown in below screenshot.

abap-cloud-default_abap-trial-9a87ace7trial-dev is for the RAP-based OData V4 service hosted on SAP BTP as shown in below screenshot.

Authentication Types:

On-premise S/4HANA services use BasicAuthentication, which is simpler but less secure for cloud-based scenarios.
The SAP BTP service uses OAuth2UserTokenExchange, enabling secure token-based communication.

All the Connected OData will be Listed in Service Manager as shown in below screenshot.

Important Note on OData Connection Methods:

Avoid connecting directly to OData services via the Service Manager, as it can lead to data inconsistency issues (e.g., all requests may unintentionally retrieve only the last edited destination). Instead, I prefer using the Destination Service (as shown in the configuration above) for:

Stable & secure connections
Proper authentication handling (Basic/OAuth2)
Consistent data retrieval (prevents mixing/overwriting datasets).

Conclusion

By following these steps, you can successfully integrate multiple OData services in a SAP BTP-based Fiori application. This setup allows seamless data flow between on-premise S/4HANA and cloud-based SAP BTP ABAP environment, ensuring a modern, scalable architecture.

I hope this helps! Let me know your thoughts or if you have any questions.
Thanks,

Akshay Anil
Technical Consultant, SAP ABAP | BTP | Fiori | Ui5

SAP Business Application Studio OData

Update/Modify any Table data dynamically

2025-04-04T05:23:22.969000+02:00

To update any table dynamically in an SAP ABAP program, the general approach involves working with dynamic internal tables. This can be useful when you don't know the table's structure at compile-time, and you need to determine the table structure at runtime.

In this scenario, I'll provide a more detailed breakdown, including how you can dynamically:

Define a dynamic table at runtime.
Insert data into it.
Update rows based on a condition.
Handle different types of data and tables.

This example will be more general and applicable to any table in SAP.

Detailed Steps for Dynamic Table Updates

1. Create a Dynamic Table

In ABAP, you use CREATE DATA to create a dynamic internal table. You also need to dynamically assign a structure for the table using the REF TO DATA concept.

2. Field Symbol for Dynamic Data

A field symbol is used to refer to the data in a dynamic table. This allows you to access and modify the contents of the table.

3. Inserting Data into the Dynamic Table

You can append data into the dynamic table by dynamically creating entries.

4. Updating Data in the Dynamic Table

To update data, you 'will loop through the table and check conditions to identify which rows need modification. You will then use the MODIFY statement to update the content.

Example Code: Dynamic Table Creation, Insertion, and Update

Handling Other SAP Tables Dynamically

The above code works with the SFFLIGHT table. However, you can adopt this to any table in SAP by adjusting the structure and fields of the dynamic table.

To generalize for any SAP table, you'd need to know the structure of the table you're dealing with. You can retrieve the table's structure dynamically using function modules or predefined structures for commonly used SAP tables.

Example: Dynamically Handling Different Tables

If you want to dynamically choose which SAP table to work with, here’s a more flexible approach: &---------------------------------------------------------------------*

*& Report ZUT_UPLOAD_EXCEL_TO_DB_TABLE

*&---------------------------------------------------------------------*

REPORT zut_upload_excel_to_db_table.

*&---------------------------------------------------------------------*

*& Global Data Definitions

*&---------------------------------------------------------------------*

DATA gt_data TYPE REF TO data.

DATA gs_data TYPE REF TO data.

FIELD-SYMBOLS: <ft_data> TYPE STANDARD TABLE,

<fs_data> TYPE any.

"Table Structure

DATA: gt_dd03p TYPE TABLE OF dd03p.

FIELD-SYMBOLS: <fs_dd03p> TYPE dd03p.

"Error Report

DATA: gs_error_report TYPE bapiret2,

gt_error_report TYPE TABLE OF bapiret2.

*&---------------------------------------------------------------------*

*& Selection Screen Definition

*&---------------------------------------------------------------------*

SELECTION-SCREEN BEGIN OF BLOCK b01 WITH FRAME TITLE TEXT-b01.

PARAMETERS: p_table TYPE dd02l-tabname OBLIGATORY.

SELECTION-SCREEN SKIP.

PARAMETERS: p_file LIKE rlgrap-filename OBLIGATORY MEMORY ID zmdmfile.

SELECTION-SCREEN SKIP.

SELECTION-SCREEN BEGIN OF LINE.

SELECTION-SCREEN COMMENT 1(30) TEXT-rfr.

PARAMETERS: p_refr RADIOBUTTON GROUP r01.

SELECTION-SCREEN END OF LINE.

SELECTION-SCREEN BEGIN OF LINE.

SELECTION-SCREEN COMMENT 1(30) TEXT-ups.

PARAMETERS: p_upsrt RADIOBUTTON GROUP r01.

SELECTION-SCREEN END OF LINE.

SELECTION-SCREEN END OF BLOCK b01.

*&---------------------------------------------------------------------*

*& PAI/PBO Processing

*&---------------------------------------------------------------------*

AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.

"F4 for File name

PERFORM f4_file_name USING 'P_FILE' CHANGING p_file.

AT SELECTION-SCREEN ON p_table.

"Validate the Table/Input

PERFORM validate_table .

*&---------------------------------------------------------------------*

*& Start-of-Selection Event

*&---------------------------------------------------------------------*

START-OF-SELECTION.

"Initialization

PERFORM initialization.

"Get Excel data in internal table

PERFORM convert_excel.

"Upload data to database table

PERFORM upload_table.

*&---------------------------------------------------------------------*

*& End-of-Selection Event

*&---------------------------------------------------------------------*

END-OF-SELECTION.

"Display ALV Report

PERFORM display_report.

*&---------------------------------------------------------------------*

*& Form f4_file_name

*&---------------------------------------------------------------------*

*& text

*&---------------------------------------------------------------------*

*& --> p1 text

*& <-- p2 text

*&---------------------------------------------------------------------*

FORM f4_file_name USING p_field TYPE any

CHANGING p_file TYPE any.

"F4 on File Name

CALL FUNCTION 'KD_GET_FILENAME_ON_F4'

EXPORTING

program_name = syst-repid

dynpro_number = syst-dynnr

field_name = p_field

static = ' '

mask = '*.XLSX'

fileoperation = 'R'

path = 'C:\TEMP\'

CHANGING

file_name = p_file

EXCEPTIONS

mask_too_long = 1

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

ENDFORM.

*&---------------------------------------------------------------------*

*& Form validate_table

*&---------------------------------------------------------------------*

*& text

*&---------------------------------------------------------------------*

*& --> p1 text

*& <-- p2 text

*&---------------------------------------------------------------------*

FORM validate_table .

"Local Variables

DATA: ls_dd02l TYPE dd02l,

ls_tvarvc type tvarvc. " C2-8270 C2-8270

CONSTANTS : lc_mhk_table(15) type c VALUE 'Z_MHK_TABLE' ." added-C2-8270

"Upload only Tables in customer namespace

IF p_table+0(1) NE 'Z' AND p_table+0(1) NE 'Y'.

MESSAGE 'Only Y or Z tables can be uploaded' TYPE 'E'.

RETURN.

ENDIF.

*— Only transparent tables can be uploaded

SELECT SINGLE *

FROM dd02l

INTO ls_dd02l

WHERE tabname = p_table.

IF sy-subrc EQ 0.

IF ls_dd02l-tabclass NE 'TRANSP'.

MESSAGE 'Only transparent TABLES can be uploaded' TYPE 'E'.

ENDIF.

ELSE.

MESSAGE 'Invalid Table Name' TYPE 'E'.

RETURN.

ENDIF.

*BOC - C2-8270

SELECT SINGLE *

INTO ls_tvarvc

FROM tvarvc

WHERE name = lc_mhk_table

and low = P_table.

if sy-subrc NE 0.

MESSAGE 'Only TVARVC entry Table can be uploaded TYPE ' TYPE 'E'.

ENDIF.

*EOC - C2-8270

ENDFORM.

*&---------------------------------------------------------------------*

*& Form convert_excel

*&---------------------------------------------------------------------*

*& text

*&---------------------------------------------------------------------*

*& --> p1 text

*& <-- p2 text

*&---------------------------------------------------------------------*

FORM convert_excel .

"Local Variables

DATA lt_raw_data TYPE truxs_t_text_data.

"Excel Functions

CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'

EXPORTING

* I_FIELD_SEPERATOR =

i_line_header = 'X'

i_tab_raw_data = lt_raw_data

i_filename = p_file

TABLES

i_tab_converted_data = <ft_data>

EXCEPTIONS

conversion_failed = 1

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

ENDFORM.

*&---------------------------------------------------------------------*

*& Form upload_table

*&---------------------------------------------------------------------*

*& text

*&---------------------------------------------------------------------*

*& --> p1 text

*& <-- p2 text

*&---------------------------------------------------------------------*

FORM upload_table.

"Local Variables

FIELD-SYMBOLS: <fs_value> TYPE any.

DATA: lv_fieldname TYPE dfies-lfieldname,

lt_value_list TYPE TABLE OF soli,

ls_message TYPE syst,

lv_value_internal TYPE c,

lt_failure_tab TYPE TABLE OF ddfkeyrc,

ls_failure_tab TYPE ddfkeyrc,

lt_additional_fields TYPE dcfielddats,

ls_additional_fields TYPE LINE OF dcfielddats.

DATA: lv_row_number TYPE i,

lv_col_number TYPE i.

"Get Table Info

CALL FUNCTION 'DDIF_TABL_GET'

EXPORTING

name = p_table

state = 'A'

langu = sy-langu

TABLES

dd03p_tab = gt_dd03p

EXCEPTIONS

illegal_input = 1

OTHERS = 2.

IF sy-subrc <> 0.

ENDIF.

SORT gt_dd03p BY position.

"Validate each Row

REFRESH: gt_error_report[].

LOOP AT <ft_data> ASSIGNING <fs_data>.

"Row Number

lv_row_number = sy-tabix.

"Validate Each Field

LOOP AT gt_dd03p ASSIGNING <fs_dd03p>.

"Column Number

lv_col_number = sy-tabix.

lv_fieldname = <fs_dd03p>-fieldname.

"Get the Value

ASSIGN COMPONENT <fs_dd03p>-fieldname OF STRUCTURE <fs_data>

TO <fs_value>.

IF sy-subrc NE 0.

CONTINUE.

ENDIF.

"Validate the Field/Value

REFRESH: lt_failure_tab[].

"Collect the errors

LOOP AT lt_failure_tab INTO ls_failure_tab.

CLEAR gs_error_report.

gs_error_report-type = 'E'.

gs_error_report-id = ls_failure_tab-arbgb.

gs_error_report-number = ls_failure_tab-msgnr.

MESSAGE ID ls_failure_tab-arbgb TYPE 'I' NUMBER ls_failure_tab-msgnr

WITH ls_failure_tab-msgv1 ls_failure_tab-msgv2

ls_failure_tab-msgv3 ls_failure_tab-msgv4

INTO gs_error_report-message.

gs_error_report-message_v1 = ls_failure_tab-msgv1.

gs_error_report-message_v2 = ls_failure_tab-msgv2.

gs_error_report-message_v3 = ls_failure_tab-msgv3.

gs_error_report-message_v4 = ls_failure_tab-msgv3.

gs_error_report-parameter = ls_failure_tab-keyvalue.

gs_error_report-row = lv_row_number.

gs_error_report-field = ls_failure_tab-fieldname.

gs_error_report-system = lv_col_number.

APPEND gs_error_report TO gt_error_report.

ENDLOOP.

"Check if there are any errors

IF gt_error_report[] IS NOT INITIAL.

RETURN.

ENDIF.

"Local Task for Update

SET UPDATE TASK LOCAL.

"Modify

IF p_refr EQ 'X'.

DELETE FROM (p_table).

ENDIF.

MODIFY (p_table) FROM TABLE <ft_data>.

IF sy-subrc EQ 0.

COMMIT WORK AND WAIT.

ELSE.

ROLLBACK WORK.

ENDIF.

ENDFORM.

*&---------------------------------------------------------------------*

*& Form display_report

*&---------------------------------------------------------------------*

*& text

*&---------------------------------------------------------------------*

*& --> p1 text

*& <-- p2 text

*&---------------------------------------------------------------------*

FORM display_report.

"Local Variables

TYPE-POOLS: slis.

DATA: lv_alv_callback_program TYPE sy-repid,

ls_alv_layout TYPE slis_layout_alv.

lv_alv_callback_program = sy-repid.

ls_alv_layout-zebra = 'X'.

ls_alv_layout-colwidth_optimize = 'X'.

"Display Report

IF gt_error_report[] IS INITIAL.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

i_interface_check = ' '

i_bypassing_buffer = ' '

i_buffer_active = ' '

i_callback_program = lv_alv_callback_program

i_callback_pf_status_set = ' '

i_callback_user_command = ' '

i_callback_top_of_page = ' '

i_callback_html_top_of_page = ' '

i_callback_html_end_of_list = ' '

i_structure_name = p_table

i_background_id = ' '

is_layout = ls_alv_layout

TABLES

t_outtab = <ft_data>

EXCEPTIONS

program_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

ELSE.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

i_interface_check = ' '

i_bypassing_buffer = ' '

i_buffer_active = ' '

i_callback_program = lv_alv_callback_program

i_callback_pf_status_set = ' '

i_callback_user_command = ' '

i_callback_top_of_page = ' '

i_callback_html_top_of_page = ' '

i_callback_html_end_of_list = ' '

i_structure_name = 'BAPIRET2'

i_background_id = ' '

is_layout = ls_alv_layout

TABLES

t_outtab = gt_error_report

EXCEPTIONS

program_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

ENDFORM.

*&---------------------------------------------------------------------*

*& Form initialization

*&---------------------------------------------------------------------*

*& text

*&---------------------------------------------------------------------*

*& --> p1 text

*& <-- p2 text

*&---------------------------------------------------------------------*

FORM initialization .

"Create dynamic internal table

CREATE DATA gt_data TYPE TABLE OF (p_table).

ASSIGN gt_data->* TO <ft_data>.

"Create dynamic work area

CREATE DATA gs_data TYPE (p_table).

ASSIGN gs_data->* TO <fs_data>.

ENDFORM.

Selection Screen :

Key Concepts:

Dynamic Table Creation Based on Structure Name:

The lv_structure_name is used to specify the table's structure dynamically.
CREATE DATA lt_dynamic TYPE TABLE OF (lv_structure_name) dynamically creates a table based on the structure name passed.

Appending Data:

In the example, the code simulates inserting data into the dynamic table based on the structure SFLIGHT. You would change this logic depending on the structure of the dynamic table you're working with.

Field Symbols:

The field symbols (<fs_dynamic>, <fs_row>) allow you to reference and modify the data dynamically. You modify rows based on conditions, like carrid or connid.

Modifying Data:

The MODIFY statement is used to update the rows of the dynamic internal table.

Conclusion:

Dynamic table updates in SAP ABAP allow you to work with tables whose structures are not known at compile-time. This provides flexibility when dealing with data from various sources or working with user-defined structures. The key challenge is ensuring that the correct structure is used and modifying data efficiently at runtime.

SDT Using SAP Business Transformation Center: End to End Process & Technical Configuration

2025-04-04T14:37:07.858000+02:00

Introduction:

SAP Business Transformation Center is a SaaS (software-as-a-service) product from SAP, embedded into SAP Cloud ALM. It is a one-stop shop for customers who want to selectively transition from SAP ERP Central Component (SAP ERP) 6.08 to SAP S/4HANA 2023 or beyond using through SHELL CONVERSION method of SDT. Their target can be either to S/4 HANA on-premises or SAP S/4 HANA private cloud edition under RISE. In general, it is available to all the customer with a valid SAP Service Cloud subscriptions and the SAP Enterprise Support agreement and does not involve any additional license cost for usage.

In this blog i will show you End-to-End migration process and setup the connectivity between source and target system with SAP Cloud ALM.

Technical System Landscape:

SAP Business Transformation Center is a cloud native application which relies on the following components:

The source system, which utilizes the current ST-PI add-on to enable the data transformation with SAP Business Transformation Center.
The SAP S/4HANA system, which contains all necessary subcomponents already shipped within the SAP S/4HANA CORE component.

Each system is accessed from the cloud layer using the SAP Cloud Connector. The SAP ECC system and the SAP S/4HANA system are connected via OData service bindings from SAP Business Technology Platform. There is an RFC-based connection between the SAP ECC and the SAP S/4HANA system.

Source system:
ECC 6.0 EHP 8
OS: SuSE Linux 15.2
DB: SAP ASE 16.0.04.01

Target system:
Release: SAP S4HANA 2023 FPS02
OS: SuSE Linux 15.5
DB: SAP HANA DB 2.00.081.00.1733303410

Target system preparation for BTC:

In a shell conversion scenario, all data from the source SAP ERP system is removed, leaving the system with the customizing data only (Without master and transaction data). This empty shell system is then converted to SAP S/4HANA using SUM DMO. After the completion of the conversion, the selected master and transaction data is then migrated to the newly converted S/4HANA system.

Prerequisites Technical Aspects
1. Execution of SAP Readiness Check for conversion
2. Execution of SAP Readiness Check for Usage and Data Profiling
3. Create target system:
a) Creation of a Shell based on customer ECC
b) Conversion of ECC Shell to SAP S/4HANA with SAP SUM and provide as target system

Prerequisites Functional Aspects:
A. Following SAP S/4HANA conversion guide (link):
a) Simplification items
b) CVI
c) Custom Code adaption
d) Inconsistencies

End-to-End Migration Process and activities in SAP BTC:

Technical configuration and connectivity of source and target system:

1. Onboarding a New ABAP Source System
a. Technical Prerequisites and Required Add-Ons
b. Required SAP Notes
c. OData Services for Source System
d. Cloud Connector for Source System
e. Connect a Source ABAP System to SAP Cloud ALM
f. Maintenance of Property Store in the Connected Source Systems
g. Additional Technical Prerequisites for Source System
h. Next Steps After Onboarding a Source System

Technical Prerequisites and Required Add-Ons:

Minimum software component version requirement	Our current version
SAP_APPL 618	SAP_APPL 618 SP15
ST-PI 740 SP>=24	ST-PI 740 SP27
DMIS 2011_1_731 >=SP18	DMIS 2011_1_731 SP26

Required SAP Notes:

3443741 - Collective note for SAP Business Transformation Center
Implement following S-Notes: 3548580

OData Services for Source System:

Activate below O-Data Services in source system-
T-Code: /N/IWFND/MAINT_SERVICE
/BDTS/COMMAND_SRV
/BDTS/INSTALLED_SAP_NOTE_SRV
/BDTS/PRESEL_TAB_DATA_SRV
/BDTS/PRESEL_TAB_READ_NAME_SRV
/BDTS/PRESEL_TASK_IS_CREATED_SRV
/BDTS/PRESEL_TASK_PORTION_SRV
/BDTS/PRESEL_TASK_READ_STATUS_SRV
/BDTS/SOFTWARE_COMPONENT_SRV
/BDTS/TABLE_FIELD_STRUCTUR_SRV

Cloud Connector for Source System:

1. Install Cloud Connector
2. Connect your SAP Cloud ALM subaccount to the cloud connector
3. Add backend source system in the cloud connector with HTTPS protocol

Connect a Source ABAP System to SAP Cloud ALM:

Connect the ABAP system to cloud ALM using the 'Landscape management'
T-Code /SDF/ALM_SETUP
Add endpoint for Business transformation center in the connected system and test the connectivity

Maintenance of Property Store in the Connected Source Systems:

Execute the /BDTS/ADMIN transaction.
Double-click on the /BDTS/PROPERTIES_SET object, or select this object and click Execute.
In the Property Store Maintenance transaction, you can create, change or delete a property.

Next Steps After Onboarding a Source System:

Generate Analysis File:
To generate an analysis file in the SAP ECC System, follow the instructions from SAP Note 3275056
For analysis file implement below two s-note
3112362 - SAP Readiness Check for SAP ERP Usage and Data Profiling
3275056 - SAP Readiness Check for SAP ERP Usage and Data Profiling: Initial Data Migration Profile 2.0
Execute the program RC_UDP_START_DMR2 via transaction SA38 in the productive client of the production system to start the analysis
Choose Schedule Analysis to schedule the background job to collect the data.
Once the data collection job is finished, choose the Download DMR2 Analysis Data option from within the program RC_UDP_START_DMR2 to download the analysis data to your local file system.
Upload the analysis file in Cloud ALM

Run system scan in Cloud ALM:

Like we had scoped the company code and transformation object for SDT, we must also check the relevance of each of the Z object and scope it based on the customer requirement or based on its last Activity after discussing with the object owner. This scoping can be performed using 'Select Scanned Table' app as shown below. Please note that any Z table with record count zero is automatically marked as out of scope by SAP BTC.

Onboarding of target S/4 HANA Shell to SAP BTC:

Technical Prerequisites and Required Add-Ons
Required SAP Notes
OData Services for Target System
Cloud Connector for Target System
Connect a Target ABAP System to SAP Cloud ALM
Create RFC Destination to SAP ECC Source System
Maintenance of Property Store in the Connected Target System
Save the Upgrade Buffers
Start the Command Daemon
Next Steps After Onboarding a Target System

Technical Prerequisites and Required Add-Ons:

Ensure that the minimum version requirement
S4COREOP 108, with corresponding support package level >=FPS1.
ST-PI >=740, with corresponding support package level >=0024.

Required SAP Notes:

Ensure to apply the SAP note 3443741 in target system.

OData Services for Target System:

In the SAP S/4HANA target system, some components from the ST-PI add-on are reused, therefore both OData V2 and V4 services need to be activated.

OData V2 services:
T-Code: /IWFND/MAINT_SERVICES
/BDTS/INSTALLED_SAP_NOTE_SRV
/BDTS/SOFTWARE_COMPONENT_SRV
/BDTS/TABLE_FIELD_STRUCTUR_SRV

OData V4 services:
T-Code: /IWFND/V4_ADMIN
API_BDTSCOMMAND
API_BDTSDESIGNTIMEENTITY
API_BDTSEXECUTIONPLAN
API_BDTSHEALTHCHECK
API_BDTSMIGRATIONSTATUS
API_BDTSTABLEFIELDSTRUCT
API_BDTSVALUEMAPPINGDATA

Cloud Connector for Target System:

1. Install Cloud Connector
2. Connect your SAP Cloud ALM subaccount to the cloud connector
3. Add backend target system in the cloud connector with HTTPS protocol

Connect a Target ABAP System to SAP Cloud ALM:

Connect the ABAP system to cloud ALM using the 'Landscape management'
T-Code /SDF/ALM_SETUP
Add endpoint for Business transformation center in the connected system and test the connectivity

Create RFC Destination to SAP ECC Source System:

Create RFC Destination to SAP ECC Source System in target system and maintain the property store in target as described in Maintenance of Property Store in SAP S/4HANA System.

This RFC will be used by the migration engine of SAP BTC to pull data packages from the SAP ECC source system and hence must be maintained in the property RfcDestinationSender in t-code bdts_admin-> Select BDTS_PROPERTIES_SET.

Maintenance of Property Store in the Connected Target System:

Save the Upgrade Buffers:

During the shell conversion process, the upgrade buffer of the system was updated and this must be saved

Execute the BDTS_ADMIN transaction.
Double-click on BDTS_DMC_SAVE_UPG_TRANS object or select Execute.
Select Save transports from upgrade

Start the Command Daemon:

To enable the handling of cloud commands on the ABAP side, the Command Daemon must be activated

Execute the BDTS_ADMIN transaction.
Double-click on BDTS_CMD_WDOG_START object or select it and click Execute.
Enter BDTS_T_DAE as the daemon user (or whatever you set up for this task) and set the frequency. The recommended frequency to use is 1.000 milliseconds.
In case the daemon is already running, a corresponding notification is issued.

Next Steps After Onboarding a Target System:

Now that your target system is onboarded, you can run a final check from the BDTS_ADMIN transaction with the BDTS_ADM_SETUP_CHECK health check, as described in Health Checks. This setup check runs health checks that are specific for the setup.

In this way we can prepare and stablished the connectivity for source and target system with SAP Cloud ALM.

Next steps after the technical configuration-

Create digital blueprint
Create transformation model and version
Create cycle and Run cycle

Once we create a version of transformation model from the blueprint and connect it to the source ECC system and target S/4 HANA system, it triggers the application data migration from source to the target. It happens in 4 phases as shown below.

PHASE 1: CYCLE PREVALIDATION (UPTIME)
PHASE 2: CYCLE PREPARATION (UPTIME)
PHASE 3: RUN CYCLES (DOWNTIME)
PHASE 4: POSTPROCESS CYCLE (DOWNTIME)

All these phases can be managed using the "Manage Cycle" app in SAP BTC.

1.Cycle Prevalidation:

During the "Cycle prevalidation" phase, several prerequisites of the connected systems are examined. Making sure there is no business data on the target S/4 HANA shell system. Any problems found are recorded in the cycle log as indicated, and they can be carried out repeatedly until this phase turns green.

2. Cycle Preparation:

In 'Cycle preparation' phase, the actual preparation and configuration of the migration engine takes place. This phase runs as a part of uptime phase and runs before the cutover. This step along with initial step up, also covers transformation rule creation, sub-transformation object creation and validation followed by the postprocessing items creation.

3. Run Cycles:

Based on the specified and scoped elements in the transformation model, the third phase, "Run Cycles," involves the actual physical data migration to the target S/4 SHELL.

4. Postprocess Cycles:

In the final step of "Post-processing", all the data that was transferred directly at database table level gets converted into SAP S/4 HANA model. Like all phases, logging is available which enables us to view the progress at a granular level.

This blog covers End to End Process & Technical Configuration for SDT using SAP BTC.

Thanks for reading!

RAP: MANAGED VS UNMANAGED RAP

2025-04-08T10:33:54.672000+02:00

Managed RAP
• Greenfield Implementation
• CRUD operations are handled by the framework.
• Transactional buffer is managed by the framework.
• The framework takes care of the save sequence.

Unmanaged RAP
• Brownfield Implementation
• CRUD requires custom implementation.
• Transactional buffer is managed with a global singleton/static class.
• Custom save sequence logic must be written.

Managed with Unmanaged Save:
• The interactive phase remains the same, but the save sequence is handled by the developer.
• Transactional buffer is managed by RAP architecture.
• No persistence table in unmanaged save.

Additional Save (Enhancing Managed RAP)
• Allows developers to implement additional steps for the save logic of a managed RAP BO,
enhancing the standard save sequence.
• Can have a persistence table, as the RAP framework takes care of persisting to the database.

Restrictions:
You can’t use a BAPI with a commit statement, as the RAP LUW takes care of commit and
rollback. Additionally, there’s no persistence table in Unmanaged Save, as the developer writes their
own logic for persisting. Please refer to the attachment for complete restrictions.

When using a function module (on-premise), always create a wrapper around it and
release it with C1 to maintain cloud compatibility.

Best Practices & Recommendations:
• Managed RAP with Unmanaged Save is often the recommended option, combining the best
of both approaches.
• Unmanaged RAP should usually be a last resort.

Key Use Cases:
• No Custom Code: Go for Managed RAP.
• Need to Utilize Update Function Module: opt for Managed RAP with Unmanaged Save.
• Reusable Code/Loose Coupling with Pre-existing Functionality: Choose Unmanaged
RAP.
• Consume Custom APIs (on-premise) in BTP: Use Custom Entities + Unmanaged RAP.
• Unmanaged Queries: Combine Custom Entities + Unmanaged RAP.

Unleashing the Power of ASTER: Scripting Your Way to Enhanced SAP Integration Testing

2025-04-13T08:00:00.015000+02:00

What is ASTER?

ASTER stands for "Another Syntax Tree Expression Runtime." But what does that really mean? Essentially, ASTER is a scripting language that allows you to go beyond standard configuration-based data manipulation and validation within Int4 Suite. It provides a syntax tree execution runtime, enabling you to handle complex scenarios and edge cases with greater ease and efficiency.

Think of it this way: while Int4 Suite's configuration-based engine is incredibly robust and serves the majority of testing needs brilliantly, ASTER offers an additional layer of flexibility for those unique, intricate situations. It's not meant to replace the existing, proven methods but rather to enhance them, providing you with a powerful tool for advanced features.

Why ASTER? The Story Behind the Script

Int4 Suite has a well-deserved reputation for its strong configuration-based data manipulation and validation engine. It has been instrumental in supporting large-scale cloud integration migrations. However, as with any powerful tool, there are always scenarios that push the boundaries.

We began to notice recurring questions and challenges from our users, particularly around variable manipulation and complex validations. "Is it possible to concatenate variables?" "How can we handle this specific edge case?" These questions spurred us to think beyond the existing configuration options.

The turning point came with a particularly demanding validation scenario presented by a customer. It became clear that we needed a solution that could enable more than just what configuration alone could provide. That's when the idea for ASTER began to take shape. What started as a small concept evolved into a significant addition to the Int4 Suite, designed to empower users with the ability to script their own solutions.

The Technology Behind ASTER

ASTER is built on a solid foundation of ABAP classes. The parsing and execution of the ASTER script occur in a safe and isolated environment, ensuring that your scripting activities don't interfere with the underlying ABAP server environment. This isolation means you can confidently use ASTER without worrying about unintended side effects.

Key Features of ASTER

Syntax Tree Execution: ASTER utilizes a syntax tree approach, which is a common technique in language design. This allows for efficient parsing and evaluation of expressions, even complex ones.
Dynamic Typing: ASTER is dynamically typed, meaning you don't have to worry about declaring data types. This simplifies scripting and makes it more accessible.
Arithmetic and String Manipulation: ASTER supports basic arithmetic operations, string manipulation, and boolean logic, providing you with the tools you need for a wide range of tasks.
User-Defined Functions: You can build your own functions in ASTER, allowing you to create reusable code and tailor the language to your specific needs.
Integration with Int4 Suite: ASTER seamlessly integrates with Int4 Suite features. You can access test case execution data, payloads, set variables, and more, making it a powerful tool for enhancing your testing workflows.
Safe and Isolated Environment: ASTER scripts are executed in a safe and isolated environment, ensuring that they don't interfere with the underlying ABAP server.

Getting Started with ASTER

ASTER is designed to be intuitive and easy to learn, especially if you have some familiarity with other programming languages. We've drawn inspiration from popular languages to make the syntax familiar and accessible.

Where to Play with ASTER

In the upcoming Int4 Suite 3.11 release, you'll find a new tile called "Scripts" within the Int4 tiles. This tile will provide access to a script management interface and a user-friendly editor. The editor, based on the open-source Ace editor, has been extended to support ASTER syntax, including syntax highlighting and code completion. This makes writing and debugging ASTER scripts a breeze.

Basic Concepts

Expressions: ASTER primarily works with expressions. An expression is a piece of code that evaluates to a value. This could be a simple arithmetic calculation, a string, or a more complex operation.
Variables: You can use variables in ASTER to store and manipulate data. Variables don't need to be explicitly declared; you can simply assign a value to a variable and start using it.
Semicolons: Use semicolons to separate multiple expressions on a single line.
Output: The output of an ASTER script is the result of the last evaluated expression.

Example: Hello World

Here's a simple "Hello World" example in ASTER:

"Hello World";

When you run this script, the output will be "Hello World."

Beyond Hello World

Of course, ASTER can do much more than just print "Hello World." You can perform arithmetic calculations, manipulate strings, work with variables, and build complex logic as shown in Figure below.

Extending Int4 Suite with ASTER

One of the most exciting aspects of ASTER is its ability to extend the capabilities of Int4 Suite. You can use ASTER to:

Perform complex data validations: Validate data based on calculations, comparisons, and logical operations.
Manipulate data: Transform and manipulate data in ways that are not possible with standard configuration.

Handle edge cases: Address unique and intricate scenarios that require custom logic.
Automate tasks: Automate repetitive tasks and streamline your testing workflows.

Using the Aster script is done directly in the payload processing tab of Automation Objects as shown in the Figure below.

The Future of ASTER

We believe that ASTER has the potential to revolutionize how you approach integration testing with Int4 Suite. We're committed to continuously improving ASTER and adding new features based on your feedback.

Kudos

Special Kudos to our two members of our Int4 Suite Product Team - Marcin Galczynski and Tomasz Mackowski for making ASTER happen!

Conclusion

ASTER is a powerful new scripting language that brings enhanced flexibility and precision to integration testing with Int4 Suite. It allows you to handle complex scenarios, manipulate data, and automate tasks with greater ease. We encourage you to explore ASTER and discover the possibilities it unlocks for your testing workflows.

Stay tuned for the release of Int4 Suite 3.11 and get ready to unleash the power of ASTER!
I hope this blog post meets your needs! Let me know if you'd like any adjustments or further assistance.

Performance comparison: FILTER vs LOOP vs FOR

2025-04-16T12:06:26.335000+02:00

Recently, I needed to move lines from one table to another. I decided to check which method is the fastest (most performant). Below is my analysis — but first, a few comments on the methodology.

Methodology

When comparing how AS ABAP processes a set of data (in particular, a table), I realized that the method executed first is always slower. Therefore, I use run_dummy() to eliminate this issue.
I use DO n TIMES for the same reason. If I called each method only once, the first one would take twice as much time as the second (proof at the end of the blog).
I ran each test multiple times and present here the results that consistently occurred.
First, I tested with a sorted table using a unique key, and then with a standard table without a key. Without a key, I couldn’t use FILTER.
The first set of tests was performed on ECC 7.5. The second was repeated on BTP Steampunk, although with a different table type (VBRP and SFLIGHT), so direct comparison of results from ECC and BTP is impossible.

ECC tests

Just paste this into any report and it should run. In the second case, the key definition and the run_filter() method were removed.

CLASS main DEFINITION CREATE PUBLIC.

  PUBLIC SECTION.
    constants runs TYPE i VALUE 1000.

    METHODS: constructor,
      run_dummy,
      run_loop,
      run_for,
      run_filter.

  PRIVATE SECTION.
    DATA all_items TYPE SORTED TABLE OF vbrp WITH UNIQUE KEY vbeln posnr.

ENDCLASS.

CLASS main IMPLEMENTATION.
  METHOD constructor.
    SELECT * FROM vbrp UP TO 20000 ROWS
      INTO TABLE _items
     ORDER BY vbeln DESCENDING.
  ENDMETHOD.

  METHOD run_dummy.
    LOOP AT all_items ASSIGNING FIELD-SYMBOL(<item>).
    ENDLOOP.
  ENDMETHOD.

  METHOD run_for.
    DATA: selected_items TYPE TABLE OF vbrp.
    selected_items = VALUE #( FOR item IN all_items
                                WHERE ( vbeln = '0080011871' )
                                ( item )
                            ).
  ENDMETHOD.

  METHOD run_loop.
    DATA: selected_items TYPE TABLE OF vbrp.
    LOOP AT all_items ASSIGNING FIELD-SYMBOL(<item>) WHERE vbeln = '0080011871'.
      APPEND <item> TO selected_items.
    ENDLOOP.
  ENDMETHOD.

  METHOD run_filter.
    DATA: selected_items TYPE TABLE OF vbrp.
    selected_items = FILTER #( all_items USING KEY primary_key WHERE vbeln = '0080011871' ).
  ENDMETHOD.
ENDCLASS.

START-OF-SELECTION.
DATA(main) = new main( ).

do main->runs TIMES.
  main->run_dummy( ).
ENDDO.

do main->runs TIMES.
  main->run_loop( ).
ENDDO.

do main->runs TIMES.
  main->run_filter( ).
ENDDO.

do main->runs TIMES.
  main->run_for( ).
ENDDO.
ENDCLASS.

Results: sorted table, 1000 executions

I've made about a dozen runs. This result is representative of all of them (they didn't differ). LOOP is always the fastest, but FILTER is always right behind (difference is insignificant). VALUE FOR however is 50% slower.

Results: standard table, 1000 executions

I've made probably about 30 test runs. Results varied slightly but all of them can be summed up to two trends presented above.

Initially, LOOP was faster. A few minutes later, FOR overtook it, only to lose its lead again later. I have no idea what caused this fluctuation. In any case, the difference between both methods is minimal.

BTP Steampunk Test

This test used a different table: the all-time favorite /DMO/FLIGHT. Unfortunately, my BTP version doesn’t offer performance profiling (trace), so I had to use timestamps, which might introduce small measurement errors.

CLASS ycl_test_loops DEFINITION
  PUBLIC
  FINAL
  CREATE PUBLIC .

  PUBLIC SECTION.
    INTERFACES if_oo_adt_classrun.

    CONSTANTS runs TYPE i VALUE 1000.

  PRIVATE SECTION.
    DATA: all_items TYPE STANDARD TABLE OF /dmo/flight WITH NON-UNIQUE SORTED KEY ki COMPONENTS connection_id,
          connid TYPE /dmo/connection_id   VALUE '0407'.
    METHODS: prepare_data,
      run_dummy,
      run_loop,
      run_for,
      run_filter.

ENDCLASS.


CLASS ycl_test_loops IMPLEMENTATION.

  METHOD if_oo_adt_classrun~main.
    DATA: start TYPE timestampl,
          end   TYPE timestampl.

    me->prepare_data( ).

    GET TIME STAMP FIELD start.
    DO runs TIMES.
      me->run_dummy( ).
    ENDDO.
    GET TIME STAMP FIELD end.
    out->write( |dummy: { end - start }| ).


    GET TIME STAMP FIELD start.
    DO runs TIMES.
      me->run_loop( ).
    ENDDO.
    GET TIME STAMP FIELD end.
    out->write( |loop: { end - start }| ).


    GET TIME STAMP FIELD start.
    DO runs TIMES.
      me->run_for( ).
    ENDDO.
    GET TIME STAMP FIELD end.
    out->write( |for: { end - start }| ).


    GET TIME STAMP FIELD start.
    DO runs TIMES.
      me->run_filter( ).
    ENDDO.
    GET TIME STAMP FIELD end.
    out->write( |filter: { end - start }| ).

  ENDMETHOD.


  METHOD prepare_data.
    DO 500 TIMES. "I have only 40 entries in DB, so 40 * 500 gives me 20k entries
      SELECT * FROM /dmo/flight
      APPENDING TABLE _items.
    ENDDO.
  ENDMETHOD.


  METHOD run_dummy.
    LOOP AT all_items ASSIGNING FIELD-SYMBOL(<item>).
    ENDLOOP.
  ENDMETHOD.


  METHOD run_filter.
    DATA: selected_items TYPE TABLE OF /dmo/flight.
    selected_items = FILTER #( all_items USING KEY ki WHERE connection_id = connid ).
  ENDMETHOD.


  METHOD run_for.
    DATA: selected_items TYPE TABLE OF /dmo/flight.
    selected_items = VALUE #( FOR item IN all_items USING KEY ki
                              WHERE ( connection_id = connid )
                              ( item )
                            ).
  ENDMETHOD.


  METHOD run_loop.
    DATA: selected_items TYPE TABLE OF /dmo/flight.
    LOOP AT all_items ASSIGNING FIELD-SYMBOL(<item>) USING KEY ki
         WHERE connection_id = connid.
      APPEND <item> TO selected_items.
    ENDLOOP.
  ENDMETHOD.
ENDCLASS.

Results: Standard Table, 1000 Executions

The results are in seconds.

dummy: 3.5287930
loop:  1.3220800
for:   1.3824890

dummy: 3.5545590
loop:  1.3494420
for:   1.3473680

As in ECC, there’s no noticeable difference between LOOP and VALUE FOR.

Results: Sorted key, 1000 Executions

The results are in seconds.

dummy:  3.5353230
loop:   0.4449050
for:    0.5068880
filter: 0.0389550

dummy:  3.5583420
loop:   0.4789230
for:    0.4469660
filter: 0.0380170

dummy:  3.4402150
loop:   0.4193350
for:    0.4578140
filter: 0.0394450

Here things get interesting. Again, FOR and LOOP are very close — but what shocked me is that FILTER is 10x faster! If anyone could double-check my results, please let me know in the comments if I made a mistake.

Conclusions

On ECC with sorted keys:

LOOP was consistently the fastest,
FILTER was nearly as fast — arguably equivalent,
VALUE FOR was 50% slower (still acceptable, but noticeably slower)

On BTP with sorted keys:

LOOP and FOR perform almost identically.
FILTER is in a league of its own, being over 10 times faster.

Others:

When working with standard tables, there’s virtually no difference between LOOP and VALUE FOR. On BTP, LOOP is slightly better.

Using a sorted key reduced search time by ~20–30x on ECC, and ~3x on BTP. On BTP, combining a sorted key with FILTER reduced execution time by a factor of 45.

Interestingly, the SELECT operation is not affected by the key definition — so initializing the sorted key costs nothing. Naturally, modifying the table means the key must be rebuilt, which adds overhead. But if all_items is read-only, a sorted key makes a massive difference.

It’s clear that performance optimizations differ between systems. You can’t write code that’s optimal for both ECC and BTP. And it’s not just about DB storage types — even pure ABAP operations behave differently. On BTP (and likely in all ABAP Cloud environments), FILTER is a game changer. On ECC, it offers little to no advantage—aside from its more concise syntax.

Discussion

I see no value in the VALUE FOR statement (pun intended). Its syntax is unintuitive and has too many brackets. Also, it’s not debuggable, which makes troubleshooting more complex scenarios a pain in the...

VALUE requires a static type (# is statically derived from context), whereas LOOP supports dynamic types determined at runtime (using field symbols and ASSIGN COMPONENT). In general, we should prefer static typing, but cases where it has to be used, LOOP remains the only way.

FILTER has a clear and concise syntax and is shorter than LOOP. Most importantly, it's significantly faster in ABAP Cloud. It forces us to use sorted keys, while LOOP allows us to be lazy.

On ECC, I used a sorted table. On Steampunk, I used a standard table with a sorted key — so some differences might stem from this.

Proof for Point 2 in Methodology

For standard tables, running a tested method only once causes results to heavily depend on the order of method calls — even if run_dummy() is used:

Someone once said: "The last shall be first, and the first last" ;).

Anyways, when testing performance, be careful not to be fooled by call order.

ABAP Cloud Landing Page in ABAP Development Tools (ADT)

2025-04-19T08:05:51.235000+02:00

I am an ABAP developer How can I learn about ABAP Cloud?

"Learn About ABAP Cloud Landing Page" in ADT is one way of learning. The ABAP Cloud Landing Page serves as a comprehensive gateway that caters to developers across all proficiency levels - from newcomers to seasoned ABAP experts.

This centralized platform offers a meticulously organized collection of SAP-validated, trusted, repository, resources, making it effortless to navigate through essential information. The page features distinct sections including "Get Started," "ABAP Cloud wizards for each Development Scenarios," documentation links, Roadmaps, What's New Information, available tutorials, ensuring a smooth learning journey.

How to navigate to Learn About ABAP Cloud Landing Page in ADT?
ADT (ABAP in Eclipse )->Select Project -> Help -> Learn About About ABAP Cloud

This page features several sections:

Get Started
News
Transactional Apps
Analytical Apps
Integration Services
More about cloud development Concepts.

1. Get Started - Learn More Section

When you click on "Learn more" it navigate to SAP help documentation where you get the most important information about ABAP Cloud in one page.

1.1. Get Started - Resources

The resource overview includes documentation which provides detailed technical information about ABAP, tutorials that guide users through specific tasks or processes, blog posts that offer insights and tips from experienced users and developers, and videos that visually explain and demonstrate ABAP concepts and programming techniques.

You will also find "Resources" in every section where corresponding blogs, how to guides, tutorials, events sessions are linked accordingly.

2. News - Roadmap

News Roadmap section gives about the ABAP Cloud roadmap, planned and upcoming features across all solutions that offer ABAP Cloud.

3. Transactional Apps - Open Generators

Generators help you to develop transactional applications with low code. Through wizard in ADT you can develop a transaction applications.

Learn More Section

Learn More section navigates to help documentation for how to develop transactional, analytical and Integration services in ABAP Cloud.

4. Analytical Apps

In this section you will find help documentation and resources related to how develop analytical apps in ABAP Cloud.

5. Integration Services - Open Generators

Click Open Generators -> Choose a Project from Project Select -> Click OK

Generators help you to develop Integration services with low code.

6 More Section

Localization and Internalization

This sections given information about how apps and services can be translated and adapted to country/region-specific requirements.

Access Management

This section gives a overview of the important points about identity and access management considerations for SAP S/4HANA Cloud, public edition and SAP BTP, ABAP environment.

Extensibility:

This section give information about extensibility options in ABAP Cloud such as:

Key User Extensibility
Developer Extensibility
Side-by-Side Extensibility
Difference between these extensibility options when to which extensibility.
Extensibility Tools for Key users and developers.

More ABAP Cloud Development

Test: This section gives overview of requirements and considerations during the test phase of application development in ABAP cloud.

Extend: This section gives information about how to extend existing services and apps, background information about the release contract framework and the ABAP language.

Deploy: This section gives information about how to deploy and transport your app or service with ABAP lifecycle management.

Administrator, Configure and Monitor: This section gives information about the requirements and tools involved with, for example, monitoring an app or service that you've developed, Analyzing SQL statements, Identify and Access Management, Communication Management, security and Transport Management in ABAP Cloud.

This centralized landing page in ADT offers a meticulously organized collection of SAP-validated, trusted, repository, resources, making it effortless to navigate through essential information at single page which caters to developers across all proficiency levels - from newcomers to seasoned ABAP experts.

ABAP Cloud Landing Page will be updated with new content by SAP every BTP, S/4HANA release. Then tiles, links, generators shown in this blogs, page would be updated accordingly with new releases. Update you ADT to latest version when a new update comes up to see new changes to this page.

RAP: Numbering | Early numbering | Late numbering | Managed numbering

2025-04-21T09:38:17.384000+02:00

Numbering

Road Map for Learning Numbering in RAP

Early numbering:

The numbering type early numbering refers to an early value assignment for the primary key field. In this case, the final key value is available in the transactional buffer instantly after the MODIFY request for CREATE.

1. External Early Numbering:

consumer provides key
Key should be unique
key should be editable in create, and non-editable in modify. syntax:

2. Managed Internal Early Numbering:

Managed early numbering is only possible for key fields with ABAP type raw (16) (UUID) of BOs with

implementation type managed.

UUID is read-only. syntax:

3. Unmanaged Internal Early Numbering:

Unmanaged Early Numbering is available in Managed and Unmanaged Implementation Scenarios with Draft Capabilities
Key is read-only. Syntax:

Bdef:

Local handler class:

Late numbering:

The RAP runtime engine assigns values to the primary key fields.
In the ABAP behaviour pool, the RAP saver method adjust_numbers must be implemented to assign a final primary key value for each entity instance.
The key value for an instance is assigned just before the instance is saved on the database. Thus, a gapless assignment of unique keys is ensured.
Late numbering is available for managed and unmanaged implementation scenarios with and without draft.

Note:

late numbering can't be external, since a consumer can't influence the SAVE sequence after the point of no return.
If draft enabled, it is mandatory that the RAP draft table has an additional key field DRAFTUUID of data type raw (16).

Summary:

passed externally by the application user: External numbering
set internally by the framework: Managed internal
set internally by developer (implementation the FOR-NUMBERING method): Unmanaged Internal

Augmentation Operation in RAP

2025-04-21T10:41:27.204000+02:00

Ever wondered how to set default values for the object page fields during Create Operation in Fiori using RAP at the projection level?

With an augmentation implementation you can add data or modify incoming requests on the projection layer before data reaches the transactional buffer. You can add data to a modify request or issue additional requests by augmenting the operation before the request is passed to the base business object.

Use case

• Defaulting for incoming requests. For example: Populate default values for fields of object page on create operation in Fiori

• Behavior-enabling denormalized fields, for example enabling editing of language dependent fields.

Definition

Augmentation is defined in the projection behavior definition on the relevant operation with the following syntax:

define behavior for Entity [alias AliasedName]
  ..
{
  use create (augment);
  use update (augment); 

  use association AssocName { create (augment); }
  ...
}

Below steps will result you how to populate default values for the object page fields on create operation especially at project layer. That means this default values population is specific to projection not for entire BO.

In your projection behavior ZC_TRAVEL_PROCESSOR_M_XX definition, define augmentation for the create operation.

use create (augment);

2. Add behavior implementation class to the project behavior.

…
define behavior for ZC_TRAVEL_PROCESSOR_M_XX alias Travel
implementation in class zcl_bp_c_travelm_xx
….

3. Click the activation button or use the shortcut Ctrl + F3 to activate the behavior definition.

4. The ADT Quick Fix feature can be used to create implementation class for travel entity.

For this, set the cursor on the class name, and press Ctrl+1 to star the Quick Fix dialog.

Click on create behavior implementation to create the class.

Click Next and Finish to create the class. In Local Types of Class you will see a augmentation operation method created where you need to implement logic to populate default values.

5.In the method implementation paste the below code.

METHOD augment_create.
  
   DATA: travel_create TYPE TABLE FOR CREATE zi_travel_m_xx.

    travel_create = CORRESPONDING #( entities ).
    LOOP AT travel_create ASSIGNING FIELD-SYMBOL(<travel>).
      <travel>-agency_id = '070012'.
      <travel>-status  = 'O'.
      <travel>-%control-agency_id = if_abap_behv=>mk-on.
      <travel>-%control-status = if_abap_behv=>mk-on.
    ENDLOOP.

    MODIFY AUGMENTING ENTITIES OF zi_travel_m_xx ENTITY Travel CREATE FROM travel_create.
  ENDMETHOD.

"MODIFY AUGMENTING ENTITIES" is a EML statement with which you can modify entities of base business object. In the above example "ZI_TRAVEL_M_XX" is the base business object and "ZC_TRAVEL_PROCESSOR_M_XX" is the project business object.

6. Save and Activate the Class.

7.Test the app now using preview tool. On Click of Create Agency ID and Status fields are defaulted.

Same behavior can be achieved with determination with draft as well. But what is the difference ?

Note: Only when draft is enabled in BO above feature can be achieved.

SAP BTP OAuth 2.0 Authentication Using Client Credentials in ABAP Environment

2025-04-22T18:37:06.382000+02:00

SAP BTP OAuth 2.0 Authentication Using Client Credentials in ABAP Environment

When working with SAP BTP (Business Technology Platform), securely sending JSON data often requires OAuth 2.0 authentication using the Client Credentials flow (Client ID and Secret Key).

This blog provides a step-by-step guide to setting up OAuth 2.0 communication in the SAP BTP ABAP environment, including creating Communication Scenarios, Communication Arrangements, and executing an outbound HTTP call with JSON payloads.

Step 1: Enable Communication Scenario in ABAP Environment

Open ABAP Development Tools (ADT) in Eclipse.
1. Navigate to Cloud Communication Management.
2. Create a new Outbound Service by assigning a Service Binding and specifying an Outbound Service ID.
3. Outbound Service ID (Default Path Prefix is optional)

Step 2: Create a Custom Communication Scenario

Log in to the SAP Fiori Launchpad on your SAP S/4HANA Cloud system.
1. Open the Custom Communication Scenarios app.
2. Click New and provide a Communication Scenario ID and Description.
3. Add the Outbound Service ID and Publish the scenario.Communication

Step 3: Create a Communication Arrangement

Log in to the SAP Fiori Launchpad on your SAP Cloud system.
Navigate to the Extensibility section and open the Custom Communication Scenarios app.
2.2 Create a Communication System
- Switch to your SAP S/4HANA Cloud system.
- Open the Communication Systems app.
- Create a new communication system and paste the URL as the hostname.
- Enter DUMMY as the Logical System and Business System.
Click New to create a new communication scenario.
Enter values for both the Communication Scenario ID and Description fields.
In the Outbound Services section, add the Outbound Service ID.
Once completed, click Publish to activate the communication scenario.

Now we require a Create a Communication Arrangement:

OAuth 2.0 Settings

Define additional settings if OAuth 2.0 is used for outbound communication

Note:- The propagation of technical users from the cloud application towards on-premises systems can be enabled in the Communication Systems app. To propagate the technical user, you must select the Cloud Conn. Technical User Propagation checkbox in the OAuth 2.0 Settings area (the checkbox is only active if the Cloud Connector switch is on). This is similar to principal propagation, but in this case, a technical user is propagated instead of a business user.

Choose + in the outbound communication user area to create a outbound communication user.
Add Communication System and it will get all the rest details then Go to Outbound Services and add Path and service URL

Choose to Save to save your communication system. And now you can Check the Connection as well

Sample ABAP Code to Send JSON Data via OAuth 2.0

DATA: lv_json            TYPE string, 
      lr_cscn            TYPE if_com_scenario_factory=>ty_query-cscn_id_range,
      http_header_fields TYPE if_web_http_request=>name_value_pairs.

* Format JSON Data
lv_json = '{ "d": { "root": ' && |{ lv_json }| && '} }'.

* Find Communication Arrangement by Scenario ID
lr_cscn = VALUE #( ( sign = 'I' option = 'EQ' low = 'ZCS_OUTBONDXXX' ) ).
DATA(lo_factory) = cl_com_arrangement_factory=>create_instance( ).
lo_factory->query_ca(
  EXPORTING
    is_query           = VALUE #( cscn_id_range = lr_cscn )
  IMPORTING
    et_com_arrangement = DATA(lt_ca)
).

IF lt_ca IS INITIAL.
  EXIT.
ENDIF.

* Select the first available Communication Arrangement
READ TABLE lt_ca INTO DATA(lo_ca) INDEX 1.

* Create HTTP Destination
TRY.
    DATA(lo_http_destination) = cl_http_destination_provider=>create_by_comm_arrangement(
      comm_scenario  = 'Z_CS_OUTBONDXXX',
      service_id     = 'Z_OB_EXPORT_XXX_XXX',
      comm_system_id = lo_ca->get_comm_system_id( )
    ).

    DATA(lo_http_client) = cl_web_http_client_manager=>create_by_http_destination( lo_http_destination ).
    lo_http_client->get_http_request( )->set_text( lv_json ).
    lo_http_client->get_http_request( )->set_header_fields( http_header_fields ).

    DATA(http_response) = lo_http_client->execute( if_web_http_client=>get ).
    DATA(http_status_code) = http_response->get_status( ).

    IF http_status_code-code = '200'.
      * Success Message
      DATA(item_msg) = new_message(
                          id       = 'Zmsg_XXX',
                          number   = '001',
                          severity = cl_abap_behv=>ms-success,
                          v1       = http_status_code-code,
                          v2       = http_status_code-reason
                        ).
      APPEND VALUE #( %msg = item_msg ) TO reported-Z_XXXX_ui.
    ELSE.
      * Authentication failed
      DATA(item_msg2) = new_message(
                           id       = 'Z_XXX',
                           number   = '002',
                           severity = cl_abap_behv=>ms-error,
                           v1       = http_status_code-code,
                           v2       = http_status_code-reason
                        ).
      APPEND VALUE #( %msg = item_msg2 ) TO reported-z_XXXX_ui.
    ENDIF.

  CATCH cx_http_dest_provider_error INTO DATA(lx_http_dest_provider_error).
    DATA(text) = lx_http_dest_provider_error->get_text( ).
  CATCH cx_web_http_client_error.
ENDTRY.

Always implement proper error handling for smooth integration with external systems.

I tried this approach myself — hope it helps!

Introducing the New Pricing and Packaging for SAP Build: A Unified Experience for all Developers

2025-04-29T12:47:47.359000+02:00

As SAP is evolving its Business Suite, AI, and Data Products to meet rising market demands, and as part of this strategy, we are introducing a new exciting, unified commercial model for SAP Build. This updated offering consolidates capabilities for pro-code, low code and AI powered development tools making it easier than ever to build applications and extensions within the SAP ecosystem.

With built-in access to runtime, automation, and extensibility services, SAP Build now empowers both business users and professional developers to choose the right tool set for the right job. The integration of generative AI enhances productivity by streamlining workflows, automating tasks, and accelerating decision-making.

To further support development, SAP Build capabilities along with SAP HANA Cloud are now fully included in SAP S/4HANA Cloud Private Packages empowering customers to handle the majority of their expected scenarios right out of the box. Read the full announcement here.

What changes?

We've heard our customers loud and clear; they asked for simpler licensing, easier provisioning, and a unified toolset. Previously, each SAP Build product like Build Apps, Process Automation, Work Zone, Build Code, and ABAP was licensed separately. This resulted in having lots of different services for customers to manage.

The following list of 14 services from SAP Build have now been consolidated:

SAP Build Services:

SAP Build Work Zone, standard edition
SAP Build Work Zone, advanced edition
SAP Build Process Automation
SAP Task Center
SAP Build Apps
SAP Mobile Services
Application Frontend Service
SAP Business Application Studio

SAP Build Runtime Services:

SAP BTP, Cloud Foundry Runtime
SAP BTP ABAP environment
SAP BTP, Kyma runtime
SAP Document Management Service
SAP Cloud Transport Management
SAP Continuous Integration and Delivery

Now you can access the full range of SAP Build capabilities listed above through just four distinct licenses:

SAP Build base user

This edition is for users who need to access applications, gain insights for day-to-day business needs, and approve tasks. SAP Build base user includes:

Access to digital workspaces
Access web and mobile apps
Request and approve workflow tasks
Access mobile start
1000 API Calls
100 MB Storage

Note: Prerequisite is at least one Build Developer license to manage SAP Build.

SAP Build premium user

This edition is for users who author content, monitor processes, customize pages, and deploy bots. SAP Build premium user includes:

Everything in SAP Build base user, plus
Monitor processes via the dashboard
Deploy attended robotic process automation bots
Author and access workspace content
Visually design digital workspaces and guided experiences
1000 API Calls
100 MB Storage

Note: Prerequisite is at least one Build Developer license to manage SAP Build.

SAP Build developer

This edition is for users who develop application/extensions, workflows, and automations for S/4 and other LoB apps. SAP Build developer includes:

Everything in SAP Build premium user, plus
Build with low-code/no-code developer tools
Develop with code-first developer tools (IDEs)
Create and deploy apps and extensions
Develop and deploy mobile applications
Design and deploy workflows
5000 API Calls
500 MB Storage

SAP Build runtime

Required for application-hosting and lifecycle management services that support the creation and execution for dev/test as well as production environments. SAP Build runtime includes:

SAP BTP, Cloud Foundry runtime
SAP BTP ABAP Environment
SAP BTP, Kyma runtime
Application runtime
Document management storage and API
Cloud transport management
Continuous integration and continuous delivery (CI/CD)

Note: Customers can access applications hosted on runtimes without using any end-user capabilities. This ensures customers aren't charged for user licenses they don’t actively use.

Find detailed information about SAP Build and what’s in scope on the SAP Help Portal.

What are the key benefits of the new SAP Build packaging, and how will it help our customers?

The new SAP Build packaging delivers a streamlined, powerful experience for building extensions, automations, and apps across the SAP ecosystem. Here's how it benefits customers:

Unified Access Across Tools: SAP Build now brings together low-code, pro-code, and AI-powered development tools under a single license removing the complexity of managing multiple products and licenses.
Built-In ERP Integration: SAP Build and SAP HANA Cloud entitlements are now included in SAP Cloud ERP Private Packages, enabling faster innovation and development for SAP S/4HANA Cloud customers.
Empowerment for Developers & Business Users: Both professional developers and key users gain the flexibility to personalize SAP systems with greater speed up to 3x faster, according to
Optimized Cost & Efficiency: A flexible, usage-based runtime model helps reduce total cost of ownership and streamline operational overhead.
Simplified Governance: A unified licensing approach improves compliance management and centralizes governance across all tools.
Business Value First: By removing commercial and technical barriers, organizations can focus more on driving transformation and delivering real business outcomes.

With SAP Build, customers can:

Scale confidently within the SAP ecosystem: Use included licenses to rapidly build compliant extensions that align with SAP standards and scale across the enterprise.
Leverage AI to boost productivity: Automate complex cross-system processes with AI agents, customize Joule with skill-specific tasks, and speed up development using SAP-optimized AI tools.
Deliver faster from front-end to full-stack: Build complete extensions with prebuilt templates, low-code tools, and integrated services like authentication, deployment, and lifecycle management—all on a single, seamless platform.

Commercial Model and Availability

As of 22nd April 2025, SAP Build is available to customers for subscription only. Availability for consumption under BTPEA and PayGo is anticipated by the end of Q2.

Call to action

Visit the SAP Build pricing page to learn more
Help portal documentation
Register for the SAP Build webinar on May 8th
Read the full announcement here
Visit the SAP Discovery Center for more details.
Review pricing on Discovery Center

Enable Multi-Input Field on the Object Page using RAP

2025-04-29T20:46:31.881000+02:00

How to enable Multi-Input Field on the Object Page using RAP?

Lets take a example of Procurement Project Business Object. In the BO there is a field "Company Code" for which multi-input needs to enabled in object page.

Below are the steps to enable above functionality using RAP:

1. Create a custom table with fields "company code" (here companycode is the field of root entity project ) and "procurementprojectuuid" ( here project uuid is the key field of root entity project)

@EndUserText.label : 'Procurement Project Company Code'
@AbapCatalog.enhancement.category : #NOT_EXTENSIBLE
@AbapCatalog.tableCategory : #TRANSPARENT
@AbapCatalog.deliveryClass : #A
@AbapCatalog.dataMaintenance : #RESTRICTED
define table zprocproj_cc {
  key client             : abap.clnt not null;
  key companycode        : bukrs not null;
  procurementprojectuuid : vdm_procurementprojectuuid;

}

2. Create a Interface view for custom table create at step 1.

@AbapCatalog.viewEnhancementCategory: [#NONE]
@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Company COde'
@Metadata.ignorePropagatedAnnotations: true
@ObjectModel.usageType:{
    serviceQuality: #X,
    sizeCategory: #S,
    dataClass: #MIXED
}
define view entity ZI_Company_Code_XX
  as select from zprocproj_cc
  association to parent ZI_PROC_PROJ_XX as _procproj on $projection.procurementprojectuuid = _procproj.Procurementprojectuuid
{
  key companycode,
      procurementprojectuuid,
      _procproj



}

Here "ZI_Company_Code_XX" is the Interface View for CompanyCode custom table and "ZI_PROC_PROJ_XX" is the Root Interface View for Procurement Project BO.

You can also find association to parent relationship from companycode Interface view to root view procurement project.

3. Create 1:N composition relation from root entity to company code interface view which is created in step 2

@AbapCatalog.viewEnhancementCategory: [#NONE]
@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Procument Project Interface View'
@Metadata.ignorePropagatedAnnotations: true
@ObjectModel.usageType:{
    serviceQuality: #X,
    sizeCategory: #S,
    dataClass: #MIXED
}
define root view entity ZI_PROC_PROJ_XX
  as select from mmprocmtproj
  composition [0..*] of zi_proc_plant_xx as _plant
  composition [0..*] of ZI_Company_Code_XX as _CompanyCode
{
  key procurementprojectuuid       as Procurementprojectuuid,
      procurementproject           as Procurementproject,
      procurementprojectname       as Procurementprojectname,
      externalprojectreference     as Externalprojectreference,
      companycode                  as Companycode,
      @Semantics.user.createdBy: true
      createdbyuser                as Createdbyuser,
      @Semantics.user.lastChangedBy: true
      lastchangedbyuser            as Lastchangedbyuser,
      @Semantics.systemDateTime.createdAt: true
      creationdatetime             as Creationdatetime,
      @Semantics.systemDateTime.lastChangedAt: true
      lastchangedatetime           as Lastchangedatetime,
      procurementprojectactvtnsts  as Procurementprojectactvtnsts,
      procmtplanningsubprojectuuid as Procmtplanningsubprojectuuid,
      sourcingorigin               as Sourcingorigin,
      sourcingscenario             as Sourcingscenario,
      iseopblocked                 as Iseopblocked,

      _plant,
      _CompanyCode

}

Here root entity is ZI_PROC_PROJ_XX and it has 1:N composition relationship to child entity ZI_Company_Code_XX.

Make sure you activate ZI_PROC_PROJ_XX and ZI_Company_Code_XX together when you form the business object relationship.

4. Enhance ZI_Company_Code_XX behavior in base BO ZI_PROC_PROJ_XX

managed implementation in class zbp_i_proc_proj_xx unique;
strict ( 2 );
with draft;

define behavior for ZI_PROC_PROJ_XX alias Project
persistent table mmprocmtproj
draft table zprocproj_dxx
lock master
total etag Lastchangedatetime
authorization master ( instance, global )
etag master Lastchangedatetime
with additional save
early numbering
{

  create;
  update;
  delete ( features : global );

  draft action Edit;
  draft action Discard;
  draft action Resume;
  draft action Activate;
  draft determine action Prepare
  {

    validation validate_companycode;
  }



  //field ( numbering : managed ) Procurementprojectuuid;


  //  field ( mandatory ) Companycode;
  field ( readonly : update ) Externalprojectreference;
  field ( readonly ) Sourcingscenario;
  //field ( mandatory : create, readonly : update ) Procurementproject;  //V4

  field ( features : instance ) Procurementproject;

  association _plant { create; with draft; }
  association _CompanyCode { create; with draft; }

  action ( features : instance ) setactive parameter zabstract_project_xx result [1] $self;


  validation validate_companycode on save { field Companycode; }

  determination set_status on modify { create; }

  determination set_project_key on save { create; }

  mapping for mmprocmtproj corresponding
  {
    Lastchangedatetime = lastchangedatetime;
  }
}

define behavior for zi_proc_plant_xx alias Plant
//persistent table mmpprojplant
draft table zprocplantd_xx
lock dependent by _project
authorization dependent by _project
//etag master <field_name>
with unmanaged save
{
  update;
  delete;

  field ( numbering : managed ) procmtprojectplantuuid;
  field ( readonly ) Procurementprojectuuid;
  association _project { with draft; }
}

define behavior for ZI_Company_Code_XX alias CompanyCode
persistent table zprocproj_cc
draft table zprocproj_ccd
lock dependent by _procproj
authorization dependent by _procproj
{
  update;
  delete;
  field ( readonly ) Procurementprojectuuid;

  association _procproj { with draft; }
}

What additions are added in the above behavior:

1. define behavior for ZI_Company_Code_XX

2. association _CompanyCode { create; with draft; } in root behavior ZI_PROC_PROJ_XX

3. draft table zprocproj_ccd created using quick fix.

5. Create a projection view ZC_PROC_CC_XX for interface view ZI_Company_Code_XX created in step 2

@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Procement Project CC Projection View'
@Metadata.ignorePropagatedAnnotations: true
define view entity ZC_PROC_CC_XX as projection on ZI_Company_Code_XX
{
    key companycode,
    procurementprojectuuid,
    /* Associations */
    _procproj : redirected to parent ZC_PROC_PROJ_XX
    
}

Here "_procproj : redirected to parent ZC_PROC_PROJ_XX" relation is formed to root projection entity ZC_PROC_PROJ_XX

6. Create a relation from root project projection view ZC_PROC_PROJ_XX to company code project view zc_proc_cc_xx.

_CompanyCode : redirected to composition child zc_proc_cc_xx,

Make sure you activate ZC_PROC_PROJ_XX and zc_proc_cc_xx together when you form the business object relationship.

7. Enhance projection Company code behavior ZC_PROC_CC_XX in projection

projection;
strict ( 2 );
use draft;
define behavior for ZC_PROC_PROJ_XX //alias <alias_name>
implementation in class zcl_proc_proj_c_xx unique
use etag
{
  use create ( augment, precheck );
  use update;
  use delete;


  use action Edit;
  use action Resume;
  use action Activate;
  use action Prepare;
  use action Discard;

  use action setactive;

  use association _plant { create; with draft; }
  use association _CompanyCode { create; with draft; }
}

define behavior for ZC_PROC_PLANT_XX //alias <alias_name>
{
  use update;
  use delete;

  use association _project { with draft; }
}

define behavior for ZC_PROC_CC_XX
{
  use update;
  use delete;
  use association _procproj { with draft; }

}

What additions are added in the above behavior:

1. define behavior for ZC_PROC_CC_XX

2. use association _CompanyCode { create; with draft; } in root behavior ZC_PROC_PROJ_XX

8. Expose company code projection view ZC_PROC_CC_XX service definition.

@EndUserText.label: 'Service Binding for Procurement Project'
define service ZSD_PROC_PROJ_XX {
  expose ZC_PROC_PROJ_XX as ProcurementProject;
  expose ZC_PROC_PLANT_XX as ProcurementPlant;
  expose ZC_PROC_CC_XX as ProcurementCC;
}

Here "expose ZC_PROC_CC_XX as ProcurementCC;" added.

9. Enhance the metadata extension of root view ZC_PROC_PROJ_XX

  : { lineItem:       [ { position: 70, importance: #HIGH, value: '_CompanyCode.companycode' }
                 ] }
  .identification: [{ position: 70, importance: #HIGH, value: '_CompanyCode.companycode' }]
  _CompanyCode;

Here association _CompanyCode; is exposed in metadata extension and value property '_CompanyCode.companycode' is added to @ui.linetem and @ui.identification annotation.

10. Now preview the UI.

Now multi-input is enabled for company code field in Object page.

On save in display mode it appears like below:

In list page field it displays like below:

New Mass-Upload of Test Cases in SAP Cloud ALM

2025-04-30T09:15:29.630000+02:00

New Mass-Upload of Test Cases in SAP Cloud ALM

It is now possible to upload a large number of test cases to SAP Cloud ALM using the mass upload feature.
With this blog post I briefly describe the process.

1. Click on the Test Preparation app

2. Navigate to the "Upload Button"

3. Download the template to fill it with your test cases

4. Perform the upload

Ideas and input for SAP

What would certainly be helpful is downloading existing test cases in SAP Cloud ALM, editing them in Excel, and uploading them again.
The exchange and reuse of test cases between multiple SAP Cloud ALM projects would also be helpful.
SAP should also consider the easy storage of test cases from multiple projects into a central operational project. This is a requirement I hear from many customers.

Conclusion

In any case, the new mass upload of test cases is a very helpful feature and a first big step in the right direction.

It saves us a lot of time and makes test management much more efficient.

Thank you SAP for providing this functionality.

SAP BTP ABAP Environment - Switch to DigiCert G5 Root Certificate Authority

2025-04-30T17:37:27.896000+02:00

Current server certificates for the domains of the SAP BTP ABAP Environment (aka "Steampunk") are issued by the DigiCert G2 Root Certificate Authority (CA). Based on current recommendations, SAP is switching to the DigiCert TLS RSA4096 Root G5 CA, see SAP Note 3566727 for more details. This switch applies to the SAP BTP Cloud Foundry Environment, to the SAP BTP ABAP Environment, and to other SAP services. New regions of the SAP BTP ABAP Environment from Q1 2025 are already set up with the DigiCert G5 Root CA. For existing regions of the SAP BTP ABAP Environment, the switch from the DigiCert G2 Root CA to the DigiCert G5 Root CA is currently planned for Q3/2025.

Call to Action

Inbound Connections

If you manage trust stores of client applications/services, which connect to your SAP BTP ABAP Environment instance(s), by yourself, then add the DigiCert TLS RSA4096 Root G5 CA to these trust stores to ensure that your applications/services still can connect to the SAP BTP ABAP Environment instance(s) when the new server certificates are used. This applies to all supported protocols.

Since different (external) client applications / services are using different technical implementations for such trust stores, we cannot provide detailed instructions how to configure these trust stores.

Outbound Connections

For outbound connections from your SAP BTP ABAP Environment instances, for example, towards other services in SAP BTP Cloud Foundry environment, please check the trust settings for the DigiCert TLS RSA4096 Root G5 CA via the Maintain Certificate Trust List application. Since some releases, the Automatic Trust List Update feature is enabled and new certificates from the SAP trust list should have been added automatically to the trust store. If the CA is not contained in the list, click on Check for Updates and add the certificate, or add it manually. You can also download it here.

References

SAP Note 3566727 : Root Certificate Replacement in the SAP BTP, Cloud Foundry Environment
Blog Post: SAP BTP Cloud Foundry: Switching to higher security level Root Certificate Authority
Blog Post: SAP BTP ABAP Environment – New Root Certificate Authority
Github: Trust Store for SAP BTP

SAP Community Escape House for May - ABAP Cloud

2025-05-01T09:00:00.029000+02:00

Welcome to the Developer Challenge for the Month of May!!!! The 👉 SAP Community Escape House has a new addition!!

Hope you all escaped alive from the SAP Build Escape House last month 😀 . So now let us relax by extending our living room this month.

SAP Community Escape House

We will be focusing on ABAP with an emphasis on Extensibility. Like previous challenges, we will explore a crucial topic that allows customers and partners to tailor SAP standard software to their business needs. Extensibility covers various aspects, including:

Adjusting software behaviour beyond standard configurations.
Extending the data model.
Exposing additional data.
Modifying UI layouts, forms, and reports.
Creating new UI elements and applications.

You can get more details on Extensibility and the various options available by watching this video: https://www.youtube.com/watch?v=IPEotH-6ekI&t=786s

Task 0 – Preparation

We hope all of you might remember the 2024 ABAP Developer Challenge which was focused on ABAP CDS where we had created an end to end Fiori List Report from a database table. This year will take a further step and explore developer extensibility on the same Travel demo data.

Refer Task0 of the 2024 ABAP Developer Challenge to complete the prerequisites.
Create the objects mentioned in the readme.md file in SAP GitHub Repository for the base data model which will be extended.
Now you will have a table, a structure, a view and a data generator class.

For this year, all SAP Developer Challenges created by the Developer Advocates will happen in the SAP Community Escape House (shout out to @nicoschoenteich for his amazing creativity). Each month we will unlock a new room in the house with a specific focus. Completing a challenge means successfully escaping the room by solving a series of coding – or no-code – tasks/questions. This month let us explore ABAP Extensibility.

Here are the links to our previous challenges:

January: UI5
February: Integration Suite
March: AI
April : Build

How to participate

Visit the SAP Community Escape House and enter your numeric SAP Community user ID.

If you don't know your user ID, click Need Help? This will display a link to your community settings page.

Then you will see your ID here:

Once you see the SAP Community Escape House, select the ABAP Living Room.

SAP Community Escape House - Available rooms

The user interface of an escape room includes the room itself as well as a terminal. You can click the objects in the room to receive tips. Like in a real (physical) escape room, you will have to try out a few things and explore the room until you receive helpful tips and, eventually, instructions. These tips and instructions are printed in the terminal next to the room. The terminal is also used to submit solutions to tasks. Read the instructions you receive carefully to understand how.

SAP Community Escape House - ABAP room

If you successfully escape the room (you will know when that happens), you will receive a badge in the SAP Community. We will assign the badges once the challenge closes.

The schedule

The ABAP room will be unlocked on May 5th and will stay unlocked until the end of the year. However, the challenge closes on May 31st, so you will have to escape the room until then to qualify for a badge. Unlike the previous year, this SAP Developer Challenge does not consist of weekly sub-challenges. The next room (next challenge) will be unlocked in June.

Useful links for the challenge

Good luck and happy escaping!

AMDP Class - Database procedure

2025-05-05T10:31:42.902000+02:00

AMDP Class

An AMDP (ABAP Managed Database Procedure) class is used to write complex logic directly in the SAP HANA database using SQL Script, instead of writing everything in ABAP.

This helps to:

Improve performance by processing data inside the database.
Reduce load on the application layer.
Speed up reports and data-heavy programs.

Open Eclipse.

Step 1: Create a package.

Give basic properties.

Select Transpost request.

STEP2 : Create AMDP class

The class will be like below.

To convert the normal class into the AMDP class, use the interface IF_AMDP_MARKER_HDB

Create class attributes, and to implement the method, click on CTRL+1.

The AMDP procedure will run on HANA DB. The memory location is not available at the database level. It is only available at the application level, so we have to pass the parameter with a pass-by value.

Two Types of AMDP Methods :

In AMDP, we can write two types of methods:

Database Procedure

This is a normal AMDP method written in SQL Script.
It can be used to read or modify data.
Called directly from ABAP like a regular method

Database Function (Table Function)

This is used with CDS Views to return a result set like a virtual table.
Implemented using an AMDP method, but used as a function in CDS.
Always read-only.

Here we will see Database Procedure.

To convert the method to the AMDP method.

To convert the normal method to the AMDP method write some code to the implementation part of methods.

Specify the target database in which you want to create the database procedure, along with the database language to be used. Additionally, list all the objects (such as tables, views, procedures, etc.) that need to be accessed within the specified schema.

2.AMDP procedure is not implicit in client handling. So, we need one more parameter to pass the client.

An error will occur when using the Database table in the AMDP method.

Step 3:

Create a program to consume the AMDP class.

Search PROGRAM and select ABAP program.

Write the below code.

Output :

Conclusion:

AMDP procedures are a powerful way to push complex logic to the SAP HANA database, allowing you to handle large volumes of data more efficiently.

Use AMDP procedures when:

You want to improve performance with code pushdown.
You need to process data-heavy logic directly in HANA.
You want to keep your ABAP code clean and efficient.

Customer & Partner Roundtable for SAP BTP ABAP Environment #23 - demo time in ADT

2025-05-07T11:19:49.506000+02:00

👉 The call for contributions for one of the upcoming roundtables is open!

If you want to show a demo or share a use case scenario for SAP BTP ABAP Environment send us an email and we will get back to you.

Introduction

As SAP BTP ABAP environment (aka Steampunk) and ABAP Cloud became more popular inside and outside of SAP, there is a high demand for rolling out the latest product news and updates, asking questions, and showing demos.

💡 You can find the slides presented, recordings, and further references from the previous roundtables in this GitHub repository.

Meeting Information

When:

May 20th, 10:00 - 11:00 AM CET – Zoom Meeting (please register in advance)

Who:

All interested customers, partners, and stakeholders are invited to join this roundtable
BTP ABAP team:
- Frank Jentsch (Product Lead for SAP BTP ABAP Environment)
- Iwona Hahn (Product Management)
- Nora Klemp (Product Management)
- Shyam Balachandran (Development Expert)
- Dr. Oliver Brein (Development Expert)
- Simon Dold (Developer)

Preliminary Agenda:

Product update for SAP BTP ABAP Environment release 2505
Demos in ABAP Development Tools (ADT):
- Quick Fiori app generation (Shyam Balachandran)
- Swagger support for OData services (Shyam Balachandran)
- UX improvements of generator framework (Shyam Balachandran)
- HANA PLV tracing incl. SQL statement viewer in ADT Cross Trace (Dr. Oliver Brein)
- Enhancements of Manage Software Components app (Simon Dold)
Q&A

Looking forward to meeting you!

Check out our SAP Business Technology ABAP Environment page in SAP Community for product updates and upcoming events.

@UI.dataPoint with Comparison Field in RAP

2025-05-08T09:37:12.601000+02:00

@ui.dataPoint

In RAP (Restful ABAP Programming Model), the @ui.dataPoint annotation is used to define how individual fields should be presented in a UI, especially in SAP Fiori Elements applications

This annotation provides semantic metadata for a field such as:

Title
Criticality (status-based coloring)
Visualization (e.g., progress bar)
Target or forecast values

It is commonly used in object pages, analytical cards, or list reports to visually highlight important values.

Use Case: Data Point with Comparison Field

We will walk through how to dynamically control the color of a field (e.g., Fees) using a comparison field.

Step1 : Create a comparison field .

In your root CDS view, define a derived field based on some logic to act as the criticality field

Step2 : Annotate in Metadata Extension

In the metadata extension of the root view, annotate the field using @ui.dataPoint.

Key properties:

Type : #AS_DATAPOINT
Title : Display label for the field
Qualifier: Uniquely identifies the data point (if multiple exist)
Visualization: Display the field appearance in UI.
Criticality: Reference to your comparison field that controls the color

Step 3: Implement Behavior and Service Layers

To expose this in Fiori:

Define a behavior definition (for managed or unmanaged BO).
Create a service definition for the CDS view.
Bind it to a service binding (e.g., for OData V4 / Fiori Elements).

🎯 Output :

The Fees field will be displayed:

With dynamic color based on the comparison field value:

🟢 Green — Positive
🟠 Orange — Critical
🔴 Red — Negative

Object page.

List Page:

Based on the comparison of the field value the Fees field color will be changed.

Green.

Red.

Orange.

Conclusion:

By leveraging @ui.dataPoint, developers can deliver data-rich, visually intuitive, Fiori-compliant UIs directly from the backend using CDS views—without needing to build custom front-end logic.

This enhances both developer productivity and end-user experience in Fiori Elements apps.

SAP Community - SAP BTP, ABAP environment

Free SAP BTP - Free ABAP System instance

RAP: Augmentation

Connecting Multiple Databases and OData Services to SAP BTP using BAS

Introduction

Summary

Steps to Connect Multiple OData Services

Step 1: Add Data Sources in UI5 Application

Step 2: Configure Models in manifest.json

Step 3: Configure ui5.yaml for Backend Connections

Conclusion

Update/Modify any Table data dynamically

SDT Using SAP Business Transformation Center: End to End Process & Technical Configuration

RAP: MANAGED VS UNMANAGED RAP

Unleashing the Power of ASTER: Scripting Your Way to Enhanced SAP Integration Testing

What is ASTER?

Why ASTER? The Story Behind the Script

The Technology Behind ASTER

Key Features of ASTER

Getting Started with ASTER

Where to Play with ASTER

Extending Int4 Suite with ASTER

The Future of ASTER

Kudos

Conclusion

Performance comparison: FILTER vs LOOP vs FOR

Methodology

ECC tests

Results: sorted table, 1000 executions

Results: standard table, 1000 executions

BTP Steampunk Test

Results: Standard Table, 1000 Executions

Results: Sorted key, 1000 Executions

Conclusions

On ECC with sorted keys:

On BTP with sorted keys:

Others:

Discussion

Proof for Point 2 in Methodology

ABAP Cloud Landing Page in ABAP Development Tools (ADT)

RAP: Numbering | Early numbering | Late numbering | Managed numbering

Road Map for Learning Numbering in RAP

1. External Early Numbering:

2. Managed Internal Early Numbering:

3. Unmanaged Internal Early Numbering:

Late numbering:

Note:

Summary:

Augmentation Operation in RAP

Use case

Definition

SAP BTP OAuth 2.0 Authentication Using Client Credentials in ABAP Environment

SAP BTP OAuth 2.0 Authentication Using Client Credentials in ABAP Environment

Step 1: Enable Communication Scenario in ABAP Environment

Open ABAP Development Tools (ADT) in Eclipse.

Step 2: Create a Custom Communication Scenario

Step 3: Create a Communication Arrangement

2.2 Create a Communication System

Sample ABAP Code to Send JSON Data via OAuth 2.0

Introducing the New Pricing and Packaging for SAP Build: A Unified Experience for all Developers

Enable Multi-Input Field on the Object Page using RAP

New Mass-Upload of Test Cases in SAP Cloud ALM

New Mass-Upload of Test Cases in SAP Cloud ALM

1. Click on the Test Preparation app

2. Navigate to the "Upload Button"

3. Download the template to fill it with your test cases

4. Perform the upload

Ideas and input for SAP

Conclusion

SAP BTP ABAP Environment - Switch to DigiCert G5 Root Certificate Authority

Call to Action

Inbound Connections

Outbound Connections

References

SAP Community Escape House for May - ABAP Cloud

Task 0 – Preparation

How to participate

The schedule

Useful links for the challenge

AMDP Class - Database procedure