SAP Function Modules

CALL_SCREEN_HU_DISPLAY SAP Function module - Display information for handling unit screens







CALL_SCREEN_HU_DISPLAY 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_HU_DISPLAY into the relevant SAP transaction such as SE37 or SE80.

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


Pattern for FM CALL_SCREEN_HU_DISPLAY - CALL SCREEN HU DISPLAY





CALL FUNCTION 'CALL_SCREEN_HU_DISPLAY' "Display information for handling unit screens
  EXPORTING
    i_screen =                  " sy-dynnr      Screen number to display
    i_table_type =              " c             Internal table type/name
    i_current_field =           " dd03l-fieldname  Current field for positioning the cursor
    i_current_line =            " sy-tabix      Current line in the step loop
    i_mat_id =                  " vepo-matnr    Material
    i_ser_nr =                  " rlmob-csernr  Serial number
    i_hu_id =                   " rlmob-clenum  Handling unit ID
    i_quantity =                " rlmob-chuqty  Quantity
    i_uom =                     " rlmob-chuuom  Unit of measure
*   i_charg =                   " rlmob-chubatch  Batch ID
    i_sobkz =                   " rlmob-chusobkz  Read HU stock indicator
    i_bestq =                   " rlmob-chubestq  HU stock indicator
    i_sonum =                   " rlmob-chusonum  Special stock number
    i_matdesc =                 " makt-maktx    Material description
    i_activity_type =           " c
*   i_read_hu_mat =             " rlmob-chumat  HU: Material number
  IMPORTING
    o_screen_fcode =            " sy-ucomm      function key pressed by user
    o_current_field =           " dd03l-fieldname  Current field for positioning the cursor
    o_current_line =            " sy-tabix      Current line in the step loop
    o_hu_id_detail =            " vekp-exidv    HU detail
    o_material_detail =         " vepo-matnr
    o_prev_screen =             " sy-dynnr      Previous screen number
    o_hu_id =                   " rlmob-clenum  Handling unit ID
    o_mat_id =                  " vepo-matnr    Material
    o_ser_nr =                  " rlmob-csernr  Serial number
    o_quantity =                " rlmob-chuqty
    o_uom =                     " rlmob-chuuom
    o_charg =                   " rlmob-chubatch
    o_sobkz =                   " rlmob-chusobkz
    o_bestq =                   " rlmob-chubestq
    o_sonum =                   " rlmob-chusonum
    o_table_type =              " c
    o_mat_qty_detail =          " vepo-vemng
    o_mat_uom_detail =          " vepo-vemeh
    o_mat_charg_detail =        " vepo-charg
    o_mat_sobkz_detail =        " vepo-sobkz
    o_mat_bestq_detail =        " vepo-bestq
    o_mat_sonum_detail =        " vepo-sonum
    o_matdesc =                 " makt-maktx
    o_read_hu_mat =             " rlmob-chumat  HU: Material number
  TABLES
    t_hu_header_for_screen =    "
    t_hu_items_for_screen =     "
    t_lein =                    " lein
  EXCEPTIONS
    FAIL_IN_CALLING_SCREEN = 1  "               Failure in calling the screen
    FAIL_IN_PHYSICAL_SCREEN_NUMBER = 2  "
    .  "  CALL_SCREEN_HU_DISPLAY

ABAP code example for Function Module CALL_SCREEN_HU_DISPLAY





