How To Fix 64436 - A new securities account group was created for the current sec. account

SAP Error Message - Details

• Message type: E = Error

• Message class: 64 - Treasury Management: Securities

• Message number: 436

• Message text: A new securities account group was created for the current sec. account

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 64436 - A new securities account group was created for the current sec. account ?

  The SAP error message 64436 indicates that a new securities account group has been created for the current securities account. This typically occurs in the context of managing financial instruments and securities within the SAP system, particularly in the Asset Management or Financial Accounting modules.
  Cause:
  The error message is triggered when:
  
  A new securities account group is created in the system, which may not have been properly configured or linked to the existing securities accounts.
  There may be inconsistencies in the configuration of the securities account groups, leading to the system not recognizing the new group in relation to existing securities accounts.
  The securities account being processed does not have a valid account group assigned to it.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Configuration:
  
  Go to the configuration settings for securities account groups in the SAP system. Ensure that the new account group is properly defined and configured.
  Verify that the new securities account group is linked to the relevant securities accounts.
  
  
  
  Assign Account Group:
  
  If the securities account does not have an account group assigned, you may need to assign the correct account group to the securities account.
  This can typically be done in the transaction code related to securities account management (e.g., transaction code OASV for securities account groups).
  
  
  
  Review Master Data:
  
  Check the master data for the securities account in question. Ensure that all required fields are filled out correctly and that the account group is valid.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to securities account management for any specific guidelines or requirements regarding account groups.
  
  
  
  Contact Support:
  
  If the issue persists after checking the configuration and master data, consider reaching out to your SAP support team or consulting with SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OASV (for managing securities account groups) and OAS1 (for creating securities accounts).
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional insights or patches that could resolve the issue.
  User Roles: Ensure that the user has the necessary permissions to create or modify securities account groups and accounts.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.