How To Fix FAC_ACC_DET_MESSAGE090 - Account key &1 doesn't exist.

SAP Error Message - Details

• Message type: E = Error

• Message class: FAC_ACC_DET_MESSAGE - Message for account determination

• Message number: 090

• Message text: Account key &1 doesn't exist.

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 FAC_ACC_DET_MESSAGE090 - Account key &1 doesn't exist. ?

  The SAP error message FAC_ACC_DET_MESSAGE090 indicates that the account key specified in your transaction does not exist in the system. This error typically occurs in the context of financial accounting or asset accounting when trying to post a transaction that requires a valid account key.
  Cause:
  
  Incorrect Account Key: The account key specified in the transaction is either misspelled or does not exist in the system.
  Configuration Issues: The account key may not have been configured properly in the system.
  Missing Master Data: The account key may not be assigned to the relevant master data (e.g., asset master records, cost centers, etc.).
  Transport Issues: If the configuration was recently transported from another system, the account key may not have been included in the transport.
  
  Solution:
  
  Check Account Key: Verify that the account key you are using is correct. Check for any typographical errors.
  Configuration Check: 
  
  Go to the configuration settings in SAP (Transaction code: SPRO).
  Navigate to the relevant area (e.g., Asset Accounting) and check if the account key is defined.
  Ensure that the account key is assigned to the appropriate account types and is active.
  
  
  Master Data Assignment: 
  
  Check if the account key is assigned to the relevant master data (e.g., asset master records).
  If necessary, create or update the master data to include the correct account key.
  
  
  Transport Check: If the account key was recently added or modified, ensure that the transport request was successfully imported into the system.
  Consult Documentation: Refer to SAP documentation or help files for more details on the specific account key and its usage.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OAOA (for Asset Accounting) or OKEQ (for Cost Center Accounting) to check configurations related to account keys.
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message.
  User Authorizations: Ensure that you have the necessary authorizations to view and modify account keys and related configurations.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in the relevant area of SAP.