AiSolvAssess.
Reads your standard PI/PO export and classifies every interface: which Integration Suite adapter and pattern it maps to, what blocks an automatic move, and the effort, bottom-up.
AISOLV / SAP INTEGRATION MIGRATION
IN PILOTAISOLV Flow
Move SAP PI/PO integrations to SAP Integration Suite, with every difference shown.
AISOLV Flow reads your SAP Process Integration / Process Orchestration content and turns it into SAP Integration Suite content you can deploy and test, with a parity report for every interface stating exactly what changes.
YOUR SOURCE
SAP PI/PO
ES Repository + Integration Directory exports
Design-time configurationON YOUR WORKSTATIONAISOLV Flow
AssessGenerateProve
YOUR TARGET
SAP Integration Suite
Deploy and test in your tenant
Cloud Integration iFlowParity reportTest mock
Every difference shown. Every missing value flagged.
No installation in PI/POPublished SAP APIsYour workstation. Your tenant.
01 / WHAT IT DOES
From export to deployment.
With the evidence alongside.
Every interface gets a parity report. Nothing is guessed. A missing value is flagged, never filled in.
Generate.
For each scenario that can be read completely, produces a ready-to-deploy Cloud Integration iFlow: SAP-delivered adapters, translated message mappings, the fault path, and a test mock.
Prove.
Every scenario comes with a parity report: what PI does, what the new flow does, every difference, and every value still to be decided.
Deliver and test.
Deploys the content to your own Integration Suite tenant and tests it end to end.
02 / SUPPORTED TODAY
A clear path for
your interfaces.
Java-only (AEX) and dual-stack PI/PO systems are both supported.
| PI/PO channel | Integration Suite adapter |
|---|---|
| HTTP | HTTPS |
| SOAP | SOAP 1.x |
| SOAP with XI protocol (ABAP proxies) | XI (synchronous and asynchronous) |
| IDoc | IDoc |
| File (including content conversion) | SFTP, with the conversion generated |
Automatic generation applies to scenarios that can be read completely. Blockers and undecided values remain visible in the assessment and parity report.
03 / HOW IT WORKS WITH SAP
Your SAP landscape.
Published interfaces.
Analyze the export offline. Deliver the content through SAP’s published APIs. Keep credentials in your tenant.
Nothing installed in your PI/PO system.
Analysis runs offline from the standard ES Repository and Integration Directory export, which you produce with your own user.
Published APIs only.
Content is delivered through SAP Integration Suite’s published Cloud Integration content API, with OAuth 2.0.
SAP-delivered adapters only.
Generated flows use SAP-delivered adapters. Back ends are reached through SAP Cloud Connector.
No credentials in content.
Flows reference credentials by name; the secrets stay in your Integration Suite security material.
No direct database access.
No unreleased APIs. No screen automation.
04 / SECURITY & DATA
Your configuration.
Under your control.
Runs on your own or your delivery team’s workstation. Nothing is sent to AISOLV or any third party.
Design-time only.
Reads design-time configuration only. No business messages are read from exports.
Credentials stay out.
Credential fields in channel configuration are never copied into reports.
Runs where you work.
Analysis runs on your own or your delivery team’s workstation. Content is deployed to your own Integration Suite tenant.
05 / PART OF AISOLV
One module.
A broader conversion toolset.
AISOLV Flow is one module of AISOLV, a toolset for SAP ECC to SAP S/4HANA conversions.
- Processes
- Custom code
- Security roles
- Fiori
- Testing
- Data
- AI readiness
- Integration Flow
IN PILOTLet’s look at
Let’s look at
your integration landscape.
Proven on SAP PI/PO systems and SAP Integration Suite.
AISOLV is an SAP PartnerEdge Build partner.