Skip to main content
Feedback

SAP JCo changelog

Changelog

2026-09 (Version 14, Runtime release)

  • Added the IDoc message function as a document property on the SAP JCo connector, so you can route IDocs without extracting the value from the EDIDC segment.

This feature is included in the runtime release.

Enhancement

  • Added log rate limiting to the SAP JCo connector so excessive third-party logging no longer floods runtime logs. Logging issues now stay isolated to the affected listener.

This enhancement is not in the runtime release.

Fixes

  • Resolved an issue where the SAP JCo V2 connector confirmed a transaction ID (TID) even when the runtime discarded the process execution during shutdown, which caused IDoc loss.

This fix is included in the runtime release.

  • Resolved an issue where the SAP JCo V2 connector could not connect to an SAP system through an SAP router. Connections now honor the jco.server.saprouter property.

  • Resolved an issue where the SAP JCo V2 IDoc Listener accepted IDoc submissions into a runtime that was shutting down and confirmed the transaction ID (TID) without running the process.

These fixes are not in the runtime release.

2026-07 (Version 11, Current)

  • Fixed an issue in the Boomi for SAP connector that caused data transfer issues when importing RFC with an item element name.

  • Fixed an issue that occurred when processing multiple documents with valid and invalid payloads.

  • Fixed an issue in the SAP JCo connector where the retry loop did not differentiate between transient unregistration failures and unrecoverable network or SSL errors. This issue caused the connector to retry indefinitely and degrade system stability.

2026-03 (Version 9)

  • Boomi renamed the SAP JCo V2 connector to the SAP JCo connector.
On this Page