Description:
R/3 Adapter 4.2.0 Patch 17 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 17 is a cumulative patch and it contains all the fixes from Patch 1 to Patch 16.

Defect-Id : 1-2M9U4G
Fixed a defect in adapter where the adapter was crashing for custom RFCs which have .INCLUDE structures within regular structures.

Defect-Id : 1-2OPQWH
Fixed a defect where the Multi-threaded request response service with Cert

Defect-Id : 1-234PAM
Fixed a defect in the adapter Run-time, where the indound adapter was consuming high percent of CPU even on idle state, when it is configured for large number of services, exceeding 100.

Defect-Id : 1-1QMDO0
Fixed a defect in the adapter palette, where the "Test Connection" operation
failed from the Run-Time Inbound Connection Tab.

Defect-Id : 1-1QFSDV
Fixed a defect in the adapter Request-Response Service, when very
small fixed data type values sent out, were corrupted in the SAP system.
Eg, if we send 0.00000080000300, it was getting saved as
8.30000000000000

(3) Defect-Id : 1-1SOUKX
Fixed a defect in adapter Run-time, where Implementation exceptions thrown
back to Outbound adapter sometimes caused short dump in SAP

Defect ID : 1-12LUWT
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"

Defect-Id : 1-1NUHYL
Enhanced the adapter to support X (bounded raw) datatype in SAP R/3 system.

Defect_Id : 1-1NZGMV
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.

Defect_Id : 1-19J464
Fixed a defect in the Design-time adapter where simple import and export parameters of direct ABAP primitive types would not be downloaded.

Defect ID : 1-1ETIOW
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.

Defect ID : 1-1PLCG4
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.

Defect-Id : 1-16YT7R
Fixed a defect in the Outbound adapter where the adapter would exit when it received a message containing data where the number of bytes of the data exceeded the field length.

Defect-Id : 1-1LQLQI
Fixed a memory leak in the run-time adapter on Windows platform for explode mode IDoc publishers and subscribers running on UTF-8 encoded repositories.

Defect-Id : 1-16YT7R
Fixed a defect where the adapter running on UNIX platforms would exit when it received a message containing Japanese data where the number of bytes of the Japanese data exceeded the field length.

Defect-Id : 1-1EWY41
Fixed a defect in the Outbound adapter where the adapter exits abnormally when the adapter processing rate per request is very high.

Defect-Id : 1-1FZ1SL
Fixed a defect in the adapter Subscription service where, if the adapter receives a message containing Japanese data,where the number of bytes of the Japanese data exceeded the field length; then the excess characters doesn't get filtered,it gets added before the next field characters,thereby corrupting the data.

Defect-Id : 1-18G7NJ
Fixed a defect in the adapter Request Response service where multiple (and simultaneous) invocations of a BAPI configured for 'Commit Required' caused the adapter to hang.  This occurred if the corresponding commit/rollback BAPIs were not fired within the 'Commit Expiry' period.

Defect-Id : 1-16YT7R
Fixed a defect in the Outbound adapter on AIX platforms where the connections to the SAP system were intermittently being interrupted and the adapter would throw CPIC errors.

Defect-Id : 1-18G7OD
Fixed a defect in the Outbound adapter on AIX platforms where the adapter may not stop completely when stopped with the command-line stop option or the stopApplicationInstance microagent method of TIBCO Hawk. This was a known issue in the 4.2.0 GA Adapter.

Enhancement Request : 1-120JXJ
(a) Enhanced the adapter subscription service to validate for destinations based on an incoming IDoc Control Record's RCVPRN field. Validation of Destinations is already supported for the publication service.
The list of Inbound valid destinations can be specified in the adapter properties file as :
adr3.Inbound.ValidDestinations=MYDEST

Multiple destinations may be specified as comma-separated values.
Eg., adr3.Inbound.ValidDestinations=MYDEST,MYDEST1,MYDEST2

When this property is specified, those IDocs with RVCPRN values not specified in the list are written to file in a format repayable by the ReadIDocFromFile plugin shipped with the adapter.

(b) Enhanced the file naming convention for idocs 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 : &ltIDOCTYP>_&ltDATETIMESTAMP>_&ltIDOC_COUNT>.idoc
IDOCCOUNT is the count of the idoc inside the adapter instance.
DATETIMESTAMP is approximated to milli-second level.

