Do you have any question about this error?
Message type: E = Error
Message class: MJ - Field Selection
Message number: 035
Message text: Not possible to save; object cannot be included in request
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.
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.
MJ035
- Not possible to save; object cannot be included in request ?The SAP error message MJ035, which states "Not possible to save; object cannot be included in request," typically occurs when you are trying to include an object (like a transport request) in a change request or transport request that is not allowed. This can happen in various scenarios, particularly when working with customizing or development objects in the SAP system.
Causes:
- Object Type Restrictions: The object you are trying to include may not be allowed in the transport request due to its type or status.
- Transport Request Status: The transport request may be in a status that does not allow for additional objects to be added (e.g., released).
- Missing Authorizations: You may not have the necessary authorizations to include the object in the transport request.
- Object Already in Another Request: The object might already be included in another transport request, preventing it from being added to the current one.
- Development Class Issues: If the object belongs to a development class that is not transportable, it cannot be included in a transport request.
Solutions:
- Check Object Status: Verify the status of the object you are trying to include. Ensure it is not released or locked.
- Review Transport Request: Check the status of the transport request you are trying to add the object to. If it is released, you may need to create a new transport request.
- Authorization Check: Ensure you have the necessary authorizations to include the object in the transport request. You may need to contact your SAP security administrator.
- Check for Existing Requests: Use transaction SE01 or SE09 to check if the object is already included in another transport request. If it is, you may need to use that request instead.
- Development Class: If the object belongs to a non-transportable development class, you may need to change its development class to a transportable one or handle it differently.
- Use Transaction SE10: You can use transaction SE10 to manage transport requests and see if there are any issues with the requests you are working with.
Related Information:
If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
MJ034
Table & is already in the list
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MJ033
Short text for table & not found
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MJ036
Table & is not a dictionary table
What causes this issue? The table field you have specified was not recognized by the ABAP/4 Repository.System Response The system issues an error me...
MJ037
Table & is not assigned to module pool $ and dynpro group $
What causes this issue? Not all fields can be used for field selection. Dictionary tables must first be assigned explicitly to the group. You need th...
Click on this link to search all SAP messages.