SAP ESH_INT_CONNECT_BACKEND Function Module for Connect backend system to appliance









ESH_INT_CONNECT_BACKEND is a standard esh int connect backend SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Connect backend system to appliance 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 esh int connect backend FM, simply by entering the name ESH_INT_CONNECT_BACKEND into the relevant SAP transaction such as SE37 or SE38.

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



Function ESH_INT_CONNECT_BACKEND 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 'ESH_INT_CONNECT_BACKEND'"Connect backend system to appliance
  EXPORTING
   IV_LOGSYS =  "Logical System
*  IV_STEXT =  "Description of RFC connection
   IV_LANGU =  "Language Key of Current Text Environment
   IV_CLIENT =  "Client
   IV_APPLSERVER =  "Name of target host
   IV_SYSTEMID =  "Name of the SAP System
   IV_SYSTEMNO =  "Transfer structure prefix for a source system
   IV_USER_NAME =  "User Name in User Master Record
   IV_PASSWORD =  "New password

 IMPORTING
   ET_RETURN_CODES =  "Table with BAPI Return Information
.



IMPORTING Parameters details for ESH_INT_CONNECT_BACKEND

IV_LOGSYS - Logical System

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

IV_STEXT - Description of RFC connection

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

IV_LANGU - Language Key of Current Text Environment

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

IV_CLIENT - Client

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

IV_APPLSERVER - Name of target host

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

IV_SYSTEMID - Name of the SAP System

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

IV_SYSTEMNO - Transfer structure prefix for a source system

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

IV_USER_NAME - User Name in User Master Record

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

IV_PASSWORD - New password

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

EXPORTING Parameters details for ESH_INT_CONNECT_BACKEND

ET_RETURN_CODES - Table with BAPI Return Information

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

Copy and paste ABAP code example for ESH_INT_CONNECT_BACKEND 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_iv_logsys  TYPE LOGSYS, "   
lv_et_return_codes  TYPE BAPIRETTAB, "   
lv_iv_stext  TYPE RFCDOC_D, "   
lv_iv_langu  TYPE SYLANGU, "   
lv_iv_client  TYPE MANDT, "   
lv_iv_applserver  TYPE RFCHOST, "   
lv_iv_systemid  TYPE SYSYSID, "   
lv_iv_systemno  TYPE RSTSPREFIX, "   
lv_iv_user_name  TYPE XUBNAME, "   
lv_iv_password  TYPE XUNCODE. "   

  CALL FUNCTION 'ESH_INT_CONNECT_BACKEND'  "Connect backend system to appliance
    EXPORTING
         IV_LOGSYS = lv_iv_logsys
         IV_STEXT = lv_iv_stext
         IV_LANGU = lv_iv_langu
         IV_CLIENT = lv_iv_client
         IV_APPLSERVER = lv_iv_applserver
         IV_SYSTEMID = lv_iv_systemid
         IV_SYSTEMNO = lv_iv_systemno
         IV_USER_NAME = lv_iv_user_name
         IV_PASSWORD = lv_iv_password
    IMPORTING
         ET_RETURN_CODES = lv_et_return_codes
. " ESH_INT_CONNECT_BACKEND




ABAP code using 7.40 inline data declarations to call FM ESH_INT_CONNECT_BACKEND

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



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!