Skip to main content
SAP

Your SAP landscapes, in the same change, incident and audit processes as the rest of IT.

SAP transport requests become Changes with approvals and segregation of duties. SAP systems become configuration items, monitoring alerts become incidents, and authorisation data becomes evidence for your authorisation concept. It covers ECC, S/4HANA on-premises and Solution Manager, as well as S/4HANA Cloud, SAP BTP and SAP Cloud ALM.

Request a demoRead the documentation

Preview, not yet field-tested. The connector agent and every collector have been tested with SAP-shaped sample data only; no live SAP system, HANA database or Cloud ALM tenant has been connected in a customer environment yet. Pilot it in a test tenant against a non-productive landscape first.

What you can do

Transport control that survives the end of Solution Manager.

Ingest, don't fetch

TENSOR never opens an RFC connection into your network. A small connector agent on your own premises reads SAP and pushes signed data out, and your RFC and HANA credentials stay on that machine. Only Cloud ALM is called directly, read-only, through OAuth.

Every transport becomes a Change

A transport first seen in a development system becomes a Normal Change, once. Release and import facts move it forward: released, imported to QA, imported to PROD. The import into production closes the Change through the change state machine, and the post-implementation review gate still applies.

Drift is recorded, not hidden

When SAP moves a transport further than its Change allowed, such as a release before approval or an import with no linked Change, TENSOR records the fact, raises a health event and shows a drift card on the Change instead of pretending it didn't happen.

Object-level collision detection

TENSOR compares the object lists of every in-flight transport that has not reached production. Two transports touching the same object show a collision card on the Change and in the change calendar's SAP view. Overriding one takes the force-import right and a written annotation.

Imports scheduled in TENSOR, executed in STMS

Plan imports into DEV, QA and PROD on the Change, with target system, sequence and maintenance window. Scheduling outside a covering window needs an audited justification. The Basis team imports in STMS and confirms in TENSOR, which timestamps the import and checks separation of duties: the developer can neither approve nor import their own transport.

Alerts, HANA and EarlyWatch next to the CI

CCMS and Solution Manager alerts create incidents linked to the SAP system CI, and repeats raise an occurrence count instead of duplicates. HANA snapshots flag stale backups and full tablespaces, and uploaded EarlyWatch Alert reports are kept as evidence against the SAP system they cover.

Authorisations against a risk catalogue

SAP role assignments are checked against a curated catalogue of 53 risky role combinations across procure-to-pay, finance, order-to-cash, user administration, Basis, development and HR. Violations are listed per connection, and the catalogue is included in the Berechtigungskonzept export.

SolMan history, sealed and searchable

Import ChaRM change documents and ITSM tickets from a Solution Manager CSV export. Every import starts with a dry run, and a confirmed batch is sealed with its SHA-256 hash in the audit chain. Migration mode tracks the parallel run, with a cutover checklist computed from live data rather than manual ticks.

Compliance relevance

How this connects to regulation

MaRisk
AT 7.2 — Separation of duties in change: transport SoD rules, separate schedule and confirm rights, and an audited force-import right.
DORA
Art. 8 — SAP systems, clients and HANA databases as versioned CIs.
DORA
Art. 17 — CCMS alerts create incidents with SAP as source, linked to the affected SAP system CI.
Common questions

What SAP Basis and change managers ask.

See TENSOR running on your own estate.

30 minutes, screen-shared, no slides. Bring the process you are least sure we handle and we will start there.