SAP SVMCRT_E2E_GET_METHOD_TRACE Function Module for
SVMCRT_E2E_GET_METHOD_TRACE is a standard svmcrt e2e get method trace 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 svmcrt e2e get method trace FM, simply by entering the name SVMCRT_E2E_GET_METHOD_TRACE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SVMCRT_E2E_ABAP
Program Name: SAPLSVMCRT_E2E_ABAP
Main Program: SAPLSVMCRT_E2E_ABAP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SVMCRT_E2E_GET_METHOD_TRACE 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 'SVMCRT_E2E_GET_METHOD_TRACE'".
EXPORTING
GUID = "
* CONN_ID = "
* CONN_CNT = "
IMPORTING
E2E_METHOD_TRACE = "
EXCEPTIONS
VMC_NOT_ACTIVE = 1 SYSTEM_FAILURE = 2 COMMUNICATION_FAILURE = 3 OTHER_FAILURE = 4
IMPORTING Parameters details for SVMCRT_E2E_GET_METHOD_TRACE
GUID -
Data type: SVMCRT_E2E_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
CONN_ID -
Data type: SVMCRT_E2E_CONN_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
CONN_CNT -
Data type: SVMCRT_E2E_CONN_COUNTEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SVMCRT_E2E_GET_METHOD_TRACE
E2E_METHOD_TRACE -
Data type: SVMCRT_E2E_METHOD_TRACE_TABLEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
VMC_NOT_ACTIVE -
Data type:Optional: No
Call by Reference: Yes
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: Yes
COMMUNICATION_FAILURE -
Data type:Optional: No
Call by Reference: Yes
OTHER_FAILURE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SVMCRT_E2E_GET_METHOD_TRACE 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_guid | TYPE SVMCRT_E2E_GUID, " | |||
| lv_vmc_not_active | TYPE SVMCRT_E2E_GUID, " | |||
| lv_e2e_method_trace | TYPE SVMCRT_E2E_METHOD_TRACE_TABLE, " | |||
| lv_conn_id | TYPE SVMCRT_E2E_CONN_ID, " | |||
| lv_system_failure | TYPE SVMCRT_E2E_CONN_ID, " | |||
| lv_conn_cnt | TYPE SVMCRT_E2E_CONN_COUNTER, " | |||
| lv_communication_failure | TYPE SVMCRT_E2E_CONN_COUNTER, " | |||
| lv_other_failure | TYPE SVMCRT_E2E_CONN_COUNTER. " |
|   CALL FUNCTION 'SVMCRT_E2E_GET_METHOD_TRACE' " |
| EXPORTING | ||
| GUID | = lv_guid | |
| CONN_ID | = lv_conn_id | |
| CONN_CNT | = lv_conn_cnt | |
| IMPORTING | ||
| E2E_METHOD_TRACE | = lv_e2e_method_trace | |
| EXCEPTIONS | ||
| VMC_NOT_ACTIVE = 1 | ||
| SYSTEM_FAILURE = 2 | ||
| COMMUNICATION_FAILURE = 3 | ||
| OTHER_FAILURE = 4 | ||
| . " SVMCRT_E2E_GET_METHOD_TRACE | ||
ABAP code using 7.40 inline data declarations to call FM SVMCRT_E2E_GET_METHOD_TRACE
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