Eg. If you are sending the MATMAS01 idoc from the SAP system to a invalid destination at 24th August 2:03:05,then idoc will be written to the file MATMAS01_20030824020305350_1.idoc

The Directory to which the idoc file is to be written can be specified in the adapter properties files as :
adr3.idocLogDirectory=d:/tibco/adapter/adr3/4.2/logs
When this property is specified the adapter will log the idoc in the specified directory.

Defect-Id : 1-135PSF
Fixed a defect in the adapter Request-Response service where duplicate session-ids would be returned to the invoking system occasionally when multiple threads simultaneously executed BAPIs with 'commit required' flag turned on.

Defect-Id : 1-12OB5D
Fixed a defect in the adapter Publication service where the adapter would exit abnormally when IDocs with completely empty segments were posted from the SAP system. This happened with UTF-8 encoded projects on UNIX platforms only.

Defect-Id : 1-13RLL0
Provided a shell script adr3_env.sh. This file updates the appropriate environment variables to deploy the run-time adapter on UNIX platforms.
Before using this file, update the following variables in the script :
1. TIBCO_HOME      eg. /usr/tibco
2. TIBCO_TRA_HOME  eg. /usr/tibco/tra/&ltver>
3. TIBCO_DESIGNER_HOME eg. /usr/tibco/designer/&ltver>
4. TIBCO_ADR3_HOME eg. /usr/tibco/adapter/adr3/&ltver>
5. TIBCO_RV_HOME   eg. /usr/tibco/tibrv
6. TIBCO_JAVA_HOME : path to the jre/&ltver> directory
7. TIB_ICU_DATA    : path to the directory containing the ICU conversion file tibicudata.dat

Defect-Id : 1-YALG5
Fixed a defect in the adapter palette where RFC schemas with very specific structures would not be refreshed correctly in the repository upon re-downloading from the SAP R/3 system.

Defect-Id : 1-Z73WR
Fixed a defect in the adapter subscription service where an exception was being thrown if an Idoc segment contained no data at all (ie. node 'FIELDS' is empty).

Defect-Id : 1-TSR5I
Fixed a defect in the adapter subscription service where fields succeeding an explicitly published null field in an IDoc message would be ignored.

Defect-Id : 1-TWLVD
Fixed a defect in the adapter Request-Response service where the commit execution for BAPIs configured for 'commit required'
would sometimes return an 'invalid session id' error at high values of 'maxConnections'.

Defect-Id : 1-ZHNM0
Fixed a defect in the adapter request-response service where a message with an error role was being traced to log if the RFCCLOSURE packet did not contain a value for the optional property 'bTransactional'.

Defect-Id : 1-ZZS2S
Fixed a defect in the adapter design-time where dragging and dropping a publication service would throw a nullpointer exception. This did not hamper configuration though.

Defect-Id : 1-11A19T
Fixed a defect in the adapter run-time where the '-setlocale' command line option was being ignored in favour of 'adr3.locale' parameter in the adapter properties file on Unix platforms. Now, '-setlocale' can be used in the command line to specify the sdk-encoding value. '-setlocale' overrides 'adr3.locale', if specified in the properties file.
eg: adr3 -system:repourl &ltrepourl> -system:configurl &ltconfigurl> -setlocale ibm-943.

Defect-Id : 1-Y790N
Removed a restriction in the run-time adapter that allowed only a maximum of 8 connections per connection pool. Each connection pool can now hold a maximum of 99 connections.

Service Request : 1-SUXMD
Enhanced the Outbound adapter for standardizing IDoc/RFC/BAPI Outbound message formats across ISO8859-1 and UTF8 encodings with respect to handling blank fields & fields with trailing blanks.
The behavior can now be controlled by setting the parameter adr3.preserveFieldBlanks from the adapter properties file.
adr3.preserveFieldBlanks=OFF (default)
strips padding blanks from individual IDoc/BAPI/RFC fields and filters out fields that are entirely blank.

adr3.preserveFieldBlanks=ON
preserves padding blanks in individual IDoc/BAPI/RFC fields and maintains fields containing only blanks as is.

Defect-Id : 1-4CX89
Added design-time and run-time support for namespaces for BAPIs/RFCs.
The "/" in BAPI/RFC name in a namespace will be replaced with "__SLASH__" at design-time and saved to project with this name.
At run-time, the adapter replaces the "__SLASH__" with the "/" character in all its interactions with the SAP R/3 system.

