How To Fix CONV117 - BOMs cannot currently be locked: Job will be restarted later

SAP Error Message - Details

• Message type: E = Error

• Message class: CONV - Messages in Connection with the Converter

• Message number: 117

• Message text: BOMs cannot currently be locked: Job will be restarted later

What causes this issue?

The conversion was executed and the coverted originals checked in.
However &V1& transformation matrices were not written because the BOM
or document structure was locked.

System Response

The tansformation matrices have been written to a database and a job
will automatically be restarted in approximately one hour.

How to fix this error?

Release the BOM or document structure.

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message CONV117 - BOMs cannot currently be locked: Job will be restarted later ?

  The SAP error message CONV117 indicates that the system is unable to lock the Bill of Materials (BOM) for processing, which is necessary for certain operations such as conversions or updates. This error typically occurs in scenarios where multiple processes are trying to access or modify the same BOM data simultaneously, leading to a contention issue.
  Causes:
  
  Concurrent Access: Multiple users or processes are trying to access or modify the same BOM at the same time.
  Long-Running Transactions: A transaction that is taking too long to complete may hold the lock on the BOM, preventing other processes from accessing it.
  System Performance Issues: High system load or performance bottlenecks can lead to delays in processing, causing locks to be held longer than expected.
  Database Locking: Database-level locks may be in place due to other operations, which can prevent the BOM from being locked.
  
  Solutions:
  
  Wait and Retry: The error message indicates that the job will be restarted later. Often, simply waiting for a few moments and allowing the system to retry can resolve the issue.
  Check for Long-Running Jobs: Use transaction codes like SM37 to monitor background jobs and identify any long-running jobs that may be holding locks on the BOM.
  Reduce Concurrent Access: If possible, limit the number of concurrent processes that access the BOM. This may involve scheduling jobs to run at different times or coordinating with users.
  System Performance Tuning: Investigate system performance and optimize it if necessary. This may involve checking for resource bottlenecks, optimizing database performance, or increasing system resources.
  Lock Analysis: Use transaction SM12 to check for existing locks on the BOM. If you find locks that are no longer needed, you may be able to release them (with caution).
  Consult SAP Notes: Check the SAP Support Portal for any relevant notes or patches that may address this issue, as it could be a known problem with a specific solution.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM12 (Lock Entries), and SM21 (System Log) for troubleshooting.
  SAP Documentation: Review SAP documentation for BOM processing and locking mechanisms to understand how locks are managed in the system.
  User Training: Ensure that users are trained on best practices for accessing and modifying BOMs to minimize contention.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.