How To Fix NEW_FEBA109 - G/L account &1 does not exist in company code &2

SAP Error Message - Details

• Message type: E = Error

• Message class: NEW_FEBA - Messages for the new bank statement postprocessing

• Message number: 109

• Message text: G/L account &1 does not exist in company code &2

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 NEW_FEBA109 - G/L account &1 does not exist in company code &2 ?

  The SAP error message NEW_FEBA109 indicates that a General Ledger (G/L) account specified in a transaction does not exist in the specified company code. This error typically occurs when trying to post a financial transaction that references a G/L account that has not been set up for the given company code.
  Cause:
  
  G/L Account Not Created: The G/L account has not been created in the specified company code.
  Incorrect Company Code: The G/L account exists, but it is not assigned to the company code you are trying to use.
  Data Entry Error: There may be a typo or incorrect entry in the G/L account number or company code.
  Account Blocked or Deleted: The G/L account may have been blocked or deleted in the system.
  
  Solution:
  
  
  Check G/L Account Creation:
  
  Go to the transaction code FS00 (G/L Account Master Record) and check if the G/L account exists for the specified company code.
  If it does not exist, you will need to create it.
  
  
  
  Create G/L Account:
  
  If the G/L account is missing, create it using transaction code FS00. Ensure you enter the correct company code and fill in all required fields.
  
  
  
  Verify Company Code Assignment:
  
  If the G/L account exists but is not assigned to the company code, you may need to create a new account or modify the existing one to include the correct company code.
  
  
  
  Check for Typos:
  
  Double-check the G/L account number and company code entered in the transaction for any typographical errors.
  
  
  
  Review Account Status:
  
  Ensure that the G/L account is not blocked or deleted. You can check this in the G/L account master record.
  
  
  
  Consult with Finance Team:
  
  If you are unsure about creating or modifying G/L accounts, consult with your finance or accounting team to ensure compliance with accounting policies.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  FS00: Create/Change G/L Account Master Record
  FBL3N: Display G/L Account Line Items
  OBY6: Define Company Code
  
  
  Authorization: Ensure you have the necessary authorizations to create or modify G/L accounts in SAP.
  Documentation: Refer to your organization's SAP documentation or guidelines for creating G/L accounts and managing financial transactions.
  
  By following these steps, you should be able to resolve the NEW_FEBA109 error and successfully post your financial transactions.