SAP LE_SHIPMENT_BADI_DATA_XFER Function Module for NOTRANSL: Copy shipment tables to BadI complex data type









LE_SHIPMENT_BADI_DATA_XFER is a standard le shipment badi data xfer 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: Copy shipment tables to BadI complex data type 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 le shipment badi data xfer FM, simply by entering the name LE_SHIPMENT_BADI_DATA_XFER into the relevant SAP transaction such as SE37 or SE38.

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



Function LE_SHIPMENT_BADI_DATA_XFER 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 'LE_SHIPMENT_BADI_DATA_XFER'"NOTRANSL: Copy shipment tables to BadI complex data type
  EXPORTING
*  I_FLAG_TRA_COMPLETE = 'X' "Indicator: Shipment Data are Complete
*  I_TRA_SAVE_CALLER =  "Initiator Indicator on Saving Shipments

CHANGING
*  C_CXSHIPMENTS =  "Aggregate type: Shipments 'pre' DB update context
*  C_CXSHIPMENTS_DBUC =  "

TABLES
*  I_XVTTK =  "
*  I_XVTRLP =  "
*  I_XVEKP =  "
*  I_YVEKP =  "
*  I_XVEPO =  "
*  I_YVEPO =  "
*  I_XVBPA =  "
*  I_YVBPA =  "
*  I_XSADR =  "
*  I_YSADR =  "
*  I_DB_VTTK_DEL =  "
*  I_YVTTK =  "
*  I_DB_VTTK_INS =  "
*  I_DB_VTTK_UPD =  "
*  I_DB_VTTP_DEL =  "
*  I_DB_VTTP_INS =  "
*  I_DB_VTTP_UPD =  "
*  I_DB_VTTS_DEL =  "
*  I_DB_VTTS_INS =  "
*  I_DB_VTTS_UPD =  "
*  I_DB_VTSP_DEL =  "
*  I_DB_VTSP_INS =  "
*  I_XVTTS =  "
*  I_DB_VTSP_UPD =  "
*  I_DB_VTFA_DEL =  "
*  I_DB_VTFA_INS =  "
*  I_DB_VTFA_UPD =  "
*  I_U_XVBPA =  "
*  I_U_YVBPA =  "
*  I_U_XVBADR =  "
*  I_U_YVBADR =  "
*  I_YVTTS =  "
*  I_XVTSP =  "
*  I_YVTSP =  "
*  I_XVTTP =  "
*  I_YVTTP =  "
*  I_XVTRLK =  "
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLV56U_001 Checking of Shipments for Changes
EXIT_SAPLV56U_002 Checking of Shipments for Completeness
EXIT_SAPLV56U_003 Shipment Number Allocation
EXIT_SAPLV56U_004 Shipment Processing: Prepare New Objects for Saving
EXIT_SAPLV56U_005 Updating of Additional Objects Within Shipment Processing
EXIT_SAPLV56U_006 Obsolete as of $.6C: Update Delivery by Delivery Routines
EXIT_SAPLV56U_007 Additional Rules for Determining Transportation Planning Status

IMPORTING Parameters details for LE_SHIPMENT_BADI_DATA_XFER

I_FLAG_TRA_COMPLETE - Indicator: Shipment Data are Complete

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

I_TRA_SAVE_CALLER - Initiator Indicator on Saving Shipments

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

CHANGING Parameters details for LE_SHIPMENT_BADI_DATA_XFER

C_CXSHIPMENTS - Aggregate type: Shipments 'pre' DB update context

Data type: CXSHIPMENT
Optional: Yes
Call by Reference: Yes

C_CXSHIPMENTS_DBUC -

Data type: CXSHIPMENT_DBUC
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for LE_SHIPMENT_BADI_DATA_XFER

I_XVTTK -

Data type: VTTKVB
Optional: Yes
Call by Reference: Yes

I_XVTRLP -

Data type: VTRLP
Optional: Yes
Call by Reference: Yes

I_XVEKP -

Data type: VEKPVB
Optional: Yes
Call by Reference: Yes

I_YVEKP -

Data type: VEKPVB
Optional: Yes
Call by Reference: Yes

I_XVEPO -

Data type: VEPOVB
Optional: Yes
Call by Reference: Yes

I_YVEPO -

Data type: VEPOVB
Optional: Yes
Call by Reference: Yes

I_XVBPA -

Data type: VBPAVB
Optional: Yes
Call by Reference: Yes

I_YVBPA -

Data type: VBPAVB
Optional: Yes
Call by Reference: Yes

I_XSADR -

Data type: SADRVB
Optional: Yes
Call by Reference: Yes

I_YSADR -

Data type: SADRVB
Optional: Yes
Call by Reference: Yes

I_DB_VTTK_DEL -

