SAP MB_MESSAGE_UPDATE Function Module for NOTRANSL: Verbuchung Nachrichtenfindung









MB_MESSAGE_UPDATE is a standard mb message update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Verbuchung Nachrichtenfindung processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for mb message update FM, simply by entering the name MB_MESSAGE_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: MBME
Program Name: SAPLMBME
Main Program: SAPLMBME
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MB_MESSAGE_UPDATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'MB_MESSAGE_UPDATE'"NOTRANSL: Verbuchung Nachrichtenfindung
EXPORTING
* M_KAPPL = ' ' "Application for message conditions
* M_OBJKY = ' ' "Object key
.



IMPORTING Parameters details for MB_MESSAGE_UPDATE

M_KAPPL - Application for message conditions

Data type: NAST-KAPPL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

M_OBJKY - Object key

Data type: NAST-OBJKY
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MB_MESSAGE_UPDATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_m_kappl  TYPE NAST-KAPPL, "   SPACE
lv_m_objky  TYPE NAST-OBJKY. "   ' '

  CALL FUNCTION 'MB_MESSAGE_UPDATE'  "NOTRANSL: Verbuchung Nachrichtenfindung
    EXPORTING
         M_KAPPL = lv_m_kappl
         M_OBJKY = lv_m_objky
. " MB_MESSAGE_UPDATE




ABAP code using 7.40 inline data declarations to call FM MB_MESSAGE_UPDATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

"SELECT single KAPPL FROM NAST INTO @DATA(ld_m_kappl).
DATA(ld_m_kappl) = ' '.
 
"SELECT single OBJKY FROM NAST INTO @DATA(ld_m_objky).
DATA(ld_m_objky) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!