Show TOC

System SettingsLocate this document in the navigation structure

In transaction SPRO, navigate to the Customizing activity Configure the Framework under Start of the navigation path Cross-Application Components Next navigation step Processes and Tools for Enterprise Applications Next navigation step SAP Geographical Enablement Framework End of the navigation path.

The following list provides configuration information:

  • GIS DB Impl. Class: Enter implementation class responsible for the geometry database access; it must implement the interface IF_GEF_GDB_SERVICE. The default implementation class provided by SAP is CL_GEF_GDB_HANA. This class is responsible for access to the SAP HANA databases, which allow further access to geometry data in SAP HANA Spatial. You may replace this with your own implementation class if you are using a different way to access your database, however, SAP does not recommend replacing standard classes for access to the geometry database.

  • DB Conn. Name: Enter name of the connection to the geometry database. This points to the database being used - SAP HANA as either the primary database or as a standalone secondary HANA database (sidecar).

  • Maximum Record Count: Used to set the maximum number of records that will be returned by a single query and applies to all geo objects in the system. You can also override this number for individual geo objects.

  • Schema Name in GDB: Enter name of the schema where the geometry data is stored. If you create your own database tables in HANA that contain geometry data, you need to maintain the name of your schema.

  • GDB View Name: Enter name of the SAP HANA database view that contains all the geometry records.

  • Database Prefix: Used to append a geometry type (point, line or polygon) to construct a database table name where the records of that geometry type is stored; also used to construct the complete view name. (Optional field)

  • GDB SRS ID: Refers to the Geometry Database Spatial Reference ID.

    Note Each database table can use only one SRS ID. If you need to save your data in a different SRS ID than the default one, then please be advised that it might not be part of the standard SAP HANA delivery. You may need to install a deployment unit which corresponds to the new SRS ID separately.

  • Ent Search Max Count: Refers to the maximum number of records that will be returned by a single enterprise search.

Note

Please be mindful of the following:

  1. Provide the name of the DB connection you created earlier in the Configuring SAP HANA DB Connection section.
  2. Replace the default schema name with your own schema, where the tables and views reside, only if necessary.
  3. Replace the prefix of the tables and views with your own prefix, only if necessary.
  4. Replace the name of the view where all the spatial information can be retrieved, only if necessary.
  5. Ensure that the system SRID differs from the default SRID.

During the operation, the framework sends all read requests to the system view, and modify requests to the system tables (depending on the geometry type). With the default settings, the system views and tables can be located as per the following list:

  • System view: SAP_GEF.sap.gef.data::gef_geom_3857.geom_all

  • System tables:
    • SAP_GEF.sap.gef.data::gef_geom_3857.point
    • SAP_GEF.sap.gef.data::gef_geom_3857.line
    • SAP_GEF.sap.gef.data::gef_geom_3857.polygon

All tables and views use SRS 3857 for the spatial data inside. During configuration, please note the following:

  • All geometry attributes are case sensitive.
  • Replace the default schema name with your own schema, where the tables and views reside, only if necessary.
  • If overwritten, all read requests will be redirected to a new view; however, modifying requests will still operate on system tables.

In the schema SAP_GEF, a sequence object "SAP_GEF"."sap.gef.data::gef_seq" is available. This object is used to allocate a unique ID to all the new geometric records, and therefore, not subject to Customizing. There's no need to configure the sequence unless records in the tables are manipulated directly, for example, importing existing spatial data.