SAP KL_EXT_GET_CR_FLAG_FROM_EV Function Module for return country risk flag for a specific det proc
KL_EXT_GET_CR_FLAG_FROM_EV is a standard kl ext get cr flag from ev SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for return country risk flag for a specific det proc 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 kl ext get cr flag from ev FM, simply by entering the name KL_EXT_GET_CR_FLAG_FROM_EV into the relevant SAP transaction such as SE37 or SE38.
Function Group: KLEXT
Program Name: SAPLKLEXT
Main Program: SAPLKLEXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function KL_EXT_GET_CR_FLAG_FROM_EV 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 'KL_EXT_GET_CR_FLAG_FROM_EV'"return country risk flag for a specific det proc.
EXPORTING
I_EV = "Determination Procedure
IMPORTING
E_COUNTRY_RISK = "Checkbox
IMPORTING Parameters details for KL_EXT_GET_CR_FLAG_FROM_EV
I_EV - Determination Procedure
Data type: KLEVDEF-ERMVERFOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for KL_EXT_GET_CR_FLAG_FROM_EV
E_COUNTRY_RISK - Checkbox
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for KL_EXT_GET_CR_FLAG_FROM_EV 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_ev | TYPE KLEVDEF-ERMVERF, " | |||
| lv_e_country_risk | TYPE XFELD. " |
|   CALL FUNCTION 'KL_EXT_GET_CR_FLAG_FROM_EV' "return country risk flag for a specific det proc |
| EXPORTING | ||
| I_EV | = lv_i_ev | |
| IMPORTING | ||
| E_COUNTRY_RISK | = lv_e_country_risk | |
| . " KL_EXT_GET_CR_FLAG_FROM_EV | ||
ABAP code using 7.40 inline data declarations to call FM KL_EXT_GET_CR_FLAG_FROM_EV
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 ERMVERF FROM KLEVDEF INTO @DATA(ld_i_ev). | ||||
Search for further information about these or an SAP related objects