SAP KL_EXT_CHECK_CHANGES Function Module for check Änderungen
KL_EXT_CHECK_CHANGES is a standard kl ext check changes SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for check Änderungen 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 check changes FM, simply by entering the name KL_EXT_CHECK_CHANGES 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_CHECK_CHANGES 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_CHECK_CHANGES'"check Änderungen.
EXPORTING
I_OBJNR = "Object Number for Financial Transactions
I_SLA = "Limit Type
IMPORTING
E_NEW_LIMIT_EXCEEDED = "Individual, user-defined character
IMPORTING Parameters details for KL_EXT_CHECK_CHANGES
I_OBJNR - Object Number for Financial Transactions
Data type: JBOBJNROptional: No
Call by Reference: Yes
I_SLA - Limit Type
Data type: TB_SLAOptional: No
Call by Reference: Yes
EXPORTING Parameters details for KL_EXT_CHECK_CHANGES
E_NEW_LIMIT_EXCEEDED - Individual, user-defined character
Data type: DATATYPE-CHAR0001Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for KL_EXT_CHECK_CHANGES 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_objnr | TYPE JBOBJNR, " | |||
| lv_e_new_limit_exceeded | TYPE DATATYPE-CHAR0001, " | |||
| lv_i_sla | TYPE TB_SLA. " |
|   CALL FUNCTION 'KL_EXT_CHECK_CHANGES' "check Änderungen |
| EXPORTING | ||
| I_OBJNR | = lv_i_objnr | |
| I_SLA | = lv_i_sla | |
| IMPORTING | ||
| E_NEW_LIMIT_EXCEEDED | = lv_e_new_limit_exceeded | |
| . " KL_EXT_CHECK_CHANGES | ||
ABAP code using 7.40 inline data declarations to call FM KL_EXT_CHECK_CHANGES
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 CHAR0001 FROM DATATYPE INTO @DATA(ld_e_new_limit_exceeded). | ||||
Search for further information about these or an SAP related objects