TRINT_TCE_MESSAGE SAP Function module

TRINT_TCE_MESSAGE 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_TCE_MESSAGE into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM TRINT_TCE_MESSAGE - TRINT TCE MESSAGE

CALL FUNCTION 'TRINT_TCE_MESSAGE' "
  EXPORTING
    iv_number =                 "
*   iv_type = 'S'               " c
*   iv_id = '0T'                " t100-arbgb
*   iv_par1 = ' '               "
*   iv_par2 = ' '               "
*   iv_par3 = ' '               "
*   iv_par4 = ' '               "
  IMPORTING
    ev_exit =                   " c
    .  "  TRINT_TCE_MESSAGE

ABAP code example for Function Module TRINT_TCE_MESSAGE

The ABAP code below is a full code listing to execute function module TRINT_TCE_MESSAGE 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_exit  
 
 TYPE C
.


DATA(ld_iv_number) = 'some text here'.

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

SELECT single ARBGB 
  FROM T100 
  INTO @DATA(ld_iv_id).


DATA(ld_iv_par1) = 'some text here'.

DATA(ld_iv_par2) = 'some text here'.

DATA(ld_iv_par3) = 'some text here'.

DATA(ld_iv_par4) = 'some text here'.
.

CALL FUNCTION 'TRINT_TCE_MESSAGE'
  EXPORTING
    iv_number =                  ld_iv_number
*   iv_type =                    ld_iv_type
*   iv_id =                      ld_iv_id
*   iv_par1 =                    ld_iv_par1
*   iv_par2 =                    ld_iv_par2
*   iv_par3 =                    ld_iv_par3
*   iv_par4 =                    ld_iv_par4
  IMPORTING
    ev_exit =                    ld_ev_exit
    .  "  TRINT_TCE_MESSAGE

IF SY-SUBRC EQ 0.
  "All OK
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_ev_exit
 
 TYPE C ,
ld_iv_number
 
 TYPE STRING ,
ld_iv_type
 
 TYPE C ,
ld_iv_id
 
 TYPE T100-ARBGB ,
ld_iv_par1
 
 TYPE STRING ,
ld_iv_par2
 
 TYPE STRING ,
ld_iv_par3
 
 TYPE STRING ,
ld_iv_par4
 
 TYPE STRING .


ld_iv_number = 'some text here'.
ld_iv_type = 'Check type of data required'.

SELECT single ARBGB 
  FROM T100 
  INTO ld_iv_id.

ld_iv_par1 = 'some text here'.
ld_iv_par2 = 'some text here'.
ld_iv_par3 = 'some text here'.
ld_iv_par4 = 'some text here'.