Do you have any question about this error?
Message type: E = Error
Message class: REBDAO -
Message number: 035
Message text: Architectural object type &1 does not exist
The architectural object type you entered does not exist.
You cannot assign the architectural object type.
Create the object type in Customizing in the
<DS:SIMG.REFXV_TIVBDAROBJTYPE>Create Architectual Object Types</>
activity.
Then add the architectural object type to your architectural hierarchy
in the <DS:SIMG.REFXV_TIVBDARNODE>Define Allowed Object Type Hierarchy
</> activity, and assign measurement types to it in the
<DS:SIMG.REFXV_TIVBDMEASAO>Measurement Types</> activity.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
REBDAO035
- Architectural object type &1 does not exist ?The SAP error message REBDAO035 indicates that the system is unable to find a specified architectural object type, which is represented by the placeholder
&1
. This error typically occurs in the context of SAP Real Estate Management (RE) or similar modules where architectural objects are used.Cause:
- Non-Existent Object Type: The specified architectural object type does not exist in the system. This could be due to a typo in the object type name or the object type not being created in the system.
- Configuration Issues: The system may not be properly configured to recognize the architectural object type. This could happen if the necessary customizing settings have not been completed.
- Authorization Issues: The user may not have the necessary authorizations to access the architectural object type.
- Transport Issues: If the object type was recently transported from another system, there may have been issues during the transport process that caused it not to be created properly.
Solution:
- Check Object Type: Verify that the architectural object type specified in the error message exists in the system. You can do this by checking the relevant configuration settings in the SAP system.
- Create Object Type: If the object type does not exist, you may need to create it. This typically involves customizing settings in the SAP system.
- Review Configuration: Ensure that all necessary configuration steps for the architectural object type have been completed. This may involve checking the customizing settings in transaction SPRO.
- Authorization Check: Ensure that the user has the necessary authorizations to access the architectural object type. You may need to consult with your security team to verify this.
- Transport Check: If the object type was supposed to be transported from another system, check the transport logs for any errors and ensure that the transport was successful.
Related Information:
SPRO
for configuration, SE11
for data dictionary objects, or SE80
for object management.If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or technical team for further investigation.
Get instant SAP help. Start your 7-day free trial now.
REBDAO034
Architectural object of type &1 and number &2 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
REBDAO033
Subordinate architectural objects exist without deletion flag (no.: &1)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
REBDAO036
Hierarchy entered is not unique
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
REBDAO037
Entry does not exist
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.