report – SAP EWM Help

Types of Internal Tables in ABAP

DPM125 — Sun, 24 Aug 2025 11:22:22 +0000

SAP defines three main types of internal tables based on their structure and access method:

1. Standard Table (`STANDARD TABLE`)

Default type if nothing is specified.
Entries are stored unsorted (in the order you append them).
Index-based access (like arrays).
Duplicate entries allowed.
Access time:
- By index → very fast (O(1))
- By key → linear search (O(n))

Use Case: Small-to-medium datasets where duplicates are needed, sequential processing.

DATA: it_mara TYPE STANDARD TABLE OF mara WITH DEFAULT KEY,
wa_mara TYPE mara.

SELECT * FROM mara INTO TABLE it_mara UP TO 10 ROWS.
READ TABLE it_mara INTO wa_mara INDEX 5. ” Access by index

2. Sorted Table (`SORTED TABLE`)

Entries are always stored in a sorted order (by key).
No need to SORT explicitly.
Unique or non-unique keys possible (depending on definition).
Binary search used internally for key access.
Access time:
- By key → fast (O(log n))
- By index → slower than standard

Use Case: When you frequently read data by key and want it sorted automatically.

DATA: it_mara_sorted TYPE SORTED TABLE OF mara
WITH UNIQUE KEY matnr.

SELECT * FROM mara INTO TABLE it_mara_sorted UP TO 10 ROWS.
READ TABLE it_mara_sorted WITH TABLE KEY matnr = ‘MAT001’
INTO DATA(wa_mara).

3. Hashed Table (`HASHED TABLE`)

Entries are stored in hash algorithm format (like a dictionary).
Only unique keys allowed.
No index access → can only be accessed via key.
Access time: By key → constant (O(1)) on average.
Best for large datasets when you always access by key.

Use Case: Fast key-based lookups, like material master lookup by MATNR.

DATA: it_mara_hashed TYPE HASHED TABLE OF mara
WITH UNIQUE KEY matnr.

SELECT * FROM mara INTO TABLE it_mara_hashed UP TO 1000 ROWS.
READ TABLE it_mara_hashed WITH TABLE KEY matnr = ‘MAT001’
INTO DATA(wa_mara).

Summary :

Type	Sorted?	Duplicates?	Access by Index	Access by Key	Performance
Standard	No	Yes	Yes	Linear Search	Best for small, sequential
Sorted	Yes	Optional	Yes	Binary Search	Best for ordered + key access
Hashed	N/A	No	No	Hash Search	Best for large, key-only access

How to remove the leading zeros from the output of program in SAP ABAP ?

DPM125 — Sat, 23 Aug 2025 21:11:30 +0000

Common Methods to Remove Leading Zeros in ABAP

WRITE statement with `NO-ZERO`

When outputting with WRITE, you can suppress leading zeros like this:

code:

DATA: lv_num TYPE n LENGTH 10 VALUE ‘0000123456’.

WRITE lv_num NO-ZERO. ” Output: 123456

SHIFT statement

You can shift the contents to the left to remove zeros:

code:

DATA: lv_num TYPE n LENGTH 10 VALUE ‘0000123456’.

SHIFT lv_num LEFT DELETING LEADING ‘0’.
WRITE lv_num. ” Output: 123456

CONDENSE with `NO-GAPS`

Works if the field is CHAR/NUMC:

DATA: lv_char TYPE char10 VALUE ‘0000123456’.

CONDENSE lv_char NO-GAPS. ” removes spaces
SHIFT lv_char LEFT DELETING LEADING ‘0’.
WRITE lv_char. ” Output: 123456

Conversion Exit (for SAP standard fields)

Some SAP fields (like Material Number MATNR) have conversion exits to display without leading zeros.

DATA: lv_matnr TYPE matnr VALUE ‘000000000000123456’.

