SAP SD_SHIPMENT_PLAN_PROPOSAL_INIT Function Module for NOTRANSL: Planungsvorschlag VT01/VT02: Initialisieren
SD_SHIPMENT_PLAN_PROPOSAL_INIT is a standard sd shipment plan proposal init 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: Planungsvorschlag VT01/VT02: 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 plan proposal init FM, simply by entering the name SD_SHIPMENT_PLAN_PROPOSAL_INIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: V56M
Program Name: SAPLV56M
Main Program:
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_SHIPMENT_PLAN_PROPOSAL_INIT 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_PLAN_PROPOSAL_INIT'"NOTRANSL: Planungsvorschlag VT01/VT02: Initialisieren.
EXPORTING
* I_SHIPMENT_TYPE = "Transport Type
* I_PLANNING_PROFILE = "
* I_SPLIT_PROFILE = "
* I_DATA_PROFILE = "
I_VT01_SHIPMENT_TYPE = "
I_VT01_PLANNING_POINT = "
CHANGING
C_PLA_PRO = "
EXCEPTIONS
SHIPMENT_TYPE_NOT_EXISTENT = 1 PLANNING_POINT_NOT_EXISTENT = 2 PLANNING_PROFILE_NOT_EXISTENT = 3 PLANNING_PROFILE_INCOMPATIBLE = 4 SPLIT_PROFILE_NOT_EXISTENT = 5 SPLIT_PROFILE_INCOMPATIBLE = 6 DATA_PROFILE_NOT_EXISTENT = 7 DATA_PROFILE_INCOMPATIBLE = 8
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_SAPLV56M_001 Collective Processing for Shipment: Enhancement of Field Catalog
EXIT_SAPLV56M_002 Collective Processing Shipment: Assign Deliveries to Shipments
EXIT_SAPLV56M_003 Collective Processing Shipment: Filling Generated Shipment Docs with Data
IMPORTING Parameters details for SD_SHIPMENT_PLAN_PROPOSAL_INIT
I_SHIPMENT_TYPE - Transport Type
Data type: TVTK-SHTYPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PLANNING_PROFILE -
Data type: RV56_VT04-PLANNING_PROFILEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SPLIT_PROFILE -
Data type: RV56_VT04-SPLIT_CRITSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATA_PROFILE -
Data type: RV56_VT04-DATA_OPTSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_VT01_SHIPMENT_TYPE -
Data type: TVTK-SHTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_VT01_PLANNING_POINT -
Data type: VTTK-TPLSTOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for SD_SHIPMENT_PLAN_PROPOSAL_INIT
C_PLA_PRO -
Data type: VT04_PLANNING_PROPOSALOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SHIPMENT_TYPE_NOT_EXISTENT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PLANNING_POINT_NOT_EXISTENT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PLANNING_PROFILE_NOT_EXISTENT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PLANNING_PROFILE_INCOMPATIBLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SPLIT_PROFILE_NOT_EXISTENT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SPLIT_PROFILE_INCOMPATIBLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATA_PROFILE_NOT_EXISTENT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATA_PROFILE_INCOMPATIBLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_SHIPMENT_PLAN_PROPOSAL_INIT 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_c_pla_pro | TYPE VT04_PLANNING_PROPOSAL, " | |||
| lv_i_shipment_type | TYPE TVTK-SHTYP, " | |||
| lv_shipment_type_not_existent | TYPE TVTK, " | |||
| lv_i_planning_profile | TYPE RV56_VT04-PLANNING_PROFILE, " | |||
| lv_planning_point_not_existent | TYPE RV56_VT04, " | |||
| lv_i_split_profile | TYPE RV56_VT04-SPLIT_CRITS, " | |||
| lv_planning_profile_not_existent | TYPE RV56_VT04, " | |||
| lv_i_data_profile | TYPE RV56_VT04-DATA_OPTS, " | |||
| lv_planning_profile_incompatible | TYPE RV56_VT04, " | |||
| lv_i_vt01_shipment_type | TYPE TVTK-SHTYP, " | |||
| lv_split_profile_not_existent | TYPE TVTK, " | |||
| lv_i_vt01_planning_point | TYPE VTTK-TPLST, " | |||
| lv_split_profile_incompatible | TYPE VTTK, " | |||
| lv_data_profile_not_existent | TYPE VTTK, " | |||
| lv_data_profile_incompatible | TYPE VTTK. " |
|   CALL FUNCTION 'SD_SHIPMENT_PLAN_PROPOSAL_INIT' "NOTRANSL: Planungsvorschlag VT01/VT02: Initialisieren |
| EXPORTING | ||
| I_SHIPMENT_TYPE | = lv_i_shipment_type | |
| I_PLANNING_PROFILE | = lv_i_planning_profile | |
| I_SPLIT_PROFILE | = lv_i_split_profile | |
| I_DATA_PROFILE | = lv_i_data_profile | |
| I_VT01_SHIPMENT_TYPE | = lv_i_vt01_shipment_type | |
| I_VT01_PLANNING_POINT | = lv_i_vt01_planning_point | |
| CHANGING | ||
| C_PLA_PRO | = lv_c_pla_pro | |
| EXCEPTIONS | ||
| SHIPMENT_TYPE_NOT_EXISTENT = 1 | ||
| PLANNING_POINT_NOT_EXISTENT = 2 | ||
| PLANNING_PROFILE_NOT_EXISTENT = 3 | ||
| PLANNING_PROFILE_INCOMPATIBLE = 4 | ||
| SPLIT_PROFILE_NOT_EXISTENT = 5 | ||
| SPLIT_PROFILE_INCOMPATIBLE = 6 | ||
| DATA_PROFILE_NOT_EXISTENT = 7 | ||
| DATA_PROFILE_INCOMPATIBLE = 8 | ||
| . " SD_SHIPMENT_PLAN_PROPOSAL_INIT | ||
ABAP code using 7.40 inline data declarations to call FM SD_SHIPMENT_PLAN_PROPOSAL_INIT
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 SHTYP FROM TVTK INTO @DATA(ld_i_shipment_type). | ||||
| "SELECT single PLANNING_PROFILE FROM RV56_VT04 INTO @DATA(ld_i_planning_profile). | ||||
| "SELECT single SPLIT_CRITS FROM RV56_VT04 INTO @DATA(ld_i_split_profile). | ||||
| "SELECT single DATA_OPTS FROM RV56_VT04 INTO @DATA(ld_i_data_profile). | ||||
| "SELECT single SHTYP FROM TVTK INTO @DATA(ld_i_vt01_shipment_type). | ||||
| "SELECT single TPLST FROM VTTK INTO @DATA(ld_i_vt01_planning_point). | ||||
Search for further information about these or an SAP related objects