SAP CN_LDST_CHANGES_GET Function Module for NOTRANSL: Rückgabe ob Änderungen vorgenommen wurden
CN_LDST_CHANGES_GET is a standard cn ldst changes get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Rückgabe ob Änderungen vorgenommen wurden 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 cn ldst changes get FM, simply by entering the name CN_LDST_CHANGES_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: CN_LDST
Program Name: SAPLCN_LDST
Main Program: SAPLCN_LDST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CN_LDST_CHANGES_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 'CN_LDST_CHANGES_GET'"NOTRANSL: Rückgabe ob Änderungen vorgenommen wurden.
EXPORTING
IV_APPLICATION = "Application of Language-Dependent Short Texts
IV_OBJECT = "Indicator for Object Type
IMPORTING
EV_CHANGES = "
IMPORTING Parameters details for CN_LDST_CHANGES_GET
IV_APPLICATION - Application of Language-Dependent Short Texts
Data type: CNLDST_APPLICOptional: No
Call by Reference: Yes
IV_OBJECT - Indicator for Object Type
Data type: CNLDST_OBJECTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CN_LDST_CHANGES_GET
EV_CHANGES -
Data type: CHAR1Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CN_LDST_CHANGES_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_ev_changes | TYPE CHAR1, " | |||
| lv_iv_application | TYPE CNLDST_APPLIC, " | |||
| lv_iv_object | TYPE CNLDST_OBJECT. " |
|   CALL FUNCTION 'CN_LDST_CHANGES_GET' "NOTRANSL: Rückgabe ob Änderungen vorgenommen wurden |
| EXPORTING | ||
| IV_APPLICATION | = lv_iv_application | |
| IV_OBJECT | = lv_iv_object | |
| IMPORTING | ||
| EV_CHANGES | = lv_ev_changes | |
| . " CN_LDST_CHANGES_GET | ||
ABAP code using 7.40 inline data declarations to call FM CN_LDST_CHANGES_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.Search for further information about these or an SAP related objects