SAP LXDCK_DECISION_LOCK Function Module for Locks a cross-docking decision









LXDCK_DECISION_LOCK is a standard lxdck decision lock SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Locks a cross-docking decision 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 lxdck decision lock FM, simply by entering the name LXDCK_DECISION_LOCK into the relevant SAP transaction such as SE37 or SE38.

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



Function LXDCK_DECISION_LOCK 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 'LXDCK_DECISION_LOCK'"Locks a cross-docking decision
EXPORTING
IV_WAREHOUSE = "Warehouse Number
IV_DECISION = "Decision number
* IV_TIMES = 3 "Locking attempts

IMPORTING
ES_DECISION = "Run time decision structure

EXCEPTIONS
DECISION_LOCK_FAIL = 1 DECISION_NOT_FOUND = 2
.



IMPORTING Parameters details for LXDCK_DECISION_LOCK

IV_WAREHOUSE - Warehouse Number

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

IV_DECISION - Decision number

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

IV_TIMES - Locking attempts

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

EXPORTING Parameters details for LXDCK_DECISION_LOCK

ES_DECISION - Run time decision structure

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

EXCEPTIONS details

DECISION_LOCK_FAIL -

Data type:
Optional: No
Call by Reference: Yes

DECISION_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for LXDCK_DECISION_LOCK 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_es_decision  TYPE LXDCK_DECRN, "   
lv_iv_warehouse  TYPE LEINT_LGNUM, "   
lv_decision_lock_fail  TYPE LEINT_LGNUM, "   
lv_iv_decision  TYPE LXDCK_DCNUM, "   
lv_decision_not_found  TYPE LXDCK_DCNUM, "   
lv_iv_times  TYPE NUM1. "   3

  CALL FUNCTION 'LXDCK_DECISION_LOCK'  "Locks a cross-docking decision
    EXPORTING
         IV_WAREHOUSE = lv_iv_warehouse
         IV_DECISION = lv_iv_decision
         IV_TIMES = lv_iv_times
    IMPORTING
         ES_DECISION = lv_es_decision
    EXCEPTIONS
        DECISION_LOCK_FAIL = 1
        DECISION_NOT_FOUND = 2
. " LXDCK_DECISION_LOCK




ABAP code using 7.40 inline data declarations to call FM LXDCK_DECISION_LOCK

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_iv_times) = 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!