SAP Community - ABAP Development

Service Catalog - Long text mass upload (ML01/ML02/ML03 Editor)

2026-03-24T10:40:00.160000+01:00

Upload Long Text for Service Catalog (ML01/ML02/ML03) using ABAP – Complete Guide with Working Solution

Introduction

Uploading Long Text (Lg Text) for Service Catalog in SAP (Transactions ML01 / ML02 / ML03) is not straightforward.

Even if you use SAVE_TEXT, you may face issues like:

Only the first line gets updated
Remaining lines are ignored
Text appears incorrectly in ML03
No clear error message

👉 The root cause is not your code, but a hidden SAP design detail that is rarely documented.

This blog explains everything end-to-end:

Data model
Common mistakes
Root cause analysis
Fully working ABAP solution

⚠️ Prerequisite

Before uploading Long Text, ensure:

✔ Service Catalog already exists
✔ Service lines are present in the system
✔ Entries are available in table ESLZ

🔍 Why this is mandatory?

Long Text is linked with:

Service Type (LBNUM)
Edition (AUSGB)
Line (ZEILE)

👉 If ZEILE does not exist in ESLZ, the text:

Will not be visible in ML03
May get stored but not linked

🧠 Understanding the Data Model

1️⃣ ESLZ Table (Structure Only)

Stores service lines
Contains hierarchy (Block, Sub-lines)
DOES NOT store long text

2️⃣ Long Text Storage

Long Text is stored using SAPscript:

Table Purpose

STXH	Text Header
STXL	Text Lines

🔥 Text Key Mapping

Field Value

TDOBJECT	ESLZ
TDID	LTXT
TDNAME	LBNUM + AUSGB + ZEILE

📊 Example Scenario

Excel Input

Service Edition Line Block TDLINE

001	2004	0000000004	0000000004	Test abc 4
001	2004	0000000005	0000000004	Test abc 5
001	2004	0000000006	0000000004	Test abc 6

Expected Output in ML03

Line 4 → Test abc 4  
Line 5 → Test abc 5  
Line 6 → Test abc 6

❌ Common Mistake (Root Cause)

Many implementations use:

GROUP BY lbnumm ausgb blknr.

Why this fails?

BLKNR = Block level
SAP stores text at LINE level (ZEILE)

Result:

❌ Only first text visible
❌ Remaining lines ignored
❌ Incorrect mapping in ML03

💥 Root Cause Explained

SAP Service Catalog Long Text is maintained per LINE (ZEILE), not per BLOCK (BLKNR)

✅ Correct Approach

✔ Process data line-wise (ZEILE)
✔ Generate text key using ZEILE
✔ Avoid grouping by BLKNR

💻 Complete Working ABAP Code

Below is a complete ABAP report which program to upload Service catalog long text, using Excel file upload.

*&---------------------------------------------------------------------*
*& Report ZPR_SERVICE_CAT_UPLOAD
*&---------------------------------------------------------------------*
*&
*&---------------------------------------------------------------------*
REPORT zpr_service_cat_upload.


*---------------------------------------------------------------------*
* TYPES
*---------------------------------------------------------------------*
TYPES: BEGIN OF ty_excel,
         lbnumm   TYPE eslz-lbnum,
         ausgb    TYPE eslz-ausgb,
         zeile    TYPE eslz-zeile, "added on 23rd march
         sortn    TYPE eslz-sortn, "added on 23rd march
         blknr    TYPE eslz-blknr,
         meins    TYPE eslz-meins, "added on 23rd march
         tdformat TYPE tline-tdformat,
         tdline   TYPE tline-tdline,
         seq      TYPE i,
       END OF ty_excel.

DATA: gt_excel TYPE STANDARD TABLE OF ty_excel,
      gs_excel TYPE ty_excel.

*---------------------------------------------------------------------*
* RESULT STRUCTURE
*---------------------------------------------------------------------*
TYPES: BEGIN OF ty_result,
         icon    TYPE icon_d,
         lbnumm  TYPE eslz-lbnum,
         status  TYPE char10,
         message TYPE string,
       END OF ty_result.

DATA: gt_result TYPE STANDARD TABLE OF ty_result,
      gs_result TYPE ty_result.

CONSTANTS:
  gc_sheet_exclude TYPE string VALUE 'Sheet1'.

*---------------------------------------------------------------------*
* SELECTION SCREEN
*---------------------------------------------------------------------*
PARAMETERS: p_file TYPE string OBLIGATORY.

*---------------------------------------------------------------------*
* F4 HELP
*---------------------------------------------------------------------*
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.

  DATA: lt_filetab TYPE filetable,
        lv_rc      TYPE i.

  CALL METHOD cl_gui_frontend_services=>file_open_dialog
    CHANGING
      file_table = lt_filetab
      rc         = lv_rc.

  IF lv_rc > 0.
    READ TABLE lt_filetab INTO DATA(ls_file) INDEX 1.
    p_file = ls_file-filename.
  ENDIF.

*---------------------------------------------------------------------*
* START-OF-SELECTION
*---------------------------------------------------------------------*
START-OF-SELECTION.

  PERFORM read_excel.
  PERFORM upload_texts.

*---------------------------------------------------------------------*
* READ EXCEL
*---------------------------------------------------------------------*
FORM read_excel.

  DATA: lo_excel         TYPE REF TO cl_fdt_xl_spreadsheet,
        lv_xstring       TYPE xstring,
        lt_raw           TYPE solix_tab,
        lv_len           TYPE i,
        lv_worksheetname TYPE string,
        lt_worksheets    TYPE string_table,
        lo_data          TYPE REF TO data.

* Upload file
  CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename   = p_file
      filetype   = 'BIN'
    IMPORTING
      filelength = lv_len
    TABLES
      data_tab   = lt_raw.

  CALL FUNCTION 'SCMS_BINARY_TO_XSTRING'
    EXPORTING
      input_length = lv_len
    IMPORTING
      buffer       = lv_xstring
    TABLES
      binary_tab   = lt_raw.

* Create Excel object
  TRY.
      CREATE OBJECT lo_excel
        EXPORTING
          document_name = p_file
          xdocument     = lv_xstring.
    CATCH cx_fdt_excel_core.
      MESSAGE 'Error reading Excel file' TYPE 'E'.
  ENDTRY.

  lo_excel->if_fdt_doc_spreadsheet~get_worksheet_names(
    IMPORTING worksheet_names = lt_worksheets ).

  DELETE lt_worksheets WHERE table_line = gc_sheet_exclude.

  READ TABLE lt_worksheets INTO lv_worksheetname INDEX 1.
  IF sy-subrc <> 0.
    MESSAGE 'Worksheet not found' TYPE 'E'.
  ENDIF.

  lo_data = lo_excel->if_fdt_doc_spreadsheet~get_itab_from_worksheet(
               worksheet_name = lv_worksheetname ).

* Convert to internal table
  CALL FUNCTION 'Z_XLS_INTO_ITAB'
    EXPORTING
      header      = 'X'
      str         = 'ZTS_SC_EXCEL'
      iv_data_ref = lo_data
      hdr_len     = '1'
    IMPORTING
      it_xls_data = gt_excel.

  IF gt_excel IS INITIAL.
    MESSAGE 'No data found in Excel file' TYPE 'E'.
  ENDIF.

ENDFORM.

*---------------------------------------------------------------------*
* UPLOAD TEXTS
*---------------------------------------------------------------------*
FORM upload_texts.

  DATA: lt_grouped TYPE SORTED TABLE OF ty_excel
                      WITH UNIQUE KEY lbnumm ausgb blknr,
        ls_group   TYPE ty_excel.


* Sort properly
  SORT gt_excel BY lbnumm ausgb blknr seq.

** Grouping loop (modern syntax)
*  SORT gt_excel BY lbnumm ausgb blknr seq.

"commented on 23.03

*  LOOP AT gt_excel INTO DATA(ls_excel)
*       GROUP BY ( lbnumm = ls_excel-lbnumm
*                  ausgb  = ls_excel-ausgb
*                  zeile  = ls_excel-zeile
*                  blknr  = ls_excel-blknr )
*       ASCENDING
*       ASSIGNING FIELD-SYMBOL(<group>).
*
*    DATA: lt_lines       TYPE STANDARD TABLE OF tline,
*          lt_group_lines TYPE STANDARD TABLE OF ty_excel,
*          ls_header      TYPE thead.
*
**--- Build NAME (with ALPHA)
*    DATA(lv_lbnumm) = |{ <group>-lbnumm ALPHA = IN }|.
*    DATA(lv_ausgb)  = <group>-ausgb.
*    DATA(lv_blknr)  = |{ <group>-blknr ALPHA = IN }|.
*
**    DATA(lv_name) = lv_lbnumm && lv_ausgb && lv_blknr.
*    DATA lv_name TYPE thead-tdname.
*
*    lv_name = lv_lbnumm && lv_ausgb && lv_blknr.
*
**--- Step 1: Move group data into internal table
*    lt_group_lines = VALUE #( FOR wa IN GROUP <group> ( wa ) ).
*
**--- Step 2: Sort by SEQ (VERY IMPORTANT)
*    SORT lt_group_lines BY seq.
*
**--- Step 3: Prepare ALL lines
*    CLEAR lt_lines.
*
*    LOOP AT lt_group_lines INTO DATA(ls_line_data).
*
*      IF ls_line_data-tdline IS NOT INITIAL.
*        APPEND VALUE tline(
*          tdformat = ls_line_data-tdformat                     " <-- FIX
*          tdline   = ls_line_data-tdline ) TO lt_lines.
*      ENDIF.
*
*    ENDLOOP.
*
**--- Header
*    ls_header = VALUE thead(
*        tdobject = 'ESLZ'
*        tdname   = lv_name
*        tdid     = 'LTXT'
*        tdspras  = sy-langu ).
*
*
*
**--- Save text (overwrite mode)
*    CALL FUNCTION 'SAVE_TEXT'
*      EXPORTING
*        header = ls_header
**       insert = space
*        insert = space
*       savemode_direct = 'X'
*      TABLES
*        lines  = lt_lines
*      EXCEPTIONS
*        OTHERS = 1.
*
**--- Result handling
*    DATA(ls_result) = VALUE ty_result(
*        lbnumm = <group>-lbnumm ).
*
*    IF sy-subrc <> 0.
*
*      DATA lv_msg TYPE string.
*
*      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
*        INTO lv_msg
*        WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
*
*      ls_result-status  = 'ERROR'.
*      ls_result-message = lv_msg.
*      ls_result-icon    = '@5C@'.
*
*    ELSE.
*
*
**      CALL FUNCTION 'COMMIT_TEXT'
**        EXPORTING
**          object           = ls_header-tdobject
**          name             = ls_header-tdname
**          id               = ls_header-tdid
**          language         = sy-langu
***         savemode_direct  = abap_true.
*          ls_result-status = 'SUCCESS'.
*      ls_result-message = 'Text Saved Successfully'.
*      ls_result-icon    = '@5B@'.
*
*    ENDIF.
*
*    APPEND ls_result TO gt_result.
*
*  ENDLOOP.
*
*  COMMIT WORK.

"commented on 23.03

  DATA: lt_lines  TYPE STANDARD TABLE OF tline,
        ls_header TYPE thead,
        ls_result TYPE ty_result.

  LOOP AT gt_excel INTO DATA(ls_excel).

*--- Build TEXT NAME using ZEILE (IMPORTANT FIX)
    DATA(lv_lbnumm) = |{ ls_excel-lbnumm ALPHA = IN }|.
    DATA(lv_ausgb)  = ls_excel-ausgb.
    DATA(lv_zeile)  = |{ ls_excel-zeile ALPHA = IN }|.

    DATA(lv_name) = lv_lbnumm && lv_ausgb && lv_zeile.

*--- Prepare text lines (single line per ZEILE)
    CLEAR lt_lines.

    IF ls_excel-tdline IS NOT INITIAL.
      APPEND VALUE tline(
        tdformat = ls_excel-tdformat
        tdline   = ls_excel-tdline ) TO lt_lines.
    ENDIF.

*--- Header
    ls_header = VALUE thead(
      tdobject = 'ESLZ'
      tdname   = lv_name
      tdid     = 'LTXT'
      tdspras  = sy-langu ).

*--- Clear result
    CLEAR ls_result.
    ls_result-lbnumm = ls_excel-lbnumm.

*--- SAVE TEXT
    CALL FUNCTION 'SAVE_TEXT'
      EXPORTING
        header          = ls_header
        insert          = space
        savemode_direct = 'X'
      TABLES
        lines           = lt_lines
      EXCEPTIONS
        OTHERS          = 1.

*--- Handle result
    IF sy-subrc <> 0.

      DATA: lv_msg TYPE string.

      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
        INTO lv_msg
        WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

      ls_result-status  = 'ERROR'.
      ls_result-message = lv_msg.
      ls_result-icon    = '@5C@'.

    ELSE.

      ls_result-status  = 'SUCCESS'.
      ls_result-message = |Text saved for line { ls_excel-zeile }|.
      ls_result-icon    = '@5B@'.

    ENDIF.

    APPEND ls_result TO gt_result.

  ENDLOOP.

*--- Final commit
  COMMIT WORK.

  PERFORM display_alv.


ENDFORM.

*---------------------------------------------------------------------*
* DISPLAY ALV
*---------------------------------------------------------------------*
FORM display_alv.

  DATA: lt_fieldcat TYPE slis_t_fieldcat_alv,
        ls_fieldcat TYPE slis_fieldcat_alv,
        ls_layout   TYPE slis_layout_alv.

* ICON
  CLEAR ls_fieldcat.
  ls_fieldcat-fieldname = 'ICON'.
  ls_fieldcat-icon      = 'X'.
  ls_fieldcat-seltext_m = 'Status'.
  APPEND ls_fieldcat TO lt_fieldcat.

* LBNUM
  CLEAR ls_fieldcat.
  ls_fieldcat-fieldname = 'LBNUMM'.
  ls_fieldcat-seltext_m = 'Package'.
  APPEND ls_fieldcat TO lt_fieldcat.

* STATUS
  CLEAR ls_fieldcat.
  ls_fieldcat-fieldname = 'STATUS'.
  ls_fieldcat-seltext_m = 'Status'.
  APPEND ls_fieldcat TO lt_fieldcat.

* MESSAGE
  CLEAR ls_fieldcat.
  ls_fieldcat-fieldname = 'MESSAGE'.
  ls_fieldcat-seltext_m = 'Message'.
  APPEND ls_fieldcat TO lt_fieldcat.

  ls_layout-zebra = 'X'.

  CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_callback_program = sy-repid
      is_layout          = ls_layout
      it_fieldcat        = lt_fieldcat
    TABLES
      t_outtab           = gt_result.

ENDFORM.  


Function Module to read Excel sheet into internal table - 
FUNCTION z_xls_into_itab.
*"----------------------------------------------------------------------
*"*"Local Interface:
*"  IMPORTING
*"     REFERENCE(P_FILE) TYPE  RLGRAP-FILENAME OPTIONAL
*"     REFERENCE(HEADER) TYPE  CHAR1 DEFAULT 'X'
*"     REFERENCE(STR) TYPE  CHAR30 OPTIONAL
*"     REFERENCE(IV_DATA_REF) TYPE REF TO  DATA OPTIONAL
*"     VALUE(HDR_LEN) TYPE  SYST_TABIX OPTIONAL
*"  EXPORTING
*"     REFERENCE(IT_XLS_DATA) TYPE  STANDARD TABLE
*"  TABLES
*"      T_FILE STRUCTURE  ALSMEX_TABLINE OPTIONAL
*"----------------------------------------------------------------------

  TYPE-POOLS: abap,slis.
  FIELD-SYMBOLS:<dy_table> TYPE STANDARD TABLE,
   <fs_current_field>,
   <wa_str>,<wa_temp>
  .
  DATA:new_line      TYPE REF TO data,
       new_line2     TYPE REF TO data,
       li_fieldcat   TYPE lvc_t_fcat,
       dy_table      TYPE REF TO data,
* t_file      TYPE STANDARD TABLE OF alsmex_tabline,
       wa_file       TYPE alsmex_tabline,
       v_col         TYPE i,
       begin_row     TYPE i,
       zls_alsm_data TYPE zts_alsmex_tabline.

********This will provide Fields in Row format of Structure created(which should be similar to Excel Format).
  CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
    EXPORTING
      i_structure_name       = str
    CHANGING
      ct_fieldcat            = li_fieldcat
    EXCEPTIONS
      inconsistent_interface = 1
      program_error          = 2
      OTHERS                 = 3.

  IF sy-subrc EQ 0.

********This will create internal table which will have fields as per the Excel Format.
    CALL METHOD cl_alv_table_create=>create_dynamic_table
      EXPORTING
        it_fieldcatalog           = li_fieldcat
        i_length_in_byte          = 'X'
      IMPORTING
        ep_table                  = dy_table
      EXCEPTIONS
        generate_subpool_dir_full = 1
        OTHERS                    = 2.
    IF sy-subrc EQ 0.
      ASSIGN dy_table->* TO <dy_table>.
    ENDIF.

******V_col will hold the number of Columns inside Excel File which is later passed to ALSM_EXCEL_TO_INTERNAL_TABLE’ .

    DESCRIBE TABLE li_fieldcat LINES v_col.

    LOOP AT t_file INTO wa_file.

******This Block will create new area to store column wise data.<wa_temp> acts as a work area which is completely blank at start of new row
      AT NEW row.
        CREATE DATA new_line2 LIKE LINE OF <dy_table>.
        ASSIGN new_line2->* TO <wa_temp>.
      ENDAT.

*******for every iteration, wa_file-col will have increment till number of columns in Excel file and then reset to 1 when there’s new row i.e row = 1. (Refer example at end of blog)

      ASSIGN COMPONENT wa_file-col OF STRUCTURE <wa_temp> TO <fs_current_field>.
      IF sy-subrc EQ 0.

        <fs_current_field> = wa_file-value.
        UNASSIGN <fs_current_field>.
      ENDIF.

*****Finally once all Columns are processed and new row is about to start, append the workarea into Internal table

      AT END OF row.
        APPEND <wa_temp> TO it_xls_data.
        UNASSIGN <fs_current_field>.
        UNASSIGN <wa_temp>.
      ENDAT.

    ENDLOOP.
*ENDIF.

***Mapping IV_DATA_REF (Excel data) to Fields

*-----------------------FIELD SYMBOLS----------------------------------*
    FIELD-SYMBOLS: <lfs_data_tab> TYPE ANY TABLE,
                   <fs_1>         TYPE any,
                   <fs_2>         TYPE any.
