SAP SD_SCDS_SAVE Function Module for NOTRANSL: Frachtkosten sichern









SD_SCDS_SAVE is a standard sd scds save 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 sichern 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 save FM, simply by entering the name SD_SCDS_SAVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: V54U
Program Name: SAPLV54U
Main Program: SAPLV54U
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SD_SCDS_SAVE 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_SAVE'"NOTRANSL: Frachtkosten sichern
EXPORTING
I_T180 = "Screen Sequence Control: Transaction Default Values
* I_OPT_UPDATE_TASK = 'X' "Selection flag
* I_OPT_RELEASE_WITH_DIALOG = 'X' "Selection flag
I_REFOBJ_TAB = "
* I_TCODE = ' ' "ABAP System Field: Current Transaction Code

CHANGING
C_SCD_TAB = "

EXCEPTIONS
NO_CHANGE = 1 NO_SAVE = 2
.




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_SAPLV54U_001 Review of Shipment Costs for Changes
EXIT_SAPLV54U_002 Review of Shipment Costs for Completeness
EXIT_SAPLV54U_003 Specification of shipment cost number
EXIT_SAPLV54U_004 Shipment Cost Processing: Prepare New Objects for Saving
EXIT_SAPLV54U_005 Shipment Cost Processing: Save New Objects
EXIT_SAPLV54U_006 Shipment Purchase Order - Sales Data (Header)
EXIT_SAPLV54U_007 Shipment Purchase Order - Sales Data (Item)

IMPORTING Parameters details for SD_SCDS_SAVE

I_T180 - Screen Sequence Control: Transaction Default Values

Data type: T180
Optional: No
Call by Reference: No ( called with pass by value option)

I_OPT_UPDATE_TASK - Selection flag

Data type: RV54A-SELKZ
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_OPT_RELEASE_WITH_DIALOG - Selection flag

Data type: RV54A-SELKZ
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_REFOBJ_TAB -

Data type: V54A0_REFOBJ_TAB
Optional: No
Call by Reference: Yes

I_TCODE - ABAP System Field: Current Transaction Code

Data type: SY-TCODE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for SD_SCDS_SAVE

C_SCD_TAB -

Data type: V54A0_SCDD_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_CHANGE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_SAVE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SD_SCDS_SAVE 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_i_t180  TYPE T180, "   
lv_c_scd_tab  TYPE V54A0_SCDD_TAB, "   
lv_no_change  TYPE V54A0_SCDD_TAB, "   
lv_no_save  TYPE V54A0_SCDD_TAB, "   
lv_i_opt_update_task  TYPE RV54A-SELKZ, "   'X'
lv_i_opt_release_with_dialog  TYPE RV54A-SELKZ, "   'X'
lv_i_refobj_tab  TYPE V54A0_REFOBJ_TAB, "   
lv_i_tcode  TYPE SY-TCODE. "   SPACE

  CALL FUNCTION 'SD_SCDS_SAVE'  "NOTRANSL: Frachtkosten sichern
    EXPORTING
         I_T180 = lv_i_t180
         I_OPT_UPDATE_TASK = lv_i_opt_update_task
         I_OPT_RELEASE_WITH_DIALOG = lv_i_opt_release_with_dialog
         I_REFOBJ_TAB = lv_i_refobj_tab
         I_TCODE = lv_i_tcode
    CHANGING
         C_SCD_TAB = lv_c_scd_tab
    EXCEPTIONS
        NO_CHANGE = 1
        NO_SAVE = 2
. " SD_SCDS_SAVE




ABAP code using 7.40 inline data declarations to call FM SD_SCDS_SAVE

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 SELKZ FROM RV54A INTO @DATA(ld_i_opt_update_task).
DATA(ld_i_opt_update_task) = 'X'.
 
"SELECT single SELKZ FROM RV54A INTO @DATA(ld_i_opt_release_with_dialog).
DATA(ld_i_opt_release_with_dialog) = 'X'.
 
 
"SELECT single TCODE FROM SY INTO @DATA(ld_i_tcode).
DATA(ld_i_tcode) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!