SAP SD_SHIPMENT_INITIALIZE Function Module for NOTRANSL: Transport initialisieren
SD_SHIPMENT_INITIALIZE is a standard sd shipment initialize 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: Transport initialisieren 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 initialize FM, simply by entering the name SD_SHIPMENT_INITIALIZE into the relevant SAP transaction such as SE37 or SE38.
Function Group: V56C
Program Name: SAPLV56C
Main Program: SAPLV56C
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_SHIPMENT_INITIALIZE 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_INITIALIZE'"NOTRANSL: Transport initialisieren.
EXPORTING
I_VTTK_TPLST = "Transportation planning point
I_VTTK_SHTYP = "Transport Type
I_VTTK_TKNUM = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_EXTNO = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_EXTNK_TTDS = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING
E_VTTKVB = "Shipment header
EXCEPTIONS
WRONG_SHIPMENT_TYPE = 1 WRONG_PLANNING_POINT = 2 EXTERNAL_NUMBER_INVALID = 3 SHIPMENT_BLOCKED = 4 DUPLICATE_SHIPMENT_NUMBER = 5
IMPORTING Parameters details for SD_SHIPMENT_INITIALIZE
I_VTTK_TPLST - Transportation planning point
Data type: TTDS-TPLSTOptional: No
Call by Reference: No ( called with pass by value option)
I_VTTK_SHTYP - Transport Type
Data type: TVTK-SHTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_VTTK_TKNUM - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: VTTK-TKNUMOptional: No
Call by Reference: No ( called with pass by value option)
I_EXTNO - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: VTTKVB-EXTNODefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_EXTNK_TTDS - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: RV56A-SELKZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SD_SHIPMENT_INITIALIZE
E_VTTKVB - Shipment header
Data type: VTTKVBOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_SHIPMENT_TYPE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_PLANNING_POINT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXTERNAL_NUMBER_INVALID - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SHIPMENT_BLOCKED - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DUPLICATE_SHIPMENT_NUMBER - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_SHIPMENT_INITIALIZE 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_e_vttkvb | TYPE VTTKVB, " | |||
| lv_i_vttk_tplst | TYPE TTDS-TPLST, " | |||
| lv_wrong_shipment_type | TYPE TTDS, " | |||
| lv_i_vttk_shtyp | TYPE TVTK-SHTYP, " | |||
| lv_wrong_planning_point | TYPE TVTK, " | |||
| lv_i_vttk_tknum | TYPE VTTK-TKNUM, " | |||
| lv_external_number_invalid | TYPE VTTK, " | |||
| lv_i_extno | TYPE VTTKVB-EXTNO, " SPACE | |||
| lv_shipment_blocked | TYPE VTTKVB, " | |||
| lv_i_extnk_ttds | TYPE RV56A-SELKZ, " SPACE | |||
| lv_duplicate_shipment_number | TYPE RV56A. " |
|   CALL FUNCTION 'SD_SHIPMENT_INITIALIZE' "NOTRANSL: Transport initialisieren |
| EXPORTING | ||
| I_VTTK_TPLST | = lv_i_vttk_tplst | |
| I_VTTK_SHTYP | = lv_i_vttk_shtyp | |
| I_VTTK_TKNUM | = lv_i_vttk_tknum | |
| I_EXTNO | = lv_i_extno | |
| I_EXTNK_TTDS | = lv_i_extnk_ttds | |
| IMPORTING | ||
| E_VTTKVB | = lv_e_vttkvb | |
| EXCEPTIONS | ||
| WRONG_SHIPMENT_TYPE = 1 | ||
| WRONG_PLANNING_POINT = 2 | ||
| EXTERNAL_NUMBER_INVALID = 3 | ||
| SHIPMENT_BLOCKED = 4 | ||
| DUPLICATE_SHIPMENT_NUMBER = 5 | ||
| . " SD_SHIPMENT_INITIALIZE | ||
ABAP code using 7.40 inline data declarations to call FM SD_SHIPMENT_INITIALIZE
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 TPLST FROM TTDS INTO @DATA(ld_i_vttk_tplst). | ||||
| "SELECT single SHTYP FROM TVTK INTO @DATA(ld_i_vttk_shtyp). | ||||
| "SELECT single TKNUM FROM VTTK INTO @DATA(ld_i_vttk_tknum). | ||||
| "SELECT single EXTNO FROM VTTKVB INTO @DATA(ld_i_extno). | ||||
| DATA(ld_i_extno) | = ' '. | |||
| "SELECT single SELKZ FROM RV56A INTO @DATA(ld_i_extnk_ttds). | ||||
| DATA(ld_i_extnk_ttds) | = ' '. | |||
Search for further information about these or an SAP related objects