SAP FVD_CHARGE_API_ACTIVATE Function Module for Activate Existing Business Operation

Search SAP Function Modules

FVD_CHARGE_API_ACTIVATE is a standard fvd charge api activate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Activate 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 activate FM, simply by entering the name FVD_CHARGE_API_ACTIVATE 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_ACTIVATE 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_ACTIVATE'"Activate Existing Business Operation
  EXPORTING
   I_S_BO_KEY =  "Business Operation Key Structure
   I_FLG_TESTRUN =  "General Indicator
   I_FLG_NO_CONFIRMATION =  "General Indicator
   I_FLG_NO_ENQUEUE =  "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 

.

IMPORTING Parameters details for FVD_CHARGE_API_ACTIVATE

I_S_BO_KEY - Business Operation Key Structure

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

I_FLG_TESTRUN - General Indicator

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

I_FLG_NO_CONFIRMATION - General Indicator

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

I_FLG_NO_ENQUEUE - 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_ACTIVATE

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

Copy and paste ABAP code example for FVD_CHARGE_API_ACTIVATE 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.

ABAP code using 7.40 inline data declarations to call FM FVD_CHARGE_API_ACTIVATE

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