CALL FUNCTION ‘CONVERSION_EXIT_ALPHA_OUTPUT’
EXPORTING
input = lv_matnr
IMPORTING
output = lv_matnr.

WRITE lv_matnr. ” Output: 123456

Best practice:

Use CONVERSION_EXIT_ALPHA_OUTPUT if dealing with SAP database fields like MATNR, KUNNR, LIFNR.
Use SHIFT ... DELETING LEADING '0' or WRITE ... NO-ZERO for simple variables.

ABAP Selection-Screen Elements

DPM125 — Sat, 23 Aug 2025 20:26:34 +0000

This report is a sample program that demonstrates how a user can enter and organize different kinds of input on an SAP screen. It includes simple fields like dates, codes, and names where you can type in values. It also provides choices through radio buttons and checkboxes, allowing users to pick options easily. To keep things clear, inputs are grouped into sections with titles and labels. Visual elements such as lines, spacing, and comments make the screen more structured and easier to read. A button is available for triggering specific actions directly from the screen. The program also uses tabs to separate information into different pages, making it less cluttered. Overall, this example shows how SAP screens can be designed to be interactive, organized, and user-friendly.

*&---------------------------------------------------------------------*
*& Report  ZTEST_PROGRAM_2
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*

REPORT ztest_program_2.

*---------------------------------------------------------------------*
* SELECTION-SCREEN DECLARATION
*---------------------------------------------------------------------*
tables: mara.

*--- Simple parameters
PARAMETERS: p_matnr TYPE mara-matnr OBLIGATORY,   " Material number
            p_mtart TYPE mara-mtart,              " Material type
            p_date  TYPE sy-datum.                " Date input

*--- Select-options for ranges
SELECT-OPTIONS: s_matkl FOR mara-matkl,           " Material group range
                s_ersda FOR mara-ersda.           " Creation date range

*--- Radio buttons (same group -> only one active)
PARAMETERS: r_raw   RADIOBUTTON GROUP g1 DEFAULT 'X', " Raw materials
            r_finsi RADIOBUTTON GROUP g1.            " Finished goods

*--- Checkbox
PARAMETERS: p_test AS CHECKBOX DEFAULT 'X'.

*--- Blocks with title
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETERS: p_user TYPE sy-uname DEFAULT sy-uname.
SELECTION-SCREEN END OF BLOCK b1.

*--- Inline elements
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS: p_len TYPE i DEFAULT 10.
SELECTION-SCREEN COMMENT 25(20) text-002 FOR FIELD p_len.
SELECTION-SCREEN END OF LINE.

*--- Pushbutton
SELECTION-SCREEN PUSHBUTTON 10(20) but1 USER-COMMAND pb1.

*---------------------------------------------------------------------*
* TEXT ELEMENTS
*---------------------------------------------------------------------*
* text-001 = "User Settings"
* text-002 = "Length of Value"
* but1     = "Execute Action"


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

  WRITE: / 'Material Number:', p_matnr,
         / 'Material Type  :', p_mtart,
         / 'Date Entered   :', p_date.

  WRITE: / 'Material Group :', s_matkl,
         / 'Creation Date  :', s_ersda.

  IF r_raw = 'X'.
    WRITE: / 'Material Category: Raw Material'.
  ELSE.
    WRITE: / 'Material Category: Finished Goods'.
  ENDIF.

  IF p_test = 'X'.
    WRITE: / 'Test Mode Active'.
  ENDIF.

  WRITE: / 'User:', p_user.
  WRITE: / 'Length:', p_len.

  " Fetch and display matching materials from MARA
  DATA: lt_mara TYPE TABLE OF mara,
        ls_mara TYPE mara.

  SELECT * FROM mara
    INTO TABLE lt_mara
        UP TO 20 ROWS
    WHERE matnr = p_matnr
      AND mtart = p_mtart
      AND matkl IN s_matkl
      AND ersda IN s_ersda.

  IF sy-subrc = 0.
    WRITE: / '--- Materials Found ---'.
    LOOP AT lt_mara INTO ls_mara.
      WRITE: / ls_mara-matnr, ls_mara-mtart, ls_mara-matkl, ls_mara-ersda.
    ENDLOOP.
  ELSE.
    WRITE: / 'No materials found for given criteria.'.
  ENDIF.


