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

Function SUSAGE_READ 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 'SUSAGE_READ'"Read Usage Log.
EXPORTING
I_YEAR_MONTH = "Usage in ABAP for month of an year format YYYYMM
IMPORTING
E_USAGE = "Usage in ABAP
IMPORTING Parameters details for SUSAGE_READ
I_YEAR_MONTH - Usage in ABAP for month of an year format YYYYMM
Data type: SUSAGE-CALENDAR_MONTHOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SUSAGE_READ
E_USAGE - Usage in ABAP
Data type: SUSAGE_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SUSAGE_READ 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_usage | TYPE SUSAGE_TYPE, " | |||
| lv_i_year_month | TYPE SUSAGE-CALENDAR_MONTH. " |
|   CALL FUNCTION 'SUSAGE_READ' "Read Usage Log |
| EXPORTING | ||
| I_YEAR_MONTH | = lv_i_year_month | |
| IMPORTING | ||
| E_USAGE | = lv_e_usage | |
| . " SUSAGE_READ | ||
ABAP code using 7.40 inline data declarations to call FM SUSAGE_READ
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 CALENDAR_MONTH FROM SUSAGE INTO @DATA(ld_i_year_month). | ||||
Search for further information about these or an SAP related objects