How To Fix FE723 - Saving not possible since accounts overlap

SAP Error Message - Details

• Message type: E = Error

• Message class: FE - CO-PA module pool messages

• Message number: 723

• Message text: Saving not possible since accounts overlap

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 FE723 - Saving not possible since accounts overlap ?

  The SAP error message FE723, "Saving not possible since accounts overlap," typically occurs in the context of financial transactions, particularly when dealing with account assignments in SAP. This error indicates that there is a conflict in the account assignments, often due to overlapping or conflicting account ranges or configurations.
  Cause:
  
  
  Overlapping Account Ranges: This error can occur if there are overlapping account ranges defined in the system. For example, if two different account assignments are trying to use the same account or range of accounts, SAP will prevent the transaction from being saved.
  
  
  Incorrect Configuration: The configuration of account assignments in the financial settings may not be set up correctly, leading to conflicts.
  
  
  Multiple Account Assignments: If a transaction is trying to assign multiple accounts that overlap in their definitions, it can trigger this error.
  
  
  Master Data Issues: There may be issues with the master data of the accounts involved, such as incorrect account types or statuses.
  
  
  Solution:
  
  
  Check Account Assignments: Review the account assignments in the transaction you are trying to save. Ensure that there are no overlapping accounts being used.
  
  
  Review Configuration: Go to the configuration settings in SAP (transaction code SPRO) and check the account assignment configurations. Look for any overlapping ranges or conflicting settings.
  
  
  Adjust Account Ranges: If you find overlapping account ranges, adjust them to ensure that each account or range is unique and does not conflict with others.
  
  
  Consult with Finance Team: If you are unsure about the correct account assignments or configurations, consult with your finance or accounting team to ensure that the correct accounts are being used.
  
  
  Check Master Data: Verify the master data for the accounts involved in the transaction. Ensure that they are correctly set up and do not have any issues that could lead to conflicts.
  
  
  Testing: After making adjustments, try to save the transaction again to see if the error persists.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO (for configuration), FS00 (for account master data), and FB50 (for general ledger postings) to help troubleshoot the issue.
  
  
  SAP Notes: Check SAP Notes and Knowledge Base Articles for any specific guidance or patches related to this error message.
  
  
  Documentation: Review SAP documentation related to financial accounting and account assignments for best practices and guidelines.
  
  
  If the issue persists after following these steps, it may be necessary to involve your SAP support team or consult with SAP directly for further assistance.