SAP Function Modules

comments icon Comments

FVD_CHARGE_API_ACTIVATE SAP Function module - Activate Existing Business Operation







FVD_CHARGE_API_ACTIVATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FVD_CHARGE_API_ACTIVATE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FVD_CHARGE_API
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM FVD_CHARGE_API_ACTIVATE - FVD CHARGE API ACTIVATE 





CALL FUNCTION 'FVD_CHARGE_API_ACTIVATE' "Activate Existing Business Operation
  EXPORTING
    i_s_bo_key =                " fvd_bo_key    Business Operation Key Structure
    i_flg_testrun =             " flag          General Indicator
    i_flg_no_confirmation =     " flag          General Indicator
    i_flg_no_enqueue =          " flag          General Indicator
*   i_calln_appln = 'INT'       " tb_callng_appln  Calling Application
  IMPORTING
    e_s_rcharge =               " rcharge       Interface Structure and Control Data Charges
    e_tab_bapierr =             " bapierr_t     Table Types for Error Handling
    e_rbo =                     " rbo           Business operation number (loans)
  EXCEPTIONS
    FATAL_ERROR = 1             "
    .  "  FVD_CHARGE_API_ACTIVATE

ABAP code example for Function Module FVD_CHARGE_API_ACTIVATE





The ABAP code below is a full code listing to execute function module FVD_CHARGE_API_ACTIVATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_s_rcharge    TYPE RCHARGE
,
ld_e_tab_bapierr    TYPE BAPIERR_T
,
ld_e_rbo    TYPE RBO
.




DATA(ld_i_s_bo_key) = 'Check type of data required'.

DATA(ld_i_flg_testrun) = 'Check type of data required'.

DATA(ld_i_flg_no_confirmation) = 'Check type of data required'.

DATA(ld_i_flg_no_enqueue) = 'Check type of data required'.

DATA(ld_i_calln_appln) = 'Check type of data required'.
.

CALL FUNCTION 'FVD_CHARGE_API_ACTIVATE'
  EXPORTING
    i_s_bo_key =                 ld_i_s_bo_key
    i_flg_testrun =              ld_i_flg_testrun
    i_flg_no_confirmation =      ld_i_flg_no_confirmation
    i_flg_no_enqueue =           ld_i_flg_no_enqueue
*   i_calln_appln =              ld_i_calln_appln
  IMPORTING
    e_s_rcharge =                ld_e_s_rcharge
    e_tab_bapierr =              ld_e_tab_bapierr
    e_rbo =                      ld_e_rbo
  EXCEPTIONS
    FATAL_ERROR =                1
    .  "  FVD_CHARGE_API_ACTIVATE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_e_s_rcharge  TYPE RCHARGE ,
ld_i_s_bo_key  TYPE FVD_BO_KEY ,
ld_e_tab_bapierr  TYPE BAPIERR_T ,
ld_i_flg_testrun  TYPE FLAG ,
ld_e_rbo  TYPE RBO ,
ld_i_flg_no_confirmation  TYPE FLAG ,
ld_i_flg_no_enqueue  TYPE FLAG ,
ld_i_calln_appln  TYPE TB_CALLNG_APPLN .




ld_i_s_bo_key = 'Check type of data required'.
ld_i_flg_testrun = 'Check type of data required'.
ld_i_flg_no_confirmation = 'Check type of data required'.
ld_i_flg_no_enqueue = 'Check type of data required'.
ld_i_calln_appln = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FVD_CHARGE_API_ACTIVATE or its description.


   
 

FVD_CHARGE_API_ACTIVATE - Activate Existing Business Operation
FVD_CHANGEDOC_PREPARE_FIELDV - API: Format Field Values
FVD_CHANGEDOCUMENT_OBJID - Text for Object Value
FVD_CFLOW_SKIP_FOR_PAYOFF - 
FVD_CFLOW_SCHEDULE_CREATE - 
FVD_CFLOW_NEXT_DUE_DATE_FIND -