How To Fix FARR_FOUNDATION559 - Customer &1, comp. code &2: no ongoing business exists

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_FOUNDATION - Revenue Accounting - Foundation

• Message number: 559

• Message text: Customer &1, comp. code &2: no ongoing business exists

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 FARR_FOUNDATION559 - Customer &1, comp. code &2: no ongoing business exists ?

  The SAP error message FARR_FOUNDATION559 indicates that there is no ongoing business for the specified customer and company code. This error typically arises in the context of the SAP Financial Accounting (FI) and Asset Accounting (AA) modules, particularly when dealing with customer accounts and their associated transactions.
  Cause:
  The error can occur due to several reasons:
  
  No Active Business Relationship: The customer may not have any active business transactions or relationships with the specified company code.
  Incorrect Configuration: The configuration settings for the customer master data or company code may not be set up correctly.
  Data Inconsistency: There may be inconsistencies in the data, such as missing or incorrect entries in the customer master or related tables.
  Inactive Customer: The customer account may be marked as inactive or blocked, preventing any ongoing business transactions.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Customer Master Data:
  
  Go to the customer master data (transaction code FD03 for display).
  Verify that the customer is active and has the correct status for the specified company code.
  
  
  
  Review Business Transactions:
  
  Ensure that there are ongoing business transactions for the customer in the specified company code. This can include open invoices, contracts, or other relevant documents.
  
  
  
  Check Configuration:
  
  Review the configuration settings for the customer account and company code in the SAP system. Ensure that the necessary settings are in place for the customer to conduct business.
  
  
  
  Data Consistency Check:
  
  Run data consistency checks to identify any discrepancies in the customer data. This can be done using transaction codes like SE16 to view relevant tables or using specific reports designed for data consistency.
  
  
  
  Consult with SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide insights based on the specific configuration and setup of your SAP environment.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FD03 (Display Customer), FBL5N (Customer Line Item Display), and SE16 (Data Browser) for checking data.
  Documentation: Review SAP documentation related to customer master data and business transactions for further understanding.
  User Roles: Ensure that the user has the necessary authorizations to access and modify customer data.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.