SAP CNPB_M_SAVE_MESSAGE Function Module for NOTRANSL: Speichert Meldungen, um sie später auszugeben
CNPB_M_SAVE_MESSAGE is a standard cnpb m save message 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: Speichert Meldungen, um sie später auszugeben 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 cnpb m save message FM, simply by entering the name CNPB_M_SAVE_MESSAGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNPB_M
Program Name: SAPLCNPB_M
Main Program: SAPLCNPB_M
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CNPB_M_SAVE_MESSAGE 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 'CNPB_M_SAVE_MESSAGE'"NOTRANSL: Speichert Meldungen, um sie später auszugeben.
EXPORTING
I_MSGID = "Messages, Message Class
I_MSGTY = "Messages, Message Type
I_MSGNO = "Messages, Message Number
IMPORTING Parameters details for CNPB_M_SAVE_MESSAGE
I_MSGID - Messages, Message Class
Data type: SY-MSGIDOptional: No
Call by Reference: Yes
I_MSGTY - Messages, Message Type
Data type: SY-MSGTYOptional: No
Call by Reference: Yes
I_MSGNO - Messages, Message Number
Data type: SY-MSGNOOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNPB_M_SAVE_MESSAGE 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_msgid | TYPE SY-MSGID, " | |||
lv_i_msgty | TYPE SY-MSGTY, " | |||
lv_i_msgno | TYPE SY-MSGNO. " |
  CALL FUNCTION 'CNPB_M_SAVE_MESSAGE' "NOTRANSL: Speichert Meldungen, um sie später auszugeben |
EXPORTING | ||
I_MSGID | = lv_i_msgid | |
I_MSGTY | = lv_i_msgty | |
I_MSGNO | = lv_i_msgno | |
. " CNPB_M_SAVE_MESSAGE |
ABAP code using 7.40 inline data declarations to call FM CNPB_M_SAVE_MESSAGE
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 MSGID FROM SY INTO @DATA(ld_i_msgid). | ||||
"SELECT single MSGTY FROM SY INTO @DATA(ld_i_msgty). | ||||
"SELECT single MSGNO FROM SY INTO @DATA(ld_i_msgno). | ||||
Search for further information about these or an SAP related objects