TIBCO ActiveMatrix BusinessWorks(TM) Plug-in for SAP Solutions 8.2.2 Hotfix 2 is released for all supported platforms. This hotfix is cumulative of prior hot fixes for this version. Listed below is a summary of updates included in Hotfix 2. Please refer to the attached Readme for additional details on these and other cumulative fixes included in this Hotfix.

================================================================================
Closed Issues in 8.2.2_HF-002 (This Release)

SAPB-1896

For the IDoc Reader, IDoc Renderer, and Post IDoc to SAP activities, IDoc
string index out of range error occurred when an IDoc segment contained no data,
SDATA portion of IDoc segment is empty.

This issue is fixed.


SAPB-1895

For the IDoc Reader activity, schema mismatch error occurred if the root schema
was mapped as ProcessInput.

This issue is fixed.


SAPB-1885

The RFC/BAPI Listener activity received time out exception when receiving
multiple concurrent RFC requests from SAP server.

This issue is fixed.


SAPB-1881

The RFC/BAPI Listener activity does not support tRFC and qRFC invocations.

Note:

To address this fix, changes have been to both design-time and runtime. Before
using these changes, please review below information.

1) The below configuration properties have been added to the General tab of the
RFC/BAPI Listener activity.

  Invocation protocol - drop down containing values request/reply, tRFC, and
  qRFC. The default is request/reply, including at runtime.
   
  TID Manager Shared Resource Reference - reference to the TID Manager Shared
  Resource when property Invocation Protocol is tRFC or qRFC.
   
  Acknowledgement Mode - drop down containing values auto and client when
  property Invocation Protocol is tRFC or qRFC. The default is auto, including
  at runtime.  When configuring this property as Auto, the activity would
  automatically acknowledge the transaction in SAP following successful send
  of output.  When configuring this property as Client, the activity would not
  automatically acknowledge the transaction in SAP and would wait for
  confirmation from the Confirm activity.
   
   Important:
   
   The Acknowledgement Mode property set to value Client is only used when the
   TID Manager Shared Resource is configured as Database. If the TID Manager
   Shared Resource is configured as None then the acknowledgement mode would
   always default to Auto.
   
2) The Advanced tab of the RFC/BAPI Listener activity has a configuration
 property named Request Timeout(ms). The configuration property is also used
 for the Confirmation Timeout(ms) which is only shown when acknowledgement mode
 in the General tab is tRFC or qRFC. The same configuration property is used
 but only difference is the corresponding label.
 
   Important:
   
   When configuring the Confirmation Timeout(ms) in the case of tRFC or qRFC,
   define value in ms which would be large enough to allow for the subsequent
   activities prior to the Confirm activity to complete.  If the value is not
   sufficient then timeout would occur and the transaction would rollback.
   
3) When a fault is encountered prior to the Confirm activity, timeout would
occur in the RFC/BAPI Listener activity which would rollback the transaction.

4) If transactions are pending in the RFC/BAPI Listener activity then those
transactions need to be completed prior to the stopping of the application.

This issue is fixed.


SAPB-1879

The Reply from RFC/BAPI in SAP activity failed to notify the RFC/BAPI Listener
activity with the updated status.

Note:

When the RFC/BAPI Listener activity times out, a new DEBUG message with id
TIBCO-BW-PALETTE-SAP-201009 has been added to correlate with the Reply from
RFC/BAPI in SAP activity. The CPIC Conversation ID is the same value as on the
output of the RFC/BAPI Listener activity. An example of the DEBUG message
is provided below.

22:13:00.640 DEBUG [pool-7-thread-1-ReplyInvalidCustomer] com.tibco.bw.palette.sap.
runtime.activities.Respond2RequestActivity - TIBCO-BW-PALETTE-SAP-201009: Reply to
RFC/BAPI Listener Activity: ReceiveRequestforBAPI_XBP_EVENT_RAISE, Job ID: bw0a100,
 CPIC Conversation ID: 56761654

This issue is fixed.


SAPB-1876

When sending Korean characters in an IDoc segment to a non-Unicode SAP system,
fields in SDATA following field containing Korean characters would have leading
spaces.

Notes:

As part of this hotfix, following restrictions would apply when sending
an IDoc to a non-Unicode SAP system where SDATA contains double-byte characters
such as Korean characters, etc.

1) When sending an IDoc containing double-byte characters, please add below Java
property with value of true.

  com.tibco.bw.palette.sap.nonunicode.doublebyte

2) If a field in SDATA is of length one and corresponding value contains a double-byte
character then the value would be ignored on the IDoc.

3) If a field in SDATA contains mixed characters (i.e. double-byte and single-byte
characters) then value would be truncated accordingly based on the size of the
field.

This issue is fixed.

SAPB-1870

The Invoke RFC/BAPI in SAP activity was sending the same input data multiple
times to SAP.

This issue is fixed.

================================================================================

Please refer to the instruction of Installation/Uninstallation in Readme file for more information.

This hotfix can be downloaded from TIBCO Support Customer Portal Web UI(https://support.tibco.com). You will need to provide your TIBCO Support Portal credentials. Once logged in you can download the hotfix by selecting the “Downloads” -> “Hotfixes” option under:

/AvailableDownloads/BusinessWorks/Plugins/SAP/8.2.2/hotfix-02

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

TIBCO ActiveMatrix BusinessWorks(TM) Plug-in for SAP Solutions 8.2.2 Hotfix 2 is now available

All Supported Platforms