How To Fix /ACCGO/FEE165 - G/L account determination possible from either BRF+ or cond. type

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/FEE -

• Message number: 165

• Message text: G/L account determination possible from either BRF+ or cond. type

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/FEE165 - G/L account determination possible from either BRF+ or cond. type ?

  The SAP error message /ACCGO/FEE165 typically indicates an issue with the determination of the General Ledger (G/L) account in the context of the SAP system's financial processes. This error can arise when the system is unable to determine the appropriate G/L account for a transaction, which can be due to several reasons.
  Cause:
  
  Configuration Issues: The G/L account determination might not be properly configured in the system. This could be due to missing or incorrect entries in the configuration tables.
  BRF+ Configuration: If the system is using Business Rule Framework plus (BRF+), there may be issues with the rules defined for G/L account determination.
  Condition Type: The condition type used for the transaction may not be set up correctly, or the necessary condition records may be missing.
  Master Data Issues: The master data for the relevant business objects (like customers, vendors, or materials) may not be complete or correctly maintained.
  Transaction Type: The transaction type being processed may not have a corresponding G/L account defined in the configuration.
  
  Solution:
  
  Check Configuration: Review the configuration settings for G/L account determination in the relevant modules (e.g., Financial Accounting, Controlling). Ensure that all necessary entries are present and correct.
  Review BRF+ Rules: If BRF+ is being used, check the rules defined for G/L account determination. Ensure that the rules are correctly set up and that they cover the scenarios you are trying to process.
  Condition Type Setup: Verify that the condition type used in the transaction is correctly configured and that the necessary condition records exist.
  Master Data Review: Check the master data for completeness and correctness. Ensure that all relevant fields are filled out and that the data is consistent.
  Transaction Type Configuration: Ensure that the transaction type being processed has a corresponding G/L account defined in the configuration.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OBYC (for automatic account determination) or BRF+ (for managing business rules) to access the relevant configuration settings.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  Documentation: Refer to SAP documentation for detailed guidance on G/L account determination and BRF+ configuration.
  Testing: After making changes, perform testing to ensure that the G/L account determination works as expected for the relevant transactions.
  
  If the issue persists after checking these areas, it may be beneficial to consult with an SAP functional consultant or support team for further assistance.