SAP FM_FUND_CREATE Function Module for
FM_FUND_CREATE is a standard fm fund create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fm fund create FM, simply by entering the name FM_FUND_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FM52
Program Name: SAPLFM52
Main Program: SAPLFM52
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_FUND_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 'FM_FUND_CREATE'".
EXPORTING
IS_FMFINCODE = "
IS_FMFINT = "
* IT_FUNDBPD = "
* I_FLG_TEST = ABAP_TRUE "Test mode
* I_FLG_CHECK_FIELD_STATUS = ABAP_TRUE "
* I_FLG_COMMIT = ABAP_FALSE "
IMPORTING
ET_MESSAGES = "Return Parameters
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_SAPLFM52_001 User exit fund: Customer-specific fields (SAP data -> SUBSCREEN)
EXIT_SAPLFM52_002 User exit fund: Customer-specific fields (SUBSCREEN data -> SAP)
EXIT_SAPLFM52_003 Check Fund
IMPORTING Parameters details for FM_FUND_CREATE
IS_FMFINCODE -
Data type: FMFINCODEOptional: No
Call by Reference: Yes
IS_FMFINT -
Data type: FMFINTOptional: No
Call by Reference: Yes
IT_FUNDBPD -
Data type: FM_T_FUNDBPD_CHANGEOptional: Yes
Call by Reference: Yes
I_FLG_TEST - Test mode
Data type: ABAP_BOOLDefault: ABAP_TRUE
Optional: Yes
Call by Reference: Yes
I_FLG_CHECK_FIELD_STATUS -
Data type: ABAP_BOOLDefault: ABAP_TRUE
Optional: Yes
Call by Reference: Yes
I_FLG_COMMIT -
Data type: ABAP_BOOLDefault: ABAP_FALSE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FM_FUND_CREATE
ET_MESSAGES - Return Parameters
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FM_FUND_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_et_messages | TYPE BAPIRET2_T, " | |||
| lv_is_fmfincode | TYPE FMFINCODE, " | |||
| lv_is_fmfint | TYPE FMFINT, " | |||
| lv_it_fundbpd | TYPE FM_T_FUNDBPD_CHANGE, " | |||
| lv_i_flg_test | TYPE ABAP_BOOL, " ABAP_TRUE | |||
| lv_i_flg_check_field_status | TYPE ABAP_BOOL, " ABAP_TRUE | |||
| lv_i_flg_commit | TYPE ABAP_BOOL. " ABAP_FALSE |
|   CALL FUNCTION 'FM_FUND_CREATE' " |
| EXPORTING | ||
| IS_FMFINCODE | = lv_is_fmfincode | |
| IS_FMFINT | = lv_is_fmfint | |
| IT_FUNDBPD | = lv_it_fundbpd | |
| I_FLG_TEST | = lv_i_flg_test | |
| I_FLG_CHECK_FIELD_STATUS | = lv_i_flg_check_field_status | |
| I_FLG_COMMIT | = lv_i_flg_commit | |
| IMPORTING | ||
| ET_MESSAGES | = lv_et_messages | |
| . " FM_FUND_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM FM_FUND_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.| DATA(ld_i_flg_test) | = ABAP_TRUE. | |||
| DATA(ld_i_flg_check_field_status) | = ABAP_TRUE. | |||
| DATA(ld_i_flg_commit) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects