GM_REV_FM_CUSTOMIZING_GET SAP Function module - Get relevant configuration for GM-FM Interface

GM_REV_FM_CUSTOMIZING_GET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name GM_REV_FM_CUSTOMIZING_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: GMREV
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM GM_REV_FM_CUSTOMIZING_GET - GM REV FM CUSTOMIZING GET

CALL FUNCTION 'GM_REV_FM_CUSTOMIZING_GET' "Get relevant configuration for GM-FM Interface
  EXPORTING
    i_company_code =            " bukrs         Company Code
    i_posting_date =            " budat         Posting date
    i_version =                 " coversi       Version
    i_fmbudget_type =           " gmccsettings-fm_budget_int  FM Budget Integration Ledger
  IMPORTING
    e_gmrev_fm_interface =      " gmrev_fm_interface  GMREV-FM interface
  EXCEPTIONS
    GM_NOT_ACTIVE = 1           "               Grantee not active
    CUSTOMIZING_MISSING = 2     "               Customizing is Missing
    NO_FM_AREA = 3              "               Can not get FM area
    .  "  GM_REV_FM_CUSTOMIZING_GET

ABAP code example for Function Module GM_REV_FM_CUSTOMIZING_GET

The ABAP code below is a full code listing to execute function module GM_REV_FM_CUSTOMIZING_GET including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_gmrev_fm_interface  
 
 TYPE GMREV_FM_INTERFACE
.


DATA(ld_i_company_code) = 'Check type of data required'.

DATA(ld_i_posting_date) = 'Check type of data required'.

DATA(ld_i_version) = 'Check type of data required'.
 

SELECT single FM_BUDGET_INT 
  FROM GMCCSETTINGS 
  INTO @DATA(ld_i_fmbudget_type).

.

CALL FUNCTION 'GM_REV_FM_CUSTOMIZING_GET'
  EXPORTING
    i_company_code =             ld_i_company_code
    i_posting_date =             ld_i_posting_date
    i_version =                  ld_i_version
    i_fmbudget_type =            ld_i_fmbudget_type
  IMPORTING
    e_gmrev_fm_interface =       ld_e_gmrev_fm_interface
  EXCEPTIONS
    GM_NOT_ACTIVE =              1
    CUSTOMIZING_MISSING =        2
    NO_FM_AREA =                 3
    .  "  GM_REV_FM_CUSTOMIZING_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_gmrev_fm_interface
 
 TYPE GMREV_FM_INTERFACE ,
ld_i_company_code
 
 TYPE BUKRS ,
ld_i_posting_date
 
 TYPE BUDAT ,
ld_i_version
 
 TYPE COVERSI ,
ld_i_fmbudget_type
 
 TYPE GMCCSETTINGS-FM_BUDGET_INT .


ld_i_company_code = 'Check type of data required'.
ld_i_posting_date = 'Check type of data required'.
ld_i_version = 'Check type of data required'.

SELECT single FM_BUDGET_INT 
  FROM GMCCSETTINGS 
  INTO ld_i_fmbudget_type.