SAP EPIC Interpretation Algorithms For Bank Statement Algorithms posting rule auto-calculation 电子银行对账单自动记账 FF_5, FEBAN

电子银行对账单自动记账

 

控制解析算法和字段操作;

Interpretation Algorithms

Use

You can find a complete list of interpretation algorithms made available by SAP in Customizing of the Electronic Bank Statement under Make Global Settings for Electronic Bank Statement and in SAP Note 114713 Information published on SAP site.

The following are some of the interpretation algorithms available:

  • 000 (No interpretation)

    You use this algorithm if you do not want to use the standard algorithms supplied by SAP. Instead, you use the algorithms you have defined yourself, in conjunction with functional enhancements (user exits).

  • 001 (Standard algorithm)

    This algorithm interprets the values in the note to payee fields of the electronic bank statement as either document numbers or reference document numbers. It checks whether the values fall within the document or reference document number ranges you entered when importing the bank statement. Only if this is the case does it try to find the items to be cleared in the system.

    Caution

    Note that you must enter the possible intervals for documents/reference documents using the values BELNR Number Range and XBLNR Number Range on the selection screen for the Import of the electronic bank statement.

    For reference document numbers: If these are stored in the system with leading zeros, the system can only find a line item if the reference document number in the bank statement is returned with these leading zeros. If, on the bank statement import selection screen, you were to enter 00100 - 00200 as the interval, the system does not find the value if the reference document number is simply 100.

  • 011 (Outgoing check: Check number not identical to document number)

    This algorithm is used for payments by check if the bank uses pre-numbered checks. Your house bank supplies the check number in the bank statement. The algorithm uses the check number to find the appropriate document number in the system.

  • 012 (Outgoing check: Check number identical to document number)

    You use this algorithm for payments by check if checks are printed using forms that do not yet contain a check number. The document number is then printed on the check as the check number. Your house bank supplies this number in the bank statement. The algorithm finds the check number (which in this case is the same as the document number) in the note to payee lines.

    On the selection screen for importing electronic bank statements, you must here too specify the possible number ranges for the document number search (see algorithm 001).

  • 013 (Outgoing check: Check number identical/not identical to document number)

    This algorithm attempts to find the check number in the note to payee lines according to either algorithm 11 or 12.

  • 015 (Clearing transaction: Selection via assignment number)

    This algorithm enables you to clear open items using the assignment number:

    If the posting rule in question permits clearing, the system selects the items for clearing using the assignment number.

    If the posting rule in question does not permit clearing, the system writes the bank reference (check number, for example) as the assignment number in the line item of the posting on account.

    This means you can later clear the item automatically via the assignment number, for example using report SAPF123W.

    Caution

    The use of these algorithms is subject to the following constraints:

    The system can only clear an item by means of the assignment number if it can locate the account to be cleared (from the bank data in the case of customers/vendors or the posting rule in the case of G/L accounts).

    To select items using the assignment number, the system uses the Bank Reference or Check Number field from the bank statement. (If there is no entry in this field, it uses the start of the Note to Payee field.) Check whether these fields contain the correct information that the system requires to able to find open items in the relevant account.

    Since the assignment number is a text field, the information in the bank statement may not be correctly formatted. If you want selection to take place using the assignment number even though the information in the bank statement is missing or not in the correct format, you can use the customer exit to enter data in the Check Number field (FEBEP CHECT).

  • 019 (DME administration reference document number)

    You use this algorithm to import those bank statement line items that relate to a previous payment run. All the items for a payment medium generated by the payment program are grouped by means of a DME (data medium exchange) reference number. Your house bank confirms the overall total for the line items, together with the DME reference number. The algorithm finds in the note to payee lines in the bank statement the DME reference number that is used to find and clear all line items in the system.

  • 020 (Document number search)

    This algorithm functions in the same way as algorithm 001, except that it interprets the contents of the note to payee fields only as a document number.

  • 021 (Reference document number search)

    This algorithm functions in the same way as algorithm 001, except that it interprets the contents of the note to payee fields only as a reference document number.

  • 022 (BZÜ bank transfer method (Germany only) with document number)

    Algorithm 022 refers to the German BZÜ procedure (payment form transfer without documents). In this case, a billing system creates a transfer form that contains a thirteen digit number in the code line. This number normally consists of the document number and a check digit. It is returned by your house bank. This algorithm cuts off the check digit and interprets the number (right-aligned) as a document number.

  • 023 (BZÜ bank transfer method (Germany only) with reference document number)

    This algorithm also relates to the German BZÜ procedure (payment form transfer without documents). In this case, a billing system creates a transfer form that contains a thirteen digit number in the code line. This number normally consists of the reference document number and a check digit. It is returned by your house bank. This algorithm interprets the number (including the check digit) in the note to payee fields of the electronic bank statement as a reference document number.

  • 026 (Search for reference document number with leading zeros, if < 10)

    You can use this algorithm if the ten digit reference number in the bank statement does not contain leading zeros (if, for example, the reference document number in the statement is 100 and not 0000000100). It works in three stages:

    • As with algorithm 021, algorithm 026 reads the Note to Payee field searching for possible reference document numbers. (Number range XBELNR on the selection screen for importing the bank statement).

    • In contrast to algorithm 21, algorithm 026 enters ten digits by adding leading zeros.

    • Finally, it compares the reference document numbers from the bank statement with the reference document numbers in the system.

  • 027 (Reference number TITO)

    This algorithm searches for the Payment Reference supplied by the Finnish TITO bank statement format.

  • 028 (Reference number per MULTICASH conversion programs)

    This algorithm is the same as algorithm 027 if the bank statement files are imported in MULTICASH format. It uses number range BELNR.

  • 029 (Payment order number)

    This algorithm searches using the payment order number. It uses number range XBELNR.

  • 030 (Brazil)

    Applies where the electronic bank statement is being used in Brazil. It searches for the document number, the fiscal year, and the number of the line item within the accounting document.

  • 031 (Document number search (customer number in line item))

    This algorithm functions in the same way as algorithm 020 (document number search). Here are some exceptions:

    • If the system can identify the corresponding business partner from a document number entered in the Note to Payee field, then you have the system add the bank details to the master data automatically. This option is also valid for algorithm 021. Since the bank statement normally contains the bank details, these details can be used to supplement the master data. You can use report RFEBKA80 to generate a file containing customers’ bank details, and add this data to the master records using report RFBIDE00. For more information, see the documentation for these reports.

      Caution

      Where an alternative payer is specified, the bank details contained in the bank statement are not those of the business partner to which the document number previously found in the note to payee refers. The bank details in question are not added to the correct business partner.

    • This algorithm is of importance when automatically creating payment advice notes when importing bank statements. The system creates a payment advice note if, when importing the bank statement data, it could not clear every open item right away, for example because it could not find every document number contained in the note to payee. The payment advice note contains the document numbers the system found, and can be used to post the bank statement items if you enter the missing document numbers yourself. It is possible that the individual document numbers or payment advice note items relate to different business partners (for example, payment by common payers). If this is the case, these items are only automatically assigned to the correct business partner if you use algorithm 031. If you use algorithm 21, you need to add the correct business partner information to each individual payment advice note item.

  • 041 (Treasury: Search for loan, then standard search)

    As for algorithm 040 above, except that the search is carried out in the reverse order.

  • 120 (Document number search with no check)

    This algorithm searches by document number in the note to payee and does not check whether the document number exists in the system. It only checks whether the number is in the number range that you specified when you imported the bank statement.

    If you define this interpretation algorithm in Customizing for the electronic bank statement, the electronic bank statement can also clear open items that exist in a bank company code different from the current one.

  • 121 (Reference document number search with no check)

    This algorithm functions in the same way as algorithm 120, except that it interprets the contents of the note to payee fields only as a reference document number.

