SAP TRINT_RELEASE_REQUEST Function Module for









TRINT_RELEASE_REQUEST is a standard trint release request 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 release request FM, simply by entering the name TRINT_RELEASE_REQUEST into the relevant SAP transaction such as SE37 or SE38.

Function Group: SCTS_RELEASE
Program Name: SAPLSCTS_RELEASE
Main Program: SAPLSCTS_RELEASE
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function TRINT_RELEASE_REQUEST 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_RELEASE_REQUEST'"
EXPORTING
IV_TRKORR = "Request/Task
* IV_DISPLAY_EXPORT_LOG = 'X' "Boolean
* IV_IGNORE_WARNINGS = ' ' "
* IV_SIMULATION = ' ' "
* IV_DIALOG = 'X' "Dialog
* IV_AS_BACKGROUND_JOB = ' ' "
* IV_SUCCESS_MESSAGE = 'X' "
* IV_WITHOUT_OBJECTS_CHECK = ' ' "
* IV_CALLED_BY_ADT = ' ' "
* IV_CALLED_BY_PERFORCE = ' ' "
* IV_WITHOUT_DOCU = ' ' "
* IV_WITHOUT_LOCKING = ' ' "

IMPORTING
ES_REQUEST = "Request
ET_DELETED_TASKS = "
ET_MESSAGES = "Object-Related Error Messages when Recording Changes

EXCEPTIONS
CTS_INITIALIZATION_FAILURE = 1 DB_ACCESS_ERROR = 10 ACTION_ABORTED_BY_USER = 11 EXPORT_FAILED = 12 EXECUTE_OBJECTS_CHECK = 13 RELEASE_IN_BG_MODE = 14 RELEASE_IN_BG_MODE_W_OBJCHK = 15 ERROR_IN_EXPORT_METHODS = 16 OBJECT_LANG_ERROR = 17 ENQUEUE_FAILED = 2 NO_AUTHORIZATION = 3 INVALID_REQUEST = 4 REQUEST_ALREADY_RELEASED = 5 REPEAT_TOO_EARLY = 6 OBJECT_LOCK_ERROR = 7 OBJECT_CHECK_ERROR = 8 DOCU_MISSING = 9
.



IMPORTING Parameters details for TRINT_RELEASE_REQUEST

IV_TRKORR - Request/Task

Data type: E070-TRKORR
Optional: No
Call by Reference: No ( called with pass by value option)

IV_DISPLAY_EXPORT_LOG - Boolean

Data type: TRBOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_IGNORE_WARNINGS -

Data type: TRBOOLEAN
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SIMULATION -

Data type: TRBOOLEAN
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_DIALOG - Dialog

Data type: TRBOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_AS_BACKGROUND_JOB -

Data type: TRBOOLEAN
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SUCCESS_MESSAGE -

Data type: TRBOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_WITHOUT_OBJECTS_CHECK -

Data type: TRBOOLEAN
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CALLED_BY_ADT -

Data type: TRBOOLEAN
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CALLED_BY_PERFORCE -

Data type: TRBOOLEAN
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_WITHOUT_DOCU -

Data type: TRBOOLEAN
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_WITHOUT_LOCKING -

Data type: TRBOOLEAN
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for TRINT_RELEASE_REQUEST

ES_REQUEST - Request

Data type: TRWBO_REQUEST
Optional: No
Call by Reference: Yes

ET_DELETED_TASKS -

Data type: TRWBO_T_E070
Optional: No
Call by Reference: Yes

ET_MESSAGES - Object-Related Error Messages when Recording Changes

Data type: CTSGERRMSGS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CTS_INITIALIZATION_FAILURE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DB_ACCESS_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ACTION_ABORTED_BY_USER -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORT_FAILED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

EXECUTE_OBJECTS_CHECK -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

RELEASE_IN_BG_MODE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

RELEASE_IN_BG_MODE_W_OBJCHK -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_IN_EXPORT_METHODS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_LANG_ERROR -

Data type:
Optional: No
Call by Reference: Yes

ENQUEUE_FAILED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_AUTHORIZATION -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_REQUEST -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

REQUEST_ALREADY_RELEASED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

