How To Fix MJ079 - Field selection for & locked by another user

SAP Error Message - Details

• Message type: E = Error

• Message class: MJ - Field Selection

• Message number: 079

• Message text: Field selection for & locked by another user

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 MJ079 - Field selection for & locked by another user ?

  The SAP error message MJ079, which states "Field selection for & locked by another user," typically occurs when a user attempts to access or modify a field in a transaction that is currently locked by another user. This can happen in various SAP modules, particularly in the context of material management or inventory management.
  Cause:
  
  Concurrent Access: Another user is currently editing the same data or field, which causes a lock on that field.
  Transaction Locking: SAP uses a locking mechanism to prevent data inconsistencies. If a user is in the middle of a transaction that involves the same field, it will be locked for other users.
  Long-running Transactions: If a transaction takes a long time to complete, it can hold locks longer than expected, leading to this error for other users trying to access the same data.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user to finish their transaction. Once they are done, the lock will be released, and you can try again.
  Identify the Lock: Use transaction code SM12 to check for locks. You can see which user is holding the lock and what object is locked. If necessary, you can contact that user to coordinate access.
  Release the Lock: If you have the necessary authorizations, you can manually release the lock in transaction SM12. However, this should be done with caution, as it may lead to data inconsistencies if the other user is still working on the data.
  Check for Background Jobs: Sometimes, background jobs can also hold locks. Check transaction SM37 to see if any background jobs are running that might be causing the lock.
  Review User Roles and Authorizations: Ensure that users have the appropriate roles and authorizations to access the fields they need without causing conflicts.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM37: To check background jobs.
  SE11: To view data dictionary objects and field definitions.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation for field selection and locking mechanisms to understand how they work and how to manage them effectively.
  
  If the problem persists or if you frequently encounter this error, it may be beneficial to consult with your SAP Basis team or system administrator for further investigation and resolution.