How To Fix J3671 - Company code &: Account with number & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: J3 - Dialog Messages for Data Pool Entry Transactions

• Message number: 671

• Message text: Company code &: Account with number & 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 J3671 - Company code &: Account with number & does not exist ?

  The SAP error message J3671 indicates that the system cannot find an account with the specified account number in the specified company code. This error typically occurs during financial transactions or postings when the system attempts to access an account that is either not created, not active, or not properly configured in the specified company code.
  Causes:
  
  Account Not Created: The account number you are trying to use has not been created in the system for the specified company code.
  Inactive Account: The account exists but is marked as inactive or blocked for postings.
  Incorrect Company Code: The account may exist in a different company code, and the transaction is being attempted in the wrong company code.
  Data Entry Error: There may be a typographical error in the account number or company code entered in the transaction.
  Configuration Issues: The account may not be properly configured in the chart of accounts or may not be assigned to the company code.
  
  Solutions:
  
  
  Check Account Existence:
  
  Go to the transaction code FS00 (G/L Account Master Record) and check if the account number exists for the specified company code.
  If it does not exist, you will need to create it.
  
  
  
  Create or Activate Account:
  
  If the account does not exist, create it using FS00.
  If the account exists but is inactive, you can activate it by editing the account settings.
  
  
  
  Verify Company Code:
  
  Ensure that you are using the correct company code in your transaction. If the account exists in another company code, you may need to switch to that company code or create the account in the intended company code.
  
  
  
  Check for Typographical Errors:
  
  Double-check the account number and company code for any typos or errors.
  
  
  
  Review Configuration:
  
  Ensure that the account is properly configured in the chart of accounts and is assigned to the relevant company code. This can be checked in the configuration settings of the financial module.
  
  
  
  Consult with SAP Support:
  
  If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting the SAP Help Portal for further assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  FS00: G/L Account Master Record
  OBY6: Define Company Code
  OBD2: Assign Company Code to Chart of Accounts
  
  
  
  SAP Documentation: Refer to the SAP Help Portal for detailed documentation on managing G/L accounts and troubleshooting common errors.
  
  
  User Roles: Ensure that you have the necessary permissions to create or modify G/L accounts in the system.
  
  
  By following these steps, you should be able to identify the cause of the error and implement the appropriate solution.