SAP ABAP

Enabling Selection Mode in Object Oriented ALV ( OO ALV )

2015-03-13T09:24:00.000-07:00

Object Oriented ALV using CL_SALV_TABLE also provide the factility to the programmer to determine whether and in which situation the user can select areas of the ALV output .it is possible to programmatically determine which area needs to be selected and which areas are not required to select. The user can select multiple columns and multiple rows in an Object Oriented ALV .

Similar to all other ALV applications , in order to achive this functionality you need to follow only 2 steps :
Step 1 : Get the object reference of class CL_SALV_SELECTIONS by calling the method get_selections( ) of class CL_SALV_TABLE.
DATA : lo_selections TYPE REF TO cl_salv_selections.
lo_selections = lo_alv->get_selections( ).
STEP 2 : Call the set_selection_mode( ) method of class CL_SALV_SELECTIONS
CALL METHOD lo_selections->set_selection_mode
EXPORTING
value = if_salv_c_selection_mode=>multiple.
Please refer to the following source codes :

REPORT ztestr_alv_9.
TYPES : BEGIN OF gy_bseg,
bukrs TYPE bukrs,
belnr TYPE belnr_d,
gjahr TYPE gjahr,
buzei TYPE buzei,
wrbtr TYPE wrbtr,
END OF gy_bseg.
DATA : gt_bseg TYPE STANDARD TABLE OF gy_bseg INITIAL SIZE 1.
REFRESH : gt_bseg[].
SELECT bukrs belnr gjahr buzei wrbtr
FROM bseg
INTO TABLE gt_bseg
UP TO 10 ROWS.
IF sy-subrc IS INITIAL.
SORT gt_bseg BY bukrs belnr gjahr buzei .
ENDIF.
DATA : lo_alv TYPE REF TO cl_salv_table.
TRY.
CALL METHOD cl_salv_table=>factory
IMPORTING
r_salv_table = lo_alv
CHANGING
t_table = gt_bseg.
CATCH cx_salv_msg .
ENDTRY.
*-- Enabling Selection Mode logic starts
DATA : lo_selections TYPE REF TO cl_salv_selections.
lo_selections = lo_alv->get_selections( ).
CALL METHOD lo_selections->set_selection_mode
EXPORTING
value = if_salv_c_selection_mode=>multiple.
*-- Enabling Selection Mode logic end
lo_alv->display( ).

HOTSPOT/SINGLE CLICK AREA IN ( OO ALV ) IN SAP ABAP .

2015-03-13T09:23:00.000-07:00

In this SAP ABAP tutorial I will show you how to make hospot or single click area in Object Oriented ALV ( OO ALV ) using CL_SALV_TABLE.

To achieve this functionality you need to call the method set_cell_type of class cl_salv_column_table and pass the value as if_salv_c_cell_type=>hotspot . Now clicking on the checkbox will trigger the event LINK_CLICK , so we need to declare and event handler class here lcl_event_handler and declare a method m_link_click to handle the action . The LINK_CLICK event will give us the row and column value of the selected row , so that we can do further process based on the value of that field.
NB : Hotspot coding is similar to the checkbox one of.my previous tutorials except instead of if_salv_c_cell_type=>checkbox_hotspot we need to pass if_salv_c_cell_type=>hotspot .
At the end we need to call the REFRESH( ) method of class CL_SALV_TABLE .
In this SAP ABAP tutorial example we are making the column vbeln values as hotspot so that when the user single click on the value it will lead us to the transaction ‘VL03N’ with the corresponding VBELN value.
Please refer to the following source codes :

REPORT ztestr_alv_10.
TYPES : BEGIN OF gy_vbap,
          vbeln TYPE vbeln_va,
          posnr TYPE posnr_va,
          matnr TYPE matnr,
END OF   gy_vbap.
DATA : gt_vbap TYPE STANDARD TABLE OF gy_vbap INITIAL SIZE 1.
DATA : lo_alv TYPE REF TO cl_salv_table.
REFRESH : gt_vbap[].
*----------------------------------------------------------------------*
*       CLASS lcl_event_handler DEFINITION
*----------------------------------------------------------------------*
*
*----------------------------------------------------------------------*
CLASS lcl_event_handler DEFINITION.
PUBLIC SECTION.
METHODS:
      m_link_click FOR EVENT link_click OF cl_salv_events_table
IMPORTING row column.
ENDCLASS.                    "lcl_event_handler DEFINITION
*----------------------------------------------------------------------*
*       CLASS lcl_event_handler IMPLEMENTATION
*----------------------------------------------------------------------*
*
*----------------------------------------------------------------------*
CLASS lcl_event_handler IMPLEMENTATION.
METHOD m_link_click.
FIELD-SYMBOLS : <lfs_vbap> TYPE gy_vbap.
READ TABLE gt_vbap ASSIGNING <lfs_vbap> INDEX row.
IF sy-subrc IS INITIAL.
SET PARAMETER ID 'VL' FIELD <lfs_vbap>-vbeln.
CALL TRANSACTION 'VL03N'.
ENDIF.
    lo_alv->refresh( ).