Data type: VTTK
Optional: Yes
Call by Reference: Yes

I_YVTTK -

Data type: VTTKVB
Optional: Yes
Call by Reference: Yes

I_DB_VTTK_INS -

Data type: VTTK
Optional: Yes
Call by Reference: Yes

I_DB_VTTK_UPD -

Data type: VTTK
Optional: Yes
Call by Reference: Yes

I_DB_VTTP_DEL -

Data type: VTTP
Optional: Yes
Call by Reference: Yes

I_DB_VTTP_INS -

Data type: VTTP
Optional: Yes
Call by Reference: Yes

I_DB_VTTP_UPD -

Data type: VTTP
Optional: Yes
Call by Reference: Yes

I_DB_VTTS_DEL -

Data type: VTTS
Optional: Yes
Call by Reference: Yes

I_DB_VTTS_INS -

Data type: VTTS
Optional: Yes
Call by Reference: Yes

I_DB_VTTS_UPD -

Data type: VTTS
Optional: Yes
Call by Reference: Yes

I_DB_VTSP_DEL -

Data type: VTSP
Optional: Yes
Call by Reference: Yes

I_DB_VTSP_INS -

Data type: VTSP
Optional: Yes
Call by Reference: Yes

I_XVTTS -

Data type: VTTSVB
Optional: Yes
Call by Reference: Yes

I_DB_VTSP_UPD -

Data type: VTSP
Optional: Yes
Call by Reference: Yes

I_DB_VTFA_DEL -

Data type: VTFA
Optional: Yes
Call by Reference: Yes

I_DB_VTFA_INS -

Data type: VTFA
Optional: Yes
Call by Reference: Yes

I_DB_VTFA_UPD -

Data type: VTFA
Optional: Yes
Call by Reference: Yes

I_U_XVBPA -

Data type: VBPAVB
Optional: Yes
Call by Reference: Yes

I_U_YVBPA -

Data type: VBPAVB
Optional: Yes
Call by Reference: Yes

I_U_XVBADR -

Data type: SADRVB
Optional: Yes
Call by Reference: Yes

I_U_YVBADR -

Data type: SADRVB
Optional: Yes
Call by Reference: Yes

I_YVTTS -

Data type: VTTSVB
Optional: Yes
Call by Reference: Yes

I_XVTSP -

Data type: VTSPVB
Optional: Yes
Call by Reference: Yes

I_YVTSP -

Data type: VTSPVB
Optional: Yes
Call by Reference: Yes

I_XVTTP -

Data type: VTTPVB
Optional: Yes
Call by Reference: Yes

I_YVTTP -

Data type: VTTPVB
Optional: Yes
Call by Reference: Yes

I_XVTRLK -

