SAP MM_ARRANG_DISPLAY_MESSAGE_DOCU Function Module for Display long text for message









MM_ARRANG_DISPLAY_MESSAGE_DOCU is a standard mm arrang display message docu SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display long text for 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 mm arrang display message docu FM, simply by entering the name MM_ARRANG_DISPLAY_MESSAGE_DOCU into the relevant SAP transaction such as SE37 or SE38.

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



Function MM_ARRANG_DISPLAY_MESSAGE_DOCU 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 'MM_ARRANG_DISPLAY_MESSAGE_DOCU'"Display long text for message
EXPORTING
I_ERROR_MESSAGES = "List of Error Messages, Settlement, Arrangements, Purchasing
* I_LANGU = SY-LANGU "ABAP System Field: Language Key of Text Environment
* I_ERROR_MESSAGES_TEXT = "Generic Type

EXCEPTIONS
PARAMETER_ERROR = 1
.



IMPORTING Parameters details for MM_ARRANG_DISPLAY_MESSAGE_DOCU

I_ERROR_MESSAGES - List of Error Messages, Settlement, Arrangements, Purchasing

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

I_LANGU - ABAP System Field: Language Key of Text Environment

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

I_ERROR_MESSAGES_TEXT - Generic Type

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

EXCEPTIONS details

PARAMETER_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

Copy and paste ABAP code example for MM_ARRANG_DISPLAY_MESSAGE_DOCU 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_parameter_error  TYPE STRING, "   
lv_i_error_messages  TYPE ARRANG_ERR, "   
lv_i_langu  TYPE SY-LANGU, "   SY-LANGU
lv_i_error_messages_text  TYPE C. "   

  CALL FUNCTION 'MM_ARRANG_DISPLAY_MESSAGE_DOCU'  "Display long text for message
    EXPORTING
         I_ERROR_MESSAGES = lv_i_error_messages
         I_LANGU = lv_i_langu
         I_ERROR_MESSAGES_TEXT = lv_i_error_messages_text
    EXCEPTIONS
        PARAMETER_ERROR = 1
. " MM_ARRANG_DISPLAY_MESSAGE_DOCU




ABAP code using 7.40 inline data declarations to call FM MM_ARRANG_DISPLAY_MESSAGE_DOCU

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 LANGU FROM SY INTO @DATA(ld_i_langu).
DATA(ld_i_langu) = SY-LANGU.
 
 


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!