ENDMETHOD.                    "m_link_click
"m_link_click
ENDCLASS.                    "lcl_event_handler IMPLEMENTATION
START-OF-SELECTION.
SELECT vbeln posnr matnr
FROM vbap
INTO TABLE gt_vbap
UP TO 10 ROWS.
IF sy-subrc IS INITIAL.
SORT gt_vbap BY vbeln posnr matnr .
ENDIF.
TRY.
CALL METHOD cl_salv_table=>factory
IMPORTING
          r_salv_table = lo_alv
CHANGING
          t_table      = gt_vbap.
CATCH cx_salv_msg .
ENDTRY.
*-- Checkbox logic starts
DATA : lo_columns TYPE REF TO cl_salv_columns_table.
lo_columns = lo_alv->get_columns( ).
lo_columns->set_optimize( 'X' ).
DATA : lo_column TYPE REF TO cl_salv_column_table.
TRY.
      lo_column ?= lo_columns->get_column( 'VBELN' ).
      lo_column->set_cell_type( if_salv_c_cell_type=>hotspot ).
      lo_column->set_output_length( 10 ).
CATCH cx_salv_not_found.
ENDTRY.
DATA: lo_events TYPE REF TO cl_salv_events_table.
lo_events = lo_alv->get_event( ).
DATA: lo_event_handler TYPE REF TO lcl_event_handler.
CREATE OBJECT lo_event_handler.
SET HANDLER lo_event_handler->m_link_click FOR lo_events.
*-- Checkbox logic end
lo_alv->display( ).

Making selection-screen block invisible / visible at runtime in SAP ABAP

2014-10-17T03:45:00.001-07:00

REPORT ztestr_screen_change1.

PARAMETERS : p_matnr TYPE matnr.

PARAMETERS: ck_fl AS CHECKBOX USER-COMMAND chk.

SELECTION-SCREEN : BEGIN OF BLOCK b03 WITH FRAME TITLE text-019.

PARAMETERS : rd_up_a RADIOBUTTON GROUP r2 DEFAULT 'X' MODIF ID abc.
PARAMETERS : p_app_up TYPE dxfields-longpath MODIF ID abc.
PARAMETERS : rd_up_p RADIOBUTTON GROUP r2 MODIF ID abc.
PARAMETERS : p_pre_up TYPE dxfields-longpath MODIF ID abc.

SELECTION-SCREEN : END OF BLOCK b03.

SELECTION-SCREEN : BEGIN OF BLOCK b02 WITH FRAME TITLE text-018.

PARAMETERS : rd_dw_a RADIOBUTTON GROUP r1 DEFAULT 'X' MODIF ID abc.
PARAMETERS : p_app_dl TYPE dxfields-longpath MODIF ID abc.
PARAMETERS : rd_dw_p RADIOBUTTON GROUP r1 MODIF ID abc.
PARAMETERS : p_pre_dl TYPE dxfields-longpath MODIF ID abc.

SELECTION-SCREEN : END OF BLOCK b02.

AT SELECTION-SCREEN OUTPUT.

LOOP AT SCREEN.

IF ck_fl IS INITIAL.

IF screen-group1 = 'ABC'.
screen-active = 0.
ENDIF.

ENDIF.
MODIFY SCREEN.

ENDLOOP.

Making parameters field uneditable / editable at runtime in SAP ABAP

2014-10-17T03:10:00.003-07:00

REPORT ztestr_screen_change.

SELECTION-SCREEN BEGIN OF BLOCK b01 WITH FRAME TITLE text-001.

PARAMETERS: rd_sel1 TYPE c RADIOBUTTON GROUP sel DEFAULT 'X' USER-COMMAND upd.
PARAMETERS: p_gui TYPE rlgrap-filename.
PARAMETERS: rd_sel2 TYPE c RADIOBUTTON GROUP sel,
p_app TYPE rlgrap-filename.

SELECTION-SCREEN END OF BLOCK b01.

AT SELECTION-SCREEN OUTPUT.

LOOP AT SCREEN.

IF rd_sel1 IS NOT INITIAL.

IF screen-name = 'P_APP'.
screen-input = 0.
ELSE.
screen-input = 1.
ENDIF.

ELSE.

IF screen-name = 'P_GUI'.
screen-input = 0.
ELSE.
screen-input = 1.
ENDIF.

ENDIF.

MODIFY SCREEN.

ENDLOOP.

UPLOADING AND DOWNLOADING FILE FROM APPLICATION SERVER IN SAP

2014-10-13T06:12:00.000-07:00

UPLOADING AND DOWNLOADING FILE FROM PRESENTATION SERVER IN SAP

2014-10-13T04:37:00.001-07:00

REPORT ztestr_file_handling.

PARAMETERS : p_path TYPE dxfields-longpath,
p_down TYPE dxfields-longpath.

TYPES : BEGIN OF ty_final,
field1(4) TYPE c,
field2(4) TYPE n,
END OF ty_final.

DATA : git_string TYPE STANDARD TABLE OF string INITIAL SIZE 1,
git_final TYPE STANDARD TABLE OF ty_final INITIAL SIZE 1.

*-- F4 help for the presentation layer
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_path.

