Skip to Content

Upgrade Options to the Latest Process Integration or Process Orchestration

Recently, there have been a lot of questions and confusions over the options available for customers to upgrade to the latest version of Process Integration (PI) or Process Orchestration (PO).

These confusions came mainly from PI customers with volume-based licenses.  And, these customers want to upgrade to PO.

Let us first look at the basic product information for Process Orchestration (PO):

  • PO is a bundled product of PI, Business Process Management (BPM) and Business Rule Management (BRM).
  • PO is licensed based on CPU.
  • With PO, PI can be installed as dual-stack or single-stack (AEX).
  • If PI is installed as AEX, PO can be installed using the same system ID (SID), meaning PI, BPM and BRM are installed on one JEE server.  This will improve TCO due to savings in hardware, support and administration.  There are also performance improvements due to internal processing of messages between PI and BPM/BRM.
  • AEX can also be installed by itself on one SID, with BPM/BRM installed on a different SID.  With this option, BPM/BRM cannot be added to AEX at a later time; a new installation will be required.  (In my opinion, this is not recommended for a PO license unless there is a special reason to do so.  However, this might be a valid path for PI volume-based license as stated below.)
  • If PI is installed as dual-stack, then PO, PI and BPM/BRM, will have to be installed with different SIDs.  PI on one SID and BPM/BRM on a different SID.

For PI customers with CPU-based license, they can go to PO by converting their license from PI to PO.  Generally speaking, this is a direct license conversion. 

For PI customers with volume-based license, below are the options:

Option 1 Convert the license from volume-based to CPU-based.  Contact your Account Executive to convert these licenses and apply credits as appropriate after dimensioning existing usage to CPU.
Option 2
  • Continue to upgrade to the latest release of PI under the existing volume-based license.  The PI installation can be dual-stack or AEX.
  • License BPM/BRM separately.
  • Installation of PI and BPM/BRM must be on separate SIDs.
  • In order to install PI, BPM and BRM on the same SID, the license must be converted from volume-based to CPU-based.

The bottom line is that PO is a bundled product of PI, BPM and BRM.  It can be installed using different options, with a single SID or 2 SIDs.  To install as a single SID, PO must be licensed.

