SAP TRINT_RELEASE_PROJECT Function Module for









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

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



Function TRINT_RELEASE_PROJECT 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_PROJECT'"
EXPORTING
* IV_DIALOG = ' ' "
* IV_TEST_MODE = ' ' "
* IV_WITH_COMMIT_WORK = ' ' "
* IV_USE_CONTROL = 'X' "

CHANGING
CS_PROJECT = "

EXCEPTIONS
NO_AUTHORIZATION = 1 REQUESTS_NOT_EXPORTED = 2 REQUESTS_NOT_IMPORTED = 3 DB_ACCESS_ERROR = 4 CANCELLED_BY_USER = 5
.



IMPORTING Parameters details for TRINT_RELEASE_PROJECT

IV_DIALOG -

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

IV_TEST_MODE -

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

IV_WITH_COMMIT_WORK -

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

IV_USE_CONTROL -

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for TRINT_RELEASE_PROJECT

CS_PROJECT -

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

EXCEPTIONS details

NO_AUTHORIZATION - No Authorization

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

REQUESTS_NOT_EXPORTED -

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

REQUESTS_NOT_IMPORTED -

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)

CANCELLED_BY_USER - Cancellation by user

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

Copy and paste ABAP code example for TRINT_RELEASE_PROJECT 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_dialog  TYPE TRPARFLAG, "   ' '
lv_cs_project  TYPE TRPROJECT, "   
lv_no_authorization  TYPE TRPROJECT, "   
lv_iv_test_mode  TYPE TRPARFLAG, "   ' '
lv_requests_not_exported  TYPE TRPARFLAG, "   
lv_iv_with_commit_work  TYPE TRPARFLAG, "   ' '
lv_requests_not_imported  TYPE TRPARFLAG, "   
lv_iv_use_control  TYPE C, "   'X'
lv_db_access_error  TYPE C, "   
lv_cancelled_by_user  TYPE C. "   

  CALL FUNCTION 'TRINT_RELEASE_PROJECT'  "
    EXPORTING
         IV_DIALOG = lv_iv_dialog
         IV_TEST_MODE = lv_iv_test_mode
         IV_WITH_COMMIT_WORK = lv_iv_with_commit_work
         IV_USE_CONTROL = lv_iv_use_control
    CHANGING
         CS_PROJECT = lv_cs_project
    EXCEPTIONS
        NO_AUTHORIZATION = 1
        REQUESTS_NOT_EXPORTED = 2
        REQUESTS_NOT_IMPORTED = 3
        DB_ACCESS_ERROR = 4
        CANCELLED_BY_USER = 5
. " TRINT_RELEASE_PROJECT




ABAP code using 7.40 inline data declarations to call FM TRINT_RELEASE_PROJECT

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.

DATA(ld_iv_dialog) = ' '.
 
 
 
DATA(ld_iv_test_mode) = ' '.
 
 
DATA(ld_iv_with_commit_work) = ' '.
 
 
DATA(ld_iv_use_control) = 'X'.
 
 
 


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!