SAP FM_CHANGE_AA_HANA_DBCON_GET Function Module for









FM_CHANGE_AA_HANA_DBCON_GET is a standard fm change aa hana dbcon get 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 fm change aa hana dbcon get FM, simply by entering the name FM_CHANGE_AA_HANA_DBCON_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function FM_CHANGE_AA_HANA_DBCON_GET 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 'FM_CHANGE_AA_HANA_DBCON_GET'"
EXPORTING
* I_APPLICATION = "
* I_SUBAPPLICATION = ' ' "
* I_KEY_VALUE = ' ' "
* I_CHECK_CONNECTION = 'X' "
* I_REQUIRED_TABLE = "
* IT_PARAMETER = "
* I_UNAME = SY-UNAME "

IMPORTING
E_DBCON_NAME = "
ET_MESSAGE = "
E_HDB_IS_PRIMARY_DB = "

EXCEPTIONS
DBCON_NOT_EXIST = 1 DBCON_NO_USE = 2 DBCON_ERROR = 3 DBCON_OTHER = 4
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLFMCH_001 Determine FM Account Assignment from Coding Block
EXIT_SAPLFMCH_002 Own Table Updates During Reassignment
EXIT_SAPLFMCH_003 Change of Account Assignment, Reject Reassignment

IMPORTING Parameters details for FM_CHANGE_AA_HANA_DBCON_GET

I_APPLICATION -

Data type: HDB_APPLICATION
Optional: Yes
Call by Reference: Yes

I_SUBAPPLICATION -

Data type: HDB_SUBAPPLICATION
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_KEY_VALUE -

Data type: HDB_KEY_VALUE
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_CHECK_CONNECTION -

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_REQUIRED_TABLE -

Data type: TABNAME
Optional: Yes
Call by Reference: Yes

IT_PARAMETER -

Data type: HDB_T_PARAMETERS
Optional: Yes
Call by Reference: Yes

I_UNAME -

Data type: SY-UNAME
Default: SY-UNAME
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FM_CHANGE_AA_HANA_DBCON_GET

E_DBCON_NAME -

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

ET_MESSAGE -

Data type: BAPIRETTAB
Optional: No
Call by Reference: Yes

E_HDB_IS_PRIMARY_DB -

Data type: FLAG
Optional: No
Call by Reference: Yes

EXCEPTIONS details

DBCON_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

DBCON_NO_USE -

Data type:
Optional: No
Call by Reference: Yes

DBCON_ERROR -

Data type:
Optional: No
Call by Reference: Yes

DBCON_OTHER -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FM_CHANGE_AA_HANA_DBCON_GET 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_dbcon_other  TYPE FLAG, "   
lv_i_check_connection  TYPE FLAG, "   'X'
lv_i_required_table  TYPE TABNAME, "   
lv_it_parameter  TYPE HDB_T_PARAMETERS, "   
lv_i_uname  TYPE SY-UNAME. "   SY-UNAME

  CALL FUNCTION 'FM_CHANGE_AA_HANA_DBCON_GET'  "
    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
         I_REQUIRED_TABLE = lv_i_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
        DBCON_OTHER = 4
. " FM_CHANGE_AA_HANA_DBCON_GET




ABAP code using 7.40 inline data declarations to call FM FM_CHANGE_AA_HANA_DBCON_GET

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



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!