One platform for every path to SAP Clean Core.

SAP is retiring PI/PO. Years of custom ABAP were never fully documented. CodeForge scores your whole landscape, writes the missing documentation, and generates deploy-ready fixes for what's safe to automate with an architect reviewing everything else.

14 63 26 33 66 1 18 48 7 17 82 79 70 35 49 27 39 6 14 36 3 8 12 46 23 61 5 59 74 56 51 31 51 12 48 58 11 47 96 62 35 57 8 21 10 1 63 33 10 4 93 59 37 58 9 8 45 61 93 25

Full inventory

Every interface or object, documented as it's scored

Tiered by complexity

Low, moderate, and complex, scored consistently

Human-gated

Every non-trivial item reviewed by a KloudData architect

PI/PO Migration or Custom Code Remediation?

CodeForge isn't two separate products — it's one platform that applies the same scoring, documentation, and review discipline to both problems. Most SAP shops eventually need both; start with whichever is more urgent.

PI/PO → BTP Integration Suite

Every interface in your Integration Directory export, inventoried, scored, migrated to an Integration Suite iFlow, and proven to match its original behavior before it deploys.

2027 end of mainstream maintenance is the forcing function

Handles custom Java UDFs and Groovy, not just template-shaped interfaces

Every interface documented, including ones nobody currently maintains

Custom Code Remediation

Every custom Z-object in a package, inventoried, documented, scored for Clean Core readiness, and remediated toward CDS, OData, or RAP with a defensible effort estimate.

S/4HANA and BTP ABAP Environment readiness, not a one-time cleanup

Read-only access — no write authorization required to assess

Documents Z-programs written years ago that nobody currently understands

Built for the person who has to
answer for this landscape.

Time and cost

A manual assessment of a landscape this size takes months of consultant time. CodeForge inventories and scores it in days, so your team spends its time on the decisions that actually need a person.

Visibility you didn't have

Interfaces and Z-programs built years ago, by people no longer at the company, get documented alongside everything built last quarter — so you finally have a real inventory, not institutional memory.

Nothing ships unreviewed

CodeForge auto-generates the straightforward cases. Anything more complex gets a clear recommendation and a named KloudData architect's sign-off before it goes anywhere near your BTP tenant.

Before you connect a tenant.

What CodeForge reads, what it generates, and where a human has to sign off.

What access does CodeForge need to my SAP system?

For PI/PO, CodeForge reads an exported Integration Directory — no live connection to your PI/PO system is required for analysis. For ABAP, it connects read-only via the ABAP Development Tools (ADT) REST API with S_DEVELOP ACTVT=03 — display-only authorization, no write access. Nothing is modified in either source system during assessment.

Does CodeForge write anything back to my SAP system?

Not to the source system. The only write target is your BTP tenant — Integration Suite for PI/PO migrations, BTP ABAP Environment (Steampunk) for ABAP remediation — and only for artifacts you've explicitly approved and chosen to deploy, one at a time.

Where does my code and configuration go?

Source content is used to generate and test migration artifacts for your engagement. It isn't used to train shared models, and isn't shared across customer engagements. Your KloudData team can walk through the specific data-handling terms for your engagement.

What determines whether something is LOW, MODERATE, or COMPLEX?

A documented, repeatable scoring methodology — not a black box. For PI/PO, it factors mapping steps, script size (Java UDFs, Groovy), and adapter types. For ABAP, it factors violations against Clean Core rules, dependencies, and object size. The same three tiers apply either way.

What happens to COMPLEX interfaces or objects?

CodeForge doesn't attempt to auto-generate these. It produces an architecture blueprint and an annotated skeleton for a human architect to take from there — the tool tells you where the real engineering effort is, rather than guessing at it.

Is a MODERATE or COMPLEX result reviewed by anyone, or just the software?

Always by a named human. Every artifact above LOW complexity is gated behind an explicit reviewer sign-off before it can be deployed — the audit trail records who approved it and when.

Can I see CodeForge running before committing to anything?

Yes. KloudData can walk you through a live session against a sample landscape — the scoring, documentation, and generation flow — before you decide whether to point CodeForge at your own system. Ask for this when you talk to an expert.

Do I need PI/PO Migration and Custom Code Remediation, or can I start with one?

Start with whichever is more urgent. PI/PO has a fixed deadline (end of mainstream maintenance in 2027); Custom Code Remediation is a standing readiness question for your next S/4HANA move. Most SAP shops end up using both, but they're scoped as independent engagements.

How do I talk to someone about my own landscape?

Use the "Talk to an Expert" link at the top of any page on this site — it goes straight to KloudData’s contact form.

Ready to see your own landscape?

Talk to KloudData about scoping an assessment for your PI/PO interfaces, your custom ABAP, or both.

Talk to an Expert