Jim,
> > ... encoded in the IG so that it can be processed by the translator.
>
> It sounds like you are talking about IGs in a computer format.
Yes, IMPDEF, the international standard EDI message for IGs. At the
risk of sounding commercial you can download a copy of our IG development
tool that generates IGs in IMPDEF from out Website:
http://www.asti-ebusiness.com
It is multi-platform, written in Java, and is available in Open Source,
The Windows binary download is only 8MByte, with 4010. You can order
the Open Source with other standards for basically the cost of the
distribution on CD.
> Computer processable IGs would be very helpful in this real world situation.
We have all the federal government IGs available in IMPDEF format, and a
converter to pick them up from the format the government seems to currently use.
> Unfortunately, IGs in computer processable format are basically non-existent
> in most EDI shops. Obviously, they're a good idea but so far no standard
> has been widely adopted.
Is that because the people at the EDI shops won't go and get them, don't
understand them or don't have the tools to do anything with them ?
> The other issue that comes up is that, in addition to identifying business
> rule errors such as you describe, you have to create error handling/audit
> logging that can be used to create an 824. No translator does this
> automatically that I'm aware of.
I'm currently working on enabling automatic 824 generation from our translator
that makes the process almost painless - simply another script command whenever
an acknowledgement or error is required and the translator tkes care of
assembling the 824 and the current contexts into the 824 structure and
sending it out to the original sender.
> > checking case sizes, discount levels against quantity can similarly
> > be encoded in the IG
>
> You are building an application within the translator.
No, not quite. Building it in the IG where it already is, but currently
only in unparseable english words. The translator only implements the IG.
Besides, these are simple constraints:
the quantity must be a whole number of cases:
assert quantity % case_size = 0;
the discount level is tiered on the quantity:
if quantity > 100
assert discount = 10;
if quantity > 1000
assert discount = 15;
> You don't want to do this. Organizations have spent 10s of millions to
> implement SAP R/3, Peoplesoft, Oracle, etc. to do this type of processing.
By using the translator to do simple automatic stuff like this, you save
all the execution cycles and processor load of even hauling SAP or Oracle
into memory ready to execute. You also get your EDI response straight
back at the lowest level without needing a further translator run to
handle outgoing 824s.
Jonathan
------------------------------------------------------------------------------
Jonathan Allen | [EMAIL PROTECTED] | Voice: 01404-823670
Barum Computer Consultants | | Fax: 01404-823671
------------------------------------------------------------------------------
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
