CALL_SCREEN_0811 SAP Function module - Calling screen 0811

CALL_SCREEN_0811 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_0811 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_0811 - CALL SCREEN 0811

CALL FUNCTION 'CALL_SCREEN_0811' "Calling screen 0811
  EXPORTING
    i_trans_id =                " vttk-tknum    HU/Shu number
    i_staging_area =            " likp-lgbzo    HU/Shu number
    i_door =                    " likp-lgtor    Door for warehouse number
    i_hu_cntr =                 " rlmob-hucnt   HU/Shu number
    i_hu_loaded =               " rlmob-huload  Number of loaded HU/Shu
    i_hu_id =                   " vekp-exidv    HU/Shu
    i_field_name =              " dd03l-fieldname  Field name
  IMPORTING
    o_trans_id =                " vttk-tknum    HU/Shu number
    o_staging_area =            " likp-lgbzo    HU/Shu number
    o_door =                    " likp-lgtor    Door for warehouse number
    o_hu_cnt =                  " rlmob-hucnt   HU/Shu number
    o_hu_loaded =               " rlmob-huload  Number of loaded HU/Shu
    o_hu_id =                   " vekp-exidv    HU/Shu
    o_screen_fcode =            " sy-ucomm      function key pressed by user
    o_field_name =              " dd03l-fieldname  Field name
  EXCEPTIONS
    FAIL_IN_CALLING_SCREEN = 1  "
    FAIL_IN_PHYSICAL_SCREEN_NUMBER = 2  "
    .  "  CALL_SCREEN_0811

ABAP code example for Function Module CALL_SCREEN_0811

The ABAP code below is a full code listing to execute function module CALL_SCREEN_0811 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_o_trans_id  
 
 TYPE VTTK-TKNUM
,
ld_o_staging_area  
 
 TYPE LIKP-LGBZO
,
ld_o_door  
 
 TYPE LIKP-LGTOR
,
ld_o_hu_cnt  
 
 TYPE RLMOB-HUCNT
,
ld_o_hu_loaded  
 
 TYPE RLMOB-HULOAD
,
ld_o_hu_id  
 
 TYPE VEKP-EXIDV
,
ld_o_screen_fcode  
 
 TYPE SY-UCOMM
,
ld_o_field_name  
 
 TYPE DD03L-FIELDNAME
.

 

SELECT single TKNUM 
  FROM VTTK 
  INTO @DATA(ld_i_trans_id).

 

SELECT single LGBZO 
  FROM LIKP 
  INTO @DATA(ld_i_staging_area).

 

SELECT single LGTOR 
  FROM LIKP 
  INTO @DATA(ld_i_door).



DATA(ld_i_hu_cntr) = 123 


DATA(ld_i_hu_loaded) = 123 
 

SELECT single EXIDV 
  FROM VEKP 
  INTO @DATA(ld_i_hu_id).

 

SELECT single FIELDNAME 
  FROM DD03L 
  INTO @DATA(ld_i_field_name).

.

CALL FUNCTION 'CALL_SCREEN_0811'
  EXPORTING
    i_trans_id =                 ld_i_trans_id
    i_staging_area =             ld_i_staging_area
    i_door =                     ld_i_door
    i_hu_cntr =                  ld_i_hu_cntr
    i_hu_loaded =                ld_i_hu_loaded
    i_hu_id =                    ld_i_hu_id
    i_field_name =               ld_i_field_name
  IMPORTING
    o_trans_id =                 ld_o_trans_id
    o_staging_area =             ld_o_staging_area
    o_door =                     ld_o_door
    o_hu_cnt =                   ld_o_hu_cnt
    o_hu_loaded =                ld_o_hu_loaded
    o_hu_id =                    ld_o_hu_id
    o_screen_fcode =             ld_o_screen_fcode
    o_field_name =               ld_o_field_name
  EXCEPTIONS
    FAIL_IN_CALLING_SCREEN =     1
    FAIL_IN_PHYSICAL_SCREEN_NUMBER =    2
    .  "  CALL_SCREEN_0811

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "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_o_trans_id
 
 TYPE VTTK-TKNUM ,
ld_i_trans_id
 
 TYPE VTTK-TKNUM ,
ld_o_staging_area
 
 TYPE LIKP-LGBZO ,
ld_i_staging_area
 
 TYPE LIKP-LGBZO ,
ld_o_door
 
 TYPE LIKP-LGTOR ,
ld_i_door
 
 TYPE LIKP-LGTOR ,
ld_o_hu_cnt
 
 TYPE RLMOB-HUCNT ,
ld_i_hu_cntr
 
 TYPE RLMOB-HUCNT ,
ld_o_hu_loaded
 
 TYPE RLMOB-HULOAD ,
ld_i_hu_loaded
 
 TYPE RLMOB-HULOAD ,
ld_o_hu_id
 
 TYPE VEKP-EXIDV ,
ld_i_hu_id
 
 TYPE VEKP-EXIDV ,
ld_o_screen_fcode
 
 TYPE SY-UCOMM ,
ld_i_field_name
 
 TYPE DD03L-FIELDNAME ,
ld_o_field_name
 
 TYPE DD03L-FIELDNAME .



SELECT single TKNUM 
  FROM VTTK 
  INTO ld_i_trans_id.


SELECT single LGBZO 
  FROM LIKP 
  INTO ld_i_staging_area.


SELECT single LGTOR 
  FROM LIKP 
  INTO ld_i_door.


ld_i_hu_cntr = 123 

ld_i_hu_loaded = 123 

SELECT single EXIDV 
  FROM VEKP 
  INTO ld_i_hu_id.


SELECT single FIELDNAME 
  FROM DD03L 
  INTO ld_i_field_name.

SAP Documentation for FM CALL_SCREEN_0811