SAP DEQUEUE_EOIUH_CM_BATYP Function Module for Release lock on object EOIUH_CM_BATYP
DEQUEUE_EOIUH_CM_BATYP is a standard dequeue eoiuh cm batyp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Release lock on object EOIUH_CM_BATYP 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 dequeue eoiuh cm batyp FM, simply by entering the name DEQUEUE_EOIUH_CM_BATYP into the relevant SAP transaction such as SE37 or SE38.
Function Group: /1BCDWBEN/OEN0000
Program Name: /1BCDWBEN/SAPLOEN0000
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DEQUEUE_EOIUH_CM_BATYP 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 'DEQUEUE_EOIUH_CM_BATYP'"Release lock on object EOIUH_CM_BATYP.
EXPORTING
* MODE_OIUH_CM_BATYP = 'E' "Lock mode for table OIUH_CM_BATYP
* MANDT = SY-MANDT "01th enqueue argument
* BATYP_BA_NO = "02th enqueue argument
* BATYP_BA_SEQ_NO = "03th enqueue argument
* X_BATYP_BA_NO = ' ' "Fill argument 02 with initial value?
* X_BATYP_BA_SEQ_NO = ' ' "Fill argument 03 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
IMPORTING Parameters details for DEQUEUE_EOIUH_CM_BATYP
MODE_OIUH_CM_BATYP - Lock mode for table OIUH_CM_BATYP
Data type: ENQMODEDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MANDT - 01th enqueue argument
Data type: OIUH_CM_BATYP-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
BATYP_BA_NO - 02th enqueue argument
Data type: OIUH_CM_BATYP-BATYP_BA_NOOptional: Yes
Call by Reference: No ( called with pass by value option)
BATYP_BA_SEQ_NO - 03th enqueue argument
Data type: OIUH_CM_BATYP-BATYP_BA_SEQ_NOOptional: Yes
Call by Reference: No ( called with pass by value option)
X_BATYP_BA_NO - Fill argument 02 with initial value?
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_BATYP_BA_SEQ_NO - Fill argument 03 with initial value?
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
_SCOPE -
Data type:Default: '3'
Optional: Yes
Call by Reference: No ( called with pass by value option)
_SYNCHRON - Synchonous unlock
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
_COLLECT - Initially only collect lock
Data type: DDENQCOLLDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DEQUEUE_EOIUH_CM_BATYP 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_mode_oiuh_cm_batyp | TYPE ENQMODE, " 'E' | |||
| lv_mandt | TYPE OIUH_CM_BATYP-MANDT, " SY-MANDT | |||
| lv_batyp_ba_no | TYPE OIUH_CM_BATYP-BATYP_BA_NO, " | |||
| lv_batyp_ba_seq_no | TYPE OIUH_CM_BATYP-BATYP_BA_SEQ_NO, " | |||
| lv_x_batyp_ba_no | TYPE OIUH_CM_BATYP, " SPACE | |||
| lv_x_batyp_ba_seq_no | TYPE OIUH_CM_BATYP, " SPACE | |||
| lv__scope | TYPE OIUH_CM_BATYP, " '3' | |||
| lv__synchron | TYPE OIUH_CM_BATYP, " SPACE | |||
| lv__collect | TYPE DDENQCOLL. " ' ' |
|   CALL FUNCTION 'DEQUEUE_EOIUH_CM_BATYP' "Release lock on object EOIUH_CM_BATYP |
| EXPORTING | ||
| MODE_OIUH_CM_BATYP | = lv_mode_oiuh_cm_batyp | |
| MANDT | = lv_mandt | |
| BATYP_BA_NO | = lv_batyp_ba_no | |
| BATYP_BA_SEQ_NO | = lv_batyp_ba_seq_no | |
| X_BATYP_BA_NO | = lv_x_batyp_ba_no | |
| X_BATYP_BA_SEQ_NO | = lv_x_batyp_ba_seq_no | |
| _SCOPE | = lv__scope | |
| _SYNCHRON | = lv__synchron | |
| _COLLECT | = lv__collect | |
| . " DEQUEUE_EOIUH_CM_BATYP | ||
ABAP code using 7.40 inline data declarations to call FM DEQUEUE_EOIUH_CM_BATYP
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_mode_oiuh_cm_batyp) | = 'E'. | |||
| "SELECT single MANDT FROM OIUH_CM_BATYP INTO @DATA(ld_mandt). | ||||
| DATA(ld_mandt) | = SY-MANDT. | |||
| "SELECT single BATYP_BA_NO FROM OIUH_CM_BATYP INTO @DATA(ld_batyp_ba_no). | ||||
| "SELECT single BATYP_BA_SEQ_NO FROM OIUH_CM_BATYP INTO @DATA(ld_batyp_ba_seq_no). | ||||
| DATA(ld_x_batyp_ba_no) | = ' '. | |||
| DATA(ld_x_batyp_ba_seq_no) | = ' '. | |||
| DATA(ld__scope) | = '3'. | |||
| DATA(ld__synchron) | = ' '. | |||
| DATA(ld__collect) | = ' '. | |||
Search for further information about these or an SAP related objects