SAP FVD_REPAY_API_CREATE_AND_POST Function Module for Create and Post Payoff









FVD_REPAY_API_CREATE_AND_POST is a standard fvd repay api create and post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create and Post Payoff 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 repay api create and post FM, simply by entering the name FVD_REPAY_API_CREATE_AND_POST into the relevant SAP transaction such as SE37 or SE38.

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



Function FVD_REPAY_API_CREATE_AND_POST 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_REPAY_API_CREATE_AND_POST'"Create and Post Payoff
  EXPORTING
   I_BUKRS =  "Company Code
*  I_BUDAT =  "Posting Date in the Document
*  I_PERIOD =  "Fiscal Period
*  I_CALLN_APPLN = 'INT' "Calling Application
*  I_EOD_FLAG =  "End of day flag for posting date
   I_RANL =  "Contract Number
*  I_PROTOCOL = '0' "Display Posting Log
*  I_LOGHANDLE =  "Application Log: Log Handle
*  I_SIM =  "Simulation (X = Simulation Run)
*  I_TAB_ADDFLOWS =  "Table Type for RBOBEPP_API (Standard)
*  I_S_RREPAYMENT_API =  "API Fields for Payoff
*  I_X_NO_CONFIRMATION = ' ' "Skip Release Procedure
*  I_NO_ENQUEUE = ' ' "Transfer Enqueue

 IMPORTING
   E_LOGHANDLE =  "Application Log: Log Handle
   E_LOG_DATA =  "Data of Application Log
   E_RBO =  "Business operation number (loans)
   E_TAB_VDBEKI =  "Table Type for Table VDBEKI
   E_TAB_VDBEPI =  "Table Type for Table VDBEPI
   E_TAB_BKPF_FI =  "Table Type for Table BKPF
   E_TAB_BSEG_OP =  "Table Type for BSEG

CHANGING
*  C_STR_VDARL =  "Loan

EXCEPTIONS
   NOT_SAVED = 1    SEPA_ERROR = 2    FAILED = 3    MANDATE_NOT_VALID = 4
.



IMPORTING Parameters details for FVD_REPAY_API_CREATE_AND_POST

I_BUKRS - Company Code

Data type: VDARL-BUKRS
Optional: No
Call by Reference: Yes

I_BUDAT - Posting Date in the Document

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

I_PERIOD - Fiscal Period

Data type: MONAT
Optional: Yes
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)

I_EOD_FLAG - End of day flag for posting date

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

I_RANL - Contract Number

Data type: VDARL-RANL
Optional: No
Call by Reference: Yes

I_PROTOCOL - Display Posting Log

Data type: CHAR1
Default: '0'
Optional: Yes
Call by Reference: Yes

I_LOGHANDLE - Application Log: Log Handle

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

I_SIM - Simulation (X = Simulation Run)

Data type: BSSPARA-SIMKZ
Optional: Yes
Call by Reference: Yes

I_TAB_ADDFLOWS - Table Type for RBOBEPP_API (Standard)

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

I_S_RREPAYMENT_API - API Fields for Payoff

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

I_X_NO_CONFIRMATION - Skip Release Procedure

Data type: TB_X_NO_CONFIRMATION
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_NO_ENQUEUE - Transfer Enqueue

Data type: FLAG
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FVD_REPAY_API_CREATE_AND_POST

E_LOGHANDLE - Application Log: Log Handle

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

E_LOG_DATA - Data of Application Log

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

E_RBO - Business operation number (loans)

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

E_TAB_VDBEKI - Table Type for Table VDBEKI

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

E_TAB_VDBEPI - Table Type for Table VDBEPI

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

E_TAB_BKPF_FI - Table Type for Table BKPF

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

E_TAB_BSEG_OP - Table Type for BSEG

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

CHANGING Parameters details for FVD_REPAY_API_CREATE_AND_POST

C_STR_VDARL - Loan

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

EXCEPTIONS details

NOT_SAVED - Payoff Not Saved

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

SEPA_ERROR - SEPA Information Cannot Be Processed

Data type:
Optional: No
Call by Reference: Yes

FAILED - Authority Check Failed for Structured Finance

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

