How To Fix FV160 - The EDI payment notice with number & has already been assigned

SAP Error Message - Details

• Message type: E = Error

• Message class: FV - Electronic Banking Messages

• Message number: 160

• Message text: The EDI payment notice with number & has already been assigned

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 FV160 - The EDI payment notice with number & has already been assigned ?

  The SAP error message FV160 indicates that there is an issue with the Electronic Data Interchange (EDI) payment notice, specifically that the payment notice with the specified number has already been assigned in the system. This typically occurs during the processing of incoming payment notices, where the system detects that the payment notice has already been processed or assigned to another transaction.
  Cause:
  
  Duplicate Processing: The payment notice has already been processed in the system, leading to a conflict when trying to process it again.
  Incorrect Configuration: There may be issues with the configuration of the EDI settings, leading to improper handling of payment notices.
  Data Entry Error: Manual entry or data import processes may have inadvertently created duplicate entries.
  System Errors: There could be a bug or issue in the SAP system that is causing it to misinterpret the status of the payment notice.
  
  Solution:
  
  Check Payment Notice Status: Verify the status of the payment notice in the system. Use transaction codes like FBL1N (Vendor Line Item Display) or FBL5N (Customer Line Item Display) to check if the payment notice has already been processed.
  Review EDI Configuration: Ensure that the EDI settings are correctly configured. Check the mapping and processing rules for incoming payment notices.
  Avoid Duplicate Processing: If the payment notice has been processed, ensure that you are not attempting to process it again. If it needs to be reprocessed, you may need to reverse the original transaction first.
  Consult Logs: Check the application logs (transaction SLG1) for any additional error messages or warnings that could provide more context on the issue.
  Contact Support: If the issue persists and you cannot identify the cause, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error message.
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes that may address this specific error or provide guidance on EDI payment processing.
  Transaction Codes: Familiarize yourself with transaction codes related to EDI and payment processing, such as WE02 (EDI Monitoring) and F110 (Automatic Payment Transactions).
  Documentation: Review SAP documentation on EDI processing and payment notices to ensure compliance with best practices.
  
  By following these steps, you should be able to identify the cause of the FV160 error and take appropriate action to resolve it.