*----------------------------------------------------------------------*
    hdr_len = COND #( WHEN hdr_len IS INITIAL THEN 1 ELSE hdr_len ).

    ASSIGN iv_data_ref->* TO <lfs_data_tab>.

    IF <lfs_data_tab> IS ASSIGNED AND <dy_table> IS ASSIGNED.

      LOOP AT <lfs_data_tab> ASSIGNING FIELD-SYMBOL(<lfs_data>).
        IF sy-tabix LE hdr_len.
          CONTINUE.  "Skip line 1
        ENDIF.

        CREATE DATA new_line2 LIKE LINE OF <dy_table>.
        ASSIGN new_line2->* TO <wa_temp>.

        DO 250 TIMES.
          ASSIGN COMPONENT sy-index OF STRUCTURE <lfs_data> TO <fs_1>.
          ASSIGN COMPONENT sy-index OF STRUCTURE <wa_temp> TO <fs_2>.
          READ TABLE li_fieldcat INTO DATA(fs_fieldcat) INDEX sy-index .
          IF sy-subrc IS INITIAL AND fs_fieldcat-datatype = 'DATS'.
            IF <fs_1> IS ASSIGNED AND <fs_2> IS ASSIGNED AND strlen( <fs_1> ) EQ 10 .
              DATA(lv_date) = |{ <fs_1>(4) }{ <fs_1>+5(2) }{ <fs_1>+8(2) }| .
              CONDENSE lv_date.
              <fs_2> = lv_date.
*              <fs_2> = <fs_1>.
              UNASSIGN: <fs_1>, <fs_2>.
              CLEAR: lv_date.
            ENDIF.
          ELSE.
            IF <fs_1> IS ASSIGNED AND <fs_2> IS ASSIGNED.
              <fs_2> = <fs_1>.
              UNASSIGN: <fs_1>, <fs_2>.
            ENDIF.
          ENDIF.
        ENDDO.

        IF <wa_temp> IS ASSIGNED AND <wa_temp> IS NOT INITIAL.
*          MOVE-CORRESPONDING <wa_temp> TO it_xls_data.
          APPEND <wa_temp> TO it_xls_data.
        ENDIF.

      ENDLOOP.
    ENDIF.
  ENDIF.

ENDFUNCTION.

⚠️ Important Points to Remember

❌ Do NOT use BLKNR for text key
✅ Always use ZEILE
❌ Avoid INSERT = 'X'
✅ Use INSERT = SPACE for overwrite
✅ Ensure ESLZ entries exist

🧪 Debug Tip

Use function module READ_TEXT:

OBJECT = 'ESLZ'
ID     = 'LTXT'
NAME   = '001200400000000004'

👉 Helps verify actual stored text

Final Result

✔ All lines updated correctly
✔ Correct mapping in ML03
✔ No missing or overwritten data

Conclusion

Uploading Service Catalog Long Text becomes easy once you understand:

SAP stores text per LINE (ZEILE)
Not per BLOCK (BLKNR)
Correct text key is the key to success

💡 Key Takeaway

If your long text upload is not working — you are most likely using the wrong key.

🙌 Closing Note

This is a common issue with no clear documentation.
Hope this blog saves you hours of debugging.

Feel free to share your feedback or improvements 🚀

Create, Delete and Updating of Packing Specification(PACKSPEC) through Upload Program Report

2026-03-25T11:07:59.250000+01:00

Introduction:

Maintaining of Packing Specification(Minimum Order Quantity and Target Quantity) for every Material-Plant combination in Service Parts Planning(SPP) system is a crucial step. Usually we do that through Standard T-Code /SCWM/IPU through upload file.

Instead to improve user experience and simplify the process of uploading, we created an Upload Report Program.

Body:

Development Completed on April 4 , 2025

Usually, creating, deleting or updating Packspec in T-Code /SCWM/PACKSPEC is a time-consuming process and requires lot of manual efforts to change every packspec directly in the standard screen.

This can also be done in T-Code /SCWM/IPU using upload template, but that is not user-friendly which requires us to download standard template of more than 100 columns and wants us to edit each and every column and upload. This is quite difficult.

It will also create a new packspec every time in the system, which will also increase the count of No. of Packspec in system, and which is also not consolidated with respect to Minimum Quantity-Target Quantity or plant-material combo. This makes us to go for custom upload program which is quite efficient in analyzing the Minimum Quantity-Target Quantity, Plant-material combination and decides to craete/update packspec based on user input.

Our Requirement is to reduce the manual intervention of changing the packspec directly in standard screen or reduce the complexity structure of upload file, instead we can have an upload program which does the Create, Update or Delete processes and provide results of the progress in SLG1 log and also as ALV report for end-users.

General Overview about Packing Specification:

One Packspec number consists of many condition records. Each Condition record represents one product and one location.

Business users usually maintains set of material-plant combo under one specific packspec number with MOQ(Minimum Order Quantity)(Minimum Quantity for Supplier - SAP system identification name) and UOQ(Unit Order Quantity)( Target Quantity - SAP system identification name).

They will also be changing this from time-to-time as per business changes.

Detailed Overview about our Report Prorgam:

Requirement consists of 2 mode namely Manual Mode and Full Mode.

Manual Mode is to change only the MOQ and UOQ of the packspec number, instead of keeping hands on the condition records. Suppose if business wants to change MOQ. UOQ from 2,3 to 6,2 respectively for all the same set of mat-loc combo present in the packspec number, they can use this manual mode to change only the MOQ and UOQ.
Full Mode will consume upload file as input. Upload Template:
Material Plant DEPL/DRP MOQ UOQ Mode A/D
From inputs from this file, it will check mode first as A/D.
Based on that, it checks if the material-loc combo is present under any other packspec number, if yes, program will delete existing condition record and create a new one with given MOQ and UOQ.
Above is example of one scenario, like this it should work for every possible scenario.
Delete a packspec , if suppose the last condition record in packspec is requested to be deleted.
Create a new packspec if a new set of MOQ-UOQ is requested n upload file.
Add one more condition record, if the requested MOQ-UOQ is already present in System.

Arriving at Solution:

We need to debug the standard T-code /SCWM/IPU to find all the standard FM's used to create, update and delete Packspec . FM's used to create, change, delete CONDITION RECORD is also required.
Function Modules found:
- ‘/SCWM/API_PACKSPEC_READ’ - To read the existing packspec details
- '/SCWM/API_PACKSPEC_CREATE' - To create a new Packspec
- '/SCWM/API_PACKSPEC_2ND_VERSION' - To create 2nd version of packspec (i.e) make it inactive, add required condition records.
- '/SCWM/API_PACKSPEC_CHANGE' - To change the MOQ and UOQ of the packspec
- '/SCWM/API_PACKSPEC_ACTIVATE' - To activate the inactive packspec.
- '/SCWM/API_PACKSPEC_DELETE' - To Delete the whole packspec
- '/SCWM/API_CONDITION_REPLICATE' - To create only one condition record within pakspec
- '/SCWM/PS_DELETE_CONDTECH' - To delete only condition record, if last condition record, call packspec delete FM also.
- '/SAPCND/MNT_SAVE_OW' - After deleting the condition record, call this FM to make the deletion process complete...as this is the process followed in standard process for successful deletion.
- 'OWN_LOGICAL_SYSTEM_GET' - To get the logical system number.
Tables used:
- '/1CN/CPSCUS_SPP' - To get packspec details of Deployment Packspec.
- '/1CN/CPSCUS_PRPL ' - To get packspec details of DRP Packspec.
- '/SCWM/PNPAKH' - Pack Spec Header(ippe node)
- 'PALTID' - iPPE Alternative: Time-Independent ID and Attributes
- '/SCWM/PAPAK' - packaging specification level (ippe alternative)
We created a report named "ZSPPR_PACKSPEC_UPLOAD" with selection screen to run the program and a backend global class named "ZCL_PS_MASTER" to support the required logics needed.
ZSPPR_PACKSPEC_UPLOADZCL_PS_MASTER global class
Report consists of Top declarations, Selection screen logics including download the template of upload file, Modification ID to differentiate between manual and full mode , Program flow with object for ZCL_PS_MASTER and flow logic and forms with different set of operations involved like change_moq_uoq, upload_data_from excel_to_itab, data_validation, refresh_depl_table, refresh_drp_table, add_mode, delete_mode, Write_log, calculate_pass_fail records for summary, display manual ALV and display Full ALV output as result.
Importing data from Excel to ITAB can be done using Standard FM like CL_GUI_FRONTEND_SERVICES=>GUI_UPLOAD, but this method has errors of terminating the whole SAP GUI session while trying to close the opened Excel file by our program.
To resolve this we came up with solution of importing set of custom classes ‘ZCL_EXCEL_READER_2007' into a separate package. This is available in abap2xlsx github repository. GitHub - abap2xlsx/abap2xlsx: Generate your professional Excel spreadsheet from ABAP · GitHub
With help of ABAPGIT Standalone program , we were able to add this set of classes into a new package. Installation | abapGit Docs
Using method GET_CELL of class ‘ZCL_EXCEL_READER_2007' , we will get all the data in excel to ITAB, without popping up of Excel GUI explicitly, avoiding unwanted termination of SAP GUI.
Once these classes are installed, we can make use multiple times in our future upload programs.
ALV display is enhanced with colored outputs with green/red for users to identify the error records easily.
The below logic is used to identify that given line of Packspec comes under which condition of Add/Delete Packspec.
- [MODE - A]
- IF MOQ-UOQ from excel is present in system.
- IF MAT-LOC from excel is in the same MOQ-UOQ from EXCEL.
- Throw ERROR"Same packspec combination already exists.".
- ELSEIF (Condition Record is present in system in another MOQ-UOQ).
- Delete that Condition Record from existing packspec, create new condition record under given MOQ-UOQ.
- ELSE.
- Add the MAT-LOC to the given packspec.
- ENDIF.
- ELSE.
- IF Condition Record is present in system.
- Delete that Condition Record from existing packspec, create a new PACKSPEC.
- ELSE.
- Create a new PACKSPEC.
- ENDIF.
- [MODE - D].
- IF MOQ-EOQ from excel is present in system.
- IF MAT-LOC from excel is in the same MOQ-EOQ from EXCEL.
- IF No. of Condition Records = 1
- Delete the PACKSPEC.
- ELSE.
- Delete the Condition Record from PACKSPEC.
- ENDIF.
- ELSE.
- Condition record is not under the given MOQ-UOQ.
- ENDIF.
- ELSE.
- Packspec(MOQ-UOQ) does not exist in system-THROW error.
- ENDIF.
Technical Mindmap for the program flow:
Screenshots of Manual Mode Test run ALV, Real run ALV and SLG1 log output.
Test Run ALV OutputReal Run ALV OutputReal Run SLG1 log Output
Screenshots of Full mode Test run ALV, Real run ALV and SLG1 log output.
Test Run ALV OutputReal Run ALV OutputReal Run SLG1 Log output
Validation check results Screenshot:
Difficult part is to find the relationship between the tables , where the condition number is getting stored.
While debugging, the condition record actually gets saved after another FM call of MNT_SAVE_OW, but to find that exact FM took really more time.
Faced lot of difficulties in DB storage malfunction due to continuous execution of FM's, so found solution with COMMIT WORK and Wait upto 2 seconds. This resolved the DB overflow issue.
Learned how to stop debugger exactly at CALL FUNCTION points while executing a t-code.
You can create SQVI query like below for your convenience at the time of development for testing purpose and data-validation!
SQVI query for Deployment packspecSQVI query for DRP packspec

Conclusion:

We can create upload reports in this way consisting of Minimum and Target Quantity with Plant-Location Combination with mode A/D. We can modify this according to business use-cases and include /exclude columns in upload file. We've kept changing parameters in TVARVC table and hard-coded the constant parameters.

This was developed when I had 8-9 months of experience, excuse me for best coding practices. Attached complete code for your reference! Please feel free to post your comments and message me for any support regarding this! Hope this helps someone! 😊

BP Extension - Search By Email in ECC 6.0

2026-03-25T18:50:42.904000+01:00

The Client was having a legacy system where they can search the for particular Vendor if its created or not based on email ID. So moving forward they came up with requirement to centralize the Vendor Management System by migrating all things into ECC.

The first requirement came to make BP screen as it was in legacy system where user can search for Partner numbers created in system based on Email Id provided. I went through many SAP notes and found multiple approaches.

Approach

SPRO config – Search Criteria

SAP Customizing Implementation Guide → Logistics - General → Cross-Application Components → SAP Business Partner → Business Partner Search → Define Search Criteria for Business Partner

OR

SAP Customizing Implementation Guide → Logistics - General → Cross-Application Components → SAP Business Partner → Business Partner Search → Basic Setting → Search → Define Search Views

Note: These will only work if the BP Search Framework is fully active

BUS config
LOCA_CUST

The above 2 options didn’t worked due to lower SAP version. So the only option was to explore LOCA_CUST.

Here is the details of all technical objects created and mapping to LOCA_CUST.

Create a Database View (SE11)
Since email addresses live in table ADR6, we need a view that joins the BP to its email.
Tables & Joins:
BUT000 (Partner) joined to BUT020 (BP/Address Link) on PARTNER = PARTNER.
BUT020 joined to ADR6 (Email) on ADDRNUMBER = ADDRNUMBER.
Create an Elementary Search Help
Once the view is active, create the search help that the BP transaction will actually display.
SE11 -> Search Help
Selection Method: Enter the view you just created (ZBP_EMAIL_SEARCH).
Search Help Exit: Use F4UT_OPTIMIZE_COLWIDTH (optional, for better UI).
Parameters:
SMTP_ADDR: Mark as IMP (Import) and EXP (Export). LPos = 1, SPos = 1.
Append to the Collective Search Help
Now you must tell the BP transaction to include your new "Email" tab in the locator.
Open Collective Search Help BUPA_ALL
Go to the Included Search Helps tab.
Click the Append Search Help button (F5).
Create a new Append . In the "Included Search Helps" of your append, add your elementary search help
Click Parameter Assignment to map the PARTNER field from your search help to the collective search help.
Verification
After activating everything:
Run transaction BP.
In the Locator (left-hand side), click the "Find By" dropdown.
You should now see your new entry ( with the Z name).

NOTE: However if you click on the new field it will throw error “Program name and Screen are not configured”
Pass the value of email field in Standard SAP flow of BP transaction
Create Append structure in BUS_JOEL_SEARCH. SE11 -> BUS_JOEL_SEARCH - >Append Structure(F5)
Here comes the Important Step for mapping to SAP hook using ABAP code. This FM will capture the data of new field and integrate it into the standard BP process for this we need to use the OOPS concept and include some standard processing code from LBUPA_DIALOG_SEARCHF02 and LBUS_LOCATORO01.
Create a Function Group. SE37-> Goto-> Function Group -> Create Group .
Click on Master Program of function group and define a local class in TOP include along with the Global variable for fetching the value of email in GV_EMAIL.

FUNCTION-POOL ZBP_FMGRP_BUPA.               "MESSAGE-ID ..

* INCLUDE LZBP_FMGRP_BUPAD...                " Local class definition
TABLES bus_joel_search.

DATA: gs_dynpro_id TYPE bus_screen-area,
      gv_email type adr6-smtp_addr. " capture screen value

CLASS lcl_searcher DEFINITION FINAL.

  PUBLIC SECTION.

    CLASS-METHODS:
    select_by_email
    IMPORTING iv_search  TYPE REF TO cl_bus_locator_search
              iv_email TYPE bus_joel_search-smtp_addr
              EXCEPTIONS search_values_missing.

ENDCLASS.

Create a Copy FM from Standard BUPA_DIALOG_SEARCH into a Z Function module. Follow the below code to fetch the partner from the view created in STEP1 based on input from email of BP screen.

FUNCTION zbp_bupa_dialog_emailrch.
*"----------------------------------------------------------------------
*"*"Local Interface:
*"  IMPORTING
*"     REFERENCE(IV_SEARCH) TYPE REF TO  CL_BUS_LOCATOR_SEARCH
*"  EXCEPTIONS
*"      SEARCH_VALUES_MISSING
*"----------------------------------------------------------------------

* Local data.
  DATA: ls_search_fields TYPE bus_joel_search. 
* Convert generic container into specific fields.
  ls_search_fields = iv_search->gv_search_fields.           

* Choose the select.
  CASE iv_search->gv_search_id.

*   The empty search?
    WHEN space.
      CALL METHOD lcl_searcher=>select_by_nothing
                  EXPORTING iv_search = iv_search.

    WHEN 'ZBP_EMAIL_SRCHELP'.    "name of elementary search help
      CALL METHOD lcl_searcher=>select_by_email
        EXPORTING
          iv_search             = iv_search
          iv_email              = ls_search_fields-smtp_addr
        EXCEPTIONS
          search_values_missing = 1.

    WHEN OTHERS.
      CLEAR sy-subrc.
  ENDCASE.
*
  CASE sy-subrc.
    WHEN 1.
      RAISE search_values_missing.
  ENDCASE.

ENDFUNCTION.

Implement the method by creating a new include in Master Program.
with the below code the Partner GUID is passed back again to BP framework to display the result of partner number based on the user input of email id.

*&---------------------------------------------------------------------*
*&  Include           ZBP_FMGRP_BUPA01
*&---------------------------------------------------------------------*
CLASS lcl_searcher IMPLEMENTATION.
*---------------------------------------------------------------------
  METHOD select_by_email.
*   Local data.

    DATA: lv_partner_type       TYPE bus_partner-type,
          lr_email TYPE RANGE OF adr6-smtp_addr,
          lt_partner_guids  TYPE bus_partner-guid_table.


    IF gv_email NE space.
      SELECT partner_guid INTO TABLE lt_partner_guids
               FROM zbp_email_search
               UP TO iv_search->gv_maximum_rows ROWS
               WHERE smtp_addr EQ gv_email.
*      BREAK-POINT.

      IF sy-subrc NE 0.
        TRANSLATE gv_email TO LOWER CASE.
        SELECT partner_guid INTO TABLE lt_partner_guids
             FROM zbp_email_search
             UP TO iv_search->gv_maximum_rows ROWS
             WHERE smtp_addr EQ gv_email.
      ENDIF.

    ENDIF.
*   Pass result table
    CALL METHOD cl_bupa_dialog_searcher=>add_partner_guids_to_result
      EXPORTING
        it_partner_guids         = lt_partner_guids
        iv_filter_by_search_type = space
        iv_search                = iv_search.
  ENDMETHOD.                    "select_by_email

ENDCLASS.                    "lcl_searcher IMPLEMENTATION

Create a new screen by Right click on Function group -> Create->Screen
Note: GV_EMAIL is the same which is declared in step 8.Don’t forget to make the text box as scrollable otherwise you may loose data .
Double click on PBO and PAI and create new include in Master Program of function group. And do the following code. This code helps to pass the necessary information of standard processing copied from LBUPA_DIALOG_SEARCHF02 and LBUS_LOCATORO01.

