SAP TRINT_INSERT_NEW_COMM Function Module for Create new request/new task









TRINT_INSERT_NEW_COMM is a standard trint insert new comm SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create new request/new task 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 trint insert new comm FM, simply by entering the name TRINT_INSERT_NEW_COMM into the relevant SAP transaction such as SE37 or SE38.

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



Function TRINT_INSERT_NEW_COMM 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_INSERT_NEW_COMM'"Create new request/new task
  EXPORTING
   WI_KURZTEXT =  "Short text for task/request
*  WI_PROTECT = ' ' "Request is created with protection
*  IV_SIMULATION = ' ' "X - in simulation mode (no update)
   WI_TRFUNCTION =  "Request type ('K', 'T', 'C',...)
*  IV_USERNAME = SY-UNAME "Owner of request
*  WI_STRKORR = ' ' "
*  IV_TARSYSTEM = ' ' "Target system for request
*  WI_CLIENT = ' ' "
*  IV_TARDEVCL = ' ' "Target development class of the request (type O only)
*  IV_DEVCLASS = ' ' "Development class (type E only)
*  IV_TARLAYER = ' ' "Target transport layer of the request (type E only)

 IMPORTING
   WE_TRKORR =  "Task/request
   WE_E070 =  "Output string for E070
   WE_E07T =  "Output string for E07T
   WE_E070C =  "Output string for E070C
   ES_E070M =  "Output string for E070M

EXCEPTIONS
   NO_SYSTEMNAME = 1    NO_SYSTEMTYPE = 2    NO_AUTHORIZATION = 3    DB_ACCESS_ERROR = 4    FILE_ACCESS_ERROR = 5    ENQUEUE_ERROR = 6    NUMBER_RANGE_FULL = 7    INVALID_INPUT = 8
.



IMPORTING Parameters details for TRINT_INSERT_NEW_COMM

WI_KURZTEXT - Short text for task/request

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

WI_PROTECT - Request is created with protection

Data type: TRPARI-S_LOCKFLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SIMULATION - X - in simulation mode (no update)

Data type: TRPARI-W_SIMULAT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

WI_TRFUNCTION - Request type ('K', 'T', 'C',...)

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

IV_USERNAME - Owner of request

Data type: E070-AS4USER
Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

WI_STRKORR -

Data type: E070-STRKORR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TARSYSTEM - Target system for request

Data type: E070-TARSYSTEM
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

WI_CLIENT -

Data type: E070C-CLIENT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TARDEVCL - Target development class of the request (type O only)

Data type: E070M-TARDEVCL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_DEVCLASS - Development class (type E only)

Data type: E070M-DEVCLASS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TARLAYER - Target transport layer of the request (type E only)

Data type: E070M-TARLAYER
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for TRINT_INSERT_NEW_COMM

WE_TRKORR - Task/request

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

WE_E070 - Output string for E070

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

WE_E07T - Output string for E07T

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

WE_E070C - Output string for E070C

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

ES_E070M - Output string for E070M

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

EXCEPTIONS details

NO_SYSTEMNAME -

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

NO_SYSTEMTYPE -

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

NO_AUTHORIZATION - No Authorization

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

DB_ACCESS_ERROR - Database access error

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

FILE_ACCESS_ERROR - Error when accessing file

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

ENQUEUE_ERROR -

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

NUMBER_RANGE_FULL -

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

INVALID_INPUT -

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

