SAP RKE_ENQUEUE_CRITERIA Function Module for









RKE_ENQUEUE_CRITERIA is a standard rke enqueue criteria 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 rke enqueue criteria FM, simply by entering the name RKE_ENQUEUE_CRITERIA into the relevant SAP transaction such as SE37 or SE38.

Function Group: KEM1
Program Name: SAPLKEM1
Main Program:
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RKE_ENQUEUE_CRITERIA 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 'RKE_ENQUEUE_CRITERIA'"
  EXPORTING
*  I_ACTION = 'E' "
*  _MODE = 'E' "
   I_ERKRS =  "
   I_PA_TYPE =  "
*  I_PALEDGER = ' ' "
   I_PLIKZ =  "
*  I_VRGAR = ' ' "
*  I_VERSI = ' ' "
*  _WAIT = ' ' "
*  _SCOPE = '2' "

TABLES
*  T_MERK =  "

EXCEPTIONS
   FOREIGN_LOCK = 1    SYSTEM_FAILURE = 2    T_MERK_FILLED_WRONG = 3
.



IMPORTING Parameters details for RKE_ENQUEUE_CRITERIA

I_ACTION -

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

_MODE -

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

I_ERKRS -

Data type: TKEB-ERKRS
Optional: No
Call by Reference: No ( called with pass by value option)

I_PA_TYPE -

Data type: CEDDB-PA_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

I_PALEDGER -

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

I_PLIKZ -

Data type: CEST0-PLIKZ
Optional: No
Call by Reference: No ( called with pass by value option)

I_VRGAR -

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

I_VERSI -

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

_WAIT -

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

_SCOPE -

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

TABLES Parameters details for RKE_ENQUEUE_CRITERIA

T_MERK -

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

EXCEPTIONS details

FOREIGN_LOCK -

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

SYSTEM_FAILURE -

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

T_MERK_FILLED_WRONG -

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

Copy and paste ABAP code example for RKE_ENQUEUE_CRITERIA 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:
lt_t_merk  TYPE STANDARD TABLE OF CEPL5, "   
lv_i_action  TYPE C, "   'E'
lv_foreign_lock  TYPE C, "   
lv__mode  TYPE C, "   'E'
lv_i_erkrs  TYPE TKEB-ERKRS, "   
lv_system_failure  TYPE TKEB, "   
lv_i_pa_type  TYPE CEDDB-PA_TYPE, "   
lv_t_merk_filled_wrong  TYPE CEDDB, "   
lv_i_paledger  TYPE CEST0-PALEDGER, "   SPACE
lv_i_plikz  TYPE CEST0-PLIKZ, "   
lv_i_vrgar  TYPE CEST0-VRGAR, "   SPACE
lv_i_versi  TYPE CEST0-VERSI, "   SPACE
lv__wait  TYPE CEST0, "   SPACE
lv__scope  TYPE CEST0. "   '2'

  CALL FUNCTION 'RKE_ENQUEUE_CRITERIA'  "
    EXPORTING
         I_ACTION = lv_i_action
         _MODE = lv__mode
         I_ERKRS = lv_i_erkrs
         I_PA_TYPE = lv_i_pa_type
         I_PALEDGER = lv_i_paledger
         I_PLIKZ = lv_i_plikz
         I_VRGAR = lv_i_vrgar
         I_VERSI = lv_i_versi
         _WAIT = lv__wait
         _SCOPE = lv__scope
    TABLES
         T_MERK = lt_t_merk
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
        T_MERK_FILLED_WRONG = 3
. " RKE_ENQUEUE_CRITERIA




ABAP code using 7.40 inline data declarations to call FM RKE_ENQUEUE_CRITERIA

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_action) = 'E'.
 
 
DATA(ld__mode) = 'E'.
 
"SELECT single ERKRS FROM TKEB INTO @DATA(ld_i_erkrs).
 
 
"SELECT single PA_TYPE FROM CEDDB INTO @DATA(ld_i_pa_type).
 
 
"SELECT single PALEDGER FROM CEST0 INTO @DATA(ld_i_paledger).
DATA(ld_i_paledger) = ' '.
 
"SELECT single PLIKZ FROM CEST0 INTO @DATA(ld_i_plikz).
 
"SELECT single VRGAR FROM CEST0 INTO @DATA(ld_i_vrgar).
DATA(ld_i_vrgar) = ' '.
 
"SELECT single VERSI FROM CEST0 INTO @DATA(ld_i_versi).
DATA(ld_i_versi) = ' '.
 
DATA(ld__wait) = ' '.
 
DATA(ld__scope) = '2'.
 


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!