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

Function SD_SCD_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_SCD_INITIALIZE'"NOTRANSL: Frachtkosten initialisieren.
EXPORTING
I_TVTF = "
* I_PRSDT = "
* I_BUDAT = "
I_REFOBJ = "
* I_OPT_SCD_SIM = "
CHANGING
C_SCD = "
EXCEPTIONS
PLANNING_POINT_NOT_VALID = 1 SCD_TYPE_NOT_VALID = 2 SCD_CREATE_NOT_POSSIBLE = 3
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_SAPLV54C_001 Determine Texts for Shipment Cost Items
EXIT_SAPLV54C_002 Shipment Cost Calculation: Generation of Shipment Cost Subitems
EXIT_SAPLV54C_003 Shipment Costs Processing: Determine Invoicing Party
EXIT_SAPLV54C_004 Shipment Costs Processing: Determine Loc. for Tax Invoice
IMPORTING Parameters details for SD_SCD_INITIALIZE
I_TVTF -
Data type: TVTFOptional: No
Call by Reference: No ( called with pass by value option)
I_PRSDT -
Data type: VFKK-PRSDTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BUDAT -
Data type: VFKK-BUDATOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REFOBJ -
Data type: V54A0_REFOBJOptional: No
Call by Reference: Yes
I_OPT_SCD_SIM -
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for SD_SCD_INITIALIZE
C_SCD -
Data type: V54A0_SCDDOptional: No
Call by Reference: Yes
EXCEPTIONS details
PLANNING_POINT_NOT_VALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SCD_TYPE_NOT_VALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SCD_CREATE_NOT_POSSIBLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_SCD_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_c_scd | TYPE V54A0_SCDD, " | |||
| lv_i_tvtf | TYPE TVTF, " | |||
| lv_planning_point_not_valid | TYPE TVTF, " | |||
| lv_i_prsdt | TYPE VFKK-PRSDT, " | |||
| lv_scd_type_not_valid | TYPE VFKK, " | |||
| lv_i_budat | TYPE VFKK-BUDAT, " | |||
| lv_scd_create_not_possible | TYPE VFKK, " | |||
| lv_i_refobj | TYPE V54A0_REFOBJ, " | |||
| lv_i_opt_scd_sim | TYPE I. " |
|   CALL FUNCTION 'SD_SCD_INITIALIZE' "NOTRANSL: Frachtkosten initialisieren |
| EXPORTING | ||
| I_TVTF | = lv_i_tvtf | |
| I_PRSDT | = lv_i_prsdt | |
| I_BUDAT | = lv_i_budat | |
| I_REFOBJ | = lv_i_refobj | |
| I_OPT_SCD_SIM | = lv_i_opt_scd_sim | |
| CHANGING | ||
| C_SCD | = lv_c_scd | |
| EXCEPTIONS | ||
| PLANNING_POINT_NOT_VALID = 1 | ||
| SCD_TYPE_NOT_VALID = 2 | ||
| SCD_CREATE_NOT_POSSIBLE = 3 | ||
| . " SD_SCD_INITIALIZE | ||
ABAP code using 7.40 inline data declarations to call FM SD_SCD_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 PRSDT FROM VFKK INTO @DATA(ld_i_prsdt). | ||||
| "SELECT single BUDAT FROM VFKK INTO @DATA(ld_i_budat). | ||||
Search for further information about these or an SAP related objects