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

Function ANST_UPLOAD_USAGE_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 'ANST_UPLOAD_USAGE_TRACE'"ANST Usage trace upload.
EXPORTING
* IM_TRANS_CODE = "Transaction Code
* IM_SCHEDULE_JOB = "Single-Character Flag
* IM_SUSG_ID = "Usage Data: Description
* IM_REQUEST_TYPE = "Request Type
* IM_LASTUSED = "no of days
* IM_DATE_FROM = "
* IM_DATE_TO = "
IMPORTING
LV_CONF = "
EX_GUID = "Anst GUID Trace
EX_JOB_SCHEDULED = "Single-Character Flag
EX_MSG = "Char255
EX_DESCRIPTION = "Trace Description
IMPORTING Parameters details for ANST_UPLOAD_USAGE_TRACE
IM_TRANS_CODE - Transaction Code
Data type: SUSG_SUB-ROOTNAMEOptional: Yes
Call by Reference: Yes
IM_SCHEDULE_JOB - Single-Character Flag
Data type: CHAR1Optional: Yes
Call by Reference: Yes
IM_SUSG_ID - Usage Data: Description
Data type: SUSG_ADMIN-DESCRIPTIONOptional: Yes
Call by Reference: Yes
IM_REQUEST_TYPE - Request Type
Data type: SUSG_SUB-ROOTTYPEOptional: Yes
Call by Reference: Yes
IM_LASTUSED - no of days
Data type: IOptional: Yes
Call by Reference: Yes
IM_DATE_FROM -
Data type: SUSG_ADMIN-DATE_FROMOptional: Yes
Call by Reference: Yes
IM_DATE_TO -
Data type: SUSG_ADMIN-DATE_TOOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ANST_UPLOAD_USAGE_TRACE
LV_CONF -
Data type: IOptional: No
Call by Reference: Yes
EX_GUID - Anst GUID Trace
Data type: ANST_GUIDOptional: No
Call by Reference: Yes
EX_JOB_SCHEDULED - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
EX_MSG - Char255
Data type: CHAR255Optional: No
Call by Reference: Yes
EX_DESCRIPTION - Trace Description
Data type: ANST_DESCRIPTIONOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ANST_UPLOAD_USAGE_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_lv_conf | TYPE I, " | |||
| lv_im_trans_code | TYPE SUSG_SUB-ROOTNAME, " | |||
| lv_ex_guid | TYPE ANST_GUID, " | |||
| lv_im_schedule_job | TYPE CHAR1, " | |||
| lv_im_susg_id | TYPE SUSG_ADMIN-DESCRIPTION, " | |||
| lv_ex_job_scheduled | TYPE CHAR1, " | |||
| lv_ex_msg | TYPE CHAR255, " | |||
| lv_im_request_type | TYPE SUSG_SUB-ROOTTYPE, " | |||
| lv_im_lastused | TYPE I, " | |||
| lv_ex_description | TYPE ANST_DESCRIPTION, " | |||
| lv_im_date_from | TYPE SUSG_ADMIN-DATE_FROM, " | |||
| lv_im_date_to | TYPE SUSG_ADMIN-DATE_TO. " |
|   CALL FUNCTION 'ANST_UPLOAD_USAGE_TRACE' "ANST Usage trace upload |
| EXPORTING | ||
| IM_TRANS_CODE | = lv_im_trans_code | |
| IM_SCHEDULE_JOB | = lv_im_schedule_job | |
| IM_SUSG_ID | = lv_im_susg_id | |
| IM_REQUEST_TYPE | = lv_im_request_type | |
| IM_LASTUSED | = lv_im_lastused | |
| IM_DATE_FROM | = lv_im_date_from | |
| IM_DATE_TO | = lv_im_date_to | |
| IMPORTING | ||
| LV_CONF | = lv_lv_conf | |
| EX_GUID | = lv_ex_guid | |
| EX_JOB_SCHEDULED | = lv_ex_job_scheduled | |
| EX_MSG | = lv_ex_msg | |
| EX_DESCRIPTION | = lv_ex_description | |
| . " ANST_UPLOAD_USAGE_TRACE | ||
ABAP code using 7.40 inline data declarations to call FM ANST_UPLOAD_USAGE_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.| "SELECT single ROOTNAME FROM SUSG_SUB INTO @DATA(ld_im_trans_code). | ||||
| "SELECT single DESCRIPTION FROM SUSG_ADMIN INTO @DATA(ld_im_susg_id). | ||||
| "SELECT single ROOTTYPE FROM SUSG_SUB INTO @DATA(ld_im_request_type). | ||||
| "SELECT single DATE_FROM FROM SUSG_ADMIN INTO @DATA(ld_im_date_from). | ||||
| "SELECT single DATE_TO FROM SUSG_ADMIN INTO @DATA(ld_im_date_to). | ||||
Search for further information about these or an SAP related objects