SAP ISU_IDE_TLS_DSPL_MSG_ADD Function Module for Fill Table and Output Structure IDE_TLS_DSPL_MESSAGE









ISU_IDE_TLS_DSPL_MSG_ADD is a standard isu ide tls dspl msg add SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fill Table and Output Structure IDE_TLS_DSPL_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 isu ide tls dspl msg add FM, simply by entering the name ISU_IDE_TLS_DSPL_MSG_ADD into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_IDE_TLS_DSPL_MSG_ADD 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_IDE_TLS_DSPL_MSG_ADD'"Fill Table and Output Structure IDE_TLS_DSPL_MESSAGE
  EXPORTING
*  X_CHKKEY =  "Check Framework - Objects for Check Variant
*  X_ICON =  "Icon in Text Fields (Substitute Display, Alias)
*  X_FIELD_NAME =  "Field in Parameter
*  X_FIELD_VALUE =  "
*  X_MSGV1_FIELD_NAME =  "Application Log: Parameters
*  X_MSGV2_FIELD_NAME =  "Application Log: Parameters
*  X_MSGV3_FIELD_NAME =  "Application Log: Parameters
*  X_MSGV4_FIELD_NAME =  "Application Log: Parameters
*  X_DEFAULT_HOTSPOT =  "Default Hotspot

CHANGING
*  XY_MSG_LINE =  "Output Structure for General Status Display with BAPIRET2
   XYT_MSG =  "Table Type for IDE_TLS_DSPL_MESSAGE
.



IMPORTING Parameters details for ISU_IDE_TLS_DSPL_MSG_ADD

X_CHKKEY - Check Framework - Objects for Check Variant

Data type: EDR_CHKVAR_DATA
Optional: Yes
Call by Reference: Yes

X_ICON - Icon in Text Fields (Substitute Display, Alias)

Data type: ICON_D
Optional: Yes
Call by Reference: Yes

X_FIELD_NAME - Field in Parameter

Data type: BAPI_FLD
Optional: Yes
Call by Reference: Yes

X_FIELD_VALUE -

Data type: ANY
Optional: Yes
Call by Reference: Yes

X_MSGV1_FIELD_NAME - Application Log: Parameters

Data type: BAPI_FLD
Optional: Yes
Call by Reference: Yes

X_MSGV2_FIELD_NAME - Application Log: Parameters

Data type: BAPI_FLD
Optional: Yes
Call by Reference: Yes

X_MSGV3_FIELD_NAME - Application Log: Parameters

Data type: BAPI_FLD
Optional: Yes
Call by Reference: Yes

X_MSGV4_FIELD_NAME - Application Log: Parameters

Data type: BAPI_FLD
Optional: Yes
Call by Reference: Yes

X_DEFAULT_HOTSPOT - Default Hotspot

Data type: IDE_TLS_DSPL_MSG_DFLT_HTSPT
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for ISU_IDE_TLS_DSPL_MSG_ADD

XY_MSG_LINE - Output Structure for General Status Display with BAPIRET2

Data type: IDE_TLS_DSPL_MESSAGE
Optional: Yes
Call by Reference: Yes

XYT_MSG - Table Type for IDE_TLS_DSPL_MESSAGE

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

Copy and paste ABAP code example for ISU_IDE_TLS_DSPL_MSG_ADD 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_chkkey  TYPE EDR_CHKVAR_DATA, "   
lv_xy_msg_line  TYPE IDE_TLS_DSPL_MESSAGE, "   
lv_x_icon  TYPE ICON_D, "   
lv_xyt_msg  TYPE IDE_TLS_DSPL_MESSAGE_T, "   
lv_x_field_name  TYPE BAPI_FLD, "   
lv_x_field_value  TYPE ANY, "   
lv_x_msgv1_field_name  TYPE BAPI_FLD, "   
lv_x_msgv2_field_name  TYPE BAPI_FLD, "   
lv_x_msgv3_field_name  TYPE BAPI_FLD, "   
lv_x_msgv4_field_name  TYPE BAPI_FLD, "   
lv_x_default_hotspot  TYPE IDE_TLS_DSPL_MSG_DFLT_HTSPT. "   

  CALL FUNCTION 'ISU_IDE_TLS_DSPL_MSG_ADD'  "Fill Table and Output Structure IDE_TLS_DSPL_MESSAGE
    EXPORTING
         X_CHKKEY = lv_x_chkkey
         X_ICON = lv_x_icon
         X_FIELD_NAME = lv_x_field_name
         X_FIELD_VALUE = lv_x_field_value
         X_MSGV1_FIELD_NAME = lv_x_msgv1_field_name
         X_MSGV2_FIELD_NAME = lv_x_msgv2_field_name
         X_MSGV3_FIELD_NAME = lv_x_msgv3_field_name
         X_MSGV4_FIELD_NAME = lv_x_msgv4_field_name
         X_DEFAULT_HOTSPOT = lv_x_default_hotspot
    CHANGING
         XY_MSG_LINE = lv_xy_msg_line
         XYT_MSG = lv_xyt_msg
. " ISU_IDE_TLS_DSPL_MSG_ADD




ABAP code using 7.40 inline data declarations to call FM ISU_IDE_TLS_DSPL_MSG_ADD

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.

 
 
 
 
 
 
 
 
 
 
 


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!