SAP RTP_US_API_CALCULATE_FMV_REP Function Module for Calculates the FMV for a set of retirement plans
RTP_US_API_CALCULATE_FMV_REP is a standard rtp us api calculate fmv rep SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Calculates the FMV for a set of retirement plans 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 rtp us api calculate fmv rep FM, simply by entering the name RTP_US_API_CALCULATE_FMV_REP into the relevant SAP transaction such as SE37 or SE38.
Function Group: RTP_US_API_REPORT
Program Name: SAPLRTP_US_API_REPORT
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RTP_US_API_CALCULATE_FMV_REP 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 'RTP_US_API_CALCULATE_FMV_REP'"Calculates the FMV for a set of retirement plans.
EXPORTING
* I_YEAR = "Calendar year
I_FLG_SIMULATION = "Simulation run; no database updates
I_FLG_REAL_RUN = "Database updates; no printing
I_FLG_PRINT = "Database updates and printing
TABLES
* T_BKKRS = "BCA: Structure bank area (RANGE)
* T_PLAN_NUMBER = "Structure for range of a plannumber
* T_TYPE_CODE = "Structure for range of a plan type
* T_PARTNER = "Structure for range of a partner number
EXCEPTIONS
INITIALIZATION_ERROR = 1 DATABASE_ERROR = 2
IMPORTING Parameters details for RTP_US_API_CALCULATE_FMV_REP
I_YEAR - Calendar year
Data type: IRTP_US_PLAN_REPORT-CALENDAR_YEAROptional: Yes
Call by Reference: Yes
I_FLG_SIMULATION - Simulation run; no database updates
Data type: IRTP_US_FMV_SELECTION-SEL_SIMULATIONOptional: No
Call by Reference: Yes
I_FLG_REAL_RUN - Database updates; no printing
Data type: IRTP_US_FMV_SELECTION-SEL_REAL_RUNOptional: No
Call by Reference: Yes
I_FLG_PRINT - Database updates and printing
Data type: IRTP_US_FMV_SELECTION-SEL_PRINTOptional: No
Call by Reference: Yes
TABLES Parameters details for RTP_US_API_CALCULATE_FMV_REP
T_BKKRS - BCA: Structure bank area (RANGE)
Data type: IBKK_RNG_BKKRSOptional: Yes
Call by Reference: Yes
T_PLAN_NUMBER - Structure for range of a plannumber
Data type: IRTP_US_RNG_PLANNUMBEROptional: Yes
Call by Reference: Yes
T_TYPE_CODE - Structure for range of a plan type
Data type: IRTP_US_RNG_PLAN_TYPEOptional: Yes
Call by Reference: Yes
T_PARTNER - Structure for range of a partner number
Data type: IRTP_US_RNG_PARTNER_NUMBEROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INITIALIZATION_ERROR -
Data type:Optional: No
Call by Reference: Yes
DATABASE_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RTP_US_API_CALCULATE_FMV_REP 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_year | TYPE IRTP_US_PLAN_REPORT-CALENDAR_YEAR, " | |||
| lt_t_bkkrs | TYPE STANDARD TABLE OF IBKK_RNG_BKKRS, " | |||
| lv_initialization_error | TYPE IBKK_RNG_BKKRS, " | |||
| lt_t_plan_number | TYPE STANDARD TABLE OF IRTP_US_RNG_PLANNUMBER, " | |||
| lv_database_error | TYPE IRTP_US_RNG_PLANNUMBER, " | |||
| lv_i_flg_simulation | TYPE IRTP_US_FMV_SELECTION-SEL_SIMULATION, " | |||
| lt_t_type_code | TYPE STANDARD TABLE OF IRTP_US_RNG_PLAN_TYPE, " | |||
| lv_i_flg_real_run | TYPE IRTP_US_FMV_SELECTION-SEL_REAL_RUN, " | |||
| lt_t_partner | TYPE STANDARD TABLE OF IRTP_US_RNG_PARTNER_NUMBER, " | |||
| lv_i_flg_print | TYPE IRTP_US_FMV_SELECTION-SEL_PRINT. " |
|   CALL FUNCTION 'RTP_US_API_CALCULATE_FMV_REP' "Calculates the FMV for a set of retirement plans |
| EXPORTING | ||
| I_YEAR | = lv_i_year | |
| I_FLG_SIMULATION | = lv_i_flg_simulation | |
| I_FLG_REAL_RUN | = lv_i_flg_real_run | |
| I_FLG_PRINT | = lv_i_flg_print | |
| TABLES | ||
| T_BKKRS | = lt_t_bkkrs | |
| T_PLAN_NUMBER | = lt_t_plan_number | |
| T_TYPE_CODE | = lt_t_type_code | |
| T_PARTNER | = lt_t_partner | |
| EXCEPTIONS | ||
| INITIALIZATION_ERROR = 1 | ||
| DATABASE_ERROR = 2 | ||
| . " RTP_US_API_CALCULATE_FMV_REP | ||
ABAP code using 7.40 inline data declarations to call FM RTP_US_API_CALCULATE_FMV_REP
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 CALENDAR_YEAR FROM IRTP_US_PLAN_REPORT INTO @DATA(ld_i_year). | ||||
| "SELECT single SEL_SIMULATION FROM IRTP_US_FMV_SELECTION INTO @DATA(ld_i_flg_simulation). | ||||
| "SELECT single SEL_REAL_RUN FROM IRTP_US_FMV_SELECTION INTO @DATA(ld_i_flg_real_run). | ||||
| "SELECT single SEL_PRINT FROM IRTP_US_FMV_SELECTION INTO @DATA(ld_i_flg_print). | ||||
Search for further information about these or an SAP related objects