Skip to Content
Technical Articles
Author's profile photo Alexander Bundschuh

Best practices Cloud Integration Content in SAP Process Orchestration – Product profiles

This is a blog within a series of best practices blogs for cloud integration content in SAP Process Orchestration. For an overview of all blogs published within this series so far, refer to the overview blog.

The following blog explains the product profile concept, and shows how you can check whether your content is supported on your SAP Process Orchestration system.

Before deploying the cloud integration content, you first need to check for which SAP Process Orchestration release and SP your content may be potential supported. This depends on the feature coverage of the particular release. Here, we have introduced the so called product profiles that allows you to use cloud integration content for different target integration platforms. A specific product profile restricts the configuration of an integration flow to the set of adapter types and integration flow steps that are supported for a particular release and SP of SAP Process Orchestration. Currently, we do support product profiles for SAP Cloud Platform Integration and SAP Process Orchestration, for latter we distinguish the various SPs. If you like to create or run an integration flow for your particular SAP Process Orchestration release and SP, you need to select the respective product profile. When you create an integration flow from scratch, a pop up comes up where you can select the product profile from a drop down menu. For an existing integration flow, you can switch the product profile on the Runtime Configuration tab of the integration flow. In any case, this has two effects. First of all, the modeling palette only shows those integration flow steps and adapters, to be more precise the particular version of the integration flow steps and adapters, which are supported for the chosen SP. Secondly, while saving an integration flow, checks are carried out, and errors are displayed in the modeling editor if a feature is used which is not supported. In case of an error marker, choose the next higher product profile version. You may eventually update your SAP Process Orchestration system.

Prerequisites

Ensure that the SAP Process Orchestration product profiles are enabled on your tenant. If this is not the case, you need to add the value igwpro to the parameter enabled.profiles in the tenant configuration. This can only be done by a tenant administrator. In SAP note 2428801 – FAQ: Cloud integration content in SAP Process Orchestration (PI), we describe how you can request that the product profiles are added to your tenant.

In your SAP Cloud Platform Integration tenant, switch to the Settings area. Note, only administrators can see this tab. If the enabled.profiles contains the value igwpro, you should see all the SAP Process Orchestration versions in the list of product profiles. We do support product profiles from 7.5 SP5 on.

Check supported product profile version

In the following, I use an eInvoicing integration scenario to show the supported product profile capability. Switch to the workspace of your tenant by selecting Design from the navigation pane, select the respective package, and click on the integration flow.

 

In the integration flow editor, switch to edit mode by selecting Edit on the upper right corner.

In the properties section of the integration flow, switch to the Runtime Configuration tab. By default, the SAP Cloud Platform Integration product profile is set. Select an SAP Process Orchestration product profile from the drop down menu, here we have chosen 7.50 SP07.

Save the modifications.

If the Integration Flow is not supported for the chosen product profile, an error marker is displayed within your editor. If you mouse over the error marker, more details are displayed. In our case, the Integration Process component with version 1.1 is not supported in 7.50 SP07. We do support version 1.0 only, support for 1.1 has been introduced with 7.50 SP08.

If you change the product profile to 7.50 SP08, and save again, the error marker is gone.

Assigned Tags

      11 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Naresh Bollepogu
      Naresh Bollepogu

      Hi

       

      I dont have option to set up new Product profile in settings. could you please suggest me.

       

      thanks,

      Naresh

      Author's profile photo Alexander Bundschuh
      Alexander Bundschuh
      Blog Post Author

      Hi Naresh,

      you need to create a ticket, see SAP note mentioned above under prerequisites

      Alex

      Author's profile photo Naresh Bollepogu
      Naresh Bollepogu

      Thanks Alex,

       

      I was assuming that  task configuration "Configure Process Integration" in HCP enables the Product profile. is it always a new ticket for new Product profile for PO system?

       

      Thanks,

      Naresh

       

      Author's profile photo Alexander Bundschuh
      Alexander Bundschuh
      Blog Post Author

      no, you need to raise the ticket only once to get the profiles added, whenever there is a new SP, the new profile will be added automatically

      Alex

      Author's profile photo Dijesh Tanna
      Dijesh Tanna

      Hello Alex,

       

      I'm going through the SAP S4HANA to field glass integration. The guide mentions that the content is "Configure-only mode". Does that mean , we can't change the Product Profile for the iflow & hence can't be deployed in SAP PO Cloud run-time.

       

      "SAP S/4HANA with SAP Fieldglass-This pre-defined package is in Configure-only mode,which means you can’t extend the middleware content as per your customized requirement.For more information, contact your SAP system administrator."

       

      Thanks & Regards,
      Dijesh Tanna

      Author's profile photo Alexander Bundschuh
      Alexander Bundschuh
      Blog Post Author

      You can also deploy content on PO without changing the profile, i.e., the CPI profile will do as well which is actually used for the standard content. So, for configure-only content, you can only figure out whether it may run on PO if you try to deploy (trial & error), if deployment end up in an error, it tells you what component or component version is not supported.

      Alex

      Author's profile photo Vijayashankar Konam
      Vijayashankar Konam

      Hello,

      Thanks for the blog. However, if an organization only has license to PO and not to CPI, in that case, how the organization could make use of the content without actually having a CPI tenant? Is that possible? Any suggestion would be appreciate.

       

      Thanks,

      Vijay Konam (VJ)

      Author's profile photo Alexander Bundschuh
      Alexander Bundschuh
      Blog Post Author

      Hi Vijay,

      sorry, this is not possible, for designing the integration flows you need a CPI tenant, you need to know that when we provide a tenant even if it is used for the design time only we do have operational costs, so we cannot provide a tenant for free

      Alex

      Author's profile photo Vijayashankar Konam
      Vijayashankar Konam

      Hope, it should be possible to ask for getting only a single tenant provisioned rather than whole landscape fro DEV to PROD. Any comment on that?

      Author's profile photo Alexander Bundschuh
      Alexander Bundschuh
      Blog Post Author

      this is up to you

      Alex

      Author's profile photo Dilip Mehra
      Dilip Mehra

      Alexander,

      Thanks for writing this blog. It just gave the very perfect explanation on product profile.Thanks.