SAP FP_ADS_CONNECTIVITY Function Module for Check ADS Connectivity









FP_ADS_CONNECTIVITY is a standard fp ads connectivity SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check ADS Connectivity 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 fp ads connectivity FM, simply by entering the name FP_ADS_CONNECTIVITY into the relevant SAP transaction such as SE37 or SE38.

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



Function FP_ADS_CONNECTIVITY 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 'FP_ADS_CONNECTIVITY'"Check ADS Connectivity
  EXPORTING
*  I_RFC_DESTINATION = ' ' "Logical destination (specified in function call)
*  I_LOGICAL_PORT = ' ' "Logical Port Name
*  I_SYSINFO = 'X' "Get System Info
*  I_LPORT_INFO = 'X' "Collect LP Info
*  I_RFC_INFO = 'X' "Collect RFC Info
*  I_CHECK_LOGON = 'X' "Check the logon data was mounted

CHANGING
*  ERRORS =  "Table of processing errors
*  PORTS =  "Table of logical ports
*  RFCS =  "Table of RFC destinations
*  SYS_INFO =  "Cloud system description
.



IMPORTING Parameters details for FP_ADS_CONNECTIVITY

I_RFC_DESTINATION - Logical destination (specified in function call)

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

I_LOGICAL_PORT - Logical Port Name

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

I_SYSINFO - Get System Info

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

I_LPORT_INFO - Collect LP Info

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

I_RFC_INFO - Collect RFC Info

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

I_CHECK_LOGON - Check the logon data was mounted

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

CHANGING Parameters details for FP_ADS_CONNECTIVITY

ERRORS - Table of processing errors

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

PORTS - Table of logical ports

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

RFCS - Table of RFC destinations

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

SYS_INFO - Cloud system description

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

Copy and paste ABAP code example for FP_ADS_CONNECTIVITY 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_errors  TYPE TPERRORS, "   
lv_i_rfc_destination  TYPE RFCDEST, "   ' '
lv_ports  TYPE TLPORTS, "   
lv_i_logical_port  TYPE PRX_LOGICAL_PORT_NAME, "   ' '
lv_rfcs  TYPE TLRFC, "   
lv_i_sysinfo  TYPE FLAG, "   'X'
lv_sys_info  TYPE CSYS_INFO, "   
lv_i_lport_info  TYPE FLAG, "   'X'
lv_i_rfc_info  TYPE FLAG, "   'X'
lv_i_check_logon  TYPE FLAG. "   'X'

  CALL FUNCTION 'FP_ADS_CONNECTIVITY'  "Check ADS Connectivity
    EXPORTING
         I_RFC_DESTINATION = lv_i_rfc_destination
         I_LOGICAL_PORT = lv_i_logical_port
         I_SYSINFO = lv_i_sysinfo
         I_LPORT_INFO = lv_i_lport_info
         I_RFC_INFO = lv_i_rfc_info
         I_CHECK_LOGON = lv_i_check_logon
    CHANGING
         ERRORS = lv_errors
         PORTS = lv_ports
         RFCS = lv_rfcs
         SYS_INFO = lv_sys_info
. " FP_ADS_CONNECTIVITY




ABAP code using 7.40 inline data declarations to call FM FP_ADS_CONNECTIVITY

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_i_rfc_destination) = ' '.
 
 
DATA(ld_i_logical_port) = ' '.
 
 
DATA(ld_i_sysinfo) = 'X'.
 
 
DATA(ld_i_lport_info) = 'X'.
 
DATA(ld_i_rfc_info) = 'X'.
 
DATA(ld_i_check_logon) = 'X'.
 


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!