How To Fix FICUSTOM_CORE002 - The document &1 &2 &3 uses the currency &4 and it will be ignored.

SAP Error Message - Details

• Message type: E = Error

• Message class: FICUSTOM_CORE - Customizable Messages for Funds Management - CORE

• Message number: 002

• Message text: The document &1 &2 &3 uses the currency &4 and it will be ignored.

What causes this issue?

The document &V1& &V2& &V3& uses the currency &V4& and it will be
ignored in the automatic down payment clearing portion of this posting.
The document being posted uses a different transaction currency.

System Response

No automatic Down Payment Clearing will be created in reference to the
document &V1& &V2& &V3&.

How to fix this error?

This is a customizable message with default value 'W' to inform that no
automatic down payment clearing entries will be created in reference to
this document. It is possible to change the message to 'E' to stop the
entire posting or '-' to hide this message. Use the transaction SM30 to
maintain the view V_T100C using Application Area FICUSTOM_CORE and
message number 002.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FICUSTOM_CORE002 - The document &1 &2 &3 uses the currency &4 and it will be ignored. ?

  The SAP error message FICUSTOM_CORE002 indicates that a document is using a currency that is not supported or recognized in the current context, and as a result, it will be ignored. This error typically arises in financial transactions or postings where currency settings are critical.
  Cause:
  
  Unsupported Currency: The document is using a currency that is not configured in the system or is not allowed for the specific transaction type.
  Currency Configuration: The currency may not be set up in the relevant company code or controlling area.
  Document Type Restrictions: Certain document types may have restrictions on the currencies that can be used.
  Currency Conversion Issues: If the system cannot convert the currency to the local currency or the currency used in the transaction, it may ignore the document.
  Master Data Issues: The master data for the vendor, customer, or other entities may not support the currency being used.
  
  Solution:
  
  
  Check Currency Configuration:
  
  Ensure that the currency used in the document is configured in the system. You can check this in the transaction code OB08 (Define Exchange Rates) and OBY6 (Define Company Code Currency).
  
  
  
  Review Document Type Settings:
  
  Verify if the document type allows the currency being used. This can be checked in the configuration settings for the specific document type.
  
  
  
  Update Master Data:
  
  Ensure that the master data for the relevant entities (customers, vendors, etc.) supports the currency. You can update the master data using transaction codes like XD02 (Change Customer) or MK02 (Change Vendor).
  
  
  
  Currency Conversion:
  
  If applicable, ensure that the system can convert the currency to the local currency. Check the exchange rate settings and ensure they are up to date.
  
  
  
  Consult SAP Notes:
  
  Look for any relevant SAP Notes that may address this specific error. Sometimes, there are known issues or patches that can resolve the problem.
  
  
  
  Testing:
  
  After making the necessary changes, test the transaction again to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  OB08: Define Exchange Rates
  OBY6: Define Company Code Currency
  XD02: Change Customer
  MK02: Change Vendor
  
  
  SAP Documentation: Refer to SAP Help Portal for detailed documentation on currency settings and financial transactions.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant for further investigation.