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

Function SUCT_UPDATE_LOCKFLAG 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 'SUCT_UPDATE_LOCKFLAG'"Update Lockflags.
EXPORTING
* IV_LOCKFLAG_VALUE = '' "Single-Character Flag
* IV_CTC = '' "Single-Character Flag
* IV_GET_WHITELIST = '' "Single-Character Flag
IMPORTING
EV_RC = "Natural number
EV_MESSAGE = "Char 80
EV_SHADOWVERSDONE = "Single-Character Flag
EV_UPG_ACTIVE = "Single-Character Flag
EV_IS_SHADOW = "Single-Character Flag
TABLES
* IT_TRKORR = "Request List for Queue Calculator/Missing Support Packages
* IT_WHITELIST = "List of Table Names
IMPORTING Parameters details for SUCT_UPDATE_LOCKFLAG
IV_LOCKFLAG_VALUE - Single-Character Flag
Data type: CHAR1Default: ''
Optional: No
Call by Reference: No ( called with pass by value option)
IV_CTC - Single-Character Flag
Data type: CHAR1Default: ''
Optional: No
Call by Reference: No ( called with pass by value option)
IV_GET_WHITELIST - Single-Character Flag
Data type: CHAR1Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SUCT_UPDATE_LOCKFLAG
EV_RC - Natural number
Data type: GSUGI_PA-NR_CONVOptional: No
Call by Reference: No ( called with pass by value option)
EV_MESSAGE - Char 80
Data type: GSUGI_PA-RCMESSAGEOptional: No
Call by Reference: No ( called with pass by value option)
EV_SHADOWVERSDONE - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
EV_UPG_ACTIVE - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
EV_IS_SHADOW - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SUCT_UPDATE_LOCKFLAG
IT_TRKORR - Request List for Queue Calculator/Missing Support Packages
Data type: PATCHLISTOptional: Yes
Call by Reference: Yes
IT_WHITELIST - List of Table Names
Data type: SUGX_TNAMEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for SUCT_UPDATE_LOCKFLAG 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_ev_rc | TYPE GSUGI_PA-NR_CONV, " | |||
| lt_it_trkorr | TYPE STANDARD TABLE OF PATCHLIST, " | |||
| lv_iv_lockflag_value | TYPE CHAR1, " '' | |||
| lv_iv_ctc | TYPE CHAR1, " '' | |||
| lv_ev_message | TYPE GSUGI_PA-RCMESSAGE, " | |||
| lt_it_whitelist | TYPE STANDARD TABLE OF SUGX_TNAME, " | |||
| lv_iv_get_whitelist | TYPE CHAR1, " '' | |||
| lv_ev_shadowversdone | TYPE CHAR1, " | |||
| lv_ev_upg_active | TYPE CHAR1, " | |||
| lv_ev_is_shadow | TYPE CHAR1. " |
|   CALL FUNCTION 'SUCT_UPDATE_LOCKFLAG' "Update Lockflags |
| EXPORTING | ||
| IV_LOCKFLAG_VALUE | = lv_iv_lockflag_value | |
| IV_CTC | = lv_iv_ctc | |
| IV_GET_WHITELIST | = lv_iv_get_whitelist | |
| IMPORTING | ||
| EV_RC | = lv_ev_rc | |
| EV_MESSAGE | = lv_ev_message | |
| EV_SHADOWVERSDONE | = lv_ev_shadowversdone | |
| EV_UPG_ACTIVE | = lv_ev_upg_active | |
| EV_IS_SHADOW | = lv_ev_is_shadow | |
| TABLES | ||
| IT_TRKORR | = lt_it_trkorr | |
| IT_WHITELIST | = lt_it_whitelist | |
| . " SUCT_UPDATE_LOCKFLAG | ||
ABAP code using 7.40 inline data declarations to call FM SUCT_UPDATE_LOCKFLAG
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 NR_CONV FROM GSUGI_PA INTO @DATA(ld_ev_rc). | ||||
| DATA(ld_iv_lockflag_value) | = ''. | |||
| DATA(ld_iv_ctc) | = ''. | |||
| "SELECT single RCMESSAGE FROM GSUGI_PA INTO @DATA(ld_ev_message). | ||||
| DATA(ld_iv_get_whitelist) | = ''. | |||
Search for further information about these or an SAP related objects