Change log for "Cloud Integration Pipeline - Generic Outbound" Date format: dd/mm/yyyy Version format: Major.Minor.Micro 20/10/2026 - 1.1.1 - Fixed a bug in the "Pipeline v2 Generic Step06 - Outbound Processing" flow with toLowerCase() expression in the condition checking the testMode header. 13/10/2026 - 1.1.0 - A new integration flow "Pipeline v2 Generic Step08 - Outbound Processing for Idoc on Edge" has been added to the package. Deploy and run this flow on Edge Integration Cell if you need to handle IDoc outbound scenarios when running the pipeline on Edge Integration Cell. A dedicated flow is needed because the proxy type OnPremise is not supported on Edge Integration Cell. Currently, the proxy type Internet is supported only. The proxy type Manual will be added with one of the next increments. - A new integration flow "Pipeline v2 Generic Step08 - Outbound Processing for XI on Edge" has been added to the package. Deploy and run this flow on Edge Integration Cell if you need to handle XI outbound scenarios when running the pipeline on Edge Integration Cell. Currently, the proxy type Internet is supported only. The proxy type Manual will be added with one of the next increments. - The integration flow "Pipeline v2 Generic Step08 - Outbound Processing for IDoc" has been enhanced to be able to maintain the list of IDoc EDIDC control record fields to be overridden by configuring the externalized parameter OverrideControlRecordParameters. With this, you now have three options to maintain the override parameter: via message header in the scenario-specific flow, as string parameter in the Partner Directory, and as externalized parameter of the generic Idoc outbound flow. - The integration flows "Pipeline v2 Generic Step08 - Outbound Processing for XI" and "Pipeline v2 Generic Step08 - Outbound Processing for Idoc" now support receiver with party when configuring the XI and Idoc adapters in the Partner Directory. - The integration flows "Pipeline v2 Generic Step08 - Outbound Processing for XI" and "Pipeline v2 Generic Step08 - Outbound Processing for Idoc" now support slash (/) in the interface name. When maintaining the configuration parameters in the Partner Directory, the slash (/) needs to be replaced by underscore (_). - For the integration flow "Pipeline v2 Generic Step08 - Outbound Processing for Idoc", a new configuration parameter EnableControlRecordCheck has been introduced. By default, the parameter is true so that message processing fails if any mandatory control record field is empty or missing. This check has been introduced previously. With the new parameter, you now have the option to disable the check by setting the parameter value to false. In this case, empty mandatory control record fields are ignored and the message processing won't fail in Cloud Integration. You disable the check, when you rather check empty mandatory control record fields in the backend system. - The integration flows "Pipeline v2 Generic Step08 - Outbound Processing for XI" and "Pipeline v2 Generic Step08 - Outbound Processing for Idoc" now support custom exits for pre-transmission. You have the options to call a custom flow right before the message delivery to the receiving system across all scenarios or scenario-specific without the need to alter the standard flows provided. In addition to the header customXPipelineStep (in this case equals 08), the header customXProtocol (either xi or idoc) is passed to the custom exit flow. - The scenario-specific custom exit definition has been enhanced. For each pipeline step, you can now define an own end point by adding the pipeline step number as suffix to the string parameter CustomXPreEndpoint in the Partner Directory. - The integration flow "Pipeline v2 Generic Step06 - Outbound Processing" now supports custom exits for post-processing. You have the options to call a custom flow after the message delivery to the next step across all scenarios or scenario-specific without the need to alter the standard flow provided. For latter, you can maintain the string parameters CustomXPostEnabled and CustomXPostEndpoint, repectively, in the Partner Directory. Right now, the CustomXPostEnabled only supports step number 06. - The standard error handling in the "Pipeline v2 Generic Step06 - Outbound Processing" flow has been enhanced supporting custom pre-processing. You now have the option to call a pre-processing custom error flow before calling the standard error handling. - Fixed a bug which resulted into a type conversion exception when in an error case an original message in XML format was stored in the dead letter queue. This happened only for cases where the original XML message was converted into a non-XML message like JSON for instance. The fix was implemented in the restoreMessage script. - Fixed a bug in the integration flows "Pipeline v2 Generic Step08 - Outbound Processing for XI" and "Pipeline v2 Generic Step08 - Outbound Processing for Idoc" with the complex conditions evaluations to route to the corresponding receiver adapters. The condition was hence replaced by a groovy script. - For the "Pipeline v2 Generic Step06 - Outbound Processing" flow, the max retry handling condition was slightly adapted to be more robust avoiding endless message retry. Instead of using equal (=) in the condition, we now use greater or equal than (>=). 20/07/2026 - 1.0.5 - Fixed a bug in the integration flow "Pipeline v2 Generic Step08 - Outbound Processing for XI" where the source message id of the id mapper could exceed the maximum length of 120 characters. Now, the source message id is concatenated based on the unique ID header and the receiver interface name cut off at 120 characters, and the context equals the receiver interface namespace cut off at 40 characters. 07/07/2026 - 1.0.4 - For the integration flows "Pipeline v2 Generic Step08 - Outbound Processing for XI" and "Pipeline v2 Generic Step08 - Outbound Processing for IDoc", the option maintaining the connection parameters in the Partner Directory has been enhanced. The parameters can be now maintained as string parameters of a partner ID representing a business system. Furthermore, some connection parameters can be also maintained as string parameters of a partner ID representing a configuration scenario. So far, this was only supported via string parameters in the corresponding business system alias. - For the "Pipeline v2 Generic Step06 - Outbound Processing" flow, the sender queue name has been added to the custom header attributes. - For the integration flow "Pipeline v2 Generic Step08 - Outbound Processing for XI", the delivery assurance settings to determine the XI Message ID have been revised to ensure that a proper Universally Unique Identifier (UUID) is passed to the receiver system. For this, the value of the UniqueID header is mapped to the header SapMessageIdEx and the XI adapter now uses Reuse instead of Map. Furthermore, in case of an XI to XI scenario, you have the option to pass the sender XI message ID from end-to-end. - For the integration flow "Pipeline v2 Generic Step08 - Outbound Processing for IDoc", the processing settings to determine a unique ID have been revised. For this, the value of the UniqueID header is mapped to the header SapMessageId and the IDoc adapter now uses Reuse instead of Map. - For the "Pipeline v2 Generic Step06 - Outbound Processing" flow, the retry behavior has been revised. For some errors where an automatic message retry would not make sense, the retry is skipped and the message is directly stored in the dead letter queue. - For the "Pipeline v2 Generic Step06 - Outbound Processing" flow, you have the option to measure and display the size of the original payload. 02/03/2026 - 1.0.3 - For the integration flow "Pipeline v2 Generic Step08 - Outbound Processing for XI", you can now override the headers SAP_Sender and SAP_Receiver from the default externalized parameters. For this, the Groovy script "readPDValuesForXI" has been extended. If the scenario-specific inbound processing flow passes empty header values to the generic XI outbound flow, the values of the externalized parameters are used. - The integration flow "Pipeline v2 Generic Step08 - Outbound Processing for XI" now supports dynamic XI headers. For this, a new Groovy script "createSapDynamicConfigurationFromHeaders" has been added. This script converts the headers passed from the scenario-specific inbound processing flow into exchange properties that the XI receiver adapter expects to add corresponding dynamic XI headers to the message sent out to the receiving system. - The integration flow "Pipeline v2 Generic Step08 - Outbound Processing for Idoc" has been enhanced to display the partner functions SNDPFC and RCVPFC in the custom header properties section of the message processing log in the message monitor. For this, the Groovy script "setIDocMonitoringProperties" has been enhanced. - The integration flow "Pipeline v2 Generic Step08 - Outbound Processing for Idoc" now fails if any mandatory control record field is empty or missing. This check has been implemented in the Groovy script "setIDocMonitoringProperties". 19/11/2025 - 1.0.2 - The integration flow "Pipeline v2 Generic Step08 - Outbound Processing for IDoc" has been enhanced to display all IDoc numbers in the message processing log in case of processing IDoc bulk messages. - Fixed a typo in the readPDValuesForXI.groovy script in the integration flow "Pipeline v2 Generic Step08 - Outbound Processing for XI". - When saving non-XML payloads in an exchange property in the integration flow "Pipeline v2 Generic Step06 - Outbound Processing", the payload is encoded to avoid that payload gets corrupted when retrieving from the exchange property. 29/10/2025 - 1.0.1 - The audit log which is attached to the message processing log in case of message retry exceeded has been updated. - Support for sender and receiver parties has been improved. - The configuration options of receiver-specific queues has been enhanced to be more flexible in the definition of receiver-specific processing. - For the name of the outbound processing queue, you can now define a prefix and a suffix which gives you more flexibility in defining receiver-specific outbound queues. - New integration flow "Pipeline v2 Generic Step08 - Outbound Processing for Idoc" has been added to handle IDoc outbound scenarios. - New integration flow "Pipeline v2 Generic Step08 - Outbound Processing for XI" has been added to handle XI outbound scenarios. 04/08/2025 - 1.0.0 - The package "Process Integration Pipeline - Generic Integration Flows and Templates" has been split up into multiple packages to be more flexible in setting up multiple pipelines, sender-specific IDoc and XI inbound flows, receiver-specific outbound flows. - For the same reason, the script collection has been replaced by local scripts. - Custom exits for pre-processing has been added with the options to call a custom flow across all scenarios or scenario-specific without the need to alter the standard flows provided. - All flow steps and adapters in the flow has been updated to their latest version. - For the pipeline related externalized parameters, descriptions have been added that provide you with more detailed information when configuring the flows. - "Pipeline v2 Generic Step06 - Outbound Processing" version 1.0.1 contains the new features mentioned above. - "Pipeline v2 Generic Step06 - Outbound Processing" version 1.0.0 copied from soon to be deprecated package "Process Integration Pipeline - Generic Integration Flows and Templates".