Message type: E = Error
Message class: UMG - Message Class for the Unicode Migration Tool.
Message number: 413
Message text: Transaction SPUMG is currently locked. Return code: &1
You called transaction SPUMG but a status check found that SPUMG cannot
be executed due to Upgrade activities.
+,,Return code 5: Shadow instance is running
+,,Return code 6: Upgrade reached phase EU_IMP
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Execution of SPUMG will be released again after Upgrade activities are
completed.
Error message extract from SAP system. Copyright SAP SE.
UMG413
- Transaction SPUMG is currently locked. Return code: &1 ?The SAP error message UMG413 indicates that the transaction SPUMG (which is used for the Support Package Manager) is currently locked, and the return code provides additional information about the nature of the lock. This error typically occurs when another user or process is currently using the transaction, preventing you from accessing it.
Cause: Concurrent Access: Another user or background job is currently executing the SPUMG transaction, which locks it for other users. Long-running Process: A previous execution of the SPUMG transaction may be taking longer than expected, causing the lock to persist. System Issues: There may be issues with the SAP system that are causing transactions to hang or not release locks properly.
Solution: Wait and Retry: If the transaction is locked due to another user, the simplest solution is to wait for that user to complete their task and then try again. Check Active Sessions: Use transaction code SM66 (Global Work Process Overview) or SM50
Get instant SAP help. Sign up for our Free Essentials Plan.
UMG412
SPUMG has been reset. Call transaction SPUMG again to start from scratch.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
UMG411
Unicode Conversion tables might contain corrupted entries (see long text)
What causes this issue? You execute transaction SPUMG for the preparation of a Unicode conversion. According to SPUMGs status tables you execute SPUM...
UMG414
Option &1 does not exist.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
UMG415
Table &1 excluded from scan. (Read long text).
What causes this issue? The table &V1& is currently excluded from the scan because the SPUMG status check "Container Tables (Type K, L)&...
Click on this link to search all SAP messages.