XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Alan LapworthSubject: EDI Error
Author: Alan Lapworth
Date: 28 Feb 2007 09:00 AM
Originally Posted: 28 Feb 2007 09:01 AM
Hi,

I have just downloaded version 2007 to see if an earlier problem had been rectified in this release. I need to convert an edifacts IFCSUM s93a file to XML. The file will convert using 2006 enterprise but fails with the error :

java.io.IOException: $2..04B Segment UNB, Element 0007: Cannot decode value "ZZ" (file:///c:/ftp_transfer/ee/search/comcheck.DAT:2,21) {close}

When I use 2007.

The segment in question contains the following:

UNB+UNOA:2+ITBAR005:ZZ+GBANC+060804:1016+446'

I have had a look at the .properties file in each version and they appear to be the same.

any ideas?

Many thanks

Al

Postnext
Tony LavinioSubject: EDI Error
Author: Tony Lavinio
Date: 28 Feb 2007 03:42 PM
Are you sure that you have an EDIFACT.properties file in the same
directory as the EDIFACT.jar file for 2007 that contains a line like
this:

S93A.0007.ZZ=Mutually defined

or possibly this?

*.0007.ZZ=Mutually defined

If you do and you want us to check further, could you send a copy
of the EDI file and your EDIFACT.properies file to stylus-field-report
(at) progress.com? We'd be happy to take a look.

But S93A is supported under Stylus Studio 2007.

Postnext
Alan LapworthSubject: EDI Error
Author: Alan Lapworth
Date: 01 Mar 2007 04:30 AM
Hi,

Thanks for the reply, but I do not appear to have an edifact.propeties file in either version only EGB-S93A-IFCSUM.properties within the jar file. I'm looking in c:\program files\Stylus Studio 2007 XML Enterprise Suite\bin is this correct?

If so where do I get the EDIFACT.properties file from?

Al

Postnext
Tony LavinioSubject: EDI Error
Author: Tony Lavinio
Date: 01 Mar 2007 09:04 AM
Just make one with a text editor.

"ZZ" is not a valid value for 0007; it should be "ZZZ" according
to the specifications.

However, we allow you to extend the range of codelist values to
add your own. There are several mechanisms, but the easiest is with
the .properties files. There can be one for EDIFACT, one for IATA,
one for EANCOM and one for X12.

Each has the same format:

<version> '.' <element> '.' <value> '=' <description>

<version> can be the actual version, like S93A for EDIFACT or
1997 for EANCOM or 005040 for X12 or 061 for IATA - or just an
asterisk to mean "all versions."

<element> is the element ID. In EDIFACT/EANCOM/IATA, they include
leading zeros, but in the X12 standard they do not. (Not my fault!)

<value> is the valid value you want to add to the list of codelist
values for that element that are allowed.

<description> is what comment should be generated in the outgoing
XML if comments are enabled. You can leave it blank, like this:

S93A.0007.ZZ=

but our recommendation is always to put in a description, like this:

S93A.0007.ZZ=Mutually defined

In your case, the following would work if you received messages in
all sorts of versions, but using ZZ instead of ZZZ:

*.0007.ZZ=Mutually defined

Our recommendation also is to be as specific as possible, including
the version wherever known.

These .properties files can contain any number of codelist extensions
you require.

Postnext
Alan LapworthSubject: EDI Error
Author: Alan Lapworth
Date: 01 Mar 2007 09:36 AM
Thanks for the information it has been a great help, I now have the files loading correctly - with the help of an additional 2 entries.

Is this procedure documented anywhere?

Once again thank you for the solution.

Al

Postnext
Tony LavinioSubject: EDI Error
Author: Tony Lavinio
Date: 01 Mar 2007 09:52 AM
The *.properties section was inadvertently left out of the documentation;
a problem that will be corrected shortly. We've been posting on SSDN as
we've come across questions like yours - but you got the best and most
complete answer so far, because I was in a good mood this morning. :)

Postnext
Alan LapworthSubject: EDI Error
Author: Alan Lapworth
Date: 01 Mar 2007 09:58 AM
Not - for long :)

We have a license key for SS 2006 Enterprise and a maintenance agreement, who do i need to contact to upgrade the key to 2007 ?

Al

Postnext
Tony LavinioSubject: EDI Error
Author: Tony Lavinio
Date: 02 Mar 2007 09:25 AM
Email stylusstudio (at) stylusstudio.com and include your
contact information and license key. They'll help you out.

Postnext
Alan LapworthSubject: EDI Error
Author: Alan Lapworth
Date: 02 Mar 2007 09:29 AM
Once again many thanks for your help

Al

Posttop
Alan LapworthSubject: EDI Error
Author: Alan Lapworth
Date: 02 Mar 2007 10:14 AM
Once again many thanks for your help

Al

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.