SAP CBIH_ER59_LOGLOCKMOD_SET_GET Function Module for
CBIH_ER59_LOGLOCKMOD_SET_GET is a standard cbih er59 loglockmod set get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 cbih er59 loglockmod set get FM, simply by entering the name CBIH_ER59_LOGLOCKMOD_SET_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: CBIH_ER59
Program Name: SAPLCBIH_ER59
Main Program:
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CBIH_ER59_LOGLOCKMOD_SET_GET 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 'CBIH_ER59_LOGLOCKMOD_SET_GET'".
EXPORTING
* I_FLG_GET = ESP1_TRUE "
* I_VALDAT = "
TABLES
X_API_TAB = "
IMPORTING Parameters details for CBIH_ER59_LOGLOCKMOD_SET_GET
I_FLG_GET -
Data type: ESP1_BOOLEANDefault: ESP1_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VALDAT -
Data type: CCIHT_AD10-VALFROptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CBIH_ER59_LOGLOCKMOD_SET_GET
X_API_TAB -
Data type: CIHEX_AD10API_TAB_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CBIH_ER59_LOGLOCKMOD_SET_GET 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_flg_get | TYPE ESP1_BOOLEAN, " ESP1_TRUE | |||
lt_x_api_tab | TYPE STANDARD TABLE OF CIHEX_AD10API_TAB_TYPE, " | |||
lv_i_valdat | TYPE CCIHT_AD10-VALFR. " |
  CALL FUNCTION 'CBIH_ER59_LOGLOCKMOD_SET_GET' " |
EXPORTING | ||
I_FLG_GET | = lv_i_flg_get | |
I_VALDAT | = lv_i_valdat | |
TABLES | ||
X_API_TAB | = lt_x_api_tab | |
. " CBIH_ER59_LOGLOCKMOD_SET_GET |
ABAP code using 7.40 inline data declarations to call FM CBIH_ER59_LOGLOCKMOD_SET_GET
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.DATA(ld_i_flg_get) | = ESP1_TRUE. | |||
"SELECT single VALFR FROM CCIHT_AD10 INTO @DATA(ld_i_valdat). | ||||
Search for further information about these or an SAP related objects