How To Fix FV673 - Planning payment advice notes or FEBCL exist - advice note not split

SAP Error Message - Details

• Message type: E = Error

• Message class: FV - Electronic Banking Messages

• Message number: 673

• Message text: Planning payment advice notes or FEBCL exist - advice note not split

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FV673 - Planning payment advice notes or FEBCL exist - advice note not split ?

  The SAP error message FV673 indicates that there are existing payment advice notes or FEBCL (Financial Electronic Bank Communication Language) documents that prevent the splitting of advice notes during the payment processing. This typically occurs when you are trying to process a payment run and the system detects that there are already associated advice notes that have not been split, which can lead to inconsistencies in the payment processing.
  Cause:
  
  Existing Payment Advice Notes: The system has detected that there are payment advice notes already created for the payment run, which are not split as required.
  Configuration Issues: There may be configuration settings in the payment processing that do not allow for the splitting of advice notes.
  Data Integrity Issues: There may be issues with the data integrity in the payment documents or related entries that prevent the system from processing the payment as intended.
  
  Solution:
  
  Check Existing Advice Notes: Review the existing payment advice notes or FEBCL documents to determine if they are correctly configured and if they need to be split.
  Split Advice Notes Manually: If applicable, manually split the advice notes in the system to allow for the processing of the payment run.
  Adjust Configuration: If the issue is related to configuration, consult with your SAP administrator or functional consultant to review the payment processing settings and ensure they are set up to allow for the splitting of advice notes.
  Clear Payment Documents: If there are any erroneous or unnecessary payment documents, consider clearing them to resolve the conflict.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F110 (Automatic Payment Transactions) and FEBAN (Bank Statement) to manage payment runs and bank statements.
  Documentation: Review SAP documentation related to payment processing and advice notes for best practices and troubleshooting steps.
  User Roles: Ensure that the user roles and authorizations are correctly set up to allow for the necessary actions to be taken in the system.
  
  If the issue persists after following these steps, it may be beneficial to engage with SAP support or a qualified SAP consultant for further assistance.