SAP INS_DBCON_ENTRY_SDB Function Module for









INS_DBCON_ENTRY_SDB is a standard ins dbcon entry sdb 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 ins dbcon entry sdb FM, simply by entering the name INS_DBCON_ENTRY_SDB into the relevant SAP transaction such as SE37 or SE38.

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



Function INS_DBCON_ENTRY_SDB 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 'INS_DBCON_ENTRY_SDB'"
EXPORTING
CON_NAME = "Logical Name for a Database Connection
* DBMS = 'ADA' "Database System
USER_NAME = "Database user
PASSWORD = "Password for setting up the connection to the database
LC_NAME = "Logical Name for a Database Connection
LC_SERVER = "Name of target host
* DB_RECO = "Availability type for an open database connect

EXCEPTIONS
NO_PERMISSION = 1 CRYPT_PASSWORD_ERROR = 2 ENTRY_ALREADY_EXISTS = 3 INSERT_DBCON_ERROR = 4 SECURE_STORE_KEY_EXISTS = 5 NAME_TOO_LONG = 6
.



IMPORTING Parameters details for INS_DBCON_ENTRY_SDB

CON_NAME - Logical Name for a Database Connection

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

DBMS - Database System

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

USER_NAME - Database user

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

PASSWORD - Password for setting up the connection to the database

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

LC_NAME - Logical Name for a Database Connection

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

LC_SERVER - Name of target host

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

DB_RECO - Availability type for an open database connect

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

EXCEPTIONS details

NO_PERMISSION -

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

CRYPT_PASSWORD_ERROR -

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

ENTRY_ALREADY_EXISTS -

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

INSERT_DBCON_ERROR -

Data type:
Optional: No
Call by Reference: Yes

SECURE_STORE_KEY_EXISTS -

Data type:
Optional: No
Call by Reference: Yes

NAME_TOO_LONG -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for INS_DBCON_ENTRY_SDB 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_con_name  TYPE DBCON_NAME, "   
lv_no_permission  TYPE DBCON_NAME, "   
lv_dbms  TYPE DBCON_DBMS, "   'ADA'
lv_crypt_password_error  TYPE DBCON_DBMS, "   
lv_user_name  TYPE DBCON_UID, "   
lv_entry_already_exists  TYPE DBCON_UID, "   
lv_password  TYPE CHAR30, "   
lv_insert_dbcon_error  TYPE CHAR30, "   
lv_lc_name  TYPE DBCON-CON_NAME, "   
lv_secure_store_key_exists  TYPE DBCON, "   
lv_lc_server  TYPE RFCDISPLAY-RFCHOST, "   
lv_name_too_long  TYPE RFCDISPLAY, "   
lv_db_reco  TYPE DBCON_RECO. "   

  CALL FUNCTION 'INS_DBCON_ENTRY_SDB'  "
    EXPORTING
         CON_NAME = lv_con_name
         DBMS = lv_dbms
         USER_NAME = lv_user_name
         PASSWORD = lv_password
         LC_NAME = lv_lc_name
         LC_SERVER = lv_lc_server
         DB_RECO = lv_db_reco
    EXCEPTIONS
        NO_PERMISSION = 1
        CRYPT_PASSWORD_ERROR = 2
        ENTRY_ALREADY_EXISTS = 3
        INSERT_DBCON_ERROR = 4
        SECURE_STORE_KEY_EXISTS = 5
        NAME_TOO_LONG = 6
. " INS_DBCON_ENTRY_SDB




ABAP code using 7.40 inline data declarations to call FM INS_DBCON_ENTRY_SDB

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_dbms) = 'ADA'.
 
 
 
 
 
 
"SELECT single CON_NAME FROM DBCON INTO @DATA(ld_lc_name).
 
 
"SELECT single RFCHOST FROM RFCDISPLAY INTO @DATA(ld_lc_server).
 
 
 


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!