How To Fix FB658 - Account group & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 658

• Message text: Account group & does not exist

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 FB658 - Account group & does not exist ?

  The SAP error message FB658, which states "Account group & does not exist," typically occurs when you are trying to create or modify a master record (such as a vendor or customer) and the specified account group is not recognized by the system. This can happen for several reasons, including configuration issues or data entry errors.
  Causes:
  
  Incorrect Account Group: The account group you are trying to use may have been mistyped or does not exist in the system.
  Missing Configuration: The account group may not have been configured in the system. This can happen if the account group was deleted or never created.
  Authorization Issues: Sometimes, users may not have the necessary authorizations to view or use certain account groups.
  Transport Issues: If the account group was recently created or modified in a different environment (like development) and not transported to the production environment, it may not exist there.
  
  Solutions:
  
  
  Check Account Group: Verify that the account group you are trying to use is correctly spelled and exists in the system. You can do this by navigating to the relevant configuration area in SAP:
  
  For customer accounts: Use transaction code OBD2 to check customer account groups.
  For vendor accounts: Use transaction code OBD3 to check vendor account groups.
  
  
  
  Create or Modify Account Group: If the account group does not exist, you may need to create it:
  
  Use transaction code OBC4 to create a new account group if you have the necessary authorizations.
  Ensure that the account group is properly configured with the required settings.
  
  
  
  Check Authorizations: Ensure that your user profile has the necessary authorizations to access the account group. You may need to contact your SAP security administrator for assistance.
  
  
  Transport Requests: If the account group was created in a different environment, ensure that the transport request containing the account group has been successfully imported into the production environment.
  
  
  Consult Documentation: If you are unsure about the configuration or the process, refer to SAP documentation or consult with your SAP support team for guidance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBD2, OBD3, OBC4, and SE11 (for data dictionary) to help troubleshoot and resolve the issue.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Forums: Consider visiting SAP community forums or user groups for additional insights and solutions from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the FB658 error and implement a solution.