REPEAT_TOO_EARLY -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_LOCK_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_CHECK_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DOCU_MISSING -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for TRINT_RELEASE_REQUEST 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_iv_trkorr  TYPE E070-TRKORR, "   
lv_es_request  TYPE TRWBO_REQUEST, "   
lv_cts_initialization_failure  TYPE TRWBO_REQUEST, "   
lv_db_access_error  TYPE TRWBO_REQUEST, "   
lv_iv_display_export_log  TYPE TRBOOLEAN, "   'X'
lv_iv_ignore_warnings  TYPE TRBOOLEAN, "   ' '
lv_action_aborted_by_user  TYPE TRBOOLEAN, "   
lv_export_failed  TYPE TRBOOLEAN, "   
lv_iv_simulation  TYPE TRBOOLEAN, "   ' '
lv_execute_objects_check  TYPE TRBOOLEAN, "   
lv_release_in_bg_mode  TYPE TRBOOLEAN, "   
lv_release_in_bg_mode_w_objchk  TYPE TRBOOLEAN, "   
lv_error_in_export_methods  TYPE TRBOOLEAN, "   
lv_object_lang_error  TYPE TRBOOLEAN, "   
lv_iv_dialog  TYPE TRBOOLEAN, "   'X'
lv_enqueue_failed  TYPE TRBOOLEAN, "   
lv_et_deleted_tasks  TYPE TRWBO_T_E070, "   
lv_et_messages  TYPE CTSGERRMSGS, "   
lv_no_authorization  TYPE CTSGERRMSGS, "   
lv_iv_as_background_job  TYPE TRBOOLEAN, "   ' '
lv_invalid_request  TYPE TRBOOLEAN, "   
lv_iv_success_message  TYPE TRBOOLEAN, "   'X'
lv_iv_without_objects_check  TYPE TRBOOLEAN, "   ' '
lv_request_already_released  TYPE TRBOOLEAN, "   
lv_iv_called_by_adt  TYPE TRBOOLEAN, "   ' '
lv_repeat_too_early  TYPE TRBOOLEAN, "   
lv_object_lock_error  TYPE TRBOOLEAN, "   
lv_iv_called_by_perforce  TYPE TRBOOLEAN, "   ' '
lv_iv_without_docu  TYPE TRBOOLEAN, "   ' '
lv_object_check_error  TYPE TRBOOLEAN, "   
lv_docu_missing  TYPE TRBOOLEAN, "   
lv_iv_without_locking  TYPE TRBOOLEAN. "   ' '

  CALL FUNCTION 'TRINT_RELEASE_REQUEST'  "
    EXPORTING
         IV_TRKORR = lv_iv_trkorr
         IV_DISPLAY_EXPORT_LOG = lv_iv_display_export_log
         IV_IGNORE_WARNINGS = lv_iv_ignore_warnings
         IV_SIMULATION = lv_iv_simulation
         IV_DIALOG = lv_iv_dialog
         IV_AS_BACKGROUND_JOB = lv_iv_as_background_job
         IV_SUCCESS_MESSAGE = lv_iv_success_message
         IV_WITHOUT_OBJECTS_CHECK = lv_iv_without_objects_check
         IV_CALLED_BY_ADT = lv_iv_called_by_adt
         IV_CALLED_BY_PERFORCE = lv_iv_called_by_perforce
         IV_WITHOUT_DOCU = lv_iv_without_docu
         IV_WITHOUT_LOCKING = lv_iv_without_locking
    IMPORTING
         ES_REQUEST = lv_es_request
         ET_DELETED_TASKS = lv_et_deleted_tasks
         ET_MESSAGES = lv_et_messages
    EXCEPTIONS
        CTS_INITIALIZATION_FAILURE = 1
        DB_ACCESS_ERROR = 10
        ACTION_ABORTED_BY_USER = 11
        EXPORT_FAILED = 12
        EXECUTE_OBJECTS_CHECK = 13
        RELEASE_IN_BG_MODE = 14
        RELEASE_IN_BG_MODE_W_OBJCHK = 15
        ERROR_IN_EXPORT_METHODS = 16
        OBJECT_LANG_ERROR = 17
        ENQUEUE_FAILED = 2
        NO_AUTHORIZATION = 3
        INVALID_REQUEST = 4
        REQUEST_ALREADY_RELEASED = 5
        REPEAT_TOO_EARLY = 6
        OBJECT_LOCK_ERROR = 7
        OBJECT_CHECK_ERROR = 8
        DOCU_MISSING = 9
. " TRINT_RELEASE_REQUEST




ABAP code using 7.40 inline data declarations to call FM TRINT_RELEASE_REQUEST

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 TRKORR FROM E070 INTO @DATA(ld_iv_trkorr).
 
 
 
 
DATA(ld_iv_display_export_log) = 'X'.
 
DATA(ld_iv_ignore_warnings) = ' '.
 
 
 
DATA(ld_iv_simulation) = ' '.
 
 
 
 
 
 
DATA(ld_iv_dialog) = 'X'.
 
 
 
 
 
DATA(ld_iv_as_background_job) = ' '.
 
 
DATA(ld_iv_success_message) = 'X'.
 
DATA(ld_iv_without_objects_check) = ' '.
 
 
DATA(ld_iv_called_by_adt) = ' '.
 
 
 
DATA(ld_iv_called_by_perforce) = ' '.
 
DATA(ld_iv_without_docu) = ' '.
 
 
 
DATA(ld_iv_without_locking) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!