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

Function CRM_LOCK_OBJECT 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 'CRM_LOCK_OBJECT'"FM to Lock Business Transactions.
EXPORTING
IV_OBJECT_ID = "Object GUID in Generic Interaction Layer
IMPORTING
EV_ACTIONSUCCESSFUL = "Success Flag
EV_MESSAGE = "String
IMPORTING Parameters details for CRM_LOCK_OBJECT
IV_OBJECT_ID - Object GUID in Generic Interaction Layer
Data type: CRMT_GENIL_OBJECT_GUIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CRM_LOCK_OBJECT
EV_ACTIONSUCCESSFUL - Success Flag
Data type: ABAP_BOOLOptional: No
Call by Reference: Yes
EV_MESSAGE - String
Data type: STRINGVALOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_LOCK_OBJECT 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_iv_object_id | TYPE CRMT_GENIL_OBJECT_GUID, " | |||
| lv_ev_actionsuccessful | TYPE ABAP_BOOL, " | |||
| lv_ev_message | TYPE STRINGVAL. " |
|   CALL FUNCTION 'CRM_LOCK_OBJECT' "FM to Lock Business Transactions |
| EXPORTING | ||
| IV_OBJECT_ID | = lv_iv_object_id | |
| IMPORTING | ||
| EV_ACTIONSUCCESSFUL | = lv_ev_actionsuccessful | |
| EV_MESSAGE | = lv_ev_message | |
| . " CRM_LOCK_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM CRM_LOCK_OBJECT
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