Activities

You define the interpretation algorithm in the Customizing activities for the electronic bank statement. In Customizing for Bank Accounting, choose  Business Transactions  Payment Transactions  Electronic Bank Statement  Make Global Settings for Electronic Bank Statement  Assign External Transaction Types to Posting Rules . For each external transaction, you then define which interpretation algorithm is to apply. For more information on the settings for external transactions, see the SAP Solution Manager documentation.

 

https://help.sap.com/viewer/495b05f6dbb24b1da46e4027d3a28fef/6.18.06/en-US/4dc5efb40c381c36e10000000a42189b.html

 

将中资银行对账单转换成外资电子银行格式:

Conversion Programs

You always need to distinguish two groups of formats when processing the bank statement in the SAP system:

  • Formats that can be further processed by SAP direct, such as SWIFT MT940 and BAI

  • Formats that are first converted using a report to the MulitCash format, in order to then be processed further

The following reports among others convert bank and account statements to the MultiCash format:

  • Report RFEBBE00 converts the Belgian bank statement format CODA to MultiCash format.

  • Report RFEBFI00 converts Finnish bank statements specifying reference payments from customers or bank collections to MultiCash format.

  • Report RFEBDK00 converts Danish bank statements to MultiCash format.

    The following services are supported:

    • UDDATA GiroBank

    • Pengeinstituttenes Betalingssystemer(PBS)

  • Report RFEBNO00 converts Norwegian bank statements to MultiCash format. The OCR giro format from Bankenes Betalings Sentral (BBS) and the OCR format from a giro account are supported.

  • Report RFEBSE00 converts Swedish bank statements to MultiCash format. The following formats are supported:

    • Bank giro OCR

    • Bank giro LM (Automatisk avprickning)

    • Bank giro Autogiro

    • Postal giro OCR

    • Postal giro TIPS (Total Integrated Payment System)

    • Postal giro Autogiro

