How To Fix CFD_ARCHIVE029 - Custom field generation is currently locked

SAP Error Message - Details

• Message type: E = Error

• Message class: CFD_ARCHIVE - Custom Fields: Archive

• Message number: 029

• Message text: Custom field generation is currently locked

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message CFD_ARCHIVE029 - Custom field generation is currently locked ?

  The SAP error message CFD_ARCHIVE029, which states "Custom field generation is currently locked," typically occurs when there is an attempt to create or modify custom fields in the SAP system while the custom field generation process is locked. This can happen for various reasons, such as ongoing system processes, maintenance activities, or user locks.
  Causes:
  
  Ongoing Processes: Another user or process may be currently generating or modifying custom fields, which locks the generation process for others.
  System Maintenance: The system may be undergoing maintenance or updates that temporarily lock the custom field generation.
  User Lock: A specific user session may have locked the custom field generation due to an active transaction or process.
  Configuration Issues: There may be configuration settings that inadvertently cause the locking of custom field generation.
  
  Solutions:
  
  Wait and Retry: If the lock is due to another user or process, waiting for a short period and then retrying the operation may resolve the issue.
  Check Active Sessions: Use transaction codes like SM66 (Global Work Process Overview) or SM50 (Work Process Overview) to check for active sessions that might be locking the custom field generation.
  Release Locks: If you identify a session that is holding the lock and it is safe to do so, you can terminate that session using transaction SM12 (Lock Entries) to release the lock.
  System Monitoring: Check for any scheduled jobs or background processes that might be running and causing the lock. You can use transaction SM37 (Job Monitoring) to review job statuses.
  Consult Basis Team: If the issue persists, it may be necessary to consult your SAP Basis team to investigate further, as they can check system logs and configurations that might be causing the lock.
  Review Configuration: Ensure that there are no misconfigurations in the custom field settings that could lead to locking issues.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to custom field generation and locking mechanisms.
  Documentation: Review SAP documentation on custom fields and their management to ensure that you are following the correct procedures.
  User Permissions: Ensure that the user attempting to generate custom fields has the necessary permissions and roles assigned.
  
  If the problem continues after trying the above solutions, it may be beneficial to escalate the issue to SAP support for further assistance.