FVD_BATCH_AUTO_IPD_CMLCHN SAP Function module - Posting as per incoming payment distribution

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

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

Pattern for FM FVD_BATCH_AUTO_IPD_CMLCHN - FVD BATCH AUTO IPD CMLCHN

CALL FUNCTION 'FVD_BATCH_AUTO_IPD_CMLCHN' "Posting as per incoming payment distribution
  EXPORTING
*   i_testlauf =                " xflag         Test Run
*   i_flg_no_commit = SPACE     " xflag         No Commit
    i_batch_pmt =               " any           Payment Request
  CHANGING
    c_febre =                   " trty_febre_bf  Table Type for FEBRE_BF
    c_febcl =                   " trty_febcl_bf  Tabele Type for FEBCL_BF
    c_messages =                " trty_balmt    Table Type for BALMT
  EXCEPTIONS
    POSTING_ERROR = 1           "               Posting Error
    .  "  FVD_BATCH_AUTO_IPD_CMLCHN

ABAP code example for Function Module FVD_BATCH_AUTO_IPD_CMLCHN

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

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

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

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

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

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

CALL FUNCTION 'FVD_BATCH_AUTO_IPD_CMLCHN'
  EXPORTING
*   i_testlauf =                 ld_i_testlauf
*   i_flg_no_commit =            ld_i_flg_no_commit
    i_batch_pmt =                ld_i_batch_pmt
  CHANGING
    c_febre =                    ld_c_febre
    c_febcl =                    ld_c_febcl
    c_messages =                 ld_c_messages
  EXCEPTIONS
    POSTING_ERROR =              1
    .  "  FVD_BATCH_AUTO_IPD_CMLCHN

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_c_febre
 
 TYPE TRTY_FEBRE_BF ,
ld_i_testlauf
 
 TYPE XFLAG ,
ld_c_febcl
 
 TYPE TRTY_FEBCL_BF ,
ld_i_flg_no_commit
 
 TYPE XFLAG ,
ld_c_messages
 
 TYPE TRTY_BALMT ,
ld_i_batch_pmt
 
 TYPE ANY .


ld_c_febre = 'Check type of data required'.
ld_i_testlauf = 'Check type of data required'.
ld_c_febcl = 'Check type of data required'.
ld_i_flg_no_commit = 'Check type of data required'.
ld_c_messages = 'Check type of data required'.
ld_i_batch_pmt = 'Check type of data required'.