SAP EXIT_SAPLV56F_010 Function Module for Shipment Processing: Copying Delivery Data to Shipment Document
EXIT_SAPLV56F_010 is a standard exit saplv56f 010 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Shipment Processing: Copying Delivery Data to Shipment Document 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 exit saplv56f 010 FM, simply by entering the name EXIT_SAPLV56F_010 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XV56
Program Name: SAPLXV56
Main Program:
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLV56F_010 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 'EXIT_SAPLV56F_010'"Shipment Processing: Copying Delivery Data to Shipment Document.
EXPORTING
I_TVTK = "Shipment Type
CHANGING
C_XVTTK = "Shipment Header
TABLES
I_XVTTP = "Shipment Items
I_XTRLP = "Delivery Item
C_XVTTS = "Stages
C_YVTTS = "Stages
C_XVTSP = "Assign Stage/Item
C_YVTSP = "Assign Stage/Item
C_XVBPA = "Partners
C_YVBPA = "Partners
C_XVBADR = "Addresses
I_XTRLK = "Delivery Header
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.LE_SHIPMENT_COPYDATE_CONFIRM NOTRANSL: Bestätigung der zu kopierenden Data aus Lieferungen
SD_SHIPMENT_COPY_DELIVERY_DATA NOTRANSL: Kopieren von Daten der Lieferung in den Transport
SD_SHIPMENT_CREATE_INVOICE NOTRANSL: Fakturieren für einen Transport
SD_SHIPMENT_EXECUTE_FUNCTIONS1 NOTRANSL: Ausführen von in einem Profil hinterlegten Funktionen vor dem Si
SD_SHIPMENT_EXECUTE_FUNCTIONS2 NOTRANSL: Ausführen von in einem Profil hinterlegten Funktionen nach dem S
SD_SHIPMENT_EXECUTE_FUNCTIONS3 NOTRANSL: Activites after saving, but not in update task
SD_SHIPMENT_GET_KNREF NOTRANSL: Ergänzen VTPA mit KNREF aus Vtrlk
SD_SHIPMENT_MAINTAIN_POPUP Field Selection for Quick Entry Dialog Box
SD_SHIPMENT_MEASUREMENT_DETERM NOTRANSL: Sum up measurements in stages for shipment header
SD_SHIPMENT_POST_GOODS_ISSUE NOTRANSL: Warenausgang für einen Transport buchen
SD_SHIPMENT_PRF_ACTIVITY_READ NOTRANSL: Aktivitätenprofil für Transport lesen (gepuffert)
SD_SHIPMENT_STATUS_COMPLETION NOTRANSL: Funktionen bei Setzen des Status 'Abfertigen' im Transportkopf
SD_SHIPMENT_STATUS_LOAD_END NOTRANSL: Funktionen bei Setzen des Status 'Laden Ende' im Transportkopf
SD_SHIPMENT_STATUS_LOAD_START NOTRANSL: Funktionen bei Setzen des Status 'Laden Beginn' im Transportkopf
SD_SHIPMENT_STATUS_PLANNED NOTRANSL: Funktionen bei Setzen des Status 'Disponiert' im Transportkopf
SD_SHIPMENT_STATUS_REGISTRATED NOTRANSL: Funktionen bei Setzen des Status 'Registriert' im Transportkopf
SD_SHIPMENT_STATUS_SHIPM_END NOTRANSL: Funktionen bei Setzen des Status 'Transport Ende' im Transportko
SD_SHIPMENT_STATUS_SHIPM_START NOTRANSL: Funktionen bei Setzen des Status 'Transport Beginn' im Transport
IMPORTING Parameters details for EXIT_SAPLV56F_010
I_TVTK - Shipment Type
Data type: TVTKOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for EXIT_SAPLV56F_010
C_XVTTK - Shipment Header
Data type: VTTKVBOptional: No
Call by Reference: Yes
TABLES Parameters details for EXIT_SAPLV56F_010
I_XVTTP - Shipment Items
Data type: VTTPVBOptional: No
Call by Reference: No ( called with pass by value option)
I_XTRLP - Delivery Item
Data type: VTRLPOptional: No
Call by Reference: No ( called with pass by value option)
C_XVTTS - Stages
Data type: VTTSVBOptional: No
Call by Reference: No ( called with pass by value option)
C_YVTTS - Stages
Data type: VTTSVBOptional: No
Call by Reference: No ( called with pass by value option)
C_XVTSP - Assign Stage/Item
Data type: VTSPVBOptional: No
Call by Reference: No ( called with pass by value option)
C_YVTSP - Assign Stage/Item
Data type: VTSPVBOptional: No
Call by Reference: No ( called with pass by value option)
C_XVBPA - Partners
Data type: VBPAVBOptional: No
Call by Reference: No ( called with pass by value option)
C_YVBPA - Partners
Data type: VBPAVBOptional: No
Call by Reference: No ( called with pass by value option)
C_XVBADR - Addresses
Data type: SADRVBOptional: No
Call by Reference: No ( called with pass by value option)
I_XTRLK - Delivery Header
Data type: VTRLKOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLV56F_010 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_tvtk | TYPE TVTK, " | |||
| lv_c_xvttk | TYPE VTTKVB, " | |||
| lt_i_xvttp | TYPE STANDARD TABLE OF VTTPVB, " | |||
| lt_i_xtrlp | TYPE STANDARD TABLE OF VTRLP, " | |||
| lt_c_xvtts | TYPE STANDARD TABLE OF VTTSVB, " | |||
| lt_c_yvtts | TYPE STANDARD TABLE OF VTTSVB, " | |||
| lt_c_xvtsp | TYPE STANDARD TABLE OF VTSPVB, " | |||
| lt_c_yvtsp | TYPE STANDARD TABLE OF VTSPVB, " | |||
| lt_c_xvbpa | TYPE STANDARD TABLE OF VBPAVB, " | |||
| lt_c_yvbpa | TYPE STANDARD TABLE OF VBPAVB, " | |||
| lt_c_xvbadr | TYPE STANDARD TABLE OF SADRVB, " | |||
| lt_i_xtrlk | TYPE STANDARD TABLE OF VTRLK. " |
|   CALL FUNCTION 'EXIT_SAPLV56F_010' "Shipment Processing: Copying Delivery Data to Shipment Document |
| EXPORTING | ||
| I_TVTK | = lv_i_tvtk | |
| CHANGING | ||
| C_XVTTK | = lv_c_xvttk | |
| TABLES | ||
| I_XVTTP | = lt_i_xvttp | |
| I_XTRLP | = lt_i_xtrlp | |
| C_XVTTS | = lt_c_xvtts | |
| C_YVTTS | = lt_c_yvtts | |
| C_XVTSP | = lt_c_xvtsp | |
| C_YVTSP | = lt_c_yvtsp | |
| C_XVBPA | = lt_c_xvbpa | |
| C_YVBPA | = lt_c_yvbpa | |
| C_XVBADR | = lt_c_xvbadr | |
| I_XTRLK | = lt_i_xtrlk | |
| . " EXIT_SAPLV56F_010 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLV56F_010
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