How To Fix /ACCGO/FEE_SI028 - G/L account not found for fee &1 in BRF+

/ACCGO/FEE_SI028 - Overview

• Message type: E = Error

• Message class: /ACCGO/FEE_SI -

• Message number: 028

• Message text: G/L account not found for fee &1 in BRF+

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.

/ACCGO/FEE_SI028 - Details

• The SAP error message /ACCGO/FEE_SI028 G/L account not found for fee &1 in BRF+ typically indicates that the system is unable to find a General Ledger (G/L) account associated with a specific fee in the Business Rule Framework plus (BRF+). This can occur in various scenarios, such as during the processing of financial transactions or when executing specific business rules that rely on fee configurations.
  
  Cause:
  
  Missing G/L Account Configuration: The G/L account for the specified fee has not been defined in the system.
  Incorrect Fee Configuration: The fee might not be correctly configured in the BRF+ application, leading to the system not being able to link it to a G/L account.
  Data Inconsistency: There may be inconsistencies in the master data or configuration settings that prevent the system from finding the appropriate G/L account.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or access the G/L account.
  
  
  Solution:
  
  
  Check G/L Account