SAP KAEPX_SET_DB_SETTINGS Function Module for









KAEPX_SET_DB_SETTINGS is a standard kaepx set db settings 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 kaepx set db settings FM, simply by entering the name KAEPX_SET_DB_SETTINGS into the relevant SAP transaction such as SE37 or SE38.

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



Function KAEPX_SET_DB_SETTINGS 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 'KAEPX_SET_DB_SETTINGS'"
CHANGING
IT_KAEPX_DATA_CARRIER = "

TABLES
* IT_DISPLAY = "

EXCEPTIONS
MISSING_INPUT = 1 WRONG_TABLE = 2
.



CHANGING Parameters details for KAEPX_SET_DB_SETTINGS

IT_KAEPX_DATA_CARRIER -

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

TABLES Parameters details for KAEPX_SET_DB_SETTINGS

IT_DISPLAY -

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

EXCEPTIONS details

MISSING_INPUT -

Data type:
Optional: No
Call by Reference: Yes

WRONG_TABLE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for KAEPX_SET_DB_SETTINGS 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:
lt_it_display  TYPE STANDARD TABLE OF SE16N_OUTPUT, "   
lv_missing_input  TYPE SE16N_OUTPUT, "   
lv_it_kaepx_data_carrier  TYPE KAEPX_DATA_CARRIER_T, "   
lv_wrong_table  TYPE KAEPX_DATA_CARRIER_T. "   

  CALL FUNCTION 'KAEPX_SET_DB_SETTINGS'  "
    CHANGING
         IT_KAEPX_DATA_CARRIER = lv_it_kaepx_data_carrier
    TABLES
         IT_DISPLAY = lt_it_display
    EXCEPTIONS
        MISSING_INPUT = 1
        WRONG_TABLE = 2
. " KAEPX_SET_DB_SETTINGS




ABAP code using 7.40 inline data declarations to call FM KAEPX_SET_DB_SETTINGS

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



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!