- The Architectural View is an optional view that is company code independent.
- It provides an architectural structure that represents the physical structure of a building.
- It is a user-defined hierarchical structure that is named according to an organization's specific nomenclature for the real estate objects they wish to represent, such as buildings, parts of a building, wing, floors, parts of a floor, rooms in a building, rooms on a floor, tower structures, linear structures, land parcels etc.
- These real estate objects are referred to as Architectural Objects (AO).
- The Usage View (UO) is company code dependent.
- It is oriented top down with the Business Entity (BE) as the top node. Buildings (BU) and Land (PR) are subordinate objects that are further sub-divided into Rental Objects (RO), and which consist of Pooled Spaces (PS), Rental Spaces (RS), and Rental Units (RU).
- All real estate objects that make up this view are controlling objects. This means that both costs and revenues can be posted to these real estate objects.
- The Usage View is mandatory and cannot be changed or realigned.
These two views will be assigned to each other. There will be a 1:1 assignment between the Site (AO view) and the Business Entity (UO view), as well as between the respective land and building real estate objects. The usage objects (BE, BU, and PR) will be created from the existing / previously created architectural objects (Site, Land, and Building). The UO's will adopt the measurements of the assigned architectural objects (AO's). This will be done by the system copying the measurements from the architectural objects to the usage objects.