The ABAP code below is a full code listing to execute function module CALL_SCREEN_HU_DISPLAY 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_screen_fcode  TYPE SY-UCOMM ,
ld_o_current_field  TYPE DD03L-FIELDNAME ,
ld_o_current_line  TYPE SY-TABIX ,
ld_o_hu_id_detail  TYPE VEKP-EXIDV ,
ld_o_material_detail  TYPE VEPO-MATNR ,
ld_o_prev_screen  TYPE SY-DYNNR ,
ld_o_hu_id  TYPE RLMOB-CLENUM ,
ld_o_mat_id  TYPE VEPO-MATNR ,
ld_o_ser_nr  TYPE RLMOB-CSERNR ,
ld_o_quantity  TYPE RLMOB-CHUQTY ,
ld_o_uom  TYPE RLMOB-CHUUOM ,
ld_o_charg  TYPE RLMOB-CHUBATCH ,
ld_o_sobkz  TYPE RLMOB-CHUSOBKZ ,
ld_o_bestq  TYPE RLMOB-CHUBESTQ ,
ld_o_sonum  TYPE RLMOB-CHUSONUM ,
ld_o_table_type  TYPE C ,
ld_o_mat_qty_detail  TYPE VEPO-VEMNG ,
ld_o_mat_uom_detail  TYPE VEPO-VEMEH ,
ld_o_mat_charg_detail  TYPE VEPO-CHARG ,
ld_o_mat_sobkz_detail  TYPE VEPO-SOBKZ ,
ld_o_mat_bestq_detail  TYPE VEPO-BESTQ ,
ld_o_mat_sonum_detail  TYPE VEPO-SONUM ,
ld_o_matdesc  TYPE MAKT-MAKTX ,
ld_o_read_hu_mat  TYPE RLMOB-CHUMAT ,
it_t_hu_header_for_screen  TYPE STANDARD TABLE OF STRING,"TABLES PARAM
wa_t_hu_header_for_screen  LIKE LINE OF it_t_hu_header_for_screen ,
it_t_hu_items_for_screen  TYPE STANDARD TABLE OF STRING,"TABLES PARAM
wa_t_hu_items_for_screen  LIKE LINE OF it_t_hu_items_for_screen ,
it_t_lein  TYPE STANDARD TABLE OF LEIN,"TABLES PARAM
wa_t_lein  LIKE LINE OF it_t_lein .

DATA(ld_i_screen) = 'some text here'.
DATA(ld_i_table_type) = 'some text here'.

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

DATA(ld_i_current_line) = '123 '.

SELECT single MATNR
FROM VEPO
INTO @DATA(ld_i_mat_id).


DATA(ld_i_ser_nr) = some text here

DATA(ld_i_hu_id) = some text here

DATA(ld_i_quantity) = Check type of data required

DATA(ld_i_uom) = Check type of data required

DATA(ld_i_charg) = some text here

DATA(ld_i_sobkz) = some text here

DATA(ld_i_bestq) = some text here

DATA(ld_i_sonum) = some text here

SELECT single MAKTX
FROM MAKT
INTO @DATA(ld_i_matdesc).

DATA(ld_i_activity_type) = '123 '.

DATA(ld_i_read_hu_mat) = some text here

"populate fields of struture and append to itab
append wa_t_hu_header_for_screen to it_t_hu_header_for_screen.

"populate fields of struture and append to itab
append wa_t_hu_items_for_screen to it_t_hu_items_for_screen.

