SAP COPA_SDTRACE_LOG_GET_ITEMS Function Module for
COPA_SDTRACE_LOG_GET_ITEMS is a standard copa sdtrace log get items 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 copa sdtrace log get items FM, simply by entering the name COPA_SDTRACE_LOG_GET_ITEMS into the relevant SAP transaction such as SE37 or SE38.
Function Group: KEI3
Program Name: SAPLKEI3
Main Program: SAPLKEI3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COPA_SDTRACE_LOG_GET_ITEMS 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 'COPA_SDTRACE_LOG_GET_ITEMS'".
EXPORTING
I_TABNAME = "Table Name
IMPORTING
ET_ITEM = "
IMPORTING Parameters details for COPA_SDTRACE_LOG_GET_ITEMS
I_TABNAME - Table Name
Data type: DD03P-TABNAMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for COPA_SDTRACE_LOG_GET_ITEMS
ET_ITEM -
Data type: RKEI1_YT_WAOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for COPA_SDTRACE_LOG_GET_ITEMS 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_et_item | TYPE RKEI1_YT_WA, " | |||
| lv_i_tabname | TYPE DD03P-TABNAME. " |
|   CALL FUNCTION 'COPA_SDTRACE_LOG_GET_ITEMS' " |
| EXPORTING | ||
| I_TABNAME | = lv_i_tabname | |
| IMPORTING | ||
| ET_ITEM | = lv_et_item | |
| . " COPA_SDTRACE_LOG_GET_ITEMS | ||
ABAP code using 7.40 inline data declarations to call FM COPA_SDTRACE_LOG_GET_ITEMS
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.| "SELECT single TABNAME FROM DD03P INTO @DATA(ld_i_tabname). | ||||
Search for further information about these or an SAP related objects