How To Fix RIS_MESSAGES021 - Include components are not locked in various requests

SAP Error Message - Details

• Message type: E = Error

• Message class: RIS_MESSAGES - Message Class of Repository Information System

• Message number: 021

• Message text: Include components are not locked in various requests

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 RIS_MESSAGES021 - Include components are not locked in various requests ?

  The SAP error message RIS_MESSAGES021 typically indicates that there are issues related to the inclusion of components in various requests, specifically that the components are not locked. This can occur in the context of transport requests or when working with the SAP Change and Transport System (CTS).
  Cause:
  
  Uncommitted Changes: The components you are trying to include in a transport request may have uncommitted changes or are in a state that does not allow them to be locked.
  Multiple Users: If multiple users are trying to modify the same object or component simultaneously, it can lead to locking issues.
  Transport Request Status: The transport request may be in a status that does not allow for the inclusion of new objects or components.
  Authorization Issues: The user may not have the necessary authorizations to lock the components or to include them in the transport request.
  
  Solution:
  
  Check Lock Status: Verify if the components are currently locked by another user. You can use transaction code SM12 to check for locks and release them if necessary.
  Commit Changes: Ensure that all changes to the components are saved and committed before trying to include them in the transport request.
  Check Transport Request Status: Make sure that the transport request is in the correct status (e.g., "Modifiable") to allow for the inclusion of new components.
  User Authorizations: Ensure that the user has the necessary authorizations to perform the actions required. This may involve checking roles and permissions in transaction PFCG.
  Use Transport Organizer: Use the Transport Organizer (transaction SE09 or SE10) to manage transport requests and ensure that components are properly included.
  Restart the Process: Sometimes, simply restarting the process or logging out and back into the system can resolve temporary locking issues.
  
  Related Information:
  
  Transaction Codes:
  
  SE09/SE10: Transport Organizer
  SM12: Display and Delete Locks
  SE03: Transport Organizer Tools
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message. You can search for notes in the SAP Support Portal.
  Documentation: Review SAP documentation related to the Change and Transport System for best practices and troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.