Change Log for Process Integration Pipeline - Generic Integration Flows & Templates Date format: dd/mm/yyyy 27/08/2025 - 1.0.13 The integration package has been deprecated and replaced by the following four new integration packages - Cloud Integration Pipeline - Generic Inbound - Cloud Integration Pipeline - Generic Pipelines - Cloud Integration Pipeline - Generic Outbound - Cloud Integration Pipeline - Templates If you've been using the previously provided package, switch to the new packages as soon as possible. To do so, perform the following steps: - Undeploy all generic flows from the deprecated package. In the new Cloud Integration packages, the name and IDs of the integration flows have the addition "v2". It's important that the old integration flows and the new integration flows must not be deployed together because they compete on reading from the same JMS queues. - Configure and deploy the required generic flows provided by the new Cloud Integration pipeline packages. - If you've used scripts from the script collection in your scenario-specific flows, replace them with local scripts. You can find the local scripts in either the generic flows or the new templates. As long as you haven't replaced all scripts, it's still recommended to run the script collection. Once you're done, you can then also undeploy the script collection. 21/05/2025 - 1.0.12 - Reworked the custom header properties to support : and | in the custom header property values - Added custom header property QualityOfService for the "Pipeline Generic Step01 - Inbound Processing for XI" flow - Updated the allowed header list for the provided template flows - Fixed an error with wrong name of the XSLTs for interface determination in combination with the staged business system names - Changed the support component of the integration package to LOD-HCI-PI-CNT-DSG 25/04/2025 - 1.0.11 - Removed leading zeros from IDoc number in ApplicationID and custom header properties in the "Pipeline Generic Step01 - Inbound Processing for Idoc" flow - Option to switch off partner ID "tilde option" to allow scenario names only as partner ID, the default is true following the recommendation to use alternative partners for determining partner IDs; if you like to use the tilde option, you need to configure the externalized parameter CustomXPid_SwitchOffTilde in most of the generic flows to true - Changed the default inbound processing queue from PIPQ01 to PIPX01 for the "Pipeline Generic Step01 - Inbound Processing for Idoc" and "Pipeline Generic Step01 - Inbound Processing for XI" flows to follow our recommendation to use the Integrated Messaging Runtime pipeline instead of the fully decoupled pipeline; if you like to use the fully decoupled pipeline in general, you need to configure the externalized parameter DefaultJMSQueueNumber to Q01, if you like to use the fully decoupled pipeline for particular scenarios only, you need to create a string parameter InboundQueue for the particular scenario in the Partner Directory with value PIPQ01 - Support for service interface namespaces to identify partner ID based on system name, service interface name and service interface namespace for the "Pipeline Generic Step01 - Inbound Processing for XI" flow - Fixed an error with wrong inbound queue in case of custom error handling for the "Pipeline Generic Step02 - Integrated Messaging Runtime Async" flow 17/03/2025 - 1.0.10 - New script in script collection "Pipeline Generic - Script Collection" to support service interface operations - Update of templates "Pipeline Template Step01 - Inbound Processing At Least Once", "Pipeline Template Step01 - Inbound Processing Exactly Once", and "Pipeline Template Step03 - Inbound Conversion" to support service interface operations - Updated the allowed header list to increase flexibility when using SAP headers starting with the terms SAP_Sender and SAP_Receiver as well as custom headers starting with the term customX - Script optimizations using new features to fix script incompatibilities and optimizing Groovy scripts via generative AI - Convert XI message ID to upper case in the generic XI inbound processing flow "Pipeline Generic Step01 - Inbound Processing for XI" to be compatible with the format which is displayed in the message monitoring of the Integration Engine of the sender system 09/01/2025 - 1.0.9 - Supporting different tenant stages, e.g., DEV, QA, PRD - New integrated messaging runtime "Pipeline Generic Step02 - Integrated Messaging Runtime Async" combining inbound conversion and receiver/interface determination in one pipeline step - New integrated messaging runtime "Pipeline Generic Step02 - Integrated Messaging Runtime Sync" for handling synchronous Content-Based-Routing scenarios - New template "Pipeline Template Step01 - Inbound Processing Synchronous" for scenario-specific synchronous inbound processing - New template "Pipeline Template Step07 - Outbound Processing Synchronous" for scenario-specific synchronous outbound processing - Generic inbound processing for XI supports both asynchronous and synchronous messaging - Failed test messages end with escalation instead of completed - Added custom error handling for generic XI and IDoc inbound flows 18/11/2024 - 1.0.8 - Option to combine receiver and interface determination in one single XSLT mapping for an improved runtime behavior - Option to bypass interface determination pipeline step in case of Recipient List pattern without interface split - Option to bypass receiver determination pipeline step in case of interface split scenarios with one single receiver only - Supporting header-based XSLT routing conditions if message body is non-XML - Extension for custom receiver determination instead of XSLT from Partner Directory - Extension for custom interface determination instead of XSLT from Partner Directory - New pipeline processing log providing more details if message is stored to the dead letter queue - Fixed standard retry handling for generic integration flows with splitter to avoid message duplicates 08/10/2024 - 1.0.7 - Add custom header properties to improve message monitoring - Allow headers starting with dc for passing dynamic configuration parameters to the generic integration flows, e.g., to support header-based routing conditions 08/08/2024 - 1.0.6 - Revised partner id approach due to lengths restrictions of the partner id - Option to use alternative partner in case of sender wildcard scenarios and to overcome partner id restrictions - Changed default max retry to 5 instead of unlimited retry - For messages in test mode, failed messages are not put into retry - For generic integration flows, adapter parameters were externalized - Option to configure message end event type in case of message stored in dead letter queue, default is Escalated - Option to bypass receiver determination and interface determination steps in case of Point-to-Point pattern - Option to configure a pipeline JMS queue prefix which makes configuration of queue names easier if you create another set of generic integration flows 31/05/2024 - 1.0.5 - Extension for custom error handling - In generic IDoc inbound processing flow, display list of IDoc numbers in case of IDoc bulk messages - For IDoc inbound, sender interface is calculated as a combination of MESTYP, IDOCTYP and CIMTYP - Supporting test mode via testMode header in the allowed headers configuration - In standard error handling, copied messages from the dead letter queue are switched to DEBUG log level 22/04/2024 - 1.0.4 - Removed the deletion of the payload exchange property to avoid that an empty payload is written into the dead letter queue - Generic inbound processing for IDoc flow now assigns the IDoc number to the SAP_ApplicationID header for better monitoring - Generic inbound processing for XI flow now assigns the XI ID to the SAP_ApplicationID header for better monitoring - For both generic inbound processing for IDoc and generic inbound processing for XI the custom status is set to DuplicateDiscarded in case of duplicate messages 12/04/2024 - 1.0.3 - Changed the dead letter queue names to ensure that the queues are automatically created when deploying the integration flows - Stored the payload in an exchange property for the generic outbound processing flow to ensure that in case of an error the payload before mapping is stored in the dead letter queue 08/04/2024 - 1.0.2 - Switched on transaction handling for flows reading and writing into JMS queues 19/03/2024 - 1.0.1 - Changed names of the integration flows for better readability 18/03/2024 - 1.0.0 - First shipment