How To Fix FKCHK012 - Account details &1 for account &2 does not exist in company code &3

SAP Error Message - Details

• Message type: E = Error

• Message class: FKCHK - Check Repository Messages

• Message number: 012

• Message text: Account details &1 for account &2 does not exist in company code &3

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 FKCHK012 - Account details &1 for account &2 does not exist in company code &3 ?

  The SAP error message FKCHK012 indicates that the system is unable to find the specified account details for a given account in the specified company code. This error typically occurs during financial transactions, such as posting invoices or payments, when the system checks for the existence of the account in the relevant company code.
  Cause:
  
  Account Not Created: The account specified in the transaction has not been created in the specified company code.
  Incorrect Account Number: The account number provided in the transaction may be incorrect or mistyped.
  Company Code Issues: The account may exist, but not in the specified company code. Accounts are often created for specific company codes, and if the wrong company code is referenced, the account will not be found.
  Data Migration Issues: If data was migrated from another system, there may have been issues during the migration process that resulted in missing accounts.
  Authorization Issues: The user may not have the necessary authorizations to view or access the account in the specified company code.
  
  Solution:
  
  Verify Account Creation: Check if the account exists in the specified company code. You can do this by navigating to the account master data in SAP (Transaction Code: FS00) and entering the account number and company code.
  Correct Account Number: Ensure that the account number entered in the transaction is correct. Double-check for any typographical errors.
  Check Company Code: Make sure that the correct company code is being used in the transaction. If the account exists in a different company code, you may need to adjust the transaction accordingly.
  Create Account if Necessary: If the account does not exist, you may need to create it using Transaction Code FS00. Ensure that you have the necessary permissions to create accounts.
  Review Migration Data: If this issue arose after a data migration, review the migration logs and data to ensure that all necessary accounts were migrated correctly.
  Consult with Authorizations Team: If you suspect that authorization issues are causing the problem, consult with your SAP security or authorizations team to ensure that you have the necessary permissions.
  
  Related Information:
  
  Transaction Codes: 
  
  FS00: Create/Change Display G/L Account
  FBL3N: Display G/L Account Line Items
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation for account management and company code settings to ensure compliance with best practices.
  
  By following these steps, you should be able to identify the cause of the FKCHK012 error and implement the appropriate solution.