How To Fix FINS_ACDOC_CUST046 - Add. crcy type doesn't match the one in FI (ledger &1/company code &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing

• Message number: 046

• Message text: Add. crcy type doesn't match the one in FI (ledger &1/company code &2)

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_CUST046 - Add. crcy type doesn't match the one in FI (ledger &1/company code &2) ?

  The SAP error message FINS_ACDOC_CUST046 indicates that there is a mismatch between the additional currency type defined in the document and the one that is configured in the Financial Accounting (FI) module for the specified ledger and company code. This error typically arises during the posting of financial documents when the additional currency type does not align with the settings in the system.
  Cause:
  
  Configuration Mismatch: The additional currency type used in the document does not match the additional currency type defined in the configuration for the specific ledger and company code.
  Document Settings: The document being posted may have been set up with an additional currency type that is not allowed or recognized for the specified ledger and company code.
  Customizing Settings: The customizing settings for the company code or ledger may not be properly configured to support the additional currency type being used.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the transaction code OB22 (or the relevant configuration path) to check the settings for the company code and ledger.
  Ensure that the additional currency types are correctly defined and that they match the ones being used in the document.
  
  
  
  Review Document:
  
  Review the document that is causing the error to see which additional currency type is being used.
  Ensure that the additional currency type is valid for the specified ledger and company code.
  
  
  
  Adjust Document Settings:
  
  If the document is incorrect, you may need to adjust the additional currency type in the document or create a new document with the correct settings.
  
  
  
  Consult with Configuration Team:
  
  If you are unsure about the configuration settings, consult with your SAP configuration team or a functional consultant who specializes in FI to ensure that the settings are correct.
  
  
  
  Testing:
  
  After making the necessary adjustments, perform a test posting to ensure that the error has been resolved.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  OB22: Configuration for additional currency types.
  FB01: General posting transaction where the error may occur.
  
  
  Documentation: Review SAP documentation or notes related to currency types and financial document postings for further insights.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.