SAP DEQUEUE_MEREP_505 Function Module for Release lock on object MEREP_505









DEQUEUE_MEREP_505 is a standard dequeue merep 505 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 MEREP_505 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 merep 505 FM, simply by entering the name DEQUEUE_MEREP_505 into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_MEREP_505 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_MEREP_505'"Release lock on object MEREP_505
EXPORTING
* MODE_MEREP_505 = 'E' "Lock mode for table MEREP_505
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* MANDT = SY-MANDT "01th enqueue argument
* DIRECTION = "02th enqueue argument
* MBL_ID = "03th enqueue argument
* SEQNO = "04th enqueue argument
* X_DIRECTION = ' ' "Fill argument 02 with initial value?
* X_MBL_ID = ' ' "Fill argument 03 with initial value?
* X_SEQNO = ' ' "Fill argument 04 with initial value?
* _SCOPE = '3' "
.



IMPORTING Parameters details for DEQUEUE_MEREP_505

MODE_MEREP_505 - Lock mode for table MEREP_505

Data type: ENQMODE
Default: 'E'
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)

MANDT - 01th enqueue argument

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

DIRECTION - 02th enqueue argument

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

MBL_ID - 03th enqueue argument

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

SEQNO - 04th enqueue argument

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

X_DIRECTION - Fill argument 02 with initial value?

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

X_MBL_ID - Fill argument 03 with initial value?

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

X_SEQNO - Fill argument 04 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)

Copy and paste ABAP code example for DEQUEUE_MEREP_505 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_merep_505  TYPE ENQMODE, "   'E'
lv__synchron  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_mandt  TYPE MEREP_505-MANDT, "   SY-MANDT
lv_direction  TYPE MEREP_505-DIRECTION, "   
lv_mbl_id  TYPE MEREP_505-MBL_ID, "   
lv_seqno  TYPE MEREP_505-SEQNO, "   
lv_x_direction  TYPE MEREP_505, "   SPACE
lv_x_mbl_id  TYPE MEREP_505, "   SPACE
lv_x_seqno  TYPE MEREP_505, "   SPACE
lv__scope  TYPE MEREP_505. "   '3'

  CALL FUNCTION 'DEQUEUE_MEREP_505'  "Release lock on object MEREP_505
    EXPORTING
         MODE_MEREP_505 = lv_mode_merep_505
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         MANDT = lv_mandt
         DIRECTION = lv_direction
         MBL_ID = lv_mbl_id
         SEQNO = lv_seqno
         X_DIRECTION = lv_x_direction
         X_MBL_ID = lv_x_mbl_id
         X_SEQNO = lv_x_seqno
         _SCOPE = lv__scope
. " DEQUEUE_MEREP_505




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_MEREP_505

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_merep_505) = 'E'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 
"SELECT single MANDT FROM MEREP_505 INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single DIRECTION FROM MEREP_505 INTO @DATA(ld_direction).
 
"SELECT single MBL_ID FROM MEREP_505 INTO @DATA(ld_mbl_id).
 
"SELECT single SEQNO FROM MEREP_505 INTO @DATA(ld_seqno).
 
DATA(ld_x_direction) = ' '.
 
DATA(ld_x_mbl_id) = ' '.
 
DATA(ld_x_seqno) = ' '.
 
DATA(ld__scope) = '3'.
 


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!