# SAP PO Upgrade: Updating Process Orchestration 7.5 and Planning the Move to Integration Suite > Source: https://netray.co/erp-help/sap-po-upgrade-process-orchestration-7-5-sps-integration-suite-migration > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer SAP Process Orchestration 7.5 is the final release of the on-premise PO line, so a PO upgrade means applying support package stacks to 7.5 (typically with the Software Update Manager) and deciding when to migrate interfaces to SAP Integration Suite. Check SAP's current maintenance dates and the Product Availability Matrix before planning, because they have been revised. ## Kind advanced ## System sap ## Erp SAP Process Orchestration (PO / PI) ## Module Integration / SAP PO 7.5 / Integration Suite ## Query sap po upgrade ## Alternate Queries - upgrade sap process orchestration 7.5 - sap po 7.5 sp upgrade - sap po to integration suite migration - sap pi po end of maintenance ## Applies To SAP PO / PI 7.3x, 7.4 and 7.5 (Java stack). Maintenance dates and tool names should be verified against current SAP notes. ## Steps ### How to plan and run a PO upgrade **Items:** - Inventory the landscape: current release and SPS, number of interfaces, adapters, ccBPM and BPMN processes, and connected systems. - Check the Product Availability Matrix and SAP's maintenance statement for your release, and read the relevant SAP notes for the target SPS. - Generate the stack with the Maintenance Planner so versions of all components are consistent. - Back up the database and file system, and run the update first in a sandbox or test system that is a copy of production. - Apply the stack with the Software Update Manager (SUM) for Java, following the guide for your database and OS. - Run regression tests on critical interfaces: message flow, mappings, adapters, certificates, monitoring and alerts. Compare message counts before and after. - Schedule the production update in a quiet window, with a rollback plan, then monitor queues and the Integration Directory after go-live. - In parallel, classify interfaces for migration to SAP Integration Suite or retention on PO. ## Sections ### Upgrade versus migrate **Body:** Upgrading PO keeps your interfaces where they are, which is the lowest-risk option if the landscape is stable. Migrating to SAP Integration Suite (Cloud Integration) moves interfaces to SAP's cloud integration service, which is where SAP invests. The two are not exclusive: many companies patch PO to stay supported while migrating interface groups over several years. SAP provides migration assessment and tooling to analyze PO content and move suitable scenarios. Expect manual rework for custom adapters, complex ccBPM processes and anything relying on the Java mapping or adapter modules. ### Staying on-premise **Body:** Not every integration should leave the data center. Where interfaces carry controlled technical data or regulated records, companies often keep the integration runtime on-premise. SAP offers hybrid options such as Edge Integration Cell for running integration runtime in your own environment, which you should evaluate against your policy. Whatever you choose, document interfaces: owner, sender, receiver, volume, payload and criticality. That inventory is the real asset in any upgrade or migration. **Code:** - Tools: Maintenance Planner, SUM (Java), SAP Notes, PAM - Monitoring: NWA, Runtime Workbench / Message Monitoring - Design: Enterprise Services Repository (ESR), Integration Directory - Targets: PO 7.5 latest SPS, or SAP Integration Suite ### Risks to test for **Body:** Common upgrade risks are adapter incompatibility, certificate and keystore changes, changed Java versions, custom modules failing, and mapping runtime differences. Message processing performance can change after an update, so compare throughput under load. Keep a clean test of end-to-end flows with real connected systems where possible, because a technically successful update that breaks one receiver is still an outage. ## Pitfalls - Starting the update without a tested restore of the production system. - Treating PO upgrade and Integration Suite migration as the same project. - Not inventorying custom adapter modules and Java mappings before choosing a target. - Relying on remembered maintenance dates instead of the current SAP statement and PAM. - Testing only happy-path messages and missing error handling and alerting. ## Ai Angle Interface inventories are the hard part of PO work. A private AI layer over your PO configuration and documentation can answer 'which interfaces use this adapter or this certificate?' and draft the impact list. Netray builds such assistants on open-weight models running on your own hardware, so integration metadata stays inside your network. ## Faq ### What is the latest version of SAP PO? **Answer:** SAP Process Orchestration 7.5 is the final release in the on-premise PO line. Upgrading usually means applying a newer support package stack to 7.5. Confirm current SPS and maintenance dates in the Product Availability Matrix and SAP's maintenance statement. ### How do I upgrade SAP PO to a newer support package? **Answer:** Plan the stack in the Maintenance Planner, back up, then apply it with the Software Update Manager for Java, test in a copy of production first, and run regression tests on key interfaces before updating production. ### Do I have to move from PO to Integration Suite? **Answer:** Not immediately. Many companies keep PO supported while migrating gradually. The decision depends on maintenance dates, your cloud policy, interface complexity and whether you want to run integration on-premise or in the cloud. ### Can integration stay on-premise after PO? **Answer:** Yes, if your policy requires it. SAP offers options such as running an integration runtime in your own environment, and third-party platforms are another route. Evaluate each against your data residency and support needs. ## Search terms sap po upgrade, sap process orchestration 7.5, sap pi po upgrade, sap po sps update, sap po to integration suite, sap po end of maintenance, sap sum java upgrade, sap po migration --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json