Data type: VTRLK
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for LE_SHIPMENT_BADI_DATA_XFER 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_i_xvttk  TYPE STANDARD TABLE OF VTTKVB, "   
lv_c_cxshipments  TYPE CXSHIPMENT, "   
lv_i_flag_tra_complete  TYPE TRA_SAVE_COMPLETE, "   'X'
lt_i_xvtrlp  TYPE STANDARD TABLE OF VTRLP, "   
lt_i_xvekp  TYPE STANDARD TABLE OF VEKPVB, "   
lt_i_yvekp  TYPE STANDARD TABLE OF VEKPVB, "   
lt_i_xvepo  TYPE STANDARD TABLE OF VEPOVB, "   
lt_i_yvepo  TYPE STANDARD TABLE OF VEPOVB, "   
lt_i_xvbpa  TYPE STANDARD TABLE OF VBPAVB, "   
lt_i_yvbpa  TYPE STANDARD TABLE OF VBPAVB, "   
lt_i_xsadr  TYPE STANDARD TABLE OF SADRVB, "   
lt_i_ysadr  TYPE STANDARD TABLE OF SADRVB, "   
lt_i_db_vttk_del  TYPE STANDARD TABLE OF VTTK, "   
lt_i_yvttk  TYPE STANDARD TABLE OF VTTKVB, "   
lv_i_tra_save_caller  TYPE TRA_SAVE_CALLER, "   
lv_c_cxshipments_dbuc  TYPE CXSHIPMENT_DBUC, "   
lt_i_db_vttk_ins  TYPE STANDARD TABLE OF VTTK, "   
lt_i_db_vttk_upd  TYPE STANDARD TABLE OF VTTK, "   
lt_i_db_vttp_del  TYPE STANDARD TABLE OF VTTP, "   
lt_i_db_vttp_ins  TYPE STANDARD TABLE OF VTTP, "   
lt_i_db_vttp_upd  TYPE STANDARD TABLE OF VTTP, "   
lt_i_db_vtts_del  TYPE STANDARD TABLE OF VTTS, "   
lt_i_db_vtts_ins  TYPE STANDARD TABLE OF VTTS, "   
lt_i_db_vtts_upd  TYPE STANDARD TABLE OF VTTS, "   
lt_i_db_vtsp_del  TYPE STANDARD TABLE OF VTSP, "   
lt_i_db_vtsp_ins  TYPE STANDARD TABLE OF VTSP, "   
lt_i_xvtts  TYPE STANDARD TABLE OF VTTSVB, "   
lt_i_db_vtsp_upd  TYPE STANDARD TABLE OF VTSP, "   
lt_i_db_vtfa_del  TYPE STANDARD TABLE OF VTFA, "   
lt_i_db_vtfa_ins  TYPE STANDARD TABLE OF VTFA, "   
lt_i_db_vtfa_upd  TYPE STANDARD TABLE OF VTFA, "   
lt_i_u_xvbpa  TYPE STANDARD TABLE OF VBPAVB, "   
lt_i_u_yvbpa  TYPE STANDARD TABLE OF VBPAVB, "   
lt_i_u_xvbadr  TYPE STANDARD TABLE OF SADRVB, "   
lt_i_u_yvbadr  TYPE STANDARD TABLE OF SADRVB, "   
lt_i_yvtts  TYPE STANDARD TABLE OF VTTSVB, "   
lt_i_xvtsp  TYPE STANDARD TABLE OF VTSPVB, "   
lt_i_yvtsp  TYPE STANDARD TABLE OF VTSPVB, "   
lt_i_xvttp  TYPE STANDARD TABLE OF VTTPVB, "   
lt_i_yvttp  TYPE STANDARD TABLE OF VTTPVB, "   
lt_i_xvtrlk  TYPE STANDARD TABLE OF VTRLK. "   

  CALL FUNCTION 'LE_SHIPMENT_BADI_DATA_XFER'  "NOTRANSL: Copy shipment tables to BadI complex data type
    EXPORTING
         I_FLAG_TRA_COMPLETE = lv_i_flag_tra_complete
         I_TRA_SAVE_CALLER = lv_i_tra_save_caller
    CHANGING
         C_CXSHIPMENTS = lv_c_cxshipments
         C_CXSHIPMENTS_DBUC = lv_c_cxshipments_dbuc
    TABLES
         I_XVTTK = lt_i_xvttk
         I_XVTRLP = lt_i_xvtrlp
         I_XVEKP = lt_i_xvekp
         I_YVEKP = lt_i_yvekp
         I_XVEPO = lt_i_xvepo
         I_YVEPO = lt_i_yvepo
         I_XVBPA = lt_i_xvbpa
         I_YVBPA = lt_i_yvbpa
         I_XSADR = lt_i_xsadr
         I_YSADR = lt_i_ysadr
         I_DB_VTTK_DEL = lt_i_db_vttk_del
         I_YVTTK = lt_i_yvttk
         I_DB_VTTK_INS = lt_i_db_vttk_ins
         I_DB_VTTK_UPD = lt_i_db_vttk_upd
         I_DB_VTTP_DEL = lt_i_db_vttp_del
         I_DB_VTTP_INS = lt_i_db_vttp_ins
         I_DB_VTTP_UPD = lt_i_db_vttp_upd
         I_DB_VTTS_DEL = lt_i_db_vtts_del
         I_DB_VTTS_INS = lt_i_db_vtts_ins
         I_DB_VTTS_UPD = lt_i_db_vtts_upd
         I_DB_VTSP_DEL = lt_i_db_vtsp_del
         I_DB_VTSP_INS = lt_i_db_vtsp_ins
         I_XVTTS = lt_i_xvtts
         I_DB_VTSP_UPD = lt_i_db_vtsp_upd
         I_DB_VTFA_DEL = lt_i_db_vtfa_del
         I_DB_VTFA_INS = lt_i_db_vtfa_ins
         I_DB_VTFA_UPD = lt_i_db_vtfa_upd
         I_U_XVBPA = lt_i_u_xvbpa
         I_U_YVBPA = lt_i_u_yvbpa
         I_U_XVBADR = lt_i_u_xvbadr
         I_U_YVBADR = lt_i_u_yvbadr
         I_YVTTS = lt_i_yvtts
         I_XVTSP = lt_i_xvtsp
         I_YVTSP = lt_i_yvtsp
         I_XVTTP = lt_i_xvttp
         I_YVTTP = lt_i_yvttp
         I_XVTRLK = lt_i_xvtrlk
. " LE_SHIPMENT_BADI_DATA_XFER




ABAP code using 7.40 inline data declarations to call FM LE_SHIPMENT_BADI_DATA_XFER

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_flag_tra_complete) = 'X'.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!