*---------------------------------------------------------------------*
* AT SELECTION-SCREEN EVENT (for pushbutton handling)
*---------------------------------------------------------------------*
AT SELECTION-SCREEN.
  CASE sy-ucomm.
    WHEN 'PB1'.
      MESSAGE 'Pushbutton was pressed!' TYPE 'I'.
  ENDCASE.

Modular Screen Features

DPM125 — Thu, 07 Aug 2025 07:28:22 +0000

1. SELECTION-SCREEN BEGIN OF SCREEN

As already explained, this defines a custom screen (like a subscreen or popup), which you can call dynamically using CALL SELECTION-SCREEN.

SELECTION-SCREEN BEGIN OF SCREEN  [AS SUBSCREEN|AS WINDOW] [TITLE ].
... fields ...
SELECTION-SCREEN END OF SCREEN .

2. SELECTION-SCREEN BEGIN OF BLOCK
Used to group parameters and fields into logical blocks, which can have their own frame and titles.

SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETERS: p_carrid TYPE s_carr_id,
p_connid TYPE s_conn_id.
SELECTION-SCREEN END OF BLOCK b1.

4. SELECTION-SCREEN BEGIN OF LINE
Used to arrange fields horizontally on the selection screen (instead of vertical default layout).

SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(10) text-002 FOR FIELD p_flag.
PARAMETERS: p_flag AS CHECKBOX.
SELECTION-SCREEN END OF LINE.

4. SELECTION-SCREEN COMMENT
Displays a label or text on the selection screen.

SELECTION-SCREEN COMMENT /1(30) text-003.

5. SELECTION-SCREEN TAB and SELECTION-SCREEN BEGIN OF TABBED BLOCK
Used to create tabbed selection screens, where each tab holds a subscreen.

SELECTION-SCREEN BEGIN OF TABBED BLOCK mytab FOR 3 LINES.
SELECTION-SCREEN TAB (20) tab1 USER-COMMAND tab1 SCREEN 101.
SELECTION-SCREEN TAB (20) tab2 USER-COMMAND tab2 SCREEN 102.
SELECTION-SCREEN END OF BLOCK mytab.

SELECTION-SCREEN BEGIN OF SCREEN 101 AS SUBSCREEN.
PARAMETERS: p_name TYPE name1.
SELECTION-SCREEN END OF SCREEN 101.

SELECTION-SCREEN BEGIN OF SCREEN 102 AS SUBSCREEN.
PARAMETERS: p_age TYPE i.
SELECTION-SCREEN END OF SCREEN 102.

Classical Report Events in SAP ABAP

DPM125 — Sun, 03 Aug 2025 06:54:31 +0000

Classical Reports in ABAP use a sequence of predefined events during program execution. These events let you structure your code based on data fetching, formatting, and output rendering.

Event	Description
`LOAD-OF-PROGRAM`	Triggered once when the program is loaded into memory (before anything else)
`INITIALIZATION`	Called before the selection screen is displayed
`AT SELECTION-SCREEN`	Called after user input is entered on the selection screen
`START-OF-SELECTION`	Main logic block, starts after selection screen input
`TOP-OF-PAGE`	Used to print page headers
`END-OF-PAGE`	Used to print page footers
`END-OF-SELECTION`	Called after START-OF-SELECTION, typically for final output
`AT LINE-SELECTION`	Triggered by user double-click (F2) on output
`AT USER-COMMAND`	Triggered when a custom function key is pressed

REPORT zrep_lclclass.

TABLES: mara.
data: lt_mara type table of mara.

