Creating an Architectural Structure 

Use

In order for you to be able to use the architectural view in real estate processes, you have to create architectural objects. You can create architectural objects only in a fixed structure, the architectural hierarchy. This structure is similar to that for the master data in the usage view (such as, business entity ® building ® rental unit). Below is a description of how to create an architectural hierarchy.

Prerequisites

Make the following settings in Customizing:

·        Maintain architectural object types

·        Define allowed object type hierarchy

To do this, choose the following path:

SAP Customizing Implementation Guide ® Flexible Real Estate Management ® Master Data ® Architectural View ® Architectural Object Type ® Create Architectural Object Types andDefine Allowed Object Type Hierarchy 

 

Procedure

On the SAP Easy Access screen, choose:

Accounting ® Flexible Real Estate Management ® RE Navigator ® Architectural Object ®  with the quick info text Create

For an accessible version of Create Architectural Structure, use transaction REBDAO.

 

 It is also very important that you read the procedure for Creating an Architectural Object. Keep in mind that both of these procedures have to be performed in the same dialog.

       1.       

       2.      Always create the object on the highest level of the hierarchy first.

Any object type can be defined as being the top-level object of the hierarchy. You define the top-level object in Customizing (see Prerequisites). We recommend you use one of the following object types as the top-level object:

¡        Locality

¡        Architectural building

¡        Land from an architectural perspective

¡        Floor

¡        Wing of building

¡        You can choose your own names for your object types.

       3.      To add a new architectural object to an architectural hierarchy, choose  with quick info text Create, and then enter the architectural object type.

       4.      You have to link each object with the object that is just above it in the hierarchy (General Data tab page). 

Any given architectural object can only be entered once in the hierarchy, or it has to be time-dependent (with different valid-from and valid-to dates); in other words an object can only be used once in the hierarchy for a given time period.

An architectural object type can only be used once in any one level of the hierarchy. The following hierarchy is not possible:

Building – Floor – Building section – Floor – Space

Architectural hierarchies are company-code-independent.

You can link multiple usage objects within a company code with one architectural object, and on the other hand, you can link multiple architectural objects with one usage object.                                

 

Example

This overview figure shows an example of an architectural structure.