SAP SD_SCDS_CREATE Function Module for NOTRANSL: Frachtkosten anlegen (online, batch)
SD_SCDS_CREATE is a standard sd scds create 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 anlegen (online, batch) 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 scds create FM, simply by entering the name SD_SCDS_CREATE 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_SCDS_CREATE 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_SCDS_CREATE'"NOTRANSL: Frachtkosten anlegen (online, batch).
EXPORTING
* I_OPT_PACKAGE_SIZE = '1' "
* I_OPT_LOG_SAVE = 'X' "
* I_OPT_COMMIT = 'X' "
* I_FKART = ' ' "Shipment Cost Type
* I_PRSDT = "Pricing Date
* I_BUDAT = "Settlement Date
IMPORTING
E_REFOBJ_RANGE_LOCKED = "
CHANGING
C_REFOBJ_RANGE = "
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_SCDS_CREATE
I_OPT_PACKAGE_SIZE -
Data type: RV54A-PACSZDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_OPT_LOG_SAVE -
Data type: BOOLE_DDefault: 'X'
Optional: Yes
Call by Reference: Yes
I_OPT_COMMIT -
Data type: BOOLE_DDefault: 'X'
Optional: Yes
Call by Reference: Yes
I_FKART - Shipment Cost Type
Data type: FKART_TDefault: ' '
Optional: Yes
Call by Reference: Yes
I_PRSDT - Pricing Date
Data type: PRSDT_KOptional: Yes
Call by Reference: Yes
I_BUDAT - Settlement Date
Data type: BUDAT_KOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for SD_SCDS_CREATE
E_REFOBJ_RANGE_LOCKED -
Data type: V54A0_REF_TABOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for SD_SCDS_CREATE
C_REFOBJ_RANGE -
Data type: V54A0_REF_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SD_SCDS_CREATE 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_refobj_range | TYPE V54A0_REF_TAB, " | |||
| lv_i_opt_package_size | TYPE RV54A-PACSZ, " '1' | |||
| lv_e_refobj_range_locked | TYPE V54A0_REF_TAB, " | |||
| lv_i_opt_log_save | TYPE BOOLE_D, " 'X' | |||
| lv_i_opt_commit | TYPE BOOLE_D, " 'X' | |||
| lv_i_fkart | TYPE FKART_T, " ' ' | |||
| lv_i_prsdt | TYPE PRSDT_K, " | |||
| lv_i_budat | TYPE BUDAT_K. " |
|   CALL FUNCTION 'SD_SCDS_CREATE' "NOTRANSL: Frachtkosten anlegen (online, batch) |
| EXPORTING | ||
| I_OPT_PACKAGE_SIZE | = lv_i_opt_package_size | |
| I_OPT_LOG_SAVE | = lv_i_opt_log_save | |
| I_OPT_COMMIT | = lv_i_opt_commit | |
| I_FKART | = lv_i_fkart | |
| I_PRSDT | = lv_i_prsdt | |
| I_BUDAT | = lv_i_budat | |
| IMPORTING | ||
| E_REFOBJ_RANGE_LOCKED | = lv_e_refobj_range_locked | |
| CHANGING | ||
| C_REFOBJ_RANGE | = lv_c_refobj_range | |
| . " SD_SCDS_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM SD_SCDS_CREATE
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 PACSZ FROM RV54A INTO @DATA(ld_i_opt_package_size). | ||||
| DATA(ld_i_opt_package_size) | = '1'. | |||
| DATA(ld_i_opt_log_save) | = 'X'. | |||
| DATA(ld_i_opt_commit) | = 'X'. | |||
| DATA(ld_i_fkart) | = ' '. | |||
Search for further information about these or an SAP related objects