Frequently asked questions
Before you connect a tenant.
What CodeForge reads, what it generates, and where a human has to sign off.
Access & safety
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.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.
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.
How the pipeline decides
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.
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.
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.
Getting started
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.
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.
Use the “Talk to an Expert” link at the top of any page on this site — it goes straight to KloudData's contact form.