SAP BBP_LA_UTILITY_LOCK Function Module for perform locking
BBP_LA_UTILITY_LOCK is a standard bbp la utility 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 perform locking 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 bbp la utility lock FM, simply by entering the name BBP_LA_UTILITY_LOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_LA_UTILITY
Program Name: SAPLBBP_LA_UTILITY
Main Program: SAPLBBP_LA_UTILITY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_LA_UTILITY_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 'BBP_LA_UTILITY_LOCK'"perform locking.
EXPORTING
* I_LOCK_PDAUC = "Single-Character Flag
* I_AUC_ITEM_GUID = "Globally Unique identifier
* I_RETRY = 'X' "Single-character flag
* I_LANGU = SY-LANGU "R/3 System, current language
* I_LOCK_AUCTION = "Single-Character Flag
* I_LOCK_ALL_CLIENT = "Single-Character Flag
* I_LOCK_ONE_CLIENT = "Single-Character Flag
* I_LOCK_LINE_ITEM = "Single-Character Flag
* I_LOCK_ALL_RETRIEVAL = "Single-Character Flag
* I_LOCK_RETRIEVAL = "Single-Character Flag
* I_AUC_GUID = "Globally Unique identifier
* I_CLIENT_GUID = "Globally Unique identifier
IMPORTING
E_SUBRC = "Return Value, Return Value After ABAP Statements
TABLES
* ET_MESSAGES = "Error Messages
IMPORTING Parameters details for BBP_LA_UTILITY_LOCK
I_LOCK_PDAUC - Single-Character Flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_AUC_ITEM_GUID - Globally Unique identifier
Data type: BBP_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RETRY - Single-character flag
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LANGU - R/3 System, current language
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LOCK_AUCTION - Single-Character Flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LOCK_ALL_CLIENT - Single-Character Flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LOCK_ONE_CLIENT - Single-Character Flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LOCK_LINE_ITEM - Single-Character Flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LOCK_ALL_RETRIEVAL - Single-Character Flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LOCK_RETRIEVAL - Single-Character Flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_AUC_GUID - Globally Unique identifier
Data type: BBP_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CLIENT_GUID - Globally Unique identifier
Data type: BBP_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_LA_UTILITY_LOCK
E_SUBRC - Return Value, Return Value After ABAP Statements
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_LA_UTILITY_LOCK
ET_MESSAGES - Error Messages
Data type: BBP_MESSAGESOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_LA_UTILITY_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_e_subrc | TYPE SY-SUBRC, " | |||
| lt_et_messages | TYPE STANDARD TABLE OF BBP_MESSAGES, " | |||
| lv_i_lock_pdauc | TYPE CHAR1, " | |||
| lv_i_auc_item_guid | TYPE BBP_GUID, " | |||
| lv_i_retry | TYPE CHAR1, " 'X' | |||
| lv_i_langu | TYPE SY-LANGU, " SY-LANGU | |||
| lv_i_lock_auction | TYPE CHAR1, " | |||
| lv_i_lock_all_client | TYPE CHAR1, " | |||
| lv_i_lock_one_client | TYPE CHAR1, " | |||
| lv_i_lock_line_item | TYPE CHAR1, " | |||
| lv_i_lock_all_retrieval | TYPE CHAR1, " | |||
| lv_i_lock_retrieval | TYPE CHAR1, " | |||
| lv_i_auc_guid | TYPE BBP_GUID, " | |||
| lv_i_client_guid | TYPE BBP_GUID. " |
|   CALL FUNCTION 'BBP_LA_UTILITY_LOCK' "perform locking |
| EXPORTING | ||
| I_LOCK_PDAUC | = lv_i_lock_pdauc | |
| I_AUC_ITEM_GUID | = lv_i_auc_item_guid | |
| I_RETRY | = lv_i_retry | |
| I_LANGU | = lv_i_langu | |
| I_LOCK_AUCTION | = lv_i_lock_auction | |
| I_LOCK_ALL_CLIENT | = lv_i_lock_all_client | |
| I_LOCK_ONE_CLIENT | = lv_i_lock_one_client | |
| I_LOCK_LINE_ITEM | = lv_i_lock_line_item | |
| I_LOCK_ALL_RETRIEVAL | = lv_i_lock_all_retrieval | |
| I_LOCK_RETRIEVAL | = lv_i_lock_retrieval | |
| I_AUC_GUID | = lv_i_auc_guid | |
| I_CLIENT_GUID | = lv_i_client_guid | |
| IMPORTING | ||
| E_SUBRC | = lv_e_subrc | |
| TABLES | ||
| ET_MESSAGES | = lt_et_messages | |
| . " BBP_LA_UTILITY_LOCK | ||
ABAP code using 7.40 inline data declarations to call FM BBP_LA_UTILITY_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.| "SELECT single SUBRC FROM SY INTO @DATA(ld_e_subrc). | ||||
| DATA(ld_i_retry) | = 'X'. | |||
| "SELECT single LANGU FROM SY INTO @DATA(ld_i_langu). | ||||
| DATA(ld_i_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects