To add a geographical map to your fact sheet, you can enhance the fact sheet in the following ways:
By adding a new facet for a map that displays geographical information for a certain entity
By changing the assignment of an existing map on the facet, that is, by assigning the address information to a different entity
Each map contains geographic locations represented by markers (pins). You can navigate to these markers to display further information.
You can include geographical maps by assigning them to one of the following levels:
Root-Entity Level: The address data is taken from the root node of the underlying search model. For more information see Example: Single Geographic Information on Root-Entity Level
Level of a Subordinate Entity: For more information see Example: Single Geographic Information on Sub-Entity Level
The most relevant vocabulary for the annotation of geographical maps is the file UI.xml. It contains the following annotation terms:
A tag which indicates that the annotated term is displayed in a map.
A tag which references one GeoLocationType that contains one set of geographic information.
A GeoLocationType includes a set of attributes which define the location of the entity, such as longitude and latitude. The term UI.GeoLocation can be defined for any fact sheet entity.
Fact sheet entities are defined by the underlying search model, and thus by an OData service meta model. Each fact sheet entity can have one or more sets of geographic information. For example, the entity Article can have multiple sets of geographic information, each of them related to one store selling the article.
In the annotation file, each entity can have not more than one UI.GeoLocation term, which is used in an Annotation Target.
Geographic information can be represented as different data types in fact sheet annotation files. These data types are defined in the vocabulary:
The geographic information is taken from an address field.
The geographic information is decoded in longitude and latitude.
In fact sheets, longitude and latitude information is used to display markers (pins) on the map. If you insert an address tag in the annotation file, address information is displayed additionally.
You have enhanced the search model fields with fields representing latitude and longitude.
To be able to display address data you must have enhanced the search model or the OData service with a field containing the formatted address string.
You have to provide the address data in the back end, where you can define country-specific address formatting.
The back-end application related to the fact sheet supports and stores geographic data which can be used to display geolocations on a map.
The URLs of the map provider services have been maintained in SAP Visual Business in the back-end system. The OData service VBI_APPL_DEF_SRV returns the URLs of the services for a given map provider.
You have maintained the Customizing settings for SAP Visual Business in Customizing for SAP NetWeaver under.
For more information about the installation and configuration of SAP NetWeaver Visual Business, see the SAP Help Portal at http://help.sap.com under .
Fact Sheets do not support the determination of coordinates for geolocations during the data processing. The data must be delivered by the back-end system.
To include a geographical map displaying geolocation information, proceed as follows:
In the annotation file, search for the facets definition area, <Annotation Term="UI.Facets">.
Add a new record tag following the examples:
Adapt the label to your requirements using an OTR text.