How To Fix FINS_RECON822 - Currency types in document header inconsistent: &1 message(s)

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation

• Message number: 822

• Message text: Currency types in document header inconsistent: &1 message(s)

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_RECON822 - Currency types in document header inconsistent: &1 message(s) ?

  The SAP error message FINS_RECON822 indicates that there is an inconsistency in the currency types used in the document header of a financial document. This typically occurs when the currency types defined in the document header do not match the expected values based on the configuration or the data entered.
  Cause:
  
  Inconsistent Currency Types: The document header may have different currency types (e.g., transaction currency, local currency, or group currency) that do not align with the expected configuration.
  Configuration Issues: There may be issues in the configuration of the currency types in the financial settings of the SAP system.
  Data Entry Errors: Manual data entry errors when creating or posting documents can lead to mismatched currency types.
  Document Type Settings: The document type settings may not be correctly configured to handle the currency types being used.
  
  Solution:
  
  Check Document Header: Review the document header for the specific document that triggered the error. Ensure that the currency types are correctly set and consistent.
  Review Configuration: Check the configuration settings for currency types in the SAP system. This can be done in the following path:
  
  SPRO ? Financial Accounting ? Financial Accounting Global Settings ? Currencies ? Define Currency Types
  
  
  Correct Data Entry: If the error is due to manual data entry, correct the currency types in the document header and repost the document.
  Document Type Settings: Verify the settings for the document type being used. Ensure that it is configured to accept the currency types present in the document.
  Use Transaction Codes: Utilize transaction codes like FB03 (Display Document) to view the document and check the currency types, or FB02 (Change Document) to make necessary adjustments.
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to financial document processing, such as FB01 (Post Document), FB02 (Change Document), and FB03 (Display Document).
  SAP Help Portal: Refer to the SAP Help Portal for detailed documentation on financial accounting and currency management.
  User Exits and BAdIs: If the issue persists, consider checking for any user exits or BAdIs that may be affecting the currency type handling in your specific implementation.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.