----------------------------------------------------------------------*
***INCLUDE LZBP_FMGRP_BUPAO01.
*----------------------------------------------------------------------*
*&---------------------------------------------------------------------*
*&      Module  DYNPRO_PBO  OUTPUT
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
MODULE dynpro_pbo OUTPUT.
  gs_dynpro_id-program_name = sy-repid.
  gs_dynpro_id-dynpro_number = sy-dynnr.

  CALL METHOD cl_bus_abstract_screen=>dynpro_pbo
              EXPORTING iv_program_name = gs_dynpro_id-program_name
                        iv_dynpro_number = gs_dynpro_id-dynpro_number.

ENDMODULE.                 " DYNPRO_PBO  OUTPUT
*&---------------------------------------------------------------------*
*&      Module  DYNPRO_PAI  INPUT
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
MODULE dynpro_pai INPUT.
  gs_dynpro_id-program_name = sy-repid.
  gs_dynpro_id-dynpro_number = sy-dynnr.

  CALL METHOD cl_bus_abstract_screen=>dynpro_pai
              EXPORTING iv_program_name = gs_dynpro_id-program_name
                        iv_dynpro_number = gs_dynpro_id-dynpro_number.
ENDMODULE.                 " DYNPRO_PAI  INPUT

Create a new include in Master Program of function group and enter the below code. These subroutines are called from the BUS_JEOL_LOCATOR framework hence it is required in our FM.

*---------------------------------------------------------------------*
*       FORM bus_locator_get_search_fields                            *
*---------------------------------------------------------------------*

FORM bus_locator_get_search_fields                          "#EC CALLED
     USING    iv_search_application TYPE bus_locator-search_application
     CHANGING ev_search_fields      TYPE bus_locator-search_fields.

 CASE iv_search_application.
    WHEN cl_bupa_dialog_searcher=>gc_search_application_bupa.
      ev_search_fields = bus_joel_search."#EC ENHOK
  ENDCASE.

ENDFORM.

*---------------------------------------------------------------------*
*       FORM bus_locator_set_search_fields                            *
*---------------------------------------------------------------------*

FORM bus_locator_set_search_fields                          "#EC CALLED
     USING    iv_search_application TYPE bus_locator-search_application
              iv_search_fields      TYPE bus_locator-search_fields.

  CASE iv_search_application.
    WHEN cl_bupa_dialog_searcher=>gc_search_application_bupa.
      bus_joel_search = iv_search_fields. "#EC ENHOK
  ENDCASE.

ENDFORM.

Functional Configuration in LOCA_CUST

Create new entry under Search by ID
Search for the Search Help created in Step gy doing an F4 on Locator Search ID.
Screen text would be displayed on the drop of Find by screen of BP .Now do F4 for FM and Program name and enter screen number created in step 11 the details. That’s the end for the required config for mapping the new field to BP screen.
Let’s test
Enter Tcode BP. Click on BY dropdown to see the new field available under name Email.
Enter any relevant email Id to find the respective BP . You can find the BP from the view created in Step 1 as well.
Result

SPP SNC (Supply Portal Collaboration) Portal - BADI - Web Dynpro Screen EPN Column inclusion

2026-03-26T07:10:11.114000+01:00

Introduction:

When we need to modify an existing column in SNC(Supply Network Collaboration) Portal under any tab with Header name and column values, we need to follow follow several set of procedures to find correct BADI and implement it.

In this blog I've explained about adding column EPN(Engineering Part Number) under Release Process->Overview tab in SNC portal.

Body:

Development Completed on Feb 5 , 2026

Business requested to include EPN(Engineering Part Number) column in the SAP SNC(Supply Network Collaboration) Portal.
T-Code for SNC Portal under APO box is /SAPAPO/SPP_CUSTOMER or we can also use /SAPAPO/SPP_SUPPLIER
SNC Poral Initial Screen
Under this screen go to Release Process->Overview Tab.
Here you can see 7th column named as "My Product Number" should be changed to "Eng. Part Number (EPN)" column with the necessary EPN numbers to be populated against every Product number.

Arriving at Solution:

After going to Release Process->Overview tab, go to debugging screen and need to find what are the available and useful BADI's for this solution to enhance this standard Web Dynpro screen.
To trigger debugging WD screen within SAP system, go to T-Code /N/SCF/WD_START and provide our Application ID : /SCF/SPP_CUSTOMER and check the checkbox "Internal Modus". So that it Web Dynpro Screen will start within SAP system. We can set breakpoint at "CALL BADI" statement and find the available BADI's.
Other way to find the class involved in particular Web Dynpro Screen is go to T-Code "/N/SCF/SCREENCFG" and click on ICH and go to screen definitions, then click on DSOVW-Release process Overview Screen (Supplier View) and click on Screen Layout. You will get the classes involved in fetching data etc.
This process is same for all Web Dynpro screens to get the respective class name.
With help of class name, we can get the logics involved in populating the screen data and BADI's called in-between.
We got BADI "/SCF/RELEASE_UI" which is useful here to populate the data from the backend. Create Enhancement Implementation and one BADI implementation within the created Enhancement Implementation.

BADI 1:
BADI Definition Name	/SCF/RELEASE_UI
Interface Used	/SCF/IF_EX_RELEASE_UI
Class where BADI is Triggered	/SCF/CL_MDLTBV_DSOVERVIEW
Method called in Class	LOAD_DATA
Enhancement Implementation	Z*
BADI Implementation	Z*
Implementing Class	Z*
Method used	/SCF/IF_EX_RELEASE_UI~LOAD_OVERVIEW_TBV

Always keep your enhancement codes within Enhancement Switch which is maintained in a separate custom table. So that, whenever there's a misfortune happens, we can turn it off immediately to prevent more damages. Always check the Switch turned on and write your own logic.
In this BADI code logic, we are fetching all the EPN values from Transparent Table /SAPAPO/MATAPN and assigning against the column "CUSTMATERIAL "(My Product Number column).
This BADI will push the data into the target column.
Next, we need another BADI to change the Column header name in Web Dynpro Screen.
We got BADI "WD_BADI_DOMODIFYVIEW" which will be triggered multiple times. Hence, we have filter option where we need to fill required parameters.

BADI 2:
BADI Definition Name	WD_BADI_DOMODIFYVIEW
Interface Used	IF_WD_BADI_DOMODIFYVIEW
Class where BADI is Triggered	CL_WDR_DELEGATING_VIEW
Method called in Class	DO_MODIFY_VIEW
Enhancement Implementation	Z*
BADI Implementation	Z*
Implementing Class	Z*
Method used	IF_WD_BADI_DOMODIFYVIEW~WDDOMODIFYVIEW

Here we are using COMPONENT_NAME as "SALV_WD_TABLE" and VIEW_NAME as "VIEW_TABLE".{ These BADI's aren't that easy to find like I mentioned here simply, it takes lot of effort to find each and every BADI 😊}. You can also find the exact component and view name from technical help on the WD screen.
These parameters we need to find through debugging as and when our logic needs to be executed.
Create EI and BI like previous BADI and add the filter values.
In the BADI code logic, check for Enhancement Switch and get the exact object where our Column Header name lies within. We need to change both Header name and Caption name (visible during Hovering the column header).
We can compare ID of both elements, but it keeps on changing from system to system, but name remains consistent. Hence, We choose name of the column.
To find the element name from the WD screen, right click on the column header name from WD screen and press "Technical Help". Go to "View and View Elements" tab. Now, dropdown the "View Elements and Properties" tab. Now the dropped down screen exactly represents the properties of column header where you right clicked for technical help.
Catch correct exceptions in correct order where subclass exception must be caught first, and then superclass exception can be caught. CX_ROOT must be caught at last of all exceptions. This BADI will also be triggered in other screens of SNC portal also, hence, if we miss catching exception, it will result in Screen Dump.
I faced lot of difficulties while finding correct component name, view name, tooltip, text of target elements. Biggest difficulty happened was to find the class name from where the data on screen is getting populated from.
Previous State/when Enhancement Switch is turned off :
Current State/when Enhancement Switch is turned On:

Conclusion:

This is how we change column name and related contents in SNC Portal. I've also worked on adding column "Commitment Level" column under "Receipts and Requirements"->"Due list for Purchasing Documents" tab by implementing the BADI "/SCF/ICH_POWL". Attached complete code for your reference! Please feel free to post your comments and message me for any support regarding this. Hope this helps someone! 😊

Fiori List Report: The "Process All" Dilemma — Parsing OData $filter in ABAP

2026-03-26T18:27:35.306000+01:00

The Problem

This scenario is more common than you might think.

In the old SAP GUI world, ALV lists frequently had buttons like "Execute All" or "Process All" defined in the GUI Status, or users could simply "Select All" rows and trigger an action. The entire dataset was right there in memory — stateful, accessible, simple.

Unfortunately, the same approach is still often requested in Fiori Elements List Reports. The reason? There's still a widespread difficulty in understanding the fundamental difference between stateful and stateless, between a classic ALV list and a Fiori List Report.

When we try to explain that there's an OData protocol with pagination behind the scenes, that "Select All" doesn't truly select all rows, or that an "Execute All" action has no knowledge of which records to process — unlike in ALV where the entire internal table was available — we can often steer the design away from this pattern. But sometimes, we can't.

The Fiori warning message helps users understand that "Select All" is only partial — it's no longer the same as it was with ALV lists.

There are legitimate use cases where, after filtering a dataset, reviewing it, validating it, the user needs to "confirm" an action or a status change to be applied to that specific result set they're currently looking at.

I won't go into the details of how the action should be implemented in ABAP — there could be timeout concerns, and often these actions are executed via background tasks or jobs. I want to focus specifically on the approach for capturing the "snapshot" of what the user has filtered.

As we said, "Select All" is not a viable option. In the modern world we have pagination, and we can't expect the user to scroll all the way to the bottom of the list. Retrieving all row identifiers from the frontend is simply not feasible.

Our Approach

The best solution we've implemented (together with @SimoneLicciardi ) is to pass the applied filter criteria back to a Static Action — essentially the same filters that were active when the user pressed "Go".

We can define an Abstract Entity as the import parameter for the RAP action. If the action dialog already has other parameters, this is simply an additional hidden parameter (@UI.hidden: true) that we can call FilterString.

define abstract entity ZA_ProcessAllParams {
  @UI.hidden: true
  FilterString : abap.string(4000);
  // ... other action parameters if needed
}

The Fiori Elements Extension

On the Fiori Elements List Report side, we need custom action logic that does two things when the user triggers the action: capture the current $filter string and inject it into the hidden parameter.

This can be achieved through a custom action defined in the manifest.json (or via a controller extension, depending on your app setup).

The _getFilterString method extracts the $filter from the current table row binding — this is exactly the same filter the framework sent to the backend when the user pressed "Go".

function _getFilterString(oView) {
    // Table ID follows Fiori Elements convention: 
    // "<appId>::<ListReportPage>--fe::table::<EntitySet>::LineItem"
    var oTable = oView.byId("<your-table-control-id>");
    if (oTable) {
        var oRowBinding = oTable.getRowBinding();
        if (oRowBinding) {
            var sPath = oRowBinding.getDownloadUrl();
            if (sPath) {
                var iFilterStart = sPath.indexOf("$filter=");
                if (iFilterStart > -1) {
                    var sFilter = sPath.substring(iFilterStart + 8);
                    var iNextParam = sFilter.indexOf("&");
                    if (iNextParam > -1) {
                        sFilter = sFilter.substring(0, iNextParam);
                    }
                    return decodeURIComponent(sFilter);
                }
            }
        }
    }
    return "";
}

Then in the action handler, we invoke the static action and pass the $filter string as the hidden parameter:

onPressExecuteAll: function () {
    var oView = this.editFlow.getView();
    var sActionName = "<your action bound context>";
    var sFilterString = _getFilterString(oView);

    var oInvokeParams = {
        controlId: "<your-table-control-id>",
        bStaticAction: true,
        invocationGrouping: "Isolated",
        parameterValues: [{
            name: "FilterString",
            value: sFilterString
        }]
    };

    this.editFlow.invokeAction(sActionName, oInvokeParams)
        .then(function (oResult) {
            // handle success
        }).catch(function (oError) {
            console.error("Action error:", oError);
        });
}

The key point: the parameterValues array injects the filter string into the hidden FilterString field of the Abstract Entity. The user never sees it — the action dialog shows only the visible parameters (if any), while the filter criteria travel silently to the backend.

Note: this was tested on S/4HANA 2023 with OData V4 and SAPUI5 1.120.

The ABAP Parser

On the backend, the action handler receives the $filter string and needs to parse it into ABAP range tables to re-execute the query with the same criteria.

We looked for standard solutions — for example, the method ODATA_FILTER2SELECT_OPTION of class CL_CLB2_TOOLS — but it only supports OData V2.

So we built a custom reusable class: ZCL_ODATA_FILTER_PARSER, which handles both V2 and V4 syntax and converts the $filter string directly into ABAP range tables.

DATA(lo_parser) = NEW zcl_odata_filter_parser(
  iv_filter  = lv_filter_string
  iv_version = zcl_odata_filter_parser=>gc_version-v4
).

DATA(lt_r_plant) = lo_parser->get_range( 'Plant' ).
DATA(lt_r_mat)   = lo_parser->get_range( 'Material' ).
DATA(lt_r_date)  = lo_parser->get_range( 'DeliveryDate' ).

The class is open source, includes ABAP Unit tests and is installable via abapGit. You can find the usage examples in the repository:

https://github.com/alespad/abap-odata-filter-parser

This is how we approached solving this problem. If you know of better approaches, closer to standard functionality, we'd love to hear about them — please share in the comments!

Send Email with inline BASE64 Image in SAP ABAP.

2026-03-27T12:30:41.235000+01:00

Introduction

