SAP C14H_LOCK_RECORD Function Module for NOTRANSL: EHS: Sperren eines Datensatzes aus einer Tabelle
C14H_LOCK_RECORD is a standard c14h lock record SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: EHS: Sperren eines Datensatzes aus einer Tabelle 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 c14h lock record FM, simply by entering the name C14H_LOCK_RECORD into the relevant SAP transaction such as SE37 or SE38.
Function Group: C14H
Program Name: SAPLC14H
Main Program: SAPLC14H
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function C14H_LOCK_RECORD 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 'C14H_LOCK_RECORD'"NOTRANSL: EHS: Sperren eines Datensatzes aus einer Tabelle.
EXPORTING
I_TABLENAME = "
I_RECN = "Sequential Number of Data Record
I_OBJECTNAME = "Generic Type
CHANGING
X_FLG_ERROR = "
IMPORTING Parameters details for C14H_LOCK_RECORD
I_TABLENAME -
Data type: ESP1_TAB_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_RECN - Sequential Number of Data Record
Data type: RCGUKEY-RECNOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJECTNAME - Generic Type
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for C14H_LOCK_RECORD
X_FLG_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for C14H_LOCK_RECORD 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_i_tablename | TYPE ESP1_TAB_NAME, " | |||
| lv_x_flg_error | TYPE ESP1_TAB_NAME, " | |||
| lv_i_recn | TYPE RCGUKEY-RECN, " | |||
| lv_i_objectname | TYPE C. " |
|   CALL FUNCTION 'C14H_LOCK_RECORD' "NOTRANSL: EHS: Sperren eines Datensatzes aus einer Tabelle |
| EXPORTING | ||
| I_TABLENAME | = lv_i_tablename | |
| I_RECN | = lv_i_recn | |
| I_OBJECTNAME | = lv_i_objectname | |
| CHANGING | ||
| X_FLG_ERROR | = lv_x_flg_error | |
| . " C14H_LOCK_RECORD | ||
ABAP code using 7.40 inline data declarations to call FM C14H_LOCK_RECORD
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 RECN FROM RCGUKEY INTO @DATA(ld_i_recn). | ||||
Search for further information about these or an SAP related objects