SAP FORMAT_MESSAGE Function Module for









FORMAT_MESSAGE is a standard format message 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 format message FM, simply by entering the name FORMAT_MESSAGE into the relevant SAP transaction such as SE37 or SE38.

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



Function FORMAT_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 'FORMAT_MESSAGE'"
EXPORTING
* ID = SY-MSGID "Application Area
* LANG = '-D' "
* NO = SY-MSGNO "
* V1 = SY-MSGV1 "1st parameter
* V2 = SY-MSGV2 "2nd parameter
* V3 = SY-MSGV3 "3rd parameter
* V4 = SY-MSGV4 "4th Parameter

IMPORTING
MSG = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for FORMAT_MESSAGE

ID - Application Area

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

LANG -

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

NO -

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

V1 - 1st parameter

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

V2 - 2nd parameter

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

V3 - 3rd parameter

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

V4 - 4th Parameter

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

EXPORTING Parameters details for FORMAT_MESSAGE

MSG -

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

EXCEPTIONS details

NOT_FOUND -

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

Copy and paste ABAP code example for FORMAT_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_id  TYPE STRING, "   SY-MSGID
lv_msg  TYPE STRING, "   
lv_not_found  TYPE STRING, "   
lv_lang  TYPE STRING, "   '-D'
lv_no  TYPE STRING, "   SY-MSGNO
lv_v1  TYPE STRING, "   SY-MSGV1
lv_v2  TYPE STRING, "   SY-MSGV2
lv_v3  TYPE STRING, "   SY-MSGV3
lv_v4  TYPE STRING. "   SY-MSGV4

  CALL FUNCTION 'FORMAT_MESSAGE'  "
    EXPORTING
         ID = lv_id
         LANG = lv_lang
         NO = lv_no
         V1 = lv_v1
         V2 = lv_v2
         V3 = lv_v3
         V4 = lv_v4
    IMPORTING
         MSG = lv_msg
    EXCEPTIONS
        NOT_FOUND = 1
. " FORMAT_MESSAGE




ABAP code using 7.40 inline data declarations to call FM FORMAT_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.

DATA(ld_id) = SY-MSGID.
 
 
 
DATA(ld_lang) = '-D'.
 
DATA(ld_no) = SY-MSGNO.
 
DATA(ld_v1) = SY-MSGV1.
 
DATA(ld_v2) = SY-MSGV2.
 
DATA(ld_v3) = SY-MSGV3.
 
DATA(ld_v4) = SY-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!