SAP OIUP_RFC_TEST_DBCON Function Module for Test DB Connections
OIUP_RFC_TEST_DBCON is a standard oiup rfc test dbcon SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Test DB Connections 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 oiup rfc test dbcon FM, simply by entering the name OIUP_RFC_TEST_DBCON into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIUP_ADMIN_WORKBENCH
Program Name: SAPLOIUP_ADMIN_WORKBENCH
Main Program: SAPLOIUP_ADMIN_WORKBENCH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function OIUP_RFC_TEST_DBCON 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 'OIUP_RFC_TEST_DBCON'"Test DB Connections.
EXPORTING
DBCON = "DBCON name
TABNAME = "Table Name
EXCEPTIONS
DBCON_INVALID = 1
IMPORTING Parameters details for OIUP_RFC_TEST_DBCON
DBCON - DBCON name
Data type: DBCON_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABNAME - Table Name
Data type: TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DBCON_INVALID - DBCON Does not exist
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIUP_RFC_TEST_DBCON 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_dbcon | TYPE DBCON_NAME, " | |||
lv_dbcon_invalid | TYPE DBCON_NAME, " | |||
lv_tabname | TYPE TABNAME. " |
  CALL FUNCTION 'OIUP_RFC_TEST_DBCON' "Test DB Connections |
EXPORTING | ||
DBCON | = lv_dbcon | |
TABNAME | = lv_tabname | |
EXCEPTIONS | ||
DBCON_INVALID = 1 | ||
. " OIUP_RFC_TEST_DBCON |
ABAP code using 7.40 inline data declarations to call FM OIUP_RFC_TEST_DBCON
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