Infovira
SAP Process Orchestration to SAP Integration Suite

See what it takes to move your SAP PO landscape to SAP Integration Suite.

Drop in your Integration Directory export, and your ESR export if you have it. In seconds you get your interface count, a migration category for each interface, the risks we see and a rough effort range.

  • Runs in your browser
  • Nothing is uploaded
  • No SAP tenant or connection needed

Drop your .tpz export files here

Integration Directory export required, ESR export optional. Several files at once, or one .zip holding them all.

How do I export from SAP PO?
  1. Integration Directory (required). Open the Integration Builder (/dir) and choose Tools > Export Configuration Objects, using the file system. Choose all objects of your communication components (or of your configuration scenarios) and untick Include Deleted Objects. You can export in several parts and drop all the files together.
  2. ESR (optional, for mapping detail). Open the Enterprise Services Builder (/rep) and choose Tools > Export Design Objects. Pick your own software component versions, the ones ending "of <your company>". Skip SAP’s own, such as SAP BASIS or SAP APPL.
  3. PO writes the files on the server. Ask your Basis team to copy them from:
    /usr/sap/<SID>/SYS/global/xi/directory_server/export/
/usr/sap/<SID>/SYS/global/xi/repository_server/export/
  4. If an export stops with "Software component version … not found", a channel points at an adapter from an older release. Leave that channel or component out and export again.
– days until SAP PO 7.5 mainstream maintenance ends (31 December 2027)
– days until optional extended maintenance ends (31 December 2030)