Technical Documentation : Connectors : Adding an SAP BW (Safyr) Connection
Was this helpful?
Adding an SAP BW (Safyr) Connection
Prerequisites
Note:
  • To connect Zeenea to SAP BW, Zeenea provides a collaborative solution with Silwood Technology and his Safyr software. This integration must be validated with our customer services.
  • You can find a link to the configuration template in Zeenea Connector Downloads.
Supported Versions
The SAP BW connector is compatible with SAP BW.
Installing the Plugin
The Silwood Safyr plugin can be downloaded here: Zeenea Connector Downloads
ATTENTION:
  • Updating the connector to version 3.0.0 from a previous version requires a data migration for the "Dataset" type objects representing Query. Please contact customer service to assist you in this migration.
  • Updating the connector to version 3.1.1 from a previous version impacts data processes identification and requires a manual deleting of existing data processes. If you documented your SAP BW data processes, please contact customer service to assist you in this migration.
For more information on how to install a plugin, please refer to the following article: Installing and Configuring Connectors as a Plugin.
Declaring the Connection
Creating and configuring connectors is done through a dedicated configuration file located in the /connections folder of the relevant scanner. The scanner frequently checks for any change and resynchronises automatically.
In order to establish a connection with SAP BW, you need to fill out the following parameters in the dedicated file:
Parameter
Expected value
name
The name that will be displayed to catalog users for this connection.
code
The unique identifier of the connection on the Zeenea platform. Once registered on the platform, this code must not be modified or the connection will be considered as new and the old one removed from the scanner.
connector_id
The connector type to use for the connection. Here, the value must be safyr-sap and this value must not be modified.
input.folder
The complete path to the folder containing files from the Silwood Safyr extraction
input.display_name
(Deprecated) To choose between the "Physical" and the "Logical" name of the objects
input.dataset_display_name
To choose between the "Physical" and the "Logical" name of datasets
input.field_display_name
To choose between the "Physical" and the "Logical" name of fields
input.flatten_attributes
Flatten the attribute's characteristics as new fields (true or false). Default value is true.
lineage
To activate the lineage feature for cubes and queries
Note: A template of the configuration file is available in this repository.
Data Extraction
To extract information, the connector identifies metadata from the JSON files of the Silwood Safyr extraction.
Collected Metadata
Inventory
Will collect the list of objects accessible by the user.
Lineage
The connector is able to reconstruct the lineage of cubes referenced in cubes as well as the lineage representing the cubes that are used by the queries.
Dataset
A dataset can be the following SAP BW object: Data Store Object, Advanced Data Store Object, HANA Composite Provider, Info Sources, Data Sources, Cube, Query, or HANA Calculation View.
  • Name
  • Source Description
  • Technical Data:
    • Type
    • Metadata Changed
    • Physical Name
    • Logical Name
Field
Dataset field.
  • Name
  • Source Description
  • Type
  • Can be null: Depending on field properties
  • Multivalued: Depending on field properties
  • Primary key: Depending on field properties
  • Technical Data:
    • Technical Name
    • Native type
    • Type: Unit, Measure, Dimension or Characteristic
    • Size
    • Data Element
    • Metadata Changed
    • Physical Name
    • Logical Name
Unique Identifier Keys
A key is associated with each item of the catalog. When the object comes from an external system, the key is built and provided by the connector.
More information about unique identification keys in this documentation: Identification Keys.
Object
Identifier Key
Description
Dataset
code/asset type/dataset name
- code: Unique identifier of the connection noted in the configuration file
- asset type: Asset type as defined by Safyr
- dataset name
Field
code/asset type/dataset name/field name
- code: Unique identifier of the connection noted in the configuration file
- asset type: Asset type as defined by Safyr
- dataset name
- field name
Data Process
code/reference/asset type/dataset name
- code: Unique identifier of the connection noted in the configuration file
- asset type: Asset type as defined by Safyr
- dataset name: Dataset name that is linked
Last modified date: 11/28/2025