How To Fix GC772 - & not in currency table

SAP Error Message - Details

• Message type: E = Error

• Message class: GC - Error Messages for Consolidation/Extended General Ledger

• Message number: 772

• Message text: & not in currency table

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 GC772 - & not in currency table ?

  The SAP error message GC772 typically indicates that there is an issue with currency conversion or currency settings in the system. The specific message "not in currency table" suggests that the system is unable to find the required currency in the currency table, which can lead to problems in transactions that involve currency conversion.
  Causes of Error GC772
  
  Missing Currency in Currency Table: The currency you are trying to use is not defined in the currency table (TCURC) in SAP.
  Incorrect Configuration: The currency settings in the configuration may not be set up correctly, leading to the system not recognizing the currency.
  Data Entry Errors: There may be a typo or incorrect entry in the transaction where the currency is specified.
  Currency Type Issues: The currency type being used may not be valid for the transaction or may not be maintained in the system.
  
  Solutions to Error GC772
  
  
  Check Currency Table:
  
  Go to transaction code OB08 to check the currency exchange rates and ensure that the currency in question is defined.
  If the currency is missing, you can add it to the currency table.
  
  
  
  Maintain Currency Settings:
  
  Ensure that the currency is properly maintained in the relevant configuration settings. This can include checking the settings in the Financial Accounting (FI) module or the controlling (CO) module.
  
  
  
  Verify Transaction Data:
  
  Review the transaction data where the error occurred. Ensure that the currency code is entered correctly and matches the codes defined in the currency table.
  
  
  
  Check Currency Types:
  
  Ensure that the currency type being used is valid for the transaction. You can check this in the configuration settings for currency types.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help resources for any specific notes related to this error message. Sometimes, SAP notes may provide additional insights or patches that can resolve the issue.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may have additional tools or insights to help resolve the issue.
  
  
  
  Related Information
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB08 (Maintain Exchange Rates), TCURC (Currency Table), and OBBS (Currency Type).
  SAP Notes: Search for SAP Notes related to error GC772 in the SAP Support Portal for any known issues or fixes.
  User Forums: Check SAP community forums or user groups for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.