Gisconnect configuration data are stored in the GIS data dictionary and are therefore fully
version managed. Optionally, the data can also be uploaded into the CASE datastore.
Once the objects are configured, access to SAP R/3 data is transparent to the GIS users. Options
to view the SAP IU3 pages are accessed from the Smallworld editors as illustrated in the
following figure.
Figure 2. GIS and SAP R/3 Data Viewable from Smallworld Editors
The configuration process indicates which field will be viewable from the GIS as well as the
rules for updating the information. Some fields can be updated only from the GIS, and others
can be updated only from SAP IU3.
The second step was to create the proper index between the two systems for the configuration to
work. Disconnect uses the SAP R/3_ID field to link objects together. Therefore, a strategy for
building these links needed to be developed. The data sets being used for this project had several
origins.
The strategy used at GPU would capitalize on a unique numbering system used in GPU’S legacy
GIS. An attribute called “pole_key” would allow the indexing process to search for
corresponding objects in both systems. As the GIS data were migrated from GFIS to
Smallworld, the pole_key was retained to keep this relationship intact.
As data were populated in SAP, this same strategy was used to retain these relationships. As
objects were populated in both systems, internal numbers were assigned and used to establish the
index that Disconnect would use to link up the information.
