Do you have any question about this error?
Message type: E = Error
Message class: EB - IS-U invoicing
Message number: 358
Message text: Lock for process &1 for contract account &2 from R582 already deleted
A lock was set for process &V1& and contract account &V2& during
invoicing
in event R582. This lock cannot be deleted, since
it has already been deleted in the intervening period.
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.
EB358
- Lock for process &1 for contract account &2 from R582 already deleted ?The SAP error message EB358 indicates that there is a lock for a process related to a contract account that has already been deleted. This typically occurs in the context of contract account management, where a process is trying to access or modify a contract account that no longer exists in the system.
Cause:
- Deleted Contract Account: The primary cause of this error is that the contract account referenced in the process has been deleted, but there is still an active lock on that account.
- Concurrency Issues: Another possible cause could be that multiple processes are trying to access the same contract account simultaneously, leading to a lock situation.
- System Inconsistencies: There may be inconsistencies in the database or application state, where the system still holds a lock for a deleted account.
Solution:
- Check Lock Entries: Use transaction code
SM12
to check for any lock entries related to the contract account. If you find any locks that are no longer valid, you can delete them.- Review Deletion Process: Ensure that the deletion process for the contract account is completed properly. If there are any pending processes or transactions that reference the deleted account, they should be resolved.
- Restart the Process: If the process that triggered the error can be restarted, try doing so after ensuring that there are no locks on the contract account.
- System Restart: In some cases, a system restart may help clear any lingering locks or inconsistencies.
- Consult SAP Notes: Check for any relevant SAP Notes or updates that may address this specific error. SAP frequently releases patches and updates that can resolve known issues.
Related Information:
SM12
(for lock entries), SE11
(for data dictionary), and SE80
(for object navigator) to investigate further.By following these steps, you should be able to resolve the EB358 error and prevent it from occurring in the future.
Get instant SAP help. Start your 7-day free trial now.
EB357
&1 invoicing unit (account: &2) tested successfully.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EB356
A total of &1 print documents locked for CI transfer (integration cat.&2)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EB359
Lock for process &1 for contract account &2 from R582 does not exist
What causes this issue? A lock was set for process &V1& and contract account &V2& during invoicing in event R582. This lock cannot be...
EB360
Change to the lock for process &1 and contract account &2 was not reset
What causes this issue? A lock was changed for process &V1& and contract account &V2& during invoicing in event R582. Reason &V3&...
Click on this link to search all SAP messages.