AiSolvEnd of mainstream maintenance for SAP Process Orchestration 7.5.
AISOLV FLOW / FOR SAP PROCESS INTEGRATION & ORCHESTRATION
SAP PARTNEREDGE BUILD PARTNERMove every SAP PI/PO interface to SAP Integration Suite. And prove each one behaves the same.
AISOLV Flow reads your standard PI/PO export, generates the Cloud Integration iFlows, deploys them to your tenant through SAP’s published API, and gives every interface a parity report: what PI does, what the new flow does, and every difference.
01 / YOUR SOURCE
SAP PI/PO
ES Repository and Integration Directory export (.tpz)
No connection to PI/PO02 / YOUR WORKSTATION
AISOLV Flow
AssessGenerateProve
03 / YOUR TENANT
SAP Integration Suite
iFlow, test mock and parity report per interface
Deployed and tested- Nothing installed in PI/PO
- SAP published APIs only
- SAP-delivered adapters only
- Nothing sent to AiSolv
- SAP PartnerEdge Build partner
01 / WHY NOW
Every PI/PO interface
has to move.
SAP’s direction for integration is SAP Integration Suite. Moving the platform is the easy part. The cost is in every interface: reading it, rebuilding it, and proving it still does what the business relies on.
End of extended maintenance for SAP Process Orchestration 7.5.
Every interface, understood.
Hundreds of channels, mappings and routing rules, often built by people who have moved on. Flow reads them all from the export and classifies each one.
Built the way Integration Suite expects.
Flow generates the iFlow from SAP-delivered adapters, with the message mapping translated and the fault path kept.
Evidence the business can sign off.
A parity report per interface lists what changed and what is still to be decided, so nothing reaches production on an assumption.
02 / HOW IT WORKS
From export to deployment.
With the evidence alongside.
Nothing is guessed. A value the export does not hold is flagged, never filled in.
Assess.
Reads your standard PI/PO export and classifies every interface: the Integration Suite adapter and pattern it maps to, what blocks an automatic move, and the effort, bottom-up.
Generate.
For each scenario the export describes completely, writes a Cloud Integration iFlow with SAP-delivered adapters, the translated message mapping, the fault path, and a test mock.
Prove.
Writes a parity report for every scenario: 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 Integration Suite tenant through SAP’s published API and calls each flow end to end against its test mock.
03 / THE PARITY REPORT
One report per interface.
Every difference shown.
The parity report is what makes a generated flow reviewable by your integration team, by the interface owner, and by your auditors.
- Every fact names its source. Each value says which export object it was read from.
- Missing values are flagged. Hosts, directories and credential names a PI export does not hold are marked to decide.
- Parity first. The new flow reproduces PI, including its quirks. Improvements are listed for you to agree, never applied silently.
Generated with 2 flagsPattern: asynchronous, point-to-point
- What PI does
- HTTP sender → message mapping MM_MaterialMaster_MATMAS → IDoc receiver ESR export · Integration Directory export
- What the new flow does
- HTTPS sender → translated mapping (script step) → IDoc receiver through SAP Cloud Connector Generated from tenant-captured adapters
- Differences
- None in the mapping logic. An empty description keeps its delimiter, as in PI. Kept for parity
- Improvements not applied
- Drop the delimiter for empty values. For the interface owner to agree
Decisions not taken from PI
- receiver addressTO_DECIDE
- credential nameTO_DECIDE
04 / ADAPTER COVERAGE
What Flow covers today.
And how far each is proven.
Tested on Java-only (AEX) and dual-stack SAP PI/PO systems. Every adapter Flow writes is copied from what an Integration Suite tenant itself saves, so the tenant accepts the content.
| PI/PO channel | Integration Suite adapter | Proven so far |
|---|---|---|
| HTTP | HTTPS | Run end to end |
| File content conversion (separated and fixed length) | Script step, generated from the channel | Run end to end |
| SOAP with XI protocol (ABAP proxies) | XI (synchronous and asynchronous) | Imported into Integration Suite |
| File | SFTP | Imported into Integration Suite |
| SOAP | SOAP 1.x | Generated |
| IDoc | IDoc | Generated |
- Run end to end
- Deployed through SAP’s published API and called with test messages. Results matched the reference.
- Imported
- Generated flow accepted by the tenant and opened in the Integration Suite designer.
- Generated
- Built from adapters captured from a tenant. Import and run against your back ends happen on your landscape.
NOT GENERATED YET
JDBC, RFC, Mail and JMS channels are assessed and flagged, with an HTTPS test entry point. ccBPM, and routing that is not point-to-point, are assessed and reported with the reason. These interfaces still get an effort estimate and a parity report to rebuild from.
- Same resultsA generated flow, deployed through SAP’s published API, returned the same results as the hand-built flow on every test case, including the fault path.
- Same outputGenerated file content conversion produced output identical to the reference for both separated and fixed-length files.
- Under load300 of 300 test messages correct at steady parallel traffic on a trial tenant. A correctness check, not a capacity figure.
05 / HOW IT WORKS WITH SAP
Your SAP landscape.
Published interfaces.
Flow analyzes the export offline, delivers content through SAP’s published APIs, and keeps every credential in your tenant.
SAP PI/POESR + Directory export
file, onceYour workstationAISOLV Flow
SAP Integration Suite · your tenantCloud Integration content API OData · OAuth 2.0 → package → iFlow → deploy
SAP Cloud ConnectorOn-premise access
SAP-delivered adaptersYour back endsSAP ECC · SAP S/4HANA · file servers
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. On-premise 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 shortcuts into SAP.
No direct database access. No unreleased APIs. No screen automation.
06 / SECURITY, DATA & REQUIREMENTS
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 the exports.
Credentials stay out.
Credential fields in channel configuration are never copied into reports. API keys are typed at a prompt and never stored.
Least privilege.
Exporting needs display and export rights only. Deploying needs edit and deploy rights in one package, nothing more.
WHAT YOU NEED
- SAP PI/PO
- A user who can export from the ES Repository and the Integration Directory. Java-only (AEX) or dual-stack.
- SAP Integration Suite
- A tenant with Cloud Integration and a service key for the content API. A test tenant is enough to start.
- SAP Cloud Connector
- Only for flows that reach on-premise systems. Configured by your Basis team.
- Workstation
- Windows, macOS or Linux with Python 3.10 or later. No other dependencies.
07 / GETTING STARTED
Start with your export.
See your own interfaces.
It starts on your landscape, your interfaces and your test tenant. You see the assessment before anything is built.
- 01
Send the export.
Your team exports the ES Repository and Integration Directory objects in scope. No access to your PI/PO system is needed.
- 02
Get the assessment.
Every interface classified, with its target adapter, its blockers and a bottom-up effort view.
- 03
Generate and deploy.
Selected interfaces are generated, deployed to your test tenant and called end to end.
- 04
Review parity.
Interface owners review each parity report and decide the open values before anything moves toward production.
08 / QUESTIONS
What teams ask first.
Do you need access to our PI/PO system?+
No. Flow works from the standard export files your team produces with SAP’s own export function. Nothing is installed in PI/PO and no connection to it is opened.
What happens to interfaces Flow cannot generate?+
They are still assessed. The report states why the interface was not generated, estimates the effort, and lists what PI does, so the rebuild starts from a specification instead of a blank page.
Are the generated flows ready for production?+
They are ready to deploy and test. Before go-live your team fills the values flagged to decide, deploys the security material the flows reference, replaces the test mock with the production receiver, and transports the content through your landscape.
Where does our configuration go?+
Nowhere outside your environment. Flow runs on your or your delivery team’s workstation and sends nothing to AiSolv or any third party. Reports name hosts and users from your configuration, so they are kept in your project repository.
Does it change how our interfaces behave?+
Not without your decision. The generated flow reproduces what PI does. Any improvement is listed separately in the parity report for the interface owner to agree.
09 / PART OF AISOLV
One module.
A broader conversion toolset.
AISOLV Flow is one module of AISOLV, AiSolv’s toolset for SAP ECC to SAP S/4HANA conversions.
- Fit · processes
- Shift · custom code
- Guard · security
- Tile · Fiori
- Case · testing
- Flow integration
- Data · migration
- AI readiness
SAP PI/PO → SAP INTEGRATION SUITELet’s look at
Let’s look at
your integration landscape.
Proven on SAP PI/PO systems and SAP Integration Suite. Bring your export.
AiSolv is an SAP PartnerEdge Build partner.