How To Fix TRS0836 - Sec. acct ID &1 has already been used in sec. acct &2

SAP Error Message - Details

• Message type: E = Error

• Message class: TRS0 - Messages for Reconciliation

• Message number: 836

• Message text: Sec. acct ID &1 has already been used in sec. acct &2

What causes this issue?

The security ID &V1& has already been used in another company code: &V2&
. A security ID must determine a unique company code.

System Response

The securities account master data is not consistent and cannot be
saved.

How to fix this error?

You need to either change the securities account ID or leave the ID
field empty.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TRS0836 - Sec. acct ID &1 has already been used in sec. acct &2 ?

  The SAP error message TRS0836 indicates that a secondary account ID has already been used in another secondary account. This typically occurs in the context of financial accounting or controlling when trying to assign or use a secondary account that is already associated with a different primary account or transaction.
  Cause:
  
  Duplicate Assignment: The secondary account ID you are trying to use is already linked to another secondary account. This can happen if there are multiple transactions or configurations that reference the same secondary account ID.
  Configuration Issues: There may be issues in the configuration of the accounts in the system, leading to conflicts when trying to assign secondary accounts.
  Data Integrity Issues: There might be inconsistencies in the data, such as incorrect entries or missing updates that lead to this error.
  
  Solution:
  
  Check Existing Assignments: Review the existing assignments of the secondary account ID in question. You can do this by navigating to the relevant transaction or configuration area in SAP where secondary accounts are managed.
  Modify or Remove Conflicting Entries: If you find that the secondary account ID is indeed being used elsewhere, you may need to either modify the existing assignment or remove it if it is no longer needed.
  Use a Different Secondary Account ID: If the secondary account ID is required for another transaction, consider using a different secondary account ID that is not currently in use.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on managing secondary accounts and resolving conflicts.
  Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP support for assistance. They can provide more detailed insights based on your specific system configuration.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FS00 (G/L Account Master Data), OB52 (Open and Close Posting Periods), and others that may help in managing account assignments.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide patches or additional guidance on resolving the issue.
  User Roles and Authorizations: Ensure that you have the necessary permissions to make changes to account assignments, as lack of authorization can also lead to errors.
  
  By following these steps, you should be able to identify the cause of the TRS0836 error and implement a suitable solution.