-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Damon
Kaufman
Sent: Tuesday, April 05, 2005 9:56 AM
To: RBG7-L Mailing List
Subject: [RBG7-L] - Re: Off topic - XML/EDI
Claudine,
I use Trusted Link as an EDI software, and it gives me the ability to
export
data in an ASCII format with a semi-colon as a delimiter, and line numbers
for the segment sections. Each line number has a definition as a segment
in
the standard, and then each position is a specific piece of data. By
sorting
through each header line (line number 1), then you can search by line
number
and position, and insert data into the database depending on it's position
and line number. You can also export the data in a fixed length field,
then
select the data from a set line position, i.e. line 3, position 10 through
18. All in how you choose to implement the conversion function from ASCII
text to data. Everything I do with EDI uses a transaction table for input,
or output.
I don't do much input into my database from EDI, as most of mine are
outgoing Advance Ship Notifications (856), but I do have an ancient
application that ran under RBase System V. On my schedule to get
implemented
is an input translation of orders over EDI (850), and material schedules
(830). The Remittance Advise (820) was what I was thinking of this
morning.
If I can add anything else, please send me a private email, or if there is
interest on the list, we can keep it going here.
Damon
----- Original Message -----
From: "Claudine Robbins" <[EMAIL PROTECTED]>
To: "RBG7-L Mailing List" <[email protected]>
Sent: Tuesday, April 05, 2005 09:58
Subject: [RBG7-L] - Re: Off topic - XML/EDI
Damon,
I read on this subject yesterday to the extent that I think I should
avoid
EDI (constantly changing standard, expensive and harder to implement,
door-to-door delivery) and maybe stick to XML (DTD (on demand)
formatting,
international, web-ready, affordable and easy to use tools). The EDI
format
for an invoice (810) is pretty straight forward but I've read that XML
may
even be easier to use. Now, please tell me more about stripping data to
a
csv...
Claudine
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Damon
Kaufman
Sent: Tuesday, April 05, 2005 6:34 AM
To: RBG7-L Mailing List
Subject: [RBG7-L] - Re: Off topic - XML/EDI
Claudine,
Are you using an EDI format to input the invoices? A number are using
an
ANSI X12 standard, in an 820 ( I think) format. If it's a standard
such
as
that, you can strip the data out to a delimited text file, then load
it
into
the database seramlessly.
Damon
Damon D. Kaufman
President
Stalder Spring Works, Inc
ISO-9001:2000 Certified
2345 S. Yellow Springs St.
Springfield, Ohio 45506
Voice 937,322,6120
Fax 937,322,2126
Primary email: [EMAIL PROTECTED]
Alternate email: [EMAIL PROTECTED]
----- Original Message -----
From: "Claudine Robbins" <[EMAIL PROTECTED]>
To: "RBG7-L Mailing List" <[email protected]>
Sent: Monday, April 04, 2005 1:36 PM
Subject: [RBG7-L] - Off topic - XML/EDI
Hi everyone,
I'm investigating the new XML/EDI combination to setup electronic
transfer of invoices into RBase, preferably through an R:Web setup.
Does anyone have any hints or recommendations for me?
TIA,
Claudine :)
