dbTalk Databases Forums  

OT (ish) - Importing EDIFACT into jBASE

comp.databases.pick comp.databases.pick


Discuss OT (ish) - Importing EDIFACT into jBASE in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Simon Verona
 
Posts: n/a

Default OT (ish) - Importing EDIFACT into jBASE - 04-04-2006 , 02:24 PM






I am having to deal with a data file supplied in "EdiFact" format - which is
a European standardized format for EDI.

The data is actually a static datafile (it's a parts pricing file from a
motor manufacturer) and I know it was generated from a flat data file and
encoded using a tool called Xlate.

I am wondering if anybody knows of tools that I can utilise to convert back
into a useful format (jBase data file preferably, flaf file, XML) using
jBASE running on Windows 200X.

Thanks in advance.

Regards
Simon



--
================================
Simon Verona
Dealer Management Service Ltd
Stewart House
Centurion Business Park
Julian Way
Sheffield
S9 1GD

Tel: 0870 080 2300
Fax: 0870 735 0011



Reply With Quote
  #2  
Old   
panzerboy@gmail.com
 
Posts: n/a

Default Re: OT (ish) - Importing EDIFACT into jBASE - 04-04-2006 , 05:07 PM







Simon Verona wrote:
Quote:
I am having to deal with a data file supplied in "EdiFact" format - which is
a European standardized format for EDI.

The data is actually a static datafile (it's a parts pricing file from a
motor manufacturer) and I know it was generated from a flat data file and
encoded using a tool called Xlate.

I am wondering if anybody knows of tools that I can utilise to convert back
into a useful format (jBase data file preferably, flaf file, XML) using
jBASE running on Windows 200X.

Thanks in advance.

Regards
Simon
...
EDIFACT is a UN sponsored/controlled EDI standard, perhaps Brussels has
created a Euro standard based on some EDIFACT message type?
Cant help you with tools but I've decoded & created a couple of
different EDIFACT message types. That 'message type' is the important
bit. EDIFACT is a set of standards for differing uses. So If you know
your message type you can generally google that & get a specification.
In general EDIFACT is plain ASCII, & each field starts with a 3
character mnemonic and ends with a '.
Subfields are delimeted by + and fields within that by : so you can
see how it is
easy to map this to an Attribute, Value and sub-value level.
eg.

UNA:+.? '
UNB+
UNH+
BGM+
.... RFF, DTM, NAD, MOA, CUR, CNT,CNI
UNT
UNZ

The UNA segment defines the characters used ':+.?"
(?) is used as a release character in case you need to use :+ in your
data
The UNB has stuff like the name of the organisation your sending to
UNH will have the transaction number and the 'Message Type Identifier',
this is the bit you want to search on to find the the specs for what
goes next.
BGM Beginning of Message

UNT number of segements in message
UNZ Number of messages (UNH thu to UNT)

Thus you have one UNA,UNB and UNZ per 'interchange' and one or more UNH
thru UNT per 'message'

Jeremy Thomson



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.