SAP integration troubleshooting and FAQ

Most SAP integration problems trace back to one of four things: the sap_integration flag, the connector agent's connectivity, the landscape role of an SAP system CI, or a separation-of-duties rule doing its job. The entries below are grouped by area.

Setup and access

The SAP pages say "SAP integration is off for this tenant"

The sap_integration flag is off. Select Go to Feature settings and switch it on. You need to be a tenant administrator. See Guides for setup and Basis administrators.

Some SAP pages show English text in a German session

The Transports and Authorizations pages and the SAP import schedule panel do not yet have German labels.

I cannot find the Transports or Authorizations page in the menu

They are not yet linked in navigation. Open them by address: /settings/sap/transports and /settings/sap/authorizations.

Connections and the connector agent

Test connection fails for an RFC system

TENSOR never opens RFC connections itself. RFC systems are served by the connector agent; check the agent's Last heartbeat and Last envelope instead.

An agent shows Heartbeat missing

No heartbeat has arrived for 15 minutes. Check that:

• the agent process runs;
• the host has HTTPS egress to your TENSOR address;
• the host clock is correct — signatures carry a timestamp.

Spooled envelopes are delivered automatically once the agent reconnects.

Enrollment fails

The token was already used or was mistyped. Create a new agent and use its new token. Tokens are shown once and cannot be retrieved.

The agent says it is running in fixture mode

The SAP libraries are not installed. For live mode, install the SAP NW RFC SDK and node-rfc (and @sap/hana-client for the HANA collector) under your own SAP licence. TENSOR does not ship them.

A disabled agent needs to come back

Disabling cannot be reversed. Create and enrol a new agent as the replacement; the old agent's history is kept.

Transports and imports

A new development transport did not create a Change

One of these applies:

• auto-create is off;
• the system's SAP system CI is not marked as dev;
• the SID has no CI;
• the transport header named no SAP connection.

Approval is refused on a transport Change

You created the Change. Another approver must approve it — this is the developer-is-not-approver rule.

Confirm import is refused

Either you created the Change (developer is not importer), or you lack sap.transport.confirm_import.

Scheduling asks for a justification

The maintenance window does not cover the target SAP system, or the SID has no CI. Choose a covering window or give a reason of at least 10 characters.

The PROD import did not close the Change

The Change could not close — for example because the post-implementation review is missing. TENSOR recorded drift; complete the Change manually.

Can TENSOR start the import in SAP for me?

Not today. Imports are executed by the Basis team in SAP STMS and confirmed in TENSOR. Release gating and automatic import from TENSOR are planned.

Evidence, authorisations and licences

USMM results differ from SAP's own USMM

The agent collects user-master facts; it does not run the USMM transaction. A formal licence audit still runs USMM in SAP.

I cannot map an SAP user to a TENSOR user

SAP-to-TENSOR user mappings cannot yet be created in the UI. Existing mappings are shown on the Authorizations page.

An EWA badge shows Evidence stale

The newest EarlyWatch Alert report for that system is older than 100 days. Upload a current report.

Acknowledging an SAP-raised incident did not clear the alarm in SAP

Alert acknowledgement write-back to SAP is planned, not yet available.

SolMan archive

A SolMan row was rejected in the dry run

A required field (external ID, kind, title, created) is missing, or the kind or date cannot be read. The report names the reason. Fix the export and repeat the dry run.

Can archive records be corrected?

No. Import a corrected batch and supersede the old one. Both batches remain on record.

My SolMan export is an XLSX file

XLSX files are not read directly. Export the data to CSV.