SAP TRINT_APPEND_COMM_SYSLOG_ENTRY Function Module for

Search SAP Function Modules

TRINT_APPEND_COMM_SYSLOG_ENTRY is a standard trint append comm syslog entry 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 append comm syslog entry FM, simply by entering the name TRINT_APPEND_COMM_SYSLOG_ENTRY 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_APPEND_COMM_SYSLOG_ENTRY 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_APPEND_COMM_SYSLOG_ENTRY'"
  EXPORTING
   WI_MSGID =  "Message application area
   WI_MSGNO =  "Message number
*  WI_MSGV2 =  "Variable 2 for message
*  WI_MSGV3 =  "Variable 3 for message
*  WI_MSGV4 =  "Variable 4 for message
*  WI_NEW_ORDER = ' ' "First action log line (only on open request)
*  WI_TRFUNCTION = ' ' "Type of request/task
   WI_TRKORR =  "Number of the request/task

.

IMPORTING Parameters details for TRINT_APPEND_COMM_SYSLOG_ENTRY

WI_MSGID - Message application area

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

WI_MSGNO - Message number

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

WI_MSGV2 - Variable 2 for message

Data type: SY-MSGV2
Optional: Yes
Call by Reference: No ( called with pass by value option)

WI_MSGV3 - Variable 3 for message

Data type: SY-MSGV3
Optional: Yes
Call by Reference: No ( called with pass by value option)

WI_MSGV4 - Variable 4 for message

Data type: SY-MSGV4
Optional: Yes
Call by Reference: No ( called with pass by value option)

WI_NEW_ORDER - First action log line (only on open request)

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

WI_TRFUNCTION - Type of request/task

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

WI_TRKORR - Number of the request/task

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

Copy and paste ABAP code example for TRINT_APPEND_COMM_SYSLOG_ENTRY 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.

ABAP code using 7.40 inline data declarations to call FM TRINT_APPEND_COMM_SYSLOG_ENTRY

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.

Search for further information about these or an SAP related objects