This table lists the enhancements and fixes in fix pack version 6.1.0.3. |
Enhancements |
1 | 86210 | | Support for asynchronous inbound processing of BAPI calls |
Symptom: The adapter supports only synchronous processing of inbound events. |
Resolution: The adapter now supports the asynchronous processing of events. With this fix pack, the adapter supports tRFC and qRFC asynchronous protocols for inbound processing. When using these protocols, the client SAP application does not wait for a response from the adapter. For more information about this feature, refer to the adapter documentation. |
|
2 | 95726 | | Support for asynchronous outbound processing of BAPI calls |
Symptom: The adapter supports only synchronous processing of outbound events. |
Resolution: The adapter now supports the asynchronous processing of events. With this fix pack, the adapter supports tRFC and qRFC asynchronous protocols for outbound processing. When using these protocols, the adapter does not wait for a response from the SAP server. For more information about this feature, refer to the adapter documentation. |
|
Fixes |
1 | 96046 | JR28793 | The basic properties user name and password are stored in an advanced configuration section |
Symptom: When version 6.1 of the adapter is used with WebSphere Message Broker, the user name and password properties are stored in an advanced configuration section of the adapter properties, even though they are basic, mandatory properties. |
Resolution: Because the user name and password are mandatory properties, they have been moved to the basic properties section. |
|
2 | 96221 | JR29142 | The adapter does not embed an application exception |
Symptom: When a BAPI outbound call fails, version 6.1 of the adapter does not embed the application exception in the FaultException message. |
Resolution: The adapter includes an application exception in the FaultException message when a BAPI outbound call fails. |
|
3 | 96094 | JR28825 | Ale inbound fails with NullPointerException |
Symptom: After applying a WebSphere(R) Process Server fix (6.0.2.1 for APAR JR26701), ALE inbound events fail with a NullPointerException. |
Resolution: This problem has been corrected. |
|
4 | 96095 | JR28827 | Subsequent calls to SAP fail after an outbound event fails |
Symptom: In some scenarios, when an outbound BAPI call from the adapter fails, the table corresponding to the BAPI is locked and all subsequent BAPI calls fail. |
Resolution: The adapter now calls the BAPI_TRANSACTION_ROLLBACK function when an outbound call to SAP fails, which enables the underlying resources within SAP to be released. |
|
This table lists the enhancements and fixes in fix pack version 6.1.0.2. |
Enhancements |
1 | 95574 | | Support for generic IDoc type in ALE pass-through interface |
Symptom: A separate IDoc definition is required for each IDoc that the adapter is expected to process. This can become unwieldy when the ALE pass-through interface is used to process many different IDoc types. |
Resolution: The ALE pass-through interface supports a generic IDoc definition that enables the adapter to process any IDoc type. An IDoc type field in the object definition is used to indicate the IDoc type. |
|
2 | 95236 | | Support for custom SAP function module in QISS interface |
Symptom: QISS interface uses the SAP RFC_READ_TABLE function module to retrieve data. On some SAP systems, the RFC_READ_TABLE function fails and causes SAP short dumps, which result in the following error: Error in ASSIGN statement in the program SAPLSDTX. |
Resolution: To overcome this issue, SAP OSS note #758278 recommends creating and using a custom function module instead of the RFC_READ_TABLE function. After this custom function module is created on the SAP system, you can enter the custom function module name when running the external service wizard. The adapter uses this custom function module at run time. |
|
3 | 95594 | | Support inbound split IDoc packet in ALE pass-through interface |
Symptom: The ALE pass-through inbound interface does not support a split IDoc packet. |
Resolution: Each IDoc in the inbound packet can be sent as an individual business object. |
|
4 | 95622 | | Transaction ID (event ID) for ALE inbound operation not populated in the business object |
Symptom: The transaction ID (event ID) is not populated in the business object. |
Resolution: The transaction ID (event ID) is now populated in the business object. |
|
This table lists the enhancements and fixes in fix pack version 6.1.0.1. |
Enhancements |
There are no enhancements in this fix pack. |
Fixes |
1 | 86215 | | Support for IDoc streams with no partial parsing |
Symptom: The ALE inbound interface does not support the processing of an incoming IDoc as an unparsed stream. |
Resolution: The ALE inbound interface supports the processing of an incoming IDoc as an unparsed stream. The external service discovery wizard now generates the required artifacts to provide this support. |
|
2 | 89221 | | Support for Secure Network Communication (SNC) |
Symptom: The adapter does not support Secure Network Communication (SNC). |
Resolution: This support has been added. |
|
3 | 90957 | | Configurable retry for failed events |
Symptom: The adapter continues to redeliver failed events indefinitely. |
Resolution: A new property, FailedEventRetryLimit, has been added to the activation specification. Through this property, you can specify the number of times the adapter attempts to deliver an event before marking it as FAILED. This only applies to failures that are normally retried; data binding errors and function selector errors are excluded. If the adapter or server is shut down and restarted, the adapter will start fresh and deliver the event the specified number of times, without regard to any retries that were attempted before the adapter was shut down.
|
|