CALL FUNCTION 'F4_DXFILENAME_TOPRECURSION'
EXPORTING
i_location_flag = 'P'
* i_server = space
* i_path = lv_i_path
* FILEMASK = '*.*'
* FILEOPERATION = 'R'
IMPORTING
* O_LOCATION_FLAG =
* O_SERVER =
o_path = p_path
* ABEND_FLAG =
EXCEPTIONS
rfc_error = 1
error_with_gui = 2
OTHERS = 3.
IF sy-subrc <> 0.
* Implement suitable error handling here
ENDIF.

*-- F4 help for the presentation layer
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_down.

CALL FUNCTION 'F4_DXFILENAME_TOPRECURSION'
EXPORTING
i_location_flag = 'P'
* i_server = space
* i_path = lv_i_path
* FILEMASK = '*.*'
* FILEOPERATION = 'R'
IMPORTING
* O_LOCATION_FLAG =
* O_SERVER =
o_path = p_down
* ABEND_FLAG =
EXCEPTIONS
rfc_error = 1
error_with_gui = 2
OTHERS = 3.
IF sy-subrc <> 0.
* Implement suitable error handling here
ENDIF.

START-OF-SELECTION.

IF p_path IS NOT INITIAL.
*-- Validate whether path exists or not
PERFORM validate_path.
*-- Upload the file
PERFORM upload_file.

IF git_string[] IS NOT INITIAL.

*-- Populate the internal table for processing
PERFORM populate_itab .

IF git_final[] IS NOT INITIAL.
*-- Process the file
PERFORM process_file.

IF p_down IS NOT INITIAL.

PERFORM validate_path_d.

*-- Download the file
PERFORM download_file.
ENDIF.

ENDIF.

ENDIF.
ENDIF.

*&---------------------------------------------------------------------*
*& Form VALIDATE_PATH
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM validate_path .

DATA: lv_result TYPE char1,
lv_file TYPE string.

lv_file = p_path.

CALL METHOD cl_gui_frontend_services=>file_exist
EXPORTING
file = lv_file
RECEIVING
result = lv_result
EXCEPTIONS
cntl_error = 1
error_no_gui = 2
wrong_parameter = 3
not_supported_by_gui = 4
OTHERS = 5.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF lv_result NE 'X'." if lv_result = 'X' then file exists
MESSAGE 'File does not exist' TYPE 'I'.
EXIT.

ENDIF.

ENDFORM. " VALIDATE_PATH
*&---------------------------------------------------------------------*
*& Form UPLOAD_FILE
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM upload_file .

DATA : lv_filename TYPE string.

lv_filename = p_path.

CALL METHOD cl_gui_frontend_services=>gui_upload
EXPORTING
filename = lv_filename
* filetype = 'ASC'
* has_field_separator = SPACE
* header_length = 0
* read_by_line = 'X'
* dat_mode = SPACE
* codepage = SPACE
* ignore_cerr = ABAP_TRUE
* replacement = '#'
* virus_scan_profile =
* IMPORTING
* filelength =
* header =
CHANGING
data_tab = git_string
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
not_supported_by_gui = 17
error_no_gui = 18
OTHERS = 19
.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

ENDFORM. " UPLOAD_FILE
*&---------------------------------------------------------------------*
*& Form POPULATE_ITAB
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM populate_itab .

DATA : lwa_final TYPE ty_final.
FIELD-SYMBOLS : <fwa_string> TYPE string.

LOOP AT git_string ASSIGNING <fwa_string>.

SPLIT <fwa_string> AT '|' INTO lwa_final-field1
lwa_final-field2.

APPEND lwa_final TO git_final.
CLEAR lwa_final.

ENDLOOP.

ENDFORM. " POPULATE_ITAB
*&---------------------------------------------------------------------*
*& Form PROCESS_FILE
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM process_file .

FIELD-SYMBOLS : <fwa_final> TYPE ty_final.

LOOP AT git_final ASSIGNING <fwa_final>.

<fwa_final>-field2 = <fwa_final>-field2 + 1.
CONDENSE <fwa_final>-field2.

ENDLOOP.

ENDFORM. " PROCESS_FILE
*&---------------------------------------------------------------------*
*& Form DOWNLOAD_FILE
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM download_file .

DATA : lv_filename TYPE string,
lwa_string TYPE string,
lit_string TYPE STANDARD TABLE OF string INITIAL SIZE 1.

FIELD-SYMBOLS : <fwa_final> TYPE ty_final.

IF p_down IS NOT INITIAL.

lv_filename = p_down.

IF git_final[] IS NOT INITIAL.

LOOP AT git_final ASSIGNING <fwa_final>.

CONCATENATE <fwa_final>-field1 <fwa_final>-field2 INTO lwa_string
SEPARATED BY '|'.
APPEND lwa_string TO lit_string.
CLEAR lwa_string.

ENDLOOP.

ENDIF.

