Using the BusinessConnect EDI Protocol powered by the Instream X12 Protocol, a validation error occurs when generating an acknowledgement.

Using the BusinessConnect EDI Protocol powered by the Instream X12 Protocol, a validation error occurs when generating an acknowledgement.

book

Article ID: KB0089480

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect EDI Protocol Powered by Instream -
Not Applicable -

Description

Resolution:
Description:
============
When the acknowledgements are enabled for a Trading Partner (TP) and an inbound file is processed, BC does not generate the output file and fails with the error message "Notification did not reach trading partner.XMLDocument could not be sent to the Trading Partner due to following reason:Errors were encountered during validation". The same file can be processed if Acknowledgements are set to None at the TP level.

Environment:
==========
Applicable to all the environments


Cause:
=====
The cause of the problem is specifying the same delimiter value for both ISA11 (Repeating separator in Interchange Header) and the Data Element Separator in the Delimiters tab. This is not allowed according to the X-12 specification.

Resolution:
=========.
Make sure that different delimiter values for ISA11 (Repeating separator in Interchange Header) and Data Element Separator are specified in Delimiters tab. This is the primary causefor this issue.

Also, make sure that the guidelins have the DSR mark set for the ISA, GS and ST segments.  This can be verified by opening the guideline with the EDISIM tool.

Issue/Introduction

Using the BusinessConnect EDI Protocol powered by the Instream X12 Protocol, a validation error occurs when generating an acknowledgement.