Services

Clean Core assessment & modernization

Fixed-scope, practitioner-led engagements that move your SAP custom code toward a clean S/4HANA core — SAP's current platform, kept standard so upgrades stay easy — without betting the business on a rewrite.
ATC — cloud-readiness worklist
error

Direct table modification — UPDATE zorders

→ RAP: MODIFY ENTITIES (released behavior)

error

Use of sy-uname / sy-datum

→ cl_abap_context_info (released API)

warn

SELECT * without a field list

→ Explicit field list

warn

SELECT inside a LOOP (N+1)

→ Single set-based read / JOIN

info

WRITE statement (no Fiori UI)

→ Fiori Elements / RAP UI

Illustrative sample — your report reflects your real codebase, scored worst-first and paired with the released, upgrade-safe fix.

What you can buy

Engagements that map to real outcomes

Clean Core readiness assessment

Know your upgrade risk before it bites: a short, fixed-scope engagement that measures how far your custom code sits from a clean S/4HANA core (SAP's current platform, kept standard with custom needs built beside it) and turns ATC noise (ATC is SAP's code-quality checker) into a plan you can act on.

  • A readiness score and risk verdict for your custom code
  • A worst-first remediation backlog, each item mapped to a fix
  • A right-sized modernization roadmap (build vs. retire vs. replace)

ATC custom-code remediation

Clear the blockers between you and the cloud: hands-on fixes for the findings that block ABAP Cloud (SAP's cloud-safe development model) — SAP-table writes, sy-fields (built-in system values), native SQL, unreleased APIs and classic Dynpro (old GUI screens).

  • ABAP_CLOUD_DEVELOPMENT_DEFAULT / S/4HANA findings cleared, batch by batch
  • Released-API replacements (official, upgrade-safe interfaces) with governed wrappers where needed
  • ATC baseline + CI gate so findings don't creep back

RAP / CDS / Fiori migration

Turn ageing reports into modern, upgrade-safe web apps: we re-platform them onto SAP's current stack — CDS data models (SAP's modern data layer), RAP behavior (its modern app framework), OData services (the standard web data interface) and Fiori Elements apps (its modern web UI).

  • Classic reports rebuilt as CDS + RAP + Fiori
  • Managed or unmanaged RAP, with EML (RAP's data-change language) replacing direct DB updates
  • A reusable VDM / extensibility pattern (SAP's standard data-model conventions) your team can extend

Integration & analytics

Connect SAP to the rest of your business reliably: brittle BDC screen-scraping (scripts that replay GUI screens) retired in favour of released APIs, and live analytics so the business sees its own data without waiting on exports.

  • BDC / CALL TRANSACTION replaced with BAPI (official interface), RAP or OData
  • OData + analytical CDS feeding Power BI / Datasphere live
  • Idempotent, observable integrations (safe to retry, easy to monitor) with retry and logging

Clean Core governance & optimization — for teams already on S/4HANA

Already live on S/4HANA or ABAP Cloud? The risk shifts from migrating to staying clean. Converted systems quietly accumulate new tech debt: custom code that crept back into the core, ATC drift, unreleased-API usage, and a continuous SAP release cadence that keeps moving under you. We keep your core clean and your extensions upgrade-safe — so every release stays a non-event, not a project.

  • A Clean Core health check: ATC drift, released-API compliance and tech-debt scored against your live system
  • CI/CD ATC quality gates so new code can't reintroduce violations
  • Extension-strategy review — the right tier for each need (key-user, in-app BAdI, side-by-side on BTP)
  • HANA performance tuning and Fiori adoption for the apps you've already shipped

ABAP Enclave — private, on-prem AI for ABAP

A privacy-first AI toolkit for ABAP teams that runs entirely on your own hardware: a locally hosted open-weight model (via Ollama) wired into VS Code, plus a CLI of capability modules — so no ABAP source ever leaves your network (suitable for regulated and air-gapped landscapes) and there's no per-seat cloud-AI licence. Developers get context-aware help in their existing workflow, with abaplint enforcing Clean ABAP before anything reaches a transport. Delivered as modular workstreams scoped to your landscape, plus an open-source kit you keep.

  • A local LLM stood up on your hardware — models benchmarked and selected for your stack
  • VS Code wired to your on-prem ABAP via ABAPfs + Continue, with zero internet egress
  • An abaplint Clean ABAP ruleset tuned to your standards, catching issues before transport
  • A CLI of capability modules (ATC triage, test generation, documentation) your team keeps
Learn more
What happens after you book

A simple, de-risked path

No open-ended day rates. You always know what you're buying and what you'll get.

  1. 1

    Book a call

    A 30-minute scoping call — your landscape, your pain points, your goals. No charge, no obligation.

  2. 2

    Fixed-scope proposal

    You get a written proposal with a defined scope, deliverables, timeline and a fixed price. No open-ended meters.

  3. 3

    Assessment sprint

    We score your code against Clean Core and hand back a prioritized, worst-first remediation plan you own outright.

  4. 4

    Remediate & hand over

    We fix the highest-risk findings in your landscape, set up the CI guardrails, and hand over with your team upskilled.

How we work

  • We work inside your landscape and your transport process — your IP stays yours.
  • Read-only analysis first; changes only on agreed, scoped objects.
  • Fixed scope and a fixed price — you always know what you're buying.
  • Code you own. No proprietary runtime, no lock-in, MIT-licensed tooling.
  • Remote-first, with working-hours overlap; NDA-friendly from day one.
  • We upskill your team as we go, so the clean core stays clean after we leave.

This is for you if…

  • Small-to-mid-size SAP teams on S/4HANA (or planning the move).
  • Teams already live on S/4HANA who need to keep the core clean and stay upgrade-safe.
  • A custom-code base big enough to be risky, small enough to lack a platform team.
  • Teams who want to modernize incrementally — not bet the business on a rewrite.
  • Leads who want their developers upskilled, not sidelined.

Probably not a fit if…

  • Greenfield SAP implementations with no custom ABAP and no plan to extend.
  • Teams looking to outsource ownership of their code long-term.
  • Anyone wanting a big-bang rip-and-replace over incremental, low-risk change.
Why a specialist

Lumivara vs the alternatives

The honest comparison for a small or mid-size SAP team weighing its options.

Criterion Lumivara A large SI Doing nothing
Cost model Fixed scope & price Day rates, scope creep $0 now, rising debt
Who does the work A senior specialist (15 yrs) A rotating, often-junior bench
Time to value Weeks, incremental Months, big-bang program None
Risk Low — no rip-and-replace High — large programs Highest — cloud & upgrades blocked
Code ownership You keep everything (MIT tooling) Often tied to their framework Frozen as-is
Your team Upskilled as we go Dependent on the vendor Falls further behind
Who you work with

Practitioner-led, start to finish

You work directly with a senior ABAP practitioner — 15 years, hands-on — start to finish.

Ready to start your Clean Core journey?

Book a free 30-minute scoping call. We'll look at your landscape and show you the fastest, lowest-risk path to a clean S/4HANA core.