[1] Question: When does the electronic account statement generate payment advice notes?
[2] Question: Why is a clearing via document and reference document numbers not executed?
[3] Question: Why sometimes a '*' is entered in Transaction FEBA instead of the posted document number?
[4] Question: Why sometimes a '*' is entered in the generated payment advice note instead of a customer number?
[5] Question: Which functions are not supported by the electronic account statement in the standard system and which possibilities are there to develop customer-specific enhancements?
[1] Question: When does the electronic account statement generate payment advice notes?
Response: Payment advice notes are always generated only in posting area 2 if the clearing fails. Note 162568 describes the postprocessing of the account statement by means of the generated payment of advice note. The generation of the payment of advice notes can also be hidden: Consider Notes 162571 and 452579.
[2] Question: Why is a clearing via document- or reference document numbers not executed?
Response: This is often caused by the following:
1. During the import, you have not defined any or an incorrect number range for the document or the reference document numbers.
2. The document or reference document numbers are not delivered in the account statement or they are delivered incorrectly. In this case, you should to check the file and should request an error-free one from your bank if necessary.
3. The found clearing information which are saved in table FEBCL is incorrectly overwritten by a user exit.
[3] Question: Why sometimes a '*' entered in Transaction FEBA instead of the posted document number?
Response: The '*' is always entered if you do not directly post but if you create batch input sessions. Transaction FEBA is not only provided for the postprocessing of account statements which have been posted directly. The postprocessing of the batch input sessions occurs in Transaction SM35.
[4] Question: Why sometimes a '*' is entered in the generated payment advice note instead of a customer number?
Response: The system attempts to find the customer via the bank detail delivered in the account statement. If this is not correctly stored in the customer master the system cannot find the customer: it then enters the '*' in the account field of the payment of advice note. If you clear via the document number, you have, however, the option to configure the interpretation algorithm 031: if this finds a document number in the note to payee, the system reads the customer number from the document.
[5] Question: Which functions are not supported by the electronic account statement in the standard system and possibilities are there to develop customer-specific enhancements?
Response: Note 124655 contains a combination of functions which are not supported by the standard system but which can be realized by the customer via user exits. Note 494777 contains an overview of the enhancement possibilities in the electronic accounts statement for this purpose.
Header Data
Release Status: Released for Customer
Released on: 27.08.2002 12:56:13
Priority: Recommendations/additional info
Category: FAQ
Primary Component: FI-BL-PT-BA bank statement
Release-Independent
Related Notes
494777 - Customer enhancements in electronic bank statement
452579 - Suppressing payment advice note generation in bank statement
162571 - Avoiding advice notes within the electronic bank statement
162568 - Advice notes + subs. processing elect. bank statement
124655 - Non-supported electronic bank statement functions
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
All product names are trademarks of their respective companies. SAPNET.RU websites are in no way affiliated with SAP AG. SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver and any other are registered trademarks of SAP AG. Every effort is made to ensure content integrity. Use information on this site at your own risk.