SAP HANA

The SAP HANA tool (nistor-tool-sap-hana, tool id sap_hana) gives SAP tables a place in the lineage graph. It reaches no SAP system: it has no connection, no executor, no router and no settings. It owns the SapHanaTable node type and the SQL helpers that find SAP table references, which the MicroStrategy tool uses when it reads cube SQL views.

Its README calls it an "identity-only tool"; the package carries no development-status classifier (see the overview).

What Nistor reads#

Nothing from SAP. For each cube SQL view that the MicroStrategy tool reads, Nistor finds the FROM and JOIN references whose schema looks like SAP's and adds one SapHanaTable node for each:

• _SYS_BIC, _SYS_BI0 and other _SYS_ schemas: HANA calculation views and BW InfoCubes;
• SAP followed by letters or digits, such as SAPABAP1 and SAPSR3: ECC and S/4HANA tables;
• any schema whose name contains HANA or BW.

The node ids look like SapHanaTable_PRD_<schema>_<object>, with / and . in the object path turned into -. Only cube SQL views are read, not report SQL.

Permissions#

None. Nistor never logs in to SAP HANA, and you need no SAP credential.

Install and activate#

Installing the MicroStrategy package installs this one (nistor-tool-microstrategy requires nistor-tool-sap-hana), and the public runtime image carries both. Activate both tools. Without sap_hana active, cubes compile without their SAP sources.

Connection settings#

There are none. SAP HANA is the one integration without a connection type, so it does not appear among the types you can choose when you create a connection.

Test it#

The tool's health probe does not call anything. It always answers healthy, with the detail no connection: identity-only tool. To check that it works, compile a MicroStrategy project whose cubes read SAP tables, then look for SapHanaTable nodes upstream of those cubes in the lineage.

Limits#

• The system part of every node id is PRD, whatever SAP system the cube reads.
• Detection is by schema name. A SAP table under a schema that matches none of the patterns above is not found. A non-SAP schema whose name contains HANA or BW is taken for SAP.
• SapHanaTable nodes carry no cost: SAP HANA is licensed, not metered.

Troubleshooting#