SprintSAP
No SAP system registered yet.
Add your first SAP connection in
Settings
to start running audits. SprintSAP connects strictly read-only via RFC.
is currently offline — displaying results from the last scan on .
All pages show cached data. Live actions ("Run audit",
"Run profiling", etc.) are disabled until the SAP system
is reachable again.
SAP Health Assessment
·
Last full audit
·
No full audit recorded yet on this system
Connection
Audit Progress
✓
✗
⋯
✓
%
Priority actions
Top 5 business-tier findings
·
✓
No business-tier findings
SAP-standard business components were clean at the last audit.
No audit data yet on this system
Audits run via the scheduler once it's configured in Settings.
Data Quality
Verifies the structural integrity of your SAP data across
application components via
automated read-only checks.
Last run:
Never run
Checks failed
out of
·
Inconclusive
not passed, not failed
Checks passed
data-backed PASS verdicts
checks in scope
business components
· FAIL
· INCONC
·
technical (informational)
· FAIL
·
custom
· FAIL
·
+ adversarial probes
No applicable checks — this system does not support the RFC_ABAP_INSTALL_AND_RUN function module
Informational only — not counted in the headline FAIL score.
Top 10 business components to fix
Ranked by fail × tier_weightBusiness components Technical components (infrastructure) Custom components (customer-developed)
SAP-standard business packages (FI, MM, SD, HR, …)
SAP kernel / Basis / DDIC / system housekeeping — informational
Customer namespaces (Z_*, Y_*, /partner/)
No components match "" in this tab.
No components in this tier.
…
Selected component
· tables
· generated checks
Passed
Failed
| ID | Description | Evidence | Result |
|---|---|---|---|
| No checks loaded — click Run Component | |||
| No checks match the current filter / search. | |||
…
Auto-Discovered Checks
Not yet discovered — click Run Discovery to analyze data dictionary
| Table | Field | Type | Description |
|---|---|---|---|
| No checks match the current filters | |||
…
Adversarial Cross-Checks
No adversarial probes yet — click Run Adversarial
| Probe | Tables | Finding / reason | Rate | Verdict |
|---|---|---|---|---|
|
|
,
Consistent
Full reason (verbatim from SAP / probe):
|
Check Reference Guide
Automated checks explained in business language. On ECC the DQ check set is auto-discovered per connected system (DDIC walk via TADIR + TDEVC + DD03L/DD05S/DD07T) — the list you see reflects THIS system's data dictionary, not a canned taxonomy. On S/4HANA the DQ checks run via RFC_READ_TABLE against the S/4HANA-native tables. System Health, Compliance & Security, and Migration Readiness checks work on both.
Auto-discovered on the connected system
The ECC DQ check set is auto-discovered per connected system (TADIR + TDEVC + DD03L/DD05S/DD07T walk). The list below reflects THIS system's data dictionary — run POST /dq/discover (or the Run Discovery button in Data Quality) to refresh. Grouped by the application-component taxonomy that emerged from the resolver.
Last discovery: · checks
Loading…
No discovery cache on this system yet
Open the Data Quality page and click Run Discovery to populate this reference from the connected system's DDIC.
Verifies:
Why it matters:
Tables:
S/4HANA-native DQ checks
These S/4HANA-native checks target the S/4HANA data model (BUT000, MATDOC, ACDOCA, BUT020, …) and run via RFC_READ_TABLE with narrow field lists — they do NOT use RFC_ABAP_INSTALL_AND_RUN, which was removed from S/4HANA 1909+. Each check scans 100% of the primary table; results always state "X records affected out of Y total".
Verifies:
Why it matters:
Tables:
Verifies:
Why it matters:
Tables:
System Profile
Platform-wide inventory of every transparent table in the active SAP system, classified by module, with row counts for application tables. Click any table to drill into per-field completeness, distinct value counts, and top values — computed on demand from 100% of that table's rows.
Last profiled:
Not yet profiled
Full system profiling in progress — discovering tables and counting rows. This may take several hours on large systems. Results are cached permanently and available offline.
System not yet profiled
Full system profiling discovers every transparent table, counts all rows, and classifies by module. Results are cached permanently and available offline. Other features (Analytics, Deployment Impact) use this data.
Full profiling may take several hours on large systems. Run once, then use cached data.
Total tables discovered
100% of DD02L (TABCLASS=TRANSP)
Application tables counted
/
Non-empty tables
Run duration
Classification breakdown
Top tables by row count
Click a table to open the full field-level profile.
| Rank | Table | Category | Rows | |
|---|---|---|---|---|
tables still have pending row counts
The current run used a s budget and counted the top
prioritised tables. To count more, re-run profiling with a longer budget
(
POST /profiling/run?budget=300),
or open any single table below to get its exact row count + field-level profile on demand.
| Field | Key | Non-blank | Completeness | Distinct | Top values |
|---|---|---|---|---|---|
| KEY |
Reading from live SAP…
Data Cleansing Detection
Identifies duplicate records, format inconsistencies, orphaned references, and incomplete mandatory fields. SprintSAP detects without modifying — remediation is performed by your team using standard SAP transactions.
Last run:
Running cleansing detection against live SAP data...
issues found
Loading cleansing data...
No cleansing data yet. Click Run Cleansing to scan live SAP data.
Table:
records
Showing page / ( total)
No records affected.
Loading audit trail...
No cleansing sessions yet
Past cleansing sessions and action logs will appear here after data is processed.
| Session | Date | Actions | Status |
|---|---|---|---|
Before/after verification
After cleansing actions are applied, run verification to compare DQ scores before and after, and detect any side effects.
Custom Business Rules
Define business-specific validation checks without coding. Rules specify target table, field, condition, and expected outcome. SprintSAP translates each rule into a read-only query and returns evidence-level results.
Loading rules...
No rules yet. Click Add Rule to create one.
.
where
records
failing record(s) — first 50 shown
Migration Assessment
Source-only ECC→S/4HANA migration evaluation: SAP Simplification Item coverage, schema mapping, data volume sizing, custom code impact, and overall readiness scoring.
Source System
SAP Simplification Item Coverage
What does this mean? When SAP built S/4HANA, they changed how hundreds of features work compared to your current ECC system. Each "simplification item" is one such change. Active items are changes that directly affect your system and need to be checked before migration. Before conversion items need to be addressed during the migration itself. Inactive items don't apply to your configuration. The more items resolved, the smoother the migration.
Database Structure Compatibility
Unchanged
Modified by SAP
Discontinued
New in S/4HANA
What does this mean? Your ECC system stores data in thousands of database tables. When migrating to S/4HANA, most tables transfer directly (unchanged). However, SAP has restructured some tables in the new system (modified) — for example, vendor and customer data now merge into a single "Business Partner" format. Some old tables no longer exist (discontinued), and S/4HANA introduces new ones. The more "modified" and "discontinued" tables you have with data, the more planning the migration requires.
ECC Data Volume & HANA Sizing
Total rows
Non-empty tables
Estimated raw size
HANA compressed
Assumptions:
What does this mean? This is the total amount of data in your current system — every transaction, every master record, every document. S/4HANA runs on an in-memory database (HANA) which compresses this data significantly. The HANA compressed range determines the server size and licence cost you'll need. Archiving old data before migration (records older than 5-7 years) can reduce this number and save on infrastructure costs.
Custom Code Impact
Programs analyzed
Programs affected
Total findings
SIC items affected
What does this mean? Over the years, your team (or SAP consultants) built custom programs to add features beyond what standard SAP provides. These are called "Z programs". Some of these programs use database tables or functions that SAP has changed or removed in S/4HANA. Programs affected is the number that needs a developer to review and potentially modify before migration. The higher this number, the more development effort (and budget) the migration will require. Programs marked as critical use tables that no longer exist — they will break on day one if not updated.
Remediation Plan
Critical
Code will break
High
Performance risk
Medium
Recommended
Low
Best practice
How to fix
Compatibility view:
SAP Notes:
What does this mean? This is the complete list of changes needed to prepare your system for S/4HANA. Critical items will cause system failures on day one if not fixed — these are non-negotiable. High items use compatibility features that work but hurt performance — plan to fix these within the first year. Medium items follow SAP best practices. Click "How to fix" on any item to see the exact technical change required, including the SAP-published replacement and relevant SAP Note numbers. Download the Remediation Plan PDF above for the full printable version.
readiness
Overall Migration Readiness
What does this mean? This score combines five factors that determine how ready your system is for migration. 80% and above means you can begin migration planning with confidence. 60-80% means there are issues to fix first but they're manageable. Below 60% means significant preparation work is needed. Each bar shows one factor — the lower ones indicate where to focus effort. Items marked "N/A" haven't been assessed yet; running those checks will refine the score. Download the Board Report above for a full explanation suitable for executive decision-making.
No assessment run yet. Click Run Assessment.
Integration Health
Monitors SAP connections to external systems through IDocs, RFC destinations, and transactional RFC queues. The Migration Readiness sub-assessment evaluates S/4HANA preparedness.
Last run:
Migration Readiness
Not accessible —
| ID | Check | Verdict | Count |
|---|---|---|---|
No Migration Readiness data yet. Click Run Migration Audit.
Loading audit data...
No audit data yet. Click Run Interface Audit.
health
Integration Health
Categories audited
/
Findings
Top findings
unavailable
records
· in error (%)
· oldest
score
Findings
By status
·
Top failing IDoc types
Monthly volume
RFC destinations by type
·
Aborted jobs
| JOBNAME | JOBCOUNT | SDLDATE | USER |
|---|---|---|---|
By object class
By user
Loading IDoc data...
No IDoc analysis yet
Run an Interface Audit first, then IDoc details will appear here.
IDocs (7 days)
In Error
Error Rate (24h)
Stuck (>30d)
IDoc Checks
| ID | Check | Verdict | Detail |
|---|---|---|---|
Top Failing Message Types
Top Failing Partners
Loading RFC data...
No RFC destination data yet
Run an Interface Audit to inventory RFC destinations.
RFC Destinations
RFC Checks
| ID | Check | Verdict | Detail |
|---|---|---|---|
Loading batch job data...
No batch job data yet
Run an Interface Audit to monitor interface batch jobs.
Interface Jobs (7d)
Failed
Batch Job Checks
| ID | Check | Verdict | Detail |
|---|---|---|---|
Loading partner data...
No partner landscape data yet
Run an Interface Audit to map partner connections.
Partners
| Partner | Channels | Status | OK (7d) | Errors (7d) | Last Exchange | Message Types |
|---|---|---|---|---|---|---|
Deployment Impact
Analyzes the impact of proposed SAP changes before they are applied. Upload a deployment package or analyze transports directly from the queue.
Failed to load transport queue
No transports loaded
Click Refresh to load transports from the SAP system.
| Transport | Description | Type | Status | Owner | Date | Objects | Action |
|---|---|---|---|---|---|---|---|
Analyzing transport
Reading objects, source code, dependencies, and computing risk score...
Status
Owner
Date
Function
objects
programs
functions
tables
Analyzed in
risk
Risk Breakdown
Transport Objects
| PGMID | Type | Object Name |
|---|---|---|
Program Analysis — programs
Clean
lines
Impact:
Findings
| Line | Severity | Category | Description | Remediation | Code |
|---|---|---|---|---|---|
|
Dependencies
Tables Read
None
FMs Called
None
Includes
None
Cross-Reference Dependencies ()
| Type | Name | Dep Type | Dep Object | Dep Name | Depth |
|---|---|---|---|---|---|
Source Preview (first lines)
Cross-Impact Analysis
blast radius (programs)
| Table | Programs Sharing | Deprecated | Critical Progs | High Progs |
|---|---|---|---|---|
| — |
Impacted DQ Checks
No existing DQ checks reference the tables touched by this transport.
Tables Touched
None detected
Function Modules Called
None detected
Source load failed
Drop deployment package (.zip)
Must contain manifest.json describing the ABAP objects to deploy
The manifest should include: package name, version, object list (programs, tables, function modules), and action type (create/modify/drop).
Live Analysis
risk
n/a — data unavailable
Risk score is incomplete
One or more factors were unmeasurable on this system. Remaining factors were renormalized to produce the score above.
Objects in package
| Type | Name | Action | Tables | Findings | Severity |
|---|---|---|---|---|---|
| — |
Impacted checks ()
No existing checks reference impacted tables.
Code Analysis — programs analyzed from SAP
Clean
| Line | Severity | Category | Description | Code |
|---|---|---|---|---|
|
No findings — code is clean.
Object Conflicts
Live-verified via DDIC tables on target system
0 conflicts
0 object conflicts — all CREATE actions target names that do not exist on the target system.
Live source info
Downstream consumers
Evidence trail
rfc_call:
ddic_table:
where_clause:
rows_returned:
verified_at:
system:
raw_row:
Reproduce in SAP:
Missing Dependencies
Runtime short-dump predictions from live DDIC existence checks
0 missing
0 missing dependencies — every table, function module, and include referenced by the package's programs either ships in this manifest or already exists on the target.
Referenced by
at line(s)
Evidence trail
rfc_call:
ddic_table:
where_clause:
rows_returned:
verified_at:
system:
error_type:
error:
Reproduce in SAP:
Auto-Generated DDIC Checks
STRICT READ-ONLY
Server-side FK orphan counts + structural impact from DDIC live graph
Click "Run deep DDIC checks" to auto-generate 100s of referential-integrity checks from the DDIC graph of impacted tables.
Each FK orphan is counted server-side on 100% of the population — no sampling.
Seeds
FK edges
Checks run
RFC path
Metrics
Evidence trail
check_id:
ddic_source:
rfc_call_discovery:
rfc_call_execution:
discovered_at:
verified_at:
ddic_row:
sample_orphans:
reason:
Reproduce in SAP:
Baseline captured
Total
Passed
Failed
Verdict
Simulation mode:
Runs the package's custom audit rules read-only against live SAP data to predict their post-deploy verdicts. For a full before/after DQ diff, run step 4 (Re-run & compare).
Simulated Post-Deploy Prediction
Total Checks
Passed
Failed
Duration
| Domain | Check | Baseline | Simulated | Delta |
|---|---|---|---|---|
| No checks in this category. | ||||
Custom Rules Simulation
Simulation could not run
INCONCLUSIVE
:
Predicted findings:
Could not verify post-deploy state
:
Baseline vs current
| Domain | Check | Before | After |
|---|---|---|---|
| No checks in this category. | |||
Failed to load deployment history
Deployment History
| Date | Filename | Objects | Impacted | Risk | Baseline | Simulation | Regressions | |
|---|---|---|---|---|---|---|---|---|
|
|
No deployment history
Upload a deployment package to see analysis history here.
Failed to load code analysis status
Analyze Z* programs for deprecated S/4HANA references, security issues, and coding patterns.
Available FMs:
Import the Z_SPRINTSAP transport into SE37 to enable source code analysis. You can still paste source code manually below.
Programs Analyzed
With Issues
Critical
Total Findings
Analyze Single Program
| Program | Lines | Findings | Severity | Impact | Actions |
|---|---|---|---|---|---|
| Clean |
No code analysis results
Click Analyze All Z Programs to scan for deprecated references and S/4HANA migration issues.
·
·
Impact:
Dependencies
Tables Read
FMs Called
Includes
Findings
| Line | Severity | Category | Description | Remediation |
|---|---|---|---|---|
Source Code
Audit History & Trends
Track how your SAP data quality evolves over time. Each audit run is stored and compared against previous baselines, showing improvements and regressions across all domains.
Score Timeline
Domain Pass-Rate Trends
Profiling — Completeness
Integration — Error Rates
Scan History
| Date | Type | Verdict | Checks | Pass / Fail | Integrity | Integration | Migration | Trigger | ||
|---|---|---|---|---|---|---|---|---|---|---|
| / |
|
|||||||||
| No scans recorded yet | ||||||||||
Scan # detail
Side-by-side comparison
| Metric | Scan A | Scan B | Delta |
|---|---|---|---|
Business Analytics
Executive-ready dashboards powered by live SAP data. Import a pre-built template or build custom visualizations with the AI assistant.
Analytics dashboards are stored separately for each SAP system. Import a template above or create a blank dashboard to get started.
Querying SAP...
cached
Empty dashboard
Add widgets manually or let the AI build them from natural language.
Export Reports
Generate comprehensive audit reports for stakeholders. Reports include data from your most recent scans.
Executive Summary
1–2 pages · PDF
For: DSI, Board — score gauges, top findings, and action items.
Detailed Audit
10–30 pages · PDF
For: Consultant, Auditor — per-domain findings with evidence tables.
Data Export
Multi-sheet · XLSX
For: Analyst, Data Manager — all findings + profiling in Excel.
Reports will include data from: DQ ,
Compliance ,
System Health
Report History
| Date | Type | System | Size | |
|---|---|---|---|---|
No reports generated yet. Click Generate above to create your first report.
Last audit run
No audit data yet
Run an audit first to generate exportable reports
Execution History
| Timestamp | Verdict | Pass | Fail | Total |
|---|---|---|---|---|
| No history yet | ||||
System Health
Assesses the operational stability of your SAP landscape — batch jobs, transports, number ranges, and user hygiene.
Last run:
System Health
| Category | Check | Status | Score |
|---|---|---|---|
No system health data yet
Click Run System Health Audit to check batch jobs, transports, number ranges, and users.
Not accessible —
| ID | Check | Verdict | Count/Metric |
|---|---|---|---|
Run a System Health audit to see detailed category breakdowns.
Compliance & Security
Identifies potential segregation of duties conflicts, financial posting anomalies, and user access risks. SprintSAP reads authorization tables without modifying any security configuration.
Last run:
Compliance Score
| ID | Check | Verdict | Count |
|---|---|---|---|
No compliance data yet
Click Run Compliance Audit to scan authorization tables, SoD conflicts, and posting anomalies.
Loading SoD data...
No SoD data yet
Run a Compliance Audit first, then SoD conflicts will appear here.
Users with conflicting transactions
| User | Role A | TCode A | Role B | TCode B | Severity |
|---|---|---|---|---|---|
| No SoD conflicts detected in tcode assignments. | |||||
Suspicious activity patterns: off-hours changes, mass changes, weekend activity.
No pattern analysis yet
Click Detect Patterns to scan change documents for suspicious activity.
| Pattern | Severity | Count | Rate | Detail |
|---|---|---|---|---|
| No suspicious patterns detected. | ||||
Loading trends...
No compliance trends yet
Run multiple compliance audits over time to see trends appear here.
Findings vs Previous Scan
New
Resolved
Persistent
Current scan:
Previous scan:
Total current:
New Findings
Resolved Findings
Persistent Findings
Migration Readiness
Evaluates S/4HANA migration preparedness — Business Partner readiness, custom code compatibility, material number formats, and data archiving opportunities.
Migration Readiness
| ID | Check | Verdict | Count |
|---|---|---|---|
No Migration Readiness audit yet. Click Run Migration Audit.
Plant Maintenance Analytics
Notification analysis from SAP PM — statuses, trends, overdue items, and functional location breakdown. All data from QMEL, JEST, QMIH, and AFIH.
Extracted:
QMEL: |
JEST: |
QMIH: |
AFIH:
No PM data loaded yet
Click Extract PM Data to pull notifications from QMEL, JEST, QMIH, and AFIH.
Total Notifications
Open
Completed
Overdue
Avg Close Time
Notifications by Status
Notifications by Type
Monthly Trend
Notifications by Plant
Top 10 Functional Locations
Overdue Notifications
| Notification | Description | Type | Status | Created | Required End | Days Overdue | Plant | Planner Group |
|---|---|---|---|---|---|---|---|---|
All Notifications
| Notification | Type | Description | Status | Created | Changed | Plant | Equipment | Func. Location | Order | Duration (d) |
|---|---|---|---|---|---|---|---|---|---|---|
IDocs Monitor
IDoc status monitoring from SAP table EDIDC — volumes, error rates, message types, and partner analysis.
Extracted:
EDIDC: rows
No IDoc data loaded yet
Click Run IDocs Scan to analyze EDIDC.
Total IDocs
Errors
Success Rate
Last 24h Volume
IDocs by Status
Top 20 Message Types
Inbound vs Outbound
Error Trend (by Date)
Top 20 Inbound Partners (SNDPRN)
Top 20 Outbound Partners (RCVPRN)
Error IDocs
| Doc Number | Status | Message Type | Direction | Sender | Receiver | Created | Time |
|---|---|---|---|---|---|---|---|
Background Jobs Monitor
Background job status monitoring from SAP table TBTCO — scheduled, running, finished, and aborted jobs.
Extracted:
TBTCO: rows
No job data loaded yet
Click Run Jobs Scan to analyze TBTCO.
Total Jobs
Failed / Aborted
Running Now
Finished (24h)
Jobs by Status
Top 20 Failed Jobs by Name
Top 20 Users
Daily Job Volume (Last 30 Days)
Periodic vs One-Time
Failed / Aborted Jobs
| Job Name | Job Count | Status | Start Date | Start Time | End Date | End Time | User |
|---|---|---|---|---|---|---|---|
| Aborted |
Change Tracker
Change document monitoring from SAP table CDHDR — who changed what, when, and suspicious activity detection.
Extracted:
CDHDR: rows
No change data loaded yet
Click Run Change Scan to analyze CDHDR.
Total Changes
Unique Users
Changes Today
Most Active Class
Suspicious Activity Detected
Top 20 Object Classes
Top 20 Users
Top 20 Transactions
Daily Change Volume (Last 30 Days)
Changes by Hour of Day
Recent Changes (Last 30 Days)
| Date | Time | User | Object Class | Object ID | Transaction |
|---|---|---|---|---|---|
Connection Settings
Register the SAP systems SprintSAP should connect to. All access remains strictly read-only.
Active connection
- System
- Type
- Host
- System ID / Client
- /
- Status
- Mode
- READ-ONLY
Registered SAP systems
system(s) registered.
Environment-defined entries are managed via .env and cannot be edited here.
| ID | Name | Type | Host | SysID / Client | Source | Actions |
|---|---|---|---|---|---|---|
| / |
|
|||||
| No systems registered yet. | ||||||
All fields except language are required. Passwords are encrypted at rest.
2-40 chars, alphanumeric + _ -. Cannot be changed after creation.