Programme SAP RFEBES00 - Do not use this program. Use RFEBKA00.

Description
Program RFEBES00 imports bank statements into the SAP System, and thencreates batch input sessions for posting in G/L and subledgeraccounting.
The bank statement format must represent the 43 standard of the Spanish"Consejo Superior Bancario".
By stating parameters, you can specify whether both sessions aregenerated in one run or whether only the session for G/L accounting isgenerated first. The batch input session names are generated by theprogram, in which case you can choose from two rules:

  • house bank ID and account ID (for example BBV-CC)

  • house bank ID and bank statement number (for example BBV-00607)

  • The batch input session name for subledger accounting always startswith /.

    Interpretation of the note-to-payee fields
    With incoming payments, you can search the note-to-payee items of thebank statement according to document numbers or reference documentnumbers by specifying the selection field (BELNR or XBELNR). Therefore,you obtain the relevant information for clearing customer payments.
    If you do not specify a selection field, the note-to-payee fields arenot interpreted.
    With outgoing payments, the system always searches for the documentnumber.
    Using the length of the selection field and the corresponding numberrange, you can narrow down the search for document numbers or referencedocument numbers and, in this respect, accelerate processing. Values,which do not correspond to the predefined length and are outside thespecified number interval, are recognized by the program as invalidand, consequently, are not used as clearing information.
    An individual user exit can be programmed for a specific interpretationof the note-to-payee fields (feasible for the insurance industry, forexample).

    Precondition
    The program checks whether the business transaction codes (externaltransactions) used by the bank were allocated to an internaltransaction within system configuration. This is necessary because thesystem uses the posting rules stored for an internal transaction topost to the G/L and subledger accounts.
    If the program finds an external transaction not maintained in thecorresponding table, the program aborts after importing the bankstatement, and outputs a list with the missing entries (error log).

    Procedure
    You must maintain these missing entries so that the system can generatethe posting transactions in the appropriate sessions. You then mustrestart the program, making sure you do not select the "importdata" field this time, since the bank statement is already in theSAP system.
    When the program is restarted, it searches the buffer for all lineitems not yet indicated as posted in the respective posting area. Aline item is regarded as posted only if a posting is put into asession.

    Output
    The posting log provides information, separated according to postingarea, on all postings put into the batch input session. It also liststhe external business transaction codes and the internal transactionswhich control posting.
    The processing statistics show you

    • how many postings

    • were created per session
      could not be created due to an error
      • for how many line items postings could not be created (by definition).

1010687CSB43: Dump CX_SY_CONVERSION_CODEPAGE