How To Fix FINS_ACDOC_UTIL023 - Batch Input not possible. Company code &1 has non integrated currencies

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_ACDOC_UTIL - Messages for package FINS_ACDOC_UTIL

• Message number: 023

• Message text: Batch Input not possible. Company code &1 has non integrated currencies

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_UTIL023 - Batch Input not possible. Company code &1 has non integrated currencies ?

  The SAP error message FINS_ACDOC_UTIL023 indicates that there is an issue with the currency settings for a specific company code in the system. This error typically arises when you attempt to perform a batch input operation (such as posting documents) for a company code that has non-integrated currencies, meaning that the currency settings do not align with the expected configurations for the transaction you are trying to execute.
  Cause:
  
  Non-Integrated Currencies: The company code is set up with currencies that are not integrated with the transaction you are trying to perform. This can happen if the company code is configured to use a different currency type (e.g., local currency, group currency) that does not match the currency of the transaction.
  Currency Configuration: The currency settings in the company code may not be properly configured, leading to inconsistencies when processing financial documents.
  Batch Input Session: The batch input session may contain data that does not conform to the currency settings of the company code.
  
  Solution:
  
  
  Check Company Code Currency Settings:
  
  Go to the transaction code OB22 (or SPRO -> Financial Accounting -> Financial Accounting Global Settings -> Company Code -> Define Company Code) and verify the currency settings for the company code in question.
  Ensure that the local currency and any additional currencies (like group currency) are correctly defined.
  
  
  
  Review the Batch Input Data:
  
  Check the data being processed in the batch input session. Ensure that the currencies used in the documents match the currencies defined for the company code.
  If necessary, adjust the data in the batch input session to align with the company code's currency settings.
  
  
  
  Adjust Currency Configuration:
  
  If the company code needs to support multiple currencies, consider adjusting the configuration to allow for integrated currencies. This may involve changing the currency type or adding additional currencies as needed.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP support team for specific guidance on handling currency configurations and batch input processes.
  
  
  
  Testing:
  
  After making the necessary adjustments, test the batch input process again to ensure that the error does not reoccur.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB22 for company code settings, SE38 for running batch input sessions, and SM35 for monitoring batch input sessions.
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address the issue.
  User Roles and Authorizations: Ensure that the user executing the batch input has the necessary authorizations to perform transactions in the specified company code.
  
  By following these steps, you should be able to resolve the error and successfully process your batch input transactions.