| This table lists the enhancements and fixes in fix pack version 5.5.7. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 87499 | JR24595 | ALE Module |
| Symptom: Adapter for SAP does not generate an appropriate message if when it goes down during recovery. |
| Resolution: Logging has been updated. Now the Adapter generates a proper message during recovery. |
|
| 2 | 87885 | | BAPI Module |
| Symptom: The adapter does not restart when an RFC_ERROR_SYSTEM_FAILURE error occurs. |
| Resolution: The adapter automatically restarts when this error occurs. |
|
| 3 | 87849 | | SAP ODA |
| Symptom: SAPODA Fails to load the BOR Tree when connected to ERP'05 System. |
| Resolution: With this fix, the SAP ODA can successfully load the BOR tree in the Business Object Designer after connecting to ERP'05 system. |
|
| 4 | 68077 | JR23566 | ODA |
| Symptom: In the BO Designer, when the user selects BOR (Business Object Repository) Node to create new business object with SAP ODA, a blank error window is displayed without any message. |
| Resolution: With this fix, the ODA can expand the BOR node and objects can be generated. |
|
| 5 | 82999 | JR23060 | ALE Module |
| Symptom: When using the ALE Module for request processing, if the "RfcProgramId" configuration property is not set, adapter throws a null pointer exception if it is terminated by pressing the 'q' key. |
| Resolution: With this fix, terminating the adapter will not cause any errors or exceptions. |
|
| 6 | 67574 | JR22614 | All Modules |
| Symptom: An RFC_ERROR_LOGON_FAILURE: A timeout problem occurs when using the ALE module. |
| Resolution: During request processing, connector was restarting for recoverable JCo errors. With this fix, the connector restarts only for nonrecoverable JCo exceptions. For non fatal JCO errors it will only fail the request. |
|
| 7 | 73643 | JR22883 | ALE Module |
| Symptom: A message is stuck in the event queue and getting processed multiple times. |
| Resolution: Duplicate event elimination is supported with this fix. To enable it, set the DuplicateEventElimination standard configuration property to true. When this property is set to true, a JMS-enabled connector can ensure that duplicate events are not delivered to the delivery queue. Also, create a new MQ queue called MONITORQUEUE to set the MonitorQueue standard configuration property. Note that a unique value is set for the objectEventId attribute in the corresponding Business Object instance. |
|
| 8 | 70697 | | Extension module |
| Symptom: In SAP Adapter ALE Extension module, whenever an event fails in a poll cycle, Adapter keeps such event in the event table with a status of R, instead of archiving it as a failure. |
| Resolution: With this fix, the failed events are archived with a failure status. |
|
| This table lists the enhancements and fixes in fix pack version 5.5.6. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 60220 | JR21157 | ODA |
| Symptom: The ODA was failing to create business objects that contain the same structure in the import and export fields. |
| Resolution: With this fix, the structures are uniquely renamed and the object is created successfully. |
|
| 2 | 59037 | JR21157 | ALE Module |
| Symptom: When the Dummy_key attribute does not exist in the business object, the adapter would fail. |
| Resolution: With this fix, the adapter will process the event successfully without dummy_key mapping. |
|
| 3 | 45003 | JR21157 | ALE Module |
| Symptom: When the connector is paused, events were sent to the error queue. |
| Resolution: With this fix, the events will remain in the event queue to be reprocessed again when the connector becomes un-paused again. |
|
| This table lists the enhancements and fixes in fix pack version 5.5.5. |
| Enhancements |
| 1 | 44697 | JR20670 | ALL |
| Symptom: Customer want MS932(Japanese) be supported! |
| Resolution: Support for MS932, Japanese characters is now supported. The new configuration property, PartnerCharset must be used to specify the PartnerCharset encoding. |
|
| 2 | 37323 | JR20575 | Extension Module |
| Symptom: If the SAP adapter is pausing (during polling), events in status 'R' from the current events table goes to status '3' in archived events table and are not processed anymore. |
| Resolution: Events sent when the connector is paused no longer go to the Archive Table with Status ‘3’. They remain in the Event Table ready to be polled with a status of ‘Q’. This change requires importing transports from the following files, 4_Delivery.zip and 4_Utilities.zip.
|
|
| Fixes |
| 1 | 60078 | JR20575 | ALE Module |
| Symptom: SAP adapter hangs after sending BO with CR LF characters. |
| Resolution: The adapter no longer hangs after sending a business object with CR LF characters. |
|
| 2 | 60038 | JR20575 | Extension Module |
| Symptom: Customer getting an error on Event Linkage on SAP 4.7 system. |
| Resolution: The Event Linkage mechanism will work on the SAP 4.7 system with this fix. This change requires importing transports in 47_EventTriggering.zip file. |
|
| 3 | 44080 | JR20575 | ALE Module |
| Symptom: When the adapter is paused some events disappeared. |
| Resolution: With this fix, all events are accounted for in the event queue. |
|
| 4 | 37455 | JR20575 | ALE Module |
| Symptom: Processing IDOCs with empty text segment gives problems |
| Resolution: When processing IDOCs with an empty text segment the adapter will not longer fail with an MQ error. |
|
| This table lists the enhancements and fixes in fix pack version 5.5.4. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 59080 | JR20290 | RFCServer Module |
| Symptom: SAP adapter in RFCServer Module is going down in receiving an invalid response. |
| Resolution: SAP Adapter RfcServer no longer terminates when an invalid response message is received from WebSphere Message Broker. |
|
| 2 | 58858 | JR20290 | ALE Module |
| Symptom: NullPointerException in case of wrong control record data (SAP ALE). |
| Resolution: SAP Adapter no longer throws the NullPointerException in case of wrong control record data (SAP ALE). |
|
| 3 | 58954 | JR20265 | RFC Server Module |
| Symptom: RFCServer Module is going down when an unsubscribed RFC is triggered from SAP. |
| Resolution: If a BO is not supported, do not terminate the adapter, rather, log an error and keep the adapter alive. |
|
| 4 | 37005 | JR20265 | Extension Module |
| Symptom: When upgrading the SAP adapter from 5.0 to 5.5 the extension module is not working. |
| Resolution: Correct processing of child BOs when using the ABAP BAPI_Handler. |
|
| 5 | 58492 | JR20232 | ALL |
| Symptom: SAPConnector fails to restart upon going down. |
| Resolution: The restart/retry feature was not restarting the connector correctly. This needs to be implemented in conjuction with an adapter framework fix. Contact WBI Technical Support for information on the adapter framework fix. |
|
| This table lists the enhancements and fixes in fix pack version 5.5.3. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 35192 | JR20092 | ALE Module |
| Symptom: Archiving/removing of events from Request directory. |
| Resolution: Performance was degrading when the Request directory fills up with many status files for ALE request processing. |
|
| 2 | 36006 | JR20092 | ALE Module |
| Symptom: SAP adapter fix pack 5.5.2 initialization not pickup AleEventDir. |
| Resolution: Adapter was not using the configured connector property value for "AleEventDir" for creating the "Request" folder. Request folder holds the status message files for ALE request processing using TID management.
NOTE: Before applying this patch, complete all of your failed ALE Request flows. After applying this patch the connector creates and uses the "Request" folder under the configured parent directory. It will no longer cleanup the previous request directory. You will have to manually cleanup that directory. |
|
| 3 | 35673 | JR20092 | ODA |
| Symptom: SAP ODA generate APSI=0 if input is SAP4.7 IDOC file. |
| Resolution: When using IDOC files from SAP R/3 4.7 systems, the Application Specific information generated in the business objects was incorrect.
This is due to the fact that, the ODA looks for "BYTE_FIRST" property of the IDOC file to get the begin index of the field. Since the BYTE_ prefix is replaced with that of CHARACTER_, the ODA could not identify the begin index and hence you find 0 in ASI. This is now fixed in the SAPODA. |
|
| 4 | 42920 | JR20092 | ODA |
| Symptom: The SAP ODA cannot generate BO correctly. |
| Resolution: A Search By Description BAPI/RFC down the RFC node was not generating its corresponding BO correctly.Code change has been made in Kirkwood patch and fixed in this release. |
|
| 5 | 35387 | JR20092 | ALE Module |
| Symptom: Zero like characters getting appended to the data in SAP, using latest adapter. |
| Resolution: Correct the setting of the space characters that pad the fields in a segment when sending it to SAP. |
|
| This table lists the enhancements and fixes in fix pack version 5.5.2. |
| Enhancements |
| 1 | 34614 | JR19942 | ALL |
| Symptom: SAPAdapter throws misleading error when MQJMS libraries are not installed. |
| Resolution: During startup SAPAdapter logs misleading error saying "JCO files missing" when MQ JMS libraries are not installed.The connector now logs proper message. |
|
| Fixes |
| 1 | 34205 | JR19928 | ALE Module |
| Symptom: Based on network error, upon loosing connection to SAP application, SAP Connector does not go down completely |
| Resolution: When SAP server shuts down abruptly request events are no longer lost during request processing. |
|
| This table lists the enhancements and fixes in fix pack version 5.5.1. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 33144 | JR19534 | Extension Module |
| Symptom: ObjectEventId set to CxIgnore in the response BO. |
| Resolution: The value of ObjectEventId is preserved for request processing. |
|
| 2 | 32731 | JR19534 | ALL |
| Symptom: 5.4.4 version of Adapter does not start with ICS 4.1.1. |
| Resolution: Configuration properties are case-insensitive beginning with ICS version 4.2.0 and WBIA 2.3.0. |
|
| 3 | 31502 | JR19375 | ALE Module |
| Symptom: restart behaivor after application is getting lost. |
| Resolution: When the connector dies due to a Fatal Error, the RestartRetryCount connector property will properly restart the connector.
|
|
|