This presentation shows how to migrate from SAP XI/PI to PO/PRO. from a dual stack system to a single stack system. Read more at https://figaf.com/qn9s

1. 7 steps to SAP PRO migration

2. Why migrate
• Get a simpler platform
• Different license form
• Not make anymore legacy interfaces
• Get continued enhancements
• Business case?

3. 7 Steps to migration

4. 1. Goals for the migration
Why are you migrating
1. Speed/Performance
2. Clean up
3. Simplify
4. Learning
5. Licensing

5. 2. Current integrations
1. Volumes for all interfaces
2. What is used. What can be removed. Yearly interfaces challenge.
3. Sync can be difficult to monitor
4. Business dialog is all used components
5. Map message into criticality, time, message
6. Map the used patterns used

6. Relevant fields
• ID
• Scenario
• Sender
• Interface
• Namespace
• Receiver
• Sender Interface Type
• Receiver Interface Type
• Number of ICO
• Number of mappings
• Messages last month:
• Criticality: Will the business break if this interface fails
• Urgency: Can we wait to fix this in two days
• Message volume/payloadsize
• Pattern: Async-sync, collect
• Estimation: Migration estimation
• Challenges: Missing password, business information
• Status: How is the migration going

7. 3. Pattern mappings
Pattern could be Sync/Async, RFC webservice enablement
1. If I was to start over on this how would I do it
2. Which can be removed
3. Updated to better performing
4. Should it be moved to gateway
5. New things to learn, ICO, AS2 adapter, SFTP, Modules, B2B Add-on.

8. 4. Resource consumptions
1. How many developers do you need
2. Can handle internal or extern resources
3. Is it core or can we handle it with knowledge transfer
4. Business involvement

9. 5. Migration phases
1. First POC test new server works not critical, few messages.
2. Ramp up to take high volume, to get feeling of how it performs.
3. Critical interfaces
4. All the rest
5. Changes to existing interfaces. If they change you need to migrate
them. Save the testing

10. 6. Development
1. Move swcv. Consider
2. Move java modules/adapters Rework? NWDI
3. SAP Migration tool
4. Channels migration
5. Update documentation
6. Test
7. Transport

11. 7. Test
1. Don't want to involve business/partners in testing. If possible
2. Easy to collect the test data.
3. Collect test data
4. Prove nothing is changed
5. Tool to support and document test

12. Big frustration with testing
• Testing with the business
• Picking out real productive data
• Business test to little PI relevant
• The want to make the simple one line document. Does not cover the
complexity of the business.

13. The fast SAP PI test tool
https://figaf.com/irt
Integration Regression Tool

14. https://figaf.com/qn9s
Read more