SAP HANA Lineage Scanner

This is the first release of the SAP HANA lineage scanner. Capabilities are limited; we welcome feedback to guide future enhancements.

What this scanner provides

The SAP HANA scanner extracts design-time lineage from your SAP HANA database. Design-time lineage is derived from object definitions (such as views) rather than from executed queries.

In this release, you get:

Lineage from views and materialized views (how data flows between tables based on view definitions).

Design-time lineage is computed from view definitions (including materialized views). Table, column, and synonym metadata are extracted separately for the data catalog; they do not drive lineage edges by themselves.

Scanned and supported objects

Current scope

The following database objects are supported:

Views (lineage from view definitions).
Materialized views (lineage from view definitions).
Tables and columns (metadata for the data catalog).
Synonyms (metadata only; not used to compute lineage).

Query history is not supported

SAP HANA does not store executed queries in a way that supports lineage extraction, so extracting query history is not possible.

Limitations

The following are not available in this release:

Runtime or query-history lineage.
Procedures and functions.
Wildcard support in schema filters (exact schema names only).
Schemas starting with SYS or _SYS (always excluded).

Supported connectivity

Connector type: JDBC
Authentication: Username and password

SAP HANA permissions

The scanner user must have SELECT privilege on the SYS schema (or on the following system views):

SYS.TABLE_COLUMNS
SYS.TABLES
SYS.VIEWS
SYS.SYNONYMS

Work with your SAP HANA administrator to grant the required privileges. The scanner runs preflight checks to verify access before extraction begins.

Scanner configuration

All fields marked with an asterisk (*) are required.

Property Description

Property	Description
`name*`	Unique identifier for the scanner job.
`sourceType*`	Source type to be scanned. Must be `SAP_HANA`.
`description*`	Brief description of the scan (for your reference).
`oneConnections`	List of Ataccama ONE connection names for automatic pairing.
`connection.jdbcUrl*`	Full JDBC connection string for the SAP HANA database. For example, `jdbc:sap://host.example.com:30041/?databaseName=HDB`. You can add custom JDBC properties such as TLS settings directly in the URL.
`connection.username*`	SAP HANA database username.
`includeSchemas`	Schemas to include in lineage extraction. Exact schema names only; wildcards are not supported. Leave empty to include all non-system schemas.
`excludeSchemas`	Schemas to exclude from lineage extraction. Exact schema names only; wildcards are not supported.
`skipTableColumnsExtraction`	If set to `true`, table and column metadata is not written to the data catalog. Default value: `false`.
`skipViewsExtraction`	If set to `true`, view definitions are not extracted and lineage analysis is skipped. Default value: `false`.
`skipSynonymsExtraction`	If set to `true`, synonym metadata is not extracted. Default value: `false`.

name*

Unique identifier for the scanner job.

sourceType*

Source type to be scanned. Must be SAP_HANA.

description*

Brief description of the scan (for your reference).

oneConnections

List of Ataccama ONE connection names for automatic pairing.

connection.jdbcUrl*

Full JDBC connection string for the SAP HANA database. For example, jdbc:sap://host.example.com:30041/?databaseName=HDB. You can add custom JDBC properties such as TLS settings directly in the URL.

connection.username*

SAP HANA database username.

includeSchemas

Schemas to include in lineage extraction. Exact schema names only; wildcards are not supported. Leave empty to include all non-system schemas.

excludeSchemas

Schemas to exclude from lineage extraction. Exact schema names only; wildcards are not supported.

skipTableColumnsExtraction

If set to true, table and column metadata is not written to the data catalog.

Default value: false.

skipViewsExtraction

If set to true, view definitions are not extracted and lineage analysis is skipped.

Default value: false.

skipSynonymsExtraction

If set to true, synonym metadata is not extracted.

Default value: false.

Example configuration

{
   "scannerConfigs": [
      {
         "name": "sap-hana-lineage",
         "sourceType": "SAP_HANA",
         "description": "Production SAP HANA lineage extraction",
         "connection": {
            "jdbcUrl": "jdbc:sap://host.example.com:30041/?databaseName=HDB",
            "username": "ATA_LINEAGE_EXTRACTION_USER"
         },
         "includeSchemas": ["SAPHANADB"],
         "excludeSchemas": [],
         "skipTableColumnsExtraction": false,
         "skipViewsExtraction": false,
         "skipSynonymsExtraction": false
      }
   ]
}

Advanced configuration

The following optional property applies to all scanners; the default is suitable for most deployments.

Property Description

Property	Description
`inputDataCatalogFilePath`	Path to a data catalog file for initialization. If not provided, an empty catalog is used. Used only for troubleshooting or specialized integrations.

inputDataCatalogFilePath

Path to a data catalog file for initialization. If not provided, an empty catalog is used. Used only for troubleshooting or specialized integrations.

Migration from obsolete flat configuration

Applies to scan plan JSON for both Ataccama ONE and Ataccama ONE Agentic.

If you are upgrading from a previous version, the old flat configuration format with host, port, databaseName, username, and password fields is still accepted but obsolete. The old filter names includedSchemas and excludedSchemas are also still accepted.

We recommend migrating to the connection object format shown earlier. The obsolete fields will be removed in a future major release.

Was this page useful?