Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: TPM_TRG - Treasury Position Management: Cross-Package Messages
Message number: 358
Message text: Securities account group missing in master data of sec.acct &1, CoCd &2
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.
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.
TPM_TRG358
- Securities account group missing in master data of sec.acct &1, CoCd &2 ?The SAP error message TPM_TRG358 indicates that there is a missing securities account group in the master data for a specific security account in a given company code. This error typically arises in the context of Treasury and Risk Management (TRM) when dealing with securities transactions.
Cause:
The error occurs when the system tries to process a transaction related to a security, but it cannot find the necessary securities account group in the master data. This can happen due to several reasons:
- Missing Configuration: The securities account group has not been defined in the system for the specified security account.
- Incorrect Master Data: The master data for the security account may not have been set up correctly or completely.
- Company Code Issues: The company code specified may not have the required securities account group configured.
Solution:
To resolve the TPM_TRG358 error, you can follow these steps:
Check Securities Account Master Data:
- Go to the transaction code
OAS1
(or the relevant transaction for managing securities accounts).- Verify that the securities account in question is correctly set up and that it includes the necessary account group.
Define Securities Account Group:
- If the securities account group is missing, you need to create it. This can typically be done in the configuration settings for Treasury and Risk Management.
- Use transaction code
SPRO
to access the configuration menu, and navigate to:Financial Supply Chain Management -> Treasury and Risk Management -> Master Data -> Define Securities Account Groups
- Create or modify the securities account group as needed.
Assign Securities Account Group to Company Code:
- Ensure that the securities account group is assigned to the relevant company code. This can also be done in the configuration settings.
Check Authorizations:
- Ensure that the user has the necessary authorizations to access and modify securities account data.
Test the Changes:
- After making the necessary changes, test the transaction again to ensure that the error is resolved.
Related Information:
OAS1
, SPRO
, and others related to Treasury and Risk Management.By following these steps, you should be able to resolve the TPM_TRG358 error and ensure that your securities account data is correctly configured in SAP.
Get instant SAP help. Sign up for our Free Essentials Plan.
TPM_TRG357
Position differentiation not defined for acct code &1, val.area 001
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TPM_TRG356
Operative valuation procedure &1 could not be converted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TPM_TRG359
No Customizing request was found
What causes this issue? While converting data you tried to carry out a step to convert Customizing. However no Customizing request was defined for th...
TPM_TRG360
Position differentiation for is missing for company code &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.