How to read a non standard GateIn EDIFACT file (Non CODECO Format)

241 views
Skip to first unread message

NewToBOTS

unread,
Dec 31, 2019, 6:32:58 AM12/31/19
to Bots Open Source EDI Translator
I have managed to read a CODECO EDIFACT GateIn file using the CODECOD95BUN.py grammar and it works perfectly.
I have attached a non standard Container Movement GateIn EDIFACT file. Can I modify an EDIFACT grammar to read this file, or do I need to create a FIXED grammar from scratch ?  thanks
Gatein edi.txt

Eppye Bots

unread,
Dec 31, 2019, 6:38:26 AM12/31/19
to 'Chuck Turco' via Bots Open Source EDI Translator
I would try to find out what edifact version (eg D95B) they have used to make this.
use that as a starting point.
with a bt of luck they only created their own message structure, and re-used the segments.

kind regards, Henk-Jan Ebbers


On Tue, Dec 31, 2019 at 12:32 PM NewToBOTS <jtscus...@gmail.com> wrote:
I have managed to read a CODECO EDIFACT GateIn file using the CODECOD95BUN.py grammar and it works perfectly.
I have attached a non standard Container Movement GateIn EDIFACT file. Can I modify an EDIFACT grammar to read this file, or do I need to create a FIXED grammar from scratch ?  thanks

--
You received this message because you are subscribed to the Google Groups "Bots Open Source EDI Translator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to botsmail+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/botsmail/138b10b4-0c12-4019-b5cd-36c037985aed%40googlegroups.com.

jtscustomer2 jira

unread,
Dec 31, 2019, 8:11:17 AM12/31/19
to bots...@googlegroups.com
Please do read this link that I got from a search on internet. Please do read the response by Klaus. I am sure you would know this as well ...


"However, many users of the older TC104 EDIFACT messages decided to
continue to use them instead of migrating to the newer versions now
part of the UN/EDIFACT message set. This is also true for other
industry that developed EDIFACT messages which now have UN/EDIFACT
versions. As the saying goes, if it is not broken why fix it."
 

So in response to this would you suggest a different approach ..

Thanking you,

Eppye Bots

unread,
Dec 31, 2019, 8:56:39 AM12/31/19
to 'Chuck Turco' via Bots Open Source EDI Translator
it seems that this is based on very old edifact directories.

so might be quite some work making the grammars.
if I had to do this now  would not bother too much and use X12-like element names - those are easier to use.
like this:
'BGM': [
    ['BOTSID', 'M', 3, 'AN'],
    ['BGM01', 'C', [
        ['BGM01.01', 'C', 3, 'AN'],
        ['BGM01.02', 'C', 3, 'AN'],
        ['BGM01.03', 'C', 3, 'AN'],
        ['BGM01.04', 'C', 35, 'AN'],
    ]],
    ['BGM02', 'C', 35, 'AN'],
    ['BGM03', 'C', 3, 'AN'],
    ['BGM04', 'C', 3, 'AN'],
],


kind regards, Henk-Jan Ebbers


Message has been deleted

NewToBOTS

unread,
Jan 7, 2020, 8:19:47 AM1/7/20
to Bots Open Source EDI Translator
Thanks Henk-Jan Ebbers, it worked as you said by rearranging the segments. Now it is properly converting from EDIFACT (GateIn) to ANSI Fixed File. And the attached file helped too. 

Thanking you,
Pramod Koshy.


On Tuesday, December 31, 2019 at 7:26:39 PM UTC+5:30, eppye wrote:
it seems that this is based on very old edifact directories.

so might be quite some work making the grammars.
if I had to do this now  would not bother too much and use X12-like element names - those are easier to use.
like this:
'BGM': [
    ['BOTSID', 'M', 3, 'AN'],
    ['BGM01', 'C', [
        ['BGM01.01', 'C', 3, 'AN'],
        ['BGM01.02', 'C', 3, 'AN'],
        ['BGM01.03', 'C', 3, 'AN'],
        ['BGM01.04', 'C', 35, 'AN'],
    ]],
    ['BGM02', 'C', 35, 'AN'],
    ['BGM03', 'C', 3, 'AN'],
    ['BGM04', 'C', 3, 'AN'],
],


kind regards, Henk-Jan Ebbers


On Tue, Dec 31, 2019 at 2:11 PM jtscustomer2 jira <jtscus...@gmail.com> wrote:
Please do read this link that I got from a search on internet. Please do read the response by Klaus. I am sure you would know this as well ...


"However, many users of the older TC104 EDIFACT messages decided to
continue to use them instead of migrating to the newer versions now
part of the UN/EDIFACT message set. This is also true for other
industry that developed EDIFACT messages which now have UN/EDIFACT
versions. As the saying goes, if it is not broken why fix it."
 

So in response to this would you suggest a different approach ..

Thanking you,
On Tue, Dec 31, 2019 at 5:08 PM Eppye Bots <eppy...@gmail.com> wrote:
I would try to find out what edifact version (eg D95B) they have used to make this.
use that as a starting point.
with a bt of luck they only created their own message structure, and re-used the segments.

kind regards, Henk-Jan Ebbers


On Tue, Dec 31, 2019 at 12:32 PM NewToBOTS <jtscus...@gmail.com> wrote:
I have managed to read a CODECO EDIFACT GateIn file using the CODECOD95BUN.py grammar and it works perfectly.
I have attached a non standard Container Movement GateIn EDIFACT file. Can I modify an EDIFACT grammar to read this file, or do I need to create a FIXED grammar from scratch ?  thanks

--
You received this message because you are subscribed to the Google Groups "Bots Open Source EDI Translator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bots...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Bots Open Source EDI Translator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bots...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Bots Open Source EDI Translator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bots...@googlegroups.com.
TB002_EDIS_February_2003.pdf
Reply all
Reply to author
Forward
0 new messages