SAP BBP_MESSAGE_APPEND Function Module for Hänge eine einzelne Nachricht an die Nachrichtentabelle an









BBP_MESSAGE_APPEND is a standard bbp message append SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Hänge eine einzelne Nachricht an die Nachrichtentabelle an 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 bbp message append FM, simply by entering the name BBP_MESSAGE_APPEND into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_MESSAGE_APPEND 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 'BBP_MESSAGE_APPEND'"Hänge eine einzelne Nachricht an die Nachrichtentabelle an
EXPORTING
I_MSGTY = "Message type: S Success, E Error, W Warning, I Info, A Abort
I_MSGID = "Messages, message class
I_MSGNO = "Messages, message number
* I_MSGV1 = "Messages, message variables
* I_MSGV2 = "Messages, message variables
* I_MSGV3 = "Messages, message variables
* I_MSGV4 = "Messages, message variables

TABLES
T_MESSAGES = "Fehlermeldungen zu einer PD-Methode
.



IMPORTING Parameters details for BBP_MESSAGE_APPEND

I_MSGTY - Message type: S Success, E Error, W Warning, I Info, A Abort

Data type: BBP_PDS_MESSAGES-MSGTY
Optional: No
Call by Reference: No ( called with pass by value option)

I_MSGID - Messages, message class

Data type: BBP_PDS_MESSAGES-MSGID
Optional: No
Call by Reference: No ( called with pass by value option)

I_MSGNO - Messages, message number

Data type: BBP_PDS_MESSAGES-MSGNO
Optional: No
Call by Reference: No ( called with pass by value option)

I_MSGV1 - Messages, message variables

Data type: BBP_PDS_MESSAGES-MSGV1
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGV2 - Messages, message variables

Data type: BBP_PDS_MESSAGES-MSGV2
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGV3 - Messages, message variables

Data type: BBP_PDS_MESSAGES-MSGV3
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGV4 - Messages, message variables

Data type: BBP_PDS_MESSAGES-MSGV4
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BBP_MESSAGE_APPEND

T_MESSAGES - Fehlermeldungen zu einer PD-Methode

Data type: BBP_PDS_MESSAGES
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_MESSAGE_APPEND 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_i_msgty  TYPE BBP_PDS_MESSAGES-MSGTY, "   
lt_t_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lv_i_msgid  TYPE BBP_PDS_MESSAGES-MSGID, "   
lv_i_msgno  TYPE BBP_PDS_MESSAGES-MSGNO, "   
lv_i_msgv1  TYPE BBP_PDS_MESSAGES-MSGV1, "   
lv_i_msgv2  TYPE BBP_PDS_MESSAGES-MSGV2, "   
lv_i_msgv3  TYPE BBP_PDS_MESSAGES-MSGV3, "   
lv_i_msgv4  TYPE BBP_PDS_MESSAGES-MSGV4. "   

  CALL FUNCTION 'BBP_MESSAGE_APPEND'  "Hänge eine einzelne Nachricht an die Nachrichtentabelle an
    EXPORTING
         I_MSGTY = lv_i_msgty
         I_MSGID = lv_i_msgid
         I_MSGNO = lv_i_msgno
         I_MSGV1 = lv_i_msgv1
         I_MSGV2 = lv_i_msgv2
         I_MSGV3 = lv_i_msgv3
         I_MSGV4 = lv_i_msgv4
    TABLES
         T_MESSAGES = lt_t_messages
. " BBP_MESSAGE_APPEND




ABAP code using 7.40 inline data declarations to call FM BBP_MESSAGE_APPEND

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 MSGTY FROM BBP_PDS_MESSAGES INTO @DATA(ld_i_msgty).
 
 
"SELECT single MSGID FROM BBP_PDS_MESSAGES INTO @DATA(ld_i_msgid).
 
"SELECT single MSGNO FROM BBP_PDS_MESSAGES INTO @DATA(ld_i_msgno).
 
"SELECT single MSGV1 FROM BBP_PDS_MESSAGES INTO @DATA(ld_i_msgv1).
 
"SELECT single MSGV2 FROM BBP_PDS_MESSAGES INTO @DATA(ld_i_msgv2).
 
"SELECT single MSGV3 FROM BBP_PDS_MESSAGES INTO @DATA(ld_i_msgv3).
 
"SELECT single MSGV4 FROM BBP_PDS_MESSAGES INTO @DATA(ld_i_msgv4).
 


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!