SAP DEQUEUE_EBBPD_ES_EEWA Function Module for Release lock on object EBBPD_ES_EEWA









DEQUEUE_EBBPD_ES_EEWA is a standard dequeue ebbpd es eewa 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 EBBPD_ES_EEWA 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 ebbpd es eewa FM, simply by entering the name DEQUEUE_EBBPD_ES_EEWA into the relevant SAP transaction such as SE37 or SE38.

Function Group: /1BCDWBEN/BEN0002
Program Name: /1BCDWBEN/SAPLBEN0002
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DEQUEUE_EBBPD_ES_EEWA 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_EBBPD_ES_EEWA'"Release lock on object EBBPD_ES_EEWA
EXPORTING
* MODE_BBPD_ES_EEWA = 'E' "Lock mode for table BBPD_ES_EEWA
* CLIENT = SY-MANDT "01th enqueue argument
* PARTNER_GUID = "02th enqueue argument
* ADDRESS_GUID = "03th enqueue argument
* X_PARTNER_GUID = ' ' "Fill argument 02 with initial value?
* X_ADDRESS_GUID = ' ' "Fill argument 03 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
.



IMPORTING Parameters details for DEQUEUE_EBBPD_ES_EEWA

MODE_BBPD_ES_EEWA - Lock mode for table BBPD_ES_EEWA

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

CLIENT - 01th enqueue argument

Data type: BBPD_ES_EEWA-CLIENT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

PARTNER_GUID - 02th enqueue argument

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

ADDRESS_GUID - 03th enqueue argument

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

X_PARTNER_GUID - Fill argument 02 with initial value?

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

X_ADDRESS_GUID - 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: DDENQCOLL
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for DEQUEUE_EBBPD_ES_EEWA 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_bbpd_es_eewa  TYPE ENQMODE, "   'E'
lv_client  TYPE BBPD_ES_EEWA-CLIENT, "   SY-MANDT
lv_partner_guid  TYPE BBPD_ES_EEWA-PARTNER_GUID, "   
lv_address_guid  TYPE BBPD_ES_EEWA-ADDRESS_GUID, "   
lv_x_partner_guid  TYPE BBPD_ES_EEWA, "   SPACE
lv_x_address_guid  TYPE BBPD_ES_EEWA, "   SPACE
lv__scope  TYPE BBPD_ES_EEWA, "   '3'
lv__synchron  TYPE BBPD_ES_EEWA, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'DEQUEUE_EBBPD_ES_EEWA'  "Release lock on object EBBPD_ES_EEWA
    EXPORTING
         MODE_BBPD_ES_EEWA = lv_mode_bbpd_es_eewa
         CLIENT = lv_client
         PARTNER_GUID = lv_partner_guid
         ADDRESS_GUID = lv_address_guid
         X_PARTNER_GUID = lv_x_partner_guid
         X_ADDRESS_GUID = lv_x_address_guid
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
. " DEQUEUE_EBBPD_ES_EEWA




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_EBBPD_ES_EEWA

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_bbpd_es_eewa) = 'E'.
 
"SELECT single CLIENT FROM BBPD_ES_EEWA INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
"SELECT single PARTNER_GUID FROM BBPD_ES_EEWA INTO @DATA(ld_partner_guid).
 
"SELECT single ADDRESS_GUID FROM BBPD_ES_EEWA INTO @DATA(ld_address_guid).
 
DATA(ld_x_partner_guid) = ' '.
 
DATA(ld_x_address_guid) = ' '.
 
DATA(ld__scope) = '3'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!