SAP HDB_DBCON_GET_APPL Function Module for Get HDB Connection for a Specific Context
HDB_DBCON_GET_APPL is a standard hdb dbcon get appl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get HDB Connection for a Specific Context 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 hdb dbcon get appl FM, simply by entering the name HDB_DBCON_GET_APPL into the relevant SAP transaction such as SE37 or SE38.
Function Group: HDB_SERVICE
Program Name: SAPLHDB_SERVICE
Main Program: SAPLHDB_SERVICE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HDB_DBCON_GET_APPL 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 'HDB_DBCON_GET_APPL'"Get HDB Connection for a Specific Context.
EXPORTING
* I_APPLICATION = "Application (Default: Cross application)
* I_SUBAPPLICATION = ' ' "Subapplication
* I_KEY_VALUE = ' ' "Key Value
* I_CHECK_CONNECTION = 'X' "Check connection to HDB
* IT_REQUIRED_TABLE = "Required tables and views for application context
* IT_PARAMETER = "Check additional Restrictions and Statuus
* I_UNAME = SY-UNAME "Check whether (batch) user is excluded in cross-application customizing
IMPORTING
E_DBCON_NAME = "Logical name for a database connection
ET_MESSAGE = "Table with BAPI Return Information
E_HDB_IS_PRIMARY_DB = "HDB is the primary DB
EXCEPTIONS
DBCON_NOT_EXIST = 1 DBCON_NO_USE = 2 DBCON_ERROR = 3
IMPORTING Parameters details for HDB_DBCON_GET_APPL
I_APPLICATION - Application (Default: Cross application)
Data type: HDB_APPLICATIONOptional: Yes
Call by Reference: Yes
I_SUBAPPLICATION - Subapplication
Data type: HDB_SUBAPPLICATIONDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_KEY_VALUE - Key Value
Data type: HDB_KEY_VALUEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_CHECK_CONNECTION - Check connection to HDB
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
IT_REQUIRED_TABLE - Required tables and views for application context
Data type: HDB_T_TABLEOptional: Yes
Call by Reference: Yes
IT_PARAMETER - Check additional Restrictions and Statuus
Data type: HDB_T_PARAMETERSOptional: Yes
Call by Reference: Yes
I_UNAME - Check whether (batch) user is excluded in cross-application customizing
Data type: SY-UNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for HDB_DBCON_GET_APPL
E_DBCON_NAME - Logical name for a database connection
Data type: DBCON_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGE - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: Yes
E_HDB_IS_PRIMARY_DB - HDB is the primary DB
Data type: FLAGOptional: No
Call by Reference: Yes
EXCEPTIONS details
DBCON_NOT_EXIST - HDB Connection Does Not Exist
Data type:Optional: No
Call by Reference: Yes
DBCON_NO_USE - HDB Connection should not be used in this context (see HDBC)
Data type:Optional: No
Call by Reference: Yes
DBCON_ERROR - HDB Connection Cannot be Reached or Used
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HDB_DBCON_GET_APPL 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_e_dbcon_name | TYPE DBCON_NAME, " | |||
| lv_i_application | TYPE HDB_APPLICATION, " | |||
| lv_dbcon_not_exist | TYPE HDB_APPLICATION, " | |||
| lv_et_message | TYPE BAPIRETTAB, " | |||
| lv_dbcon_no_use | TYPE BAPIRETTAB, " | |||
| lv_i_subapplication | TYPE HDB_SUBAPPLICATION, " SPACE | |||
| lv_dbcon_error | TYPE HDB_SUBAPPLICATION, " | |||
| lv_i_key_value | TYPE HDB_KEY_VALUE, " SPACE | |||
| lv_e_hdb_is_primary_db | TYPE FLAG, " | |||
| lv_i_check_connection | TYPE FLAG, " 'X' | |||
| lv_it_required_table | TYPE HDB_T_TABLE, " | |||
| lv_it_parameter | TYPE HDB_T_PARAMETERS, " | |||
| lv_i_uname | TYPE SY-UNAME. " SY-UNAME |
|   CALL FUNCTION 'HDB_DBCON_GET_APPL' "Get HDB Connection for a Specific Context |
| EXPORTING | ||
| I_APPLICATION | = lv_i_application | |
| I_SUBAPPLICATION | = lv_i_subapplication | |
| I_KEY_VALUE | = lv_i_key_value | |
| I_CHECK_CONNECTION | = lv_i_check_connection | |
| IT_REQUIRED_TABLE | = lv_it_required_table | |
| IT_PARAMETER | = lv_it_parameter | |
| I_UNAME | = lv_i_uname | |
| IMPORTING | ||
| E_DBCON_NAME | = lv_e_dbcon_name | |
| ET_MESSAGE | = lv_et_message | |
| E_HDB_IS_PRIMARY_DB | = lv_e_hdb_is_primary_db | |
| EXCEPTIONS | ||
| DBCON_NOT_EXIST = 1 | ||
| DBCON_NO_USE = 2 | ||
| DBCON_ERROR = 3 | ||
| . " HDB_DBCON_GET_APPL | ||
ABAP code using 7.40 inline data declarations to call FM HDB_DBCON_GET_APPL
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_subapplication) | = ' '. | |||
| DATA(ld_i_key_value) | = ' '. | |||
| DATA(ld_i_check_connection) | = 'X'. | |||
| "SELECT single UNAME FROM SY INTO @DATA(ld_i_uname). | ||||
| DATA(ld_i_uname) | = SY-UNAME. | |||
Search for further information about these or an SAP related objects