SAP SD_SHIPMENTS_CHECK_COMPLETE Function Module for NOTRANSL: Überprüfung von Transporten auf Vollständigkeit
SD_SHIPMENTS_CHECK_COMPLETE is a standard sd shipments check complete 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: Überprüfung von Transporten auf Vollständigkeit 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 shipments check complete FM, simply by entering the name SD_SHIPMENTS_CHECK_COMPLETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: V56U
Program Name: SAPLV56U
Main Program: SAPLV56U
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_SHIPMENTS_CHECK_COMPLETE 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_SHIPMENTS_CHECK_COMPLETE'"NOTRANSL: Überprüfung von Transporten auf Vollständigkeit.
EXPORTING
* I_OPT_DIALOG = ' ' "
IMPORTING
E_ERRORS_OCCURRED = "
E_WARNINGS_OCCURRED = "There are warnings
TABLES
I_XVTTK = "
I_YVTTK = "
I_XVTTP = "
I_YVTTP = "
I_XVTTS = "
I_YVTTS = "
I_XVTSP = "
I_YVTSP = "
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 SD_SHIPMENTS_CHECK_COMPLETE
I_OPT_DIALOG -
Data type: RV56A-SELKZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SD_SHIPMENTS_CHECK_COMPLETE
E_ERRORS_OCCURRED -
Data type: RV56A-SELKZOptional: No
Call by Reference: No ( called with pass by value option)
E_WARNINGS_OCCURRED - There are warnings
Data type: RV56A-SELKZOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SD_SHIPMENTS_CHECK_COMPLETE
I_XVTTK -
Data type: VTTKVBOptional: No
Call by Reference: No ( called with pass by value option)
I_YVTTK -
Data type: VTTKVBOptional: No
Call by Reference: No ( called with pass by value option)
I_XVTTP -
Data type: VTTPVBOptional: No
Call by Reference: No ( called with pass by value option)
I_YVTTP -
Data type: VTTPVBOptional: No
Call by Reference: No ( called with pass by value option)
I_XVTTS -
Data type: VTTSVBOptional: No
Call by Reference: No ( called with pass by value option)
I_YVTTS -
Data type: VTTSVBOptional: No
Call by Reference: No ( called with pass by value option)
I_XVTSP -
Data type: VTSPVBOptional: No
Call by Reference: No ( called with pass by value option)
I_YVTSP -
Data type: VTSPVBOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_SHIPMENTS_CHECK_COMPLETE 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_i_opt_dialog | TYPE RV56A-SELKZ, " SPACE | |||
| lv_e_errors_occurred | TYPE RV56A-SELKZ, " | |||
| lt_i_yvttk | TYPE STANDARD TABLE OF VTTKVB, " | |||
| lv_e_warnings_occurred | TYPE RV56A-SELKZ, " | |||
| lt_i_xvttp | TYPE STANDARD TABLE OF VTTPVB, " | |||
| lt_i_yvttp | TYPE STANDARD TABLE OF VTTPVB, " | |||
| lt_i_xvtts | TYPE STANDARD TABLE OF VTTSVB, " | |||
| lt_i_yvtts | TYPE STANDARD TABLE OF VTTSVB, " | |||
| lt_i_xvtsp | TYPE STANDARD TABLE OF VTSPVB, " | |||
| lt_i_yvtsp | TYPE STANDARD TABLE OF VTSPVB. " |
|   CALL FUNCTION 'SD_SHIPMENTS_CHECK_COMPLETE' "NOTRANSL: Überprüfung von Transporten auf Vollständigkeit |
| EXPORTING | ||
| I_OPT_DIALOG | = lv_i_opt_dialog | |
| IMPORTING | ||
| E_ERRORS_OCCURRED | = lv_e_errors_occurred | |
| E_WARNINGS_OCCURRED | = lv_e_warnings_occurred | |
| TABLES | ||
| I_XVTTK | = lt_i_xvttk | |
| I_YVTTK | = lt_i_yvttk | |
| I_XVTTP | = lt_i_xvttp | |
| I_YVTTP | = lt_i_yvttp | |
| I_XVTTS | = lt_i_xvtts | |
| I_YVTTS | = lt_i_yvtts | |
| I_XVTSP | = lt_i_xvtsp | |
| I_YVTSP | = lt_i_yvtsp | |
| . " SD_SHIPMENTS_CHECK_COMPLETE | ||
ABAP code using 7.40 inline data declarations to call FM SD_SHIPMENTS_CHECK_COMPLETE
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 SELKZ FROM RV56A INTO @DATA(ld_i_opt_dialog). | ||||
| DATA(ld_i_opt_dialog) | = ' '. | |||
| "SELECT single SELKZ FROM RV56A INTO @DATA(ld_e_errors_occurred). | ||||
| "SELECT single SELKZ FROM RV56A INTO @DATA(ld_e_warnings_occurred). | ||||
Search for further information about these or an SAP related objects