| This table lists the enhancements and fixes in interim fix version 7.5.0.4. |
| Enhancements |
| There are no enhancements in this interim fix. |
| Fixes |
| 1 | Defect 6830 | | CI Only - CI - PMR 22000,004,000, time datatype of SAP not working properly in CI for SAP connector - JR42189
|
| Symptom: CI Only - CI - PMR 22000,004,000, time datatype of SAP not working properly in CI for SAP connector - JR42189 |
| Resolution: Fixed the issue |
|
| 2 | Defect 6851 | | CI Only - CI Item not present in the schema for table type parameter - JR41974.
|
| Symptom: CI Only - CI Item not present in the schema for table type parameter - JR41974. |
| Resolution: Fixed the issue |
|
| 3 | Defect 7037 | | CI Only - ForwardFit JR 42125 : With DateAsString set, exception is thrown when accessing uninitialised date.
|
| Symptom: CI Only - ForwardFit JR 42125 : With DateAsString set, exception is thrown when accessing uninitialised date |
| Resolution: Fixed the issue |
|
| 4 | Defect 7079 | | CI Only - Cast Iron PMR 47804 019 866 receive idoc with control record name issue (migration causes problem) - JR42357.
|
| Symptom: CI Only - Cast Iron PMR 47804 019 866 receive idoc with control record name issue (migration causes problem) - JR42357 |
| Resolution: Fixed the issue |
|
| 5 | Defect 7098 | | CI Only - JCo Repository cache needs to be cleared when EMD is closed- Fwd Fit of 7035 - JR42187.
|
| Symptom: CI Only - JCo Repository cache needs to be cleared when EMD is closed- Fwd Fit of 7035 - JR42187 |
| Resolution: Fixed the issue |
|
| 6 | Defect 7113 | | CI Only - Cast Iron JR39474 :PMR 47765 019 866 send idoc problem (adpter looking for data in the XML even if schema element it is minOccurs=0).
|
| Symptom: CI Only - Cast Iron JR39474 :PMR 47765 019 866 send idoc problem (adpter looking for data in the XML even if schema element it is minOccurs=0) |
| Resolution: Fixed the issue |
|
| 7 | Defect 7114 | | CI Only - Cast IronJR42351: PMR 48128,019,866 - old projects using extended idoc is not working for send idoc activity.
|
| Symptom: CI Only - Cast IronJR42351: PMR 48128,019,866 - old projects using extended idoc is not working for send idoc activity |
| Resolution: Fixed the issue |
|
| 8 | Defect 7156 | | CI Only - cast iron PMR 48128,019,866 segment names in the idoc has randon number appended to it.
|
| Symptom: CI Only - cast iron PMR 48128,019,866 segment names in the idoc has randon number appended to it |
| Resolution: Fixed the issue |
|
| 9 | Defect 7186 | | CI Only - PMR 48828,019,866 CI attributes type in genertaed schemas of the idoc should be xsd:string but it is anySimpleType.
|
| Symptom: CI Only - PMR 48828,019,866 CI attributes type in genertaed schemas of the idoc should be xsd:string but it is anySimpleType |
| Resolution: Fixed the issue |
|
| 10 | Defect 7187 | | CI Only - PMR 48828,019,866 CI Default value should be populated for attributes in the generated schemas for idocs.
|
| Symptom: CI Only - PMR 48828,019,866 CI Default value should be populated for attributes in the generated schemas for idocs |
| Resolution: Fixed the issue |
|
| 11 | Defect 7255 | | CI Only - CI PMR 49881,019,866 Addtional fields in idoc need to be generated based on a hidden configuration property - JR43091.
|
| Symptom: CI Only - CI PMR 49881,019,866 Addtional fields in idoc need to be generated based on a hidden configuration property - JR43091 |
| Resolution: Fixed the issue |
|
| 12 | Defect 7537 | | CI Only - CI : SAP Adapter not displaying some rfcs during EMD in Japanese locale - PMR 36658,69C,760 - JR43087.
|
| Symptom: CI Only - CI : SAP Adapter not displaying some rfcs during EMD in Japanese locale - PMR 36658,69C,760 - JR43087 |
| Resolution: Fixed the issue |
|
| 13 | Defect 7859 | | CI Only - ALE Inbound fails for all idocs on CastIron.
|
| Symptom: CI Only - ALE Inbound fails for all idocs on CastIron |
| Resolution: Fixed the issue |
|
| 14 | Defect 8099 | | CI Only - CI : SAP RFC Inbound gives malformed XML
|
| Symptom: CI Only - CI : SAP RFC Inbound gives malformed XML |
| Resolution: Fixed the issue |
|
| 15 | Defect 8148 | | CI: Connections are not getting closed for IDOCs in SAP Adapter for Cast Iron runtime.
|
| Symptom: CI: Connections are not getting closed for IDOCs in SAP Adapter for Cast Iron runtime |
| Resolution: Fixed the issue |
|
| 16 | Defect 8162 | | CI - TransactionId should not be generated in the schema for synchronous BAPI inbound mode.
|
| Symptom: CI - TransactionId should not be generated in the schema for synchronous BAPI inbound mode |
| Resolution: Fixed the issue |
|
| 17 | Defect 8677 | | CI Only -Foward Fit - JR41999 The maximum length ASI of the time and date fields should be increased by 2 (7501_IF07).
|
| Symptom: CI Only -Foward Fit - JR41999 The maximum length ASI of the time and date fields should be increased by 2 (7501_IF07) |
| Resolution: Fixed the issue |
|
| 18 | Defect 8678 | | CI Only - ForwardFit - 7976 Cast Iron: JCO_ERROR_ILLEGAL_STATE exception is thrown when multiple Receive IDoc activities connecting to the same endpoint are started simultaneously (7501_IF12).
|
| Symptom: CI Only - ForwardFit - 7976 Cast Iron: JCO_ERROR_ILLEGAL_STATE exception is thrown when multiple Receive IDoc activities connecting to the same endpoint are started simultaneously (7501_IF12) |
| Resolution: Fixed the issue |
|
| 19 | Defect 8979 | | CI Only - ForwardFit - 8147 Cast Iron : The Adapter throws NullPointerException if the TABNAM field in the ControlRecord of a IDoc in the Send ALE is not populated (7501_IF12).
|
| Symptom: CI Only - ForwardFit - 8147 Cast Iron : The Adapter throws NullPointerException if the TABNAM field in the ControlRecord of a IDoc in the Send ALE is not populated (7501_IF12) |
| Resolution: Fixed the issue |
|
| 20 | Defect 8680 | | ForwardFit - 8016 SAP Adapter prints messages at INFO level during outbound operation. (7501_IF12).
|
| Symptom: ForwardFit - 8016 SAP Adapter prints messages at INFO level during outbound operation. (7501_IF12) |
| Resolution: Fixed the issue |
|
| 21 | Defect 8747 | | CI 6199 : BAPI Inbound not working.
|
| Symptom: CI 6199 : BAPI Inbound not working |
| Resolution: Fixed the issue |
|
| 22 | Defect 8761 | | CI ForwardFit - JR44574 - 7501_IF14
|
| Symptom: CI ForwardFit - JR44574 - 7501_IF14 |
| Resolution: Fixed the issue |
|
| 23 | Defect 8762 | | CI only : JCO_ERROR_RESOURCE exception is thrown when multiple Receive IDoc activities connecting to the same endpoint are started simultaneously.
|
| Symptom: CI only : JCO_ERROR_RESOURCE exception is thrown when multiple Receive IDoc activities connecting to the same endpoint are started simultaneously |
| Resolution: Fixed the issue |
|
| This table lists the enhancements and fixes in interim fix version 7.5.0.3. |
| Enhancements |
| 1 |
Defect 8216 |
|
Generating schema in SAP PI standards for BAPI inbound |
| Generating schema in SAP PI standards for BAPI inbound. |
|
|
| Fixes |
| 1 |
Defect 8222 |
|
send idoc problem (adpter looking for data in the XML even if schema element it is minOccurs=0) |
| Symptom: send idoc problem (adpter looking for data in the XML even if schema element it is minOccurs=0) |
| Resolution: Fixed the issue |
|
| 2 |
Defect 7141 |
|
PMR 48896,019,866: BAT: Send Idoc error while sending ALEAUD01 |
| Symptom: Error occurred while trying to execute activity Send IDOC *
* Effected Idoc Field Field "ALEAUD01/IDOC/E1ADHDR/E1STATE/DOCNUM" , *
* the type is "string" but when use "MOP1111" and "MOP", there will *
* be error . |
| Resolution: Fixed the issue |
|
3 |
Defect 7172 |
JR42301 |
cast iron PMR 48128,019,866 segment names in the idoc has randon number appended to it |
| Symptom: cast iron PMR 48128,019,866 segment names in the idoc has randon number appended to it |
| Resolution: Fixed the issue,Originally delivered as 7003_IF23. |
|
4 |
Defect 7197 |
|
ALEPT Inbound Idoc Data Stream for Packet Idoc does not have complete data. |
| Symptom: ALEPT Inbound Idoc Data Stream for Packet Idoc does not have complete data. |
| Resolution: Fixed the issue |
|
| 5 |
Defect 7199 |
|
Bapi Bank.Change is not working in CastIron |
| Symptom: With the bapi, Bank.Change, user is not able to change the bank details of existing bank.
In castiron ,
Activity used is - Invoke BAPI
Commit transaction option is checked. |
| Resolution: Fixed the issue |
|
| 6 |
Defect 7208 |
|
ALE Inbound with PI enabled for Extended IDocs throws Exception |
| Symptom: ALE Inbound with PI enabled for Extended IDocs throws Exception |
| Resolution: Fixed the issue |
|
| 7 |
Defect 7217 |
|
Extension IDoc SOWMYAEXT does not work in RAD/WAS |
| Symptom: ALE Inbound for extension IDoc SOWMYAEXT fails with the following exception:
Caused by: commonj.connector.runtime.SelectorException: Business object definition for 'SapACwmZAllSapDatatypesSowmyaext' in namespace 'com.ibm.xmlns.prod.websphere.j2ca.sap.sapacwmzallsapdatatypessowmyaext' |
| Resolution: Fixed the issue |
|
| 8 |
Defect 7381 |
|
retriveall for QISS table is returning all records irrespective of giving child field column |
| Symptom: retriveall for QISS table is returning all records irrespective of giving child field column |
| Resolution: Fixed the issue |
|
| 9 |
Defect 7619 |
JR42632 |
When ALE QRFC with audit update is enabled, status code of AUDIT (ALEAUD) idoc on SAP is 75 instead on 64. (7004_IF09) |
| Symptom: When ALE QRFC with audit update is enabled, status code of AUDIT (ALEAUD) idoc on SAP is 75 instead on 64. (7004_IF09) |
| Resolution: Fixed the issue |
|
| 10 |
Defect 7620 |
JR42645 |
JCO Resource error when applications have transactionality set to yes as well as no. (7003_IF26) |
| Symptom:JCO Resource error when applications have transactionality set to yes as well as no. (7003_IF26) |
| Resolution: Fixed the issue |
|
| 11 |
Defect 7621 |
JR42462 |
ALEPT INBOUND IDOC DATA STREAM FOR PACKET IDOC DOES NOT HAVE COMPLETE DATA. (7501_IF10) |
| Symptom: ALEPT INBOUND IDOC DATA STREAM FOR PACKET IDOC DOES NOT HAVE COMPLETE DATA. (7501_IF10) |
| Resolution: Fixed the issue |
|
| 12 |
Defect 7836 |
JR43029 |
SYNC BAPI DISCOVERED AS ASYNC IN EMD, FAILS DURING RUNTIME SAYING TID IS NULL. |
| Symptom:When a Sync BAPI is discovered as Async in EMD, it fails during
runtime saying TID is null |
| Resolution: Fixed the issue |
|
| 13 |
Defect 8447 |
|
BAPI Inbound with BOR for SAP Naming Convension (PI) is failing |
| Symptom: Business object definition for 'BAPI_CUSTOMER_GETDETAIL' in namespace 'urn:sap-com:document:sap:business' not found... |
| Resolution: Fixed the issue |
|
| 14 |
Defect 8513 |
|
Iterative Discovery (for PI enabled application) on adding RFC to an existing BOR BAPI module fails |
| Symptom: A module with existing BOR BAPIs added. Do iterative discovery and add RFC.
The new BAPI added runs however the older ones fail |
| Resolution: Fixed the issue |
|
| 15 |
Defect 8081 |
|
PI with BAPI BOR fails at EMD step |
| Symptom: PI with BAPI BOR fails at the discovery EMD step and gives a NullPointerException |
| Resolution: Fixed the issue |
|
| 16 |
Defect 8236 |
|
Segment names in the idoc has randon number appended to it |
| Symptom: Segment names in the idoc has randon number appended to it |
| Resolution: Fixed the issue |
|
| 17 |
Defect 8349 |
|
SAP RFC Inbound gives malformed XML |
| Symptom: SAP RFC Inbound functionality gives malformed XML whilst running in asynchronous mode |
| Resolution: Fixed the issue |
|
| 18 |
Defect 8321 |
|
ALE Outbound with SAP Naming Convention Failed to delivery the Idoc if we have more than one IDOC configured in a sinlge module |
Symptom: Configure two IDocs for ALE Outbound with SAP Naming Convention (PI). Then Execute both the Idocs.
IDoc with the Xsd generated with random number for IDOC business object will fail |
| Resolution: Fixed the issue |
|
| 19 |
Defect 8231 |
JR42189 |
Time datatype of SAP not working properly in cast iron for SAP connector |
| Symptom: Time datatype of SAP not working properly in cast iron for SAP connector |
| Resolution: Fixed the issue |
|
| 20 |
Defect 8294 |
|
With DateAsString set, exception is thrown when accessing uninitialised date |
| Symptom: With "Date as a String" property enabled, the Adapter throws an exception "Trying to access row values in a table which does not have any rows yet" when accessing an uninitialized date field |
| Resolution: Fixed the issue |
|
| 21 |
Defect 8232 |
JR41974 |
CI Item not present in the schema for table type parameter |
| Symptom: CI Item not present in the schema for table type parameter |
| Resolution: Fixed the issue |
|
| 22 |
Defect 8234 |
JR42187 |
JCo Repository cache needs to be cleared when EMD is closed |
| Symptom: JCo Repository cache needs to be cleared when EMD is closed |
| Resolution: Fixed the issue |
|
| 23 |
Defect 8233 |
JR42125 |
With DateAsString set, exception is thrown when accessing uninitialised date |
| Symptom: With DateAsString set, exception is thrown when accessing uninitialised date |
| Resolution: Fixed the issue |
|
| 24 |
Defect 8237 |
|
CI attributes type in genertaed schemas of the idoc should be xsd:string but it is anySimpleType |
| Symptom: CI attributes type in genertaed schemas of the idoc should be xsd:string but it is anySimpleType |
| Resolution: Fixed the issue |
|
| 25 |
Defect 8238 |
|
Default value should be populated for attributes in the generated schemas for idocs |
| Symptom: Default value should be populated for attributes in the generated schemas for idocs |
| Resolution: Fixed the issue |
|
| 26 |
Defect 8235 |
JR42351 |
Old projects using extended idoc is not working for send idoc activity |
| Symptom: PMR 48128,019,866 - old projects using extended idoc is not working for send idoc activity |
| Resolution: Fixed the issue |
|
| This table lists the enhancements and fixes in interim fix version 7.5.0.2. |
| Enhancements |
| 1 | CR 76052 | | Password less authentication (SSO / X509) using SAP adapter |
| Support for Password less authentication (SSO / X509) using SAP adapter. |
|
|
| Fixes |
| 1 | | | For ALE "SAP Field Names " Options when "Send IDoc with unparsed data record" option is enabled |
| Symptom: For ALE "SAP Field Names " Options when "Send IDoc with unparsed data record" option is enabled. |
| Resolution: This problem is now Fixed. |
|
| 2 | | | For ALE Invalid IDoc version does not throws the errors, when IDocs are discovered by file |
| Symptom: For ALE Invalid IDoc version does not throws the errors, when IDocs are discovered by file. |
| Resolution: This problem is now Fixed. |
|
| 3 | CR103628 | | During trfc Inbound calls, the events are duplicated or lost. |
| Symptom: During trfc Inbound calls, the events are duplicated or lost. |
| Resolution: This problem is now Fixed. |
|
| 4 | | JR40936 | Data cross over happens when global variables are used in ABAP program. |
| Symptom: Data cross over happens when global variables are used in ABAP program. |
| Resolution: This problem is now Fixed. |
|
| 5 | | JR41367 | Nested structure output schema being generated with CastIron |
| Symptom: Nested structure output schema being generated with CastIron. |
| Resolution: This problem is now Fixed. |
|
| 6 | | JR41368 | Table types in Import and Export parameters should contain a item field during PI standard artifact generation. |
| Symptom: CTable types in Import and Export parameters should contain a item field during PI standard artifact generation. |
| Resolution: This problem is now Fixed. |
|
| 7 | | | ALE_Pass_Through is failing for generic idoc |
| Symptom: Ale_Pass_Through with generic idoc is failing with the following error "Business object definition for the BO in namespace not found".. |
| Resolution: This problem is now Fixed. |
|
| 8 | | | Advanced Configuration Properties does not contain explanation for a field |
| Symptom: Advanced Configuration Properties does not contain explanation for a field. |
| Resolution: This problem is now Fixed. |
|
| 9 | | | ALE Outbound Fails with Null Pointer Exception |
| Symptom: During EMD create Outbound -> ALE -> Orders05/Alereq01 -> Fails with Null Pointer Exception. |
| Resolution: This problem is now Fixed. |
|
| 10 | | | Language not being considered when used dynamically. |
| Symptom: On using language as one of the dynamic parameter for testing it is observed that a new connection is not made in SAP for new language. |
| Resolution: This problem is now Fixed. |
|
| 11 | | | SNC token not getting printed in the traces when the logging is set to finest |
| Symptom: SNC token not getting printed in the traces when the logging is set to finest. |
| Resolution: This problem is now Fixed. |
|
| 12 | | | Optional Parameter information are not sync when we do iterative discovery for BAPI. |
| Symptom: Optional Parameter information are not sync when we do iterative discovery for BAPI. |
| Resolution: This problem is now Fixed. |
|
| 13 | | JR41324 | In case of wrong credential it's not showing proper error message but generating FFDC on RAD/WAS |
| Symptom: In case of wrong credential it's not showing proper error message but generating FFDC on RAD/WAS. |
| Resolution: This problem is now Fixed. |
|
| 14 | | JR41974 | The variables with nested table type parameters are not generated correctly during PI style artifact generation |
| Symptom: The variables in import and export parameters which contain nested table type parameter is not generated correctly during PI generation. The item element is not generated in the schema |
| Resolution: This problem is now fixed to include an item element for every table type parameter in the schema. |
|
| 15 | | JR42125 | Exception is thrown by the SAP Adapter when serializing a BAPI response containing an uninitialized date field |
| Symptom: An exception is thrown when serializing a BAPI response containing an uninitialised date field, if the schemas are generated with date field as a string parameter. |
| Resolution: This problem is now fixed to read the value from the BAPI table only for initialised fields. |
|
| 16 | | JR42645 | JCO Resource error when applications have transactionality set to yes as well as no. |
| Symptom: When applications are deployed with transaction set to yes as well as no we see JCO resource error if the same managed connection is being used from the connection pool. |
| Resolution: This problem is now fixed. |
|
| 17 | | JR43619 | SAP ADAPTER 7502_IF01, WHEN BAPI OUTBOUND IS RUN AFTER ALE
OUTBOUND FAILS WITH NPE. |
| Symptom: BAPI outbound run after ALE Outbound fails with NPE as the connection pool size is set to 1. |
| Resolution: This problem is now fixed. |
|
| This table lists the enhancements and fixes in interim fix version 7.5.0.1. |
| Enhancements |
| 1 | CR102203 | | BAPI schema generated from BOR and RFC discovery has some minor changes. |
| Symptom: Adapter to generate all the top level elements in camel case for BAPI. CI code which invoke EMD APIs will notify adapter whether to generate top level eleme. |
| Resolution: This problem is now fixed. |
|
| 2 | CR102338 | | Different between the generated schema for Idoc typ. |
| Symptom: The artifacts generated when using PI enabled should be the same as in CI. |
| Resolution: This problem is now fixed. |
|
| 3 | CR102337 | | IDOC - ComplexType names for segment. |
| Symptom: Adapter generates a complex type with the name of segment definition name and in camel case. Adapter should generate complex element name as segment type but annotation should have segment definition name so that there is no adapter runtime changes required. |
| Resolution: This problem is now fixed. |
|
| 4 | CR102336 | | IDOC - MessageType is required for CI UI |
| Symptom:IDOC - MessageType is required for CI UI . |
| Resolution: This problem is now fixed. |
|
| 5 | CR103078 | | SAP Idoc Library to be used for Idoc processing |
| Symptom:To track the usage of idoc library for idoc processing . |
| Resolution: This problem is now fixed. |
|
| 6 | CR103254 | | Reading additional tables to get number of decimals and computing max length. |
| Symptom:Reading additional tables to get number of decimals and computing max length. Observed to be causing major performance degradation. These values can be retrieved using JCo API. Refer SAP JCo API for more information . |
| Resolution: This problem is now fixed. |
|
| 7 | CR103498 | | SAP WMB Events enhancements - Monitoring. |
Symptom:CEI events are emitted at the following points:
connection success, connection failure, connection close and authentication failure. |
| Resolution: This problem is now fixed. |
|
| 8 | CR102956 | | Submitted Single RFC Program ID support. |
| Symptom:To support Single RFC Program ID |
| Resolution: This problem is now fixed. |
|
| 9 | CR76336 | | SAP EMD adds random numbers to the end of duplicate field names. |
| Symptom:SAP EMD adds random numbers to the end of duplicate field names |
| Resolution: This problem is now fixed. |
|
| 10 | CR102472 | | Provide Control Record structure r Ale Pass through Generic IDoc. |
| Symptom:Provide Control Record structure r Ale Pass through Generic IDoc |
| Resolution: This problem is now fixed. |
|
| 11 | CR102327 | | BAPI discovery UI Changes |
| Symptom:BOR Discovery UI not same as other discoveries |
| Resolution: This problem is now fixed. |
|
| 12 | CR102329 | | BAPI - generated schema changes for CI |
| Symptom:when user sets SAP original casing, not only simple element names should be in original casing but also element which are complex should also appear in original case. |
| Resolution: This problem is now fixed. |
|
| 13 | CR102332 | | BAPI namespace changes and table type schema generation changes for CI |
| Symptom: XXXXX |
| Resolution: This problem is now fixed. |
|
| 14 | CR102331 | | BAPI toplevel BO name changes |
| Symptom: When the "Generate business objects in SAP XI Standard" is switched ON, the top level business object schema will be split into two parts: Request and Response. The request schema will contain the IN parameters, INOUT / changing parameters. The response schema will contain the OUT, INOUT / Changing parameters. |
| Resolution: This problem is now fixed. |
|
| 15 | CR101971 | | Serviceability Enhancement |
| Symptom: Support for CPIC traces. |
| Resolution: This problem is now fixed. |
|
| 16 | 5486(RTC) | | Serviceability Enhancement |
| Symptom: JCoAPI traces to be traced into SAP Adpater traces |
| Resolution: This problem is now fixed. |
|
| 17 | CR102400 | | Performance of RFC discovery |
| Symptom:RFC Discovery will take less time. Run EMD and calculate the time for discovery and compare with previous versions. |
| Resolution: This problem is now fixed. |
|
| 18 | CR103566 | | In ALE Interface provide an option in EMD to choose the optional segments Submitted |
| Symptom:In ALE , EMD Discovery panel provided the option to choose the optional segments |
| Resolution: This problem is now fixed. |
|
| Fixes |
| 1 | 5821(RTC) | | Artifacts generated with 7500 RAR is failing on running with 7501 RAR.. |
| Symptom: The condition to instantiate the handler for older artifacts is wrong. |
| Resolution: This problem is now fixed. |
|
| 2 | CR103763 | | CI: Filterproperty discovery by name should be default behavior for even negative. |
| Symptom:Filter property value discovery by name should be default value for all positive and negative cases. Even if use input anything other than discovery by name then also it should use discovery by name. Adapter should do discover by description only if user explicitly select it . |
| Resolution: This problem is now fixed. |
|
| 3 | 5981(RTC) | | Negative value is being accepted for "Connection Retry Interval. |
| Symptom: Negative values are being accepted for "Connection Retry Interval" of "Additional connection configuration" tab of "Specify the Service Generation and Deployment Properties" screen in inbound ALE scenario. |
| Resolution: This problem is now fixed. |
|
| 4 | 5849(RTC) | | Iterative Discovery does not shows the Foreign Key relationship for BAPI RS using BOR. |
| Symptom: Create a BAPI Result set using BOR for Customer GetList & GetDetail with the foreign key relationship.
Complete the EMD and do a iterative discovery for the same VOR module and move to the Config objects Panel. The EMD should show the already selected foreign key, but its doesn't show. |
| Resolution: This problem is now fixed. |
|
| 5 | CR103693 | | CI: Response schema order is not maintinaed for BAPI and RFC. |
| Symptom: BAPI elements attributes and tables order is not maintained as we read from SAPServer. |
| Resolution: This problem is now fixed. |
|
| 6 | CR103253 | | When a transactional RAR is used, QRFC qNames are retrieved during EMD. |
| Symptom: The queue names have to be retrieved only when qRFC is selected. This degrades performance for non-qRFC scenarios as well and takes a bit longer for schema generation, there by delay in EMD run. |
| Resolution: This problem is now fixed. |
|
| 7 | CR103251 | | Internationalized strings used as property names. |
| Symptom:Name of Properties should not be internationalized. These names are not presented to the user. Currently, the property names are found to be internationalized. |
| Resolution: This problem is now fixed. |
|
| 8 | CR102981 | | SAP schema generation is slow for BAPI/RFC. |
| Symptom: SAP BOR discovery has become very fast. But, the time taken to generate schema is bit longer than expected. |
| Resolution: This problem is now fixed. |
|
| 9 | CR102981 | | Optimized use of SAP ASI Metadata. |
| Symptom:Optimized use of SAP ASI Metadata during discovery and schema generation. This is also a code level optimization which has no functionality impact. |
| Resolution: This problem is now fixed. |
|
| 10 | CR103303 | | SAP BOR schema generation should generate key fields as xml attributes. |
| Symptom: SAP adapter while generating schema for BAPI -BOR , the key fields should be generated as xml attributes to the top level complex types. |
| Resolution: This problem is now fixed. |
|
| 11 | CR103302 | | AFC - XML attribute support in DESPI XML |
| Symptom: AFC - XML attribute support in DESPI XML. |
| Resolution: This problem is now fixed. |
|
| 12 | CR103442 | | Primary Key elements to be part of response BO for BOR - PI enabled |
| Symptom: The primary key elements which are represented as attributes should also be part of the response. Tables KEYFIELDS should be part of request and response.. |
| Resolution: This problem is now fixed. |
|
| 13 | CR103391 | | ** filter does not work with BOR discovery |
| Symptom: While discovering BOR, add ** to the filter for eg. customer** , nothing is discovered. |
| Resolution: This problem is now fixed. |
|
| 14 | CR103397 | | In BOR discovery objects with same name appended with a random number. |
| Symptom: In BOR discovery without PI enabled if any object have the description. The second object is appended with a random number.For eg,:In BOR discovery use "customer*" as filter criteria. In the nodes we could see nodes with names as customer and customer1534. |
| Resolution: This problem is now fixed. |
|
| 15 | CR103444 | | Discovery model for BOR changes when PI is enabled / disabled. |
| Symptom:Discovery model for BOR discovery with "Customer*" filter, changes when PI enabled and disabled. |
| Resolution: This problem is now fixed. |
|
| 16 | CR103148 | | SAPBapiRecord.getNext() method calling Cursor.completObject() more than once |
| Symptom:SAPBapiRecord.getNext() method calling Cursor.completObject() more than once . |
| Resolution: This problem is now fixed. |
|
| 17 | CR103099 | | BAPI: SAP EMD throw exception during EMD when try to search BAPI from BOR. |
| Symptom: SAP EMD throw exception during EMD when try to search BAPI from BOR |
| Resolution: This problem is now fixed. |
|
| 18 | 5705(RTC) | | No full stack trace exceptions thrown in the trace file for ALE Inbound Idocs. |
| Symptom: Exception is not found as expected. |
| Resolution: This problem is now fixed. |
|
| 19 | CR103691 | | CI: BAPI Bank.change schema elements order different from SAP GUI. |
| Symptom: BAPI Bank.change elements attributes and tables order is not maintained as we read from SAPServer. |
| Resolution: This problem is now fixed. |
|
| 20 | CR103692 | | CI: BAPI should differentiate table parameters. |
| Symptom: CI: BAPI should differentiate table parameters for request , response or both. |
| Resolution: This problem is now fixed. |
|
| 21 | 5612(RTC) | | Fix for DetectIllegalXMLCharacter Property in AFC 7.5.0.1 - Change needed in SAP adapter |
| Symptom:In v7.5, AFC allows the detect illegal XML character property to be supported for all runtimes. |
| Resolution: This problem is now fixed. |
|
| 22 | 5613(RTC) | | Unable to stop RFC traces, if switched from True to False. |
| Symptom: Unable to stop RFC traces, if switched from True to False. |
| Resolution: This problem is now fixed. |
|
| 23 | CR103616 | | Iterative discovery fails for Non PI BAPI. |
| Symptom: BOR iterative Discovery fails when run iterative discovery for BOR with PI not enabled. |
| Resolution: This problem is now fixed. |
|
| 24 | CR103617 | | The BOR EMD with wrapper option fails. |
| Symptom: BAPI discovery with generate wrapper enabled fails. |
| Resolution: This problem is now fixed. |
|
| 25 | 5633(RTC) | | ALE IB throws BO definition not found on WMB8 |
| Symptom: ALE IB throws BO definition not found on WMB8. |
| Resolution: This problem is now fixed. |
|
| 26 | CR103626 | | qRFC support for idoc inbound - idoc.jar. |
| Symptom: qRFC support for idoc inbound - idoc.jar. |
| Resolution: This problem is now fixed. |
|
| 27 | CR103621 | | CI migration order of elements in xsd. |
| Symptom: Order of BOR - RFC discovery should be same as that in SAP GUI when PI is enabled. |
| Resolution: This problem is now fixed. |
|
| 28 | CR103624 | | CI Migration for BOR fails - location issue. |
| Symptom: CI Migration issue. No impact on WPS and WMB users. |
| Resolution: This problem is now fixed. |
|
| 29 | CR103625 | | For classverb X. Attributes not to be generated. |
| Symptom: Only for CI not applicable for non CI users. |
| Resolution: This problem is now fixed. |
|
| 30 | CR103595 | | Headline:Handlers- ALE inbound scenario |
| Symptom:Inbound handler implementation is changed. BAPI (RFC, tRFC) , ALE (PT, Generic, IDoc) |
| Resolution: This problem is now fixed. |
|
| 31 | CR103441 | | LineType enhancement |
| Symptom:Supoort for fileld type NUMC,DEC,TIMS and INT4 has be implemented, Reference CR103441 . |
| Resolution: This problem is now fixed. |
|
| 32 | | JR39757 | BAPI_TRANSACTION_COMMIT ERROR NOT HANDLED CORRECTLY BY TXMANAGER |
| Symptom:BAPI_TRANSACTION_COMMIT ERROR NOT HANDLED CORRECTLY BY TXMANAGER . |
| Resolution: This problem is now fixed. |
|
| 33 | CR103140 | | CI Leverage IDocHandler functionality singleRFCProgramId Issue childof CR103078 |
| Symptom: CI Leverage IDocHandler functionality singleRFCProgramId Issue childof CR103078. |
| Resolution: This problem is now fixed. |
|
| 34 | CR103302 | | CI:XML attribute support in DESPI XML |
| Symptom: The BAPI schmea generated using BOR discovery should have all key fields as xml attribute to the toplevel complex type. Current XML DESPI implementation does not consider xml attribute for processing. |
| Resolution: This problem is now fixed. |
|
| 35 | CR103303 | | CI:SAP BOR schema generation should generate key fields as xml attributes |
| Symptom:SAP adapter while generating schema for BAPI -BOR , the key fields should be generated as xml attributes to the top level complex types. The CR is to do adapter changes for EMD and runtime. . |
| Resolution: This problem is now fixed. |
|
| 36 | CR103311 | | CI:IDoc tid information is not returned. |
| Symptom: CI:IDoc tid information is not returned. |
| Resolution: This problem is now fixed. |
|
| 37 | CR103420 | | CI: SAP adapter BAPI outbound giving wrong output for table parameter. |
| Symptom:The table parameter should be filled with array of objects instead the output is coming as nested. . |
| Resolution: This problem is now fixed. |
|
| 38 | CR103472 | | CI:SalesOrder.GetList - schema difference when compared to CI SAP Connector. |
| Symptom: Schema generated for SalesOrder.GetList BAPI has difference in element name 'Material' under Sales Order --> item. |
| Resolution: This problem is now fixed. |
|
| 39 | CR103510 | | CI: IDoc iterative discovery failing wit... |
| Symptom:CI: IDoc iterative discovery failing wit... |
| Resolution: This problem is now fixed. |
|
| 40 | CR103519 | | CI:IDoc schema having segment defination as element name instead of segment type. |
| Symptom: CI:IDoc schema having segment defination as element name instead of segment type. |
| Resolution: This problem is now fixed. |
|
| 41 | CR103568 | | CI: IDoc value returned by inbound idoc adapter is not valid using idoc.jar. |
| Symptom:IDoc delivered by ALE inbound adapter is not valid. Here is the outline of the idoc event received by CI endpoint. |
| Resolution: This problem is now fixed. |
|
| 42 | CR103569 | | CI: Response BO for RFC should be rfc.Response. |
| Symptom:currently adapter generating response bo name as rfc.response instead of rfc.Response . |
| Resolution: This problem is now fixed. |
|
| 43 | CR103571 | | CI: migration:formatted bo name for /CWLD/OUTBOUND_REQUEST_MQ generated differe |
| Symptom:The formatted bo name for RFC /CWLD/OUTBOUND_REQUEST_MQ generated differently compared to existing CI SAP connector. |
| Resolution: This problem is now fixed. |
|
| 44 | CR103576 | | CI : Not able to generate Schemas for IDOCs with unreleased segments in SAP. |
Symptom: Not able to generate Schemas for IDOCs with unreleased segments in SAP adapter.
Example for Unrelated segment IDOCs are MATMAS02, /CWM/DELVRY03 and so on.
For CI, SAP adapter should use blank for idoc release version always. This will fetch latest version of the idoc. |
| Resolution: This problem is now fixed. |
|
| 45 | CR103577 | | CI : IDoc schemas are not generated with null namespace |
| Symptom:As per CI requirement, the IDoc schemas should be always generated with null namespace but adapter is setting default namespace for all IDoc schemas . |
| Resolution: This problem is now fixed. |
|
| 46 | CR103582 | | CI: MATMAS03 E1MARAM segment has less elements compared to we60 |
| Symptom: The schema generated by the adapter for MATMAS043ver-40A for segment E1MARAM has 99 segment compared to 126 segment when generated from SAP GUI we60 and also from old CI connector. |
| Resolution: This problem is now fixed. |
|
| 47 | CR103583 | | CI : control record fields DIRECT and IDOCTYP differences. |
Symptom: As per we60 and CI requirement these fields should be as explained as -
As per we60 control record DIRECT field has a enum value of 1-outbound and 2-inbound but with 6.1 it is a string with maxlength.
There is another attribute called IDOCTYP which has a maxlength of 30 in 6.1 but no maxlength value in 5.1 and attribute value fixed is set to select IDOCTYPE. |
| Resolution: This problem is now fixed. |
|
| 48 | CR103584 | | CI : The segment E1EDL39 should have maxOccurs value to 9 instead of unbounded. |
| Symptom: There is a segment called E1EDL39 under E1EDL37 which has a maxoccurs of 9 when generated with existing CI connector and we60 but schema generated by sap adapter has unbounded value. |
| Resolution: This problem is now fixed. |
|
| 49 | CR103587 | | NPE exception for second project deployed with different IDoc. |
| Symptom: NPE exception for second project deployed with different IDoc. |
| Resolution: This problem is now fixed. |
|
| 50 | 6036(RTC) | | Not able to create the project module for AEP inbound. |
| Symptom:Not able to create the Project Module for AEP Inbound in WPS and EMD throws the error msg "The discovery service for resource adapter 'IBM WebSphere Adapter for SAP Software with transaction support' has an error. |
| Resolution: This problem is now fixed. |
|
| Upgrade notes |
| To upgrade to this Interim fix version on WebSphere Process Server, do the following : |
| 1. Ensure that you have followed the "Installation Instructions" section in the download link before proceeding. |
| 2. If you need to use the test fix for EMD, delete the connector project in WebSphere Integration Developer, import the new RAR file, and apply the enterprise information system (EIS) specific dependency files. |
| . a. Open the Java build path for the SCA module and remove the Connector project that is selected on Projects tab. |
| . b. Open the dependency editor and remove the connector project. |
| . c. Delete the connector project from the workspace |
| . d. Import the new RAR file. Add any dependency files from EIS specific application-specific information as needed. |
| . e. Open the Java build path for the SCA module and select the Connector project that is selected on the Projects tab. |
| . f. Open the dependency editor and add the connector project if it is not already present and select Deploy with Module. |
| 3. If you need to update deployed applications on WebSphere Process Server, do the following : |
| . a. Select Update for the corresponding application on the WebSphere Process Server administrative console. |
| . b. Select Single Module with a relative path as name of the RAR file - CWYAP_SAPAdapter.rar, CWYAP_SAPAdapter_Tx.rar. |
| . c. Click Browse on the local file system to select the updated RAR file that has the changes. |
| . d. Select the default values in the remaining steps and click Finish. This will ensure that existing configurations, for example, are not changed and that only JAR files will be updated. |
| . e. If there is a change in CWYAP_SAPAdapterExt.jar, the jar should placed in the 'lib' directory of WebSphere Process Server and the server has to restarted. |
| To upgrade to this Interim fix version on Websphere Message Broker (WMB) runtime, do the following : |
| 1. Unzip the Package_WMB.zip to your temp local directory , it would create following directory "AdapterPackage". |
| 2. Stop all your Brokers that are using this install. |
| 3. Go to "AdapterPackage" directory it should contain the files CWYAP_SAPAdapter.jar, CWYBS_AdapterFoundation.jar and CWYAP_SAPAdapterExt.jar |
| . a. Backup the existing file CWYAP_SAPAdapter.jar, CWYBS_AdapterFoundation.jar and CWYAP_SAPAdapterExt.jar files. |
| . b. Copy the above files to MQSI_INSTALL_PATH\adapters\prereqs\jar directory , where MQSI_INSTALL_PATH is WMB runtime install path. (eg. C:\Program Files\IBM\MQSI\7.0\adapters\prereqs\jars). |
| 4. Restart your Brokers. |
| To upgrade to this Interim fix version on Websphere Message Broker Toolkit (WMBT), do the following : |
| 1. Unzip the Package_WMBT.zip to your temp local directory , it will create the directory "AdapterPackage". |
| 2. Stop your WMB Toolkit. |
| . a. Backup the existing CWYAP_SAPAdapter_Tx.rar file. |
| . b. Copy the above CWYAP_SAPAdapter_Tx.rar files to WMBT_INSTALL_PATH\ResourceAdapters\SAP_(version_number)\deploy directory , where WMBT_INSTALL_PATH is WMBT runtime install path. (eg. C:\Program Files\IBM\WMBT70\ResourceAdapters\SAP_7.0.0.0\deploy). |
| 3. Restart WMBT. |