SAP Connector Release Notes - Mule 4

You can now update a specific row in a table by adding the new INDEX_ROW_UPDATE parameter to the payload when using Function Listener.

Added a new parameter, Use SAP Format On Function Listener, to control the SAP date format on the function listener.

The Document Listener and Function Listener sources can now connect to SAP via Message Server.

SAP Document Listener received messages based on the SAP debug log but did not trigger a flow. (SE-21727)

SAP Function Listener stopped receiving messages after multiple exceptions. (SE-21728)

An error was not thrown for an IDoc parsing exception. (SE-18502)

Some exceptions logged at the ERROR level should have been logged at the DEBUG level. (SE-18631)

Added IDocXMLProcessor parse and render options.

SAP Connector could not process certain Japanese characters on Windows.(SE-18494)

When there was an odd number of Chinese characters in a request, SAP Connector could not process them. (SE-17904)

SAP Connector did not listen for IDOC/BAPI from two different SAP instances when they had the same program ID configured. (SE-17173)

Restarting an application failed to register the program ID and other apps stopped processing. (SE-14920)

SAP Connector failed to serialize incoming data into a valid XML object when the data contained 0x0. (SE-15986)

SAP Connector failed to receive IDOC_INBOUND_ASYNCHRONOUS on the function source because of parsing issues. (SE-15632)

Metadata did not mark nodes as repeatable. (SE-14232)

Fixed existing vulnerabilities. (CONN-5801)

Fixed Munit cannot delete data folder while disposing an application in Windows. (SE-15095)

SAP Connector failed to parse fields that started with a digit. (SE-15150)

SAP Connector did not send field values with special characters in the name to SAP.

Fix for IDoc BENEFIT3 basic type missing from metadata list (SE-13986)

Fix for Found exception stopping source warning for Inbound SAP Function Source Connector (SE-14337)

SAP Connector table rows were missing in a response back to the SAP server. (SE-14063)

SAP Connector did not recognize all BAPI metadata. (SE-14018)

The JCO_ERROR_DESTINATION_DATA_INVALID error was incorrectly thrown in the SAP Connector. (SE-14098)

Implemented metadata support for the function source.

Refactored error types to provide better error handling.

IDoc source filtering is added to enable users to filter the document type based on a regular expression. Any type of regular expression is supported.

The SAP X.509 certificate field is now required when the connection is Certificate.

The reconnection strategy on SAP (applies to operations only) is improved. With this enhancement, when a connection fails on the FunctionSource or DocumentSource, the JCo server automatically tries to reestablish a connection in the following way:

Message logging is added for when the connector is in debug mode.

The timeout parameter is removed because the JCo library does not support timeout functionality.

Fixed some memory leak issues

Fixed class loader leak issues

Adapted demos for the new operation

Updated documentation

Fixed the issue of the function source request-response pattern not working (SE-13280)

Made other general changes that increase the stability and improve the performance of the connector

The Create operation is renamed Retrieve IDoc.

The execute BAPI functions over qRFC, tRFC, and sRFC operations are merged into Synchronous Remote Function Call (sRFC) and Asynchronous Remote Function Call (aRFC) operations.

Disable function template cache flag is renamed to Disable JCo internal cache, and applies to both functions and sources. The default value is false.

The sources now have -listener in their aliases instead of source. For example, the XML is changed from sap:document-source to sap:document-listener.

The SAP configuration has the following changes:

SAP Connector failed to receive IDOC_INBOUND_ASYNCHRONOUS on the function source because of parsing issues. (SE-15632)

Metadata did not mark nodes as repeatable. (SE-14232)

Fixed Munit cannot delete data folder while disposing an application in Windows. (SE-15794)

The issue that caused SAP Connector fail to parse fields starting with a digit is fixed. (SE-15150)

The issue that caused SAP Connector to not send values of fields with special characters in the name to SAP is fixed.

Fix for IDoc BENEFIT3 basic type missing from metadata list (SE-13986)

Fix for Found exception stopping source warning for Inbound SAP Function Source Connector (SE-14337)

Fixed SAP Connector metadata not being built for inner tables. (SE-14018)

Fixed SAP Connector not recognizing specific JCo error types as connection issues. (SE-14098)

General connector improvements.

Refactoring to improve compliance with the Mule development best practices.

Deprecated the UNKNOWN error type that will be removed in the next major upcoming release.

Fixed missing configuration parameters in the source configuration. (SE-12658, SE-12484).

Fixed sRFC call that reported a successful response, but which had data missing on the SAP side. The timeout must be set to 0 (default value) to execute a function as a transaction. In this case, using a try scope. (SE-12681)

Retrieving 50K records using the SAP connector results in an OOME inconsistency at 1.5 GB heap memory. (CONN-1838)

Unable to define the RFC timeout setting in the SAP connector in Mule 4.(SE-12045)

SAP Connector - Wrong number format returned. Fixed by adding the new useSAPFormat parameter, which if set to true, returns the default values received from SAP. (SE-12022)

SAP Connector - Parsing error when the SAP response contains nested tables. (SE-11910)

Fixed SAP Connector vulnerability to an XML External Entity (XXE).

Fixed SAP Connector Encoding field with a hint description.

New SAP format for the date and time when working with BAPI functions over sRFC:

Added SAP date and time format (see Features for more information). (SE-11815)

The SAP connector did not accept special characters in an incoming BAPI function sRFC response. (SE-11651)

Configuring SNC in SAP connector was not working. Added message server configuration parameters:

String JCO_MSHOST = "jco.client.mshost";
String JCO_MSSERV = "jco.client.msserv";
String JCO_R3NAME = "jco.client.r3name";
String JCO_GROUP = "jco.client.group";
String JCO_SAPROUTER = "jco.client.saprouter";

SAP connector is not honoring the encoding set in the configuration. (SE-11690)

I_DOCNUM is not being returned. (SE-11630)

SAP Connector throws parsing XML error for a BAPI call (SE-11457)

Sap Connector caching JCOFunction templates. (SE-11417)

Solved the issue where empty tables would crash the metadata generation. (SE-10776)

Customer facing SAP connector was not able to update SAP correctly when IDOCs were sent as a collection. (SE-11221)

SAP connector did not accept slash "/" on a BAPI function call. (SE-10952)

Out of memory when retrieving data from SAP due to XML serialization. Solved by changing XML serialization implementation.

Fixed empty metadata name issue that caused the metadata generation to fail. The empty entries were removed so only the valid ones end up in the XML.

Fixed source not sending the response back to SAP in case of export parameters. Solved by implementing handling for this scenario.

Duplicate IDoc elements were filtered. Now they are properly processed.

Trying to access row values in a table which does not have any rows yet was throwing an error. It doesn’t do that anymore now.

Connector can now be downloaded without having to add the releases repository in the settings.xml.

MuleSoft Help Center

MuleSoft Services