iWay Software has discontinued support for the original SAP adapter, which was based on JVM 1.42 and required SAP JCo 2.0x (discontinued by SAP).

iWay Software will discontinue distribution of the mySAP ERP adapter (using SAP JCo 2.x) with the next major release of iWay Service Manager. This adapter is based on JVM 1.5 and requires SAP JCo 2.1x. For more information on end of life for JCo 2.1, see SAP Note 549268. iWay Software will provide support until end of life of JCo 2.1, but no new features. It is recommended that all customers migrate to the mySAP ERP adapter (using SAP JCo 3.x). SAP JCo 3.x can support Java 1.5, 1.6, and 1.7. In addition, the mySAP ERP adapter (using SAP JCo 3.x) is the current track for all new feature requests and development.

The iWay Application Adapter for mySAP ERP (SAP JCo 3.x) User’s Guide contains complete documentation on the features and available support of the adapter. In iSM Version 6.1.7, the following features has been added:

• Client mode (inbound to SAP).
• Support for Explicit Commit RFC/BAPI. If you need to issue an SAP database commit at the end of your function call, then select this option. An asynchronous call to the database is issued.
• Support for Commit with Wait. If you need absolute confirmation of the commit function, then select this option. A synchronous call to the database for commit is issued. Note that performance can be impacted when using this option.
• Server mode (outbound from SAP)
• Support is provided for automatic checking of the IDoc release type through the SAP Partner Profile. If you are sending to multiple partners with different IDoc releases, then select this option to automatically synchronize the metadata for the IDoc with the SAP release version in the SAP Partner Profile. This option allows multiple release versions per target, where setting the user input option is a global parameter for the target.
• Support is provided for automatically sending STATUS IDoc messages after an IDoc is received. When an IDoc is received by the adapter, after successful processing, a STATUS IDoc is sent back to SAP noting the successful receipt. A user in the SAP transaction for monitoring IDocs can see the complete sending and receipt trail for the IDoc.
• IDoc (Flat) encoding. When receiving native non-XML IDocs from SAP, you may require to encode the IDocs into a file format compatible for further processing by other applications. Select an encoding (such as UTF-8) for the native IDoc text files to be written.

iWay Application Adapter for PeopleSoft does not support custom methods. The adapter only supports a subset of the delivered methods by the component interface APIs. Supported methods include Create, Save, Get, and Find. The Cancel method is not supported.

This is the third and final release of SWIFT 2012. All components, documentation, and sample channels have been updated. Note that many documents did not have any updates in SWIFT 2012, and remain unchanged since SWIFT 2011. For additional information and available Ebix file downloads, go to http://techsupport.ibi.com.

Due to component requirements, SWIFT will no longer be supported on any releases prior to iSM Version 6.1.6. New versions of SWIFT will only be supported in the current release of iSM.

Due to component requirements, the following SWIFT adapter components are deprecated:

• com.ibi.preparsers.SwiftPreParser
• com.ibi.preemit.SwiftPreEmitter
• com.ibi.wsift.SWIFTInAdapter
• com.ibi.swift.SWIFTServiceAdapter
• com.ibi.agents.XDSWIFTTransformAgent
• ADR.zip

If you are still running any of these SWIFT adapter components that are listed, they will function in iSM Version 6.1.7, but are unsupported. However, they will be removed in the next version of iSM.

A minor correction has been made to 4010 271 Loop 2110C - DTP corrected date mask.

HL04 check for HIPAA documents does not apply to X12, specifically for 856, and has been disabled by the addition of the following parameter:

check4Zero="false"

To re-enable the check, remove this parameter from the rules file.

• Using Dictionary Builder to modify HIPAA or SWIFT metadata is not supported in the current release.
• The following error is caused by a conflict of classes having the same name in the iwhl7.jar and iwedi.jar files:

  com.ibi.edaqm.XDEDIError.setData_element_syntax_code(I)V - No such method error.

  If you receive this error, rename or remove the iwhl7.jar file from the \lib directory.

• EDIFACT Version UN911 has not been updated for this release.
• Zone decimal transformation is not supported in this release. As a workaround, you can hard code the field in the transformation to convert zone decimals to real or numeric decimals. You can also add a custom Java external subroutine.
• Blank spaces (hex 20) as element or subelement separators generate Java errors. X12 data that is transformed to XML and then transformed back to X12 may contain tags in one sequence of the input document and in a different sequence in the output document. For example, the order of REF segments is not guaranteed.
• Processing large documents may result in an out of memory Java error. The standard splitter reads multiple interchanges from a single file, and reads multiple single documents from an interchange. A standard solution to split a single large document into smaller pieces for processing is currently not supported. Several workarounds exist depending on the document and the data being passed.
• iTM integration will be included in a future release.
• Errors in parsing data return an input document for error routing in Base 64 format rather than CDATA format.
• Each custom transform project must be in its own directory, folder, and project. iWay Transformer does not allow you to save more than one custom transform project to a directory.
• Outbound channels with embedded process flows that contain transforms may not run rules validation as expected. There are two workarounds available:
  1. Split your channel into two channels, where one channel contains the transform and the other channel contains the preemitter.
  2. Modify the ebix for this transform by changing the x12-package.xml file to run outbound validation.

  If you decide to use the second workaround, it is recommended that you open a support case with customer support unless you are extremely familiar with ebix structures.

• The behavior of the XDXMLSplitterIterator will change in a future release. This component is used within the SDQ to create and transform multiple output documents. The current behavior now drops the iterated portion to the bottom of the output document. In a future release, the iterated portion will remain in the same location in the outbound document. The only repair required (to the SDQ splitters) will be to modify and rebuild the transforms that run after the iterator in the process flow and to rebuild the channel. Further detailed instructions for this repair will be available in a future release.
• Tidy printing (pretty printing) may cause false validation errors on outbound documents. It is recommended that you do not reformat the XML with any non-iWay software before processing through preemitters.
• Metadata is cached for performance in channels. After adding or removing an ebix that is associated with a channel, you must restart the server to clear the old information from the cache.
• Standard document processing always creates an acknowledgment document (997 or 999 for HIPAA, 997 for X12, and APERAK for EDIFACT). Currently there is no standard methodology to create acknowledgment documents by trading partner or to disable all acknowledgments. This will be addressed in a future release.
• HIPAA 837 documents contain a unique validation issue. In sequence 2010AA, there are two REF segments with relational validation requirements. Currently, the adapters only validate the maximum number of REF segments (4) and that the qualifiers used are valid. A rule to validate the relationship test will be included in a future release.
• X12 document Versions 4030 or higher with repeating elements or repeating composite elements may not parse correctly. This issue does not apply to the iWay Integration Solution for HIPAA. HIPAA documents are not affected. This issue will be addressed in a future release.
• SWIFT pipelining is available, but unsupported.
• Viewing older SWIFT ebix in iIT and attempting to validate them may display bad index messages. This is caused by multiple documents in the ebix with the same root name - for example MT102 and MT102STP. This issue exists in all e-commerce products. SWIFT and HIPAA documents are read only in iIT, and this issue should not impact your ability to view these documents. The correction is to move the non core (and/or STP) documents to their own ebix. This may happen in a future release if iIT is allowed to edit these documents.

This section lists ANSI X12, VICS, UCS, and HIPAA documents that are supported in the latest release.

This section lists EDIFACT documents that are supported in the latest release.

This section lists SWIFT documents that are supported in the latest release.

Note: For updated Ebix information, refer to http://techsupport.ibi.com.

This section lists the supported separators and delimiters for the preparsers and preemitters.