SAP UPC_TRACE_INFO_GET Function Module for GUID and CALLNR
UPC_TRACE_INFO_GET is a standard upc trace info get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for GUID and CALLNR 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 upc trace info get FM, simply by entering the name UPC_TRACE_INFO_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPC_TRACE
Program Name: SAPLUPC_TRACE
Main Program: SAPLUPC_TRACE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPC_TRACE_INFO_GET 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 'UPC_TRACE_INFO_GET'"GUID and CALLNR.
IMPORTING
E_GUID = "BW Generation Tool: GUID in Compressed Form (CHAR25)
E_CALLNR = "Call Number
EXPORTING Parameters details for UPC_TRACE_INFO_GET
E_GUID - BW Generation Tool: GUID in Compressed Form (CHAR25)
Data type: RSSGUID25Optional: No
Call by Reference: Yes
E_CALLNR - Call Number
Data type: UPC_Y_CALLNROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for UPC_TRACE_INFO_GET 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_e_guid | TYPE RSSGUID25, " | |||
| lv_e_callnr | TYPE UPC_Y_CALLNR. " |
|   CALL FUNCTION 'UPC_TRACE_INFO_GET' "GUID and CALLNR |
| IMPORTING | ||
| E_GUID | = lv_e_guid | |
| E_CALLNR | = lv_e_callnr | |
| . " UPC_TRACE_INFO_GET | ||
ABAP code using 7.40 inline data declarations to call FM UPC_TRACE_INFO_GET
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