SAP GET_CHANGES_LONG_TEXT Function Module for NOTRANSL: PM: Abfrage über Änderungen an Langtexten
GET_CHANGES_LONG_TEXT is a standard get changes long text 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: PM: Abfrage über Änderungen an Langtexten 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 get changes long text FM, simply by entering the name GET_CHANGES_LONG_TEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: ITX1
Program Name: SAPLITX1
Main Program: SAPLITX1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_CHANGES_LONG_TEXT 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 'GET_CHANGES_LONG_TEXT'"NOTRANSL: PM: Abfrage über Änderungen an Langtexten.
EXPORTING
* I_OBJECT = "Texts: Application Object
* I_NAME = "Name
* I_ID = "Text ID
* I_SPRAS = "Language Key
TABLES
E_TEXT = "Help fields for the updating of texts
IMPORTING Parameters details for GET_CHANGES_LONG_TEXT
I_OBJECT - Texts: Application Object
Data type: STXH-TDOBJECTOptional: Yes
Call by Reference: Yes
I_NAME - Name
Data type: STXH-TDNAMEOptional: Yes
Call by Reference: Yes
I_ID - Text ID
Data type: STXH-TDIDOptional: Yes
Call by Reference: Yes
I_SPRAS - Language Key
Data type: STXH-TDSPRASOptional: Yes
Call by Reference: Yes
TABLES Parameters details for GET_CHANGES_LONG_TEXT
E_TEXT - Help fields for the updating of texts
Data type: PMTX_WORKOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for GET_CHANGES_LONG_TEXT 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_e_text | TYPE STANDARD TABLE OF PMTX_WORK, " | |||
| lv_i_object | TYPE STXH-TDOBJECT, " | |||
| lv_i_name | TYPE STXH-TDNAME, " | |||
| lv_i_id | TYPE STXH-TDID, " | |||
| lv_i_spras | TYPE STXH-TDSPRAS. " |
|   CALL FUNCTION 'GET_CHANGES_LONG_TEXT' "NOTRANSL: PM: Abfrage über Änderungen an Langtexten |
| EXPORTING | ||
| I_OBJECT | = lv_i_object | |
| I_NAME | = lv_i_name | |
| I_ID | = lv_i_id | |
| I_SPRAS | = lv_i_spras | |
| TABLES | ||
| E_TEXT | = lt_e_text | |
| . " GET_CHANGES_LONG_TEXT | ||
ABAP code using 7.40 inline data declarations to call FM GET_CHANGES_LONG_TEXT
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 TDOBJECT FROM STXH INTO @DATA(ld_i_object). | ||||
| "SELECT single TDNAME FROM STXH INTO @DATA(ld_i_name). | ||||
| "SELECT single TDID FROM STXH INTO @DATA(ld_i_id). | ||||
| "SELECT single TDSPRAS FROM STXH INTO @DATA(ld_i_spras). | ||||
Search for further information about these or an SAP related objects