SAP TEXT_MAINTENANCE Function Module for Maintenance of Texts for Maintenance Objects
TEXT_MAINTENANCE is a standard text maintenance SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Maintenance of Texts for Maintenance Objects 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 text maintenance FM, simply by entering the name TEXT_MAINTENANCE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ITX1
Program Name: SAPLITX1
Main Program: SAPLITX1
Appliation area: I
Release date: 31-Jan-1995
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TEXT_MAINTENANCE 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 'TEXT_MAINTENANCE'"Maintenance of Texts for Maintenance Objects.
EXPORTING
* EQTYP = ' ' "Equipment category (only for equip.)
X_XAKTYP = "Activity Category
* INIT = 'X' "Indicator showing whether call is for the first time
* MTX_REQUIRED = ' ' "Indicator showing whether text for the object is mandatory
OBJECT = "Affected object (type)
OBJECT_NR = "Object number
SPRAS = "Language of the text to be maintained
SPRAS_MASTER = "Master language of affected object
TEXT01 = "Object short text in logon language
TXTID = "ID of the text to be maintained
IMPORTING
IND_UPD_1 = "Indicator showing whether changes were made
LTX_EXIST = "Indicator showing whether long text (still) exists
TEXT02 = "Object short text in logon language
IND_UPD_GENERAL = "Indicator showing whether update is required
IMPORTING Parameters details for TEXT_MAINTENANCE
EQTYP - Equipment category (only for equip.)
Data type: T370T-EQTYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_XAKTYP - Activity Category
Data type: T370-AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
INIT - Indicator showing whether call is for the first time
Data type: EQKT-KZLTXDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MTX_REQUIRED - Indicator showing whether text for the object is mandatory
Data type: EQKT-KZLTXDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT - Affected object (type)
Data type: TTXOB-TDOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NR - Object number
Data type: RM63T-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
SPRAS - Language of the text to be maintained
Data type: EQKT-SPRASOptional: No
Call by Reference: No ( called with pass by value option)
SPRAS_MASTER - Master language of affected object
Data type: EQKT-SPRASOptional: No
Call by Reference: No ( called with pass by value option)
TEXT01 - Object short text in logon language
Data type: RM63T-OBJTXOptional: No
Call by Reference: No ( called with pass by value option)
TXTID - ID of the text to be maintained
Data type: TTXID-TDIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TEXT_MAINTENANCE
IND_UPD_1 - Indicator showing whether changes were made
Data type: RM63E-INDUOptional: No
Call by Reference: No ( called with pass by value option)
LTX_EXIST - Indicator showing whether long text (still) exists
Data type: EQKT-KZLTXOptional: No
Call by Reference: No ( called with pass by value option)
TEXT02 - Object short text in logon language
Data type: RM63T-OBJTXOptional: No
Call by Reference: No ( called with pass by value option)
IND_UPD_GENERAL - Indicator showing whether update is required
Data type: RM63E-INDUOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TEXT_MAINTENANCE 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_eqtyp | TYPE T370T-EQTYP, " SPACE | |||
| lv_ind_upd_1 | TYPE RM63E-INDU, " | |||
| lv_x_xaktyp | TYPE T370-AKTYP, " | |||
| lv_init | TYPE EQKT-KZLTX, " 'X' | |||
| lv_ltx_exist | TYPE EQKT-KZLTX, " | |||
| lv_text02 | TYPE RM63T-OBJTX, " | |||
| lv_mtx_required | TYPE EQKT-KZLTX, " SPACE | |||
| lv_object | TYPE TTXOB-TDOBJECT, " | |||
| lv_ind_upd_general | TYPE RM63E-INDU, " | |||
| lv_object_nr | TYPE RM63T-OBJNR, " | |||
| lv_spras | TYPE EQKT-SPRAS, " | |||
| lv_spras_master | TYPE EQKT-SPRAS, " | |||
| lv_text01 | TYPE RM63T-OBJTX, " | |||
| lv_txtid | TYPE TTXID-TDID. " |
|   CALL FUNCTION 'TEXT_MAINTENANCE' "Maintenance of Texts for Maintenance Objects |
| EXPORTING | ||
| EQTYP | = lv_eqtyp | |
| X_XAKTYP | = lv_x_xaktyp | |
| INIT | = lv_init | |
| MTX_REQUIRED | = lv_mtx_required | |
| OBJECT | = lv_object | |
| OBJECT_NR | = lv_object_nr | |
| SPRAS | = lv_spras | |
| SPRAS_MASTER | = lv_spras_master | |
| TEXT01 | = lv_text01 | |
| TXTID | = lv_txtid | |
| IMPORTING | ||
| IND_UPD_1 | = lv_ind_upd_1 | |
| LTX_EXIST | = lv_ltx_exist | |
| TEXT02 | = lv_text02 | |
| IND_UPD_GENERAL | = lv_ind_upd_general | |
| . " TEXT_MAINTENANCE | ||
ABAP code using 7.40 inline data declarations to call FM TEXT_MAINTENANCE
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 EQTYP FROM T370T INTO @DATA(ld_eqtyp). | ||||
| DATA(ld_eqtyp) | = ' '. | |||
| "SELECT single INDU FROM RM63E INTO @DATA(ld_ind_upd_1). | ||||
| "SELECT single AKTYP FROM T370 INTO @DATA(ld_x_xaktyp). | ||||
| "SELECT single KZLTX FROM EQKT INTO @DATA(ld_init). | ||||
| DATA(ld_init) | = 'X'. | |||
| "SELECT single KZLTX FROM EQKT INTO @DATA(ld_ltx_exist). | ||||
| "SELECT single OBJTX FROM RM63T INTO @DATA(ld_text02). | ||||
| "SELECT single KZLTX FROM EQKT INTO @DATA(ld_mtx_required). | ||||
| DATA(ld_mtx_required) | = ' '. | |||
| "SELECT single TDOBJECT FROM TTXOB INTO @DATA(ld_object). | ||||
| "SELECT single INDU FROM RM63E INTO @DATA(ld_ind_upd_general). | ||||
| "SELECT single OBJNR FROM RM63T INTO @DATA(ld_object_nr). | ||||
| "SELECT single SPRAS FROM EQKT INTO @DATA(ld_spras). | ||||
| "SELECT single SPRAS FROM EQKT INTO @DATA(ld_spras_master). | ||||
| "SELECT single OBJTX FROM RM63T INTO @DATA(ld_text01). | ||||
| "SELECT single TDID FROM TTXID INTO @DATA(ld_txtid). | ||||
Search for further information about these or an SAP related objects