SAP SX2_TRACE_WRITE_ACTIONMSG Function Module for









SX2_TRACE_WRITE_ACTIONMSG is a standard sx2 trace write actionmsg 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 sx2 trace write actionmsg FM, simply by entering the name SX2_TRACE_WRITE_ACTIONMSG into the relevant SAP transaction such as SE37 or SE38.

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



Function SX2_TRACE_WRITE_ACTIONMSG 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 'SX2_TRACE_WRITE_ACTIONMSG'"
EXPORTING
IM_1 = "ID of the calling workflow module
IM_2 = "Logged Action in Workflow Trace
IM_3 = "Messages, Message Class
IM_4 = "Messages, Message Type
IM_5 = "Messages, Message Number
IM_6 = "
IM_7 = "
IM_8 = "
IM_9 = "
.



IMPORTING Parameters details for SX2_TRACE_WRITE_ACTIONMSG

IM_1 - ID of the calling workflow module

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

IM_2 - Logged Action in Workflow Trace

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

IM_3 - Messages, Message Class

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

IM_4 - Messages, Message Type

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

IM_5 - Messages, Message Number

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

IM_6 -

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

IM_7 -

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

IM_8 -

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

IM_9 -

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

Copy and paste ABAP code example for SX2_TRACE_WRITE_ACTIONMSG 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_im_1  TYPE SWT_LOG-OWNMODID, "   
lv_im_2  TYPE SWT_LOG-TACTION, "   
lv_im_3  TYPE SWAERROR-MSGID, "   
lv_im_4  TYPE SWAERROR-MSGTY, "   
lv_im_5  TYPE SWAERROR-MSGNO, "   
lv_im_6  TYPE ANY, "   
lv_im_7  TYPE ANY, "   
lv_im_8  TYPE ANY, "   
lv_im_9  TYPE ANY. "   

  CALL FUNCTION 'SX2_TRACE_WRITE_ACTIONMSG'  "
    EXPORTING
         IM_1 = lv_im_1
         IM_2 = lv_im_2
         IM_3 = lv_im_3
         IM_4 = lv_im_4
         IM_5 = lv_im_5
         IM_6 = lv_im_6
         IM_7 = lv_im_7
         IM_8 = lv_im_8
         IM_9 = lv_im_9
. " SX2_TRACE_WRITE_ACTIONMSG




ABAP code using 7.40 inline data declarations to call FM SX2_TRACE_WRITE_ACTIONMSG

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 OWNMODID FROM SWT_LOG INTO @DATA(ld_im_1).
 
"SELECT single TACTION FROM SWT_LOG INTO @DATA(ld_im_2).
 
"SELECT single MSGID FROM SWAERROR INTO @DATA(ld_im_3).
 
"SELECT single MSGTY FROM SWAERROR INTO @DATA(ld_im_4).
 
"SELECT single MSGNO FROM SWAERROR INTO @DATA(ld_im_5).
 
 
 
 
 


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!