How To Fix BD073 - No authorization for locking/unlocking

BD073 - Overview

• Message type: E = Error

• Message class: BD - cross-application: data transfer

• Message number: 073

• Message text: No authorization for locking/unlocking

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 BD073 - No authorization for locking/unlocking ?

  The SAP error message BD073, which states "No authorization for locking/unlocking," typically occurs when a user attempts to lock or unlock an object (such as a document or a record) in the SAP system but does not have the necessary authorizations to perform that action. This can happen in various contexts, such as during data entry, processing, or when trying to manage certain transactions.
  
  Cause:
  
  Missing Authorizations: The user does not have the required authorization objects assigned to their user profile to perform locking/unlocking actions.
  Role Configuration: The roles assigned to the user may not include the necessary permissions for the specific transaction or object type.
  Profile Issues: The user’s authorization profile may not be updated or may have been incorrectly configured.
  Object-Specific Restrictions: There may be specific restrictions on certain objects that prevent the user from locking or unlocking them.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after receiving the error to check which authorization