CALL METHOD cl_gui_frontend_services=>gui_download
EXPORTING
* bin_filesize =
filename = lv_filename
* filetype = 'ASC'
* append = SPACE
* write_field_separator = SPACE
* header = '00'
* trunc_trailing_blanks = SPACE
* write_lf = 'X'
* col_select = SPACE
* col_select_mask = SPACE
* dat_mode = SPACE
* confirm_overwrite = SPACE
* no_auth_check = SPACE
* codepage = SPACE
* ignore_cerr = ABAP_TRUE
* replacement = '#'
* write_bom = SPACE
* trunc_trailing_blanks_eol = 'X'
* wk1_n_format = SPACE
* wk1_n_size = SPACE
* wk1_t_format = SPACE
* wk1_t_size = SPACE
* show_transfer_status = 'X'
* fieldnames =
* write_lf_after_last_line = 'X'
* virus_scan_profile = '/SCET/GUI_DOWNLOAD'
* IMPORTING
* filelength =
CHANGING
data_tab = lit_string
EXCEPTIONS
file_write_error = 1
no_batch = 2
gui_refuse_filetransfer = 3
invalid_type = 4
no_authority = 5
unknown_error = 6
header_not_allowed = 7
separator_not_allowed = 8
filesize_not_allowed = 9
header_too_long = 10
dp_error_create = 11
dp_error_send = 12
dp_error_write = 13
unknown_dp_error = 14
access_denied = 15
dp_out_of_memory = 16
disk_full = 17
dp_timeout = 18
file_not_found = 19
dataprovider_exception = 20
control_flush_error = 21
not_supported_by_gui = 22
error_no_gui = 23
OTHERS = 24
.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

ENDIF.

ENDFORM. " DOWNLOAD_FILE
*&---------------------------------------------------------------------*
*& Form VALIDATE_PATH_D
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM VALIDATE_PATH_D .

DATA: lv_result TYPE char1,
lv_file TYPE string.

lv_file = p_down.

CALL METHOD cl_gui_frontend_services=>file_exist
EXPORTING
file = lv_file
RECEIVING
result = lv_result
EXCEPTIONS
cntl_error = 1
error_no_gui = 2
wrong_parameter = 3
not_supported_by_gui = 4
OTHERS = 5.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF lv_result NE 'X'." if lv_result = 'X' then file exists
MESSAGE 'File does not exist' TYPE 'I'.
EXIT.

ENDIF.
ENDFORM. " VALIDATE_PATH_D

INPUT file contents

ABCD|1000
EFGH|2000
IJKL|3000
MNOP|4000
QRST|5000

OUTPUT FILE CONTENT :
ABCD|1001
EFGH|2001
IJKL|3001
MNOP|4001
QRST|5001
INPUT :

Important conversion exits in SAP ABAP

2014-09-12T04:54:00.001-07:00

Important conversion exits:

Why conversion exits : Suppose we are loop a table to populate final internal table,

So inorder the read statement to be successful, we need to take the value with zeros (example : 000000000005000700) then only the read statement will be successful.

So , verify the condition and assign the value before using conversion routine.

Now we don’t want the output to be displayed with 000000 in ALV , so to suppress that we use ALV.

1.To convert matnr , input : 000000000005000700

Output : 5000700

      CALL FUNCTION 'CONVERSION_EXIT_MATN1_OUTPUT'
        EXPORTING
          input  = gs_ekpo-matnr
        IMPORTING
          output = gs_ekpo-matnr.

2.To convert lifnr (vendor), input: 0000301593

Output: 301593

      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
        EXPORTING
          input  = gs_ekko-lifnr
        IMPORTING
          output = gs_ekko-lifnr.

COLLECT STATEMENT IN SAP ABAP

2014-08-24T07:17:00.001-07:00

In this SAP ABAP tutorial I will show you the use COLLECT STATEMENT in SAP ABAP

Collect statement is used to summarize the data of the internal table.

SYNTAX : collect <work_area> into <internal_table>.

Some points before using collect statement:

1. Before using collect statement , all the fields of an internal table that are not part of the key of the table should be of numeric type ( f, p, i).

2. When we use collect statement to add a new line or record in an internal table, the SAP system checks whether the line with the same key value already exist in the table. IF no such line exists, then collect will act as a normal append.
However, if the line having the same key value is found in the internal table, the collect statement will adds the content of the numeric field in the work area with the contents of the numeric fields in the existing entry of the table.

Program :

REPORT  ztest_r_05.

TYPES : BEGIN OF ty_shop,
          item TYPE char10,
          quantity TYPE i,
          amount   TYPE i,
        END OF   ty_shop.

DATA : lt_shop TYPE STANDARD TABLE OF ty_shop INITIAL SIZE 1,
       ls_shop TYPE ty_shop,
       lt_shop_summ LIKE lt_shop.

FIELD-SYMBOLS : <fs_shop> TYPE ty_shop.

DO 6 TIMES.

  CASE sy-index.

    WHEN 1.

      ls_shop-item = 'SOAP'.
      ls_shop-quantity = 1.
      ls_shop-amount   = 50.

      APPEND ls_shop TO lt_shop.
      CLEAR ls_shop.

    WHEN 2.
      ls_shop-item = 'SAMPOO'.
      ls_shop-quantity = 1.
      ls_shop-amount   = 120.

      APPEND ls_shop TO lt_shop.
      CLEAR ls_shop.

    WHEN 3.

      ls_shop-item = 'FACE_WASH'.
      ls_shop-quantity = 1.
      ls_shop-amount   = 100.

      APPEND ls_shop TO lt_shop.
      CLEAR ls_shop.

    WHEN 4.
      ls_shop-item = 'SOAP'.
      ls_shop-quantity = 1.
      ls_shop-amount   = 70.

      APPEND ls_shop TO lt_shop.
      CLEAR ls_shop.

    WHEN 5.
      ls_shop-item = 'SAMPOO'.
      ls_shop-quantity = 1.
      ls_shop-amount   = 200.

      APPEND ls_shop TO lt_shop.
      CLEAR ls_shop.

    WHEN 6.

      ls_shop-item = 'FACE_WASH'.
      ls_shop-quantity = 1.
      ls_shop-amount   = 240.

      APPEND ls_shop TO lt_shop.
      CLEAR ls_shop.

    WHEN OTHERS.

  ENDCASE.

