SAP FVD_CHARGE_API_CHANGE Function Module for Change Existing Business Operation









FVD_CHARGE_API_CHANGE is a standard fvd charge api change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Existing Business Operation 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 fvd charge api change FM, simply by entering the name FVD_CHARGE_API_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function FVD_CHARGE_API_CHANGE 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 'FVD_CHARGE_API_CHANGE'"Change Existing Business Operation
EXPORTING
I_S_RCHARGE_API = "Handling Type
I_TAB_ADDFLOW = "Table Type for RBOBEPP_API (Standard)
I_FLG_TESTRUN = "General Indicator
* I_CALLN_APPLN = 'INT' "Calling Application

IMPORTING
E_S_RCHARGE = "Interface Structure and Control Data Charges
E_TAB_BAPIERR = "Table Types for Error Handling
E_RBO = "Business operation number (loans)

EXCEPTIONS
FATAL_ERROR = 1 MANDATE_NOT_VALID = 2 SEPA_ERROR = 3
.



IMPORTING Parameters details for FVD_CHARGE_API_CHANGE

I_S_RCHARGE_API - Handling Type

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

I_TAB_ADDFLOW - Table Type for RBOBEPP_API (Standard)

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

I_FLG_TESTRUN - General Indicator

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

I_CALLN_APPLN - Calling Application

Data type: TB_CALLNG_APPLN
Default: 'INT'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FVD_CHARGE_API_CHANGE

E_S_RCHARGE - Interface Structure and Control Data Charges

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

E_TAB_BAPIERR - Table Types for Error Handling

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

E_RBO - Business operation number (loans)

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

EXCEPTIONS details

FATAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

MANDATE_NOT_VALID - Invalid SEPA Mandate for an EDD Payment Method

Data type:
Optional: No
Call by Reference: Yes

SEPA_ERROR - SEPA Information Cannot Be Processed

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FVD_CHARGE_API_CHANGE 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_s_rcharge  TYPE RCHARGE, "   
lv_fatal_error  TYPE RCHARGE, "   
lv_i_s_rcharge_api  TYPE RCHARGE_API, "   
lv_e_tab_bapierr  TYPE BAPIERR_T, "   
lv_i_tab_addflow  TYPE TRTY_RBOBEPP_API, "   
lv_mandate_not_valid  TYPE TRTY_RBOBEPP_API, "   
lv_e_rbo  TYPE RBO, "   
lv_sepa_error  TYPE RBO, "   
lv_i_flg_testrun  TYPE FLAG, "   
lv_i_calln_appln  TYPE TB_CALLNG_APPLN. "   'INT'

  CALL FUNCTION 'FVD_CHARGE_API_CHANGE'  "Change Existing Business Operation
    EXPORTING
         I_S_RCHARGE_API = lv_i_s_rcharge_api
         I_TAB_ADDFLOW = lv_i_tab_addflow
         I_FLG_TESTRUN = lv_i_flg_testrun
         I_CALLN_APPLN = lv_i_calln_appln
    IMPORTING
         E_S_RCHARGE = lv_e_s_rcharge
         E_TAB_BAPIERR = lv_e_tab_bapierr
         E_RBO = lv_e_rbo
    EXCEPTIONS
        FATAL_ERROR = 1
        MANDATE_NOT_VALID = 2
        SEPA_ERROR = 3
. " FVD_CHARGE_API_CHANGE




ABAP code using 7.40 inline data declarations to call FM FVD_CHARGE_API_CHANGE

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.

 
 
 
 
 
 
 
 
 
DATA(ld_i_calln_appln) = 'INT'.
 


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!