Note

You can find a list of formats supported by SAP and also the corresponding conversion programs in SAP Note 106121 Information published on SAP site.

The reports import a statement file that is stored on a PC or in a file system. They create two MultiCash files:

  1. Statement File

    This file contains data about the statements (statement number, old balance, new balance, currency, bank account number).

  2. Transaction Amount File

    This file contains the individual transactions from the statements.

Note
 
 

How to create custom Interpretation Algorithm

You can create custom interpretation algorithm to change system to look for the document to be cleared according the the reference field or the document number.

How does Interpretation algorithm work?

Tries to find in the note to payee information if there is any number in the document number range that you select in the selection screen. Once the system finds all the possible Document Numbers, it tries to find the corresponding FI document by looking for it in table BKPF.

With this document number, it updates table FEBCL with the corresponding clearing information. If it is not possible to find such FI document number, then it updates the table FEBCL to clear the document by amount. Then the system tries to post the document using the clearing information from FEBCL (document number or amount, depending on the above). Only in case, this posting fails, it posts the document on account. But first of all, it tries with the document number or with the amount.

 

For example in SAP Standard bank reconciliation always refer to KIDNO ( Payment reference ) , to find FI Document No, but in this case we want to find such FI Document No refer to ZUONR ( Assignment No ).

The solution . We can create custom Interpretation algorithm 901 to switch that rule.

 

Step by Step to Create Custom Interpretation Algorithm and Assign it

1.Go to transaction SE37 and create function module with the name should start Z_FIEB_interpretationnumber_ALGORITHM . for this case the name is Z_FIEB_901_ALGORITHM.

But the easier way you can copy from Interpretation algorithm 21 ( FIEB_021_ALGORITHM ).

2.Write the ABAP code in your custom interpretation algorithm.

 

 

Note :

You need to select FI Doc No from BSIS ( Open Item ) table based on ZUONR which you have input during FF67 Transaction.

 

 

Next, you need to passing some information to internal table T_AVIP_OUT with SFELD ( Name of selection field ) = ZUONR and SWERT ( Selection Value ) with value of ZUONR ( Assignment No ) and T_AVIP_OUT-KONTO fill with GL Account from FI Doc (BSIS ) before.

 

 

3.Go to SPRO

interpretation-algorithm-custom-abap

4.Assign interpretation algorithm 901 for your transaction type and posting rule the Z_FIEB_901_ALGORITHM will get called automatically.

interpretation-algorithm-custom-abap-2

5.For Electronic Bank Statement, the way almost same as before. but for SPRO you need to open .

interpretation-algorithm-custom-abap-3

6.You can assign the custom interpretation algorithm 901 ( Z_FIEB_901_ALGORITHM ) in this screen.

interpretation-algorithm-custom-abap-4

That how to create custom interpretation algorithm and the way to assign custom interpretation to posting rule and transaction type.

 

 

Incoming search terms:

posted @ 2020-07-25 22:19  Slashout  阅读(3703)  评论(0)  编辑  收藏  举报