Hierarchy
EA-FIN (Software Component) EA-FIN⤷
RE-FX (Application Component) Flexible Real Estate Management⤷
RE_CA_CU (Package) RE: Customizing (IMG) and Area Menu
IMG Activity
| ID | REFXV_TIVBDAROBJTYPE | Create Architectural Object Types |
| Transaction Code | S_ALN_01000778 | (empty) |
| Created on | 20020129 | |
| Customizing Attributes | REFXV_TIVBDAROBJTYPE | Process Architectural Object Types |
| Customizing Activity | REFXV_TIVBDAROBJTYPE | Process Architectural Object Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | REFXV_TIVBDAROBJTYPE |
Use
In this step, you define your allowed architectural object types.
By defining architectural object types, you define the different, distinct architectural levels you wish to have in the system and their relationship to each other. An architectural object of the type Building and an architectural object of the type Room are the same object from a technical perspective, and both are processed in the same "Process Architectural Object" master data dialog. However, you can make your settings so that different fields and screens are available for rooms than for buildings (Screen Sequence field). In addition, you can specify, for example, that rooms can only be created as subobjects of buildings.
@0S@ We recommend that you enter only a small number of object types that you really need. For example, you should avoid creating different architectural object types for different types of rooms. You can make this kind of distinction instead at the function of the architectural object level.
Requirements
The same attributes exist in the architectural view as in the usage view, which enables you to derive the usage view from the architectural view, if you want. For this to be possible, you have to assign the master data of business entities, land, and buildings in the usage view to the corresponding architectural object types.
Standard settings
Activities
1.Assign the master data of business entities, land, and buildings in the usage view to architectural object types by setting the appropriate indicator (for example, AO = BU).
2. Top Level
You have to set the Top Level indicator for the object type that will be the highest node in the architectural hierarchy. To make it possible to reflect the architectural view in the usage view, you have to choose an object type that is assigned to the business entity as the Top Level node. It is possible to define more than one architectural object type as the Top Level.
@0S@ Assume you want a particular object type in the architectural view (such as a building) to be available both as a Top Level node and as a subordinate object type. In that case, you have to create two different object types (for example, building 1 as Top Level node and building 2 as subordinate node).
Reason: If both the "locality" and "building" architectural object types are designated as Top Level nodes, then it is not possible to insert a building in the hierarchy below the locality.
3. Number Assignment
@0S@ Set the Global NA (global number assignment) indicator, if you want number assignment for the object type to be unique, regardless of the hierarchical level. Number assignment is automatically global for the top-level object. However, if you create a building within the locality, the number of the building only has to be unique within the locality. If you have two localities, A1 and A2, then building B1 can exist in both of them. If instead you also want the building number to be unique, then set the Global NA indicator for the Building. The system then ensures that each building number is unique in the entire client, across all localities.
4. In the HiLev.Obj.Type (higher-level object type) field, you can enter object types for which you do not want global number assignment. Here you enter for these objects at which higher level in the hierarchy number assignment should be unique. For rooms, for example, this could be the floor, the building or the locality.
5. Screen Sequence
SAP supplies a standard screen sequence. You can define additional screen sequences (for instance per architectural object type) in this IMG activity.
Example
@0S@ The actual hierarchical relationship between architectural objects with different object types is not actually specified until you create their master data. However, in Customizing you can already define the relationships that should be possible in the Define Allowed Object Type Hierarchy IMG activity. Examples of these relationships are:
Building # Wing of Building - Floor - Room
Building # Floor - Wing of Building - Room
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | REFXV_TIVBDAROBJTYPE | 0 | ALN0000034 | Basic Data |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TIVBDAROBJTYPE | V - View | SM30 |
History
| Last changed by/on | SAP | 20030429 |
| SAP Release Created in | 110 |
