SAP EPS_ACCEPT_CONNECTION Function Module for









EPS_ACCEPT_CONNECTION is a standard eps accept connection 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 eps accept connection FM, simply by entering the name EPS_ACCEPT_CONNECTION into the relevant SAP transaction such as SE37 or SE38.

Function Group: EPSC
Program Name: SAPLEPSC
Main Program: SAPLEPSC
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function EPS_ACCEPT_CONNECTION 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 'EPS_ACCEPT_CONNECTION'"
EXPORTING
IV_CLIENT_ADDRESS = "
IV_SERVER_ADDRESS = "

EXCEPTIONS
INVALID_SERVER = 1 PERMISSION_DENIED = 2
.



IMPORTING Parameters details for EPS_ACCEPT_CONNECTION

IV_CLIENT_ADDRESS -

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

IV_SERVER_ADDRESS -

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

EXCEPTIONS details

INVALID_SERVER -

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

PERMISSION_DENIED -

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

Copy and paste ABAP code example for EPS_ACCEPT_CONNECTION 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_invalid_server  TYPE STRING, "   
lv_iv_client_address  TYPE WEPSC-EPSCLIENT, "   
lv_iv_server_address  TYPE WEPSC-EPSSERVER, "   
lv_permission_denied  TYPE WEPSC. "   

  CALL FUNCTION 'EPS_ACCEPT_CONNECTION'  "
    EXPORTING
         IV_CLIENT_ADDRESS = lv_iv_client_address
         IV_SERVER_ADDRESS = lv_iv_server_address
    EXCEPTIONS
        INVALID_SERVER = 1
        PERMISSION_DENIED = 2
. " EPS_ACCEPT_CONNECTION




ABAP code using 7.40 inline data declarations to call FM EPS_ACCEPT_CONNECTION

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 EPSCLIENT FROM WEPSC INTO @DATA(ld_iv_client_address).
 
"SELECT single EPSSERVER FROM WEPSC INTO @DATA(ld_iv_server_address).
 
 


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!