"populate fields of struture and append to itab
append wa_t_lein to it_t_lein. . CALL FUNCTION 'CALL_SCREEN_HU_DISPLAY' EXPORTING i_screen = ld_i_screen i_table_type = ld_i_table_type i_current_field = ld_i_current_field i_current_line = ld_i_current_line i_mat_id = ld_i_mat_id i_ser_nr = ld_i_ser_nr i_hu_id = ld_i_hu_id i_quantity = ld_i_quantity i_uom = ld_i_uom * i_charg = ld_i_charg i_sobkz = ld_i_sobkz i_bestq = ld_i_bestq i_sonum = ld_i_sonum i_matdesc = ld_i_matdesc i_activity_type = ld_i_activity_type * i_read_hu_mat = ld_i_read_hu_mat IMPORTING o_screen_fcode = ld_o_screen_fcode o_current_field = ld_o_current_field o_current_line = ld_o_current_line o_hu_id_detail = ld_o_hu_id_detail o_material_detail = ld_o_material_detail o_prev_screen = ld_o_prev_screen o_hu_id = ld_o_hu_id o_mat_id = ld_o_mat_id o_ser_nr = ld_o_ser_nr o_quantity = ld_o_quantity o_uom = ld_o_uom o_charg = ld_o_charg o_sobkz = ld_o_sobkz o_bestq = ld_o_bestq o_sonum = ld_o_sonum o_table_type = ld_o_table_type o_mat_qty_detail = ld_o_mat_qty_detail o_mat_uom_detail = ld_o_mat_uom_detail o_mat_charg_detail = ld_o_mat_charg_detail o_mat_sobkz_detail = ld_o_mat_sobkz_detail o_mat_bestq_detail = ld_o_mat_bestq_detail o_mat_sonum_detail = ld_o_mat_sonum_detail o_matdesc = ld_o_matdesc o_read_hu_mat = ld_o_read_hu_mat TABLES t_hu_header_for_screen = it_t_hu_header_for_screen t_hu_items_for_screen = it_t_hu_items_for_screen t_lein = it_t_lein EXCEPTIONS FAIL_IN_CALLING_SCREEN = 1 FAIL_IN_PHYSICAL_SCREEN_NUMBER = 2 . " CALL_SCREEN_HU_DISPLAY
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_screen_fcode  TYPE SY-UCOMM ,
it_t_hu_header_for_screen  TYPE STANDARD TABLE OF STRING ,
wa_t_hu_header_for_screen  LIKE LINE OF it_t_hu_header_for_screen,
ld_i_screen  TYPE SY-DYNNR ,
ld_i_table_type  TYPE C ,
it_t_hu_items_for_screen  TYPE STANDARD TABLE OF STRING ,
wa_t_hu_items_for_screen  LIKE LINE OF it_t_hu_items_for_screen,
ld_o_current_field  TYPE DD03L-FIELDNAME ,
ld_i_current_field  TYPE DD03L-FIELDNAME ,
ld_o_current_line  TYPE SY-TABIX ,
it_t_lein  TYPE STANDARD TABLE OF LEIN ,
wa_t_lein  LIKE LINE OF it_t_lein,
ld_i_current_line  TYPE SY-TABIX ,
ld_o_hu_id_detail  TYPE VEKP-EXIDV ,
ld_i_mat_id  TYPE VEPO-MATNR ,
ld_o_material_detail  TYPE VEPO-MATNR ,
ld_i_ser_nr  TYPE RLMOB-CSERNR ,
ld_o_prev_screen  TYPE SY-DYNNR ,
ld_i_hu_id  TYPE RLMOB-CLENUM ,
ld_o_hu_id  TYPE RLMOB-CLENUM ,
ld_o_mat_id  TYPE VEPO-MATNR ,
ld_i_quantity  TYPE RLMOB-CHUQTY ,
ld_i_uom  TYPE RLMOB-CHUUOM ,
ld_o_ser_nr  TYPE RLMOB-CSERNR ,
ld_i_charg  TYPE RLMOB-CHUBATCH ,
ld_o_quantity  TYPE RLMOB-CHUQTY ,
ld_o_uom  TYPE RLMOB-CHUUOM ,
ld_i_sobkz  TYPE RLMOB-CHUSOBKZ ,
ld_o_charg  TYPE RLMOB-CHUBATCH ,
ld_i_bestq  TYPE RLMOB-CHUBESTQ ,
ld_o_sobkz  TYPE RLMOB-CHUSOBKZ ,
ld_i_sonum  TYPE RLMOB-CHUSONUM ,
ld_o_bestq  TYPE RLMOB-CHUBESTQ ,
ld_i_matdesc  TYPE MAKT-MAKTX ,
ld_o_sonum  TYPE RLMOB-CHUSONUM ,
ld_i_activity_type  TYPE C ,
ld_i_read_hu_mat  TYPE RLMOB-CHUMAT ,
ld_o_table_type  TYPE C ,
ld_o_mat_qty_detail  TYPE VEPO-VEMNG ,
ld_o_mat_uom_detail  TYPE VEPO-VEMEH ,
ld_o_mat_charg_detail  TYPE VEPO-CHARG ,
ld_o_mat_sobkz_detail  TYPE VEPO-SOBKZ ,
ld_o_mat_bestq_detail  TYPE VEPO-BESTQ ,
ld_o_mat_sonum_detail  TYPE VEPO-SONUM ,
ld_o_matdesc  TYPE MAKT-MAKTX ,
ld_o_read_hu_mat  TYPE RLMOB-CHUMAT .


"populate fields of struture and append to itab
append wa_t_hu_header_for_screen to it_t_hu_header_for_screen.
ld_i_screen = 'some text here'.
ld_i_table_type = 'some text here'.

"populate fields of struture and append to itab
append wa_t_hu_items_for_screen to it_t_hu_items_for_screen.

SELECT single FIELDNAME
FROM DD03L
INTO ld_i_current_field.


"populate fields of struture and append to itab
append wa_t_lein to it_t_lein.
ld_i_current_line = '123 '.

SELECT single MATNR
FROM VEPO
INTO ld_i_mat_id.


ld_i_ser_nr = some text here

ld_i_hu_id = some text here

ld_i_quantity = Check type of data required

ld_i_uom = Check type of data required

ld_i_charg = some text here

ld_i_sobkz = some text here

ld_i_bestq = some text here

ld_i_sonum = some text here

SELECT single MAKTX
FROM MAKT
INTO ld_i_matdesc.

ld_i_activity_type = '123 '.

ld_i_read_hu_mat = some text here

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CALL_SCREEN_HU_DISPLAY or its description.