MM_ARRANG_GRID_BUFFER_MESSAGE SAP Function module

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

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

Pattern for FM MM_ARRANG_GRID_BUFFER_MESSAGE - MM ARRANG GRID BUFFER MESSAGE

CALL FUNCTION 'MM_ARRANG_GRID_BUFFER_MESSAGE' "
* EXPORTING
*   i_knuma =                   " knuma
*   i_knumh =                   " knumh
*   i_refresh =                 " char1
*   i_mode = 'A'                " char1
*   i_counter_item =            " numc10
*   i_kona_all = SPACE          " boole_d
*   it_error_message_arr =      " type_arrangerra
  IMPORTING
    et_error_message_arr =      " type_arrangerra
  EXCEPTIONS
    PARAMETER_ERROR = 1         "
    .  "  MM_ARRANG_GRID_BUFFER_MESSAGE

ABAP code example for Function Module MM_ARRANG_GRID_BUFFER_MESSAGE

The ABAP code below is a full code listing to execute function module MM_ARRANG_GRID_BUFFER_MESSAGE 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_et_error_message_arr  
 
 TYPE TYPE_ARRANGERRA
.


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

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

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

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

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

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

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

CALL FUNCTION 'MM_ARRANG_GRID_BUFFER_MESSAGE'
* EXPORTING
*   i_knuma =                    ld_i_knuma
*   i_knumh =                    ld_i_knumh
*   i_refresh =                  ld_i_refresh
*   i_mode =                     ld_i_mode
*   i_counter_item =             ld_i_counter_item
*   i_kona_all =                 ld_i_kona_all
*   it_error_message_arr =       ld_it_error_message_arr
  IMPORTING
    et_error_message_arr =       ld_et_error_message_arr
  EXCEPTIONS
    PARAMETER_ERROR =            1
    .  "  MM_ARRANG_GRID_BUFFER_MESSAGE

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_et_error_message_arr
 
 TYPE TYPE_ARRANGERRA ,
ld_i_knuma
 
 TYPE KNUMA ,
ld_i_knumh
 
 TYPE KNUMH ,
ld_i_refresh
 
 TYPE CHAR1 ,
ld_i_mode
 
 TYPE CHAR1 ,
ld_i_counter_item
 
 TYPE NUMC10 ,
ld_i_kona_all
 
 TYPE BOOLE_D ,
ld_it_error_message_arr
 
 TYPE TYPE_ARRANGERRA .


ld_i_knuma = 'Check type of data required'.
ld_i_knumh = 'Check type of data required'.
ld_i_refresh = 'Check type of data required'.
ld_i_mode = 'Check type of data required'.
ld_i_counter_item = 'Check type of data required'.
ld_i_kona_all = 'Check type of data required'.
ld_it_error_message_arr = 'Check type of data required'.