How To Fix FINS_ACDOC_CUST173 - Currency code of currency type &2 changed (see longtext)

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing

• Message number: 173

• Message text: Currency code of currency type &2 changed (see longtext)

What causes this issue?

You have changed the currency code of currency type &V3& (old value was
&V4&). This currency type is used in company code &V1&, ledger &V2&.
Postings exist in company code &V1&, ledger &V2&.
After this change, the existing journal entries are not longer valid.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

If the company code is already used in your production system, you need
to revoke this change.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FINS_ACDOC_CUST173 - Currency code of currency type &2 changed (see longtext) ?

  The SAP error message FINS_ACDOC_CUST173 indicates that there is an issue with the currency code associated with a specific currency type in the system. This error typically arises in the context of financial accounting and controlling, particularly when dealing with document postings or currency conversions.
  Cause:
  The error message is triggered when the currency code for a specific currency type (indicated by &2 in the message) has been changed in the system. This can happen due to various reasons, such as:
  
  Configuration Changes: Changes made in the configuration settings for currency types in the SAP system.
  Master Data Updates: Updates to master data that affect currency settings, such as changes in the company code or business area.
  Data Migration: During data migration or system upgrades, currency codes may have been altered or incorrectly mapped.
  Inconsistent Data: There may be inconsistencies in the data where the currency type is not aligned with the expected currency code.
  
  Solution:
  To resolve the FINS_ACDOC_CUST173 error, you can take the following steps:
  
  
  Check Configuration:
  
  Go to the configuration settings for currency types in the SAP system (Transaction code: OB22).
  Verify that the currency codes assigned to the relevant currency types are correct and consistent.
  
  
  
  Review Master Data:
  
  Check the master data for the affected entities (e.g., company codes, customers, vendors) to ensure that the currency settings are accurate.
  Ensure that the currency type and currency code are correctly assigned.
  
  
  
  Analyze Document Postings:
  
  Review the document postings that triggered the error. Check if there are any inconsistencies in the currency types used in the postings.
  If necessary, reverse or correct the postings that are causing the error.
  
  
  
  Consult Long Text:
  
  The error message may have a long text that provides additional details about the issue. You can view the long text by clicking on the message or using the message number in the SAP system.
  
  
  
  Check for Updates:
  
  If the issue arose after a recent update or migration, check if there are any known issues or patches related to currency handling in your version of SAP.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. Provide them with the error message details and any relevant context.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB22 (Define Currency Types), FB50 (G/L Account Document Entry), and others that may be involved in financial postings.
  Documentation: Review SAP documentation related to currency management and financial accounting for best practices and troubleshooting tips.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary corrections to resolve it.