BUS_MESSAGE_STORE SAP Function module - BDT: Saving Messages

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

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

Pattern for FM BUS_MESSAGE_STORE - BUS MESSAGE STORE

CALL FUNCTION 'BUS_MESSAGE_STORE' "BDT: Saving Messages
  EXPORTING
    arbgb =                     " sy-msgid      Application Area
    msgty =                     " sy-msgty      Message category (S, I, E, W, A)
    txtnr =                     " sy-msgno      Message Number
*   cancel = ' '                " boole_d
*   msgv1 = SPACE               "               Message Variable
*   msgv2 = SPACE               "               Message Variable
*   msgv3 = SPACE               "               Message Variable
*   msgv4 = SPACE               "               Message Variable
*   tbfld_strg =                "               Cursor Field / Bright Fields
*   stepl =                     " sy-stepl      Possible Step Loop Line of Message
*   flag_coll_end =             "               Subsequent messages will not be collected
*   repeat_show = '1'           " c             Display W Messages and I Messages More than Once?
*   sicht =                     " tbz3e-sicht   Current View
*   i_not_active_handler = SPACE  " c           See long text (double-click)
*   namespace = SPACE           " obj_namere    Generic Entry of Protected Namespace (Lowercase)
  IMPORTING
    e_not_active =              "               Message Handler Not Active
    .  "  BUS_MESSAGE_STORE

ABAP code example for Function Module BUS_MESSAGE_STORE

The ABAP code below is a full code listing to execute function module BUS_MESSAGE_STORE 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_not_active  
 
 TYPE STRING
.


DATA(ld_arbgb) = 'some text here'.

DATA(ld_msgty) = 'some text here'.

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

DATA(ld_cancel) = 'some text here'.

DATA(ld_msgv1) = 'some text here'.

DATA(ld_msgv2) = 'some text here'.

DATA(ld_msgv3) = 'some text here'.

DATA(ld_msgv4) = 'some text here'.

DATA(ld_tbfld_strg) = 'some text here'.

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

DATA(ld_flag_coll_end) = 'some text here'.

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

SELECT single SICHT 
  FROM TBZ3E 
  INTO @DATA(ld_sicht).


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

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

CALL FUNCTION 'BUS_MESSAGE_STORE'
  EXPORTING
    arbgb =                      ld_arbgb
    msgty =                      ld_msgty
    txtnr =                      ld_txtnr
*   cancel =                     ld_cancel
*   msgv1 =                      ld_msgv1
*   msgv2 =                      ld_msgv2
*   msgv3 =                      ld_msgv3
*   msgv4 =                      ld_msgv4
*   tbfld_strg =                 ld_tbfld_strg
*   stepl =                      ld_stepl
*   flag_coll_end =              ld_flag_coll_end
*   repeat_show =                ld_repeat_show
*   sicht =                      ld_sicht
*   i_not_active_handler =       ld_i_not_active_handler
*   namespace =                  ld_namespace
  IMPORTING
    e_not_active =               ld_e_not_active
    .  "  BUS_MESSAGE_STORE

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_e_not_active
 
 TYPE STRING ,
ld_arbgb
 
 TYPE SY-MSGID ,
ld_msgty
 
 TYPE SY-MSGTY ,
ld_txtnr
 
 TYPE SY-MSGNO ,
ld_cancel
 
 TYPE BOOLE_D ,
ld_msgv1
 
 TYPE STRING ,
ld_msgv2
 
 TYPE STRING ,
ld_msgv3
 
 TYPE STRING ,
ld_msgv4
 
 TYPE STRING ,
ld_tbfld_strg
 
 TYPE STRING ,
ld_stepl
 
 TYPE SY-STEPL ,
ld_flag_coll_end
 
 TYPE STRING ,
ld_repeat_show
 
 TYPE C ,
ld_sicht
 
 TYPE TBZ3E-SICHT ,
ld_i_not_active_handler
 
 TYPE C ,
ld_namespace
 
 TYPE OBJ_NAMERE .


ld_arbgb = 'some text here'.
ld_msgty = 'some text here'.
ld_txtnr = 'Check type of data required'.
ld_cancel = 'some text here'.
ld_msgv1 = 'some text here'.
ld_msgv2 = 'some text here'.
ld_msgv3 = 'some text here'.
ld_msgv4 = 'some text here'.
ld_tbfld_strg = 'some text here'.
ld_stepl = 'Check type of data required'.
ld_flag_coll_end = 'some text here'.
ld_repeat_show = 'Check type of data required'.

SELECT single SICHT 
  FROM TBZ3E 
  INTO ld_sicht.

ld_i_not_active_handler = 'Check type of data required'.
ld_namespace = 'Check type of data required'.