SAP LXE_SC_POPUP_CALL_POPUP Function Module for call correction popup









LXE_SC_POPUP_CALL_POPUP is a standard lxe sc popup call popup SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for call correction popup 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 lxe sc popup call popup FM, simply by entering the name LXE_SC_POPUP_CALL_POPUP into the relevant SAP transaction such as SE37 or SE38.

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



Function LXE_SC_POPUP_CALL_POPUP 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 'LXE_SC_POPUP_CALL_POPUP'"call correction popup
  EXPORTING
   TEXT =  "
*  TEXT_MAX_LENGTH =  "Lenght restriction for text (0 or initial means no restriction)
   SUGGESTIONS =  "SpellChecker: spelling errors and suggestions
   LANGUAGE =  "Translation Language
*  SHOW_SEQ_PROC_FWD_BUTTON =  "Display button for sequential fwd processing (several texts)
*  SHOW_SEQ_PROC_BWD_BUTTON =  "Display button for sequential bwd processing (several texts)
*  LINEBREAKS_OK = ABAP_FALSE "linebreaks in text ok or display warning

 IMPORTING
   CORRECTED_TEXT =  "
   SPELLING_EXCEPTIONS =  "Table of Strings, e.g. for spelling error exceptions
   BUTTON =  "Function Code that Triggered PAI
.



IMPORTING Parameters details for LXE_SC_POPUP_CALL_POPUP

TEXT -

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

TEXT_MAX_LENGTH - Lenght restriction for text (0 or initial means no restriction)

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

SUGGESTIONS - SpellChecker: spelling errors and suggestions

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

LANGUAGE - Translation Language

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

SHOW_SEQ_PROC_FWD_BUTTON - Display button for sequential fwd processing (several texts)

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

SHOW_SEQ_PROC_BWD_BUTTON - Display button for sequential bwd processing (several texts)

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

LINEBREAKS_OK - linebreaks in text ok or display warning

Data type: BOOLEAN
Default: ABAP_FALSE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for LXE_SC_POPUP_CALL_POPUP

CORRECTED_TEXT -

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

SPELLING_EXCEPTIONS - Table of Strings, e.g. for spelling error exceptions

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

BUTTON - Function Code that Triggered PAI

Data type: SY-UCOMM
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for LXE_SC_POPUP_CALL_POPUP 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_text  TYPE STRING, "   
lv_corrected_text  TYPE STRING, "   
lv_text_max_length  TYPE I, "   
lv_spelling_exceptions  TYPE LXE_SC_T_STRINGS, "   
lv_button  TYPE SY-UCOMM, "   
lv_suggestions  TYPE LXE_SC_T_ERROR_SUGGESTIONS, "   
lv_language  TYPE LXEISOLANG, "   
lv_show_seq_proc_fwd_button  TYPE BOOLEAN, "   
lv_show_seq_proc_bwd_button  TYPE BOOLEAN, "   
lv_linebreaks_ok  TYPE BOOLEAN. "   ABAP_FALSE

  CALL FUNCTION 'LXE_SC_POPUP_CALL_POPUP'  "call correction popup
    EXPORTING
         TEXT = lv_text
         TEXT_MAX_LENGTH = lv_text_max_length
         SUGGESTIONS = lv_suggestions
         LANGUAGE = lv_language
         SHOW_SEQ_PROC_FWD_BUTTON = lv_show_seq_proc_fwd_button
         SHOW_SEQ_PROC_BWD_BUTTON = lv_show_seq_proc_bwd_button
         LINEBREAKS_OK = lv_linebreaks_ok
    IMPORTING
         CORRECTED_TEXT = lv_corrected_text
         SPELLING_EXCEPTIONS = lv_spelling_exceptions
         BUTTON = lv_button
. " LXE_SC_POPUP_CALL_POPUP




ABAP code using 7.40 inline data declarations to call FM LXE_SC_POPUP_CALL_POPUP

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 UCOMM FROM SY INTO @DATA(ld_button).
 
 
 
 
 
DATA(ld_linebreaks_ok) = ABAP_FALSE.
 


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!