ENDDO.

LOOP AT lt_shop ASSIGNING <fs_shop>.

  WRITE : / <fs_shop>-item , <fs_shop>-quantity, <fs_shop>-amount.

ENDLOOP.

ULINE.

WRITE : / 'Summarized records using Collect statement'.

LOOP AT lt_shop INTO ls_shop.

  COLLECT ls_shop INTO lt_shop_summ.

ENDLOOP.

LOOP AT lt_shop_summ INTO ls_shop.

  WRITE : / <fs_shop>-item , <fs_shop>-quantity, <fs_shop>-amount.

ENDLOOP.

USE OF CLEAR , REFRESH, FREE IN SAP ABAP

2014-08-18T01:23:00.000-07:00

In this SAP ABAP tutorial I will show you the use of clear, refresh and free .

Clear:

Syntax : clear <variable_name>.

Use : clear the contents of the variable.

Variables may be internal table , work area , variables declared using elementary data types etc.

E.g.:

Program 1.

DATA : lv_num TYPE i VALUE 1000.

WRITE : / 'Value before clear : ', lv_num.

CLEAR lv_num.

WRITE : / 'Value after clear : ',lv_num.

Program 2.

TYPES : BEGIN OF ty_mara,
          matnr TYPE matnr," Material Number
          mtart TYPE mtart," Material Type
          matkl TYPE matkl," Material Group
        END OF   ty_mara.

DATA : lt_mara TYPE STANDARD TABLE OF ty_mara INITIAL SIZE 1. " Internal table declaration

DATA : lt_mara_header TYPE STANDARD TABLE OF ty_mara WITH HEADER LINE. " Internal table with header line

DATA : ls_mara TYPE ty_mara." Work area declaration

CLEAR : ls_mara , lt_mara[], lt_mara, lt_mara_header[] , lt_mara_header.

REFRESH :

It is used to clear the contents of only internal table. It will only clear the body of the internal table.

TYPES : BEGIN OF ty_mara,
          matnr TYPE matnr," Material Number
          mtart TYPE mtart," Material Type
          matkl TYPE matkl," Material Group
        END OF   ty_mara.
*-- Internal table declaration
DATA : lt_mara TYPE STANDARD TABLE OF ty_mara INITIAL SIZE 1.
*-- Internal table with header line
DATA : lt_mara_header TYPE STANDARD TABLE OF ty_mara WITH HEADER LINE.
*--  Work area declaration
DATA : ls_mara TYPE ty_mara.
*-- Use of refresh
REFRESH : lt_mara[], lt_mara , lt_mara_header[] .

N.B.: Both clear and refresh are used to clear the contents but they never release the memory space.

FREE :

It is used to clear the contents and release the memory of internal table only.

E.g.:

Thanks a lot again friends for reading this tutorial. If you find this is useful and helpful to you, please consider it sharing to your friends using the social buttons below.

Thank you and I invite everyone to connect with me on my facebook page ABAP TOPICS or follow me on goole plus. You can subscribe also to keep updated with latest posts. Enjoy reading this blog .

Please mail all your contributions to roushan.c.kumar@gmail.com . We request you to mention your Name & Organization you are working for. Your posts will be verified and posted in this site with your name.

Internal Table in SAP ABAP

2014-08-18T01:03:00.001-07:00

Internal Table:

In real time different modules e.g. MM , FI , CO , SD etc. hits the database to update the values so that they want to see the values in particular way such as for SD – Sales related details, for FI – Financial related details etc. that may change the database value.

So, instead of hitting the database and changing the values at the database level SAP come up with a concept known as internal table.

Internal table is a variable which is used to extract the records from the database table and process the records. Internal table is like temporary table.

So, now different departments can make a copy of the database table , process them according to their requirements by using internal table without changing the database table.

Properties of internal table:

1. The data that is copied from database table is copied record by record and in the same sequence. So accessing data from internal table will also be done record by record and in the same sequence.

2. Internal table is a collection of group of structures and structure is a group of fields.

3. Internal table stores the records, manipulate and format the records according to user requirement.

4. Memory allocation of internal table is done at runtime as internal tables can store any number of records (may be 1 million or 1 billion).

5. The line type of an internal table can be any ABAP data types – elementary, structured or internal tables.

Steps to declare internal table:

1.Declare the structure of the internal table.

TYPES : BEGIN OF ty_mara_t,
         matnr TYPE mtart,
         maktx TYPE maktx,
         matkl TYPE matkl,
        END OF   ty_mara_t.

DATA : BEGIN OF ls_mara_d,
         matnr TYPE mtart,
         maktx TYPE maktx,
         matkl TYPE matkl,
      END OF    ls_mara_d.

DATA : ls_mara_3 TYPE ty_mara_t.