" Selection Screen
SELECT-OPTIONS: s_matnr FOR mara-matnr.

" LOAD-OF-PROGRAM

LOAD-OF-PROGRAM.
  WRITE: / '>> Program loaded into memory.'.

  " INITIALIZATION

INITIALIZATION.
  s_matnr-sign   = 'I'.
  s_matnr-option = 'EQ'.
  s_matnr-low    = '1'.
  s_matnr-high = '9999'.
  APPEND s_matnr.

  " AT SELECTION-SCREEN

AT SELECTION-SCREEN.
  IF s_matnr[] IS INITIAL.
    MESSAGE 'Please enter a carrier ID' TYPE 'E'.
  ENDIF.

  " START-OF-SELECTION

START-OF-SELECTION.
  WRITE: / '>> Start of selection'.
  SELECT * FROM mara INTO TABLE lt_mara
  WHERE matnr IN s_matnr.

  IF sy-subrc = 0.
    LOOP AT lt_mara INTO DATA(ls_matnr).
      WRITE: / ls_matnr-matnr,
               ls_matnr-ernam,
               ls_matnr-ersda.
    ENDLOOP.
  ELSE.
    WRITE: / 'No data found'.
  ENDIF.

  " END-OF-SELECTION

END-OF-SELECTION.
  WRITE: / '>> End of selection processing.'.

  " TOP-OF-PAGE

TOP-OF-PAGE.
  WRITE: / 'Material Master Report'.
  WRITE: / '------------------------'.

  " AT LINE-SELECTION

AT LINE-SELECTION.
  MESSAGE 'You clicked a line!' TYPE 'I'.

Output:
Execute

FM for Help Request

DPM125 — Wed, 30 Jul 2025 12:29:27 +0000

Help Request (triggered by F1 key) provides field-level documentation to help users understand the purpose or use of a field.

Types of Help Request:

Automatic Help (F1) from Data Element
- Comes from documentation maintained in the data element.
- No coding needed — just maintain the documentation in SE11.
Custom Help Request (Manual)
- In module pool programs, you can write custom F1 help logic using PROCESS ON HELP-REQUEST.

Code :

*&---------------------------------------------------------------------*
*&---------------------------------------------------------------------*
*& Report ZPRG_TEST
*&---------------------------------------------------------------------*

REPORT zprg_test_ecc.

DATA :  it_help TYPE STANDARD TABLE OF helpval WITH HEADER LINE.

PARAMETERS : s_id TYPE ZAR_STUDENT_ID.

AT SELECTION-SCREEN ON s_id.
  SELECT SINGLE student_id FROM zar_student_data INTO @DATA(id).
  IF id IS INITIAL.
    MESSAGE 'Student ID not found' TYPE 'E'.
  ENDIF.

AT SELECTION-SCREEN ON HELP-REQUEST FOR s_id.
  CLEAR it_help[].

  it_help-tabname = 'bkid'.
  it_help-fieldname = 'Student_ID'.
  it_help-keyword = 'Description'.
  it_help-length = 150.
  it_help-value = 'Enter a student id or refer table ZAR_STUDENT_DATA to find student id'.

  APPEND it_help.

  CALL FUNCTION 'HELP_GET_VALUES'
    EXPORTING
      popup_title = 'About s-id'
    TABLES
      fields      = it_help
    EXCEPTIONS
      no_entries  = 1
      OTHERS      = 2.

  IF sy-subrc <> 0.
* Implement suitable error handling here
  ENDIF.

START-OF-SELECTION.

  SELECT * FROM zar_student_data INTO TABLE @DATA(lc_it_zlib) WHERE STUDENT_ID = @s_id.

  LOOP AT lc_it_zlib INTO DATA(wa_zlib).
    WRITE (22) : wa_zlib-student_id, wa_zlib-student_fname.
    SKIP.
  ENDLOOP.

Output :
Execute and Press F1.