ZZAN.AI
Suites

Four suites for legacy modernization

SAP EP, SAP ABAP and DB are available now. AS/400 launches in January 2027.

SAP EP Suite

Any EP screen, rebuilt in React

We read the Java, JSP and PAR source directly and extract every screen, event and interface. Each screen is first rebuilt exactly as it looks today so business users can confirm it, then moved to a new UI on your design system with a Java back end.

Nothing missed

Screens, events, RFCs and SQL are extracted from the code structure itself, not by an LLM, so every run gives the same result.

A guide for every screen

Business summary, action flow and the RFC and DB calls behind each screen, on one page.

Rebuilt as it was

Screens rebuilt with the original CSS and structure, marked done only after passing quality checks.

Portal features decided first

Replacements for portal-specific features such as SSO and document storage are decided first. The AS-IS can’t be signed off until they are.

New screens on your design system

New screens are built from your design system and approved package by package.

From
JavaJSP / PARPortal config
To
React (on your design system)Java · Spring BootScaffolds for 10 back-end stacks
Progress
  1. Analysis
  2. AS-IS sign-off
  3. Conversion & build
  4. Testing
  5. UAT & acceptance
  6. Hypercare
SAP ABAP Suite

ABAP development, now with AI

AIFLOW connects to your SAP system (RFC for ECC, ADT and RFC for S/4HANA), so development, checks and transport happen on one browser screen. AI edits code and writes tests, while every SAP change is made under a personal account, with approval and an audit trail.

Develop with AI

In the Workbench, AI fixes code, repairs defects and writes documentation. A person reviews the diff before anything reaches SAP.

Checked against your standards

Code is checked against your ABAP development standards. What can be fixed is fixed automatically, exceptions go through approval, and results are exported to Excel for review.

Tests proven in numbers

Coverage is measured by SAP itself. AI writes and fills in test cases, and passes are voided when the code changes.

Record once, regression every night

Record a flow in SAP GUI once and it becomes an E2E test that reruns every night. Tests run under each user’s own account on their own PC, so no additional SAP licenses are needed.

Every change under control

Production systems and SAP standard objects can’t be modified, second-person approval can be required, and every change is logged with human and AI work kept apart.

From
SAP ECC · RFCS/4HANA · ADT / RFC
To
ABAP codeTests · Review reports · Docs
Progress
  1. Analysis
  2. AS-IS sign-off
  3. Conversion & build
  4. Testing
  5. UAT & acceptance
  6. Hypercare
DB Suite

Business logic, out of the database

We analyze Oracle PL/SQL and decide by rule whether each object moves to Java, stays in the database, or is split between the two. Only logic flows a person has confirmed become code, and the result runs against the original with the same inputs to compare performance and output. Oracle is supported today.

What to convert

Convert, keep or split — decided by rules you can explain.

Only confirmed flows become code

AI drafts the logic flow; only the version a person confirms becomes code.

Measured against the original

Round trips, reads and return values are compared with the original, and a result mismatch blocks the change.

From
Oracle PL/SQLStored procedures
To
Java · MyBatisCode that is easy to test and review
Progress
  1. Analysis
  2. AS-IS sign-off
  3. Conversion & build
  4. Testing
  5. UAT & acceptance
  6. Hypercare
AS/400 RPG Suite
Launching Jan 2027

AS/400, into a modern system

AIFLOW reads AS/400 system information and legacy code. AI analyzes it, your team confirms it, and it becomes a modern system on the stack you choose.

AI analysis

AI analyzes system information and legacy code.

Human confirmation

Your team reviews and confirms the analysis.

Modernization

Converted into a modern system on your chosen stack.

From
System informationLegacy code
To
Modern systemYour chosen stack
Progress
  1. Analysis
  2. AS-IS sign-off
  3. Conversion & build
  4. Testing
  5. UAT & acceptance
  6. Hypercare
How It Works

Six stages. People decide at every one.

At each stage, AI takes the repetitive work and people make the calls that need business judgment.

  1. 01

    Analysis

    What AI doesExtracts every screen, event, interface and SQL statement from the code and writes a guide for each screen.

    What people decideConfirm the business process map.

  2. 02

    AS-IS sign-off

    What AI doesLays out the evidence and proposes how portal-specific features should be replaced.

    What people decideDecide what to keep and what to change.

  3. 03

    Conversion & build

    What AI doesRebuilds screens, converts them to the new UI, generates project scaffolds and code, and verifies the build.

    What people decideReview the results and approve changes to SAP.

  4. 04

    Testing

    What AI doesGenerates and fills in test cases, turns one SAP GUI recording into an E2E test, and reruns regression every night.

    What people decideAccept or reject test cases.

  5. 05

    UAT & acceptance

    Planned

    What AI doesTakes in issues, links each one to its fix and tracks the retest.

    What people decidePass or fail the retest and approve out-of-scope requests.

  6. 06

    Hypercare

    Planned

    What AI doesTracks post-go-live issues and their retests.

    What people decideConfirm before changes reach production.

Skip a check, and the next step stays closed

  • AS-IS can’t be signed off until portal-specific features are decided.
  • No DB conversion code is generated without a workflow a person has confirmed.
  • With approval turned on, no SAP change lands without a second person’s sign-off.
  • When code changes, earlier test passes are voided automatically.

Find the right suite for your systems

Talk with our experts about your legacy platform and the best path forward.