Open Beta — free access

Master your
SAP landscape.

SAPscope automatically collects data from your SAP systems and generates precise architecture diagnostics powered by AI. In seconds.

★ View on GitHub → Read the docs →

sapscope.luku.fr

SAPscope

Acme Corp

admin

logout

Systems

PRD 756

QAS 756

DEV 755

AI Analysis — PRD SAP_BASIS 756 HANA 2.0

Maintenance status

            OK  SAP_BASIS 756 — mainstream maintenance active

            OK  Kernel 785 — up to date

             !   SP Level SAPKB75614 — 3 critical notes applicable

            OK  HANA 2.0 SPS 07 — support active until 2030

SAP_BASIS SAP_ABA +14 components

Features

Everything a Basis consultant
always wanted.

No more running SM51, SE16, SPAM one after another to reconstruct a picture of your system.

Automatic RFC collection

An agent runs on any server with RFC access and automatically collects components, support packages, kernel levels and custom ABAP objects — no manual work required.

AI-powered diagnostics

Every snapshot generates a structured report: maintenance status, identified risks, prioritized recommendations, actions to schedule.

Snapshot comparison

See exactly what changed between two dates: added or updated components, applied patches, evolution of custom objects.

Multi-client, multi-system

Manage multiple SAP clients from a single interface. Each scope is isolated, with its own agent tokens and assigned consultants.

Isolation & confidentiality

Single-use agent tokens, read-only consultant access. Your SAP data stays within your perimeter — never exposed to the outside.

Continuous history

Every snapshot is archived. Go back to any date, compare periods, track drift before it becomes an incident.

agent · PRD

$python agent.py --sid PRD

→ Connecting via RFC...

✓ Components 47 collected

✓ Support packages done

✓ Kernel 785 pl14 done

✓ Custom objects 312

Snapshot PRD · sent · 1.2s

health overview · Acme Corp

PRD

QAS

WARNING

DEV

CRITICAL

diff · PRD · Oct 14 → Nov 3

~ SAP_BASIS 756.00 → 756.01

~ Kernel 784 → 785

+ SAPKB75614 new patch applied

= YCUSTREP_ZZ no change

= ZFINREP_V2 no change

landscape · all clients

Acme Corp

PRD 87 QAS 74 DEV 55

GlobalBank

PRD 92 QAS 88

TechGroup

PRD 71 QAS 38

agent tokens · Acme Corp

PRD

sk-prd-••••••••••••a3f2

READ ONLY · LOCAL RFC

QAS

sk-qas-••••••••••••b7c1

READ ONLY · LOCAL RFC

health score · PRD · 30 days

Today87

-7d 78

-30d38

How it works

Up and running in 10 minutes.

No complex RFC setup. No BTP access. Just a Python agent, a cron job, and you're done.

Step 01

Deploy the agent on any server with network access to SAP

The pyrfc agent runs on any server — your monitoring server, a VM, or a Docker container — and connects to SAP via RFC on port 33XX. No software installed on SAP servers. No inbound connection required.

$git clone https://github.com/LukuLaMule/sapscope.git
$cd sapscope/agent && pip install -r requirements.txt
$# SAPSCOPE_TOKEN=your_token_here
$python -m agent --dry-run
✓Snapshot sent — PRD, 47 components

Step 02

Data syncs automatically

A systemd timer triggers the agent every 24h. Each run sends a complete snapshot: installed components, support packages, kernel, custom ABAP objects, DB info.

PRD — active

Last snapshot: 2h ago · 47 components · 1,247 custom objects

QAS — active

Last snapshot: 3h ago · 47 components · 1,199 custom objects

DEV — inactive

Last snapshot: 26h ago · Check the timer

Step 03

Consult the AI analysis from anywhere

Claude analyzes each snapshot and generates a structured report: maintenance status, identified risks, prioritized recommendations. Accessible on desktop, tablet or mobile.

Priority recommendations

OK SAP_BASIS 756 SP14 — maintenance assured until 2027

! SAP Note 3089413 critical — schedule application

! Kernel 785 patch 19 available — update recommended

OK HANA 2.0 SPS07 — supported version

Next recommended maintenance window: Q2 2026

FAQ

Frequently asked questions

Yes. SAPscope is compatible with SAP ECC 6.0, S/4HANA, BW and Solution Manager. Collection is done via RFC/SM59, with no modification to the SAP system. See our RFC user setup guide.

No. The agent runs on your infrastructure and only sends SAPscope anonymized technical metrics (performance, jobs, system logs). No business data, no table content is ever transmitted.

Less than 10 minutes. Clone the repo, copy-paste deploy/.env.example to .env, run docker compose up -d. Then install the agent on any server with RFC access to SAP. That's it.

A System (A) type user with a minimal read-only authorization profile. We provide an ABAP program ZSAPSCOPE_SETUP that creates the user and assigns exactly the required authorizations. See the RFC guide.

No. AI diagnostics are based only on technical metrics: system performance, background job statuses, error logs. No table data (customers, orders, accounting…) is ever transmitted to the model.

SAPscope is self-hosted — you own the deployment. Your licence key activates the AI analysis engine. If you need a new key or want to change plans, contact us at pro@luku.fr.

Yes, SAPscope is exclusively self-hosted — your SAP data never leaves your infrastructure. Clone the repo and deploy with Docker Compose on your own server. See the documentation to get started.

By default, the agent runs once every 24 hours via a systemd timer. You can adjust this interval — hourly collection is supported for critical systems. Each run takes under 30 seconds and has negligible impact on system performance.

Yes. The agent connects locally from within the SAP server via RFC — no inbound connection from the internet is needed. SAProuter and Message Server (logon groups) are supported through the systems.yaml configuration file.

Yes. SAPscope automatically detects the system type (S/4HANA, ECC, BW, SolMan, PI/PO…) from installed components. All system types are displayed in a unified landscape view, with transport routes visualized across the whole STMS domain.

Master yourSAP landscape.

Everything a Basis consultantalways wanted.