FVD_REPAY_UI_CONFIRMATION SAP Function module - Call Payoff from Release

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

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

Pattern for FM FVD_REPAY_UI_CONFIRMATION - FVD REPAY UI CONFIRMATION

CALL FUNCTION 'FVD_REPAY_UI_CONFIRMATION' "Call Payoff from Release
  EXPORTING
    i_vdarl_key =               " vdarl_key     VDARL Schlussel-Struktur
    i_rbo =                     " vdbohead-rbo  Business operation number (loans)
    i_vzfgd =                   " vzfgd         Release data (Informative data for the release procedure)
    i_bo_cat =                  " sbo_cat       Business Operation Category
  EXCEPTIONS
    USER_CANCEL = 1             "               Benutzerabbruch / Simulation
    UPDATE_ERROR = 2            "               Error on update
    FATAL_ERROR = 3             "
    .  "  FVD_REPAY_UI_CONFIRMATION

ABAP code example for Function Module FVD_REPAY_UI_CONFIRMATION

The ABAP code below is a full code listing to execute function module FVD_REPAY_UI_CONFIRMATION 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_i_vdarl_key) = 'Check type of data required'.
 

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


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

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

CALL FUNCTION 'FVD_REPAY_UI_CONFIRMATION'
  EXPORTING
    i_vdarl_key =                ld_i_vdarl_key
    i_rbo =                      ld_i_rbo
    i_vzfgd =                    ld_i_vzfgd
    i_bo_cat =                   ld_i_bo_cat
  EXCEPTIONS
    USER_CANCEL =                1
    UPDATE_ERROR =               2
    FATAL_ERROR =                3
    .  "  FVD_REPAY_UI_CONFIRMATION

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
ELSEIF SY-SUBRC EQ 3. "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_i_vdarl_key
 
 TYPE VDARL_KEY ,
ld_i_rbo
 
 TYPE VDBOHEAD-RBO ,
ld_i_vzfgd
 
 TYPE VZFGD ,
ld_i_bo_cat
 
 TYPE SBO_CAT .


ld_i_vdarl_key = 'Check type of data required'.

SELECT single RBO 
  FROM VDBOHEAD 
  INTO ld_i_rbo.

ld_i_vzfgd = 'Check type of data required'.
ld_i_bo_cat = 'Check type of data required'.