SAP TRINT_TADIR_MODIFY Function Module for
TRINT_TADIR_MODIFY is a standard trint tadir modify SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 trint tadir modify FM, simply by entering the name TRINT_TADIR_MODIFY into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDI0
Program Name: SAPLSDI0
Main Program: SAPLSDI0
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TRINT_TADIR_MODIFY 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 'TRINT_TADIR_MODIFY'".
EXPORTING
* AUTHOR = '~' "Object author
PGMID = "Object type (R3TR, R3OB, ...)
* SRCDEP = '~' "Repair flag
* SRCSYSTEM = '~' "Original System
* VERSID = '~' "Version Number
* CHANGE_MASTERLANG = '~' "
* FORCE_MODE = '~' "
* PAKNOCHECK = '~' "Exception Indicator for Package Check
* OBJSTABLTY = '~' "Release Status of a Development Object
* DELFLAG = '~' "
* TRANSL_TECH_TEXT = '~' "
* CPROJECT = '~' "L - ojbect must be checked against GTADIR
* CREATED_ON = '~' "
* CHECK_DATE = '~' "
* CHECK_CFG = '~' "
* DEVCLASS = '~' "Package
* EDTFLAG = '~' "'X' -> Object cannot be edited
* EXISTS = '~' "
* GENFLAG = '~' "
* MASTERLANG = '~' "Object was generated in this language
OBJECT = "Object subtype (PROG, TABL ...)
OBJ_NAME = "Object name
IMPORTING
ES_TADIR = "Object directory entry (TADIR)
EXCEPTIONS
OBJECT_EXISTS_GLOBAL = 1 OBJECT_EXISTS_LOCAL = 2 OBJECT_HAS_NO_TADIR = 3
IMPORTING Parameters details for TRINT_TADIR_MODIFY
AUTHOR - Object author
Data type: TADIR-AUTHORDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
PGMID - Object type (R3TR, R3OB, ...)
Data type: TADIR-PGMIDOptional: No
Call by Reference: No ( called with pass by value option)
SRCDEP - Repair flag
Data type: TADIR-SRCDEPDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SRCSYSTEM - Original System
Data type: TADIR-SRCSYSTEMDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
VERSID - Version Number
Data type: TADIR-VERSIDDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGE_MASTERLANG -
Data type: TRPARI-S_SELECTDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
FORCE_MODE -
Data type: TRPARI-FLAGDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
PAKNOCHECK - Exception Indicator for Package Check
Data type: TADIR-PAKNOCHECKDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJSTABLTY - Release Status of a Development Object
Data type: TADIR-OBJSTABLTYDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
DELFLAG -
Data type: TADIR-DELFLAGDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TRANSL_TECH_TEXT -
Data type: TADIR-TRANSLTTXTDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CPROJECT - L - ojbect must be checked against GTADIR
Data type: TADIR-CPROJECTDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CREATED_ON -
Data type: TADIR-CREATED_ONDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHECK_DATE -
Data type: TADIR-CHECK_DATEDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHECK_CFG -
Data type: TADIR-CHECK_CFGDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
DEVCLASS - Package
Data type: TADIR-DEVCLASSDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EDTFLAG - 'X' -> Object cannot be edited
Data type: TADIR-EDTFLAGDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXISTS -
Data type: SDIT_PARAM-FLAGDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
GENFLAG -
Data type: TADIR-GENFLAGDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MASTERLANG - Object was generated in this language
Data type: TADIR-MASTERLANGDefault: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT - Object subtype (PROG, TABL ...)
Data type: TADIR-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
OBJ_NAME - Object name
Data type: TADIR-OBJ_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TRINT_TADIR_MODIFY
ES_TADIR - Object directory entry (TADIR)
Data type: TADIROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_EXISTS_GLOBAL - Object already exists globally
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_EXISTS_LOCAL - Object already exists locally
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_HAS_NO_TADIR - Object does not exist locally
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TRINT_TADIR_MODIFY 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_author | TYPE TADIR-AUTHOR, " '~' | |||
| lv_es_tadir | TYPE TADIR, " | |||
| lv_object_exists_global | TYPE TADIR, " | |||
| lv_pgmid | TYPE TADIR-PGMID, " | |||
| lv_srcdep | TYPE TADIR-SRCDEP, " '~' | |||
| lv_srcsystem | TYPE TADIR-SRCSYSTEM, " '~' | |||
| lv_versid | TYPE TADIR-VERSID, " '~' | |||
| lv_change_masterlang | TYPE TRPARI-S_SELECT, " '~' | |||
| lv_force_mode | TYPE TRPARI-FLAG, " '~' | |||
| lv_paknocheck | TYPE TADIR-PAKNOCHECK, " '~' | |||
| lv_objstablty | TYPE TADIR-OBJSTABLTY, " '~' | |||
| lv_delflag | TYPE TADIR-DELFLAG, " '~' | |||
| lv_transl_tech_text | TYPE TADIR-TRANSLTTXT, " '~' | |||
| lv_cproject | TYPE TADIR-CPROJECT, " '~' | |||
| lv_object_exists_local | TYPE TADIR, " | |||
| lv_created_on | TYPE TADIR-CREATED_ON, " '~' | |||
| lv_check_date | TYPE TADIR-CHECK_DATE, " '~' | |||
| lv_check_cfg | TYPE TADIR-CHECK_CFG, " '~' | |||
| lv_devclass | TYPE TADIR-DEVCLASS, " '~' | |||
| lv_object_has_no_tadir | TYPE TADIR, " | |||
| lv_edtflag | TYPE TADIR-EDTFLAG, " '~' | |||
| lv_exists | TYPE SDIT_PARAM-FLAG, " '~' | |||
| lv_genflag | TYPE TADIR-GENFLAG, " '~' | |||
| lv_masterlang | TYPE TADIR-MASTERLANG, " '~' | |||
| lv_object | TYPE TADIR-OBJECT, " | |||
| lv_obj_name | TYPE TADIR-OBJ_NAME. " |
|   CALL FUNCTION 'TRINT_TADIR_MODIFY' " |
| EXPORTING | ||
| AUTHOR | = lv_author | |
| PGMID | = lv_pgmid | |
| SRCDEP | = lv_srcdep | |
| SRCSYSTEM | = lv_srcsystem | |
| VERSID | = lv_versid | |
| CHANGE_MASTERLANG | = lv_change_masterlang | |
| FORCE_MODE | = lv_force_mode | |
| PAKNOCHECK | = lv_paknocheck | |
| OBJSTABLTY | = lv_objstablty | |
| DELFLAG | = lv_delflag | |
| TRANSL_TECH_TEXT | = lv_transl_tech_text | |
| CPROJECT | = lv_cproject | |
| CREATED_ON | = lv_created_on | |
| CHECK_DATE | = lv_check_date | |
| CHECK_CFG | = lv_check_cfg | |
| DEVCLASS | = lv_devclass | |
| EDTFLAG | = lv_edtflag | |
| EXISTS | = lv_exists | |
| GENFLAG | = lv_genflag | |
| MASTERLANG | = lv_masterlang | |
| OBJECT | = lv_object | |
| OBJ_NAME | = lv_obj_name | |
| IMPORTING | ||
| ES_TADIR | = lv_es_tadir | |
| EXCEPTIONS | ||
| OBJECT_EXISTS_GLOBAL = 1 | ||
| OBJECT_EXISTS_LOCAL = 2 | ||
| OBJECT_HAS_NO_TADIR = 3 | ||
| . " TRINT_TADIR_MODIFY | ||
ABAP code using 7.40 inline data declarations to call FM TRINT_TADIR_MODIFY
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 AUTHOR FROM TADIR INTO @DATA(ld_author). | ||||
| DATA(ld_author) | = '~'. | |||
| "SELECT single PGMID FROM TADIR INTO @DATA(ld_pgmid). | ||||
| "SELECT single SRCDEP FROM TADIR INTO @DATA(ld_srcdep). | ||||
| DATA(ld_srcdep) | = '~'. | |||
| "SELECT single SRCSYSTEM FROM TADIR INTO @DATA(ld_srcsystem). | ||||
| DATA(ld_srcsystem) | = '~'. | |||
| "SELECT single VERSID FROM TADIR INTO @DATA(ld_versid). | ||||
| DATA(ld_versid) | = '~'. | |||
| "SELECT single S_SELECT FROM TRPARI INTO @DATA(ld_change_masterlang). | ||||
| DATA(ld_change_masterlang) | = '~'. | |||
| "SELECT single FLAG FROM TRPARI INTO @DATA(ld_force_mode). | ||||
| DATA(ld_force_mode) | = '~'. | |||
| "SELECT single PAKNOCHECK FROM TADIR INTO @DATA(ld_paknocheck). | ||||
| DATA(ld_paknocheck) | = '~'. | |||
| "SELECT single OBJSTABLTY FROM TADIR INTO @DATA(ld_objstablty). | ||||
| DATA(ld_objstablty) | = '~'. | |||
| "SELECT single DELFLAG FROM TADIR INTO @DATA(ld_delflag). | ||||
| DATA(ld_delflag) | = '~'. | |||
| "SELECT single TRANSLTTXT FROM TADIR INTO @DATA(ld_transl_tech_text). | ||||
| DATA(ld_transl_tech_text) | = '~'. | |||
| "SELECT single CPROJECT FROM TADIR INTO @DATA(ld_cproject). | ||||
| DATA(ld_cproject) | = '~'. | |||
| "SELECT single CREATED_ON FROM TADIR INTO @DATA(ld_created_on). | ||||
| DATA(ld_created_on) | = '~'. | |||
| "SELECT single CHECK_DATE FROM TADIR INTO @DATA(ld_check_date). | ||||
| DATA(ld_check_date) | = '~'. | |||
| "SELECT single CHECK_CFG FROM TADIR INTO @DATA(ld_check_cfg). | ||||
| DATA(ld_check_cfg) | = '~'. | |||
| "SELECT single DEVCLASS FROM TADIR INTO @DATA(ld_devclass). | ||||
| DATA(ld_devclass) | = '~'. | |||
| "SELECT single EDTFLAG FROM TADIR INTO @DATA(ld_edtflag). | ||||
| DATA(ld_edtflag) | = '~'. | |||
| "SELECT single FLAG FROM SDIT_PARAM INTO @DATA(ld_exists). | ||||
| DATA(ld_exists) | = '~'. | |||
| "SELECT single GENFLAG FROM TADIR INTO @DATA(ld_genflag). | ||||
| DATA(ld_genflag) | = '~'. | |||
| "SELECT single MASTERLANG FROM TADIR INTO @DATA(ld_masterlang). | ||||
| DATA(ld_masterlang) | = '~'. | |||
| "SELECT single OBJECT FROM TADIR INTO @DATA(ld_object). | ||||
| "SELECT single OBJ_NAME FROM TADIR INTO @DATA(ld_obj_name). | ||||
Search for further information about these or an SAP related objects