How To Fix S_UNIFIED_CON_API164 - Workbench Error: Locked by author for customizing &1

S_UNIFIED_CON_API164 - Overview

• Message type: E = Error

• Message class: S_UNIFIED_CON_API - Messages for API for Unified Connectivity

• Message number: 164

• Message text: Workbench Error: Locked by author for customizing &1

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 S_UNIFIED_CON_API164 - Workbench Error: Locked by author for customizing &1 ?

  The SAP error message S_UNIFIED_CON_API164 indicates that a workbench object is locked by the author for customizing. This typically occurs when a user is trying to modify or transport a workbench object (like a program, function module, or table) that is currently locked by another user who is making changes to it.
  
  Cause:
  
  Object Locking: The object is locked because the author (the user who created or last modified the object) is currently editing it or has it locked in a transport request.
  Transport Request: The object may be part of a transport request that is currently being processed or has not been released.
  User Session: The user may have an active session that has not been properly closed, leaving the object in a locked state.
  
  
  Solution:
  
  
  Check Lock Entries:
  
  Use transaction code SM12 to check for lock entries. You can filter by the user ID or the object name to see if the object is locked