SAP NAME_OF_CURRENT_TRACE_FILE Function Module for
NAME_OF_CURRENT_TRACE_FILE is a standard name of current trace file 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 name of current trace file FM, simply by entering the name NAME_OF_CURRENT_TRACE_FILE into the relevant SAP transaction such as SE37 or SE38.
Function Group: STR1
Program Name: SAPLSTR1
Main Program: SAPLSTR1
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function NAME_OF_CURRENT_TRACE_FILE 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 'NAME_OF_CURRENT_TRACE_FILE'".
IMPORTING
PATHNAME = "
EXCEPTIONS
BUFFER_OVERFLOW = 1
EXPORTING Parameters details for NAME_OF_CURRENT_TRACE_FILE
PATHNAME -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
BUFFER_OVERFLOW -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for NAME_OF_CURRENT_TRACE_FILE 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_pathname | TYPE STRING, " | |||
lv_buffer_overflow | TYPE STRING. " |
  CALL FUNCTION 'NAME_OF_CURRENT_TRACE_FILE' " |
IMPORTING | ||
PATHNAME | = lv_pathname | |
EXCEPTIONS | ||
BUFFER_OVERFLOW = 1 | ||
. " NAME_OF_CURRENT_TRACE_FILE |
ABAP code using 7.40 inline data declarations to call FM NAME_OF_CURRENT_TRACE_FILE
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