SAP POPUP_FOR_INTERACTION Function Module for Dialog box (can be configured for various purposes)









POPUP_FOR_INTERACTION is a standard popup for interaction SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Dialog box (can be configured for various purposes) 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 popup for interaction FM, simply by entering the name POPUP_FOR_INTERACTION into the relevant SAP transaction such as SE37 or SE38.

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



Function POPUP_FOR_INTERACTION 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 'POPUP_FOR_INTERACTION'"Dialog box (can be configured for various purposes)
EXPORTING
HEADLINE = "
* BUTTON_2 = ' ' "
* BUTTON_3 = ' ' "
TEXT1 = "
* TEXT2 = ' ' "
* TEXT3 = ' ' "
* TEXT4 = ' ' "
* TEXT5 = ' ' "
* TEXT6 = ' ' "
* TICON = 'I' "
BUTTON_1 = "

IMPORTING
BUTTON_PRESSED = "
.



IMPORTING Parameters details for POPUP_FOR_INTERACTION

HEADLINE -

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

BUTTON_2 -

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

BUTTON_3 -

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

TEXT1 -

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

TEXT2 -

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

TEXT3 -

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

TEXT4 -

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

TEXT5 -

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

TEXT6 -

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

TICON -

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

BUTTON_1 -

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

EXPORTING Parameters details for POPUP_FOR_INTERACTION

BUTTON_PRESSED -

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

Copy and paste ABAP code example for POPUP_FOR_INTERACTION 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_headline  TYPE STRING, "   
lv_button_pressed  TYPE STRING, "   
lv_button_2  TYPE STRING, "   ' '
lv_button_3  TYPE STRING, "   ' '
lv_text1  TYPE STRING, "   
lv_text2  TYPE STRING, "   ' '
lv_text3  TYPE STRING, "   ' '
lv_text4  TYPE STRING, "   ' '
lv_text5  TYPE STRING, "   ' '
lv_text6  TYPE STRING, "   ' '
lv_ticon  TYPE STRING, "   'I'
lv_button_1  TYPE STRING. "   

  CALL FUNCTION 'POPUP_FOR_INTERACTION'  "Dialog box (can be configured for various purposes)
    EXPORTING
         HEADLINE = lv_headline
         BUTTON_2 = lv_button_2
         BUTTON_3 = lv_button_3
         TEXT1 = lv_text1
         TEXT2 = lv_text2
         TEXT3 = lv_text3
         TEXT4 = lv_text4
         TEXT5 = lv_text5
         TEXT6 = lv_text6
         TICON = lv_ticon
         BUTTON_1 = lv_button_1
    IMPORTING
         BUTTON_PRESSED = lv_button_pressed
. " POPUP_FOR_INTERACTION




ABAP code using 7.40 inline data declarations to call FM POPUP_FOR_INTERACTION

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.

 
 
DATA(ld_button_2) = ' '.
 
DATA(ld_button_3) = ' '.
 
 
DATA(ld_text2) = ' '.
 
DATA(ld_text3) = ' '.
 
DATA(ld_text4) = ' '.
 
DATA(ld_text5) = ' '.
 
DATA(ld_text6) = ' '.
 
DATA(ld_ticon) = 'I'.
 
 


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!