How To Fix FTR_GENERAL035 - Security account &1 does not exist in company code &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FTR_GENERAL - Common messages for Correspondence object

• Message number: 035

• Message text: Security 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 FTR_GENERAL035 - Security account &1 does not exist in company code &2 ?

  The SAP error message FTR_GENERAL035 indicates that a security account specified in a financial transaction does not exist in the specified company code. This error typically arises in the context of financial transactions involving securities, such as when processing transactions related to investments, bonds, or other financial instruments.
  Cause:
  The error can occur due to several reasons:
  
  Missing Security Account: The security account referenced in the transaction has not been created or is not defined in the system for the specified company code.
  Incorrect Configuration: The configuration settings for the security accounts may not be properly set up in the system.
  Data Entry Error: There may be a typographical error in the security account number or company code entered in the transaction.
  Company Code Assignment: The security account may exist, but it is not assigned to the specified company code.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Security Account Configuration:
  
  Go to the transaction code OB52 (or the relevant configuration transaction) to check if the security account exists for the specified company code.
  If it does not exist, you will need to create it.
  
  
  
  Create Security Account:
  
  Use transaction code OAS1 (or the relevant transaction for creating security accounts) to create the missing security account for the specified company code.
  
  
  
  Verify Company Code Assignment:
  
  Ensure that the security account is correctly assigned to the company code in question. This can be checked in the configuration settings for financial instruments.
  
  
  
  Review Transaction Data:
  
  Double-check the transaction data for any typographical errors in the security account number or company code.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP support team for specific configuration steps related to security accounts.
  
  
  
  Testing:
  
  After making the necessary changes, re-attempt the transaction to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OAS1 (for creating security accounts), OB52 (for financial accounting settings), and FTR_CREATE (for creating financial transactions).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to create or modify security accounts.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or consult with an SAP expert for further assistance.