New Pipeline for Cloud Integration features with version 1.0.11
Version 1.0.11 of the Process Integration Pipeline package for Cloud IntegrationCloud IntegrationBuilds and runs integration flows that process, route and map messages between cloud and on-premise systems, SAP and non-SAP, through prebuilt adapters; available only under an SAP Integration Suite plan.sap official, btp changes two defaults the post says require attention. The "tilde option", which built a partner ID by joining the sender system and interface names, is now switched off: a message whose partner ID cannot be resolved through an alternative partner goes into an error that is resolved by fixing the Partner Directory entry and restarting the message, instead of being constructed under an ID that may not exist there and left on the first JMS queue with no way to correct its partner ID header. Keeping the old behaviour means setting the externalised parameter CustomXPid_SwitchOffTilde to false in the five generic flows that call the partner-ID script; the default inbound processing queue also moves from PIPQ01 to PIPX01 in the generic XI and IDoc inbound flows, so those messages go to the integrated messaging runtime rather than the fully decoupled pipeline.
Where it sits
Who is behind it
Properties
About this work
Details
Graph
Source
History
- Entered the atlasDiscovered via SAP Community · cloud-integration-tag, SAP Community · integration-suite-tag.
For your agent
- Ref
content:new-pipeline-for-cloud-integration-features-with-version-1-0-11- JSON
- /content/new-pipeline-for-cloud-integration-features-with-version-1-0-11.json
- MCP
- Connecting an agent