| This table lists the enhancements and fixes in interim fix version 6.1.0.6 |
| Enhancements |
| 1 | 75527 | | Provide the WAIT before invoking BAPI_TRANSACTION_COMMIT |
| Symptom: The adapter does not wait for sometime before invoking BAPI_TRANSACTION_COMMIT. |
| Resolution: This is fixed |
|
| 2 | 99253 | | Support for multiple idoc in ALE pass through outbound. |
| Symptom: The adapter supports the Outbound scenario for ALE PassThrough IDocs only for a single IDoc. |
| Resolution: Now it support posting multiple IDocs.Delimiter can be used to seperate IDoc.Using delimiter is an optional feature. |
|
| 3 | 99998 | | Make adapter 6.1 comply with the new WPS v7.0 SDO implementation |
| Symptom: Currently the Adapter 6.1 version only supports EMF, and doesn't support XCI. |
| Resolution:A fix has been delivered to make Adapter 6.1 comply with the new WPS v7.0 SDO implementation. |
|
| Fixes |
| 1 | 100282 | JR34939 | Field naming of IDoc control record and data record cannot be handled independently |
| Symptom: Currently both Control record and Data record can be generated either using Field name or Field Description |
| Resolution: Option is provided in EMD to generate control record and data record independently.For eg
now control record can be generated using field name and data record using field description and vice versa.
|
|
| 2 | 100127 | JR34712 | SAP Adapter reports that an accessor for BAPI fields of type STRING is not found
|
| Symptom: When a BAPI contains fields of type String, the request fails with "No accessor-to-data mapping" found error
|
| Resolution: The fix for SAP Adapter is made to map the JCO Type String to the corresponding accessor
|
|
| 3 | 76155 | JR31207 | The adapter does not correctly handle stale connections and does not do a retry when the connection is lost during request processing. |
| Symptom: The adapter does not correctly handle stale connections to the SAP EIS. |
| Resolution: This is now fixed. The adapter also does a retry if the connection is invalid during request processing. |
|
| 4 | 100079 | JR34652 | Error message when building a new SAP request adapter connection if BAPI contain changing parameter. |
| Symptom: Error message when building a new SAP Request Adapter Connection. Receive com.ibm.adapter.framework.BaseException message
Reason: unable to create definitions local part cannot be "null"when creating a QName.
|
| Resolution: EMD was failing for changing paramter.The code is corrected
|
|
| 5 | 99343 | JR34424 | BAPI Inbound with namespace syntax "/ABC/XYZ" is throwing exceptions. |
| Symptom: com.ibm.websphere.sca.ServiceRuntimeException: commonj.connector.runtime.SelectorException: commonj.connector.runtime.SelectorException: For the RFC TypeSapABCXYZWrapperOperation is not found using the application-specific information: caused by: commonj.connector.runtime.SelectorException: commonj.connector.runtime.SelectorException: For the RFC TypeSapABCXYZWrapperOperation is not found using the application-specific information |
| Resolution: This is now fixed. |
|
| 6 | 99304 | JR34330 | ALE Inbound with Extended IDocs fails when using the qRFC protocol. |
| Symptom: Incorrect handling for Extended IDoc naming conventions. |
| Resolution: This is now fixed. |
|
| 7 | 99289 | JR34365 | Empty xml tags are not sent after atleast one more populated field within an IDoc segment
|
| Symptom: If an IDoc segment has 3 fields field1,filed2 and field3 and only field1 and filed 2 are populated in the output object.
|
| Resolution: 3 options are provided in the Advanced Tab of the Connection Wizard
1.BEFORE_AND_AFTER - Sends empty field tags before and after one more populated IDoc field.
2.ONLY_BEFORE - Sends empty field tags before one more populated IDoc field.
3.ALL_UNPOPULATED_FIELDS_SEGMENTS - Sends empty field tags before and after unpopulated fields as well as segments. This is highly performance intensive and meant to be selected if there are no alternatives.
|
|
| 8 | 77031 | JR32699 | The adapter ALE module fail at runtime when BO names are resolved in different cases. |
| Symptom: com.ibm.j2ca.sap.exception.SapAleOutboundException: Exception while getting accessor. Please make sure property exists with accessor name NameOfTableStructure or TABNAM or Tabnam |
| Resolution: This is now fixed. |
|
| 9 | 77612 | JR33266 | Czech characters in the IDoc are getting corrupted while running ALE passthrough inbound |
| Symptom: While running ALE pass through inbound, some Czech characters are getting corrupted in the output IDoc from adapter |
| Resolution: This is now fixed. |
|
| 10 | 77900 | JR33557 | Duplicate Control Record in IDoc packet sent to endpoint |
| Symptom: While running ALE pass through inbound adapter sends IDoc packet to endpoint with duplicate control record |
| Resolution: This is now fixed. |
|
| 11 | 76730 | JR33951 | Maxlength asi property is incorrectly set to 0 for BAPI OUT and INOUT parameters |
| Symptom: For BAPI OUT and INOUT parameters, the maxlength asi property is incorrectly set to 0. As a result, maxlength restriction is not imposed on these parameters. |
| Resolution: This is now fixed. |
|
| 12 | 77941 | JR33598 | The adapter does not use the value set for "Use SAP Field names" checkbox during Metadata Discovery |
| Symptom: The adapter always generates the Business Object attributes names in Camel casing inspite of the setting for "Use SAP Field names" checkbox during Metadata Discovery. |
| Resolution: This is now fixed. The adapter now provides options to choose casing for the Control Record and the Data Record separately |
|
| 13 | 75643 | JR29813 | When doing outbound using the BAPI WU interface, data was not correctly updated in the SAP EIS. |
| Symptom: When running an outbound using the BAPI WU interface, the adapter was resetting connection resource after each BAPI execution, thus resetting global state. This was causing BAPI called later not to get the latest values. |
| Resolution: This was corrected. The reset is now being called only once, after all BAPIs are executed. A new property was added in EMD for this feature. |
|
| 14 | 93528 | JR34574 | When two different business objects have the same name but different namespaces, inbound/outbound operations may fail. |
| Symptom: In multiple applications, if some Business Objects have the same BO name but different BO namespaces, inbound or outbound operation may fail, e.g., retreive may report NullPointerException. This issue impacts both inbound and outbound. |
| Resolution: Delivered a fix to not only use BO name but also namespace to differentiate BO during runtime. |
|
| 15 | 100313 | JR34869 | Adapter does not use connectionpool in the first pollcycle during "unordered" delivery. |
| Symptom: When using "unordered" delivery mode with "maximum connections" larger than 1, connection pool will not be used during the first poll cycle and NPE will be thrown. |
| Resolution: A fix has been delivered to have the ActivationSpec for one specific endpoint to be configured before polling for the first cycle, thus enable connection pool be used for "unordered" mode |
|
| This table lists the enhancements and fixes in fix pack version 6.1.0.4. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 75473 | | The adapter returns old information/data from the SAP EIS. |
| Symptom: When the adapter retrieves data that was recently modified, the values that were returned were not the latest values. |
| Resolution: The adapter resets all connection resources before retrieving data, thereby, retrieving the latest data. |
|
| 2 | 75474 | | JCO Connection pool error during server restart |
| Symptom: After restarting the server, some of the deployed modules threw an exception which looks like:
MessageEndpoint activation failed for ActivationSpec com.ibm.j2ca.sap.SAPActivationSpecWithXid and MDB Application SAPInboundInvoiceServiceApp#SAPInboundInvoiceServiceEJB.jar#export.interfaces.SAPInvoiceInboundInterfaceEIS, due to the following exception:
com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool boy.novo.dk is removed.
at com.sap.mw.jco.JCO$Pool.getClient(JCO.java:5006) |
| Resolution: The adapter now uses a unique pool name for all applications and the symptom is no longer reproducible. |
|
| 3 | 75643 | | While running an outbound using the BAPI WorkUnit interface, the adapter resets the connection resource after executing each BAPI thereby resetting the global state. BAPI's executed later did not get the latest values. |
| Symptom: When running an outbound using the BAPI WorkUnit interface, the adapter was resetting connection resource after each BAPI execution, thus resetting global state. This was causing BAPI called later not to get the latest values. |
| Resolution: The adapter now resets the connection resource only after executing all BAPIs. |
|
| 4 | 96037 | | When a simple BAPI call fails, the adapter does not rollback to remove table locks. |
| Symptom: While using the BAPI_GOODSMVT_CREATE BAPI, the adapter does not rollback correctly in cases of failure. |
| Resolution: This has been corrected. The adapter now rolls back correctly after any failure. |
|
| 5 | 96094 | | ALE inbound fails with a null pointer exception after applying JR26701 on WPS. |
| Symptom: The adapter was still excepting the WebSphere Process Server runtime to return an exception when the attribute being queries does not exist. The WebSphere Process Server runtime now returns a NULL instead this leading to an NullPointerException. |
| Resolution: The adapter can now handle a NULL if the BO.getProperty() call fails, in line with the API specification change. |
|
| 6 | 75522 | | The adapter does not support more than four BAPIs in the EMD Object selection screen. |
| Symptom: When more than four BAPIs are selected for processing during an inbound EMD, the adapter does not correctly generate the artifacts and the event processing fails. |
| Resolution: The adapter can now handle more than four BAPIs and it generates the artifacts correctly. |
|
| 7 | 92875 | | During inbound processing, if you select three BAPIs, an index out of range error is thrown during EMD. |
| Symptom: In the Configure Composite Properties panel, if you select three BAPI's and click on Next, the following error message is displayed: Error in creating schema files. Array index out of range: 3 |
| Resolution: The EMD now completes properly for any number of BAPIs. |
|
| 8 | 92924 | | An error message is always displayed at runtime, without any effect on the behavior. |
| Symptom: While running any inbound or outbound scenario, the following error message is always dispayed, without any impact on runtime:
[10/14/08 16:55:44:890 CST] 00000093 LogUtils E SAPRFCDataBinding getDataObject CWYBS0499E: An invalid key was encountered while the adapter was using Resource Bundle com.ibm.j2ca.sap.LogMessages with Locale en_US. The key is either null or an empty string. |
| Resolution: This issue has been fixed. |
|
| 9 | 75748 | | Commit or Rollback on BAPI should be done by the container. |
| Symptom: The adapter was calling the Commit or Rollback functionality on its own and not based on the request by the container. |
| Resolution: This has been fixed. Adapter will now call Commit or Rollback as per container request if it is Local Transaction. When NoTransaction is used, the adapter does an automatic auto-Commit/Rollback |
|
| 10 | 75654 | | When the Import or Export section of a BAPI (instead the Tables section) contains tables, then a BAPI fails. |
| Symptom: During runtime, a BAPI call with Table parameters in the Import or Export section fails with the exception:
CWYAP2044:The Z_READ_PRICING_DATA BAPI (without transaction) failed.
Error: Cannot convert field CONFIG of type TABLE to JCO.Structure
Explanation=In the input BAPI business object, the data, metadata or both are incorrect. |
| Resolution: The adapter now supports Table parameters in the Import/Export section. |
|
| 11 | 75545 | | The adapter EMD throws "Error: nothing found" while discovering certain BAPIs. |
| Symptom: When we attempt to discover a nested BAPI(more than 2 levels deep) using the EMD Discovery screen, ESD wizard connects to SAP with the Filter, if specified. While retrieving the metadata from SAP, the wizard terminates with the error ("Nothing found"). |
| Resolution: The adapter can now handle nested BAPIs in the discovery screen. |
|
| 12 | 75649 | | Decimal fields are not saved in BAPIs. |
| Symptom: When decimal fields are present in a BAPI, there are errors in the return type. |
| Resolution: The adapter can now correctly handle decimal fields in BAPI parameters. |
|
| 13 | 75878 | | When more than one inbound application is running, during startup an error message is displayed stating that the JCO pool name already exists. |
| Symptom: When the first inbound application is started, the hostname of the SAP system is used as the pool name. When more than one application is started simultaneously, an error message is displayed stating that the JCO pool name already exists. |
| Resolution: The adapter now creates unique pool names for each inbound module. |
|
| 14 | 75880 | | 1475880ALE inbound listener threads still remain and are not killed after the application is stopped |
| Symptom: When running an inbound ALE module, some listener threads still remain and try to process idocs even after the application is stopped. |
| Resolution: This has been fixed. Listener threads are killed after the application stops. |
|
| 15 | 76039 | | ESD fails if two BAPIs have the same field names, separted by a '_'. |
| Symptom: When you select two BAPIs in the SCI interface ESD with field names that differ by a _ alone(though the structures are the same), the ESD fails to generate the artifacts. |
| Resolution: This has been fixed. The adapter now ignores case while trying to generate the second XSD. |
|
| 16 | 92923 | | An error message displayed in the log when running ALE outbound without a Business Graph. |
| Symptom: If you deploy an ALE outbound module, uncheck "Generate business graph" in EMD, and deploy it in WebSphere Process Server there is an exception logged at runtime eventhough the functionality works fine -
[10/14/08 15:27:03:406 CST] 0000006d LogUtils E com.ibm.j2ca.sap.ale.outbound.AleInvoker postIDoc CWYAP3068:Cursor.getNext() method call failed, verify that the input business object Cursor com.ibm.j2ca.extension.dataexchange.sdo.InputCursorSDO@61b261b2 data is initialized. Error Message: Exception while getting accessor. Please make sure property exists with accessor name verb Explanation=The input data has not been populated in the input business object Cursor. UserAction=Input business object data may not have been initialized in the business object specified in the error message, make sure data in initialized before calling getNext(). |
| Resolution: This has been fixed. The adapter now displays an Information message in the log file. |
|
| 17 | 92929 | | Log file has no information about the partner character set information. |
| Symptom: If an incorrect value is given to the partner character set, like abc123, the adapter does not log an error indicating that the value set is not valid. |
| Resolution: This has been fixed. The adapter now displays an appropriate log message. |
|
| 18 | 93147 | | When you deploy SAP adapter module on WebSphere Process Server, IllegalCharsetNameException is thrown. |
| Symptom: If no value is specified for the Partner character set, the adapter throws an IllegalCharsetNameException at runtime. |
| Resolution: This has been fixed. The adapter does not throw the exception if no value is set. The default value is used instead. |
|
| 19 | 76089 | | SQI without Business Graph throws an exception |
| Symptom: Executing SQI without BG throws the following exception:
com.ibm.websphere.sca.ServiceRuntimeException: DataBinding Exception thrown in J2CMethodBindingImpl.invoke() commonj.connector.runtime.DataBindingException: Failed to initialize cursor at com.ibm.ws.sca.internal.j2c.J2CMethodBindingImpl.invoke(J2CMethodBindingImpl.java:360)
at com.ibm.ws.sca.internal.j2c.J2CInterfaceBindingImpl.invoke(J2CInterfaceBindingImpl.java:118)
at com.ibm.ws.sca.internal.j2c.handler.J2CImportHandler.invokeDynamicImport(J2CImportHandler.java:1044)
at com.ibm.ws.sca.internal.j2c.handler.J2CImportHandler.processMessage(J2CImportHandler.java:338)
at ..................
|
| Resolution: This has been fixed. |
|
| 20 | 76042 | | Adapter throws an error if the data record is not populated. |
| Symptom: When using one or more SAPRequestNodes, the adapter fails to complete subsequent request after a failure. |
| Resolution: This has been fixed. |
|
| 21 | 75794 | | Poor service diagnostics for wrongly configured SAP Gateway host setting. |
| Symptom: The Adapter does not throw an exception if the gateway host setting is wrongly configured. It only logs a trace of the issue - thus the Message Broker cannot catch an exception to be able to report the issue to the user. |
| Resolution: This has been fixed. |
|
| 22 | 75795 | | Building Connection with Async q/tRFC BAPI with Out Params gives bad error. |
| Symptom: The adapter continues to execute a q/tRFC BAPI request which has a required Output paramater. Since the q/tRFC call is async, required Output parameters cannot be supported. |
| Resolution: This has been fixed. The adapter does not allow completion of the EMD wizard when selected BAPIs have required Output parameters for executing a q/tRFC BAPI call. |
|
| 23 | 75814 | | While using the adapter connection wizard to build an Inbound to SAP adapter, if you set only "Gateway Service" and omit "Gateway Host" the following error message is thrown: throw NullPointerException SAPManagedConnectionFactory.isGatewayConfigured |
| Symptom: The Adapter Connection Wizard can allow a user to build an Inbound to SAP Adapter that will throw NullPointerException SAPManagedConnectionFactory.isGatewayConfigured if they only set "Gateway Service" and omit "Gateway Host". |
| Resolution: This has been fixed. |
|
| 24 | 76058 | 46390,082,000 | The JCA SAP adapter does not correctly generate the operation name for inbound using extension IDocs. |
| Symptom: The adapter was generating a different operation name during the EMD run and another at runtime. This mismatch caused a FunctionSelectorException at runtime. |
| Resolution: This has been fixed. |
|
| 25 | 90460,217,631 | | The time fields are being translated to hhmmss format(0-12hr format) with missing AM/PM information. |
| Symptom: Adapter returns the time value in 12 hour format without the AM/PM information which is not complete. |
| Resolution: The adapter now sends the time in 24 hour format correctly. |
|
| 26 | 52930,SGC,724 | | Adapter messages incorrectly uses the event type "E" |
| Symptom: BAPI trace messages that are actually non-error messages incorrectly uses the event type "E". |
| Resolution: This has been fixed. |
|
| 27 | 76149 | 40278,999,858 | The JCA SAP Adapter does not handle multibyte characters from non-Unicode systems correctly. |
| Symptom: When using the QISS module to retrieve data from a non-Unicode system, the BO gets filled incorrectly as soon as table contains multibyte characters. |
| Resolution: The adapter now correctly handles multibyte characters from non-Unicode systems. |
|
| 28 | 76163 | 52369,SGC,724 | The adapter does not serialize a complex IDoc structure correctly in the endpoint. |
| Symptom: A BO dump of a complex, multi-segment IDoc is not serialized correctly. |
| Resolution: This has been fixed. |
|
| 29 | 75915 | | Nullname space support in base class. |
| Symptom: Base class doesn't support null namespace using 6.1 adapter. |
| Resolution: This has been fixed. |
|
| 30 | 93155 | | TypeFactory is using ext classloader instead of application classloader in WAS. |
| Symptom: Class.forName method could not find the record and throws Business Object not found exception and Inbound on ALE fails. |
| Resolution: This has been fixed. |
|
| 31 | 76299 | | Adapter on WebSphere Transformation Extender throws a NullPointerException. |
| Symptom: NullPointerException thrown while performing outbound or inbound communication with Websphere Adapter on WebSphere Transformation Extender. |
| Resolution: No more NullPointerExceptions are thrown by the Adapter on WebSphere Transformation Extender while performing outbound and inbound operation. |
|
| 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. |
|