SAP TR_WRITE_LOG Function Module for Write log
TR_WRITE_LOG is a standard tr write log SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Write log 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 tr write log FM, simply by entering the name TR_WRITE_LOG into the relevant SAP transaction such as SE37 or SE38.
Function Group: SLOG
Program Name: SAPLSLOG
Main Program: SAPLSLOG
Appliation area: S
Release date: 02-Jul-1997
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TR_WRITE_LOG 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 'TR_WRITE_LOG'"Write log.
EXPORTING
* IV_LOG_TYPE = 'FILE' "Log type: 'FILE', 'DB', 'MEMORY'
* IV_LOGNAME_FILE = "Name of log (file)
* IV_LOGNAME_DB = "Name of log (database)
* IV_LOGNAME_MEMORY = "Name of log (memory)
* IV_APPEND_MODE = ' ' "Memory log: Append messages
* IV_CONDENSE = 'X' "Lines are condensed
TABLES
IT_MSGS = "Table with messages
EXCEPTIONS
INVALID_INPUT = 1 FILE_ACCESS_ERROR = 2 DB_ACCESS_ERROR = 3
IMPORTING Parameters details for TR_WRITE_LOG
IV_LOG_TYPE - Log type: 'FILE', 'DB', 'MEMORY'
Data type: TRLOG_TYPEDefault: 'FILE'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_LOGNAME_FILE - Name of log (file)
Data type: TSTRF01-FILEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_LOGNAME_DB - Name of log (database)
Data type: DDPRH-PROTNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_LOGNAME_MEMORY - Name of log (memory)
Data type: TSTRF01-FILENAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_APPEND_MODE - Memory log: Append messages
Data type: TRPARI-FLAGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_CONDENSE - Lines are condensed
Data type: TRPARI-FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for TR_WRITE_LOG
IT_MSGS - Table with messages
Data type: SPROT_UOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_INPUT - Invalid entry
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FILE_ACCESS_ERROR - Error accessing file
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DB_ACCESS_ERROR - Error Accessing Database
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TR_WRITE_LOG 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: | ||||
| lt_it_msgs | TYPE STANDARD TABLE OF SPROT_U, " | |||
| lv_iv_log_type | TYPE TRLOG_TYPE, " 'FILE' | |||
| lv_invalid_input | TYPE TRLOG_TYPE, " | |||
| lv_iv_logname_file | TYPE TSTRF01-FILE, " | |||
| lv_file_access_error | TYPE TSTRF01, " | |||
| lv_iv_logname_db | TYPE DDPRH-PROTNAME, " | |||
| lv_db_access_error | TYPE DDPRH, " | |||
| lv_iv_logname_memory | TYPE TSTRF01-FILENAME, " | |||
| lv_iv_append_mode | TYPE TRPARI-FLAG, " ' ' | |||
| lv_iv_condense | TYPE TRPARI-FLAG. " 'X' |
|   CALL FUNCTION 'TR_WRITE_LOG' "Write log |
| EXPORTING | ||
| IV_LOG_TYPE | = lv_iv_log_type | |
| IV_LOGNAME_FILE | = lv_iv_logname_file | |
| IV_LOGNAME_DB | = lv_iv_logname_db | |
| IV_LOGNAME_MEMORY | = lv_iv_logname_memory | |
| IV_APPEND_MODE | = lv_iv_append_mode | |
| IV_CONDENSE | = lv_iv_condense | |
| TABLES | ||
| IT_MSGS | = lt_it_msgs | |
| EXCEPTIONS | ||
| INVALID_INPUT = 1 | ||
| FILE_ACCESS_ERROR = 2 | ||
| DB_ACCESS_ERROR = 3 | ||
| . " TR_WRITE_LOG | ||
ABAP code using 7.40 inline data declarations to call FM TR_WRITE_LOG
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.| DATA(ld_iv_log_type) | = 'FILE'. | |||
| "SELECT single FILE FROM TSTRF01 INTO @DATA(ld_iv_logname_file). | ||||
| "SELECT single PROTNAME FROM DDPRH INTO @DATA(ld_iv_logname_db). | ||||
| "SELECT single FILENAME FROM TSTRF01 INTO @DATA(ld_iv_logname_memory). | ||||
| "SELECT single FLAG FROM TRPARI INTO @DATA(ld_iv_append_mode). | ||||
| DATA(ld_iv_append_mode) | = ' '. | |||
| "SELECT single FLAG FROM TRPARI INTO @DATA(ld_iv_condense). | ||||
| DATA(ld_iv_condense) | = 'X'. | |||
Search for further information about these or an SAP related objects