SAP BusinessObjects lineage configuration

Connect to SAP BusinessObjects to scan metadata and display it on lineage.

This is a technology preview and is not yet supported for use in production environments.

Supported SAP BusinessObjects versions

  • SAP BusinessObjects BI Platform 4.3 Support Pack 4

Processed metadata

The following SAP BusinessObjects metadata is processed and displayed on lineage:

  • Documents that use UNX universes as their data provider
  • Single-source data foundations
  • Database connections (JDBC, ODBC)
  • Report elements, except custom elements
  • Business objects (dimensions, measures, attributes) and their definitions that use pure SQL
  • Spreadsheets

Limitations

The following data is not processed:

  • Data sources of data providers other than UNX universe, including UNV universes or files
  • Multisource-enabled data foundations
  • @Functions, except @Aggregate_Aware
  • Filter business objects
  • Custom report elements
  • Free-hand SQL statements

Creating a metadata import asset

Data source connection

To connect to the data source from which you want to import lineage metadata, you need to select a data source definition and a connection. You can create them before you start creating the metadata import, or you can create them when you create and configure the metadata import asset.

Data source definition

Select SAP BusinessObjects as the data source type.

Connection

For connection details, see SAP BusinessObjects connection.

Connection mode

You can connect to SAP BusinessObjects by using one of the following connection modes:

Include and exclude lists

You can include or exclude documents based on their ID, name or a local file path. The values that you provide are evaluated as regular expressions.

Limitation
When you provide the local file path as a regular expression in the include filter, it can't contain right-side wildcard characters, for example /myDocuments/.*. You can use right-side wildcard characters in the exclude filter, for example /documentsYear2025/.*. Left-side wildcards apply both to include and exclude filters for the file path, for example .*/Document2025.

Assets which are added later in the data source will also be included or excluded if they match the conditions specified in the lists.

Example values:

  • 2413
  • myDocument
  • Document.*2025
  • mySampleProjects/testFolder/firstDocument
  • .*/testFolder/firstDocument

External inputs

If you want to add the ODBC connection definitions that you use, you can optionally add the connection definition file in a .zip file as an external input. The .zip file can have the following structure:

     - connection_definition
        - odbcConnectionDefinition.ini

Learn more