Hierarchy

⤷

⤷

IMG Activity
ID | SIMG_REFXES | Define Hierarchical Location Structure |
Transaction Code | S_EEI_69000029 | (empty) |
Created on | 20120516 | |
Customizing Attributes | SIMG_REFXES | Define Hierarchical Location Structure |
Customizing Activity | SIMG_REFXES | Define Hierarchical Location Structure |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_REFXES |
Use
In this Customizing activity, you define various location structures. Location structures are used to uniquely identify parcels or land registers for different purposes.
In Spain, you use the ES Hierarchical Location Structure to create the hierarchy for Spain.
Requirements
Standard settings
Activities
You must first define the location structure ID (ES for Spain) and its name on the Hierarchical Location Structure screen, and specify the number of levels for the hierarchy and the names of each level as follows:
- Country
- Province
- Municipality
You must also define the type of real estate object on the Allowed Hier. Location Structures per Object Type screen, and then you enter all the possible locations for each defined hierarchy level on the Hierarchical Locations in Location Structure screen. In Spain, the code system is built up as follows:
- A 2-digit number (for example 01) represents the province
- A 4-digit number (for example 0101) represents the municipality
Then, you assign the already defined hierarchical locations to one another and assign a key for each location on the Assignment of Hierarchical Locations in Location Structure screen. 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. The key of the hierarchical location must not contain any spaces.
If the assignment changes due to restructuring of individual hierarchical locations, you can assign new keys (on the Assignment of Hierarchical Locations in Location Structure level) or other locations to an existing key. However, if the key itself changes, then you have to change the master data.
Example
Business Attributes
ASAP Roadmap ID | 207 | Establish Reporting |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
SIMG_REFXES | ES | Spain |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_REFXES | 0 | PEN0000001 | Real Estate Localization |
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 | 20120516 |
SAP Release Created in | 607 |