You must be Logged on to comment or reply to a post.
  • Hi William,


    this is an excellent blog and couldn't have come at a better time as  we are currently planning to take our dual stack PI 7.1 to single stack Java 7.3x in Q1/2 2013.


    Thank you and all the best,



  • Thanks for the really clear product explanations!


    Do you know if there are any mechanisms to protect performance in PI if all 3 are loaded in the same SID? In otherwords, are there any technical ways to give priority to PI so that important synchronous interfaces are not becoming unreliable due to resource swings that may come in from BPM or BRM?

  • Hi Bill,


    This helps.

    One quick question, for the PO Installation (PI + BPM + BRM), there is no need for an extra AEX component, right ? This should be selected automatically with the installation type ?




  • Hi William,


    Thanks for making things a bit clear There seems to be lot of confusion going on around especially with the 3 products clubbed together (BPM + BRM + AEX/PI).


    How does all this PO tie in with SAP CE?


    In our case, we have a standalone PI 7.30 (dual stack) installation and a separate CE (7.20 SP 6) installation. There are applications built in SAP CE using both Netweaver BPM and BRF rule engine.


    If we want to develop BPMs, would you suggest doing it in ccBPM or use CE BPM? I understand from a strategic view, it makes more sense to go for CE BPM. But if I do, would I still be able to use mappings in PI? Or this is only possible in PO?




    • Hi Jai,

      BPM development should definitely target CE BPM, not ccBPM.


      PO is a license which includes PI, BPM and BRM.  From this blog, it can be installed in any of the 3 options outlined above.  However, if BPM is to use the mappings developed in PI, you must install PO using a single SID.




  • Hi William,


    We have installed SAP CE instance (BPM, BRM usage types).

    Can we install / upgrade / put Process Orchestration add-on to same instance keeping same SID?


    We did put usage type PI-AE which is PI component on same instance but this is not what we need. We are looking for PO installation on same existing CE instance.


    Please suggest.



    Mandeep Virk

  • Hi William,

    We have several interfaces using ccBPM in current PI 7.11 and currently we are planning to upgrade it to PI 7.31.

    If we go with  only Java and we need to redesign all of them, instead of that, if we just upgrade upgrade PI to 7.31 and install BPM and BRM saparately, do you think we will be able to use all PO functionalities?




    • BPM/BRM can be installed on a separate server.  You will not be able to use the SOAP/XI protocol between PI and BPM.  You will need to use the WS adapter.


      Also, since you will have the PI dual-stack, the Eclipse iFlow tool cannot be used.  It can only be used with the java-only installation.




      • Are you sure William that in 7.31 PI double stack the usage of WS-RM to connect to a separate instance of BPM/BRM 7.31 is still mandatory? I thought SOAP only communication was now enabled...

        • SOAP is an option that can be enabled, but not recommended.  WS provides reliable messaging, and so does the SOAP/XI30.  SOAP by itself does not.


          However, SOAP/XI30 can only be used for AEX and BPM, not dual-stack and BPM.




          • Hi William


            Working with one of the SAP’s Partner here in the UK, I have had few good opportunities/projects to work for SAP BPM (SAP NW 7.3 with EHPx)   implementation/installation and upgrade projects.


            Recently, for one of our customer I had chance to install PO system, i.e SAP Netweaver Process Orchestration (PI+BPM+BRM) 7.4 with SP03.


            In the previous BPM version (i.e. until SAP Netweaver 7.3 with EHP n), we could select “usage type” components while installation & this way we can select required components like ADOBE with other components.


            But for PO installation (by default NW 7.4 PO comes SP02), there is no option for selecting the components but it gets installed by its default selection as PO system except Adobe component.


            How we get Adobe functionalities?, while I upgraded to SP03 (from default SP02) also the MoPz didn’t pick it up for Adobe components.


            Why SAP removed Adobe component from the default installation?, is it not required for PO or if it is required by manual deployment ?


            Also the PO installation (Process Integration and Orchestration Package) from SAPInst menu also bit confusing, it says “Optional standalone Units”, any reason for this as well?


            Best Regards


  • William-


    This information is very useful for customer using PI. In this regard have a question for you. One of our customers are using PI 7.1 dual stack as you mentioned above they have 2 licensing options based up on their usage types. In their PI landscape they have lot of BPM connecting legacy systems. If we migrate to latest version of PI following scenarios

    • CPU based licensing
    • Volume based licensing


    How difficult it would be to leverage the existing BPM in both the above scenarios. It would be really appreciated if you could provide me details how to handle BPM's in 2 scenarios.



    Please let me know



    Hari Sonnenahalli

    • Hi Hari,

          I can try to help you with this question. Customers can continue to use PI as is and upgrade to the latest and greatest version leveraging the dual stack or single stack deployment option without any licensing event. But they need to limit themselves to PI functionality. BPM per se is not a function of PI and as such, it cannot be used without properly licensing it. So if your customer wants to continue to use PI 7.4 functionality, it does not matter if they originally licensed PI with the CPU or volume based metric. SAP grandfathers how the customer licensed and they can continue to license more on that metric.

          Now, the conversion comes when the PI customer wants to use more than PI functionality. For example, they may want to use BPM, BRM or the B2B Add-On. In this case, they can:

          - Convert their existing PI licenses (volume or CPU based) to the PO (core based) license. The customer assigned Account Executive can help you with how this conversion works, but this follows pretty standard rules at SAP (you get credit for what you paid and this is applied toward licensing the new material number (in this case PO core-based). Another example why a customer may want to convert PI to PO is because they may want to leverage the B2B Add-On that now is part of the Process Orchestration package.

          - License a side PO installation for the BPM use cases. Again, this is something that needs to be addressed by the Account Executive but it is technically possible.

          If this does not answer your question, please do not hesitate to reach out to me.




      • Eduardo-


        Thank you very much for providing me insight on licensing for PI customer and will work with respective account executive to understand customer licensing.  But my questions was more on technical aspect that is already our customer is using BPM with 7.1 sp06, I think they have licensed BPM at some point of time when they purchased PI 7.1 Considering that if our customer wants to use PO which a bundle of BPM and BRM, Than how difficult is to migrate existing BPM in 7.1 to PO installed on dual stack or all the BPM’s need to be rebuilt.


        Please let me know your valuable feedback.





  • Hi William,


    Thank you for nice detailed information. I have a query on your comments as a below.


    "If PI is installed as AEX, PO can be installed using the same system ID (SID), meaning PI, BPM and BRM are installed on one JEE server.  This will improve TCO due to savings in hardware, support and administration.  There are also performance improvements due to internal processing of messages between PI and BPM/BRM. "

    Does this match my below situation.  Please correct me in case i am wrong..

    Currently we have PI7.3(sp4)dual. We are planning to go upgrade to 7.4, but for PO licensing, it is planned next year. Meanwhile, I plan to migrate to PI 7.4 (AEX).


    My doubt is, later,


    - Can I move from AEX 7.4 to PO 7.4 with install of the BPM+BRM+B2B Add-on on the same system without affecting the existing mapping & configuration. ( shouldn't have any Development effort for changes/testing). Little confused here, as i also understand BPM/BRM can be installed with same SID,but a different server.


    - Or Does it require a complete new install of PO 7.4 and migrate the

    mapping & config of existing PI 7.4 AEX.




    • Hi,

      Yes, with a PO license, you can deploy BPM, BRM and B2B onto the existing AEX 7.4, under the same SID.  All design and configuration artifacts in AEX will remain unchanged.


      You can also install BPM and BRM on a different server, but must have a different SID.




  • Hello William,

    When the PI and BPM are in different SID how will the call to BPM from PI be made. Any related blogs for the configuration?Thanks





      • Hello Alex,

        Do you have any configuration document for calling BPM (BPM running on PO) from PI Dual Stack system (PI dual stack and PO systems are installed with different SID's).


        What connections are required between PI dual stack and PO java stack for calling BPM from PI system?




        • Hi Sudhakar,


          in BPM you either have a message start event or an intermediate message event to send messages to a BPM process, either way you need to define a trigger where you define the service interface whereas the corresponding service reference needs to be of type WS. Once you have deployed your process, open the NWA and navigate to SOA --> Application and Scenario Communication --> Single Service Administration. On the Service Definitions tab search for your interface / WSDL Port Type Name. From here you can access the WSDL url and the service endpoint url. On PI, you need to create a channel of either WS or SOAP type where you maintain the very service endpoint url.



  • Hi ,

    The scenario we have tried out goes like this: PI calls BPM in PO (both are in different system ids) . However there is no response sent back from  PO to PI . Soap is being used for the calls. Is there any step required to be added in the BPM  for this to be achieved. Can anyone help out here? Thanks





    • Hi Pavithra,


      not sure if I understand your question properly. Do you mean that you expect a response when calling BPM but you don't get any? Well, this depends on your service interface of your message event. If you like to call the BPM process synchronously, your service interface needs to be sync. In this case assign the trigger of the message start event to your message end event, and in the input mapping of your message end event map the response context to the response message type. For an example, check out this document on SCN



  • We have several interfaces using ccBPM in current PI 7.31 (dual stack). We are planning to install BPM and BRM separately for PO functionality.. I saw in previous comment that we cannot use the eclipse iflow in such scenarios..


    Are there other limitations of such an approach? Does this approach impact any existing scenarios on our PI 7.31 system?

    • Hi Krish,


      I do not fully understand your question. Do you intend to deploy BPM/BRM on top of a PI dual stack system? This is actually not supported.

      If you however plan to run BPM/BRM on a separate system, please see my comment above about how to connect BPM/BRM with PI. Be aware that in this case, monitoring wouldn't be integrated, i.e., it wouldn't be possible to navigate from the process instance within the process monitoring to the related messages in the message monitoring.



      • Hi Alex,

        I meant BPM/BRM on separate system. I had read somewhere that some capabilities of PO (like java gateway ) to expose backend ECC services as ODATA are possible only with single instance.. wanted to check if that was true?





        • Hi Krish,


          this is true, Gateway Java component for PI is only supported on PI Java Only deployment options, i.e., either SAP Process Orchestration or Advanced Adapter Engine Extended, it is not supported on PI dual-stack.

          Furthermore, as of 7.4 SP4 we have enhanced the PAM to support running PI Java Only on HANA DB, whereas PI dual stack on HANA DB is not supported.

          I have just updated SAP note 1515223, it's currently in status for checking and released for customer soon. Here, I have listed the major new features that we have recently shipped with the latest releases, also highlighting what is supported with SAP Process Orchestration in comparison to PI dual stack.


  • Hi,

    We are planning migrate PI 7.11 to PO 7.4. So we would migrate component from 7.11 to 7.4 and start using that in production one by one and until all components are successfully migrated.

    So since during the project both PI 7.11 and 7.4 would be live, Would that cause license violation, if we have CPU based license?



    • Hi Vik,


      for SAP Process Orchestration, only core based licensing is supported. Please get in touch with your account executive or sales representative to discuss licensing matters, and potential license conversion and credit.



  • Hi all / Alexander Bundschuh / William Li


    we are on PI 7.4 AEX SP 7. We currently have volume based licensing. We still have an old PI 7.0 Double Stack where we are migrating scenarios over to the new PI 7.4


    I'm aware that the combined volume of both PI systems count. However, I cannot find some counterpart for report SXMS_XI_AUDIT_DISPLAY or transaction USMM in PI 7.4 AEX. Performance Monitoring only reaches back to the start of this year.


    Many thanks and kind regards


  • Hi All,


    If anyone plans to upgrade from 7.3 Dual stack to PO, in 7.3 has interfaces on both ABAP and JAVA. Which of the below would be good possible approach, and are there any further recommendations.


    1) Migrate all at once to PO and go live(switch to PO at once)


    2) Phased approach: This has the New PO standing in parallel to Old 7.3 dual stack. ECC to use both PO and PI7.3 systems. Migration of interfaces happen in Phases, each phase has a set of interfaces, that will move to PO and go live.  Once all the interfaces move from PI7.3 to PO, then old systems to be retired.


    There are some threads, showing possibility of ECC pointing to 2 PI systems.


    Many Thanks,


    • Hi Venkat,


      According to my experience it would be good idea to go in "Phases approach" where you can migrate less critical interface first and once everything works file you may plan for next batch. There is one more advantage to go with parallel two PI approach.. In case if you face any issue and it is not getting resolved or needs SAP support then you can switch back to older PI for the interface until the issue is resolved.


      Thanks& Regards,

      Binod Kumar

      • Hi Binod,


        Thanks for reply. Yes this is correct for Phased approach as you said. I have a question, lets say if we plan to do all at a shot, i.e switching to new PI in prod. For this we first do everything in Dev with complete test, and similary test in every environment. We prepare the new PI in production well in advance but disable channels. During the Golive we switch to new PI. We always keep a fall back plan for the old system. I think this can be done possible if there is thorough testing in Pre Prod.


        Does anyone anticipate any risks here.! I am just trying to have the pros and cons in both approches.


        Many Thanks,


    • Venkat-


      I am currently migrating from dual to single for one of our client. It depends up on complexity of the landscape to make a call if you need perform a phase migration or complete migration. If the landscape is simple meaning no BPM, no Tables in PI ABAP stack, No ABAP mappings then you can take a shot at complete migration using SAP migration tool. If the landscape is complex with integration as mentioned above then it would be easy to do a phase wise migration.


      Pros of Phase wise migrations


      • Easy to manage object list for migration
      • Easy to track defects as it is done in phases
      • Easy to resolve issues


      Cone of Phase wise migrations


      • Cost of migration would be more as resource need to spend more time
      • Go-live would be in phases for which you need to set expectations with client so that they can plan accordingly
      • Decommissioning of the existing system can’t be done immediately.


      Hope this helps!!





        • Hi Venkat,


          Hari has already mentioned most of the points.


          I would like to add and suggest that in case if you want to go with one shot approach then you have to be sure that you have done testing using your production box as well in controlled and agreed manner with your client for all possible interfaces in advance before going live. This would be difficult to make your client agree but sometimes if they agree life becomes easy or else you may also connect your planned live PI box with your SAP / third party test/sandbox system to see if everything is working fine in Live PI system before go live.


          Things gets difficult when you have connections where you are using certificates and these kind of connections cannot be confirmed to be working when tested from different system for production.


          You can group interfaces related to same third party or similar system in case if you want to go in phases.


          Please also make sure that all the proxy interfaces have been migrated in one batch when you plan for phases approach. Or else handling two PI for proxy will become bit tricky for runtime.




          • Hi Binod,


            Thanks for comments. Yes what you said is true. Regarding the Production for test, Client wont agree. We have to go with alernative. We are finalizing the approach.





        Hi Hari,

        Thank you for all your points and its very informative.

        one query regd. Go-live time, we are planning to have phase wise migration, during that PI and PO both would be operative.

        In this case, do we need to buy temp. license to operate for PI and PO , or existing license works ?

        Thank you.