SAP ISU_EDATEX_TASK_MSG_OPEN Function Module for









ISU_EDATEX_TASK_MSG_OPEN is a standard isu edatex task msg open 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 isu edatex task msg open FM, simply by entering the name ISU_EDATEX_TASK_MSG_OPEN into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_EDATEX_TASK_MSG_OPEN 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 'ISU_EDATEX_TASK_MSG_OPEN'"
EXPORTING
X_APPL_LOG = "Application Log: Object Name (Application Code)

IMPORTING
Y_MSG_HANDLE = "Message object identification
.



IMPORTING Parameters details for ISU_EDATEX_TASK_MSG_OPEN

X_APPL_LOG - Application Log: Object Name (Application Code)

Data type: BALHDR-OBJECT
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ISU_EDATEX_TASK_MSG_OPEN

Y_MSG_HANDLE - Message object identification

Data type: EMSG_HANDL
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_EDATEX_TASK_MSG_OPEN 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_x_appl_log  TYPE BALHDR-OBJECT, "   
lv_y_msg_handle  TYPE EMSG_HANDL. "   

  CALL FUNCTION 'ISU_EDATEX_TASK_MSG_OPEN'  "
    EXPORTING
         X_APPL_LOG = lv_x_appl_log
    IMPORTING
         Y_MSG_HANDLE = lv_y_msg_handle
. " ISU_EDATEX_TASK_MSG_OPEN




ABAP code using 7.40 inline data declarations to call FM ISU_EDATEX_TASK_MSG_OPEN

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 OBJECT FROM BALHDR INTO @DATA(ld_x_appl_log).
 
 


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!