How To Fix FB104 - Trans. & &: Acct already exists; general area not being processed

SAP Error Message - Details

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 104

• Message text: Trans. & &: Acct already exists; general area not being processed

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 FB104 - Trans. & &: Acct already exists; general area not being processed ?

  The SAP error message FB104 ("Trans. & &: Acct already exists; general area not being processed") typically occurs when you are trying to post a transaction in the Financial Accounting (FI) module, and the system detects that the account you are trying to use already exists in the system, but it is not set up correctly for the transaction type or the general area you are trying to process.
  Causes:
  
  Account Configuration: The account you are trying to use may not be configured for the specific transaction type or general ledger area you are working with.
  Account Type: The account might be set up as a different type (e.g., asset, liability, expense) that does not allow the transaction you are attempting to post.
  Posting Period: The posting period may be closed, preventing any transactions from being processed for that account.
  Account Group Settings: The account group settings may restrict certain types of postings or transactions.
  Missing Master Data: The necessary master data for the account may not be fully maintained or may be missing.
  
  Solutions:
  
  
  Check Account Configuration: Verify the configuration of the account in the SAP system. Ensure that it is set up correctly for the type of transaction you are trying to post.
  
  Use transaction code FS00 to check the account details.
  
  
  
  Review Transaction Type: Ensure that the transaction type you are using is compatible with the account. If necessary, consult with your finance team to confirm the correct transaction type.
  
  
  Open Posting Period: Check if the posting period is open. You can do this using transaction code OB52 to review and adjust the posting periods if needed.
  
  
  Account Group Settings: Review the account group settings to ensure that they allow the type of transaction you are trying to post. You can check this in the configuration settings.
  
  
  Master Data Maintenance: Ensure that all necessary master data for the account is maintained. This includes checking for any missing fields or incorrect settings.
  
  
  Consult Documentation: If you are unsure about the configuration or settings, refer to SAP documentation or consult with your SAP support team for guidance.
  
  
  Related Information:
  
  Transaction Codes: 
  
  FS00: Display/Change G/L Account Master Data
  OB52: Maintain Posting Periods
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Authorization: Ensure that you have the necessary authorizations to post transactions to the account in question.
  
  If the issue persists after checking these areas, it may be beneficial to involve your SAP support team or a consultant who specializes in SAP FI to further investigate the problem.