DATA : ls_mara_4 LIKE ls_mara_d.

Types – it is used to define user defined data types.

Data - it is used to defined user defined data objects.

2.Declare internal table using the structure.

DATA : lt_mara_1 TYPE TABLE OF ty_mara_t,
       lt_mara_2 LIKE TABLE OF ls_mara_d,
       lt_mara_3 LIKE TABLE OF ls_mara_3,
       lt_mara_4 LIKE TABLE OF ls_mara_4.

Thanks a lot again friends for reading this tutorial. If you find this is useful and helpful to you, please consider it sharing to your friends using the social buttons below.

The magic of write statement with edit mask SAP ABAP tutorial

2014-08-13T10:59:00.003-07:00

In this SAP ABAP tutorial I will show you how powerful write statement actually is.Please refer to the following programs.

Program 1:

Real time requirement – The client wants to display the date field in YYMMDD format. Mainly used in smart forms where different company wants to display the smart forms in different date format.

DATA : LV_OUTPUT(50) TYPE C.

WRITE SY-DATUM.

ULINE.

WRITE SY-DATUM TO LV_OUTPUT YYMMDD.

WRITE LV_OUTPUT.

Output : 140813

Program 2:

Real time requirement – The client wants to display the output without leading zeros. Mainly used in smart forms where the client wants a character value to be displayed as ‘123’ instead of ‘0000000123’ or vice versa.

DATA: num(10) TYPE n VALUE '123',

formatted_text(10) TYPE c .

WRITE num TO formatted_text.

WRITE formatted_text.

WRITE num TO formatted_text NO-ZERO.

WRITE formatted_text.

Program 3:

DATA: lv_char(10) TYPE c VALUE '0000000123',

lv_output_c(10) TYPE c,

lv_output_n(10) TYPE n.

WRITE / : 'Original Value : ', lv_char.

WRITE lv_char TO lv_output_c NO-ZERO.

WRITE lv_char TO lv_output_n NO-ZERO.

WRITE lv_char TO lv_char NO-ZERO.

WRITE : / 'Value assigned to type c : ', 40 lv_output_c.

WRITE : / 'Value assigned to type n : ',40 lv_output_n.

WRITE : / 'Value assigned to the same variable : ',40 lv_char.

Program 4:

Real time requirement – The client wants to display the output without any sign neither + nor -. Mainly used in smart forms where the client wants a character value to be displayed as the number itself without any sign.

DATA: lv_var1 TYPE i,

lv_output TYPE c LENGTH 10.

DO 10 TIMES.

lv_var1 = sy-index - 5.

IF lv_var1 >= 0.

WRITE lv_var1 TO lv_output.

WRITE : / lv_output.

ELSE.

WRITE lv_var1 TO lv_output NO-SIGN.

WRITE : / lv_output.

ENDIF.

ENDDO.

Program: 5.

DATA: lv_var1 TYPE i VALUE -10,

lv_output TYPE c LENGTH 10.

WRITE : / lv_var1.

WRITE lv_var1 NO-SIGN.

Thanks a lot again friends for reading this tutorial. If you find this is useful and helpful to you, please consider it sharing to your friends using the social buttons below.

How to find the number of days between two date in SAP ABAP using Function Module

2014-04-28T03:58:00.000-07:00

Following are the codes to find the number of days between two date in SAP ABAP using Function Module
*&---------------------------------------------------------------------*
*& Report  ZTESTR_5
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*

REPORT  ztestr_5.

DATA : lv_days TYPE p.

PARAMETERS : p_date1 TYPE sy-datum,
             p_date2 TYPE sy-datum.

CALL FUNCTION '/SDF/CMO_DATETIME_DIFFERENCE'
EXPORTING
   DATE1                  = p_date1
*   TIME1                  =
   DATE2                  = p_date2
*   TIME2                  =
IMPORTING
   DATEDIFF               = lv_days
*   TIMEDIFF               =
*   EARLIEST               =
EXCEPTIONS
   INVALID_DATETIME       = 1
   OTHERS                 = 2
          .
IF sy-subrc <> 0.
* Implement suitable error handling here
ENDIF.

WRITE : / lv_days.

Similarly , you can also find the time difference by populating the time1 and time2 parameter.
Thanku , please do share and comment.

How to convert floating value ( 4.4000000000000000E+01 ) to char value ( 44 )

2014-03-26T02:00:00.002-07:00

In our development we often came across many situation where we need to convert floating value to char value for example to display the value at the output of ALV .

REPORT  ztestr_2.

DATA : lv_value_from TYPE atflv VALUE '4.4000000000000000E+01',
       lv_output     TYPE cha_class_view-sollwert.

CLEAR : lv_output.

CALL FUNCTION 'QSS0_FLTP_TO_CHAR_CONVERSION'
  EXPORTING
    i_number_of_digits   = 2
    i_fltp_value         = lv_value_from
    i_screen_fieldlength = 16
  IMPORTING
    e_char_field         = lv_output.

WRITE : /  lv_output.

output : 44.00

NB : The exporting parameter ' i_number_of_digits ' determines the number of digits after decimal which are visible.
if you write i_number_of_digits = 1 ,
output will be 44.0

Timestamp in yyyymmddhhmmss format in ABAP

