Error when transporting Integration Flows via CTS+ or File

[Former Member]

Usage of Integration Flows for PI integration scenarios

SAP recommends using the newly introduced “Integration Flows” in NWDS (Eclipse). This is a very nice feature and has been described by Michal in the following blog:
http://scn.sap.com/community/pi-and-soa-middleware/blog/2011/11/09/pixi-eclipse-based-integration-fl...

Problem Description

When you try to transport an integration flow which refers to a predefined communication channel you will get an error during activation of the configuration objects in the Integration Directory.

The key of the communication channel contains a business system. After importing the integration flow together with the communication channel for the first time, the key of the communication channel is adjusted correctly according to the transport group definition in the System Landscape Directory. However, the reference of the integration flow to the communication channel is not adjusted. As a result, the integration flow loses the link to the communication channel and the consistency check reports the following error: "Referenced channel | | does not exist" (please refer to the screenshots below).

The error occurs after transport of the configuration objects and integration flow to the target system (for example from PI development system to the PI quality system).

The following export procedure is usually followed:

1. Selection of the Integration Flow (integration scenario) via the export wizard:

2. Wait till the transport creation is confirmed:

3. After the transport has been released and imported into the target system via CTS+ and the objects are tried to be activated, the following error will occur:

Solution

After a lot of discussions with the SAP support, the error was finally confirmed and the issue was forwarded to the SAP BC-XI-IBC (Integration Directory) development and support group.

The new SAP Note is now available since August, 19^th 2013 describing the correction. Please refer to the following link for the note:

https://service.sap.com/sap/support/notes/1901073