Copy and paste ABAP code example for TRINT_INSERT_NEW_COMM 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_we_trkorr  TYPE E070-TRKORR, "   
lv_wi_kurztext  TYPE E07T-AS4TEXT, "   
lv_no_systemname  TYPE E07T, "   
lv_wi_protect  TYPE TRPARI-S_LOCKFLAG, "   SPACE
lv_iv_simulation  TYPE TRPARI-W_SIMULAT, "   SPACE
lv_we_e070  TYPE E070, "   
lv_no_systemtype  TYPE E070, "   
lv_wi_trfunction  TYPE E070-TRFUNCTION, "   
lv_we_e07t  TYPE E07T, "   
lv_iv_username  TYPE E070-AS4USER, "   SY-UNAME
lv_no_authorization  TYPE E070, "   
lv_we_e070c  TYPE E070C, "   
lv_wi_strkorr  TYPE E070-STRKORR, "   SPACE
lv_db_access_error  TYPE E070, "   
lv_es_e070m  TYPE E070M, "   
lv_iv_tarsystem  TYPE E070-TARSYSTEM, "   SPACE
lv_file_access_error  TYPE E070, "   
lv_wi_client  TYPE E070C-CLIENT, "   SPACE
lv_enqueue_error  TYPE E070C, "   
lv_iv_tardevcl  TYPE E070M-TARDEVCL, "   SPACE
lv_number_range_full  TYPE E070M, "   
lv_iv_devclass  TYPE E070M-DEVCLASS, "   SPACE
lv_invalid_input  TYPE E070M, "   
lv_iv_tarlayer  TYPE E070M-TARLAYER. "   SPACE

  CALL FUNCTION 'TRINT_INSERT_NEW_COMM'  "Create new request/new task
    EXPORTING
         WI_KURZTEXT = lv_wi_kurztext
         WI_PROTECT = lv_wi_protect
         IV_SIMULATION = lv_iv_simulation
         WI_TRFUNCTION = lv_wi_trfunction
         IV_USERNAME = lv_iv_username
         WI_STRKORR = lv_wi_strkorr
         IV_TARSYSTEM = lv_iv_tarsystem
         WI_CLIENT = lv_wi_client
         IV_TARDEVCL = lv_iv_tardevcl
         IV_DEVCLASS = lv_iv_devclass
         IV_TARLAYER = lv_iv_tarlayer
    IMPORTING
         WE_TRKORR = lv_we_trkorr
         WE_E070 = lv_we_e070
         WE_E07T = lv_we_e07t
         WE_E070C = lv_we_e070c
         ES_E070M = lv_es_e070m
    EXCEPTIONS
        NO_SYSTEMNAME = 1
        NO_SYSTEMTYPE = 2
        NO_AUTHORIZATION = 3
        DB_ACCESS_ERROR = 4
        FILE_ACCESS_ERROR = 5
        ENQUEUE_ERROR = 6
        NUMBER_RANGE_FULL = 7
        INVALID_INPUT = 8
. " TRINT_INSERT_NEW_COMM




ABAP code using 7.40 inline data declarations to call FM TRINT_INSERT_NEW_COMM

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_we_trkorr).
 
"SELECT single AS4TEXT FROM E07T INTO @DATA(ld_wi_kurztext).
 
 
"SELECT single S_LOCKFLAG FROM TRPARI INTO @DATA(ld_wi_protect).
DATA(ld_wi_protect) = ' '.
 
"SELECT single W_SIMULAT FROM TRPARI INTO @DATA(ld_iv_simulation).
DATA(ld_iv_simulation) = ' '.
 
 
 
"SELECT single TRFUNCTION FROM E070 INTO @DATA(ld_wi_trfunction).
 
 
"SELECT single AS4USER FROM E070 INTO @DATA(ld_iv_username).
DATA(ld_iv_username) = SY-UNAME.
 
 
 
"SELECT single STRKORR FROM E070 INTO @DATA(ld_wi_strkorr).
DATA(ld_wi_strkorr) = ' '.
 
 
 
"SELECT single TARSYSTEM FROM E070 INTO @DATA(ld_iv_tarsystem).
DATA(ld_iv_tarsystem) = ' '.
 
 
"SELECT single CLIENT FROM E070C INTO @DATA(ld_wi_client).
DATA(ld_wi_client) = ' '.
 
 
"SELECT single TARDEVCL FROM E070M INTO @DATA(ld_iv_tardevcl).
DATA(ld_iv_tardevcl) = ' '.
 
 
"SELECT single DEVCLASS FROM E070M INTO @DATA(ld_iv_devclass).
DATA(ld_iv_devclass) = ' '.
 
 
"SELECT single TARLAYER FROM E070M INTO @DATA(ld_iv_tarlayer).
DATA(ld_iv_tarlayer) = ' '.
 


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!