How To Fix /ACCGO/FEE207 - ***&1 G/L account started***

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/FEE -

• Message number: 207

• Message text: ***&1 G/L account started***

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 /ACCGO/FEE207 - ***&1 G/L account started*** ?

  The SAP error message /ACCGO/FEE207 ***&1 G/L account started*** typically relates to issues with General Ledger (G/L) accounts in the context of the SAP system, particularly in the area of financial accounting or controlling. This error can occur in various scenarios, such as during the posting of transactions, during the execution of reports, or when trying to perform certain financial operations.
  Cause:
  
  G/L Account Configuration: The G/L account may not be properly configured in the system. This could include missing settings for account types, account groups, or other related configurations.
  Account Status: The G/L account might be in a status that does not allow postings, such as being blocked or marked for deletion.
  Posting Period: The posting period may be closed, preventing any transactions from being posted to that G/L account.
  Transaction Type: The transaction type being used may not be compatible with the G/L account in question.
  Authorization Issues: The user may not have the necessary authorizations to post to the specified G/L account.
  
  Solution:
  
  
  Check G/L Account Configuration:
  
  Navigate to the G/L account in the SAP system and verify its configuration. Ensure that it is set up correctly for the intended use.
  Check the account type and ensure it is appropriate for the transactions being posted.
  
  
  
  Review Account Status:
  
  Check if the G/L account is blocked or marked for deletion. If it is, you may need to unblock it or create a new account.
  
  
  
  Verify Posting Period:
  
  Ensure that the posting period is open. You can check this in the transaction code OB52 to see if the period is open for posting.
  
  
  
  Check Transaction Type:
  
  Ensure that the transaction type being used is compatible with the G/L account. You may need to adjust the transaction type or use a different G/L account.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to post to the G/L account. This can be checked with the help of your SAP security team.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for more specific guidance related to the error message.
  
  
  
  Related Information:
  
  Transaction Codes: You may find it useful to use transaction codes such as FS00 (G/L Account Master Data), OB52 (Open and Close Posting Periods), and SU01 (User Maintenance) to investigate the issue further.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Community Forums: Consider searching or posting in SAP community forums for insights from other users who may have encountered the same issue.
  
  If the problem persists after following these steps, it may be necessary to involve your SAP support team or a consultant for further investigation.