How To Fix /PRA/MIGRATION009 - Account number &1 for ERP company code &2 is not active in new COA table

SAP Error Message - Details

• Message type: E = Error

• Message class: /PRA/MIGRATION -

• Message number: 009

• Message text: Account number &1 for ERP company code &2 is not active in new COA table

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 /PRA/MIGRATION009 - Account number &1 for ERP company code &2 is not active in new COA table ?

  The SAP error message /PRA/MIGRATION009 Account number &1 for ERP company code &2 is not active in new COA table typically occurs during the migration process when transitioning from one Chart of Accounts (COA) to another in SAP. This error indicates that the specified account number is not active in the new Chart of Accounts table, which is necessary for the migration to proceed successfully.
  Cause:
  
  Inactive Account: The account number specified in the error message is not marked as active in the new Chart of Accounts.
  Mapping Issues: There may be issues with the mapping of accounts from the old Chart of Accounts to the new one, leading to the account not being recognized.
  Data Migration Issues: During the data migration process, the account may not have been included or properly migrated to the new COA.
  Configuration Errors: There may be configuration errors in the new Chart of Accounts setup that prevent the account from being recognized.
  
  Solution:
  
  Check Account Status: Verify if the account number is indeed active in the new Chart of Accounts. You can do this by navigating to the relevant transaction (e.g., FS00) and checking the account status.
  Review Migration Mapping: Ensure that the mapping of accounts from the old COA to the new COA is correct. This may involve checking the migration settings and ensuring that all necessary accounts are included.
  Activate the Account: If the account is not active, you may need to activate it in the new Chart of Accounts. This can typically be done in the account master data settings.
  Data Consistency Check: Run data consistency checks to ensure that all accounts have been properly migrated and that there are no discrepancies.
  Consult Documentation: Review any migration documentation or guidelines provided by SAP for the specific migration process you are undertaking.
  Seek Help from SAP Support: If the issue persists, consider reaching out to SAP support for assistance, especially if this is part of a larger migration project.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FS00 (G/L Account Master Record), OBY6 (Define Chart of Accounts), and OX15 (Assign Company Code to Chart of Accounts).
  Migration Tools: If you are using SAP S/4HANA or other migration tools, ensure that you are following the correct procedures and using the appropriate tools for the migration.
  Testing: Always perform thorough testing in a development or sandbox environment before executing migrations in production to identify and resolve issues like this in advance.
  
  By following these steps, you should be able to resolve the error and successfully complete the migration process.