Description:
R/3 Adapter 4.2.0 Patch 14 is released for all platforms supported by R/3 Adapter 4.2.0. To know the platforms supported by R/3 Adapter 4.2.0 please see the readme file. Patch 14 is a cumulative patch and it contains all the fixes from Patch 1 to Patch 13.

(1) Service Request : 1-12LVQ5

Enhanced the adapter multi-lingual support on Windows platforms for more efficient conversions between Unicode and multibyte character sets, leading to marked improvement in performance. The adapter now supports TIBCO Adapter SDK based Unicode conversion routines on Windows. This mechanism replaces the earlier less-efficient platform-based conversion routines.
All adapters running on Windows with UTF-8 encoded projects and processing characters belonging to non-ISO8859-1 character sets are required to perform the following migration steps :
(i) Replace the existing "adr3.locale" or "-setlocale" parameter with the equivalent Adapter SDK-encoding.
For eg., if the adapter is processing ShiftJIS characters, replace the existing locale entry "Japanese_Japan.932" to "ibm-943".
Similarly, replace "Chinese_China.40936" with "ibm-1386" and "Chinese_Taiwan.950" with "ibm-1370".
If you are using a locale other than mentioned above, please contact TIBCO Support for obtaining equivalent Adapter SDK-encoding values.
(ii) Set the environment variable TIB_ICU_DATA to point to the directory containing the file tibicudata.dat. This file is located under the directory TIBCO_HOME/tra/1.0/bin.
Eg: TIB_ICU_DATA=TIBCO_HOME/tra/1.0/bin.
SAP blended code-page "eurojapan" is now supported on all platforms. To use this codepage, copy the eurojapan.cnv file from the adapter bin directory to the directory as specified in step (ii) above.
Specify the locale as "adr3.locale=eurojapan" or "-setlocale eurojapan"


(2) Service Request : 1-1ICRWM
Enhanced the adapter to support X (bounded raw) datatype in SAP R/3 system.

(3) Service Request : 1-1MUTS1
Fixed a defect in the Oneway Request-Response service where the adapter would exit while writing the request data to file in situations where the SAP R/3 application server raised an exception and the data being written to file contained null table fields.
Also, enhanced the file naming convention for RFCs that are written to file and provided a parameter to specify the directory to which the files are logged.
Filenames will be of the format : &ltRFCNAME>_&ltDATETIMESTAMP>_&ltRFCCOUNT>.rfc
RFCCOUNT is the count of the particular RFC invocation being written to file. DATETIMESTAMP is approximated to milli-second level.
Eg. If you are invoking an RFC, Z_TEST_RFC on the adapter, and the 20th invocation fails at 23rd April 2:03:05 2004, then the RFC will be written to the file Z_TEST_RFC_20040423020305350_1.rfc
The Directory to which the RFC file is to be written can be specified in the adapter properties files as : adr3.rfcLogDirectory=d:/tibco/adapter/adr3/4.2/rfc_logs
When this property is specified the adapter will log the rfc in the specified directory.

(4) Service Request : 1-17B2JL
Fixed a defect in the Design-time adapter where simple import and export parameters of direct ABAP primitive types would not be downloaded.

(5) Service Request : 1-1EN50X
Enhanced the adapter palette to download schema information to any custom folder specified.
For Eg.In the Configuration tab of Adapter Services for an Instance, if you specify "custom" in the text field provided for "Custom Folder" and download MATMAS01 IDoc,then MATMAS01 IDoc Schema will be saved under /tibco/public/class/ae/custom/basic/IDocs.

(6) Service Request : 1-1NNDY3
Fixed a defect in the adapter palette where IDoc schema could not be downloaded in legacy 3.x format from 4.7 version of SAP R/3 onwards.

"Please contact TIBCO Support to obtain the Patch"