TRINT_CREATE_CTS_MESSAGE SAP Function module

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

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

Pattern for FM TRINT_CREATE_CTS_MESSAGE - TRINT CREATE CTS MESSAGE

CALL FUNCTION 'TRINT_CREATE_CTS_MESSAGE' "
  EXPORTING
    msgid =                     " symsgid
    msgty =                     " symsgty
    msgno =                     " symsgno
*   msgv1 = SPACE               " c
*   msgv2 = SPACE               " c
*   msgv3 = SPACE               " c
*   msgv4 = SPACE               " c
  IMPORTING
    message =                   " cts_message
    .  "  TRINT_CREATE_CTS_MESSAGE

ABAP code example for Function Module TRINT_CREATE_CTS_MESSAGE

The ABAP code below is a full code listing to execute function module TRINT_CREATE_CTS_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_message  
 
 TYPE CTS_MESSAGE
.


DATA(ld_msgid) = 'some text here'.

DATA(ld_msgty) = 'some text here'.

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

DATA(ld_msgv1) = 'some text here'.

DATA(ld_msgv2) = 'some text here'.

DATA(ld_msgv3) = 'some text here'.

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

CALL FUNCTION 'TRINT_CREATE_CTS_MESSAGE'
  EXPORTING
    msgid =                      ld_msgid
    msgty =                      ld_msgty
    msgno =                      ld_msgno
*   msgv1 =                      ld_msgv1
*   msgv2 =                      ld_msgv2
*   msgv3 =                      ld_msgv3
*   msgv4 =                      ld_msgv4
  IMPORTING
    message =                    ld_message
    .  "  TRINT_CREATE_CTS_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_message
 
 TYPE CTS_MESSAGE ,
ld_msgid
 
 TYPE SYMSGID ,
ld_msgty
 
 TYPE SYMSGTY ,
ld_msgno
 
 TYPE SYMSGNO ,
ld_msgv1
 
 TYPE C ,
ld_msgv2
 
 TYPE C ,
ld_msgv3
 
 TYPE C ,
ld_msgv4
 
 TYPE C .


ld_msgid = 'some text here'.
ld_msgty = 'some text here'.
ld_msgno = 'Check type of data required'.
ld_msgv1 = 'some text here'.
ld_msgv2 = 'some text here'.
ld_msgv3 = 'some text here'.
ld_msgv4 = 'some text here'.