2013-03-17T05:23:00.001-07:00

REPORT ZTESTR_TS.

DATA : lv TYPE string.

WRITE : / sy-datum , sy-timlo , sy-uzeit.

CONCATENATE sy-datum+0(4) sy-datum+4(2) sy-datum+6(2) sy-timlo+0(2) sy-timlo+2(2) sy-timlo+4(2) INTO lv.

WRITE : / lv.

Validating Select-options in SAP ABAP

2013-03-16T09:14:00.000-07:00

Generally , while validating select-options we write the code as below.

*It is only partially correct , refer the codes below
select matnr from mara into lv_mara
where matnr in so_matnr.
if sy-subrc is not initial.
"error message
endif.

but above code , is wrong . Now suppose the user enters two material number , 0000000002 and
0000000045 where the 2nd one does not exist in the system .But sy-subrc will become 0 , and the error message will not be executed .
So , we have to consider the following codes that will help !!!

REPORT ztestr_14.

TABLES : mara.

SELECT-OPTIONS : so_matnr FOR mara-matnr.

TYPES : BEGIN OF ty_matnr,
          matnr TYPE matnr,
        END OF   ty_matnr.

DATA : li_matnr TYPE STANDARD TABLE OF ty_matnr.
FIELD-SYMBOLS : <fls_matnr> TYPE ty_matnr.

IF so_matnr IS NOT INITIAL.

SELECT matnr FROM mara
               INTO TABLE li_matnr
               WHERE matnr IN so_matnr.

IF sy-subrc IS INITIAL.

    SORT li_matnr ASCENDING BY matnr.

    LOOP AT so_matnr.

      READ TABLE li_matnr ASSIGNING <fls_matnr>
                          WITH KEY matnr = so_matnr-low
                          BINARY SEARCH.

      IF sy-subrc IS NOT INITIAL.

        PERFORM error_handling USING text-e01 so_matnr-low.

      ENDIF.

    ENDLOOP.

    IF so_matnr-high IS NOT INITIAL.

      READ TABLE li_matnr ASSIGNING <fls_matnr>
                          WITH KEY matnr = so_matnr-high
                          BINARY SEARCH.

      IF sy-subrc IS NOT INITIAL.

        PERFORM error_handling USING text-e01 so_matnr-high.

      ENDIF.

    ENDIF.

ELSE.

     PERFORM error_handling USING text-e01 so_matnr-low.

ENDIF.

ENDIF.

form ERROR_HANDLING using    p_text_e01 TYPE string
                              value type any.

      DATA : lv_message TYPE string.
       CONSTANTS : lc_plach1 TYPE char2 VALUE '&1'.
        CLEAR : lv_message.
        lv_message = p_text_e01." where text-e01 = Material number &1 does not exist
        REPLACE lc_plach1 WITH value
        INTO lv_message.
        MESSAGE e000(zh) WITH lv_message.

endform.                    " ERROR_HANDLING

Validating Local/Presentation path exist or not in SAP ABAP

2013-03-03T09:29:00.001-08:00

Following is the program that checks whether the local path entered is valid or not.

TYPE-POOLS : abap.

Paramaters : p_zloc type rlgrap-filename.

    DATA : lv_dir TYPE string,
           lv_bol TYPE abap_bool,
           lv_string TYPE rlgrap-filename.
    DATA lv_w_string TYPE string.
    DATA : lv_i TYPE i,
                lv_j TYPE i.

    lv_string   = p_zloc.
    lv_w_string = lv_string.

    DO.
      SEARCH lv_w_string FOR '\'.
      IF sy-subrc EQ 0.
        lv_i = sy-fdpos + 1.
        lv_j = lv_i + lv_j.
        lv_w_string = lv_w_string+lv_i.
      ELSE.
        EXIT.
      ENDIF.
    ENDDO.

    lv_dir = lv_string+0(lv_j).

    CALL METHOD cl_gui_frontend_services=>directory_exist
      EXPORTING
        directory            = lv_dir
      RECEIVING
        result               = lv_bol
      EXCEPTIONS
        cntl_error           = 1
        error_no_gui         = 2
        wrong_parameter      = 3
        not_supported_by_gui = 4
        OTHERS               = 5.
    IF lv_bol NE 'X'." if lv_bol = 'X' the path is a vlid path
      MESSAGE e000(zh) WITH text-008.
    ENDIF.

How to separate path name and file name in abap

2013-03-03T09:16:00.001-08:00

parameters : p_locpth type RGGRAP-FILENAME. " Parameter where user input the full path

    DATA : lv_w_string TYPE string,
                 lv_string TYPE rlgrap-filename.

    DATA : lv_i TYPE i,
                 lv_j TYPE i.

    lv_string   = p_locpth.
    lv_w_string = lv_string.

    DO.
      SEARCH lv_w_string FOR '\'.
      IF sy-subrc EQ 0.
        lv_i = sy-fdpos + 1. " sy-fdpos gives the location of the character you are searching and it *starts with 0
        lv_j = lv_i + lv_j.
        lv_w_string = lv_w_string+lv_i.
      ELSE.
        EXIT.
      ENDIF.
    ENDDO.

    lv_dir = lv_string+0(lv_j).

write : / lv_dir.

SAP for a layman...