I recently came across the need to send an automatically generated email based on a given HTML template. To my surprise, this time the template arrived with embedded/inline (src="data&colon;image/png;base64,...) images using Base64 encoding. I should mention that all previous HTML mail templates I worked with contained image links pointing to a content web server.

Since this was new to me, I did some research on the topic but did not find much information, except for this helpful blog post:
https://community.sap.com/t5/technology-blog-posts-by-members/send-email-with-image-from-mime-repository-in-sap-abap/ba-p/14285931

In that scenario, the images are stored in the MIME repository, whereas in my case they are embedded directly in the HTML file. Therefore, I needed to extract the picture content from the HTML code, rebuild the template, and generate an email using standard SAP BCS functionality.

After implementing this successfully, I would like to share some of my coding approach with the community.

Code Example:

REPORT zemail_to_send_img2.

*----------------------------------------------------------------------
* Data Declarations
*----------------------------------------------------------------------
TYPES: BEGIN OF lty_pic_str,
         name TYPE string,
         mime TYPE w3conttype,
         src  TYPE xstring,
       END OF lty_pic_str.

DATA: lv_html_in  TYPE string,               "HTML body string (input)
      lv_html_out TYPE string,               "HTML body string (output)
      lt_html_out TYPE soli_tab,             "HTML body lines
      lv_pic_cnt  TYPE i,                    "Picture counter
      lv_src      TYPE xstring,              "Image content in XSTRING
      lt_solix    TYPE solix_tab,            "Binary table
      lv_len      TYPE so_obj_len,           "Length of binary content
      lt_pic_tab  TYPE TABLE OF lty_pic_str. "Table with pictures

DATA: lo_mime_srv  TYPE REF TO cl_gbt_multirelated_service,
      lo_doc       TYPE REF TO cl_document_bcs,
      lo_bcs       TYPE REF TO cl_bcs,
      lo_sender    TYPE REF TO if_sender_bcs,
      lo_recipient TYPE REF TO if_recipient_bcs.

*----------------------------------------------------------------------
* Step 1: Build HTML Email Body
*----------------------------------------------------------------------
lv_html_in =
   |<html>|
&& |<!-- To work with BCS, styles should be defined locally !!! -->|
&& |<body style="background-color:#e6f0fa; font-family:Arial; margin:0; padding:10px;">|
&& |<div style="max-width:600px; margin:auto; background:#ffffff; padding:20px; border-radius:8px; border:1px solid #d0d7e3;">|
&& | <div style="text-align:center; margin-bottom:15px;">|
&& |<!-- Inline BASE64 PNG Image -->|
&& | <img src="data&colon;image/png;base64,|
&& |iVBORw0KGgoAAAANSUhEUgAAAKMAAACUCAMAAADIzWmnAAAAY1BMVEX///8AAABHR0f7+/vz8/PV1dXw8PA6Ojr29vbk5OTp6ekyMj|
&& |Ls7OwpKSnc3NxAQECcnJyRkZFfX1/MzMxkZGStra2+vr5WVlZQUFB1dXUeHh6mpqaLi4sPDw99fX1vb28XFxcA3zptAAAMl0lEQVR4|
&& |nO1c52LyvA6G7EH2hCzu/yo/Sw7BQ06B0vGe0+dPm0Esy1qWZR8Of/jDH/7wh/97RG7bDnkxAop8aCs3+mmSRERtUVp+cpmOd0yXxL|
&& |fqovoFhAZpO/vHPfhjmwY/SGGaL7FGVKKTuQzhzxDoNOVFpOSCV6UbuOX9cnu4tN/PTLeQaDiWOZK24MMFic076Y04d7+Xwlke0a71|
&& |DhX723MViXr2f3XwWoXKOf0+Csu1zZJLYwkMOjHVuVTrGxVjsn+Cf/irVr3K7fI9VKbzlbc7tAtqRIOSNrB/x+2lkV0N8I/TAHXXuR|
&& |osLpjj16uPPXBT4zdehDwqeZseXHjbax484ZcpDvjZ8Rr+y6z5Ygpd3k7Zsrbhn+utwZZdFMKbBbtu1/8HFAw29C0f+f5LB3zEYU4a|
&& |hwllBg3fyDiw1hNRb12mVOXtogEN60IYedS1ZPgyCl0uUgWMoQti5m9URTCctvCufWZ3NkeIb1tw6RVHQULeDs6DGnU3hDHP7g0Nwt|
&& |BytDetQaTwfocCWtUoz/Lb74GdIwMGBy48aCcTxIpdXzzpfY+Zn/p+iZyckdMOyuf0/vE+Ye87Prj2DFZECGmAgrPyCzbYsSCh4eWu|
&& |VS6q+uwd3oqQf9XhV8CIpBIeN+hXZIDfEc1Me7nLgzOj2LyVyBSc2zFfwwLQWal54GusRopRfBvcFdAzfxXhACWnfGN06UL0er0xKg|
&& |Krk4vPvatCzo3wq8QpcD7lOhSHCsxY8jb1RsPtb2OJTUmRlivp8A3ANynUcXqxcxV8tX8TkWg34k2JQc4SOcwaBC7fAZySKXdBJDeq|
&& |UjSabyEyTCRT6PWKMB7QyfQn7YenXnA1HMDaehOKMBMk9DPAYOGY5Tc+QjOd/ErAerGo4sgEkoVFiRJ9W4KtT3kotHw6QA+W44ppbs|
&& |MAzdxV6TqoFGWRWXcmJfaGQIQFlkHUrhHekdC2ZwHudZuTXur8TKiHphw32nWpOIDNmfNaCuM/6XFaRt/UVOer8MnrWEVS10HRKV7Y|
&& |RzHshRtRNYuT8OtSNZMQvr8E9LLYzWouxWnq1M9566ahF9gHh0lsRv48Q3toB16YulV+7kX64m6uoGOD4vmfBijesv5vu82YHSVMfr|
&& |fMRcGIL9M0jLwgsKFZ2w4CLwrTlBEfF8W8dNkk/zAbG/emKouuhM8AdVj0VzCq2UVpEKlNkjj2szv8OE4S6sUr9FOM2KOOENuHAUb4|
&& |KioDzFI655C2+Vxbej5iH4lVM/lI0cBeRHvjsmYuL869A7CMkl8GpeRKaDuhW7XDyIbxI1qTrFtGyKOFjr19pVU/S9jXRwAjLfllh9|
&& |lcXwlV7MCpYZY45ON8XpaaY1nO85gPMBOsnUBpPmTy24n3kBkvjTZYa9kvgyEq9BctIxfA01j6bSbVk8RICPYS3Zl+DNAPybodIDDV|
&& |vSt4QoOrgPBM9YYH7mzkvo7anYcA6ZBJuhMmWoyAt49mTzGQvTp0WigxabHUI9CdXkNLjauOnACQDqLpRtUa7Mz8LIkwHp0832A2wy|
&& |ccQrPjzGAwiG5BRFpLd7yO5vguzlpXT4ausqgjMfmyNCHlDBMEspy2zzMSPm7pX6EMBNNd3zTB8/y7LxWhzyMD6+nZTaETxPo+UfO4|
&& |3hRRAJjj64nb4aRxrVEdxkeIWP9jmY0Q+RO2Ds0jRQbH3o9k5gfMslvP2MhW7xSIP9VPJ1PlXwTzQZlD3M91W5Nr47+PUtcD+ARlwc|
&& |Czmc0vk5mYkjIiRE9p82sCZurkoQZVzKihAD9m9rWNwTafMs05BaDsj2dXCGvtxBrZHCAD5jxdazCeQJCvCIHBR9Cw2VBflA8YPR64|
&& |ErMYVSYnBI5FsRLORZx8fwDdDXAtIhuD3punI6mJNy2hIbWUdt0HZa1HOZt4hyFsWGFkv0uomu7GzYD4Tm221gzaCqbvV7NZO10Nlh|
&& |lmDOpYhXR8SiFgP+8U9Qh8UyAL7pqygBwO7bB5+Ku6p4AFFv1jmZWU6A4E5XRbLIz1zYJu+6YAmPXtog5WQQwgjZbQxWoyyD7QaO3Q|
&& |aJloZMI3qUqzbyNEFIR6NAYvgzmrvRl8Z0qMUckgSpFo9IR65CYfALNCs7tGXatJcfWIOAcU6bGUBeU3YVJEvgzpSXXVQ8R5W9tUoU|
&& |3pDjxOeIREMPdqRAze+kK+DSHbXvw8kylewEVZvVvfVh0cCSrjCSNKB4kni2CHgNEYFfaEFBBZVRKgXKpaw4jSUgcLIXtizhQwo1dh|
&& |akIKKJNCgXLAkXFEIXzcC/ELYnWJY97KL+4wuncFoMLq6MAKAD2ikBjYozE3TqVGIoI4PTipKbR5JV8Kpn/7Oo05se4RPJhTmQkVhu|
&& |UeOl8CTnIv5z4QLm97EmtBHWFTCOD6pEaJcUJwojMRGyCLQet1Q3FYXQc10AjzaEsB1k6oN7cnCfmEAxfJyCcx9WQijCZN44/if4jG|
&& |3z7Wh39AZ/4F2/NP2HCTL6R/+zO+8LmYIvogpsi/JKYwxWZUPvanYrN/Icb1DHMFeqLx/rnCQ+m95+ZcnUkKOL5mzkXkqrmyk5MhkI|
&& |I9Gp+eu5pz6yJMOQAyg/dDOQBTLoVUOAg3+51cSv9sLuWx5N7P5qQeK/8gc3tEESbHSC7/3gC5PdI0QW7PVxt5PLdH5khLrKQgUOya|
&& |C8iRkvw35Uj3bK0IKsE/0ouuXOPNpZaRyQGDeqj0PJNrNuTsaS/1iZy9+r3axAcCgWHtg26MXkZfYVyAN6x9lA+Xpww6QY6pauL1Na|
&& |SYWEN6vDyOWouDEhNKN15fizsTa3FPFBH39JomJSyvr2kqPIM1zWfqzgxrw9RIeNmew4YVDor7uS4DWvnUBwDmKGvskWVYurX2ur+3|
&& |xi6HbOAl1CKsXdijrjWLWu79ARkbLcTtiK5VeK4MCaqklZoPk4Wtdae2wSEsLf0trPl4slRz0b6yUztDqgXApFBQFSaPCWjA3voEBV|
&& |A8pQbJoivOX6xBkmUYa5CernitNeug7+PhdHxQy0XQrwcEwwts5EWkck1cSic6XqiJK7XEwIvVzVptoa1LESC4mCOqUSlr5Qi16ZZe|
&& |x/gYUq3ez+BQLWM+zlCjWahCA/7UkLn6AGD4pVpXcClyRZEdnCLYouQXUOla38ArXduqsigfBEVYkuvHWtfXiu3l7S43qkHW7xXDvr|
&& |x7mMClW8ZGqBjmQjqony1f3FkBWinVXoOJrLHyun+x8prR6XSKWEPtNbH95kGA4Ai5LQfLzbXCdNxI5ftYwW5ZvILdj5PkclXfPE6X|
&& |rlBrb/GjT1XsyYCcNRco223HXmkQdwLkzcDeWk6wEwDHC3cCnGCHQsVaTxYmEBqthXsXa/Bo/uskop8A2anGMhb5Zy24o+KEMgZ7Ku|
&& |ioAkKlUwD0tvnZkndUnCsugSCddOXQowBzMwkHEwBLrFSxNHt7UwSjb0dtsYi7MpY2Qj/9VNhIYBbEvizadIH9NMo7wArK16ZH3aTg|
&& |roxN4bI5Pr5UGS7B4Vv6p+vShiBDKVOEWHE26o7MG4jdm+EV3GDUiucJfH5DVwiacr2TMBw1uwxzRiogOOslVPd9KOHtbAtDevIpgE|
&& |8U9iriLk2FO50WxwEg3lJmEcDZfiMbZTF5y35S3N4q74FU4khiBnWgKnjxS9uHcG/lw4mJD1DBp+97SUGN5KGl8p1EbRX65U1BcC+p|
&& |/7ZzNYB1d3eFe9glkrzJsCd3kiQA/PK2yIB7ch9aRHgQeEDBtrcZt4SINg2WHWJ19eAUKzEb8PUW7PG9ze/akcuRIpHnlS25KkiDrk|
&& |fIfNE6osSsNzxcJO/efHABmqDbXnvcYCrmCEAZ1GnELIfIEbjVVSD4Xvv6lZ1HuwhGtGb8zIJTKbMBKqEVUwhGU8jU4UBwa83PLDjm|
&& |n93mSiHHeJaf/QAJJNH66skaOWWE25jxgIr17Ifki04kqXhAwM/QAILvsWV0VAcbLNT9DI3NFK5naPRfdpZPME6cB866FTbbFKUjzi|
&& |LZnEyL76bbWSSXz0YRe7ArHgvAmS4uknsb4L0zXRo0heF2psv7DDeNIOeRgN94/MyKMx9Q3O5+1xrnLq5hyZX4djaO/3UHumxw15DS|
&& |alqU/r5FBR0kRhY3WxhwypZ2PWNoGr/lJCS7Wo+J8js+8ngAE5zVtEkkSCOe1bQe6xSX65ym/r5zr6qzPK9eKgclUjzzqtXOvErm7z|
&& |2ZqxrlOWw96GeHlTKFxfdSCHCaTppA75/BVv7AGWyINF/0fIV+J17y7zkyjMbvPxNwRdSO9NmKbLL7C85WvEM9o7L9XWdU/uEPf/jD|
&& |H34G/wGmG7NImfqvDAAAAABJRU5ErkJggg==|
&& |" alt="World" style="width:80px;" />|
&& | </div>|
&& | <p style="font-size:12px; color:#000;text-align:center">|
&& |   <b>HELLO WORLD!!!</b><br><br>|
&& | </p>|
&& | </div>|
&& |</body></html>|.


*----------------------------------------------------------------------
* Step 2: Extract all pictures and build new HTML Email Body
*----------------------------------------------------------------------
lv_html_out = lv_html_in.

" Get All Images...
FIND ALL OCCURRENCES OF REGEX `<img\b[^>]*>` IN lv_html_in RESULTS DATA(lt_matches) IGNORING CASE.
LOOP AT lt_matches ASSIGNING FIELD-SYMBOL(<m>).
  DATA(lv_img) = lv_html_in+<m>-offset(<m>-length).

  " Get Source...
  FIND FIRST OCCURRENCE OF REGEX `src="([^"]+)"` IN lv_img SUBMATCHES DATA(lv_source) IGNORING CASE.
  IF sy-subrc = 0 AND lv_source IS NOT INITIAL.

    " BASE64...
    IF to_lower( lv_source ) CS ';base64,'.

      " Get Picture...
      FIND FIRST OCCURRENCE OF REGEX ';base64,(.*)$' IN lv_source SUBMATCHES DATA(lv_base64) IGNORING CASE.
      IF sy-subrc = 0 AND lv_base64 IS NOT INITIAL.

        ADD 1 TO lv_pic_cnt.

        " Get Picture Name...
        DATA(lv_pic_name) = |inline_image_{ lv_pic_cnt }.png|.

        " Append Image Table...
        CLEAR: lv_src.
        CALL FUNCTION 'SCMS_BASE64_DECODE_STR'
          EXPORTING
            input  = lv_base64
          IMPORTING
            output = lv_src
          EXCEPTIONS
            failed = 1
            OTHERS = 2.
        IF sy-subrc <> 0.
          CONTINUE.
        ENDIF.
        " Mime type is hardcoded here for simplicity...
        APPEND VALUE #( name = lv_pic_name
                        mime = 'image/png'
                        src=lv_src  ) TO lt_pic_tab[].

        " Build new Source...
        DATA(lv_new_source) = |cid:{ lv_pic_name }|.

        " Replace Source...
        DATA(lv_new_img) = lv_img.
        REPLACE FIRST OCCURRENCE OF lv_source IN lv_new_img WITH lv_new_source.

        " Replace Image...
        REPLACE FIRST OCCURRENCE OF lv_img IN lv_html_out WITH lv_new_img.
      ENDIF.
    ENDIF.
  ENDIF.
ENDLOOP.


*----------------------------------------------------------------------
* Step 3: Convert HTML-Out STRING to SOLIX
*----------------------------------------------------------------------
lt_html_out[] = cl_document_bcs=>string_to_soli( lv_html_out ).


*----------------------------------------------------------------------
* Step 4: Create MIME Multi-Part Object for Email
*----------------------------------------------------------------------
CREATE OBJECT lo_mime_srv.


*----------------------------------------------------------------------
* Step 5: Add Inline Images (Content-ID Based Embedding)
*----------------------------------------------------------------------
LOOP AT lt_pic_tab ASSIGNING FIELD-SYMBOL(<fs_pic>).
  CLEAR: lt_solix[], lv_len.
  lt_solix = cl_bcs_convert=>xstring_to_solix( <fs_pic>-src ).
  lv_len   = xstrlen( <fs_pic>-src ).

  lo_mime_srv->add_binary_part(
    content      = lt_solix
    content_type = <fs_pic>-mime
    length       = lv_len
    content_id   = <fs_pic>-name ).
ENDLOOP.


*----------------------------------------------------------------------
* Step 6: Set HTML Body into MIME Service
*----------------------------------------------------------------------
lo_mime_srv->set_main_html(
  content     = lt_html_out
  filename    = 'email.htm'
  description = 'Hello World!' ).

*----------------------------------------------------------------------
* Step 7: Create Email Document with Subject
*----------------------------------------------------------------------
TRY.
    lo_doc = cl_document_bcs=>create_from_multirelated(
      i_subject          = 'Hello World!'
      i_multirel_service = lo_mime_srv ).
  CATCH cx_root INTO DATA(lx_root).
    WRITE: /, |Something went wrong....|. RETURN.
ENDTRY.

*----------------------------------------------------------------------
* Step 8: Create and Send Email Using BCS
*----------------------------------------------------------------------
TRY.
    lo_bcs = cl_bcs=>create_persistent( ).
    lo_bcs->set_document( lo_doc ).

    lo_sender = cl_sapuser_bcs=>create( sy-uname ).
    lo_bcs->set_sender( lo_sender ).

    lo_recipient = cl_cam_address_bcs=>create_internet_address(
                     'hello.world@gmail.com' ).
    lo_bcs->add_recipient( lo_recipient ).

    lo_bcs->send( i_with_error_screen = abap_true ).

  CATCH cx_root INTO lx_root.
    WRITE: /, |Something went wrong....|. RETURN.
ENDTRY.

COMMIT WORK AND WAIT.

*----------------------------------------------------------------------
* Final Message
*----------------------------------------------------------------------
WRITE / 'Email sent successfully Check It in SOST. !'.

Output:

Explanation

The program performs the following major steps:

Construct an HTML template containing inline Base64‑encoded images. (But you may get it as local file on your PC or form MIME repository. These options are not considered here ).
Scan the HTML for <img> tags and extract the Base64 image data.
Decode each Base64 image with the help of function module SCMS_BASE64_DECODE_STRE and store it as a binary part for the email.
Replace Base64 data in HTML with CID references (e.g., cid:inline_image_1.png).
Convert HTML to BCS format (SO_DOCUMENT format).
Create a MIME multi-part message via class CL_GBT_MULTIRELATED_SERVICE.
Embed all images as MIME parts so email clients can render them inline.
Assemble the email document with subject, HTML body, and images.
Send the email using BCS to the configured recipient.

This ABAP report builds an HTML email containing Base64‑encoded inline images, extracts and decodes those images, embeds them as MIME parts in the email, rewrites the HTML to use Content‑ID (CID) references, and sends the fully constructed HTML email with inline images using the SAP BCS framework. The email is sent from the logged-on SAP user to a fixed email address and can be traced via transaction SOST.

Thank you for taking the time to read my post. I hope this information helps anyone facing a similar requirement. If you have questions, feedback, or suggestions for improvement, feel free to leave a comment below.

Custom Business Configurations (F4579): Define default grouping and sorting

2026-03-27T13:50:03.260000+01:00

Introduction

The Custom Business Configurations (CUBCO) app serves as an entry point to the Business Configuration Maintenance Object (SMBC) provided by custom applications or partners.

This blog explains how to define the default grouping and sorting for the tables of the business configuration object.
The basic procedure is already explained here, but we apply it directly to the result of the ADT wizard.

This blog is relevant for

Example scenario

Company codes are defined in the configuration table ZDEMO_CC. In the CUBCO app, the rows are to be grouped and sorted by country.

@EndUserText.label : 'Company Code'
@AbapCatalog.enhancement.category : #NOT_EXTENSIBLE
@AbapCatalog.tableCategory : #TRANSPARENT
@AbapCatalog.deliveryClass : #C
@AbapCatalog.dataMaintenance : #ALLOWED
define table zdemo_cc {
  key client            : abap.clnt not null;
  key company_code      : abap.numc(4) not null;
  country               : land1;
  last_changed_at       : abp_lastchange_tstmpl;
  local_last_changed_at : abp_locinst_lastchange_tstmpl;
}

Define presentation variant

First you use the ADT wizard to generate a Business Configuration Maintenance Object for this table.

In the generated CDS view ZI_COMPANYCODE_S of the Singleton entity, you change the facet type from #LINEITEM_REFERENCE to #PRESENTATIONVARIANT_REFERENCE and add the targetQualifier attribute:

  @ui.facet: [ {
    id: 'ZI_CompanyCode', 
    purpose: #STANDARD, 
    type: #PRESENTATIONVARIANT_REFERENCE, 
    targetQualifier: 'myVariant',
    label: 'Company Codes', 
    position: 1 , 
    targetElement: '_CompanyCode'
  } ]
  .lineItem: [ {
    position: 1 
  } ]
  key 1 as SingletonID,

In the metadata extension ZI_COMPANYCODE of the company code entity, add the following presentation variant:

