We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

EXIT_RFEBBU10_001 -

EXIT_RFEBBU10_001 -

BAL Application Log Documentation   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Enhancement for Electronic Bank Statement

Description

This function exit enables you to analyze each line item on your electronic bank statement and supplement them with additional information.

You have the following options:

  1. Search each line item for clearing information (for example, document numbers, customer numbers, etc).
  2. Change the internal transaction (for example, because of information from the note to payee).
  3. Change the account determination by using account modification.
  4. Assign the postings to different batch input sessions.

Link to Standard Program

First the electronic bank statement is completely imported into the buffer for banking data. After the import, the system interprets the data. In this step, it searchs for the clearing information in each line item on the bank statement by reading the lines for the note to payee and finding the document numbers or reference document numbers. After each interpretation of a line item by the SAP module, the function exit described here is accessed. Each customer can individually modify further processing. After the function exit is accessed, changed data is updated in the buffer for banking data.

The system only generates the postings if all the line items on the bank statements to be processed have been interpreted.

Structure of Transferred Data

The function exit imports the following structures:

  • I_FEBKO = Header record from electronic bank statement
  • I_FEBEP = Line items from electronic bank statement
  • I_TESTRUN = 'X' this is a test run (flag)

The function exit exports the following structures:

  • E_XFEBKO = Header record from electronic bank statement
  • E_XFEBEP = Line items from electronic bank statement
  • E_UPDATE = Indicators of whether data was changed in the exit
  • E_MSGTYP = Message type (E,S,W,I)
  • E_MSGTEXT = Message to be output

The user exit interfac uses the following tables:

T_FEBCL = Table with clearing information

T_FEBRE = Table of notes to payees

The structures FEBKO, FEBEP, FEBRE and FEBCL are defined in the Data Dictionary.

Note

Using structures I_FEBKO and I_FEBEP as well as tables T_FEBRE and T_FEBCL, you obtain all the data contained in the SAP System for one line item on a bank statement. This data is data, such as amounts, sent by the bank and is also data, such as the company code, enhanced during processing.

Example:

*----------------------------------------------------------------------*

* INCLUDE ZXF01U01

*

*----------------------------------------------------------------------*

*-- process for electronic bank-statement only

IF I_FEBKO-EFART = 'E' AND I_FEBKO-ANWND = '0001'.

*-- copy input to output

E_FEBKO = I_FEBKO.

E_FEBEP = I_FEBEP.

*-- change G/L account 113100 to 113119

IF E_FEBKO-HKONT = '0000113100'.

E_FEBKO-HKONT = '0000113119'.

MOVE 'X' TO E_UPDATE.

ENDIF.

ENDIF.

Note on Option 1: Finding and Transferring Clearing Information

Procedure: If SAP's standard algorithms for finding clearing information are not sufficient for your purposes, you can add to or reject the information (T_FEBCL) already found. To do this, you must evaluate the information from table T_FEBRE, which contains the notes to payee delivered by the bank for this line item.

Example:
Your customers use your preprinted money transfer forms. In this case, you know where to find the clearing information in the note to payee. For automatic clearing you need either the document number (BELNR), or reference document number (XBLNR), or the account number and additional information such as the document date.

If you find the document number, you can fill table T_FEBCL, as follows:

T_FEBCL-KUKEY = I_FEBEP-KUKEY
T_FEBCL-ESNUM = I_FEBEP-ESNUM
T_FEBCL-CSNUM = 1.
T_FEBCL-KOART = "D" for customer
T_FEBCL-AGKON = SPACE if clearing with BELNR, no account necessary
T_FEBCL-SELFD = "BELNR" selection field is the document number
T_FEBCL-SELVON = document number found
T_FEBCL-SELBIS = SPACE only to fill in intervals

In this case, it is not absolutely necessary to enter the customer number. If nevertheless you enter it, you might considerably simplify the postprocessing of incorrect transactions in the batch input session. You can then choose the correct transactions from the customer open items.

You can use table T_FEBCL to copy as much clearing information as you need. This may be necessary, for example, if a customer clears several invoices with one payment. In doing this, do not forget to include the field T_FEBCL-CSNUM.

If you have found a customer number and a document date, you can copy the clearing information, as follows:

T_FEBCL-KUKEY = I_FEBEP-KUKEY
T_FEBCL-ESNUM = I_FEBEP-ESNUM
T_FEBCL-CSNUM = 1.
T_FEBCL-KOART = 'D'
T_FEBCL-AGKON = 'TESTCUST'
T_FEBCL-SELFD = 'DOCDAT'
T_FEBCL-SELVON = '19940520' for document date 05/20/1994

Note on Option 2: Changing the Internal Transaction

The internal transaction (field FEBEP-VGINT) determines the posting rules and the account determination. It is specified by assigning an external transaction to an internal one (table T028G). It is possible that not all the line items given the same external transaction by the bank are posted with the same posting rule. You can then assign a different internal transaction to certain line items and thus change the posting rules.

Example:
You gave the telephone company and the utilities company direct debit authorization for the telephone bill and the electric bill. You then receive the same external transaction for both direct debits on the bank statement. Without the function exit, you would have to use the same posting rules for both transactions, since this external transaction is assigned to only one internal transaction. Using the function exit, you can then separate the telephone bills from the direct debits through the note to payee and assign a different internal transaction to them. This procedure enables you, for example, to post the telephone bills with a document type different from the one for the electric bills.

Note on Option 3: Altering Account Determination with Account Modification

The accounts to be posted to are determined using the internal transaction and by replacing the account symbols. You can also alter the account determination by using account modification (field FEBEP-KFMOD).

Example:
An insurance company has defined the account symbol CASHIN for the policy holder's cash receipt. To improve the clarity of transactions, the accounting department wants to post cash receipt entries to a different cash receipt account, depending on the type of insurance. The policy type is encoded in the first three digits of the policy number. Policy holders pay premiums with the insurance company's preprinted, money transfer forms on which the policy number is printed. In the function exit, the account modification can then be set as the first three digits of the policy number.

The G/L account for the bank account is 113100. The following entries are made in the account determination:

Acct symbol Acct modif. Curr. Subledger acct
CASHIN + + ++++++++01
CASHIN 200 + ++++++++20
CASHIN 300 + ++++++++30

If a cash receipt for policy number 200.1234.2345.11 occurs, field FEBEP-KFMOD is set to 200 in the function exit. 200 means the system posts to account 113120. If a policy number is not found for the cash receipt, field FEBEP-KFMOD is left blank (SPACE) and the system posts to account 113101.

Note:
When defining account determination, you can check whether your entries produce the required results by using the "Simulation" function.

Note on Option 4: Assigning Postings to Different Batch Input Sessions

You can assign subledger postings to different batch input sessions by entering any two-character ID in field FEBEP-GRPNR. The ID is then a component of the session name.






Vendor Master (General Section)   General Material Data  
This documentation is copyright by SAP AG.

Length: 9579 Date: 20200919 Time: 010915     sap01-206 ( 162 ms )