SAP MESSAGE_HANDLING Function Module for NOTRANSL: ATP-Server: Nachrichten-Verwaltung









MESSAGE_HANDLING is a standard message handling 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: ATP-Server: Nachrichten-Verwaltung 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 handling FM, simply by entering the name MESSAGE_HANDLING into the relevant SAP transaction such as SE37 or SE38.

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



Function MESSAGE_HANDLING 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_HANDLING'"NOTRANSL: ATP-Server: Nachrichten-Verwaltung
EXPORTING
P_FCODE = "

TABLES
* P_ATPMSGX = "
.



IMPORTING Parameters details for MESSAGE_HANDLING

P_FCODE -

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

TABLES Parameters details for MESSAGE_HANDLING

P_ATPMSGX -

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

Copy and paste ABAP code example for MESSAGE_HANDLING 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_p_fcode  TYPE ATP00-ATPFC, "   
lt_p_atpmsgx  TYPE STANDARD TABLE OF ATPMSG. "   

  CALL FUNCTION 'MESSAGE_HANDLING'  "NOTRANSL: ATP-Server: Nachrichten-Verwaltung
    EXPORTING
         P_FCODE = lv_p_fcode
    TABLES
         P_ATPMSGX = lt_p_atpmsgx
. " MESSAGE_HANDLING




ABAP code using 7.40 inline data declarations to call FM MESSAGE_HANDLING

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 ATPFC FROM ATP00 INTO @DATA(ld_p_fcode).
 
 


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!