SAP EHSB_LOCKFUNCTION_NAME_BUILD Function Module for NOTRANSL: EHS: den Name der (Ent-)Sperrfunktion berechnen

Search SAP Function Modules

EHSB_LOCKFUNCTION_NAME_BUILD is a standard ehsb lockfunction name build 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: den Name der (Ent-)Sperrfunktion berechnen 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 ehsb lockfunction name build FM, simply by entering the name EHSB_LOCKFUNCTION_NAME_BUILD into the relevant SAP transaction such as SE37 or SE38.

Function Group: EHSB
Program Name: SAPLEHSB
Main Program: SAPLEHSB
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EHSB_LOCKFUNCTION_NAME_BUILD 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 'EHSB_LOCKFUNCTION_NAME_BUILD'"NOTRANSL: EHS: den Name der (Ent-)Sperrfunktion berechnen
  EXPORTING
   I_FLG_ENQUEUE =  "
   I_LOCKMOD =  "Lock Mode
   I_TABLENAME =  "Table Name
*  I_LOCK_OBJ_NAME_PREFIX = 'ESL' "
*  I_FLG_HOLD_PREFIX = ESP1_FALSE "
*  I_FLG_COMPUTE_PREFIX = ESP1_FALSE "
*  I_S_LOCK_OBJECT =  "
*  I_X_LOCK_OBJECT =  "
*  I_ENDING =  "

 IMPORTING
   E_FUNCTION_NAME =  "

EXCEPTIONS
   ILLEGAL_INPUT = 1    INTERNAL_ERROR = 2 

.

IMPORTING Parameters details for EHSB_LOCKFUNCTION_NAME_BUILD

I_FLG_ENQUEUE -

Data type: ESP1_BOOLEAN
Optional: No
Call by Reference: No ( called with pass by value option)

I_LOCKMOD - Lock Mode

Data type: RCGSTDBUF-LOCKMOD
Optional: No
Call by Reference: No ( called with pass by value option)

I_TABLENAME - Table Name

Data type: ESP1_TAB_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

I_LOCK_OBJ_NAME_PREFIX -

Data type: ESP1_LOCK_OBJECT_PREFIX
Default: 'ESL'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_HOLD_PREFIX -

Data type: ESP1_BOOLEAN
Default: ESP1_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_COMPUTE_PREFIX -

Data type: ESP1_BOOLEAN
Default: ESP1_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_S_LOCK_OBJECT -

Data type: ESP1_LOCK_OBJ
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_X_LOCK_OBJECT -

Data type: ESP1_LOCK_OBJ
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ENDING -

Data type: ESP1_FUNC_NAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for EHSB_LOCKFUNCTION_NAME_BUILD

E_FUNCTION_NAME -

Data type: ESP1_FUNC_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ILLEGAL_INPUT - Invalid Entry

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INTERNAL_ERROR - Internal System Error

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for EHSB_LOCKFUNCTION_NAME_BUILD 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.

ABAP code using 7.40 inline data declarations to call FM EHSB_LOCKFUNCTION_NAME_BUILD

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