SAP FMSP_STRATEGY_FROM_BADI Function Module for Get Strategy Environment from BADI
FMSP_STRATEGY_FROM_BADI is a standard fmsp strategy from badi SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Strategy Environment from BADI 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 fmsp strategy from badi FM, simply by entering the name FMSP_STRATEGY_FROM_BADI into the relevant SAP transaction such as SE37 or SE38.
Function Group: FM_SPLIT_DERIVE
Program Name: SAPLFM_SPLIT_DERIVE
Main Program: SAPLFM_SPLIT_DERIVE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMSP_STRATEGY_FROM_BADI 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 'FMSP_STRATEGY_FROM_BADI'"Get Strategy Environment from BADI.
EXPORTING
I_DERIVE = "Derivation Structure for FM account assignment splitting
CHANGING
C_STRATEGY = "Environment for strategy
IMPORTING Parameters details for FMSP_STRATEGY_FROM_BADI
I_DERIVE - Derivation Structure for FM account assignment splitting
Data type: FMSPLIT_DERIVEOptional: No
Call by Reference: Yes
CHANGING Parameters details for FMSP_STRATEGY_FROM_BADI
C_STRATEGY - Environment for strategy
Data type: ABADRENVOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMSP_STRATEGY_FROM_BADI 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_derive | TYPE FMSPLIT_DERIVE, " | |||
| lv_c_strategy | TYPE ABADRENV. " |
|   CALL FUNCTION 'FMSP_STRATEGY_FROM_BADI' "Get Strategy Environment from BADI |
| EXPORTING | ||
| I_DERIVE | = lv_i_derive | |
| CHANGING | ||
| C_STRATEGY | = lv_c_strategy | |
| . " FMSP_STRATEGY_FROM_BADI | ||
ABAP code using 7.40 inline data declarations to call FM FMSP_STRATEGY_FROM_BADI
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