SAP LXDCK_DECISION_CONSTRUCT Function Module for Creates a planned cross-docking decision









LXDCK_DECISION_CONSTRUCT is a standard lxdck decision construct SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Creates a planned 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 construct FM, simply by entering the name LXDCK_DECISION_CONSTRUCT 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_CONSTRUCT 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_CONSTRUCT'"Creates a planned cross-docking decision
  EXPORTING
   IV_WAREHOUSE =  "Warehouse Number
*  IV_COMMIT =  "Single-character flag
   IV_DECISION_TYPE =  "Decision type
   IS_INBOUND_KEY =  "Inbound key
   IS_OUTBOUND_KEY =  "Outbound key
   IS_MATERIAL_DATA =  "Material data
   IV_QUANTITY =  "Decision Quantity
   IV_UNIT_MEASURE =  "Decision Unit of Measure
   IV_ORIGIN =  "Decision origin
*  IV_OUT_MOVEMENT =  "Outbound movement type

 IMPORTING
   ES_DECISION =  "Run time decision structure
.



IMPORTING Parameters details for LXDCK_DECISION_CONSTRUCT

IV_WAREHOUSE - Warehouse Number

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

IV_COMMIT - Single-character flag

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

IV_DECISION_TYPE - Decision type

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

IS_INBOUND_KEY - Inbound key

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

IS_OUTBOUND_KEY - Outbound key

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

IS_MATERIAL_DATA - Material data

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

IV_QUANTITY - Decision Quantity

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

IV_UNIT_MEASURE - Decision Unit of Measure

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

IV_ORIGIN - Decision origin

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

IV_OUT_MOVEMENT - Outbound movement type

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

EXPORTING Parameters details for LXDCK_DECISION_CONSTRUCT

ES_DECISION - Run time decision structure

Data type: LXDCK_DECRN
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for LXDCK_DECISION_CONSTRUCT 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_iv_commit  TYPE CHAR1, "   
lv_iv_decision_type  TYPE LXDCK_DCTYP, "   
lv_is_inbound_key  TYPE LXDCK_OBKEY, "   
lv_is_outbound_key  TYPE LXDCK_OBKEY, "   
lv_is_material_data  TYPE LXDCK_MATNR_DATA, "   
lv_iv_quantity  TYPE LXDCK_DCQTY, "   
lv_iv_unit_measure  TYPE LXDCK_DCUOM, "   
lv_iv_origin  TYPE LXDCK_DCORG, "   
lv_iv_out_movement  TYPE LEINT_BWLVS. "   

  CALL FUNCTION 'LXDCK_DECISION_CONSTRUCT'  "Creates a planned cross-docking decision
    EXPORTING
         IV_WAREHOUSE = lv_iv_warehouse
         IV_COMMIT = lv_iv_commit
         IV_DECISION_TYPE = lv_iv_decision_type
         IS_INBOUND_KEY = lv_is_inbound_key
         IS_OUTBOUND_KEY = lv_is_outbound_key
         IS_MATERIAL_DATA = lv_is_material_data
         IV_QUANTITY = lv_iv_quantity
         IV_UNIT_MEASURE = lv_iv_unit_measure
         IV_ORIGIN = lv_iv_origin
         IV_OUT_MOVEMENT = lv_iv_out_movement
    IMPORTING
         ES_DECISION = lv_es_decision
. " LXDCK_DECISION_CONSTRUCT




ABAP code using 7.40 inline data declarations to call FM LXDCK_DECISION_CONSTRUCT

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.

 
 
 
 
 
 
 
 
 
 
 


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!