SAP DEQUEUE_E_OIU_CUSPAM Function Module for Release lock on object E_OIU_CUSPAM
DEQUEUE_E_OIU_CUSPAM is a standard dequeue e oiu cuspam 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 E_OIU_CUSPAM 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 e oiu cuspam FM, simply by entering the name DEQUEUE_E_OIU_CUSPAM into the relevant SAP transaction such as SE37 or SE38.
Function Group: /1BCDWBEN/OEN0001
Program Name: /1BCDWBEN/SAPLOEN0001
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DEQUEUE_E_OIU_CUSPAM 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_E_OIU_CUSPAM'"Release lock on object E_OIU_CUSPAM.
EXPORTING
* MODE_OIU_PR_CUSPAMH = 'E' "Lock mode for table OIU_PR_CUSPAMH
* MANDT = SY-MANDT "01th enqueue argument
* GPLT_PAM_CD = "02th enqueue argument
* EFF_FROM_DT = "03th enqueue argument
* X_GPLT_PAM_CD = ' ' "Fill argument 02 with initial value?
* X_EFF_FROM_DT = ' ' "Fill argument 03 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
IMPORTING Parameters details for DEQUEUE_E_OIU_CUSPAM
MODE_OIU_PR_CUSPAMH - Lock mode for table OIU_PR_CUSPAMH
Data type: ENQMODEDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MANDT - 01th enqueue argument
Data type: OIU_PR_CUSPAMH-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
GPLT_PAM_CD - 02th enqueue argument
Data type: OIU_PR_CUSPAMH-GPLT_PAM_CDOptional: Yes
Call by Reference: No ( called with pass by value option)
EFF_FROM_DT - 03th enqueue argument
Data type: OIU_PR_CUSPAMH-EFF_FROM_DTOptional: Yes
Call by Reference: No ( called with pass by value option)
X_GPLT_PAM_CD - Fill argument 02 with initial value?
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_EFF_FROM_DT - 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_E_OIU_CUSPAM 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_oiu_pr_cuspamh | TYPE ENQMODE, " 'E' | |||
| lv_mandt | TYPE OIU_PR_CUSPAMH-MANDT, " SY-MANDT | |||
| lv_gplt_pam_cd | TYPE OIU_PR_CUSPAMH-GPLT_PAM_CD, " | |||
| lv_eff_from_dt | TYPE OIU_PR_CUSPAMH-EFF_FROM_DT, " | |||
| lv_x_gplt_pam_cd | TYPE OIU_PR_CUSPAMH, " SPACE | |||
| lv_x_eff_from_dt | TYPE OIU_PR_CUSPAMH, " SPACE | |||
| lv__scope | TYPE OIU_PR_CUSPAMH, " '3' | |||
| lv__synchron | TYPE OIU_PR_CUSPAMH, " SPACE | |||
| lv__collect | TYPE DDENQCOLL. " ' ' |
|   CALL FUNCTION 'DEQUEUE_E_OIU_CUSPAM' "Release lock on object E_OIU_CUSPAM |
| EXPORTING | ||
| MODE_OIU_PR_CUSPAMH | = lv_mode_oiu_pr_cuspamh | |
| MANDT | = lv_mandt | |
| GPLT_PAM_CD | = lv_gplt_pam_cd | |
| EFF_FROM_DT | = lv_eff_from_dt | |
| X_GPLT_PAM_CD | = lv_x_gplt_pam_cd | |
| X_EFF_FROM_DT | = lv_x_eff_from_dt | |
| _SCOPE | = lv__scope | |
| _SYNCHRON | = lv__synchron | |
| _COLLECT | = lv__collect | |
| . " DEQUEUE_E_OIU_CUSPAM | ||
ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_OIU_CUSPAM
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_oiu_pr_cuspamh) | = 'E'. | |||
| "SELECT single MANDT FROM OIU_PR_CUSPAMH INTO @DATA(ld_mandt). | ||||
| DATA(ld_mandt) | = SY-MANDT. | |||
| "SELECT single GPLT_PAM_CD FROM OIU_PR_CUSPAMH INTO @DATA(ld_gplt_pam_cd). | ||||
| "SELECT single EFF_FROM_DT FROM OIU_PR_CUSPAMH INTO @DATA(ld_eff_from_dt). | ||||
| DATA(ld_x_gplt_pam_cd) | = ' '. | |||
| DATA(ld_x_eff_from_dt) | = ' '. | |||
| DATA(ld__scope) | = '3'. | |||
| DATA(ld__synchron) | = ' '. | |||
| DATA(ld__collect) | = ' '. | |||
Search for further information about these or an SAP related objects