Every PI/PO migration hits the same wall: a list of interfaces SAP's own Migration Assessment tool flags as "Evaluation Required," and stops there. This session is a practical playbook for what happens next.
What this session walks through
The session
This session is a practical playbook for triaging your "Evaluation Required" list quickly, deciding the right fate for each flagged interface using a retire/replace/redesign/rehost framework, and walking through one real interface from flag to a running iFlow. It also covers what most migration plans miss: building contingency into effort estimates that carry the widest uncertainty in the whole project, and making sure monitoring, alerting, and failed-message handling are rebuilt before go-live, not discovered after it.
What you'll learn
How to triage your "Evaluation Required" list in minutes, not weeks, by recognizing the rule patterns that push an interface into this category.
A practical framework — retire, replace, redesign, rehost — for deciding what to do with each flagged interface.
A live walkthrough of one interface, from flag to a running iFlow.
How to plan contingency for the widest effort-estimate deviations in a PI/PO migration.
What to rebuild in monitoring, alerting, and failed-message reprocessing before you call it cutover.
Where the line still sits — what remains a manual architectural call, even with help.
The framework
Retire
Is the interface still in use? If not, it doesn't migrate at all.
Replace
Is there standard content or an existing API that already does this?
Redesign
Rebuild it natively in Integration Suite instead of lifting it as-is.
Rehost
Carry it forward with minimal changes where redesign isn't worth it.
Your host
Speaker name — TBA
Title — TBA, AiFA Labs
Details on our host for this session are coming soon.
Join AiFA Labs live for a practical playbook on clearing your "Evaluation Required" backlog — from triage to a running iFlow.
Save your seat →