SAP /MAP/D_SELECTION_SCREEN_RFC Function Module for

Search SAP Function Modules

/MAP/D_SELECTION_SCREEN_RFC is a standard /map/d selection screen rfc 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 /map/d selection screen rfc FM, simply by entering the name /MAP/D_SELECTION_SCREEN_RFC into the relevant SAP transaction such as SE37 or SE38.

Function Group: /MAP/D_FG_EM01
Program Name: /MAP/SAPLD_FG_EM01
Main Program: /MAP/SAPLD_FG_EM01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /MAP/D_SELECTION_SCREEN_RFC 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 '/MAP/D_SELECTION_SCREEN_RFC'"
  EXPORTING
   IS_EVENTINFO =  "

 IMPORTING
   ETO_CHASEL_EVOCCUR =  "
   ETO_CHASEL_LOC =  "
   ETO_CHASEL_PROD1 =  "
   ETO_CHASEL_PROD2 =  "
   ETO_CHASEL_PROD3 =  "
   E_CANCEL =  "

EXCEPTIONS
   EVDIM_NOT_EXIST = 1    IOBJ_ERROR = 2    GENERAL_ERROR = 3 

.

IMPORTING Parameters details for /MAP/D_SELECTION_SCREEN_RFC

IS_EVENTINFO -

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

EXPORTING Parameters details for /MAP/D_SELECTION_SCREEN_RFC

ETO_CHASEL_EVOCCUR -

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

ETO_CHASEL_LOC -

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

ETO_CHASEL_PROD1 -

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

ETO_CHASEL_PROD2 -

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

ETO_CHASEL_PROD3 -

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

E_CANCEL -

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

EXCEPTIONS details

EVDIM_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

IOBJ_ERROR -

Data type:
Optional: No
Call by Reference: Yes

GENERAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for /MAP/D_SELECTION_SCREEN_RFC 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.

ABAP code using 7.40 inline data declarations to call FM /MAP/D_SELECTION_SCREEN_RFC

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