FVD_REPAY_API_ACTIVATE SAP Function module - Activate Payoffs

FVD_REPAY_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_REPAY_API_ACTIVATE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FVD_REPAY_API
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM FVD_REPAY_API_ACTIVATE - FVD REPAY API ACTIVATE

CALL FUNCTION 'FVD_REPAY_API_ACTIVATE' "Activate Payoffs
  EXPORTING
    i_bukrs =                   " vdarl-bukrs   Company Code
    i_ranl =                    " vdarl-ranl    Contract Number
    i_rbo =                     " vdbohead-rbo  Business operation number (loans)
*   i_loghandle =               " balloghndl    Application Log: Log Handle
*   i_x_no_confirmation = SPACE  " tb_x_no_confirmation  Skip Release Procedure
*   i_no_enqueue = SPACE        " flag          Transfer Enqueue
*   i_calln_appln = 'INT'       " tb_callng_appln  Calling Application
  IMPORTING
    e_loghandle =               " balloghndl    Application Log: Log Handle
    e_log_data =                " fvd_typ_log_data  Data of Application Log
    e_rbo =                     " vdbohead-rbo  Business operation number (loans)
  EXCEPTIONS
    NOT_ACTIVATED = 1           "               Payoff Not Activated
    FAILED = 2                  "               Authority Check Failed for Structured Finance
    .  "  FVD_REPAY_API_ACTIVATE

ABAP code example for Function Module FVD_REPAY_API_ACTIVATE

The ABAP code below is a full code listing to execute function module FVD_REPAY_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_loghandle  
 
 TYPE BALLOGHNDL
,
ld_e_log_data  
 
 TYPE FVD_TYP_LOG_DATA
,
ld_e_rbo  
 
 TYPE VDBOHEAD-RBO
.

 

SELECT single BUKRS 
  FROM VDARL 
  INTO @DATA(ld_i_bukrs).

 

SELECT single RANL 
  FROM VDARL 
  INTO @DATA(ld_i_ranl).

 

SELECT single RBO 
  FROM VDBOHEAD 
  INTO @DATA(ld_i_rbo).


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

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

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

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

CALL FUNCTION 'FVD_REPAY_API_ACTIVATE'
  EXPORTING
    i_bukrs =                    ld_i_bukrs
    i_ranl =                     ld_i_ranl
    i_rbo =                      ld_i_rbo
*   i_loghandle =                ld_i_loghandle
*   i_x_no_confirmation =        ld_i_x_no_confirmation
*   i_no_enqueue =               ld_i_no_enqueue
*   i_calln_appln =              ld_i_calln_appln
  IMPORTING
    e_loghandle =                ld_e_loghandle
    e_log_data =                 ld_e_log_data
    e_rbo =                      ld_e_rbo
  EXCEPTIONS
    NOT_ACTIVATED =              1
    FAILED =                     2
    .  "  FVD_REPAY_API_ACTIVATE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "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_loghandle
 
 TYPE BALLOGHNDL ,
ld_i_bukrs
 
 TYPE VDARL-BUKRS ,
ld_e_log_data
 
 TYPE FVD_TYP_LOG_DATA ,
ld_i_ranl
 
 TYPE VDARL-RANL ,
ld_e_rbo
 
 TYPE VDBOHEAD-RBO ,
ld_i_rbo
 
 TYPE VDBOHEAD-RBO ,
ld_i_loghandle
 
 TYPE BALLOGHNDL ,
ld_i_x_no_confirmation
 
 TYPE TB_X_NO_CONFIRMATION ,
ld_i_no_enqueue
 
 TYPE FLAG ,
ld_i_calln_appln
 
 TYPE TB_CALLNG_APPLN .



SELECT single BUKRS 
  FROM VDARL 
  INTO ld_i_bukrs.


SELECT single RANL 
  FROM VDARL 
  INTO ld_i_ranl.


SELECT single RBO 
  FROM VDBOHEAD 
  INTO ld_i_rbo.

ld_i_loghandle = 'Check type of data required'.
ld_i_x_no_confirmation = 'Check type of data required'.
ld_i_no_enqueue = 'Check type of data required'.
ld_i_calln_appln = 'Check type of data required'.