SAP ABAP IMG Activity REFXVC_TIVBDLOCSYS (Define Hierarchical Location Structure)
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 REFXVC_TIVBDLOCSYS Define Hierarchical Location Structure  
Transaction Code S_AEN_10000762   (empty) 
Created on 20050323    
Customizing Attributes REFXVC_TIVBDLOCSYS   Define Hierarchical Location Structure 
Customizing Activity REFXVC_TIVBDLOCSYS   Define Hierarchical Location Structure 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name REFXVC_TIVBDLOCSYS    

Use

In this activity you define various location structures. Location structures are used to uniquely identify parcels or land registers for different purposes.

In Germany, you use these settings to create, at the minimum, the following two hierarchies:

Requirements

Standard settings

Activities

Enter an ID and a name for your location structure.

Specify the number of levels for the hierarchy and the names of each level.

For each location structure, you also specify the following:

  • Allowed Hierarchical Location Structures per Object Type
    Specify if assignment of the object type to this location structure is mandatory. Specify if this is the standard location structure.
  • Hierarchical Locations in Location Structure
    Here you enter the possible locations for each defined hierarchy level.

    Example:
    You defined these three levels for the location system:
    1 - Country
    2 - Region
    3 - City
    Then you enter all countries, regions and cities that you need in your system.

  • Assignment of Hierarchical Locations in Location Structure
    You assign the already defined hierarchical locations to one another and assign a key for each location. You can then assign only this key to a parcel or a public register in the application.

    You are not required to assign the keys systematically, but it is a good idea. The key of the hierarchical location is not allowed to contain any spaces.
    If the assignment should change due to restructuring of individual hierarchical locations, it is not a problem to assign new keys (at the level Assignment of Hierarchical Locations in Location Structure) or to assign other locations to an existing key. However, if the key itself should change, then you have to change the master data.

Example

You defined the following locations at the given level:

Level 1 - Country:
DE - Germany
CH - Switzerland
US - USA

Level 2 - Region:
D05 - North Rhine-Westphalia
D10 - Bavaria
CH01 - Basel
CH02 - Tessin
US01 - Michigan
US02 - Florida

Level 3 - City:
D-K - Cologne
D-D - Duesseldorf
D-M - Munich
CH-B - Basel
CH-LG - Lugano
US-CH - Chicago
US-M - Miami
US-OL - Orlando

Assignment of Hierarchical Locations in Location Structure:
For the assignment of hierarchical locations in the hierarchy, you have to assign a unique key to each hierarchical location.
A hierarchical location cannot be used in object unless it has a key here.

DE-K Cologne DE D05 D-K
DE-D Duesseldorf DE D05 D-D
DE-M Munich DE D10 D-M
CH-B Basel CH CH01 CH-B
CH-LG Lugano CH CH02 CH-LG
US-CH Chicago US US01 US-CH
US-M Miami US US02 US-M
US-OL Orlando US US02 US-OL

In this case, you would assign the location DE-K to a parcel in Cologne. It is then clearly visible, both in master data processing and in reports, that this parcel has the following location:

- Country:     Germany
- Region:     North Rhine-Westphalia
- City     Cologne

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 REFXVC_TIVBDLOCSYS 0 AEN0000002 Land Use Management 
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
VC_TIVBDLOCSYS C - View cluster SM34  
History
Last changed by/on SAP  20120627 
SAP Release Created in 600