SAP SD_SHIPMENT_HAZMAT_CHECK Function Module for NOTRANSL: Gefahrgutprüfung Transport
SD_SHIPMENT_HAZMAT_CHECK is a standard sd shipment hazmat check 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: Gefahrgutprüfung Transport 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 shipment hazmat check FM, simply by entering the name SD_SHIPMENT_HAZMAT_CHECK 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_SHIPMENT_HAZMAT_CHECK 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_SHIPMENT_HAZMAT_CHECK'"NOTRANSL: Gefahrgutprüfung Transport.
EXPORTING
I_DG_CHK_START = "
* I_TVTK = "Transport Type
* I_DISPLAY_MODE = ' ' "
* I_TRA_SAVE_CALLER = "
IMPORTING
E_HAZMAT_CHECKS_FAILED = "
TABLES
* I_TKNUM_RANGE = "
I_XVTSP = "
I_YVTSP = "
* I_XVBPA = "
* I_YVBPA = "
* I_XSADR = "
* I_YSADR = "
* I_XVTFA = "
* I_YVTFA = "
I_XVTTK = "
I_YVTTK = "
I_XVTTP = "
I_YVTTP = "
I_VTRLK = "
I_VTRLP = "
I_XVTTS = "
I_YVTTS = "
EXCEPTIONS
DO_NOT_SAVE = 1
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_SHIPMENT_HAZMAT_CHECK
I_DG_CHK_START -
Data type: DGPCS_DG_CHK_STARTOptional: No
Call by Reference: No ( called with pass by value option)
I_TVTK - Transport Type
Data type: TVTKOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DISPLAY_MODE -
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TRA_SAVE_CALLER -
Data type: TRA_SAVE_CALLEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SD_SHIPMENT_HAZMAT_CHECK
E_HAZMAT_CHECKS_FAILED -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SD_SHIPMENT_HAZMAT_CHECK
I_TKNUM_RANGE -
Data type: RANGE_C10Optional: Yes
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)
I_XVBPA -
Data type: VBPAVBOptional: Yes
Call by Reference: No ( called with pass by value option)
I_YVBPA -
Data type: VBPAVBOptional: Yes
Call by Reference: No ( called with pass by value option)
I_XSADR -
Data type: SADRVBOptional: Yes
Call by Reference: No ( called with pass by value option)
I_YSADR -
Data type: SADRVBOptional: Yes
Call by Reference: No ( called with pass by value option)
I_XVTFA -
Data type: VTFAVBOptional: Yes
Call by Reference: No ( called with pass by value option)
I_YVTFA -
Data type: VTFAVBOptional: Yes
Call by Reference: No ( called with pass by value option)
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_VTRLK -
Data type: VTRLKOptional: No
Call by Reference: No ( called with pass by value option)
I_VTRLP -
Data type: VTRLPOptional: 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)
EXCEPTIONS details
DO_NOT_SAVE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_SHIPMENT_HAZMAT_CHECK 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_do_not_save | TYPE STRING, " | |||
| lt_i_tknum_range | TYPE STANDARD TABLE OF RANGE_C10, " | |||
| lv_i_dg_chk_start | TYPE DGPCS_DG_CHK_START, " | |||
| lv_e_hazmat_checks_failed | TYPE C, " | |||
| lt_i_xvtsp | TYPE STANDARD TABLE OF VTSPVB, " | |||
| lt_i_yvtsp | TYPE STANDARD TABLE OF VTSPVB, " | |||
| 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_xvtfa | TYPE STANDARD TABLE OF VTFAVB, " | |||
| lt_i_yvtfa | TYPE STANDARD TABLE OF VTFAVB, " | |||
| lv_i_tvtk | TYPE TVTK, " | |||
| lt_i_xvttk | TYPE STANDARD TABLE OF VTTKVB, " | |||
| lt_i_yvttk | TYPE STANDARD TABLE OF VTTKVB, " | |||
| lv_i_display_mode | TYPE C, " ' ' | |||
| lt_i_xvttp | TYPE STANDARD TABLE OF VTTPVB, " | |||
| lv_i_tra_save_caller | TYPE TRA_SAVE_CALLER, " | |||
| lt_i_yvttp | TYPE STANDARD TABLE OF VTTPVB, " | |||
| lt_i_vtrlk | TYPE STANDARD TABLE OF VTRLK, " | |||
| lt_i_vtrlp | TYPE STANDARD TABLE OF VTRLP, " | |||
| lt_i_xvtts | TYPE STANDARD TABLE OF VTTSVB, " | |||
| lt_i_yvtts | TYPE STANDARD TABLE OF VTTSVB. " |
|   CALL FUNCTION 'SD_SHIPMENT_HAZMAT_CHECK' "NOTRANSL: Gefahrgutprüfung Transport |
| EXPORTING | ||
| I_DG_CHK_START | = lv_i_dg_chk_start | |
| I_TVTK | = lv_i_tvtk | |
| I_DISPLAY_MODE | = lv_i_display_mode | |
| I_TRA_SAVE_CALLER | = lv_i_tra_save_caller | |
| IMPORTING | ||
| E_HAZMAT_CHECKS_FAILED | = lv_e_hazmat_checks_failed | |
| TABLES | ||
| I_TKNUM_RANGE | = lt_i_tknum_range | |
| I_XVTSP | = lt_i_xvtsp | |
| I_YVTSP | = lt_i_yvtsp | |
| I_XVBPA | = lt_i_xvbpa | |
| I_YVBPA | = lt_i_yvbpa | |
| I_XSADR | = lt_i_xsadr | |
| I_YSADR | = lt_i_ysadr | |
| I_XVTFA | = lt_i_xvtfa | |
| I_YVTFA | = lt_i_yvtfa | |
| I_XVTTK | = lt_i_xvttk | |
| I_YVTTK | = lt_i_yvttk | |
| I_XVTTP | = lt_i_xvttp | |
| I_YVTTP | = lt_i_yvttp | |
| I_VTRLK | = lt_i_vtrlk | |
| I_VTRLP | = lt_i_vtrlp | |
| I_XVTTS | = lt_i_xvtts | |
| I_YVTTS | = lt_i_yvtts | |
| EXCEPTIONS | ||
| DO_NOT_SAVE = 1 | ||
| . " SD_SHIPMENT_HAZMAT_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM SD_SHIPMENT_HAZMAT_CHECK
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_display_mode) | = ' '. | |||
Search for further information about these or an SAP related objects