SAP RM_FIMA_ANALYSIS Function Module for RM-FIMA: Risik Analysis









RM_FIMA_ANALYSIS is a standard rm fima analysis SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RM-FIMA: Risik Analysis 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 rm fima analysis FM, simply by entering the name RM_FIMA_ANALYSIS into the relevant SAP transaction such as SE37 or SE38.

Function Group: RMR1
Program Name: SAPLRMR1
Main Program: SAPLRMR1
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RM_FIMA_ANALYSIS 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 'RM_FIMA_ANALYSIS'"RM-FIMA: Risik Analysis
EXPORTING
SPARA = "
SFGDT = "

IMPORTING
E_STATUS = "Return Value, Return Value after ABAP Statements

TABLES
I_METH = "
* E_MEO = "Profitability Segment RM_FIMA_BASIS
* E_EOOPT = "RM additional object for options- single value analysis NPV
* E_ERROR = "
* E_EONPV = "
* E_EOBAR = "
* E_EOPOS = "
* E_EOBVAR = "
* E_EODD = "
* E_EOVAR10 = "RM Results Object for P+L 10 Times per BP
* E_EORA = "RM Interim Result Object - NPV Style
.



IMPORTING Parameters details for RM_FIMA_ANALYSIS

SPARA -

Data type: JBRHSSPARI
Optional: No
Call by Reference: Yes

SFGDT -

Data type: TVS_SFGDT_TAB
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for RM_FIMA_ANALYSIS

E_STATUS - Return Value, Return Value after ABAP Statements

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

TABLES Parameters details for RM_FIMA_ANALYSIS

I_METH -

Data type: VTVFIMA
Optional: No
Call by Reference: No ( called with pass by value option)

E_MEO - Profitability Segment RM_FIMA_BASIS

Data type: TVM_MEO_TAB
Optional: Yes
Call by Reference: Yes

E_EOOPT - RM additional object for options- single value analysis NPV

Data type: VTVEOOPT
Optional: Yes
Call by Reference: Yes

E_ERROR -

Data type: BAPIERR
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_EONPV -

Data type: VTVEONPV
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_EOBAR -

Data type: VTVEOBAR
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_EOPOS -

Data type: VTVEOPOS
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_EOBVAR -

Data type: VTVEOBVAR
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_EODD -

Data type: VTVEODD
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_EOVAR10 - RM Results Object for P+L 10 Times per BP

Data type: VTVEOVAR10
Optional: Yes
Call by Reference: Yes

E_EORA - RM Interim Result Object - NPV Style

Data type: VTVEORA
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for RM_FIMA_ANALYSIS 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_spara  TYPE JBRHSSPARI, "   
lt_i_meth  TYPE STANDARD TABLE OF VTVFIMA, "   
lv_e_status  TYPE SY-SUBRC, "   
lt_e_meo  TYPE STANDARD TABLE OF TVM_MEO_TAB, "   
lt_e_eoopt  TYPE STANDARD TABLE OF VTVEOOPT, "   
lv_sfgdt  TYPE TVS_SFGDT_TAB, "   
lt_e_error  TYPE STANDARD TABLE OF BAPIERR, "   
lt_e_eonpv  TYPE STANDARD TABLE OF VTVEONPV, "   
lt_e_eobar  TYPE STANDARD TABLE OF VTVEOBAR, "   
lt_e_eopos  TYPE STANDARD TABLE OF VTVEOPOS, "   
lt_e_eobvar  TYPE STANDARD TABLE OF VTVEOBVAR, "   
lt_e_eodd  TYPE STANDARD TABLE OF VTVEODD, "   
lt_e_eovar10  TYPE STANDARD TABLE OF VTVEOVAR10, "   
lt_e_eora  TYPE STANDARD TABLE OF VTVEORA. "   

  CALL FUNCTION 'RM_FIMA_ANALYSIS'  "RM-FIMA: Risik Analysis
    EXPORTING
         SPARA = lv_spara
         SFGDT = lv_sfgdt
    IMPORTING
         E_STATUS = lv_e_status
    TABLES
         I_METH = lt_i_meth
         E_MEO = lt_e_meo
         E_EOOPT = lt_e_eoopt
         E_ERROR = lt_e_error
         E_EONPV = lt_e_eonpv
         E_EOBAR = lt_e_eobar
         E_EOPOS = lt_e_eopos
         E_EOBVAR = lt_e_eobvar
         E_EODD = lt_e_eodd
         E_EOVAR10 = lt_e_eovar10
         E_EORA = lt_e_eora
. " RM_FIMA_ANALYSIS




ABAP code using 7.40 inline data declarations to call FM RM_FIMA_ANALYSIS

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.

 
 
"SELECT single SUBRC FROM SY INTO @DATA(ld_e_status).
 
 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!