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

Function SUSG_API_LOCK 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 'SUSG_API_LOCK'"Usage Data: RFC API Lock.
EXPORTING
USGID = "
EXCEPTIONS
LOCK_FAILURE = 1
IMPORTING Parameters details for SUSG_API_LOCK
USGID -
Data type: SUSG_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
LOCK_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SUSG_API_LOCK 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_usgid | TYPE SUSG_ID, " | |||
| lv_lock_failure | TYPE SUSG_ID. " |
|   CALL FUNCTION 'SUSG_API_LOCK' "Usage Data: RFC API Lock |
| EXPORTING | ||
| USGID | = lv_usgid | |
| EXCEPTIONS | ||
| LOCK_FAILURE = 1 | ||
| . " SUSG_API_LOCK | ||
ABAP code using 7.40 inline data declarations to call FM SUSG_API_LOCK
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