|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Inovis TLE 6.0 Service Pack 3 - Review
Inovis has Released Service Pack 3 for TLE 6.0. After installing
the update, there are a few things I found customers should be aware
of. First of all, although it shouldn't make any difference, I'm
running on Windows 2000 and Oracle 9.2.
____________________________________________
The first thing that I got hit by was a change Inovis made regarding
how it deals with the character sent in ISA16 (Subelement Separator).
In Previous Versions, you could have almost anything you wanted for
a Subelement Separator. In the more than 15 Years that I've been
doing EDI, I have never seen any cases that used the Subelement
separator. Inovis however determined that in allowing the same
character to be defined as both an Element separator and a
Subelement separator was a bug. They fixed it and by doing that,
they shut down all EDI with trading partners that sent EDI with the
same character for both. I have a trading partner that sends me EDI
using Version 002002 and they used the "*" character for both the
Element separator and in ISA16. I have to manually edit the EDI to
change ISA16 to another character ( I'm changing it to "\" ) in
order to get the EDI to translate. Support is saying that they
logged a defect for this because in version 002002, it was allowed
to have the same character for both. In either case, I suggest you
look at the EDI you're receiving and work on getting your trading
partners to change their ISA16 if the above condition exists.
The second thing I ran into was that my Application to Application
maps wouldn't work anymore. This turned out to be two issues.
First of all, even though the translation is APP2APP, you still have
to define an Interchange for the trading partners event to link to.
The interchange I had setup Only setup the Delimiter Characters. I
get a flat file off of the Internet in a comma delimited (.CSV
excel ) format. I had defined the Segment delimiter as 0D (CR), the
element delimiter as 2C (comma) and the subelement separator as 2C
(comma). The other values I used in addition to the Trading partner
Identifier and the Internal Identifier was "U" for Standards
and "00200" for version although don't ask me why I choose those
values. I had to enter something.
In trying to translate the APP2APP, I got the same error as the
ISA16 issue. Changing the Sub-element delimiter to 5C "\" changed
the error to a CMDS.801 "Incorrect Envelope".
Working with support, I had to delete the event that was used for
the Application to Application translation and re-create it using
the following information:
____________________________________________
When you setup an ApptoApp event, you are setting up an Outbound
event. This means that in the Ops Center, your Application
represents the source file and the Event represents the target. If
the Application source data is delimited, then in the Application
you need to check the Delimited check box and specify the
delimiters/separators in order for the translator to be able to read
the input data. If the target is delimited then in the Event, the
only difference is with the Standard. It should be "PROPD", rather
than "PROP". Otherwise, as usual with ApptoApp, the Version
is "Proprietary", Committee is "P", Envelope Name is "Any2Any" and
FG Type is PR. I usually use "A2A" for the Doc ID...
In the Application layout Document Constant Cross Reference, the
Document Name would be "Proprietary" (Same as the Version in the
Event setup).
Note: In the Mapping Workbench, make sure that you check the
Delimited check box, where appropriate, for the source and/or
target, when defining the ApptoApp
____________________________________________
After doing this, the app2app did translate. However I didn't get
the record tags that were defined in the mapping workbench. In the
Mapping Workbench, I view the Target Application and then choose
Record Properties. Here I have a Tag defined for each record. I
didn't get that value in the output application file created by the
map.
For Now, I added a field to each record called "RECORD_TAG" and did
a Fill for each record to get the tag.
After doing that I got the record tags in my output and the
translation was successful.
____________________________________________
Other things I noticed after installing SP3, each working directory
created now contains a sub folder called tmp. Not a big issue and I
do not see any files left in the folder. They get cleaned up ok.
Also, their are some new utilities included. In windows, the
clean_tlrt.exe now supports the same options as UNIX
clean_tlrt.ksh. A new utility xml2txt.exe will convert a stream of
XML documents to an XPath-like format that can more readily be
processed by scripts.
For anyone still running TLE 5.1 or 5.2 their is a Mapping Workbench
Migration Tool included that will migrate all of your events from
the version 5.1 or 5.2 Mapping Workbench into Mapping Workbench 6.0.
When I went to 6.0, I had to manually create and import all of my
5.1 events into 6.0. It would of been nice to have this when I went
to 6.0.
Also note that Inovis Support Number is now 1-877-446-6847.
Roy Nelson
262-534-5141
|
|
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