eg. /tibco/MY_CUSTOM_RFC will be visible in the TIBCO environment as __SLASH__tibco__SLASH__MY_CUSTOM_RFC.
The above applies to parameters referred to by the BAPI/RFC as well.

To download the list of BAPIs/RFCs with namespaces, either enter the entire name of the RFC or give a partial filter in the RFC Filter. Make sure that the RFC Group Filter is blank.

eg.
1) To download a list of all BAPIs/RFCs with namespaces give RFC Filter as "/*" and leave the RFC Group Filter blank.
2) To download a RFC with name space "SAPTRX" just give RFC Filter as "/SAPTRX/*" and leave the RFC Group Filter blank.

Note: The default RFC Filter expression "*' would not download BAPI/RFC's with namespaces.

Defect-Id: 1-NO80X
Provided support for traditional Chinese on non-Win32 platforms as well. The adapter now uses the underlying TIBCO Adapter SDK conversion routines on non-Win32 platforms. SAP blended code-pages are not supported on non-Win32 platforms. Refer accompanying document on SAP language support in TIBCO Adapter for R/3 for details.

Defect-Id: 1-9QH0Q
Fixed a defect where the value of the field SPRAS_ISO would get appended to the field MAKTX in the segment E1MAKTM for a MATMAS01 idoc published in explode mode.

Defect-Id: 1-S4CMV
Fixed a defect where the adapter aborted when multiple threads raised short-dumps in the SAP R/3 system simultaneously at high messaging rates for Inbound one way RFC invocations.

Defect-Id:1-PWYX4, 1-JOFUK
Fixed a defect where the Outbound RFC Invocation timeout was not configurable and was always set to 5 minutes. The timeout can now be specified from the adapter properties file as : adr3.&ltrfc name>.invocationTimeout. The timeout value should be in milliseconds.
Eg., to set the timeout for the Outbound Request-Response invocation adapter service to 10 minutes, make the following entry in the properties file :
adr3.RFC_CUSTOMER_GET.invocationTimeout=600000

Defect-Id: 1-GZ5MS
Fixed an issue of adapter adding weird characters for idocs having '_' in their name.

Defect-Id: 1-L3BNK
Fixed an issue in 3.x -> 4.x migration where advisories' folders were not getting created automatically after upgrading to 4.x.

Service Request : 1-HWRYL
Fixed a design-time issue where the class reference for IDoc Publishers did not automatically update from '-4x' to '-4x-SEQUENCE' when the publish mode was changed from 'explode' to 'explodebatch'.

Enhanced the explode-batch publishmode. The adapter now publishes exploded idocs in a batch with the '-4x-SEQUENCE' as a class container rather than a sequence container for subscription in TIBCO BusinessWorks.


Defect-Id: 1-F0H7N
Fixed a memory leak in the run-time adapter for explode mode IDoc publishers and subscribers running on UTF-8 encoded repositories.


Service Request  : 1-EP8S1
Fixed an issue in the subscriber where IDoc posts subsequent to an IDoc post that raises an exception in SAP were not processed.

Service Requests : 1-CVH37 and 1-CKKD1
Fixed an issue in the run-time adapter where an 'Invalid connection' exception was being thrown for request-response RFC calls even subsequent to the SAP system coming up after going down.
Fixed an issue in the run-time adapter where the adapter crashed while processing data-caching requests in a multithreaded mode.

Defect Id : 1-CTSUH
Fixed an issue with R/3 Palette when a R/3 Adapter Instance Repository migrated from R/3 Adapter version 3.0 (or lesser) to 3.2 was opened with the 4.2.0 R/3 Palette, the palette failed to load the client connection information.

Defect Id : 1-BQG9A
Fixed an issue when "R3Connections" Folder is moved the palette would fail to connect to the DTA

Defect Id : 1-ASR58
Fixed an issue in the design-time adapter to provide support for downloading Schemas from SAP CRM 3.0 and SAP WAS 6.1.0 systems.

This hot fix can be downloaded from the TIBCO Product Support ftp server, ftp://support-ftp.tibco.com/, using your username and password for the TIBCO Support Web.  Once logged on you can find the hot fix under:

available_downloads/ActiveEnterprise/Adapters/SAP-R3/4.2.0/patch17

Please contact TIBCO Support if you have any problems finding or downloading this patch