bots grammar recorddefs enhancement
114 views
Skip to first unread message
Lucky Lud
Feb 5, 2013, 9:15:27 AM2/5/13
to botsmail
Hi,
I want to share an idea about reccordefs grammar enhancement and especially for Edifact messages with lot's of fields with list code.
The idea is to add a new format, for a list of values available for a field like :
'SGU': [
['BOTSID', 'M', 3, 'AN'],
['9166', 'M', 3, 'AN'],
['7299', 'C', 3, 'AN'],
['6176', 'C', 7, 'N'],
['7168', 'C', 3, 'N'],
['1050', 'C', 10, 'AN'],
['1049', 'C', 3, 'L', [ 1, 2, 3, 4, 5, 6]],
['4513', 'C', 3, 'AN'],
],
Best Regards,
Ludovic
I want to share an idea about reccordefs grammar enhancement and especially for Edifact messages with lot's of fields with list code.
The idea is to add a new format, for a list of values available for a field like :
'SGU': [
['BOTSID', 'M', 3, 'AN'],
['9166', 'M', 3, 'AN'],
['7299', 'C', 3, 'AN'],
['6176', 'C', 7, 'N'],
['7168', 'C', 3, 'N'],
['1050', 'C', 10, 'AN'],
['1049', 'C', 3, 'L', [ 1, 2, 3, 4, 5, 6]],
['4513', 'C', 3, 'AN'],
],
Best Regards,
Ludovic
henk-jan ebbers
Feb 5, 2013, 1:01:03 PM2/5/13
to bots...@googlegroups.com
hi Ludovic,
code checking ;-))
standard like edifact/x12 kind of suggest that code checking is useful/should be done.
as you might have noticed, this is not in bots.
IMHO code checking turns out to be less useful than it looks.
If it is useful, bots could do this (think it is not that hard to build it in).
but in my edi experience it is not worth the trouble.
in my experience it is 'turned off' in most edi implementations.
why do you think it is useful? (please, convince me)
kind regards,
henk-jan
> --
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
code checking ;-))
standard like edifact/x12 kind of suggest that code checking is useful/should be done.
as you might have noticed, this is not in bots.
IMHO code checking turns out to be less useful than it looks.
If it is useful, bots could do this (think it is not that hard to build it in).
but in my edi experience it is not worth the trouble.
in my experience it is 'turned off' in most edi implementations.
why do you think it is useful? (please, convince me)
kind regards,
henk-jan
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
Lucky Lud
Feb 5, 2013, 7:08:25 PM2/5/13
to bots...@googlegroups.com
Yes that's it ! code checking :)
I agree, this feature is not so much used, but it can be useful during testing.
For example, checking some fields in incoming csv and if something is wrong or missing, sending an email with errors to a partner could be nice :)
Regards,
Ludovic
--
I agree, this feature is not so much used, but it can be useful during testing.
For example, checking some fields in incoming csv and if something is wrong or missing, sending an email with errors to a partner could be nice :)
Regards,
Ludovic
2013/2/5 henk-jan ebbers <eppye...@gmail.com>
To unsubscribe from this group and stop receiving emails from it, send an email to botsmail+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
___ ___
/\ \ _____ /\ \
\:\ \ /::\ \ /::\ \
\:\ \ /:/\:\ \ /:/\:\ \
___ ___ ___ \:\ \ /:/ \:\__\ /:/ \:\ \
/\ \ /\__\ /\ \ \:\__\ /:/__/ \:|__| /:/__/ \:\__\
\:\ \ /:/ / \:\ \ /:/ / \:\ \ /:/ / \:\ \ /:/ /
\:\ /:/ / \:\ /:/ / \:\ /:/ / \:\ /:/ /
\:\/:/ / \:\/:/ / \:\/:/ / \:\/:/ /
\::/ / \::/ / \::/ / \::/ /
\/__/ \/__/ \/__/ \/__/
henk-jan ebbers
Feb 7, 2013, 5:44:21 AM2/7/13
to bots...@googlegroups.com
On 02/06/2013 01:08 AM, Lucky Lud wrote:
> Yes that's it ! code checking :)
> I agree, this feature is not so much used, but it can be useful during testing.
> For example, checking some fields in incoming csv and if something is wrong or missing, sending an email with errors to a partner could be nice :)
think the easiest way to do this is check the codes in the mapping script!
kind regards,
henk-jan
>
>
> Regards,
>
> Ludovic
>
> 2013/2/5 henk-jan ebbers <eppye...@gmail.com <mailto:eppye...@gmail.com>>
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
> --
> 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 <mailto:botsmail%2Bunsu...@googlegroups.com>.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "Bots Open Source EDI Translator" group.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
>
>
> --
>
> ___ ___
> /\ \ _____ /\ \
> \:\ \ /::\ \ /::\ \
> \:\ \ /:/\:\ \ /:/\:\ \
> ___ ___ ___ \:\ \ /:/ \:\__\ /:/ \:\ \
> /\ \ /\__\ /\ \ \:\__\ /:/__/ \:|__| /:/__/ \:\__\
> \:\ \ /:/ / \:\ \ /:/ / \:\ \ /:/ / \:\ \ /:/ /
> \:\ /:/ / \:\ /:/ / \:\ /:/ / \:\ /:/ /
> \:\/:/ / \:\/:/ / \:\/:/ / \:\/:/ /
> \::/ / \::/ / \::/ / \::/ /
> \/__/ \/__/ \/__/ \/__/
>
>
>
>
>
> --
>
> ___ ___
> /\ \ _____ /\ \
> \:\ \ /::\ \ /::\ \
> \:\ \ /:/\:\ \ /:/\:\ \
> ___ ___ ___ \:\ \ /:/ \:\__\ /:/ \:\ \
> /\ \ /\__\ /\ \ \:\__\ /:/__/ \:|__| /:/__/ \:\__\
> \:\ \ /:/ / \:\ \ /:/ / \:\ \ /:/ / \:\ \ /:/ /
> \:\ /:/ / \:\ /:/ / \:\ /:/ / \:\ /:/ /
> \:\/:/ / \:\/:/ / \:\/:/ / \:\/:/ /
> \::/ / \::/ / \::/ / \::/ /
> \/__/ \/__/ \/__/ \/__/
> --
> 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.
> You received this message because you are subscribed to the Google Groups "Bots Open Source EDI Translator" group.
Lucky Lud
Feb 7, 2013, 9:49:35 AM2/7/13
to bots...@googlegroups.com
Hi henk-jan,
For sure :) I'll have a look in grammar.py first if I can do something to implement it in an easy way.
Best regards,
Ludovic
think the easiest way to do this is check the codes in the mapping script!
For sure :) I'll have a look in grammar.py first if I can do something to implement it in an easy way.
Best regards,
Ludovic
henk-jan ebbers
Feb 7, 2013, 9:56:49 AM2/7/13
to bots...@googlegroups.com
hi Ludovic,
you could take a look at this: http://code.google.com/p/bots/wiki/MappingCcode
(this way you could have a code list that can be maintained via gui)
kind regards,
henk-jan
you could take a look at this: http://code.google.com/p/bots/wiki/MappingCcode
(this way you could have a code list that can be maintained via gui)
kind regards,
henk-jan
Steven Hammond
Feb 7, 2013, 10:09:06 AM2/7/13
to bots...@googlegroups.com
Is there anyway to have the display of an EDI file use the termination
character as a new line? In other words, when I click on the inbound PO
to look at it, currently it is one LONG line. Instead, could it
determine the segment terminator and then use it to wrap so that the
segments are on separate lines.
Thanks for a great product!
Steven Hammond
TCC
Cleburne, TX
character as a new line? In other words, when I click on the inbound PO
to look at it, currently it is one LONG line. Instead, could it
determine the segment terminator and then use it to wrap so that the
segments are on separate lines.
Thanks for a great product!
Steven Hammond
TCC
Cleburne, TX
henk-jan ebbers
Feb 7, 2013, 12:45:11 PM2/7/13
to bots...@googlegroups.com
no.
but would be useful indeed; but I have never looked at it.
this is not as easy as it might seem.
sometimes there is already <CR/LF>,
some use <LF> as segemtn seperator, etc..
kind regards,
henk-jan
but would be useful indeed; but I have never looked at it.
this is not as easy as it might seem.
sometimes there is already <CR/LF>,
some use <LF> as segemtn seperator, etc..
kind regards,
henk-jan
Steven Hammond
Feb 7, 2013, 2:44:27 PM2/7/13
to bots...@googlegroups.com
Well, honestly, I wrote a short python program to read the field separator and segment terminator and it replaces it with values I want (like \n). I just pre-process the inbound document through it first before handing it off to the bots-engine.py I didn't know if there was place to hook in bots or not. This way it essential sets the field/segment separators to something more readable. I have 1 trading partner that uses non-printable characters for the field separator!
Steve Hammond
--
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+unsubscribe@googlegroups.com.
Lucky Lud
Feb 7, 2013, 5:06:57 PM2/7/13
to bots...@googlegroups.com
you could take a look at this: http://code.google.com/p/bots/wiki/MappingCcode
This table is really useful. Thanks.
Ludovic
henk-jan ebbers
Feb 8, 2013, 11:33:37 AM2/8/13
to bots...@googlegroups.com
hi Steven,
On 02/07/2013 08:44 PM, Steven Hammond wrote:
> Well, honestly, I wrote a /short/ python program to read the field separator and segment terminator and it replaces it with values I want (like \n).
yes, that works in a lot of cases; you write it and you know when something strange is showing up (oh yeah, I remember blah blah)
I am very interesting & sure want to cooperate, but
> I just pre-process the inbound document through it first before handing it off to the bots-engine.py I didn't know if there was place to hook in bots or not.
think is is better to make a hook for this.
hook should be in the 'display part',
main reason is that some companies really send strange things (eg the x12 file has a <CR/LF> after 80position) so you do not want to mangle something in the original x12 file.
henk-jan
> This way it essential sets the field/segment separators to something more readable. I have 1 trading partner that uses non-printable characters for the field separator!
>
> Steve Hammond
>
On 02/07/2013 08:44 PM, Steven Hammond wrote:
> Well, honestly, I wrote a /short/ python program to read the field separator and segment terminator and it replaces it with values I want (like \n).
yes, that works in a lot of cases; you write it and you know when something strange is showing up (oh yeah, I remember blah blah)
I am very interesting & sure want to cooperate, but
> I just pre-process the inbound document through it first before handing it off to the bots-engine.py I didn't know if there was place to hook in bots or not.
hook should be in the 'display part',
main reason is that some companies really send strange things (eg the x12 file has a <CR/LF> after 80position) so you do not want to mangle something in the original x12 file.
henk-jan
> This way it essential sets the field/segment separators to something more readable. I have 1 trading partner that uses non-printable characters for the field separator!
>
> Steve Hammond
>
> On Thu, Feb 7, 2013 at 11:45 AM, henk-jan ebbers <eppye...@gmail.com <mailto:eppye...@gmail.com>> wrote:
>
> no.
> but would be useful indeed; but I have never looked at it.
> this is not as easy as it might seem.
> sometimes there is already <CR/LF>,
> some use <LF> as segemtn seperator, etc..
>
> kind regards,
> henk-jan
>
>
> On 02/07/2013 04:09 PM, Steven Hammond wrote:
>
> Is there anyway to have the display of an EDI file use the termination character as a new line? In other words, when I click on the inbound PO to look at it, currently it is one LONG line.
> Instead, could it determine the segment terminator and then use it to wrap so that the segments are on separate lines.
>
> Thanks for a great product!
>
> Steven Hammond
> TCC
> Cleburne, TX
>
>
> --
> 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 <mailto:botsmail%2Bunsu...@googlegroups.com>.
>
> no.
> but would be useful indeed; but I have never looked at it.
> this is not as easy as it might seem.
> sometimes there is already <CR/LF>,
> some use <LF> as segemtn seperator, etc..
>
> kind regards,
> henk-jan
>
>
> On 02/07/2013 04:09 PM, Steven Hammond wrote:
>
> Is there anyway to have the display of an EDI file use the termination character as a new line? In other words, when I click on the inbound PO to look at it, currently it is one LONG line.
> Instead, could it determine the segment terminator and then use it to wrap so that the segments are on separate lines.
>
> Thanks for a great product!
>
> Steven Hammond
> TCC
> Cleburne, TX
>
>
> --
> You received this message because you are subscribed to the Google Groups "Bots Open Source EDI Translator" group.
> --
> 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.
> You received this message because you are subscribed to the Google Groups "Bots Open Source EDI Translator" group.
henk-jan ebbers
Apr 30, 2013, 5:29:29 PM4/30/13
to bots...@googlegroups.com
hai Steven,
added this to bots in development version.
kind regards,
henk-jan
On 02/07/2013 08:44 PM, Steven Hammond wrote:
> Well, honestly, I wrote a /short/ python program to read the field separator and segment terminator and it replaces it with values I want (like \n). I just pre-process the inbound document through
added this to bots in development version.
kind regards,
henk-jan
On 02/07/2013 08:44 PM, Steven Hammond wrote:
> it first before handing it off to the bots-engine.py I didn't know if there was place to hook in bots or not. This way it essential sets the field/segment separators to something more readable. I
> have 1 trading partner that uses non-printable characters for the field separator!
>
> Steve Hammond
>
> have 1 trading partner that uses non-printable characters for the field separator!
>
> Steve Hammond
>
> On Thu, Feb 7, 2013 at 11:45 AM, henk-jan ebbers <eppye...@gmail.com <mailto:eppye...@gmail.com>> wrote:
>
> no.
> but would be useful indeed; but I have never looked at it.
> this is not as easy as it might seem.
> sometimes there is already <CR/LF>,
> some use <LF> as segemtn seperator, etc..
>
> kind regards,
> henk-jan
>
>
> On 02/07/2013 04:09 PM, Steven Hammond wrote:
>
> Is there anyway to have the display of an EDI file use the termination character as a new line? In other words, when I click on the inbound PO to look at it, currently it is one LONG line.
> Instead, could it determine the segment terminator and then use it to wrap so that the segments are on separate lines.
>
> Thanks for a great product!
>
> Steven Hammond
> TCC
> Cleburne, TX
>
>
> --
> 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 <mailto:botsmail%2Bunsu...@googlegroups.com>.
>
> no.
> but would be useful indeed; but I have never looked at it.
> this is not as easy as it might seem.
> sometimes there is already <CR/LF>,
> some use <LF> as segemtn seperator, etc..
>
> kind regards,
> henk-jan
>
>
> On 02/07/2013 04:09 PM, Steven Hammond wrote:
>
> Is there anyway to have the display of an EDI file use the termination character as a new line? In other words, when I click on the inbound PO to look at it, currently it is one LONG line.
> Instead, could it determine the segment terminator and then use it to wrap so that the segments are on separate lines.
>
> Thanks for a great product!
>
> Steven Hammond
> TCC
> Cleburne, TX
>
>
> --
> You received this message because you are subscribed to the Google Groups "Bots Open Source EDI Translator" group.
> --
> 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.
> You received this message because you are subscribed to the Google Groups "Bots Open Source EDI Translator" group.
Reply all
Reply to author
Forward
0 new messages