Skip to content
SAP change and release governanceNothing installed in SAP

Govern every SAP transport with a record you can verify.

TrackIt puts ordered gates, mandatory verification evidence, and enforced segregation of duties around your transport requests — recording every release decision in a tamper-evident audit ledger.

✓ No ABAP Code in SAP✓ PostgreSQL RLS Isolation✓ SAML 2.0 / OIDC & SCIM✓ Hash-Chained Audit Trails
SAP Landscape:S/4HANA Enterprise•Client: 500 (PRD)Illustration
Transport Request

S4DK904218

Component / Subsystem

FI-GL: Core Real-Time Settlement

Governance Policy

Strict Dual Sign-off (SoD)

Current Stage
Gate 4: Awaiting Sign-offs
Gate 4 — Production Release PolicyMandatory 2-Person Rule

Production release gate: dual sign-off

Segregation of Duties:Enforced (Maker ≠ Checker)

Delivery Authority

Sarah Chen (PM Lead)

Awaiting
Confirms regression suite pass, rollback verification, and deployment window approval.
Signature required

Business Owner

Julian Meyer (Finance VP)

Awaiting
Signs off commercial ledger impacts, user acceptance confirmation, and zero open P1 tickets.
Signature required

Production release: on hold

TrackIt does not mark S4DK904218 ready for production import until both independent approvals are recorded.

Complete Pending Approval Active Gate

Illustration with invented people and data. Not a real system.

Four ordered gates

Production needs two different people to sign off.

Tamper-evident ledger

Hash-chained entries you can verify offline.

Isolation in the database

Row-level security, tested in CI against a real database.

SSO and SCIM

SAML 2.0, OIDC and directory sync, set up by your admin.

The problem

Transport approvals live in inboxes.

When a production import goes wrong, or an auditor asks who approved it, the answer is scattered across email, chat and shared folders.

The Fragile Status Quo

Scattered across inboxes, spreadsheets & chats

High Audit Risk
  • Approval decisions sit in email threads and chat messages.
  • Test evidence and rollback plans live in local folders.
  • Basis imports without structural proof that sign-offs happened.
  • Emergency changes leave no central review trail.

Result: Weeks of stressful audit preparation and blind imports that jeopardize production.

The Architecture of Certainty

Ordered gates and a tamper-evident ledger

Audit Ready
  • Every decision is a recorded, attributable step in a fixed order.
  • Evidence is attached to the transport it belongs to.
  • A gate does not open until the one before it is complete.
  • Emergency access is time-boxed, justified and on the record.

Result: an audit package you can verify offline, and a recorded approval behind every transport TrackIt releases.

How it works

Four gates. One order. No shortcuts.

A transport moves forward only when the gate before it is complete. Choose a gate to see who approves it and what evidence it needs.

Target System: DEV-100 — Development & Customizing

Unit test & DEV to QAS

The change is complete in development and ready to move to quality. Technical evidence is logged before it can be released.

Segregation of Duties (SoD) Policy

Unit-test evidence is attached before the transport leaves development; high-risk and customizing changes also need a rollback plan.

Example policy. In the current pilot, SAP responses come from a simulator.

Hash-Chained Verification•Tamper-evident non-repudiation

Authorized Approver Roles

  • Project manager

Mandatory Technical Evidence

  • Unit test evidence
  • Code review sign-off
  • Rollback plan

The product

What your release team works in.

The same screens your approvers, Basis administrators and auditors use every day.

Approvals

Approvals that cannot approve themselves.

  • Gates open in order; a transport cannot skip one.
  • Nobody approves a transport they raised.
  • Production needs the project manager and a business stakeholder, never the same person.
  • Approvers are reminded before an approval is overdue.
The approval queue, showing transport requests with their gate status and who needs to act.
Demo data. Simulated enterprise release workflow.
Governance

Emergency access with nothing hidden.

  • Break-glass access needs an incident, is time-boxed and expires by itself.
  • Security alerts are reviewed and acknowledged by an administrator.
  • Every override is attributed to a person and recorded.
The governance console, showing security alerts, ledger integrity and emergency sessions.
Demo data. Simulated enterprise release workflow.
Audit

A record an auditor can verify.

  • Approvals, evidence uploads and overrides are hash-chained entries.
  • Verify the chain on demand, or offline against an export.
  • Evidence stays attached to the transport it belongs to.
The audit view, listing every transport with its status, risk level and a manifest download.
Demo data. Simulated enterprise release workflow.

Identity and security

Built for the questions procurement asks.

What is implemented, stated plainly. The Trust page lists what is not done yet.

SAML 2.0 • OIDC • SCIM

Your identity provider

Per-organization SAML 2.0 and OpenID Connect, set up by your own admin, with a verified domain. SCIM 2.0 syncs users and groups.

Enforced by design
PostgreSQL Row-Level Security

Tenant isolation

Each organization's data is separated by PostgreSQL row-level security, checked in CI. The platform operator cannot read your records.

Enforced by design
AES-256-GCM Cryptography

Credentials stay protected

Credentials and secrets are encrypted at rest with AES-256-GCM, so a database copy does not expose them.

Enforced by design
Zero ABAP Modification

Nothing installed in SAP

No ABAP add-on and no transport into your landscape: only standard function modules are called.

Enforced by design

Architecture

An overlay, not an add-on.

TrackIt sits beside your SAP landscape. It reads transport metadata through standard interfaces, runs the approval workflow, and keeps the record.

  • Standard function modules only; nothing is deployed into SAP.
  • A separate record of approvals and evidence per organization.
  • Sign-in through your identity provider; roles inside TrackIt.
Nothing installed in SAP

Unlike legacy change management tools, TrackIt requires no ABAP packages, no modification of standard SAP tables, and no transport imports into your core landscape.

Enterprise Security & DMZ Boundary
Zone 1: Enterprise Identity & Organization BoundarySAML 2.0 / SCIM 2.0

Customer IdP

Okta / Entra ID / Ping

Directory Sync

SCIM User/Group Mapping

Role Context

Basis, PM, Auditor, Owner

HTTPS (encrypted in transit)
Zone 2: TrackIt Sovereign Control PlaneTenant RLS Enforced

Gate Engine

Ordered Dual Sign-offs

SoD Policy Engine

Maker != Checker Guard

Audit Ledger

Hash-Chained SHA-256

Standard RFC Read-Only Calls • Outbound DMZ Agent
Zone 3: Customer SAP Landscape (On-Premises / RISE / Hyperscaler)Zero In-SAP Code
DEV-100

Development

Workbench
QAS-200

Quality

SIT / Regression
PRD-500

Production

Dual Sign-off
Architectural Principle: TrackIt is an overlay governance plane, not an SAP add-on. Metadata is ingested via standard SAP RFCs; release gates are enforced through identity and recorded approvals.

Who it is for

One workflow for everyone who touches a release.

Basis administrator

Release Readiness View

Primary Mandate & Responsibility

Imports approved transports

Non-Negotiable TrackIt Safeguard

Sees which gates are complete before moving anything

See which gates are complete for every transport, so nothing is imported to production ahead of its approvals.

Basis administrator View
AUTH: VERIFIED
Active Context:PRD Release Gate 4
Permission Set:Role-Scoped Policy
SoD Constraint:Strict Maker!=Checker
Ready for Enterprise Operations
Tailored Enterprise Pilot

See it on your own transports.

Tell us about your landscape and release process. We will walk you through the product with your workflow in mind.

Nothing installed in SAPCustom RFC permissions modelDedicated isolation sandbox