SAP GM_GET_FM_CUSTOMIZING Function Module for Get relevant configuration for GM-FM Interface
GM_GET_FM_CUSTOMIZING is a standard gm get fm customizing 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 relevant configuration for GM-FM Interface 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 gm get fm customizing FM, simply by entering the name GM_GET_FM_CUSTOMIZING into the relevant SAP transaction such as SE37 or SE38.
Function Group: GMGRBD
Program Name: SAPLGMGRBD
Main Program: SAPLGMGRBD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GM_GET_FM_CUSTOMIZING 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 'GM_GET_FM_CUSTOMIZING'"Get relevant configuration for GM-FM Interface.
EXPORTING
I_COMPANY_CODE = "Company Code
I_GRANT_NBR = "Grant
I_DOC_TYPE = "Budget Document Type
I_PROCESS = "GM Budgeting User Interface Process
I_FROM_DATE = "Date
IMPORTING
E_FM_OBJECTS = "
EXCEPTIONS
FM_NOT_ACTIVE = 1 CUSTOMIZING_MISSING = 2
IMPORTING Parameters details for GM_GET_FM_CUSTOMIZING
I_COMPANY_CODE - Company Code
Data type: BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_GRANT_NBR - Grant
Data type: GM_GRANT_NBROptional: No
Call by Reference: No ( called with pass by value option)
I_DOC_TYPE - Budget Document Type
Data type: GM_BDGT_DOC_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_PROCESS - GM Budgeting User Interface Process
Data type: GM_BDGT_PROCESSOptional: No
Call by Reference: No ( called with pass by value option)
I_FROM_DATE - Date
Data type: DATUMOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GM_GET_FM_CUSTOMIZING
E_FM_OBJECTS -
Data type: GMBU_F_FM_OBJECTSOptional: No
Call by Reference: Yes
EXCEPTIONS details
FM_NOT_ACTIVE - FM Integration not active
Data type:Optional: No
Call by Reference: Yes
CUSTOMIZING_MISSING - Customizing is Missing
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GM_GET_FM_CUSTOMIZING 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_e_fm_objects | TYPE GMBU_F_FM_OBJECTS, " | |||
| lv_fm_not_active | TYPE GMBU_F_FM_OBJECTS, " | |||
| lv_i_company_code | TYPE BUKRS, " | |||
| lv_i_grant_nbr | TYPE GM_GRANT_NBR, " | |||
| lv_customizing_missing | TYPE GM_GRANT_NBR, " | |||
| lv_i_doc_type | TYPE GM_BDGT_DOC_TYPE, " | |||
| lv_i_process | TYPE GM_BDGT_PROCESS, " | |||
| lv_i_from_date | TYPE DATUM. " |
|   CALL FUNCTION 'GM_GET_FM_CUSTOMIZING' "Get relevant configuration for GM-FM Interface |
| EXPORTING | ||
| I_COMPANY_CODE | = lv_i_company_code | |
| I_GRANT_NBR | = lv_i_grant_nbr | |
| I_DOC_TYPE | = lv_i_doc_type | |
| I_PROCESS | = lv_i_process | |
| I_FROM_DATE | = lv_i_from_date | |
| IMPORTING | ||
| E_FM_OBJECTS | = lv_e_fm_objects | |
| EXCEPTIONS | ||
| FM_NOT_ACTIVE = 1 | ||
| CUSTOMIZING_MISSING = 2 | ||
| . " GM_GET_FM_CUSTOMIZING | ||
ABAP code using 7.40 inline data declarations to call FM GM_GET_FM_CUSTOMIZING
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