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: 058
Message text: Positions in company code &1 are blocked by user &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_TRG058
- Positions in company code &1 are blocked by user &2 ?The SAP error message TPM_TRG058 indicates that certain positions in a company code are blocked by a specific user. This typically occurs in the context of Treasury and Risk Management (TRM) or similar financial modules where certain transactions or positions are restricted due to user locks.
Cause:
- User Lock: The positions in the specified company code are locked by a user, which prevents other users from making changes or processing transactions related to those positions.
- Transaction in Process: A user may be currently processing a transaction that involves the locked positions, leading to the blocking of those positions for other users.
- Authorization Issues: The user may not have the necessary authorizations to access or modify the positions, leading to a perceived lock.
Solution:
- Identify the User: Check which user has locked the positions. This can often be done through transaction codes like
SM12
(to view and manage locks) orSM21
(to view system logs).- Contact the User: If possible, contact the user who has locked the positions to understand why they are locked and if they can release them.
- Release Locks: If the user is unavailable or if the lock is no longer valid (e.g., the user has logged off), an administrator can manually release the locks using transaction
SM12
.- Check Authorizations: Ensure that the user trying to access the positions has the necessary authorizations. This may involve checking roles and profiles assigned to the user.
- Review Processes: If this is a recurring issue, review the business processes to ensure that locks are not being held unnecessarily and that users are aware of how to release locks when they are done.
Related Information:
SM12
: To view and manage lock entries.SM21
: To view system logs for any related errors or warnings.SU01
: To manage user authorizations and roles.By following these steps, you should be able to resolve the TPM_TRG058 error and understand the underlying issues related to locked positions in your SAP system.
Get instant SAP help. Sign up for our Free Essentials Plan.
TPM_TRG057
Warning! Valuation area &1 initialized with key date &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TPM_TRG056
Test run for reversal of initialization step &1 executed successfully
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TPM_TRG059
Key date: &3 is earlier than the key date of step &1: &2
What causes this issue? You want to execute the current valuation area-dependent step for the key date &V3&. However, the valuation area-inde...
TPM_TRG060
Key date: &3 is not the same as the key date of step &1: &2
What causes this issue? You wish to carry out the current valuation area-independent step for the key date. However, the valuation area-independent s...
Click on this link to search all SAP messages.