SAP MESSAGES_SAVE Function Module for

Search SAP Function Modules

MESSAGES_SAVE is a standard messages save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 messages save FM, simply by entering the name MESSAGES_SAVE into the relevant SAP transaction such as SE37 or SE38.

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

Function MESSAGES_SAVE 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 'MESSAGES_SAVE'"
  EXPORTING
   I_BALOBJECT =  "
*  I_BALSUBOBJECT =  "
*  I_IN_UPDATE_TASK = ' ' "
*  I_IDENTIFICATION =  "

 IMPORTING
   E_LOG_HANDLE =  "

EXCEPTIONS
   NO_MESSAGES = 1    NOT_ACTIVE = 2    PROGRAM_ERROR = 3    SAVE_NOT_ALLOWED = 4    WRONG_IDENTIFICATION = 5 

.

IMPORTING Parameters details for MESSAGES_SAVE

I_BALOBJECT -

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

I_BALSUBOBJECT -

Data type: BALSUBOBJ
Optional: Yes
Call by Reference: Yes

I_IN_UPDATE_TASK -

Data type: BOOLE_D
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_IDENTIFICATION -

Data type: SYUZEIT
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for MESSAGES_SAVE

E_LOG_HANDLE -

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

EXCEPTIONS details

NO_MESSAGES -

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

NOT_ACTIVE -

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

PROGRAM_ERROR - Program Errors

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

SAVE_NOT_ALLOWED -

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

WRONG_IDENTIFICATION -

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

Copy and paste ABAP code example for MESSAGES_SAVE 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.

ABAP code using 7.40 inline data declarations to call FM MESSAGES_SAVE

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.

Search for further information about these or an SAP related objects