How To Fix FINS_ACDOC_CUST092 - Enter a different currency type than currency type &2 in company code &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing

• Message number: 092

• Message text: Enter a different currency type than currency type &2 in company code &1

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 FINS_ACDOC_CUST092 - Enter a different currency type than currency type &2 in company code &1 ?

  The SAP error message FINS_ACDOC_CUST092 indicates that there is a mismatch in the currency type being used in a financial document compared to what is expected for the specified company code. This error typically arises when you are trying to post a document in a currency that is not allowed or is different from the currency type defined for that company code.
  Cause:
  
  Currency Type Mismatch: The currency type you are trying to use (e.g., document currency, local currency, or group currency) does not match the currency type defined in the configuration for the company code.
  Configuration Issues: The company code may have specific settings that restrict the use of certain currency types for transactions.
  Incorrect Document Settings: The document you are trying to post may have been set up incorrectly, leading to the use of an unsupported currency type.
  
  Solution:
  
  
  Check Currency Type Configuration:
  
  Go to the configuration settings for the company code in SAP (Transaction Code: OBY6).
  Verify the currency types defined for the company code and ensure that the currency you are trying to use is allowed.
  
  
  
  Change the Currency Type:
  
  If you are able to change the currency type in your transaction, select a different currency type that is compatible with the company code settings.
  Ensure that the currency type you are using matches the expected currency type for the transaction.
  
  
  
  Review Document Settings:
  
  Check the document you are trying to post for any incorrect settings related to currency.
  If necessary, adjust the document to use the correct currency type.
  
  
  
  Consult with SAP Support or Configuration Team:
  
  If you are unsure about the configuration or how to resolve the issue, consult with your SAP support team or the team responsible for financial configurations in your organization.
  
  
  
  Related Information:
  
  Currency Types in SAP: SAP uses different currency types such as document currency, local currency, and group currency. Each company code can have specific settings for these currency types.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6 (Company Code Global Settings) and FB50 (General Ledger Document Entry) to troubleshoot and resolve the issue.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message, as there may be updates or fixes provided by SAP.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.