Do you have any question about this error?
Message type: E = Error
Message class: REBD - RE - Messages - Objects
Message number: 021
Message text: No permitted object types defined
In Customizing, no object types are defined for the contract type used.
You can define which object types are permissible for the contract
type.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check your entries in the
<DS:SIMG.REFXV_TIVCNOBJ>Object Types Permitted for
Contract Type</> IMG activity.
Error message extract from SAP system. Copyright SAP SE.
REBD021
- No permitted object types defined ?The SAP error message REBD021, which states "No permitted object types defined," typically occurs in the context of SAP Real Estate Management (RE) or related modules when the system is unable to find any permitted object types for a specific operation or transaction. This can happen in various scenarios, such as when trying to create or manage real estate objects, contracts, or other related entities.
Cause:
Configuration Issues: The most common cause of this error is that the system configuration does not define any permitted object types for the operation you are trying to perform. This could be due to missing or incorrect settings in the customizing (SPRO) configuration.
Authorization Issues: Sometimes, the user may not have the necessary authorizations to access certain object types, leading to this error.
Data Inconsistencies: If there are inconsistencies in the master data or if the object types have been deleted or deactivated, this error may also occur.
Solution:
Check Configuration:
- Go to the SAP Customizing Implementation Guide (SPRO).
- Navigate to the relevant section for Real Estate Management (e.g., "Real Estate Management" -> "Basic Settings" -> "Define Object Types").
- Ensure that the necessary object types are defined and permitted for the relevant transactions.
Review Authorizations:
- Check the user roles and authorizations to ensure that the user has the necessary permissions to access the object types in question.
- Use transaction code SU53 to analyze authorization issues after the error occurs.
Data Validation:
- Verify that the object types you are trying to use are active and correctly set up in the system.
- Check for any inconsistencies in the master data that might affect the operation.
Consult Documentation:
- Review SAP documentation or notes related to the specific transaction or object type you are working with. There may be specific notes or updates that address this issue.
Contact SAP Support:
- If the issue persists after checking the configuration and authorizations, consider reaching out to SAP support for further assistance. Provide them with details of the error message and the context in which it occurs.
Related Information:
By following these steps, you should be able to identify the cause of the REBD021 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
REBD020
No permitted object types are defined
What causes this issue? No object types are defined. In Customizing, you have to define which object types are allowed for object assignment per cont...
REBD019
&1 assignment lines were deleted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
REBD022
Assignment of object type &1 to an object group is not allowed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
REBD023
The first entry is already displayed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.