SAP FKK_S_LOCK_GET Function Module for
FKK_S_LOCK_GET is a standard fkk s lock get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fkk s lock get FM, simply by entering the name FKK_S_LOCK_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKKLOCK_SERVICE
Program Name: SAPLFKKLOCK_SERVICE
Main Program: SAPLFKLOCK
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_S_LOCK_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 'FKK_S_LOCK_GET'".
EXPORTING
I_KEYSTRUCTURE = "
* I_X_ARCHIVE_SELECT = ' ' "
* I_LOTYP = "
* I_PROID = "
* I_LOCKDATE = SY-DATLO "
* I_X_MASS_ACCESS = ' ' "
I_X_DEPENDANT_LOCKTYPES = "
* I_X_ONLY_CHECK_LOCKS = ' ' "
* I_X_REFRESH = ' ' "
* I_X_USE_FIELDLIST = ' ' "
IMPORTING
E_X_LOCK_EXIST = "
E_X_DEPENDANT_LOCK_EXIST = "
TABLES
* IT_PROID = "
* IT_LOCKREASON = "
ET_LOCKS = "
* ET_DEPENDANT_LOCKS = "
* IT_GPART = "
* ET_LOCKSH = "
EXCEPTIONS
NO_LOTYP = 1 NO_FIELD_IN_STRUCTURE = 2 EMPTY_FIELD = 3
IMPORTING Parameters details for FKK_S_LOCK_GET
I_KEYSTRUCTURE -
Data type:Optional: No
Call by Reference: Yes
I_X_ARCHIVE_SELECT -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_LOTYP -
Data type: DFKKLOCKS-LOTYPOptional: Yes
Call by Reference: Yes
I_PROID -
Data type: DFKKLOCKS-PROIDOptional: Yes
Call by Reference: Yes
I_LOCKDATE -
Data type:Default: SY-DATLO
Optional: Yes
Call by Reference: Yes
I_X_MASS_ACCESS -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_X_DEPENDANT_LOCKTYPES -
Data type: BOOLE-BOOLEOptional: No
Call by Reference: Yes
I_X_ONLY_CHECK_LOCKS -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_X_REFRESH -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_X_USE_FIELDLIST -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FKK_S_LOCK_GET
E_X_LOCK_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_X_DEPENDANT_LOCK_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FKK_S_LOCK_GET
IT_PROID -
Data type: FKKR_PROIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_LOCKREASON -
Data type: FKKR_LOCKROptional: Yes
Call by Reference: No ( called with pass by value option)
ET_LOCKS -
Data type: DFKKLOCKSOptional: No
Call by Reference: No ( called with pass by value option)
ET_DEPENDANT_LOCKS -
Data type: DFKKLOCKSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_GPART -
Data type: FKLOC_T_GPARTOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_LOCKSH -
Data type: DFKKLOCKSHOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_LOTYP -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_FIELD_IN_STRUCTURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EMPTY_FIELD -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FKK_S_LOCK_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: | ||||
| lt_it_proid | TYPE STANDARD TABLE OF FKKR_PROID, " | |||
| lv_no_lotyp | TYPE FKKR_PROID, " | |||
| lv_e_x_lock_exist | TYPE FKKR_PROID, " | |||
| lv_i_keystructure | TYPE FKKR_PROID, " | |||
| lv_i_x_archive_select | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_lotyp | TYPE DFKKLOCKS-LOTYP, " | |||
| lt_it_lockreason | TYPE STANDARD TABLE OF FKKR_LOCKR, " | |||
| lv_no_field_in_structure | TYPE FKKR_LOCKR, " | |||
| lv_e_x_dependant_lock_exist | TYPE FKKR_LOCKR, " | |||
| lv_i_proid | TYPE DFKKLOCKS-PROID, " | |||
| lt_et_locks | TYPE STANDARD TABLE OF DFKKLOCKS, " | |||
| lv_empty_field | TYPE DFKKLOCKS, " | |||
| lv_i_lockdate | TYPE DFKKLOCKS, " SY-DATLO | |||
| lt_et_dependant_locks | TYPE STANDARD TABLE OF DFKKLOCKS, " | |||
| lt_it_gpart | TYPE STANDARD TABLE OF FKLOC_T_GPART, " | |||
| lv_i_x_mass_access | TYPE BOOLE-BOOLE, " SPACE | |||
| lt_et_locksh | TYPE STANDARD TABLE OF DFKKLOCKSH, " | |||
| lv_i_x_dependant_locktypes | TYPE BOOLE-BOOLE, " | |||
| lv_i_x_only_check_locks | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_x_refresh | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_x_use_fieldlist | TYPE BOOLE-BOOLE. " SPACE |
|   CALL FUNCTION 'FKK_S_LOCK_GET' " |
| EXPORTING | ||
| I_KEYSTRUCTURE | = lv_i_keystructure | |
| I_X_ARCHIVE_SELECT | = lv_i_x_archive_select | |
| I_LOTYP | = lv_i_lotyp | |
| I_PROID | = lv_i_proid | |
| I_LOCKDATE | = lv_i_lockdate | |
| I_X_MASS_ACCESS | = lv_i_x_mass_access | |
| I_X_DEPENDANT_LOCKTYPES | = lv_i_x_dependant_locktypes | |
| I_X_ONLY_CHECK_LOCKS | = lv_i_x_only_check_locks | |
| I_X_REFRESH | = lv_i_x_refresh | |
| I_X_USE_FIELDLIST | = lv_i_x_use_fieldlist | |
| IMPORTING | ||
| E_X_LOCK_EXIST | = lv_e_x_lock_exist | |
| E_X_DEPENDANT_LOCK_EXIST | = lv_e_x_dependant_lock_exist | |
| TABLES | ||
| IT_PROID | = lt_it_proid | |
| IT_LOCKREASON | = lt_it_lockreason | |
| ET_LOCKS | = lt_et_locks | |
| ET_DEPENDANT_LOCKS | = lt_et_dependant_locks | |
| IT_GPART | = lt_it_gpart | |
| ET_LOCKSH | = lt_et_locksh | |
| EXCEPTIONS | ||
| NO_LOTYP = 1 | ||
| NO_FIELD_IN_STRUCTURE = 2 | ||
| EMPTY_FIELD = 3 | ||
| . " FKK_S_LOCK_GET | ||
ABAP code using 7.40 inline data declarations to call FM FKK_S_LOCK_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.| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_x_archive_select). | ||||
| DATA(ld_i_x_archive_select) | = ' '. | |||
| "SELECT single LOTYP FROM DFKKLOCKS INTO @DATA(ld_i_lotyp). | ||||
| "SELECT single PROID FROM DFKKLOCKS INTO @DATA(ld_i_proid). | ||||
| DATA(ld_i_lockdate) | = SY-DATLO. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_x_mass_access). | ||||
| DATA(ld_i_x_mass_access) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_x_dependant_locktypes). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_x_only_check_locks). | ||||
| DATA(ld_i_x_only_check_locks) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_x_refresh). | ||||
| DATA(ld_i_x_refresh) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_x_use_fieldlist). | ||||
| DATA(ld_i_x_use_fieldlist) | = ' '. | |||
Search for further information about these or an SAP related objects