TRINT_POPUP_TO_CREATE_REQUEST SAP Function module

TRINT_POPUP_TO_CREATE_REQUEST is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name TRINT_POPUP_TO_CREATE_REQUEST into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SCTSREQ
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM TRINT_POPUP_TO_CREATE_REQUEST - TRINT POPUP TO CREATE REQUEST

CALL FUNCTION 'TRINT_POPUP_TO_CREATE_REQUEST' "
  IMPORTING
    ev_tarpackage =             " tardevcl      Target Package
    ev_package =                " devclass      Package
    ev_tarlayer =               " tarlayer      Target Transport Layer
    ev_target =                 " tr_target     Transport target of a request
  CHANGING
    cv_type =                   " trfunction    Type of Request/Task
    cv_text =                   " as4text       Short Text Describing R/3 Repository Objects
*   ct_users =                  " trusers       Employee
  EXCEPTIONS
    ACTION_CANCELLED = 1        "
    .  "  TRINT_POPUP_TO_CREATE_REQUEST

ABAP code example for Function Module TRINT_POPUP_TO_CREATE_REQUEST

The ABAP code below is a full code listing to execute function module TRINT_POPUP_TO_CREATE_REQUEST including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ev_tarpackage  
 
 TYPE TARDEVCL
,
ld_ev_package  
 
 TYPE DEVCLASS
,
ld_ev_tarlayer  
 
 TYPE TARLAYER
,
ld_ev_target  
 
 TYPE TR_TARGET
.


DATA(ld_cv_type) = 'Check type of data required'.

DATA(ld_cv_text) = 'Check type of data required'.

DATA(ld_ct_users) = 'Check type of data required'.
.

CALL FUNCTION 'TRINT_POPUP_TO_CREATE_REQUEST'
  IMPORTING
    ev_tarpackage =              ld_ev_tarpackage
    ev_package =                 ld_ev_package
    ev_tarlayer =                ld_ev_tarlayer
    ev_target =                  ld_ev_target
  CHANGING
    cv_type =                    ld_cv_type
    cv_text =                    ld_cv_text
*   ct_users =                   ld_ct_users
  EXCEPTIONS
    ACTION_CANCELLED =           1
    .  "  TRINT_POPUP_TO_CREATE_REQUEST

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_cv_type
 
 TYPE TRFUNCTION ,
ld_ev_tarpackage
 
 TYPE TARDEVCL ,
ld_cv_text
 
 TYPE AS4TEXT ,
ld_ev_package
 
 TYPE DEVCLASS ,
ld_ct_users
 
 TYPE TRUSERS ,
ld_ev_tarlayer
 
 TYPE TARLAYER ,
ld_ev_target
 
 TYPE TR_TARGET .


ld_cv_type = 'Check type of data required'.
ld_cv_text = 'Check type of data required'.
ld_ct_users = 'Check type of data required'.