@ui.presentationVariant: [
  {
    qualifier: 'myVariant',
    sortOrder: [
      {
        by: 'Country',
        direction: #ASC
      }
    ],
    groupBy: [ 'Country' ],
    visualizations: [{type: #AS_LINEITEM}]
  }
]
annotate view ZI_CompanyCode with

Finally, open the generated SMBC object ZCOMPANYCODE in ADT and open the table settings section. Change the table type attribute from Grid Table to Responsive Table because grouping is not supported for grid tables. If you only need the default sorting, you can continue to use the grid table.

Our 2026 Roadmap for Joule for Developers ABAP AI capabilities

2026-03-28T20:13:48.908000+01:00

Sapphire 2026 is approaching quickly and as usual it will bring lots of new announcements. So now is the right point in time to recap what has been announced already until Q2/2026 and prepare for the ABAP AI sessions.

The ABAP Platform AI (covering both SAP BTP ABAP Environment and SAP S/4HANA) transitions from a set of independent AI skills to full-scale Agentic AI. The roadmap focuses heavily on developer productivity via Joule and the modernization of ABAP development tools. The key benefits for customers and partners of the roadmap until Q2/2026 are:

ABAP development tools in VS Code with ABAP MCP Server.
ABAP AI for lower releases of SAP S/4HANA Cloud Private Edition (i.e. 2021, 2022, 2023 and 2025).
Simplified customer on-boarding of ABAP AI via SAP for Me and Central Business Configuration.
Faster innovation with Side-by-Side consumption of SAP and 3rd party Agentic IDEs and LLMs
(e.g. Microsoft, Amazon, IBM, OpenAI, Anthropic, Google, Mistral…)

The biggest shift in 2026 will be the move toward Agentic AI, where the existing ABAP AI skills doesn't just explain, complete or generate code (e.g. RAP, CDS, Tests) independently but acts as an autonomous collaborator. This includes built-in ABAP MCP (Model Context Protocol) server. The introduction of VS Code as IDE can only be a start as the depth and breath of Eclipse which we achieved in so many years cannot be reached with one or two steps in VS Code. It'll be a journey which starts with first providing End-to-end UI services development with agents.

The new ABAP AI side-by-side architecture is designed to provide a scalable and future‑proof foundation for ABAP AI capabilities across heterogeneous SAP landscapes. It enables customers to consume ABAP AI services side‑by‑side, independent of the underlying S/4HANA release, ensuring access even for lower‑release Private Edition systems.

A core benefit of the architecture is also its simplified enablement model through SAP for Me and Central Business Configuration, reducing on-boarding effort and ensuring consistent lifecycle management across environments.
In addition, the architecture allows us to accelerate innovation speed by allowing to leverage SAP‑provided ABAP AI models alongside leading third‑party LLMs (e.g., Microsoft, Amazon, IBM, OpenAI, Anthropic, Google, Mistral) more independently from releases. This flexibility ensures rapid adoption of new capabilities without dependency on individual release cycles.

If you missed the highlights we delivered in Q1/2026 have a look into what Olga Dolinskaja shared about ABAP AI ATC finding explain and custom code explain and proposals. Although this will be a focus also for our future roadmap we will also not stop investing into AI app generators like the Embedded Analytics model generator.

Here you can learn more:

More high-level insights about Joule for Developers/ABAP AI and ABAP platform can be found here . Here you find more on ABAP- 1,

Optional Task: Use Joule CDS Unit Test Generation

2026-03-30T06:30:00.020000+02:00

Thank you to everyone who participated in the ABAP Developer Challenge over the past four weeks and successfully completed all four tasks focused on ABAP AI capabilities. We truly appreciate the enthusiasm and engagement shown throughout the challenge. As a follow-up, we are excited to introduce an additional bonus task.

In Week 2, you enhanced a CDS data definition by implementing simple logic. Building on that work, your next step is to create an ABAP test class to validate the logic within the CDS data definition. For this task, you will utilize another feature of Joule’s ABAP AI capabilities — CDS Test Generation.

Task:

Select the CDS data definition that you enhanced in Week 2.
Generate an ABAP test class using Joule’s CDS Test Generation feature.
Execute the test class and ensure that all generated test cases run successfully.

Please refer to the link below for detailed guidance on how to use this ABAP AI capability.

https://help.sap.com/docs/abap-cloud/abap-development-tools-user-guide/use-cds-test-class-generator?locale=en-US

Smaller ABAP Runtime Size Now Available in SAP BTP ABAP Environment

2026-03-31T14:40:48.302000+02:00

Starting March 31, 2026, SAP BTP ABAP environment introduces a new runtime sizing option: 0.5 ABAP Compute Units (ACU) which is 8 GB of runtime memory.

With the introduction of 0.5 ACU, customers can now operate ABAP systems at 50% lower ABAP runtime cost compared to the previous minimum size of 1 ACU making it significantly more cost-efficient to run development, test, and sandbox systems.

This enhancement allows SAP BTP ABAP environment to run on smaller runtime units, lowering the entry barrier for development and test systems.

What is an ABAP Compute Unit (ACU)?

ABAP Compute Units (ACUs) define the runtime capacity of an SAP BTP ABAP environment system. One ACU corresponds to 16 GB of memory allocated to the ABAP runtime. The total runtime size determines how much capacity is available across all ABAP application servers. For more information, see the documentation on ABAP Compute Units.

What’s New?

With this update SAP BTP ABAP environment now supports 0.5 ABAP Compute Units (ACU) as the new minimum system configuration.

It allows to run smaller systems, enabling more granular runtime sizing compared to previous configurations. It creates an additional option to better match the actual workloads, particularly for smaller environments.

What are the Key Benefits?

50% lower ABAP runtime cost compared to the previous minimum size (1 ACU)
Improved resource utilization for smaller or variable workloads
Lower entry barrier for new and existing customers

For a detailed breakdown of cost components, see my previous blog post on ABAP environment cost calculation.

How to Adjust Existing Systems?

Adjusting the ABAP runtime size (ACUs) is handled via manual scaling and does not lead to a system downtime . You can use the SAP BTP Cockpit to update the service instance, for example, from 1 ACU to 0,5 ACU, see the documentation on Updating an ABAP System.

What Needs to be Considered?

For systems with a runtime size of 0.5 ACU, only one application server is used. This setup is suited for development and test, but not recommended for productive use, as it may increase the likelihood of short outages.

Overview about typical use cases and recommend systems sizes

Use Case	Size	Total Runtime Memory	Application Servers
Development, test, sandbox systems for smaller projects	0.5 ACU (new)	8 GB	1 á 8 GB
Development, test, sandbox systems for bigger projects; Productive systems for up to 1,000 active users per day	1 ACU	16 GB	2 á 8 GB
Productive systems with higher concurrency or up to 100 tenants	2 ACU	32 GB	4 á 8 GB
Productive systems with bigger max session size	4 ACU	64 GB	2 á 32 GB
Productive systems with higher load in multitenant SaaS solution	4 ACU	64 GB	8 á 8 GB

Further References

For more information about sizing options and configuration parameters in SAP BTP ABAP environment, see the documentation on Creating an ABAP System.

The Agentic Revolution Is Here — And Your ABAP Code Is the Foundation

2026-04-03T18:00:00.017000+02:00

Three Waves in Two Years

To understand where we are, you need to understand the three inflection points Jensen described. They happened faster than anyone expected.

Wave 1: Generative AI (2022–2023)

ChatGPT changed computing from retrieval-based to generative. Instead of a database returning a record, a model generates an answer. Jensen put it bluntly: "Computing used to be retrieval-based. Now it's generative." The architecture implications of that sentence are enormous and still rippling through every layer of enterprise software.

Wave 2: Reasoning AI (2024)

OpenAI's o1 model introduced something that made generative AI trustworthy: the ability to think. To reflect. To decompose a problem it couldn't solve into steps it could. To ground itself on facts before answering. Reasoning AI made large language models genuinely useful for complex, multi-step work — not just creative writing and summarisation.

Wave 3: Agentic AI (2025–2026)

This is the one that changes your job. Jensen cited Claude Code — the very AI assistant many of us now use daily — as the breakthrough moment:

"Claude Code has revolutionised software engineering. There is not one software engineer at NVIDIA today who is not assisted by an AI coding agent."

The shift is fundamental. With generative AI, you ask a question. With agentic AI, you give a task. The agent reads your files, writes code, compiles it, tests it, finds the failures, fixes them, and iterates — autonomously, in a loop, until the work is done or it needs your input.

Computing demand, Jensen said, has grown one million times in the last two years. That is not a typo. The explosion is driven by agentic inference: every time an agent thinks, plans, reads a file, calls a tool, or generates an output, it burns tokens.

GTC 2026 Keynote — Jensen Huang's enterprise agentic architectures slide (02:02:57). SAP is bottom-left. Each diagram is a production blueprint, not a roadmap.

What Jensen Showed at 02:02:57

At just over two hours into the keynote, Jensen showed a slide he called a renaissance. Each of the twelve architecture diagrams was a real, production blueprint. Not a roadmap. Not a vision. Each company had already rebuilt its product around AI agents.

"This is a reinvention. A renaissance of enterprise IT. Every single SaaS company will become an Agentic as a Service company. No question about it."

He compared it to three previous platform shifts:

When Linux arrived → every company needed a Linux strategy
When HTML/HTTP arrived → every company needed a web strategy
When Kubernetes arrived → every company needed a cloud-native strategy
Now Now OpenClaw (the open-source agentic OS) has arrived → every company needs an agentic strategy

NemoClaw and SAP: A Security Partnership

Jensen announced NemoClaw as NVIDIA's enterprise-hardened version of OpenClaw. To understand where it fits in the SAP picture, it helps to be precise about what it is — and what it is not.

OpenClaw is, in Jensen's words, "the operating system of agentic computers." It handles task decomposition, sub-agent spawning, tool calling, file access, cron scheduling, multi-modal I/O, and LLM orchestration. It reached more GitHub stars in a few weeks than Linux achieved in thirty years.

The enterprise problem with a system that can "access sensitive information, execute code, and communicate externally" is obvious. You cannot deploy raw OpenClaw in an SAP landscape and have it reach your vendor master, financial postings, and HR records without controls.

NemoClaw solves this by adding three security layers on top of OpenClaw:

Layer	What It Does
OpenShell	Sandboxes agent execution; controls what it can read, write, and call
Policy Engine	Enforces the enterprise's own business rules
Network Guardrail + Privacy Router	Prevents data leaving the enterprise boundary

Important clarification: NemoClaw is not the foundation SAP Joule is built on. Joule is SAP's own product, with its own architecture, models, and AI infrastructure running on BTP and SAP AI Core. NemoClaw is NVIDIA technology that SAP — as a launch enterprise partner — is integrating as an optional security and governance layer within BTP, tied specifically to Joule Studio. It is available for customers who require the strongest possible compliance controls when agents interact with sensitive ERP, financial, or supply chain data.

The architecture looks like this:

The bottom line for ABAP developers remains unchanged regardless of which security envelope is in play: when an agent needs to do something in SAP — read a purchase order, create a vendor, trigger a workflow, query a cost centre — it calls your ABAP.

Your BAPIs. Your CDS views. Your OData services.

What This Means in Practice

Let me make this concrete with an example that exists today.

A procurement manager asks Joule: "Which of our top twenty suppliers have delivery performance below 90% this quarter, and what is the total open invoice value against them?"

In the pre-agentic world, someone writes a report in SE38, schedules it, exports to Excel, and manually cross-references two tables. Elapsed time: hours, or days if it hits a queue.

In the agentic world, Joule:

Decomposes the question into sub-tasks
Calls a procurement agent → queries I_SupplierDeliveryPerformance CDS view via OData
Calls a finance agent → queries I_SupplierOpenItemMD CDS view via OData
Synthesises both results
Returns a structured answer in seconds

The entire chain runs through NemoClaw's policy engine and your ABAP authorization framework. The agent's service user has only the authorizations you have granted. Every CDS view it accesses must have the proper access control annotation and a corresponding DCL.

The Four Things Your ABAP Must Get Right
If agents are going to call your code — and they are — four things matter more than they ever did before.

1. Clean, Annotated CDS Views

CDS views are the primary structured data interface for AI agents in SAP. An agent does not navigate transaction codes. It calls OData endpoints backed by CDS. If your CDS views lack semantic annotations, have incomplete access control, or expose data structures that predate any logical data model, they become a liability.The minimum bar for agent-ready CDS:

@AccessControl.authorizationCheck: #CHECK
@EndUserText.label: 'Supplier Delivery Performance'
@VDM.viewType: #CONSUMPTION
@OData.publish: true
define view entity I_SupplierDeliveryPerformance
  as select from ...
{
  @Semantics.businessPartner.role: #SUPPLIER
  SupplierID,

  @Semantics.quantity.unitOfMeasure: 'DeliveryUnit'
  ConfirmedDeliveryQty,

  @Semantics.percentage
  OnTimeDeliveryRate
}

Semantic annotations tell the LLM what each field means. Without them, the agent is guessing from column names. With them, it can reason correctly.

2. Authority Checks on Every Agent-Callable Interface

NemoClaw's policy engine delegates final security enforcement to ABAP. This is not a weakness — it is the correct architecture. The LLM should not be trusted with authorization decisions. ABAP should.
Every function module, BAPI, and method that an agent can call must perform an explicit authority check:

METHOD get_supplier_invoice_data.
  AUTHORITY-CHECK OBJECT 'F_LFA1_BUK'
    ID 'BUKRS' FIELD iv_company_code
    ID 'ACTVT' FIELD '03'.

  IF sy-subrc <> 0.
    RAISE EXCEPTION TYPE cx_sy_authorization_check
      EXPORTING
        textid = cx_sy_authorization_check=>no_authorization.
  ENDIF.

  " ... proceed with data retrieval
ENDMETHOD.

An agent running as a service user with overly broad authorizations is an insider threat waiting to happen. Lock it down at the ABAP layer.

3. Machine-Speed Performance

A human clicks a button every thirty seconds. An agent may call your BAPI ten thousand times per hour. An interface that performs acceptably under human load may collapse completely under agent load.
Review your agent-callable interfaces against these criteria:
• No SELECT * in performance-critical paths — agents fetch data in loops, field-level selects only.
• Buffer vendor master, material master, and configuration data where appropriate.
• Avoid dialogue modules and unnecessary commits in agent-exposed interfaces — agents expect atomic, stateless calls.
• Consider ABAP Cloud compatibility — if you are on S/4HANA, agent integrations will increasingly come via BTP.

4. Reliable, Structured Error Returns

Agents chain multiple tool calls into a single business process. If step three of a five-step chain fails silently — no exception raised, just a blank result set — the agent may proceed with corrupted state and complete a transaction based on missing data.
Your interfaces need to fail loudly, clearly, and catchably:

METHOD create_purchase_requisition.
TRY.
" ... BAPI call
IF lt_return[] IS NOT INITIAL.
LOOP AT lt_return INTO ls_return
WHERE type = 'E' OR type = 'A'.
RAISE EXCEPTION TYPE cx_pr_creation_failed
EXPORTING
message = ls_return-message
message_id = ls_return-id
number = ls_return-number.
ENDLOOP.
ENDIF.
CATCH cx_sy_authorization_check INTO DATA(lx_auth).
RAISE EXCEPTION TYPE cx_pr_creation_failed
EXPORTING message = 'Authorization check failed'.
ENDTRY.
ENDMETHOD.

A well-structured exception gives the orchestration layer the information it needs to retry, compensate, or escalate. A dump gives it nothing.

Physical AI: Why EWM and IBP Developers Should Pay Close Attention

Jensen spent a significant portion of the keynote on physical AI — robots, autonomous vehicles, digital twins. At first glance this might seem distant from ABAP. It is not.

He announced partnerships with ABB, KUKA, Universal Robots, BYD, Hyundai, Nissan, and Geely — collectively representing the automation of manufacturing floors and logistics networks at a scale never seen before. These physical systems will generate transactions. Inventory movements, goods receipts, production confirmations, delivery completions — triggered by machines at machine speed, not by warehouse workers scanning barcodes.

If you work in SAP Extended Warehouse Management, SAP Integrated Business Planning, or SAP Manufacturing Integration and Intelligence, the interfaces you build today will be called by robots tomorrow. The same four principles apply — and the performance requirement becomes even more acute.

Your Learning Roadmap

The field is moving fast. But not everything needs to be learned at once. Here is how I would prioritise it.

Start Now — Zero Extra Investment Required

AI tools today. Use AI coding tools on real ABAP work — every unit test, every code review, every CDS view.
Learn what SAP Joule can already do. Log into your BTP account and explore the Joule capabilities available today.
Audit your CDS views. Run a quick check across your landscape for CDS views with @AccessControl.authorizationCheck: #NOT_REQUIRED — these are potential agent-accessible data leaks.

Next Three to Six Months

ABAP RAP (RESTful Application Programming Model). If you have been deferring it, stop. RAP is the model that produces the OData V4 services that Joule agents consume.
SAP AI Core and SAP BTP basics. You do not need to become a BTP developer. Understand the platform well enough to design ABAP interfaces that integrate cleanly with it.
Python literacy. Not fluency — literacy. Most AI tooling and agent orchestration frameworks are Python-first. Being able to read a Python agent script is now a professional responsibility.

Strategic Awareness

OpenClaw and MCP (Model Context Protocol). OpenClaw is the open-source agent OS. MCP is the protocol that defines how agents discover and call tools. SAP Joule implements MCP under the hood.
HANA Vector Engine. HANA Cloud's vector engine brings unstructured data (PDFs, emails, contracts) directly into your SAP data layer.

The Part Nobody Is Saying Loudly Enough

Jensen made a prediction that deserves more attention than it received.

In the near future, every engineer at NVIDIA will receive an annual token budget — roughly equivalent to half their salary in additional compensation — because AI-amplified engineers are demonstrably ten times more productive. Engineers are already asking: "How many tokens come with this job?"

Here is the part that matters for us specifically:

AI tokens without SAP domain expertise produce plausible-looking but wrong ABAP. An LLM that does not understand the difference between a financial posting document and a parked document will generate code that compiles, passes basic tests, and silently corrupts your general ledger. It will call RFC_READ_TABLE in production because it found an example online. It will bypass the credit check in a sales order because it did not know the check existed.

Your twenty years of knowing where the bodies are buried in SAP — that is not a liability in an AI-augmented world. It is the irreplaceable ingredient that makes the AI's output correct and trustworthy.

The developers who will thrive are not the ones who resist this shift. And they are not the ones who hand everything to an LLM and hope for the best. They are the ones who treat AI as a powerful amplifier of their own judgment — who know enough to direct it well, verify its output, and design the systems it integrates with.

That combination — deep SAP domain knowledge plus AI tool fluency — is genuinely rare right now. The window to build it is open. It will not stay open long.

Wrapping Up

GTC 2026 was not a technology conference for GPU enthusiasts. It was a signal that the enterprise software industry has passed an inflection point. Jensen's slide showing SAP, Salesforce, ServiceNow, and Siemens side by side — each with a production agentic architecture — was not a prediction of what is coming. It was a photograph of what has already happened.

SAP has placed its bet. Joule is real, BTP is the platform, and the structured data of your SAP landscape — managed, modelled, and secured by ABAP code — is what gives every agent running on top of it the ground truth it needs to be useful.

Action Items

✓ Write clean CDS views.

✓ Lock down your authority checks.

✓ Tune for machine-speed consumption.

✓ Raise clear exceptions.

✓ Learn RAP.

✓ Open Claude Code.

The revolution is not coming for your job. It is coming for the parts of your job that should have been automated years ago. What remains — and what becomes more valuable — is everything that requires judgment, domain knowledge, and the ability to see when the AI is confidently wrong.

That is the ABAP developer of 2026.

Joule for Developers ABAP AI Sapphire and ASUG 2026 Sessions

2026-04-04T17:52:59.936000+02:00

In case you do not have planned your Sapphire and ASUG agenda here are my recommendations if you want to learn about the latest innovations from ABAP Platform and Joule for developers (J4D) ABAP AI capabilities:

1. Introduction to ABAP Cloud supported by generative AI | BTP1429: Get an overview on ABAP Cloud and recent innovations, get insights on Clean Core and see how generative AI boosts your adoption of ABAP Cloud conducted by Alexander Rother (VP, Head of ABAP Platform Product Management).

2. Build smarter: Agentic ABAP development tools for Visual Studio Code | BTP2573: Simona Marincei (Head of AI - SAP ABAP Platform) will show how ABAP agents orchestrate in VS Code via the ABAP MCP-server tasks, speed up coding, and boost productivity across orchestrators from various partners.

3. Agentic ABAP with SAP Joule for Developers: Build faster, migrate smarter | JOU1428: Simona Marincei (Head of AI - SAP ABAP Platform) and Nora Klemp (Senior Product Specialist) will explain how agentic ABAP accelerates SAP S/4HANA migrations and streamline ABAP Cloud development across modern and legacy environments.

4. Customer Influence and feedback: The product road map for ABAP Cloud | BTP1603: Learn from Alexander Rother (VP, Head of ABAP Platform Product Management) how to give feedback to the ABAP product roadmap with the Customer Influence site which allows submitting, tracking, and prioritizing ideas.

5. Modernize classic extensions for clean core in SAP Cloud ERP Private | BTP1426: Volker Drees (Product Expert, ABAP Cloud, SAP SE) will explain clean core extensibility practice in SAP S/4HANA Cloud Private Edition. Learn how to govern clean core development using the ABAP test cockpit and how to use the ABAP Cloud development model and clean core extensibility principles to modernize your custom on-stack extensions.

The full Sapphire and ASUG 2026 agenda can be found here.

Here you can learn more:

More high-level insights about Joule for Developers/ABAP AI and ABAP platform can be found here . Here you find more on ABAP- 1,

How I Connected Claude AI to My SAP ABAP System Using MCP — A Complete Windows Guide

2026-04-07T12:35:07.976000+02:00

Introduction

The SAP developer community has been buzzing about connecting Claude AI directly to live SAP ABAP systems using MCP (Model Context Protocol) — reading code, modifying objects, creating transports, and activating changes, all from a natural language chat interface.

I tried it myself on Windows, and it works. This blog walks you through exactly how to set it up.

What is MCP?

MCP (Model Context Protocol) is an open standard that lets AI models like Claude connect to external tools and data sources. Think of it as a plugin system for AI — instead of just answering questions from training data, Claude can actually call tools that interact with real systems.

For SAP developers, this means Claude can:

Read your actual ABAP code directly from your system
Write and modify objects
Run syntax checks
Create transport requests
Activate objects

All without you copy-pasting anything.

The Architecture

Claude Desktop / Claude Code CLI         ↕ MCP Protocol  ┌──────────────────────────┐  │   mcp-abap-adt           │  ← Read-only (13 tools)  │   mcp-abap-abap-adt-api  │  ← Full CRUD (30 tools)  └──────────────────────────┘         ↕ ADT REST API    Your SAP ABAP System

Both MCP servers were built by Mario Andreschak and communicate with SAP via the same ADT (ABAP Development Tools) API that Eclipse uses under the hood.

Prerequisites

Before starting, you need:

Windows 10 or 11 (64-bit)
An SAP ABAP system with /sap/bc/adt active in SICF
A user with SAP_ADT_DEVELOPER role (or equivalent)
A Claude Pro/Max/Team subscription at claude.ai
Internet connection

Step 1 — Install Node.js

Node.js is the runtime required by Claude Code CLI and the MCP servers.

Go to https://nodejs.org and download the LTS version
Install with all defaults
Verify in Command Prompt:

node -v    → v24.x.xnpm -v     → 11.x.x

Step 2 — Install Git for Windows

Git provides the bash shell Claude Code requires on Windows.

Go to https://git-scm.com/downloads/win and download the installer
During setup, on the PATH screen select: "Git from the command line and also from 3rd-party software"
Complete with all other defaults

Step 3 — Install Claude Code CLI

cmd

npm install -g @anthropic-ai/claude-codeclaude --version

Then log in:

cmd

claude

Select option 1 (Claude subscription), log in via browser, return to terminal.

Step 4 — Install mcp-abap-adt (Read-Only MCP Server)

This server gives Claude read access to your SAP system with 13 tools including GetProgram, GetClass, GetFunction, GetTable, SearchObject, and more.

cmd

mkdir C:\Toolscd C:\Toolsgit clone https://github.com/mario-andreschak/mcp-abap-adtcd mcp-abap-adtnpm installnpm run build

Create a .env file in the folder:

SAP_URL=https://your-sap-system.com:44300SAP_USERNAME=YOUR_USERNAMESAP_PASSWORD=YOUR_PASSWORDSAP_CLIENT=300TLS_REJECT_UNAUTHORIZED=0

cmd

claude mcp add mcp-abap-adt node C:/Tools/mcp-abap-adt/dist/index.jsclaude mcp list

You should see: mcp-abap-adt: ✓ Connected

Step 5 — Install mcp-abap-abap-adt-api (Full CRUD Server)

This is the powerful one — 30 tools including read, write, syntax check, activate, lock/unlock, and transport management.

cmd

cd C:\Toolsgit clone https://github.com/mario-andreschak/mcp-abap-abap-adt-api.gitcd mcp-abap-abap-adt-apinpm installnpm run build

Create .env (note: slightly different variable names):

SAP_URL=https://your-sap-system.com:44300SAP_USER=YOUR_USERNAMESAP_PASSWORD=YOUR_PASSWORDSAP_CLIENT=300SAP_LANGUAGE=ENNODE_TLS_REJECT_UNAUTHORIZED=0

cmd

claude mcp add mcp-abap-adt-api node C:/Tools/mcp-abap-abap-adt-api/dist/index.js

Step 6 — Setup Claude Desktop (GUI Interface)

Claude Desktop is where it really comes alive — a beautiful chat UI like the LinkedIn video.

Download from https://claude.ai/download
Install and log in
Go to ☰ → Settings → Developer → Edit Config
Replace the content with:

json

{
  "mcpServers": {
    "mcp-abap-adt": {
      "command": "C:\\Program Files\\nodejs\\node.exe",
      "args": ["C:\\Tools\\mcp-abap-adt\\dist\\index.js"],
      "env": {
        "SAP_URL": "https://your-sap-system.com:44300",
        "SAP_USERNAME": "YOUR_USERNAME",
        "SAP_PASSWORD": "YOUR_PASSWORD",
        "SAP_CLIENT": "300",
        "TLS_REJECT_UNAUTHORIZED": "0"
      }
    },
    "mcp-abap-adt-api": {
      "command": "C:\\Program Files\\nodejs\\node.exe",
      "args": ["C:\\Tools\\mcp-abap-abap-adt-api\\dist\\index.js"],
      "env": {
        "SAP_URL": "https://your-sap-system.com:44300",
        "SAP_USER": "YOUR_USERNAME",
        "SAP_PASSWORD": "YOUR_PASSWORD",
        "SAP_CLIENT": "300",
        "SAP_LANGUAGE": "EN",
        "NODE_TLS_REJECT_UNAUTHORIZED": "0"
      }
    }
  }
}

⚠️ Windows-specific tip: You MUST use the full path C:\\Program Files\\nodejs\\node.exe — using just "node" does not work in Claude Desktop on Windows. Also note double backslashes \\ in all paths.

Kill Claude in Task Manager and reopen
Go back to Settings → Developer — you should see both servers listed as running ✅

Step 7 — Add Free Official SAP MCP Servers

Bonus: Claude Desktop has a built-in directory of official SAP MCP servers. Click "Connect your tools to Claude" at the bottom of the chat, search for "SAP", and add:

SAPUI5 MCP Server — for UI5 development
SAP CAP MCP Server — for CAP projects
SAP Fiori MCP Server — for Fiori Elements apps

Also add these free hosted servers to Claude Code CLI (no installation needed):

cmd

claude mcp add --transport http abap-docs https://mcp-abap.marianzeis.de/mcpclaude mcp add --transport http sap-docs https://mcp-sap-docs.marianzeis.de/mcp

These give Claude access to the full ABAP keyword documentation across 8 SAP releases, ABAP cheat sheets, CAP docs, UI5 docs, and SAP Community posts.

Testing It

Open Claude Desktop, create a New Chat, and type:

Get the source code of program SAPMV45A

Watch Claude automatically call your SAP system, retrieve the source code, and explain it — all in seconds.

For write operations (test on $TMP objects only!):

Find a simple Z program in $TMP, add a comment at the top saying "Modified by Claude", save and activate it

For complex workflows like the LinkedIn video:

Connect to my SAP system. Copy class ZCL_SOURCE from package ZPKG_A into ZPKG_B, rename it to ZCL_TARGET, change the carrier_id in the SELECT for /DMO/CONNECTION, create a transport and activate.

Security Notes

Never commit .env files to Git
Change your SAP password if shared in screenshots
Use dedicated service accounts with minimum required authorizations
Only test write operations in $TMP before moving to real packages
The TLS_REJECT_UNAUTHORIZED=0 flag disables SSL validation — use only in dev environments
Check your company's AI policy before sending code to external APIs

My Experience

What surprised me most is how Claude handles the entire workflow autonomously. It doesn't just write code — it searches for the object, reads the source, understands the structure, reads class includes, creates the transport, locks the object, writes the code, runs a syntax check, activates, and unlocks. All from one natural language request.

Important Hint

It can make ABAP-specific mistakes (like forgetting RAP locking fields, or using reserved DDIC words). Always review AI-generated code before activating in production. But as a development accelerator and code reviewer, it's genuinely powerful.

References

GitHub: mcp-abap-adt — Mario Andreschak
GitHub: mcp-abap-abap-adt-api — Mario Andreschak
GitHub: sap-skills — 35 Claude Code plugins for SAP
Blog: SAP Docs MCP Server — Marian Zeis
Blog: Claude Code via MCP — SAP Community
Blog: Installing and Extending an ABAP MCP Server — SAP Community

I hope this helps other ABAP developers get started. If you run into issues or have questions, feel free to comment below. Happy coding!

HRFORM - Sending Payslips to Individual Employees from SAP to Outlook or Mails - for all countries

2026-04-07T13:23:33.058000+02:00

Introduction

Are you an ABAP developer working in the HCM module, HR ABAP? Explore this blog to learn how to create a custom program for sending employee pay slips by mail.

Requirement

Even though Payslips are accessible in EC, clients will often ask us to send them by mail as attachments.

Challenges

1. There are no standard reports available for all the countries to send payslips by mail, like the one for India.
2. Also, developing a report from scratch is very complex for HR Forms.

Steps to create a custom report

1. We are not going to create a report from Scratch; SAP already developed a report for India HINU_HRFORMS_MAIL, but for other countries, standard reports are not available.

Changes in the report: Change the default constant and parameter values (your custom HR Form name, country grouping, payroll area for your country, etc).

Code for your reference

CONSTANTS : gc_applogname    TYPE balobj_d VALUE 'ZHRPAYSLIP',
            gc_applogsubname TYPE balsubobj VALUE 'ZHRFORM_MAIL'.
PARAMETERS: p_molga          LIKE thrforms_01-molga VALUE CHECK DEFAULT '24',
            p_fclass         TYPE hrf_class VALUE CHECK DEFAULT 'PAYSLIP', "thrforms_01-formclass
            p_fname          LIKE thrforms_01-infonet OBLIGATORY DEFAULT 'ZHR_PAYSLIP'.

2. This report will work after implementing the BADI HRFORM_HRF02; otherwise, we can only display the payslip.

3. Write your own logic to send mail in the method AFTER_PDF_PRINT. Also sample implementation class is available for our reference.

Report Analysis

1. This is a SUBMIT program of the HRFORM report.

2. It needs a BADI implementation of HRFORM_HRF024.

3. Functionality is the same as HRFORM display tcode, e.g., PC00_M24_HRF, etc.

4. Designed with SLG1 log. (log gets updated in SLG1 after running the report).

Results & thoughts

With the help of the HINU_HRFORMS_MAIL report, we can develop our custom report to send a payslip as an attachment to all employees. And it would be better if SAP had given a standard report for other countries, too or else any SAP Support Note for reference, mentioning this report.

Custom Business Configurations (F4579): Collaborative draft

2026-04-08T10:55:35.536000+02:00

Introduction

The Custom Business Configurations (CUBCO) app serves as an entry point to the Business Configuration Maintenance Object (SMBC) provided by custom applications or partners.

When you use the ADT wizard to generate a Business Configuration Maintenance Object, the singleton pattern is used when generating the draft enabled RAP BO. One characteristic of this pattern is that all child entities are locked together, so it is not possible for multiple users to work with the same configuration at the same time.

This blog describes how to avoid this restriction by using collaborative draft.

This blog is relevant for

Example scenario

In the configuration table ZDEMO_CC, the company codes are stored.

@EndUserText.label : 'Company Code'
@AbapCatalog.enhancement.category : #NOT_EXTENSIBLE
@AbapCatalog.tableCategory : #TRANSPARENT
@AbapCatalog.deliveryClass : #C
@AbapCatalog.dataMaintenance : #ALLOWED
define table zdemo_cc {
  key client            : abap.clnt not null;
  key company_code      : abap.numc(4) not null;
  country               : land1;
  last_changed_at       : abp_lastchange_tstmpl;
  local_last_changed_at : abp_locinst_lastchange_tstmpl;
}

Enable collaborative draft

In the generated behavior definition, add "collaborative" to the draft annotation:

managed with additional save implementation in class ZBP_I_COMPANYCODE_S unique;
strict;
with collaborative draft;

Add the draft query annotation and the share action to the singleton entity definition:

define behavior for ZI_CompanyCode_S alias CompanyCodeAll
draft table ZDEMO_CC_D_S query ZR_DEMO_CC_CD
[...]
{
  draft action Share;
  [...]
}

Right-click the singleton draft table and choose New Data Definition to create the CDS view for the draft query:

@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Draft Query View'
define view entity ZR_DEMO_CC_CD
  as select from zdemo_cc_d_s
{
  key singletonid                   as Singletonid,
      lastchangedatmax              as Lastchangedatmax,
      transportrequestid            as Transportrequestid,
      draftentitycreationdatetime   as Draftentitycreationdatetime,
      draftentitylastchangedatetime as Draftentitylastchangedatetime,
      draftadministrativedatauuid   as Draftadministrativedatauuid,
      draftentityoperationcode      as Draftentityoperationcode,
      hasactiveentity               as Hasactiveentity,
      draftfieldchanges             as Draftfieldchanges
}

You need to enhance the authorization of the involved users. In SAP BTP ABAP environment and SAP S/4HANA Public Cloud Edition you assign business catalog SAP_CORE_BC_RAP_DRAFT_PC to the user, in SAP S/4HANA Private Cloud Edition authorization object S_DRAFT.

Collaboration

User TB is creating a new company code 400 while at the same time user PW is editing company code 100. All changes are recorded on the same transport request.

Since the collaborative draft is enabled for the singleton root entity, the save and discard draft action are applied to all object changes. In this example, users PW and TB process two different company codes, which are logically different objects. Technically, however, they process the same singleton root entity. In practice, this means that discarding the draft or saving must be aligned between the users involved, as the save action persists the changes in all company codes.
For completely independent editing of individual objects, you must develop a RAP BO without a singleton pattern.

GitHub Copilot for SAP ABAP in VS Code: Setup Guide for On-Premise Teams

2026-04-09T08:24:40.755000+02:00

How I Got Here — My Personal Experience

I’ve been working in SAP for close to 20 years now. Over that time, I’ve seen the development landscape evolve from SE38 and SE80 to Eclipse ADT, from classical ABAP to ABAP OO, and now RAP. But nothing has shifted the day-to-day developer experience as quickly as AI-assisted coding.

When our team started discussing AI tools for ABAP development, the first name that came up was SAP Joule. It looked promising, deeply trained on SAP code, integrated into Eclipse ADT, and purpose-built for ABAP. But when I dug into the availability details, I hit a wall: Joule for Developers is not available for on-premise S/4HANA systems. Our landscape is on-premises, and that wasn’t going to change overnight.

So I started exploring what else was out there. I looked at Amazon Q Developer, which has strong ABAP capabilities and an impressive ABAP Accelerator MCP server. But it required standing up AWS infrastructure. Then I checked GitHub Copilot and realized our organization already had Copilot Business licenses under our GitHub Enterprise agreement. The path of least resistance was clear.

I set it up on a Friday afternoon. By Monday morning, I was using it in real development work. The speed at which I became productive surprised me. I honestly expected a longer ramp-up.

What Surprised Me Most

I initially set up Copilot in both Eclipse ADT and VS Code, expecting roughly the same experience. I was wrong. The Eclipse plugin gives you solid code completions and a useful chat panel, but VS Code with Agent Mode is on a different level entirely. The first time I described a multi-step task in natural language and watched the agent plan its approach, create files, and iterate on errors autonomously, I knew this was going to change how my team works.

One moment that stood out: I pointed Agent Mode at a legacy report that nobody on the current team had written. Within minutes, it had analyzed the entire program, generated a functional description, flagged two performance issues with nested SELECTs, and suggested refactored code with JOINs. That single interaction would have taken a developer half a day to do manually.

Another area where I’ve seen real value is unit test generation. Let’s be honest, ABAP Unit tests are often the first thing that gets cut from project timelines. With Copilot’s /tests command, you can generate a solid test scaffold in seconds. It’s not perfect, you still need to review and adjust, but it removes the biggest barrier, which is the blank-page problem of writing test classes from scratch.

The AI Landscape for On-Premise ABAP Teams

If you’re on an on-premise SAP system, here’s where things stand today:

Solution	On-Premise?	IDE Support	Key Consideration
SAP Joule	No	Eclipse ADT	Cloud only (BTP / S/4HANA Cloud)
Amazon Q Developer	Yes	Eclipse, VS Code, BAS	Requires AWS ecosystem
GitHub Copilot	Yes	Eclipse ADT, VS Code	Broad model choice, mature Agent Mode

I went with GitHub Copilot because we already had the licenses. Your mileage may vary, if your organization is on AWS, Amazon Q Developer is absolutely worth evaluating. The important thing is that on-premise ABAP teams are no longer locked out of AI-assisted development.

Eclipse vs. VS Code — What I Found

For AI-powered development tasks, VS Code with Copilot Agent Mode is in a different league.

Eclipse ADT + Copilot: Good code completions, a helpful chat panel, and basic agent support that’s been improving with each release. For day-to-day ABAP work, it’s a meaningful step forward.

VS Code + Copilot: Everything Eclipse has, plus fully autonomous Agent Mode with multi-step planning, terminal integration, and direct SAP system awareness through the ABAP FS extension. This is where I do my complex development work now.

Installation Steps

Here’s the exact setup I followed. The whole process took me about 30–45 minutes, and I was productive immediately after.

Step 1: Install Visual Studio Code

Download and install the latest version of VS Code from code.visualstudio.com. I’d recommend getting the latest stable release — older versions may not support all Copilot features.

Step 2: Install ABAP Remote Filesystem Extension

This is the extension that makes VS Code talk to your SAP system. Without it, Copilot has no ABAP context — with it, the AI can see your actual system objects.

Open VS Code and navigate to Extensions (Ctrl+Shift+X)
Search for and install ABAP Remote Filesystem

Click on the extension settings to configure

Click on Abapfs: Remote to add your SAP system

Add the SAP system connection details. I configured both our DEV and SBX systems here. Use placeholder values if you’re just testing the setup initially.

Step 3: Install SAP Web IDE Adapter for VS Code

This extension enables SAP-specific development workflows within VS Code. It’s a small addition but it rounds out the SAP development experience.

From the Extensions marketplace, install SAP Web IDE Adapter

Step 4: Install SAP Joule Studio Code Extension

Even though Joule isn’t available for on-premise ABAP, I installed the Joule Studio Code Editor extension anyway — it’s useful if you also work with BTP environments, and it doesn’t interfere with Copilot.

Install SAP Joule (Joule Studio Code Editor) from the Extensions marketplace

Step 5: Install GitHub Copilot Extension

This is the main event. Install the GitHub Copilot extension and sign in with your company’s GitHub account.

Install GitHub Copilot from the VS Code Extensions marketplace

A tip from my experience: if your company uses SSO for GitHub, make sure you complete the authentication through the browser window that pops up. I initially missed this and spent 10 minutes wondering why Copilot wasn’t activating.

Step 6: Activate ADT Service on SAP System

This is the SAP Basis step. Make sure the ADT service is active in transaction SICF. If your Basis team hasn’t already enabled this for Eclipse ADT, you’ll need to request it.

Step 7: Connect to the SAP System

Now connect VS Code to your SAP system. This is the moment where everything comes together.

Open the Command Palette (Ctrl+Shift+P)
Run: ABAP FS: Connect to an ABAP system

Select the SAP system to connect

Step 8: Verify SAP System Connection

Once connected, you should see your SAP system’s object tree in the Explorer pane. When I first saw our $TMP package, Core Data Services, and Source Code Library appear in VS Code, it felt like two worlds merging.

Confirm the connected SAP system appears under ABAP Remote Filesystem
You should now be able to browse SAP objects remotely

Step 9: Verify GitHub Copilot and Model Availability

Finally, confirm that Copilot is active and check which AI models your organization has approved. In our case, we have access to Claude Haiku, Claude Opus, Claude Sonnet, and GPT models. I primarily use Claude Haiku for quick tasks and Claude Sonnet for complex agent work.

Confirm that GitHub Copilot is active in the editor
Verify that your company-approved AI models are available

Quick Start: Using Copilot for ABAP in VS Code

Once installed, open the Copilot Chat panel (Ctrl+Alt+I) and choose your mode. Here’s how I use each one in practice:

Ask Mode — My Go-To for Quick Answers

I use this multiple times a day. Instead of searching SAP Help or opening a browser, I just ask Copilot directly in the IDE. It’s especially useful for BAPIs and function modules I don’t work with regularly.

“Explain how BAPI_USER_GET_DETAIL works”

“Best practices for exception handling in ABAP OO?”

Edit Mode — For Targeted Refactoring

When I have existing code open and want specific changes, I select the code, press Ctrl+I, and describe what I need. This has been particularly useful for modernizing older code patterns.

“Refactor this to use NEW instead of CREATE OBJECT”

“Optimize this to use a JOIN instead of nested SELECTs”

Agent Mode — Where the Magic Happens

This is the feature that changed my workflow. I describe a complex task and let the agent figure out the approach. It plans, generates, reviews its own output, and iterates. Not every result is perfect on the first try, but the starting point it gives you is usually 70–80% there.

“Create an ABAP class ZCL_BP_VALIDATOR with unit tests for BP number validation”

“Analyze program ZSALES_ORDER_REPORT — generate documentation and flag performance issues”

“Create a complete RAP application for insurance claims with CDS views, behavior definition, and service binding”

Slash Commands I Use Daily

These are quick shortcuts in the chat panel that I’ve made part of my routine:

/explain — I use this constantly on unfamiliar legacy code
/fix — Helpful when I get a syntax error I can’t immediately spot
/tests — My favorite — generates unit test scaffolds in seconds
/doc — Generates inline documentation for methods and classes

Creating and Searching Custom Objects

One thing I didn’t expect was how smooth object creation is directly from VS Code. Enter the ‘>’ command to list options, then select ABAP Create Object.

Select the object type to be created

Enter the object name

Enter the description

Enter the package and transport number to save

For searching existing objects, use the ABAP Search for Object command. The filter option is handy when you’re looking for a specific object type.

Custom Instructions — This Is a Game-Changer

If you set up only one additional thing beyond the basic installation, make it this. Custom Instructions tell Copilot how your team writes code — your naming conventions, your preferred patterns, your performance rules. Without them, Copilot gives you generic ABAP. With them, it gives you code that looks like your team wrote it.

Create a file called .github/copilot-instructions.md under each connected system. You define your rules in plain English, and Copilot follows them automatically across all suggestions.

The instructions I set up for our team enforce:

Use of modern ABAP syntax (7.55+) — no legacy patterns in new code
Our naming conventions (ZCL_*, ZIF_*, ZCX_* prefixes)
Performance-safe data access patterns (CDS-first, no SELECT *)
Domain-specific knowledge for our business context
Under each system, add a folder ‘.github’ and a file ‘copilot-instructions.md’

You can deploy centrally or explore global deployment options with your GitHub Administrator
Below is a sample of the instruction file I created for our team

A personal observation: after deploying Custom Instructions, I noticed the quality of Copilot’s ABAP suggestions improved dramatically. It stopped suggesting CREATE OBJECT and started using NEW. It stopped generating SELECT * and started using explicit field lists. These are small things individually, but across a team of developers, they add up to consistently better code.

How My Team Uses This Daily

Here are the five ways GitHub Copilot has become part of our regular workflow:

Agent Mode for direct development — Writing ABAP code directly into the SAP system. This is the use case that saves the most time, especially for generating boilerplate like data declarations, ALV setup, and standard SELECT patterns.
Documentation generation — Pointing Copilot at legacy code and getting clear, readable documentation. For a team maintaining 15+ years of custom ABAP, this alone justified the setup effort.
Code reviews — Using Copilot to review code for quality, performance patterns, and best practices before peer review. It catches things humans miss when they’re deep in the logic.
Unit test generation — Creating ABAP Unit test scaffolds with /tests. We’ve gone from almost zero test coverage on new code to having at least basic test classes for every new method.
Code modernization — Refactoring older ABAP to modern syntax and OO patterns. This is especially useful during S/4HANA preparation work.

Honest Limitations — What I’ve Learned the Hard Way

I want to be transparent about where Copilot falls short for ABAP, because I think setting realistic expectations is important:

The AI models are not fine-tuned for ABAP. ABAP has far less training data on GitHub compared to languages like Python or JavaScript. Copilot sometimes suggests almost-but-not-quite right syntax, especially for SAP-specific APIs and BAPIs.
Module-specific business logic still needs human expertise. Copilot doesn’t know your company’s custom tables, your specific process flows, or your regulatory requirements. Custom Instructions help, but they don’t replace domain knowledge.
Always review the generated code before activating. I’ve caught subtle issues with incorrect table key definitions and missing authority checks. The AI gets you 70–80% there; the last 20–30% is where your experience matters.
This is a developer productivity tool, not an enterprise transformation platform. It complements the specialized tools organizations use for large-scale migration and conversion programs.

Bottom Line

AI-assisted ABAP development works on-premise today. GitHub Copilot in VS Code, especially Agent Mode, has genuinely changed how I work and how my team approaches development tasks. The setup takes an afternoon, and the productivity gains start from day one.

If your organization has GitHub Copilot licenses and an on-premise SAP landscape, I’d encourage you to try this setup.

I’d love to hear from others in the community who are exploring AI tools for ABAP development. What’s working for you? What challenges have you faced? Let’s keep the conversation going.

#SAP #ABAP #GitHubCopilot #VSCode #AgentMode #AI #OnPremise #S4HANA #GenAI

My Learning in Logistics Tracking app - Field Logistics

2026-04-09T11:58:09.026000+02:00

This blog walks through the real-world challenges we faced while building the logistics tracking app. This is an attempt to capture all the pointers and if there's any further points to be added , it will be added later.

The Logistics Tracking (LT) app is SAP's standard tool for monitoring shipments and deliveries in real time. But out of the box, it comes with its own set of challenges — limited flexibility in status updates, gaps in milestone triggering, and difficulty handling complex scenarios like partial deliveries or kit item management — which can quickly become pain points on a project.

The heart of all logistics milestone is via config SPRO->Logistics - General -> Field Logistics->Reporting->Define Logistics Tracking Profile . Once you are here , you can then see the below screenshot having all milestones for a particular Profile id as shown below.

Starting with "Milestone ID" - There are standard milestone ID's and there might be case that a custom milestone id is needed for your specific case. In that case, the problem can occur in the related stand. class of milestone because the constants used by standards might be referring to the standard milestone and you might need to copy the standard class and create your own custom class and change the constant value to your milestone id and use custom class instead of stand. milestone class.

Sequence : All the milestone listed above will be executed in a sequence mentioned in column "Sequence". If a sequence gets the dump then the next sequence will not be executed and you won't see any milestone in LT app . So if there's something which is not triggerring then you make sure to check if there's no dump occurning in system in tcode ST22.

Class : There are standard classes for each standard milestone but you might have to change it to custom class due to any reason specific to your needs . In that case ensure to copy the stand. class and on top of it you add your specific code.

Define Risks : For every milestone there is specific risks associated and corresponding risk class will have the logic to raise risks. Every risk class has a interface and a method via interface IS_RISK_VALID in which we have to write our logic.
- There are 2 importing and 1 changing parameter in every risk class:
  - IV_MILESTONE_ID - Contains the milestone ID
  - IS_MT_RISK - To raise a risk by passing values in fields fldlogsmatltrackgriskid ,fldlogsmatltrckgrisktypeid
  - CT_MT_DTLS - 1 single record everytime to validate via logic to see if it valid to raise risk

How milestones are triggerred:

Milestones are triggerred mostly via events. You can check class CL_FLOG_MANAGEKIT_EVTLISTENER->local definitions->method on_itemchanged . You will find most of the events getting triggerred here but if it's not there then you need to ask the functional team what is the underlying document getting generated at the end . If it's material document or PO document then you go to SWE2 and you need to find the relevant event and see the class in it. Example below:

Common issues faced and solutions:

If milestone is not triggerred -
- Check in SPRO , supply process for which milestone is triggerred, if filters set is only for specific type of supply process then it will not trigger anything for other than that. You can check it by selecing corresponding milestone and then choosing "Define Supply process" as shown below:
- If the above point is correctly maintained and still it's not triggerred then Check table FLOG_MT_DTLS , If there's related entry for the MO and milestone ? If not then put a debugger in Milestone class on user SAP_WFRT and re-execute the scenerio and if debugger is triggerring then check where it's failing in milestone class.

If milstone is triggerred but risk is not raised: Check table FLOG_MT_DTLS, if there's related entry for MO & milestone id and if risk id is blank then go to corresponding risk class and put a debugger point with your user id and then go to SE38 and execute program FLOG_MT_EXECUTE_RISKS and fill up the selection screen with relevant details of your MO and milestone id and execute. The debugger should reach at your risk class and then check the logic where it's failing and accordingly change the logic if needed.

Risk raised is at incorrect row: Risk is getting raised at incorrect row because it's Group id(fldlogsmaterialtrackinggroupid ) is blank. Please check FLOG_MT_DTLS table and field Group id for related risk. Group id field a combination of order no. and row number . If it's blank the risk will be raised on the top row. There is a standard logic for filling this field but if it's failing then you would like to fill it up from your custom risk classes. You will go to table FLOG_SUPLITEM by picking up document id of CT_MT_DTLS and filter on field UUID field of suplitem table and pick up field FLDLOGSSUPLRITMPOITMUNIQUEID and pass it to field fldlogsmaterialtrackinggroupid in risk class.
- If risks have correct group id then check for an entry which is created for milestone and if it does not have group id then we need to copy the stand. milestone class and create a custom milestone class and update the group id with above mentioned logic . With correct group id , risks and milestones will raise at correct row.

Some important CDS views, Tables for the logic
- FLOG_MT_DTLS
- FLOG_SUPLITEM
- C_FldLogsMngKitIssuedItmTP

At the end ,below is the view of each risk and milestone:

If you have any pointers , please let us know . We will include it here.

How SAP Joule is Transforming the Developer Experience

2026-04-09T13:17:12.692000+02:00

In today’s rapidly evolving tech landscape, being an ABAP developer is no longer just about writing code. To stay relevant and competitive, developers must embrace AI-powered tools that enhance productivity, improve code quality, and accelerate delivery.

One such innovation is SAP Joule, an AI assistant designed specifically for SAP developers. Integrated directly into ABAP Development Tools for Eclipse, Joule brings generative AI capabilities into your daily development workflow - without requiring you to switch between tools.

Let’s explore how Joule is transforming ABAP development.

What is SAP Joule for Developers?

SAP Joule is an AI-powered assistant that supports developers throughout the entire development lifecycle - from writing and understanding code to testing, optimization, and even migration.

Think of it as a smart coding partner that understands your context and helps you work faster and smarter.

Key features of Joule for Developers :

1. Chat and Help feature

Joule Chat allows you to interact using simple, natural language.

Ask questions about ABAP concepts
Get instant help from SAP documentation
Retrieve context-aware answers based on your work

You can also use commands like:

/help > for assistance
/explain > to understand code or objects

2. Code Understanding and Assistance

Understanding legacy or complex code is often time-consuming. Joule simplifies this with its Explain feature.

It provides clear explanations for:

ABAP Classes
ABAP Programs
ATC findings
CDS artifacts

Example;

/explain _view_name

Alternatively, Right-click on objects > Joule > Explain

3. Predictive Code Completion

Joule enhances your coding speed with AI-driven suggestions.

Auto-completes code intelligently
Works for classes, interfaces, and programs
Accept suggestions instantly using Tab

You can even write a requirement as a comment, and Joule will generate the code for you as ghost text.

Settings
Go to Window > Preferences > Source Code Editors > Code Completion, then review or update your settings. Make sure the "Trigger predictive code completion" option is enabled.

To display predictive suggestions in a dialog optimized for screen readers, go to Window > Preferences > ABAP Development > Accessibility > Predictive Code Completion.

You can manually trigger suggestions using Alt + J (Windows) or Option + J (Mac). Automatic triggering can also be turned on or off through the search dialog (Ctrl + 3).

To display proposals in a dialog box, enable the "Show Proposals in a dialog box" option.

To receive a suggested solution, write your requirement in plain commented text. The proposed solution will appear as ghost text. Press Tab to accept it.

4. Testing Support

Writing unit tests becomes significantly easier with Joule.

Automatically generates ABAP Unit tests
Supports global and local classes
Generates test classes for CDS entities

This improves:

Test coverage
Code reliability
Developer productivity

To create an ABAP Unit test, right-click on the class and choose Joule > Start Chat for ABAP Unit. The Joule perspective will then present recommended next steps.

In Joule Chat, click "Add Tests to New Test Class".

Joule will suggest ABAP Unit tests, giving you options to Apply, Insert, Copy, Refactor, or Generate Test.

5. Development

Joule can help you build applications faster by generating key components.

RAP Business Logic

Generates determinations and validations
Uses simple descriptions to create logic

Enter the requirement and specify what each method is expected to perform.

The proposal is generated based on your method description, and you can modify it manually if needed.

OData UI Services

Create complete applications from scratch
Automatically generates:
- Service definitions
- CDS views
- Behavior definitions
- Database tables

This significantly reduces manual effort in building applications.

Steps to create an OData UI application:

Right-click on the package and select Generate ABAP Repository Objects.

2. Choose OData UI Service from Scratch.

3. In the Configure Generator window, enter a description of your BO in Joule Chat. For example:

4. Based on your prompt, Joule will suggest the BO entities and fields. If they match your requirements, click Accept. You can also modify them manually or with Joule’s assistance. Once satisfied, click Next.

5. Review the list of artifacts to be generated, then click Next. Select the Transport Request and click Finish.

Consume OData

The Consume capability in Joule lets you generate OData requests and corresponding ABAP code via the OData Client Proxy.
You need a service consumption model with a model class, created in ABAP Development Tools for Eclipse using the service metadata.

Steps:

Open the service consumption model of your OData service.
Start Joule chat:
- Right-click an object > Joule > Consume, or
- Open Joule chat and type /consume.

How It Works

Known OData request: Enter it directly (e.g., GET /Travel?$select=ID) and Joule will generate the corresponding ABAP code.
Need help creating a request: Describe your goal in plain language, and Joule will generate both the OData request and ABAP code.

You can adjust the generated request or code and try again.

6. Migration

Joule migration assistant helps you:

Understand ATC findings
Identify obsolete or incompatible code
Adapt to data model changes

This reduces risk and speeds up migration projects.

SAP Joule is more than just a development tool - it’s a game changer for ABAP developers. By integrating AI into everyday workflows, it helps developers write cleaner code, automate repetitive tasks, and quickly understand complex business objects.

Custom Sorting for Virtual Elements in RAP

2026-04-10T00:06:47.289000+02:00

Introduction

In the ABAP RESTful Application Programming Model (RAP), virtual elements are essential for displaying computed data that doesn't exist in the database—such as deriving a month or year from a timestamp. However, because these elements are calculated at runtime, they lack standard OData capabilities like server-side sorting and filtering. In this article, we will explore how to overcome these limitations by implementing a SADL exit. We’ll walk through how to enable full sorting and calculation capabilities for virtual elements, ensuring a seamless experience for the end user.

What are Virtual Elements in RAP?

In the ABAP RESTful Application Programming Model (RAP), a virtual element is a field defined in a CDS (Core Data Services) projection view that does not have a corresponding column in the underlying database table.

Real-Time Business Scenario: Sales Period Reporting

In many SAP implementations, the business requires reports segmented by Month and Year (e.g., for Monthly Sales Performance). While the underlying database table stores a precise (Created On) date, it does not store the Month or Year as separate columns.

The Problem

If we create a Fiori Elements app and want to show "Sales Month" and "Sales Year" as separate columns:

Simple Virtual Elements can calculate these strings (e.g., "January", "2024").
The Failure: When a user tries to sort the "Sales Month" column, the UI will throw an error or do nothing because the OData service doesn't know how to sort a field that doesn't exist in the database.

The Solution

By using a SADL Exit, we "map" the virtual Month/Year fields back to the physical Sales date field. This allows the database to perform the sort on the actual date, while the user sees the sorted Month or Year on their screen.

Implementation Steps

Step 1: Create a database table

Define the physical storage. This is where the raw data lives before any calculations happen.

@EndUserText.label : 'Sales table'
@AbapCatalog.enhancement.category : #NOT_EXTENSIBLE
@AbapCatalog.tableCategory : #TRANSPARENT
@AbapCatalog.deliveryClass : #A
@AbapCatalog.dataMaintenance : #RESTRICTED
define table zsales_table {

  key client      : abap.clnt not null;
  key sales_uuid  : sysuuid_x16 not null;
  sales_id        : abap.char(10);
  sales_date      : abap.dats;
  @Semantics.amount.currencyCode : 'zsales_table.currency'
  total_amount    : abap.curr(15,2);
  currency        : abap.cuky;
  last_changed_at : timestampl;

}

Step 2: Create a interface view on top of database table.

This layer projects the database fields into a clean, business-oriented structure.

@AbapCatalog.viewEnhancementCategory: [#NONE]
@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Interface view for sales table'
@Metadata.ignorePropagatedAnnotations: true
@ObjectModel.usageType:{
    serviceQuality: #X,
    sizeCategory: #S,
    dataClass: #MIXED
}
define root view entity zi_sales_table
  as select from zsales_table
{
  key sales_uuid      as SalesUuid,
      sales_id        as SalesId,
      sales_date      as SalesDate,
      @Semantics.amount. currencyCode: 'Currency'
      total_amount    as TotalAmount,
      currency        as Currency,
      last_changed_at as LastChangedAt
}

Step 3: Create a Consumption view

This is where the Virtual Elements are defined. We use annotations to link the UI to the specific ABAP logic for calculation and sorting.

@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Projection view for sales table'
@Metadata.ignorePropagatedAnnotations: true

define root view entity ZP_SALESPROJ
  provider contract transactional_query
  as projection on zi_sales_table
{
      .facet: [{ type: #IDENTIFICATION_REFERENCE,
                    position: 10,
                    label: 'Salestable',
                    targetQualifier: 'GENERAL',
                    purpose: #STANDARD }]
                    
      .lineItem: [{ position: 10, label: 'Sales Uuid' }]
  key SalesUuid,

      .lineItem: [{ position: 20, label: 'Sales Id' }]
      .identification: [{ position: 20, label: 'Sales Id' }]
      SalesId,

      .lineItem: [{ position: 30, label: 'Sales order date' }]
      .identification: [{ position: 30, label: 'Sales order date', qualifier: 'GENERAL' }]
      SalesDate,

      .lineItem: [{ position: 40, label: 'Sales order year' }]
      .identification: [{ position: 40, label: 'Sales order year', qualifier: 'GENERAL' }]
      @ObjectModel.virtualElement: true
      @ObjectModel.virtualElementCalculatedBy: 'ABAP:ZCL_SALES_VE_HANDLER'
      @ObjectModel.sort.transformedBy: 'ABAP:ZCL_SALES_VE_HANDLER'
  virtual SalesYear  : abap.char(4),

      .lineItem: [{ position: 50, label: 'Sales order month' }]
      .identification: [{ position: 50, label: 'Sales order month' , qualifier: 'GENERAL' }]
      @ObjectModel.virtualElement: true
      @ObjectModel.virtualElementCalculatedBy: 'ABAP:ZCL_SALES_VE_HANDLER'
      @ObjectModel.sort.transformedBy: 'ABAP:ZCL_SALES_VE_HANDLER'
  virtual SalesMonth : abap.char(2),

      .lineItem: [{ position: 60, label: 'Total amount' }]
      .identification: [{ position: 60, label: 'Total amount' }]
      @Semantics.amount.currencyCode: 'Currency'
      TotalAmount,

      Currency
}

Step 5: The Handler Class Logic

This class implements two critical interfaces: if_sadl_exit_calc_element_read for the calculation and if_sadl_exit_sort_transform to enable sorting.

CLASS zcl_sales_ve_handler DEFINITION
  PUBLIC
  FINAL
  CREATE PUBLIC .

  PUBLIC SECTION.

    INTERFACES if_sadl_exit_calc_element_read.
    INTERFACES if_sadl_exit_sort_transform.
  PROTECTED SECTION.
  PRIVATE SECTION.
ENDCLASS.



CLASS zcl_sales_ve_handler IMPLEMENTATION.
  METHOD if_sadl_exit_calc_element_read~get_calculation_info.
    IF line_exists( it_requested_calc_elements[ table_line = 'SALESYEAR' ] ) OR
           line_exists( it_requested_calc_elements[ table_line = 'SALESMONTH' ] ).
      APPEND 'SALESDATE' TO et_requested_orig_elements.

    ENDIF.
  ENDMETHOD.

  METHOD if_sadl_exit_calc_element_read~calculate.
    DATA lt_data TYPE TABLE OF zp_salesproj WITH DEFAULT KEY.
    lt_data = CORRESPONDING #( it_original_data ).


    LOOP AT lt_data ASSIGNING FIELD-SYMBOL(<fs_row>).
      <fs_row>-SALESYEAR  = <fs_row>-salesdate(4).
      <fs_row>-SALESMONTH = <fs_row>-salesdate+4(2).
    ENDLOOP.
    ct_calculated_data = CORRESPONDING #( lt_data ).
  ENDMETHOD.

  METHOD if_sadl_exit_sort_transform~map_element.
    CASE iv_element.
      WHEN 'SALESYEAR' OR 'SALESMONTH'.
        " Map the UI sort request to the database field 'SALESDATE'
        APPEND VALUE #( name = 'SALESDATE' ) TO et_sort_elements.
    ENDCASE.
  ENDMETHOD.

ENDCLASS.

Result:

With the handler class implemented, the Sales order month and Sales order year ( Virtual Elements) now behaves like a standard database fields.

Downloading Data in Different Formats Using Factory Design Pattern

2026-04-10T07:55:27.623000+02:00

Downloading Data in Different Formats Using Factory Design Pattern

In real projects, users often need the ability to download business data (e.g., sales orders, customer data, or flight bookings) in different formats like TXT, PDF, DOC.

If we try to achieve this in a single report with IF/ELSE or CASE statements, the code quickly becomes messy and hard to maintain. Every new requirement (e.g., CSV, JSON, XML) would require changing the program logic.

This is where the Factory Design Pattern helps.

How the Factory Design Pattern Works Here--

Interface (ZIF_FILE_DOWNLOADER)
1. Defines the common contract: one method DOWNLOAD_FILE.
2. Ensures all file downloaders behave the same way from the outside.

Concrete Classes (TXT, DOC, PDF, XLSX Downloaders)
1. Each class implements the interface and contains logic specific to that file type.
2. Example:
  1. TXT → Uses GUI_DOWNLOAD with ASCII format.
  2. DOC → Uses GUI_DOWNLOAD with linefeeds.

PDF → Uses CL_APOC_PDF_GENERATOR and binary download.

XLSX → Uses CL_FDT_XL_SPREADSHEET to generate Excel.

Factory Class (ZCL_FILE_FACTORY)
1. Acts as a central decision-maker.
2. Based on user selection (TXT, DOC, PDF, XLSX), it instantiates the correct class.
3. The main program never directly knows which class it is using — it only calls the common method.

Report Program (ZDEMO6)
1. Reads user input (p_type).
2. Calls the factory to get the right downloader object.
3. Invokes DOWNLOAD_FILE, which internally runs the format-specific logic.

Flow of Execution--

User selects file type on selection screen.
Report calls factory to get the correct downloader.
Factory returns the right class instance (TXT/PDF/DOC/XLSX).
Report calls DOWNLOAD_FILE method (same for all).
File gets saved on the user’s local system in the chosen format.

Benefits of Using Factory Pattern--

Scalability – Easy to add new file formats without modifying existing code.

Maintainability – Each file logic is isolated in its own class.

Reusability – The same design can be reused in multiple applications (ALV exports, reports, integration).

Clean Code – Avoids long IF/ELSE or CASE blocks.

REPORT zdemo6.

*----------------------------------------------------------------------
* Interface for File Downloaders
*----------------------------------------------------------------------

INTERFACE zif_file_downloader.
  METHODS:
    download_file
      IMPORTING it_data TYPE STANDARD TABLE.
ENDINTERFACE.

CLASS zcl_txt_downloader DEFINITION.
  PUBLIC SECTION.
    INTERFACES zif_file_downloader.
ENDCLASS.


*----------------------------------------------------------------------
* TXT File Downloader Implementation
*----------------------------------------------------------------------


CLASS zcl_txt_downloader IMPLEMENTATION.
  METHOD zif_file_downloader~download_file.
    DATA: lv_filename TYPE string VALUE 'C:\temp\New folder1'.

    " Download using classic FM GUI_DOWNLOAD
    CALL FUNCTION 'GUI_DOWNLOAD'
      EXPORTING
        filename                = lv_filename                     " Name of file
        filetype                = 'ASC'                " File Type (ASC or BIN)
        write_field_separator   = 'X'                " Separate Columns by Tabs in Case of ASCII Download
        confirm_overwrite       = 'X'                " Overwrite File Only After Confirmation
      TABLES
        data_tab                = it_data                     " Transfer table
      EXCEPTIONS
        file_write_error        = 1                    " Cannot write to file
        no_batch                = 2                    " Front-End Function Cannot Be Executed in Background
        gui_refuse_filetransfer = 3                    " Incorrect Front End
        invalid_type            = 4                    " Invalid value for parameter FILETYPE
        no_authority            = 5                    " No Download Authorization
        unknown_error           = 6
        header_not_allowed      = 7                    " Invalid header
        separator_not_allowed   = 8                    " Invalid separator
        filesize_not_allowed    = 9                    " Invalid file size
        header_too_long         = 10                   " The header information is limited to 1023 bytes at present
        dp_error_create         = 11                   " Cannot Create Data Provider
        dp_error_send           = 12                   " Error Sending Data with DataProvider
        dp_error_write          = 13                   " Error Writing Data with DataProvider
        unknown_dp_error        = 14                   " Error when calling data provider
        access_denied           = 15                   " Access to File Denied
        dp_out_of_memory        = 16                   " Not Enough Memory in DataProvider
        disk_full               = 17                   " Storage Medium Full
        dp_timeout              = 18                   " Timeout of DataProvider
        file_not_found          = 19                   " Could not find file
        dataprovider_exception  = 20                   " General Exception Error in Data Provider
        control_flush_error     = 21                   " Error in Control Framework
        OTHERS                  = 22.
    IF sy-subrc IS INITIAL.
      WRITE: / 'TXT file downloaded:', lv_filename.
    ENDIF.
  ENDMETHOD.
ENDCLASS.


*----------------------------------------------------------------------
* PDF File Downloader Implementation
*----------------------------------------------------------------------


CLASS zcl_pdf_downloader DEFINITION.
  PUBLIC SECTION.
    INTERFACES zif_file_downloader.  " Implements interface
ENDCLASS.

CLASS zcl_pdf_downloader IMPLEMENTATION.
  METHOD zif_file_downloader~download_file.

    DATA: lv_filename TYPE string VALUE 'C:\temp\output4.pdf',
          lt_pdf      TYPE STANDARD TABLE OF x255.

    " Generate PDF binary from given data using APOC PDF generator
    DATA(lo_pdf) = NEW cl_apoc_pdf_generator( ).
    lo_pdf->create_pdf(
      EXPORTING
        input             = it_data
      RECEIVING
        pdf_binary_output = DATA(rv_bin)
    ).

    " Convert XSTRING PDF to binary table
    CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
      EXPORTING
        buffer     = rv_bin
      TABLES
        binary_tab = lt_pdf.

    " Save as binary file on local machine
    cl_gui_frontend_services=>gui_download(
      EXPORTING
        filename                  = lv_filename                     " Name of file
        filetype                  = 'BIN'               " File type (ASCII, binary ...)
        confirm_overwrite         = 'X'                " Overwrite File Only After Confirmation
      CHANGING
        data_tab                  = lt_pdf                     " Transfer table
      EXCEPTIONS
        file_write_error          = 1                    " Cannot write to file
        no_batch                  = 2                    " Front-End Function Cannot Be Executed in Backgrnd
        gui_refuse_filetransfer   = 3                    " Incorrect Front End
        invalid_type              = 4                    " Invalid value for parameter FILETYPE
        no_authority              = 5                    " No Download Authorization
        unknown_error             = 6                    " Unknown error
        header_not_allowed        = 7                    " Invalid header
        separator_not_allowed     = 8                    " Invalid separator
        filesize_not_allowed      = 9                    " Invalid file size
        header_too_long           = 10                   " Header information currently restricted to 1023 bytes
        dp_error_create           = 11                   " Cannot create DataProvider
        dp_error_send             = 12                   " Error Sending Data with DataProvider
        dp_error_write            = 13                   " Error Writing Data with DataProvider
        unknown_dp_error          = 14                   " Error when calling data provider
        access_denied             = 15                   " Access to File Denied
        dp_out_of_memory          = 16                   " Not Enough Memory in DataProvider
        disk_full                 = 17                   " Storage Medium full
        dp_timeout                = 18                   " Timeout of DataProvider
        file_not_found            = 19                   " Could not find file
        dataprovider_exception    = 20                   " General Exception Error in DataProvider
        control_flush_error       = 21                   " Error in Control Framework
        not_supported_by_gui      = 22                   " GUI does not support this
        error_no_gui              = 23                   " GUI not available
        OTHERS                    = 24
    ).

    IF sy-subrc IS INITIAL.
      WRITE: / 'PDF file downloaded:', lv_filename.
    ENDIF.

  ENDMETHOD.
ENDCLASS.


*----------------------------------------------------------------------
* DOC File Downloader Implementation
*----------------------------------------------------------------------


CLASS zcl_doc_downloader DEFINITION.
  PUBLIC SECTION.
    INTERFACES zif_file_downloader.
ENDCLASS.

CLASS zcl_doc_downloader IMPLEMENTATION.
  METHOD zif_file_downloader~download_file.
    DATA: lv_filename TYPE string VALUE 'C:\temp\output.doc'.

    " Download using GUI_DOWNLOAD in ASCII mode
    CALL FUNCTION 'GUI_DOWNLOAD'
      EXPORTING
        filename                 = lv_filename                     " Name of file
        filetype                 = 'ASC'                " File Type (ASC or BIN)
        write_lf_after_last_line = abap_true            " Writes LF even after last line
        write_field_separator    = 'X'
        confirm_overwrite        = 'X'
      TABLES
        data_tab                 = it_data                     " Transfer table
      EXCEPTIONS
        file_write_error         = 1                    " Cannot write to file
        no_batch                 = 2                    " Front-End Function Cannot Be Executed in Background
        gui_refuse_filetransfer  = 3                    " Incorrect Front End
        invalid_type             = 4                    " Invalid value for parameter FILETYPE
        no_authority             = 5                    " No Download Authorization
        unknown_error            = 6
        header_not_allowed       = 7                    " Invalid header
        separator_not_allowed    = 8                    " Invalid separator
        filesize_not_allowed     = 9                    " Invalid file size
        header_too_long          = 10                   " The header information is limited to 1023 bytes at present
        dp_error_create          = 11                   " Cannot Create Data Provider
        dp_error_send            = 12                   " Error Sending Data with DataProvider
        dp_error_write           = 13                   " Error Writing Data with DataProvider
        unknown_dp_error         = 14                   " Error when calling data provider
        access_denied            = 15                   " Access to File Denied
        dp_out_of_memory         = 16                   " Not Enough Memory in DataProvider
        disk_full                = 17                   " Storage Medium Full
        dp_timeout               = 18                   " Timeout of DataProvider
        file_not_found           = 19                   " Could not find file
        dataprovider_exception   = 20                   " General Exception Error in Data Provider
        control_flush_error      = 21                   " Error in Control Framework
        OTHERS                   = 22.
    IF sy-subrc IS INITIAL.
      WRITE: / 'DOC file downloaded:', lv_filename.
    ENDIF.
  ENDMETHOD.
ENDCLASS.


*----------------------------------------------------------------------
* Factory Class - Returns Correct Downloader Object
*----------------------------------------------------------------------


CLASS zcl_file_factory DEFINITION.
  PUBLIC SECTION.
    CLASS-METHODS get_downloader
      IMPORTING iv_type              TYPE string
      RETURNING VALUE(ro_downloader) TYPE REF TO zif_file_downloader.
ENDCLASS.

CLASS zcl_file_factory IMPLEMENTATION.
  METHOD get_downloader.
    " Choose correct class based on file type
    CASE iv_type.
      WHEN 'TXT'.
        CREATE OBJECT ro_downloader TYPE zcl_txt_downloader.
      WHEN 'PDF'.
        CREATE OBJECT ro_downloader TYPE zcl_pdf_downloader.
      WHEN 'DOC'.
        CREATE OBJECT ro_downloader TYPE zcl_doc_downloader.
      WHEN OTHERS.
        MESSAGE 'Invalid format!' TYPE 'E'.
    ENDCASE.
  ENDMETHOD.
ENDCLASS.

INITIALIZATION.

*----------------------------------------------------------------------
* Selection Screen
*----------------------------------------------------------------------

  " Choose format dynamically
  PARAMETERS: p_type TYPE string DEFAULT 'TXT'.  " Options: TXT / PDF / DOC

*----------------------------------------------------------------------
* Main Logic
*----------------------------------------------------------------------

START-OF-SELECTION.

  DATA: lo_down  TYPE REF TO zif_file_downloader.

  " Get some sample data from SFLIGHT table
  SELECT FROM sflight
    FIELDS * INTO TABLE (lt_data)
    UP TO 10 ROWS.

  " Use factory to get correct downloader object
  lo_down = zcl_file_factory=>get_downloader( iv_type = p_type ).
  lo_down->download_file( it_data = lt_data ).

For TEXT:-

We can see in our folder.

For WORD--

We can see in our folder--

For PDF:-

We can see in our folder--

Conclusion:-

In this blog, we explored how the Factory Design Pattern can be effectively applied in ABAP to download data in different formats such as TEXT, WORD, PDF without tightly coupling the logic to a specific format. By introducing a factory class that decides which concrete formatter to instantiate, we achieve:

Flexibility – easily add new output formats in the future without modifying existing logic.
Reusability – the same factory and interface can be used across multiple applications.
Maintainability – reduces redundant code and keeps responsibilities clearly separated.
Scalability – supports evolving business needs where multiple consumers may require different file formats.

The Factory Design Pattern not only promotes clean code principles but also aligns with object-oriented best practices in ABAP. By leveraging this approach, developers can build solutions that are extensible, testable, and future-proof.

Thank You.