CALL_SCREEN_170 SAP Function module - calling screen 0170

CALL_SCREEN_170 is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CALL_SCREEN_170 into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: LMOB
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM CALL_SCREEN_170 - CALL SCREEN 170

CALL FUNCTION 'CALL_SCREEN_170' "calling screen 0170
  EXPORTING
    i_nltyp =                   " ltap-nltyp    Destination storage type
    i_nlber =                   " ltap-nlber    Destination storage section
    i_nlpla =                   " ltap-nlpla    Destination storage bin
    i_bwlvs =                   " ltak-bwlvs    Movement type
  IMPORTING
    e_nltyp =                   " ltap-nltyp    Destination storage type
    e_nlber =                   " ltap-nlber    Destination storage section
    e_nlpla =                   " ltap-nlpla    Destination storage bin
    e_bwlvs =                   " ltak-bwlvs    Movement type
    e_letyp =                   " lein-letyp    Handling unit type
    e_clenum =                  " rlmob-clenum  HU verification field
    e_lenum =                   " lein-lenum    HU number
    e_text =                    " leinm-text    Text
    e_screen_fcode =            " sy-ucomm      function key pressed by user
  TABLES
    x_sus =                     " leinm         HU data
  EXCEPTIONS
    FAIL_IN_PHYSICAL_SCREEN_NUMBER = 1  "
    .  "  CALL_SCREEN_170

ABAP code example for Function Module CALL_SCREEN_170

The ABAP code below is a full code listing to execute function module CALL_SCREEN_170 including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_e_nltyp  
 
 TYPE LTAP-NLTYP
,
ld_e_nlber  
 
 TYPE LTAP-NLBER
,
ld_e_nlpla  
 
 TYPE LTAP-NLPLA
,
ld_e_bwlvs  
 
 TYPE LTAK-BWLVS
,
ld_e_letyp  
 
 TYPE LEIN-LETYP
,
ld_e_clenum  
 
 TYPE RLMOB-CLENUM
,
ld_e_lenum  
 
 TYPE LEIN-LENUM
,
ld_e_text  
 
 TYPE LEINM-TEXT
,
ld_e_screen_fcode  
 
 TYPE SY-UCOMM
,
it_x_sus  
 
 TYPE STANDARD TABLE OF LEINM,"TABLES PARAM
wa_x_sus
 
 LIKE LINE OF it_x_sus
.

 

SELECT single NLTYP 
  FROM LTAP 
  INTO @DATA(ld_i_nltyp).

 

SELECT single NLBER 
  FROM LTAP 
  INTO @DATA(ld_i_nlber).

 

SELECT single NLPLA 
  FROM LTAP 
  INTO @DATA(ld_i_nlpla).

 

SELECT single BWLVS 
  FROM LTAK 
  INTO @DATA(ld_i_bwlvs).

 

"populate fields of struture and append to itab
append wa_x_sus to it_x_sus.
.

CALL FUNCTION 'CALL_SCREEN_170'
  EXPORTING
    i_nltyp =                    ld_i_nltyp
    i_nlber =                    ld_i_nlber
    i_nlpla =                    ld_i_nlpla
    i_bwlvs =                    ld_i_bwlvs
  IMPORTING
    e_nltyp =                    ld_e_nltyp
    e_nlber =                    ld_e_nlber
    e_nlpla =                    ld_e_nlpla
    e_bwlvs =                    ld_e_bwlvs
    e_letyp =                    ld_e_letyp
    e_clenum =                   ld_e_clenum
    e_lenum =                    ld_e_lenum
    e_text =                     ld_e_text
    e_screen_fcode =             ld_e_screen_fcode
  TABLES
    x_sus =                      it_x_sus
  EXCEPTIONS
    FAIL_IN_PHYSICAL_SCREEN_NUMBER =    1
    .  "  CALL_SCREEN_170

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_nltyp
 
 TYPE LTAP-NLTYP ,
ld_i_nltyp
 
 TYPE LTAP-NLTYP ,
it_x_sus
 
 TYPE STANDARD TABLE OF LEINM ,
wa_x_sus
 
 LIKE LINE OF it_x_sus,
ld_e_nlber
 
 TYPE LTAP-NLBER ,
ld_i_nlber
 
 TYPE LTAP-NLBER ,
ld_e_nlpla
 
 TYPE LTAP-NLPLA ,
ld_i_nlpla
 
 TYPE LTAP-NLPLA ,
ld_e_bwlvs
 
 TYPE LTAK-BWLVS ,
ld_i_bwlvs
 
 TYPE LTAK-BWLVS ,
ld_e_letyp
 
 TYPE LEIN-LETYP ,
ld_e_clenum
 
 TYPE RLMOB-CLENUM ,
ld_e_lenum
 
 TYPE LEIN-LENUM ,
ld_e_text
 
 TYPE LEINM-TEXT ,
ld_e_screen_fcode
 
 TYPE SY-UCOMM .



SELECT single NLTYP 
  FROM LTAP 
  INTO ld_i_nltyp.
 

"populate fields of struture and append to itab
append wa_x_sus to it_x_sus.

SELECT single NLBER 
  FROM LTAP 
  INTO ld_i_nlber.


SELECT single NLPLA 
  FROM LTAP 
  INTO ld_i_nlpla.


SELECT single BWLVS 
  FROM LTAK 
  INTO ld_i_bwlvs.

SAP Documentation for FM CALL_SCREEN_170