Ansicht
Dokumentation

FEB00001EXIT_RFEBBU10_001 - Electronic account statement

BAL Application Log Documentation   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Enhancement for the Electronic Account Statement

Description

With this function exit, you can analyze each line item on your electronic account statement and gain additional information.

In particular, you can do the following:

• 1. examine all transactions according to clearing information (for example,document numbers, customer numbers, and so on)

• 2. change the internal transaction (for example, based on information from the note to payee)

• 3. influence account determination by account grouping

• 4. distribute the postings to different batch input sessions.

Link to the Standard Program

First, the electronic account statement is fully imported into the database buffer. The so-called interpretation of data is carried out after the import. In this step, each line item on the account statement is examined for clearing information by scanning the lines of the note to payee according to document numbers or reference document numbers. The function exit described here is called up after each interpretation of an individual transaction by SAP modules. Here, every customer can individually influence further processing. The changed data is updated in the database buffer after each function exit is called up.

The postings are first generated if all the line items of the account statements to be processed have been interpreted.

Structure of the Transferred Data

The function exit imports the following structures:

• I_FEBKO = header record of the electronic account statement

• I_FEBEP = line item of the electronic account statement

• T_FEBRE = table of notes to payees

• T_FEBCL = table with clearing information

The function exit exports the following structures:

• E_XFEBKO = header record of the electronic account statement

• E_XFEBEP = line item of the electronic account statement

• E_UPDATE = indicator of whether data was changed in the exit

• E_MSGTYP = message type (E,S,W,I)

• E_MSGTEXT = message that is to be output

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

Note

Via the structures FEBKO and FEBEP and the tables FEBRE and FEBCL, you receive all data that is contained in the SAP System for an individual transaction (line item) of an account statement. This is data from the bank (for example, amounts) and data that was added during the processing (for example, company code).

ad 1.: Finding and Transferring Clearing Information

Procedure: If the standard SAP algorithms for finding clearing information do not meet your requirements, you can add to or reject the information already found (FEBCL). To do this, you have to evaluate information from table FEBRE. This table contains the notes to payees that were supplied by the bank for this line item.

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

If you have found the document number, you can fill table FEBCL as follows:

FEBCL-KUKEY = I_FEBEP-KUKEY
FEBCL-ESNUM = I_FEBEP-ESNUM
FEBCL-CSNUM = 1.
FEBCL-KOART = 'D' for customer
FEBCL-AGKON = SPACE no account required if clearing with BELNR
FEBCL-SELFD = 'BELNR' the selection field is the document number
FEBCL-SELVON = found document number
FEBCL-SELBIS = SPACE only to be filled for intervals

In this case, it is not absolutely necessary to enter the customer number. If you do it anyway, you can possibly make the postprocessing of incorrect transactions in the batch input session much easier. You can then choose the correct transactions from the open items of the customer.

You can transfer any amount of clearing information with table FEBCL. This is, for example, necessary if a customer settles several invoices with one payment. Do not forget in this case to increase the field FEBCL-CSNUM.

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

FEBCL-KUKEY = I_FEBEP-KUKEY
FEBCL-ESNUM = I_FEBEP-ESNUM
FEBCL-CSNUM = 1.
FEBCL-KOART = 'D'
FEBCL-AGKON = 'TESTDEBITOR'
FEBCL-SELFD = 'BLDAT'
FEBCL-SELVON = '19940520' for document date 05/20/1994

ad 2.: Changing the Internal Process

The internal transaction (field FEBEP-VGINT) determines the posting rule and the account determination. It was determined by allocating external transactions to internal transactions (table T028G). It may happen that not all line items, which have received the same external transaction from the bank, should be updated with the same posting rule. You can then allocate another internal transaction to certain line items and therefore change the posting rule.

Example:
You have given a collection authorization to the media company and the utility company for telephone bills and energy supply. You then receive the same external transaction for both direct debits on the account statement. This means that you have to use the same posting rule for both transactions without a function exit, since exactly one internal transaction is allocated to this external transaction. With the function exit, you can then determine the telephone bills from the direct debits due to the note to payee, and allocate another internal transaction to them. As a result, you can, for example, post the telephone bills with a document type different to that for the electricity bills.

ad 3.: Influencing Account Determination by Account Grouping

The accounts to be posted to are determined via the internal transaction and by replacing the account symbols. The account determination can also be influenced by the account grouping (field FEBEP-KFMOD).

Example:
An insurance company has defined the account symbol GELDEINGANG for the cash receipts of insured persons. To improve the transparency, the accounting department wants to post the cash receipt postings to another cash receipt account depending on the insurance type. The insurance type is encrypted in the first three digits of the insurance policy number. The insured persons pay the insurance contributions using the preprinted forms for money transfer of the insurance company which contain the insurance policy number. You can then set the account grouping equal to the first three digits of the insurance policy number in the function exit.

The General Ledger for the bank account is 113100. The following entries are made in the account determination:

Account symbol	Account grouping	Currency	G/L account
GELDEINGANG	+	+	++++++++01
GELDEINGANG	200	+	++++++++20
GELDEINGANG	300	+	++++++++30

If a cash receipt occurs for the insurance policy number 200.1234.2345.11, the field FEBEP-KFMOD is set to 200 in the function exit. Then, posting takes place to account 113120. If no insurance policy number is found during the cash receipt, the field FEBEP-KFMOD equals SPACE and posting takes place to account 113101.

Note:
When defining the account determination, you can check with the function Simulation whether your entries lead to the required result.

ad 4.: Distributing the Postings to Different Batch Input Sessions

You can distribute the postings of subledger accounting to different batch input sessions by filling the field FEBEP-GRPNR with any two-digit identification code. The identification code is then part of the batch input session name.

CL_GUI_FRONTEND_SERVICES - Frontend Services   General Material Data  
This documentation is copyright by SAP AG.

Length: 9025 Date: 20240416 Time: 230830     sap01-206 ( 163 ms )