Integrations

Works with the tools your SAP team already runs.

Trace reads tickets from your service desk and acts through standard SAP transactions. Below is exactly what's available today and what we're building with design partners.

Available today, and planned. One works now: a CSV export for a Replay. The rest are being built with design partners.

Ticket intake

CSV import

Upload closed tickets from any tool for a Replay. Read on your machine.

Available
Ticket intake

ServiceNow

Read incidents and post Trace's classification and proposed fix back to the ticket.

Planned for design partners
Ticket intake

Jira Service Management

Pull SAP queues and write the triage result into the issue.

Planned for design partners
Ticket intake

SAP Solution Manager

Read incidents and ChaRM change requests; changes follow your existing approval flow.

Planned for design partners
SAP landscape

SAP ECC 6.0

Works through standard transactions (BD87, SM12, SM37, SU01) under a dedicated least-privilege user. Nothing installed on SAP.

Planned for design partners
Governance

Change approval

Every production change waits for an approver in your change process, recorded with their name. In a Replay, approvals are recorded in Trace.

Planned for design partners
Notifications

Microsoft Teams and Slack

Approvals and fixed-and-verified notices where your team already works.

Planned for design partners
Identity

Single sign-on (SAML)

Sign in to Trace with your identity provider.

Planned for design partners

Don't see your tool? Design partners decide which integration we build next. Tell us yours.

Start with a CSV.

A Replay needs nothing but an export of closed tickets. No integration, no access to SAP.