SAP RTP_US_API_DB_MODIFY_FMV Function Module for Bridging function for updating the dbase table rtp_us_tot









RTP_US_API_DB_MODIFY_FMV is a standard rtp us api db modify fmv SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Bridging function for updating the dbase table rtp_us_tot 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 db modify fmv FM, simply by entering the name RTP_US_API_DB_MODIFY_FMV 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_DB_MODIFY_FMV 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_DB_MODIFY_FMV'"Bridging function for updating the dbase table rtp_us_tot
 IMPORTING
   E_UPDATED =  "
   E_INSERTED =  "

TABLES
*  T_FMV =  "Total amounts for a retirement plan

EXCEPTIONS
   UPDATE_FAILED = 1    INSERT_FAILED = 2
.



EXPORTING Parameters details for RTP_US_API_DB_MODIFY_FMV

E_UPDATED -

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

E_INSERTED -

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

TABLES Parameters details for RTP_US_API_DB_MODIFY_FMV

T_FMV - Total amounts for a retirement plan

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

EXCEPTIONS details

UPDATE_FAILED -

Data type:
Optional: No
Call by Reference: Yes

INSERT_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RTP_US_API_DB_MODIFY_FMV 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:
lt_t_fmv  TYPE STANDARD TABLE OF RTP_US_TOT, "   
lv_e_updated  TYPE I, "   
lv_update_failed  TYPE I, "   
lv_e_inserted  TYPE I, "   
lv_insert_failed  TYPE I. "   

  CALL FUNCTION 'RTP_US_API_DB_MODIFY_FMV'  "Bridging function for updating the dbase table rtp_us_tot
    IMPORTING
         E_UPDATED = lv_e_updated
         E_INSERTED = lv_e_inserted
    TABLES
         T_FMV = lt_t_fmv
    EXCEPTIONS
        UPDATE_FAILED = 1
        INSERT_FAILED = 2
. " RTP_US_API_DB_MODIFY_FMV




ABAP code using 7.40 inline data declarations to call FM RTP_US_API_DB_MODIFY_FMV

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



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!