SAP integration
SAP integration availability
The implementation status of every SAP integration capability, as of 24 September 2026.
Preview — not yet field-tested
The SAP integration has been built and tested with SAP-shaped fixture data only. No live SAP system, HANA database or Cloud ALM tenant has been connected in a customer environment yet. Run a pilot in a test tenant against a non-productive SAP landscape before you rely on it for production transports or audit evidence.
This table is the reference for what the SAP integration does today. Where another page in this section describes a capability, it follows this table: Available capabilities are described as working, Partially available ones carry the limitation from the Notes column, and Planned ones are not yet available.
Status as of 24 September 2026:
| Capability | Status | Notes |
|---|---|---|
| Feature flag and SAP settings pages | Available | Transports and Authorizations pages are not linked in navigation and are English only. |
| Connections: RFC records and OAuth cloud systems | Available | RFC data arrives only through the agent. |
| Connector agent: enrollment, heartbeat, signed ingest, spool | Available | Tested in fixture mode only; live mode needs customer-supplied SAP libraries. |
| Collector configuration per agent | Available | |
| System inventory to CMDB CIs | Available | The Push sample inventory button is a test aid. |
| Landscapes (DEV, QA, PROD) | Available | |
| CAB role per landscape stage | Partially available | Stored and checked by the cutover checklist; no screen to set it yet. |
| Transport auto-create, position sync, PROD close, drift | Available | |
| Transport SoD | Partially available | Developer is not approver and developer is not importer are enforced; approval-stage separation is not yet enforced. |
| Object collision detection and force import | Available | |
| Import scheduling and confirmation | Available | Import schedule panel is English only. |
| Release gating and automatic import from TENSOR | Planned | Consent-gated write-back to SAP. |
| CCMS and SolMan alerts to incidents | Available | Severity map override has no screen yet. |
| Alert acknowledgement write-back to SAP | Planned | |
| HANA status and CI update | Available | |
| BackInt job cross-reference (for example Veeam) | Planned | |
| EarlyWatch Alert evidence | Partially available | Manual upload available; agent upload planned. |
| SAP authorisations, SoD violations, 53-rule catalog | Partially available | Assignments and findings visible; SAP-to-TENSOR user mappings cannot yet be created in the UI. |
| SAP SoD catalog in the Berechtigungskonzept | Available | |
| USMM measurement and SLAW aggregation | Partially available | Collection and recording exist; scheduling runs and viewing SLAW results have no screen yet. |
| Cloud ALM bridge | Available | Tasks and events pulled; requirements by push only. |
| SolMan archive import, seal, supersede, browse, export | Available | CSV only; XLSX planned. |
| Migration mode, dashboard, cutover checklist, widget | Available | |
| SAP skills seeding | Available | |
Dedicated sap_basis_admin role | Planned | infrastructure_admin acts as Basis administrator until then. |
What the planned items mean for you today
- Release gating and automatic import. TENSOR does not hold back releases or trigger imports in SAP. The Basis team imports in SAP STMS and confirms in TENSOR; if SAP moves ahead of a Change, TENSOR records drift. See Transports and imports.
- Alert acknowledgement write-back. Acknowledging or resolving an SAP-raised incident does not clear the alarm in SAP. See Operations and evidence.
- BackInt job cross-reference. HANA status shows the BackInt tool in use, without a cross-reference to its jobs.
- Agent upload of EarlyWatch Alert reports. Upload EWA reports manually.
- XLSX for the SolMan archive. Export Solution Manager data to CSV. See SolMan migration.
- Dedicated Basis administrator role. Assign
infrastructure_adminto Basis administrators. See Roles and permissions.
What the partial items mean for you today
- CAB role per landscape stage. The cutover checklist item Production CAB configured for every landscape checks a value that has no screen yet.
- Transport SoD. Do not rely on TENSOR to keep the DEV-to-QA approver from approving QA-to-PROD.
- SAP authorisations. You can read role assignments, SoD violations and existing user mappings, but not create mappings in the UI.
- USMM and SLAW. Measurements are collected and recorded, but you cannot schedule runs or view SLAW results on screen yet.
- Severity map override. The per-connection override of the default CCMS severity map (1 to SEV1, 2 to SEV2, 3 and 4 to SEV3, 5 to SEV4) has no screen yet.