SAP MESSAGE_SET_AND_CONVERT Function Module for NOTRANSL: Setzen und Übertragen der Systemfelder einer Message.

Search SAP Function Modules

MESSAGE_SET_AND_CONVERT is a standard message set and convert 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: Setzen und Übertragen der Systemfelder einer Message. 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 message set and convert FM, simply by entering the name MESSAGE_SET_AND_CONVERT into the relevant SAP transaction such as SE37 or SE38.

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

Function MESSAGE_SET_AND_CONVERT 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 'MESSAGE_SET_AND_CONVERT'"NOTRANSL: Setzen und Übertragen der Systemfelder einer Message.
  EXPORTING
   MSG_CLASS =  "Message Class
   MSG_TYPE =  "ABAP System Field: Message Type
   MSG_NUMBER =  "Message Number
*  MSG_PARM1 =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  MSG_PARM2 =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  MSG_PARM3 =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  MSG_PARM4 =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  LOG_NO =  "Application Log: Log Number
*  LOG_MSG_NO =  "Application log: Internal message serial number

 IMPORTING
   RETURN =  "Return Parameter

.

IMPORTING Parameters details for MESSAGE_SET_AND_CONVERT

MSG_CLASS - Message Class

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

MSG_TYPE - ABAP System Field: Message Type

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

MSG_NUMBER - Message Number

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

MSG_PARM1 - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

MSG_PARM2 - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

MSG_PARM3 - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

MSG_PARM4 - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

LOG_NO - Application Log: Log Number

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

LOG_MSG_NO - Application log: Internal message serial number

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

EXPORTING Parameters details for MESSAGE_SET_AND_CONVERT

RETURN - Return Parameter

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

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

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