How To Fix FAC_ACC_DET_MESSAGE122 - Enter a credit posting key for the G/L accounts type.

SAP Error Message - Details

• Message type: E = Error

• Message class: FAC_ACC_DET_MESSAGE - Message for account determination

• Message number: 122

• Message text: Enter a credit posting key for the G/L accounts type.

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_MESSAGE122 - Enter a credit posting key for the G/L accounts type. ?

  The SAP error message FAC_ACC_DET_MESSAGE122 typically occurs when you are trying to post a transaction in the Financial Accounting (FI) module, specifically related to asset accounting, and the system requires a credit posting key for the General Ledger (G/L) accounts involved in the transaction.
  Cause:
  The error is triggered when:
  
  You are attempting to post a transaction that requires a credit entry, but you have not specified a valid credit posting key for the G/L accounts.
  The configuration of the G/L accounts does not allow for the type of transaction you are trying to perform.
  The posting keys defined in the system do not match the requirements for the transaction type.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Posting Keys:
  
  Ensure that you are using the correct posting keys for the transaction. Posting keys determine whether the entry is a debit or credit and which type of account can be posted to.
  Common credit posting keys include 40 (for G/L accounts) and 50 (for asset accounts).
  
  
  
  Review G/L Account Configuration:
  
  Go to the G/L account configuration in the SAP system (Transaction Code: FS00) and check the settings for the accounts involved in the transaction.
  Ensure that the accounts are set up to allow credit postings.
  
  
  
  Transaction Type:
  
  Verify that the transaction type you are trying to post is appropriate for the accounts and posting keys you are using.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation or help files related to asset accounting and posting keys to ensure you are following the correct procedures.
  
  
  
  User Authorization:
  
  Ensure that you have the necessary authorizations to post transactions to the specified G/L accounts.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  
  Related Information:
  
  Posting Keys: These are two-digit keys that control the type of posting (debit or credit) and the type of account (G/L, customer, vendor, etc.) that can be posted to.
  G/L Account Types: Different types of G/L accounts (like asset accounts, expense accounts, revenue accounts) have specific configurations that dictate how they can be used in postings.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FS00: Create/Change G/L Account
  FB50: Enter G/L Account Document
  F-02: General Posting
  
  
  
  By following these steps and understanding the underlying concepts, you should be able to resolve the error and successfully post your transaction.