Copy and paste ABAP code example for FVD_REPAY_API_CREATE_AND_POST 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_i_bukrs  TYPE VDARL-BUKRS, "   
lv_not_saved  TYPE VDARL, "   
lv_c_str_vdarl  TYPE VDARL, "   
lv_e_loghandle  TYPE BALLOGHNDL, "   
lv_i_budat  TYPE BUDAT, "   
lv_i_period  TYPE MONAT, "   
lv_i_calln_appln  TYPE TB_CALLNG_APPLN, "   'INT'
lv_i_eod_flag  TYPE TB_EOD_FLG_CMLCHN, "   
lv_i_ranl  TYPE VDARL-RANL, "   
lv_e_log_data  TYPE FVD_TYP_LOG_DATA, "   
lv_sepa_error  TYPE FVD_TYP_LOG_DATA, "   
lv_e_rbo  TYPE VDBOHEAD-RBO, "   
lv_failed  TYPE VDBOHEAD, "   
lv_i_protocol  TYPE CHAR1, "   '0'
lv_i_loghandle  TYPE BALLOGHNDL, "   
lv_e_tab_vdbeki  TYPE TRTY_VDBEKI, "   
lv_mandate_not_valid  TYPE TRTY_VDBEKI, "   
lv_i_sim  TYPE BSSPARA-SIMKZ, "   
lv_e_tab_vdbepi  TYPE TRTY_VDBEPI, "   
lv_e_tab_bkpf_fi  TYPE TRTY_BKPF, "   
lv_i_tab_addflows  TYPE TRTY_RBOBEPP_API, "   
lv_e_tab_bseg_op  TYPE TRTY_BSEG, "   
lv_i_s_rrepayment_api  TYPE REPAY_API_STRUC, "   
lv_i_x_no_confirmation  TYPE TB_X_NO_CONFIRMATION, "   SPACE
lv_i_no_enqueue  TYPE FLAG. "   SPACE

  CALL FUNCTION 'FVD_REPAY_API_CREATE_AND_POST'  "Create and Post Payoff
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_BUDAT = lv_i_budat
         I_PERIOD = lv_i_period
         I_CALLN_APPLN = lv_i_calln_appln
         I_EOD_FLAG = lv_i_eod_flag
         I_RANL = lv_i_ranl
         I_PROTOCOL = lv_i_protocol
         I_LOGHANDLE = lv_i_loghandle
         I_SIM = lv_i_sim
         I_TAB_ADDFLOWS = lv_i_tab_addflows
         I_S_RREPAYMENT_API = lv_i_s_rrepayment_api
         I_X_NO_CONFIRMATION = lv_i_x_no_confirmation
         I_NO_ENQUEUE = lv_i_no_enqueue
    IMPORTING
         E_LOGHANDLE = lv_e_loghandle
         E_LOG_DATA = lv_e_log_data
         E_RBO = lv_e_rbo
         E_TAB_VDBEKI = lv_e_tab_vdbeki
         E_TAB_VDBEPI = lv_e_tab_vdbepi
         E_TAB_BKPF_FI = lv_e_tab_bkpf_fi
         E_TAB_BSEG_OP = lv_e_tab_bseg_op
    CHANGING
         C_STR_VDARL = lv_c_str_vdarl
    EXCEPTIONS
        NOT_SAVED = 1
        SEPA_ERROR = 2
        FAILED = 3
        MANDATE_NOT_VALID = 4
. " FVD_REPAY_API_CREATE_AND_POST




ABAP code using 7.40 inline data declarations to call FM FVD_REPAY_API_CREATE_AND_POST

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.

"SELECT single BUKRS FROM VDARL INTO @DATA(ld_i_bukrs).
 
 
 
 
 
 
DATA(ld_i_calln_appln) = 'INT'.
 
 
"SELECT single RANL FROM VDARL INTO @DATA(ld_i_ranl).
 
 
 
"SELECT single RBO FROM VDBOHEAD INTO @DATA(ld_e_rbo).
 
 
DATA(ld_i_protocol) = '0'.
 
 
 
 
"SELECT single SIMKZ FROM BSSPARA INTO @DATA(ld_i_sim).
 
 
 
 
 
 
DATA(ld_i_x_no_confirmation) = ' '.
 
DATA(ld_i_no_enqueue) = ' '.
 


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!