How To Fix FARR_CONTRACT_MAIN642 - Company code &1 under accounting principle &2 is not in Migration status

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 642

• Message text: Company code &1 under accounting principle &2 is not in Migration status

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_CONTRACT_MAIN642 - Company code &1 under accounting principle &2 is not in Migration status ?

  The SAP error message FARR_CONTRACT_MAIN642 indicates that there is an issue with the migration status of a company code under a specific accounting principle. This error typically arises during the migration of contracts or when trying to perform certain operations related to asset accounting in SAP.
  Cause:
  The error occurs when:
  
  The specified company code (&1) is not set to the correct migration status for the accounting principle (&2). This means that the company code has not been properly configured for the migration process, or it has not been activated for the relevant accounting principle.
  The migration process for the company code has not been completed, or there are missing configurations that need to be addressed.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Migration Status:
  
  Go to the relevant transaction in SAP (e.g., transaction code OAYR for Asset Accounting) and check the migration status of the company code.
  Ensure that the company code is set to the correct migration status for the accounting principle you are working with.
  
  
  
  Activate Migration:
  
  If the company code is not in the correct migration status, you may need to activate it. This can typically be done in the configuration settings for Asset Accounting.
  Ensure that all necessary migration steps have been completed for the company code.
  
  
  
  Review Configuration:
  
  Check the configuration settings for the accounting principles and ensure that they are correctly set up for the company code in question.
  Verify that all required settings for asset accounting and migration are in place.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or guides related to the migration process for asset accounting. This can provide insights into the necessary steps and configurations.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the migration status and configurations, consider reaching out to SAP support for further assistance. They can provide specific guidance based on your system setup.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OAYR (for Asset Accounting settings) and S_ALR_87012086 (for asset reports).
  Migration Process: Understand the overall migration process for asset accounting in SAP, including the steps involved and the prerequisites for successful migration.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional context or solutions.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.