SAP POPUP_TO_CONFIRM_CUSTOMER Function Module for Dialog box to confirm customer assignment for data file; Application Mon.









POPUP_TO_CONFIRM_CUSTOMER is a standard popup to confirm customer 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 to confirm customer assignment for data file; Application Mon. 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 to confirm customer FM, simply by entering the name POPUP_TO_CONFIRM_CUSTOMER into the relevant SAP transaction such as SE37 or SE38.

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



Function POPUP_TO_CONFIRM_CUSTOMER 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_TO_CONFIRM_CUSTOMER'"Dialog box to confirm customer assignment for data file; Application Mon.
  EXPORTING
   BUKRS =  "Company code from EWDEBITORS
   TITEL =  "Title line of dialog box
   DATENFILE =  "ASCII - Data file
*  ENDX = 75 "
*  ENDY = 14 "
   FIRMENNAME =  "Short text from EWDEBITORS
   KDINFONR =  "Customer info number from EWDEBITORS
   KDNR =  "Customer number from EWDEBITORS
*  STARTX = 5 "
*  STARTY = 2 "

 IMPORTING
   ANSWER =  "selected answer of user
.



IMPORTING Parameters details for POPUP_TO_CONFIRM_CUSTOMER

BUKRS - Company code from EWDEBITORS

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

TITEL - Title line of dialog box

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

DATENFILE - ASCII - Data file

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

ENDX -

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

ENDY -

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

FIRMENNAME - Short text from EWDEBITORS

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

KDINFONR - Customer info number from EWDEBITORS

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

KDNR - Customer number from EWDEBITORS

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

STARTX -

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

STARTY -

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

EXPORTING Parameters details for POPUP_TO_CONFIRM_CUSTOMER

ANSWER - selected answer of user

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

Copy and paste ABAP code example for POPUP_TO_CONFIRM_CUSTOMER 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_bukrs  TYPE STRING, "   
lv_answer  TYPE STRING, "   
lv_titel  TYPE STRING, "   
lv_datenfile  TYPE STRING, "   
lv_endx  TYPE STRING, "   75
lv_endy  TYPE STRING, "   14
lv_firmenname  TYPE STRING, "   
lv_kdinfonr  TYPE STRING, "   
lv_kdnr  TYPE STRING, "   
lv_startx  TYPE STRING, "   5
lv_starty  TYPE STRING. "   2

  CALL FUNCTION 'POPUP_TO_CONFIRM_CUSTOMER'  "Dialog box to confirm customer assignment for data file; Application Mon.
    EXPORTING
         BUKRS = lv_bukrs
         TITEL = lv_titel
         DATENFILE = lv_datenfile
         ENDX = lv_endx
         ENDY = lv_endy
         FIRMENNAME = lv_firmenname
         KDINFONR = lv_kdinfonr
         KDNR = lv_kdnr
         STARTX = lv_startx
         STARTY = lv_starty
    IMPORTING
         ANSWER = lv_answer
. " POPUP_TO_CONFIRM_CUSTOMER




ABAP code using 7.40 inline data declarations to call FM POPUP_TO_CONFIRM_CUSTOMER

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_endx) = 75.
 
DATA(ld_endy) = 14.
 
 
 
 
DATA(ld_startx) = 5.
 
DATA(ld_starty) = 2.
 


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!