How To Fix FB035 - No data exists for creating G/L accounts for company code &

SAP Error Message - Details

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 035

• Message text: No data exists for creating G/L accounts for company code &

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 FB035 - No data exists for creating G/L accounts for company code & ?

  The SAP error message FB035 ("No data exists for creating G/L accounts for company code &") typically occurs when you attempt to create a General Ledger (G/L) account in a company code that does not have the necessary configuration or data set up. Here are the potential causes, solutions, and related information for this error:
  Causes:
  
  Missing Company Code Configuration: The company code you are trying to create the G/L account for may not be properly configured in the system.
  Missing Chart of Accounts Assignment: The company code might not be assigned to a chart of accounts, or the chart of accounts does not have the necessary settings.
  Authorization Issues: The user may not have the required authorizations to create G/L accounts for the specified company code.
  Inactive Company Code: The company code may be inactive or not fully set up in the system.
  Missing Master Data: Required master data for the G/L account creation process may be missing.
  
  Solutions:
  
  
  Check Company Code Configuration:
  
  Go to transaction code OBY6 to verify that the company code is correctly configured and active.
  Ensure that the company code is assigned to a valid chart of accounts.
  
  
  
  Verify Chart of Accounts Assignment:
  
  Use transaction code OB13 to check if the company code is assigned to a chart of accounts.
  Ensure that the chart of accounts is properly defined and contains the necessary account types.
  
  
  
  Review User Authorizations:
  
  Check the user roles and authorizations to ensure that the user has the necessary permissions to create G/L accounts.
  Use transaction code SU53 to analyze any authorization issues after attempting the action.
  
  
  
  Check Company Code Status:
  
  Ensure that the company code is not marked as inactive. You can check this in the company code settings.
  
  
  
  Ensure Required Master Data Exists:
  
  Verify that all required master data for G/L account creation is in place, including account groups and field status groups.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  OBY6: Company Code Configuration
  OB13: Chart of Accounts Assignment
  FS00: Create/Change G/L Account
  SU53: Authorization Check
  
  
  
  Documentation: Refer to SAP Help documentation for detailed steps on configuring company codes and chart of accounts.
  
  
  SAP Notes: Check SAP Notes for any specific patches or updates related to this error message.
  
  
  By following these steps, you should be able to identify the root cause of the FB035 error and implement the necessary solutions to resolve it. If the issue persists, consider reaching out to your SAP support team for further assistance.