SAP SD_SALES_DOCUMENT_ENQUEUE Function Module for NOTRANSL: Enqueue-Sperre für Objekt EVVBAKE anfordern









SD_SALES_DOCUMENT_ENQUEUE is a standard sd sales document enqueue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Enqueue-Sperre für Objekt EVVBAKE anfordern 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 sd sales document enqueue FM, simply by entering the name SD_SALES_DOCUMENT_ENQUEUE into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_SALES_DOCUMENT_ENQUEUE 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 'SD_SALES_DOCUMENT_ENQUEUE'"NOTRANSL: Enqueue-Sperre für Objekt EVVBAKE anfordern
  EXPORTING
*  MODE_VBAK = 'E' "Lock Mode
*  I_CRM_LOCK_MODE = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  I_CHECK_SCENARIO_A = ' ' "Character Field of Length 1
*  I_VBAK =  "Sales Document: Header Data
*  I_XVBAK_UPDKZ = 'U' "Update Indicator
*  MANDT = SY-MANDT "Client
*  VBELN =  "Sales Document
*  X_VBELN = ' ' "
*  _SCOPE = '2' "
*  _WAIT = ' ' "
*  _COLLECT = ' ' "Indicator Whether Locks Should Only Be Collected First
*  LOGSYS =  "Logical System
*  CSL_LOGSYS =  "Logical System

EXCEPTIONS
   FOREIGN_LOCK = 1    SYSTEM_FAILURE = 2    NO_CHANGE = 3
.



IMPORTING Parameters details for SD_SALES_DOCUMENT_ENQUEUE

MODE_VBAK - Lock Mode

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

I_CRM_LOCK_MODE - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

I_CHECK_SCENARIO_A - Character Field of Length 1

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

I_VBAK - Sales Document: Header Data

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

I_XVBAK_UPDKZ - Update Indicator

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

MANDT - Client

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

VBELN - Sales Document

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

X_VBELN -

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)

_WAIT -

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

_COLLECT - Indicator Whether Locks Should Only Be Collected First

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

LOGSYS - Logical System

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

CSL_LOGSYS - Logical System

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

EXCEPTIONS details

FOREIGN_LOCK -

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

NO_CHANGE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SD_SALES_DOCUMENT_ENQUEUE 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_vbak  TYPE DD26E-ENQMODE, "   'E'
lv_foreign_lock  TYPE DD26E, "   
lv_i_crm_lock_mode  TYPE BAPIFLAG-BAPIFLAG, "   SPACE
lv_i_check_scenario_a  TYPE CHAR01, "   SPACE
lv_i_vbak  TYPE VBAK, "   
lv_i_xvbak_updkz  TYPE UPDKZ_D, "   'U'
lv_mandt  TYPE VBAK-MANDT, "   SY-MANDT
lv_system_failure  TYPE VBAK, "   
lv_vbeln  TYPE VBAK-VBELN, "   
lv_no_change  TYPE VBAK, "   
lv_x_vbeln  TYPE VBAK, "   SPACE
lv__scope  TYPE VBAK, "   '2'
lv__wait  TYPE VBAK, "   SPACE
lv__collect  TYPE DDENQ_LIKE-COLLECT, "   ' '
lv_logsys  TYPE T000-LOGSYS, "   
lv_csl_logsys  TYPE LOGSYS. "   

  CALL FUNCTION 'SD_SALES_DOCUMENT_ENQUEUE'  "NOTRANSL: Enqueue-Sperre für Objekt EVVBAKE anfordern
    EXPORTING
         MODE_VBAK = lv_mode_vbak
         I_CRM_LOCK_MODE = lv_i_crm_lock_mode
         I_CHECK_SCENARIO_A = lv_i_check_scenario_a
         I_VBAK = lv_i_vbak
         I_XVBAK_UPDKZ = lv_i_xvbak_updkz
         MANDT = lv_mandt
         VBELN = lv_vbeln
         X_VBELN = lv_x_vbeln
         _SCOPE = lv__scope
         _WAIT = lv__wait
         _COLLECT = lv__collect
         LOGSYS = lv_logsys
         CSL_LOGSYS = lv_csl_logsys
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
        NO_CHANGE = 3
. " SD_SALES_DOCUMENT_ENQUEUE




ABAP code using 7.40 inline data declarations to call FM SD_SALES_DOCUMENT_ENQUEUE

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 ENQMODE FROM DD26E INTO @DATA(ld_mode_vbak).
DATA(ld_mode_vbak) = 'E'.
 
 
"SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_i_crm_lock_mode).
DATA(ld_i_crm_lock_mode) = ' '.
 
DATA(ld_i_check_scenario_a) = ' '.
 
 
DATA(ld_i_xvbak_updkz) = 'U'.
 
"SELECT single MANDT FROM VBAK INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
 
"SELECT single VBELN FROM VBAK INTO @DATA(ld_vbeln).
 
 
DATA(ld_x_vbeln) = ' '.
 
DATA(ld__scope) = '2'.
 
DATA(ld__wait) = ' '.
 
"SELECT single COLLECT FROM DDENQ_LIKE INTO @DATA(ld__collect).
DATA(ld__collect) = ' '.
 
"SELECT single LOGSYS FROM T000 INTO @DATA(ld_logsys).
 
 


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!