EXIT_SAPLLMOB_995 SAP Function module - USER EXIT - DATA TO CUSTOMER SCREEN (DUMMY 1807)

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

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

Pattern for FM EXIT_SAPLLMOB_995 - EXIT SAPLLMOB 995

CALL FUNCTION 'EXIT_SAPLLMOB_995' "USER EXIT - DATA TO CUSTOMER SCREEN (DUMMY 1807)
  EXPORTING
    i_vttk =                    " vttk          Data to Display on Customer Screen
    i_vekp =                    " vekp          Data to Display on Customer Screen
    i_vttp =                    " vttp          Data to Display on Customer Screen
    i_rlmob =                   " rlmob         Data to Display on Customer Screen
    i_likp =                    " likp          Data to Display on Customer Screen
    i_tap_init_size =           " sy-tabix      Internal Tables, Current Line Index
    i_tap_total_lines =         " sy-tabix      Internal Tables, Current Line Index
    i_tap_index =               " sy-tabix      Internal Tables, Current Line Index
    i_temporary_index =         " sy-tabix      Internal Tables, Current Line Index
    i_line_no_step_loop =       " sy-tabix      Internal Tables, Current Line Index
    i_screen_fcode =            " sy-ucomm      Screens, function code triggered by PAI
    i_current_field =           " c
  TABLES
    tap_vttp =                  " vttp          Shipment Item
    .  "  EXIT_SAPLLMOB_995

ABAP code example for Function Module EXIT_SAPLLMOB_995

The ABAP code below is a full code listing to execute function module EXIT_SAPLLMOB_995 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:
it_tap_vttp  
 
 TYPE STANDARD TABLE OF VTTP,"TABLES PARAM
wa_tap_vttp
 
 LIKE LINE OF it_tap_vttp
.


DATA(ld_i_vttk) = 'Check type of data required'.

DATA(ld_i_vekp) = 'Check type of data required'.

DATA(ld_i_vttp) = 'Check type of data required'.

DATA(ld_i_rlmob) = 'Check type of data required'.

DATA(ld_i_likp) = 'Check type of data required'.

DATA(ld_i_tap_init_size) = '123 '.

DATA(ld_i_tap_total_lines) = '123 '.

DATA(ld_i_tap_index) = '123 '.

DATA(ld_i_temporary_index) = '123 '.

DATA(ld_i_line_no_step_loop) = '123 '.

DATA(ld_i_screen_fcode) = 'some text here'.

DATA(ld_i_current_field) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_tap_vttp to it_tap_vttp.
.

CALL FUNCTION 'EXIT_SAPLLMOB_995'
  EXPORTING
    i_vttk =                     ld_i_vttk
    i_vekp =                     ld_i_vekp
    i_vttp =                     ld_i_vttp
    i_rlmob =                    ld_i_rlmob
    i_likp =                     ld_i_likp
    i_tap_init_size =            ld_i_tap_init_size
    i_tap_total_lines =          ld_i_tap_total_lines
    i_tap_index =                ld_i_tap_index
    i_temporary_index =          ld_i_temporary_index
    i_line_no_step_loop =        ld_i_line_no_step_loop
    i_screen_fcode =             ld_i_screen_fcode
    i_current_field =            ld_i_current_field
  TABLES
    tap_vttp =                   it_tap_vttp
    .  "  EXIT_SAPLLMOB_995

IF SY-SUBRC EQ 0.
  "All OK
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_i_vttk
 
 TYPE VTTK ,
it_tap_vttp
 
 TYPE STANDARD TABLE OF VTTP ,
wa_tap_vttp
 
 LIKE LINE OF it_tap_vttp,
ld_i_vekp
 
 TYPE VEKP ,
ld_i_vttp
 
 TYPE VTTP ,
ld_i_rlmob
 
 TYPE RLMOB ,
ld_i_likp
 
 TYPE LIKP ,
ld_i_tap_init_size
 
 TYPE SY-TABIX ,
ld_i_tap_total_lines
 
 TYPE SY-TABIX ,
ld_i_tap_index
 
 TYPE SY-TABIX ,
ld_i_temporary_index
 
 TYPE SY-TABIX ,
ld_i_line_no_step_loop
 
 TYPE SY-TABIX ,
ld_i_screen_fcode
 
 TYPE SY-UCOMM ,
ld_i_current_field
 
 TYPE C .


ld_i_vttk = 'some text here'. 

"populate fields of struture and append to itab
append wa_tap_vttp to it_tap_vttp.
ld_i_vekp = 'some text here'.
ld_i_vttp = 'some text here'.
ld_i_rlmob = 'some text here'.
ld_i_likp = 'some text here'.
ld_i_tap_init_size = '123 '.
ld_i_tap_total_lines = '123 '.
ld_i_tap_index = '123 '.
ld_i_temporary_index = '123 '.
ld_i_line_no_step_loop = '123 '.
ld_i_screen_fcode = 'some text here'.
ld_i_current_field = 'some text here'.

SAP Documentation for FM EXIT_SAPLLMOB_995