Convert MP2 locations.
MP2 locations are combinations of four unique fields.
MP2 examples
|
MP2 Location=WEST CAMPUS MP2 Sub-Location 1=BLDG1 MP2 Sub-Location 2=FLOOR3 MP2 Sub-Location 3=ROOM306 |
AND |
MP2 Location=WEST CAMPUS MP2 Sub-Location 1=BLDG1 MP2 Sub-Location 2=FLOOR2 MP2 Sub-Location 3=ROOM205 |
MP2 Location and MP2 Sub-Location 1 for each of these examples are exactly the same. However, if you examine the entire combination of four fields, you will see they are completely different. One is room 306 on the 3rd floor and the other is room 205 on the 2nd floor.
In HxGN EAM, you may have only one field displayed at a time, while in MP2 screens displayed all 4 fields, such as, WEST CAMPUS and BLDG1 would be displayed separately on the HxGN EAM screens. This is sufficient if you are constructing your HxGN EAM hierarchy from scratch; however, MP2 fields must be unique when converting. Here is an example of how to make the one 30 character field unique:
HxGN EAM example
WEST CAMPUS-BLDG1-ROOM306
WEST CAMPUS-BLDG1-ROOM205
There are 25 characters in the example. This is less than the 30 character maximum in HxGN EAM. MP2Sub-Location 2 has been taken out, but users may still find the proper location.
If you chose this setup your grid would look like this:
|
Prefix |
Field |
Start Position |
Length |
Suffix |
|---|---|---|---|---|
|
<blank> |
Location |
1 |
11 |
- |
|
<blank> |
MP2 Sub-location 1 |
1 |
5 |
- |
|
<blank> |
MP2 Sub-location 3 |
1 |
7 |
This would guarantee field lengths covered at least the largest location and was still less than 30 characters. The system will cut off all data at the maximum length specified.
You may also use the prefix option to convert MP2 Sub-locations 1's. Here is an example:
|
Prefix |
Field |
Start Position |
Length |
Suffix |
|---|---|---|---|---|
|
GVILLE |
- |
|||
|
<blank> |
MP2 Sub-location 1 |
1 |
5 |
This would be the end result:
GVILLE-BLDG1
GVILLE-BLDG2