SAP CMS_OBJ_OBJECT_VALDTY_LOCK Function Module for Lock the Validity of CMS objects
CMS_OBJ_OBJECT_VALDTY_LOCK is a standard cms obj object valdty 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 Lock the Validity of CMS objects 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 cms obj object valdty lock FM, simply by entering the name CMS_OBJ_OBJECT_VALDTY_LOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_OBJ_OBJECT_VALDTY
Program Name: SAPLCMS_OBJ_OBJECT_VALDTY
Main Program: SAPLCMS_OBJ_OBJECT_VALDTY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMS_OBJ_OBJECT_VALDTY_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 'CMS_OBJ_OBJECT_VALDTY_LOCK'"Lock the Validity of CMS objects.
EXPORTING
I_TAB_OBJ_VALDTY = "CMS-Basel II: Object GUID
IMPORTING
E_TAB_RC = "Return Code and corresponding Message
IMPORTING Parameters details for CMS_OBJ_OBJECT_VALDTY_LOCK
I_TAB_OBJ_VALDTY - CMS-Basel II: Object GUID
Data type: CMS_TAB_OBJ_VALDTYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CMS_OBJ_OBJECT_VALDTY_LOCK
E_TAB_RC - Return Code and corresponding Message
Data type: CMS_TAB_MSG_COL_MESSAGEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CMS_OBJ_OBJECT_VALDTY_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_tab_rc | TYPE CMS_TAB_MSG_COL_MESSAGE, " | |||
| lv_i_tab_obj_valdty | TYPE CMS_TAB_OBJ_VALDTY. " |
|   CALL FUNCTION 'CMS_OBJ_OBJECT_VALDTY_LOCK' "Lock the Validity of CMS objects |
| EXPORTING | ||
| I_TAB_OBJ_VALDTY | = lv_i_tab_obj_valdty | |
| IMPORTING | ||
| E_TAB_RC | = lv_e_tab_rc | |
| . " CMS_OBJ_OBJECT_VALDTY_LOCK | ||
ABAP code using 7.40 inline data declarations to call FM CMS_OBJ_OBJECT_VALDTY_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