How To Fix FGL_PRE_CHECK002 - Currency type &2 cannot be used in FI by company code &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FGL_PRE_CHECK - Pre Transition Check FI-GL

• Message number: 002

• Message text: Currency type &2 cannot be used in FI by company code &1

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 FGL_PRE_CHECK002 - Currency type &2 cannot be used in FI by company code &1 ?

  The SAP error message FGL_PRE_CHECK002 indicates that a specific currency type cannot be used in Financial Accounting (FI) for a given company code. This error typically arises during the configuration or execution of financial transactions when the system detects an inconsistency with the currency settings.
  Cause:
  
  Currency Type Configuration: The currency type specified (denoted as &2 in the error message) is not configured for the company code (denoted as &1). This could happen if the currency type is not assigned to the company code in the system settings.
  Missing Currency Type: The currency type may not be defined in the system at all, or it may not be activated for the specific company code.
  Incorrect Transaction: The transaction being executed may not support the specified currency type, leading to this error.
  
  Solution:
  
  
  Check Currency Type Configuration:
  
  Go to the transaction code OB22 (or navigate through the menu: SPRO > Financial Accounting > Financial Accounting Global Settings > Currencies > Define Currency Types).
  Verify that the currency type in question is defined and check its settings.
  
  
  
  Assign Currency Type to Company Code:
  
  If the currency type is not assigned to the company code, you need to assign it. This can be done in the same configuration area (OB22).
  Ensure that the currency type is marked as "active" for the company code.
  
  
  
  Review Company Code Settings:
  
  Check the company code settings in transaction code OBY6 (or SPRO > Financial Accounting > Financial Accounting Global Settings > Company Code > Define Company Code).
  Ensure that the currency settings for the company code are correctly configured.
  
  
  
  Consult Documentation:
  
  If you are unsure about the currency types and their usage, refer to SAP documentation or consult with your SAP functional consultant for guidance.
  
  
  
  Testing:
  
  After making the necessary changes, test the transaction again to ensure that the error is resolved.
  
  
  
  Related Information:
  
  Currency Types: In SAP, currency types are used to differentiate between various currencies used in financial transactions (e.g., local currency, group currency, hard currency).
  Company Code: A company code is the smallest organizational unit in SAP for which a complete self-contained set of accounts can be drawn up.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB22 (Define Currency Types) and OBY6 (Define Company Code) for configuration tasks.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant for further investigation.