You insist your trading partner conform to the EDI standards. They cannot send the delimeter or terminator characters as part of the data for this very reason. It is common for a supplier to make adjustments to the standards to conform to what their customer sends, especially if the customer is an important one. But there are limits to what can be done and still use a translator.
If this is not possible, have the files from this trading partner arrive in a separate directory. Create a custom program that can open the file and replace the misplaced segment terminators, and then write the file to where SI can pick it up.
If they were sending the segment delimiter, you can kludge that by adding elements to the segment definition.
------------------------------
Howard Parks
------------------------------
Original Message:
Sent: Thu November 28, 2019 12:59 AM
From: Pranjit Biswas
Subject: Handle segment terminator as part of EDI data in some fields - Sterling Map Editor
Hi All,
We have a scenario where we have to ask Sterling map to ignore segment terminator when it is part of some EDI fields itself. Currently we have some partners where they are sending data which has the same character as well as that character itself is the segment delimiter. And hence our map is throwing validation error stating inccorect number of EDI segments as per standards. How do we ignore this and continue processing the translation ?
------------------------------
Pranjit Biswas
------------------------------