SAP SD_SCD_GET_INSTANCE Function Module for NOTRANSL: Initialisierung für Frachtkosten BADI's
SD_SCD_GET_INSTANCE is a standard sd scd get instance 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: Initialisierung für Frachtkosten BADI's 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 get instance FM, simply by entering the name SD_SCD_GET_INSTANCE into the relevant SAP transaction such as SE37 or SE38.
Function Group: V54BADI
Program Name: SAPLV54BADI
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_SCD_GET_INSTANCE 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_GET_INSTANCE'"NOTRANSL: Initialisierung für Frachtkosten BADI's.
EXPORTING
I_BADI = "BAdI Def.
CHANGING
C_INTERFACE_REF = "Generic Type
EXCEPTIONS
NO_INITIALIZATION = 1
IMPORTING Parameters details for SD_SCD_GET_INSTANCE
I_BADI - BAdI Def.
Data type: EXIT_DEFOptional: No
Call by Reference: Yes
CHANGING Parameters details for SD_SCD_GET_INSTANCE
C_INTERFACE_REF - Generic Type
Data type: ANYOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_INITIALIZATION - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SD_SCD_GET_INSTANCE 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_badi | TYPE EXIT_DEF, " | |||
| lv_c_interface_ref | TYPE ANY, " | |||
| lv_no_initialization | TYPE ANY. " |
|   CALL FUNCTION 'SD_SCD_GET_INSTANCE' "NOTRANSL: Initialisierung für Frachtkosten BADI's |
| EXPORTING | ||
| I_BADI | = lv_i_badi | |
| CHANGING | ||
| C_INTERFACE_REF | = lv_c_interface_ref | |
| EXCEPTIONS | ||
| NO_INITIALIZATION = 1 | ||
| . " SD_SCD_GET_INSTANCE | ||
ABAP code using 7.40 inline data declarations to call FM SD_SCD_GET_INSTANCE
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.Search for further information about these or an SAP related objects