2012-09-26T10:56:00.001-07:00

Whenever you hear the word SAP from a layman , in almost all the cases they pronounce it wrong as "SAP" (like the sap of the tree) , it happens with me also when i first speak this word . Actually the correct way is "ess-ay-pea" pronounced as S (separate) , A (separate) and P (separate) not in continuous 'SAP'.

SAP stands for Systems Applications and Products in Data Processing is a software that integrates all the business functional areas of a company in a synchronous way .

The business fnctional areas or functional modules or application areas represents various modules on the basis of the business areas such as

1.SD - Sales and Distribution.

2.PP - Production Planning.

3.WM - Warehouse Management

4.MM - Material Management.

5.FI - Financial Accounting.

6.PM - Plant Maintenance etc

Let me explain the above definition in detail , Tata Motors producing variety of cars having headquaters in different different locations of India say for example Hyderabad , Delhi , Mumbai and Bangalore . Now at the time of festivals suddenly the selling of cars increases , so the sales department ,SD(Sales and Distribution) has to inform the PP(Production Planning) to give more cars to the Warehouse Management , the Production Planning in turn send report to MM(Material Management), which in turn send report to different different vendors to get the different parts of cars such as tyres , steels , glass etc and finally report goes to FI (Financial Accounting) and the final report of the entire process goes to the CEO . The entire process have to be done at the same time to be more productive . Now suppose the SD module is maintained differently from other modules , so the revenue generated from sales and more requirement of product has to be updated manually into other modules , which is not at all synchronous and more prone to errors.

Thus to solve this problem we use SAP because it has very high level of integration between various functional modules which ensures proper synchronization and consistency with zero error . SAP integrates all its functional modules because of its centralized database for all the different modules of business.

Now upto this point you are clear about SAP , now know some of the facts about SAP

SAP came from the German word "Systeme, Anwendungen, und Produkte in der Datenverarbeitung".

It is developed by five IBM employees Hans-Werner Hector , Hasso Plattner , Dietmar Hopp , Klaus Tschira and Claus Wellenreuther in 1972 .

Object Oriented Programming

2012-08-25T07:41:00.000-07:00

Object Oriented Programming as the name suggest is a programming technique which revolves around objects . In simple terms it is the process by which the real world problems are converted into software solutions . Let us take an example , tata safari is the real world object of class car , this object has two characteristics i.e it has a state(attribute or data) and behavior (methods or functions).The state includes engaged gear , current speed etc and the behavior includes accelerations , changing gear , applying brakes etc . The software solution of the above will be attributes (data or state) and behavior (methods or functions) .
Attributes includes :   data : engaged_gear  type c,    (In ABAP)
                                            current_speed type n.
                                   or
                                   int current_speed; (In Java)
Behaviors includes : method apply_brakes()
                                    {
                                        current_speed = current_speed - 2.
                                     }
                                    method accelerations() etc.
Following are the features of Object Oriented Programming

1.Class - Class is a pattern or style based on which all the objects in that class is created . Class is a collection of attributes and behaviors of similar types of objects.
But a class does not have its physical existence it is the objects present in a class that have physical existence like the folders in our computer does not have physical existence rather it is the files that present inside the folder has physical existence i.e occupies some memory .

Attributes : Attributes contains the data that can be stored in the objects of a class.
Behaviors : Behaviors refers to the functionality of the object.

2.Object - Object is the runtime instance of a class which has physical existence and having its own attributes and behaviors . We can create any number of objects based on a single class and the process of object creation is known as instantiation.

Example - Human is a class because we can not touch human i.e it does not have physical existence but we can touch the hands , nose , hair which are the objects of human class .
Car is a class because we can not touch car but we can touch indica car , safari car etc which are objects of class car.

3.Abstraction - Abstraction is a feature through which the essential parts of the object is represented hiding the background details.

Data is abstracted by high level language constructs such as numbers ,letters , high level data concepts etc.
Functionality is abstracted by presenting interfaces that hide complex logics such as methods or functions.

Example - When we are driving car we simply apply the brakes without knowing what is happening in the background that stop the car i.e unnecessary details are abstracted.

4.Encapsulation - Encapsulation is the packaging of attributes(data member) and behaviors(member functions) into one reusable module where user can only call certain functions or methods but cannot access the data directly.This feature enables the class to hide the implementation details of the class.
It helps in data data hiding which leads to data security(making attributes and behaviors private) .

Example - Think of the capsules that doctor recomend you , which is nothing but the packaging of different benefitial drugs , leaves etc into one reusable module.

5.Polymorphism - The term is derived from greek words poly means many and morphos means forms . So polymorphism means method having same name have different forms i.e objects from different classes react differently to the same method calls.

Example - Our behaviour is different when we are with our parents , different when we are with our friends , teachers etc . Similarly same method behaves differently based on which class object call it.

6.Inheritance - Inheritance is the feature through which the attributes and behaviors of one object can be reused in other which leads to reusability and reusability leads to less amount of coding.

7.Exception Handling - Exception handling is a feature through which user can handle the abnormal behavior (number divided by 0 is an example of abnormal behaviour) of the programme . Whenever an exception , control navigates to the exception block handles the exception and exit out of the programme normally.

If you like this tutorial , please like and comment...