SAP Function Modules

comments icon Comments

FVD_CHARGE_API_POST SAP Function module - Post Existing Business Operation







FVD_CHARGE_API_POST 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_POST 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_POST - FVD CHARGE API POST 





CALL FUNCTION 'FVD_CHARGE_API_POST' "Post Existing Business Operation
  EXPORTING
    i_s_bo_key =                " fvd_bo_key    Business Operation Key Structure
    i_flg_no_confirmation =     " flag          General Indicator
    i_flg_no_enqueue =          " flag          General Indicator
    i_s_post_info =             " rcharge_bo_postinfo_ui  Posting Information
*   i_calln_appln = 'INT'       " tb_callng_appln  Calling Application
  IMPORTING
    e_s_rcharge =               " rcharge       Interface Structure and Control Data Charges
    e_rbo =                     " rbo           Business operation number (loans)
    e_tab_bapierr =             " bapierr_t     Table Types for Error Handling
    e_tab_vdbeki =              " trty_vdbeki   Table Type for Table VDBEKI
    e_tab_vdbepi =              " trty_vdbepi   Table Type for Table VDBEPI
  EXCEPTIONS
    FATAL_ERROR = 1             "
    .  "  FVD_CHARGE_API_POST

ABAP code example for Function Module FVD_CHARGE_API_POST





The ABAP code below is a full code listing to execute function module FVD_CHARGE_API_POST 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_rbo    TYPE RBO
,
ld_e_tab_bapierr    TYPE BAPIERR_T
,
ld_e_tab_vdbeki    TYPE TRTY_VDBEKI
,
ld_e_tab_vdbepi    TYPE TRTY_VDBEPI
.




DATA(ld_i_s_bo_key) = '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_s_post_info) = 'Check type of data required'.

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

CALL FUNCTION 'FVD_CHARGE_API_POST'
  EXPORTING
    i_s_bo_key =                 ld_i_s_bo_key
    i_flg_no_confirmation =      ld_i_flg_no_confirmation
    i_flg_no_enqueue =           ld_i_flg_no_enqueue
    i_s_post_info =              ld_i_s_post_info
*   i_calln_appln =              ld_i_calln_appln
  IMPORTING
    e_s_rcharge =                ld_e_s_rcharge
    e_rbo =                      ld_e_rbo
    e_tab_bapierr =              ld_e_tab_bapierr
    e_tab_vdbeki =               ld_e_tab_vdbeki
    e_tab_vdbepi =               ld_e_tab_vdbepi
  EXCEPTIONS
    FATAL_ERROR =                1
    .  "  FVD_CHARGE_API_POST

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_rbo  TYPE RBO ,
ld_i_flg_no_confirmation  TYPE FLAG ,
ld_e_tab_bapierr  TYPE BAPIERR_T ,
ld_i_flg_no_enqueue  TYPE FLAG ,
ld_e_tab_vdbeki  TYPE TRTY_VDBEKI ,
ld_i_s_post_info  TYPE RCHARGE_BO_POSTINFO_UI ,
ld_e_tab_vdbepi  TYPE TRTY_VDBEPI ,
ld_i_calln_appln  TYPE TB_CALLNG_APPLN .




ld_i_s_bo_key = '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_s_post_info = '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_POST or its description.


   
 

FVD_CHARGE_API_POST - Post Existing Business Operation
FVD_CHARGE_API_MAINTAIN_DIALOG - External Call of Maintain Dialog for Payoff (Display/Change)
FVD_CHARGE_API_GETLIST - API Get List
FVD_CHARGE_API_GETDETAIL - Get Detail
FVD_CHARGE_API_DELETE - Delete Existing Business Operation (Create and Act.)
FVD_CHARGE_API_CREATE_AND_POST - Create and Post Business Operation