How To Fix FINS_ACDOC_CUST393 - Cur.types of extens. &2 and underlying ledger &3 in comp. code &1 differ

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing

• Message number: 393

• Message text: Cur.types of extens. &2 and underlying ledger &3 in comp. code &1 differ

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_CUST393 - Cur.types of extens. &2 and underlying ledger &3 in comp. code &1 differ ?

  The SAP error message FINS_ACDOC_CUST393 indicates that there is a mismatch between the currency types of the extension and the underlying ledger in a specific company code. This error typically arises during financial postings or when trying to create or modify documents in the system.
  Cause:
  
  Currency Type Mismatch: The error occurs when the currency type defined in the extension (for example, a custom table or a specific configuration) does not match the currency type defined in the underlying ledger for the specified company code.
  Configuration Issues: There may be inconsistencies in the configuration settings for currency types in the Financial Accounting (FI) module, particularly in the settings for ledgers and extensions.
  Custom Development: If there are custom developments or enhancements in the system, they may not align with the standard currency settings.
  
  Solution:
  
  
  Check Currency Type Configuration:
  
  Go to the configuration settings in SAP (Transaction Code: SPRO).
  Navigate to Financial Accounting (New) > General Ledger Accounting (New) > Ledger > Define Ledgers.
  Verify the currency types assigned to the ledger and ensure they match the currency types used in the extension.
  
  
  
  Review Company Code Settings:
  
  Check the company code settings (Transaction Code: OX02).
  Ensure that the currency type settings for the company code are consistent with the ledger settings.
  
  
  
  Analyze Custom Extensions:
  
  If there are custom extensions or modifications, review the code to ensure that it adheres to the currency type settings of the underlying ledger.
  Make necessary adjustments to align the currency types.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
  
  
  
  Testing:
  
  After making changes, perform tests to ensure that the error no longer occurs during financial postings or document processing.
  
  
  
  Related Information:
  
  
  Currency Types: In SAP, currency types are used to define how currencies are handled in financial transactions. Common currency types include:
  
  00: Document currency
  10: Local currency
  20: Hard currency
  30: Index-based currency
  
  
  
  Transaction Codes:
  
  SPRO: Access to the SAP Reference IMG for configuration.
  OX02: Configuration for company codes.
  OB22: Define currency types.
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions for this specific error message.
  
  
  If the issue persists after following these steps, it may be beneficial to consult with an SAP functional consultant or reach out to SAP support for further assistance.