SAP J_1I6_ENQUEUE_DEQUEUE Function Module for Enqueue / Dequeue









J_1I6_ENQUEUE_DEQUEUE is a standard j 1i6 enqueue dequeue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Enqueue / Dequeue 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 j 1i6 enqueue dequeue FM, simply by entering the name J_1I6_ENQUEUE_DEQUEUE into the relevant SAP transaction such as SE37 or SE38.

Function Group: J1I6
Program Name: SAPLJ1I6
Main Program: SAPLJ1I6
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function J_1I6_ENQUEUE_DEQUEUE 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 'J_1I6_ENQUEUE_DEQUEUE'"Enqueue / Dequeue
EXPORTING
I_ACTION = "1 = Enqueue / 2 = Dequeue
I_WERKS = "Plant
I_EXGRP = "Excise group
* I_VBELN_B = "
* I_VGBEL = "

EXCEPTIONS
SYSTEM_FAILURE = 1 ACTION_MISSING = 2 WRONG_ACTION = 3 WERKS_MISSING = 4 EXGRP_MISSING = 5 FOREIGN_LOCK = 6
.



IMPORTING Parameters details for J_1I6_ENQUEUE_DEQUEUE

I_ACTION - 1 = Enqueue / 2 = Dequeue

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

I_WERKS - Plant

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

I_EXGRP - Excise group

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

I_VBELN_B -

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

I_VGBEL -

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

EXCEPTIONS details

SYSTEM_FAILURE -

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

ACTION_MISSING -

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

WRONG_ACTION -

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

WERKS_MISSING -

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

EXGRP_MISSING -

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

FOREIGN_LOCK -

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

Copy and paste ABAP code example for J_1I6_ENQUEUE_DEQUEUE 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_i_action  TYPE STRING, "   
lv_system_failure  TYPE STRING, "   
lv_i_werks  TYPE J_1IEXCHDR-WERKS, "   
lv_action_missing  TYPE J_1IEXCHDR, "   
lv_i_exgrp  TYPE J_1IEXCHDR-EXGRP, "   
lv_wrong_action  TYPE J_1IEXCHDR, "   
lv_i_vbeln_b  TYPE J_1IEXCDTL-RDOC2, "   
lv_werks_missing  TYPE J_1IEXCDTL, "   
lv_i_vgbel  TYPE J_1IEXCDTL-RDOC1, "   
lv_exgrp_missing  TYPE J_1IEXCDTL, "   
lv_foreign_lock  TYPE J_1IEXCDTL. "   

  CALL FUNCTION 'J_1I6_ENQUEUE_DEQUEUE'  "Enqueue / Dequeue
    EXPORTING
         I_ACTION = lv_i_action
         I_WERKS = lv_i_werks
         I_EXGRP = lv_i_exgrp
         I_VBELN_B = lv_i_vbeln_b
         I_VGBEL = lv_i_vgbel
    EXCEPTIONS
        SYSTEM_FAILURE = 1
        ACTION_MISSING = 2
        WRONG_ACTION = 3
        WERKS_MISSING = 4
        EXGRP_MISSING = 5
        FOREIGN_LOCK = 6
. " J_1I6_ENQUEUE_DEQUEUE




ABAP code using 7.40 inline data declarations to call FM J_1I6_ENQUEUE_DEQUEUE

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.

 
 
"SELECT single WERKS FROM J_1IEXCHDR INTO @DATA(ld_i_werks).
 
 
"SELECT single EXGRP FROM J_1IEXCHDR INTO @DATA(ld_i_exgrp).
 
 
"SELECT single RDOC2 FROM J_1IEXCDTL INTO @DATA(ld_i_vbeln_b).
 
 
"SELECT single RDOC1 FROM J_1IEXCDTL INTO @DATA(ld_i_vgbel).
 
 
 


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!