SAP FVD_REPAY_API_ACTIVATE Function Module for Activate Payoffs

Search SAP Function Modules

FVD_REPAY_API_ACTIVATE is a standard fvd repay 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 Payoffs 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 activate FM, simply by entering the name FVD_REPAY_API_ACTIVATE 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_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_REPAY_API_ACTIVATE'"Activate Payoffs
  EXPORTING
   I_BUKRS =  "Company Code
   I_RANL =  "Contract Number
   I_RBO =  "Business operation number (loans)
*  I_LOGHANDLE =  "Application Log: Log Handle
*  I_X_NO_CONFIRMATION = ' ' "Skip Release Procedure
*  I_NO_ENQUEUE = ' ' "Transfer Enqueue
*  I_CALLN_APPLN = 'INT' "Calling Application

 IMPORTING
   E_LOGHANDLE =  "Application Log: Log Handle
   E_LOG_DATA =  "Data of Application Log
   E_RBO =  "Business operation number (loans)

EXCEPTIONS
   NOT_ACTIVATED = 1    FAILED = 2 

.

IMPORTING Parameters details for FVD_REPAY_API_ACTIVATE

I_BUKRS - Company Code

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

I_RANL - Contract Number

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

I_RBO - Business operation number (loans)

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

I_LOGHANDLE - Application Log: Log Handle

Data type: BALLOGHNDL
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

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_REPAY_API_ACTIVATE

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

EXCEPTIONS details

NOT_ACTIVATED - Payoff Not Activated

Data type:
Optional: No
Call by Reference: Yes

FAILED - Authority Check Failed for Structured Finance

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FVD_REPAY_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_REPAY_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