SAP CALL_EXIT_SAPLKLEX_002 Function Module for Capsule for User Exit for Derivation of Default Risk Rule









CALL_EXIT_SAPLKLEX_002 is a standard call exit saplklex 002 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Capsule for User Exit for Derivation of Default Risk Rule 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 call exit saplklex 002 FM, simply by entering the name CALL_EXIT_SAPLKLEX_002 into the relevant SAP transaction such as SE37 or SE38.

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



Function CALL_EXIT_SAPLKLEX_002 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 'CALL_EXIT_SAPLKLEX_002'"Capsule for User Exit for Derivation of Default Risk Rule
EXPORTING
I_DATE = "
I_STEP_ID = "
I_OBJECT = "
I_TEMP = "
I_FOB = "All FO Fields Relevant for Derivation of DRR

IMPORTING
E_OBJECT = "
E_TEMP = "
E_FOB = "All FO Fields Relevant for Derivation of DRR
E_EXIT_IS_ACTIVE = "
E_FAILED = "

EXCEPTIONS
DERIVATION_FAILED = 1
.



IMPORTING Parameters details for CALL_EXIT_SAPLKLEX_002

I_DATE -

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

I_STEP_ID -

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

I_OBJECT -

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

I_TEMP -

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

I_FOB - All FO Fields Relevant for Derivation of DRR

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

EXPORTING Parameters details for CALL_EXIT_SAPLKLEX_002

E_OBJECT -

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

E_TEMP -

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

E_FOB - All FO Fields Relevant for Derivation of DRR

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

E_EXIT_IS_ACTIVE -

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

E_FAILED -

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

EXCEPTIONS details

DERIVATION_FAILED -

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

Copy and paste ABAP code example for CALL_EXIT_SAPLKLEX_002 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_i_date  TYPE SY-DATUM, "   
lv_e_object  TYPE SY, "   
lv_derivation_failed  TYPE SY, "   
lv_e_temp  TYPE JBRTEMPDERI, "   
lv_i_step_id  TYPE TKEDRS-STEPID, "   
lv_e_fob  TYPE KLFODERIALL, "   
lv_i_object  TYPE KLFODERIALL, "   
lv_i_temp  TYPE JBRTEMPDERI, "   
lv_e_exit_is_active  TYPE JBRTEMPDERI, "   
lv_i_fob  TYPE KLFODERIALL, "   
lv_e_failed  TYPE KLFODERIALL. "   

  CALL FUNCTION 'CALL_EXIT_SAPLKLEX_002'  "Capsule for User Exit for Derivation of Default Risk Rule
    EXPORTING
         I_DATE = lv_i_date
         I_STEP_ID = lv_i_step_id
         I_OBJECT = lv_i_object
         I_TEMP = lv_i_temp
         I_FOB = lv_i_fob
    IMPORTING
         E_OBJECT = lv_e_object
         E_TEMP = lv_e_temp
         E_FOB = lv_e_fob
         E_EXIT_IS_ACTIVE = lv_e_exit_is_active
         E_FAILED = lv_e_failed
    EXCEPTIONS
        DERIVATION_FAILED = 1
. " CALL_EXIT_SAPLKLEX_002




ABAP code using 7.40 inline data declarations to call FM CALL_EXIT_SAPLKLEX_002

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.

"SELECT single DATUM FROM SY INTO @DATA(ld_i_date).
 
 
 
 
"SELECT single STEPID FROM TKEDRS INTO @DATA(ld_i_step_id).
 
 
 
 
 
 
 


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!