Ok, I am almost there! Just one last issue. So I have an inbound x12 858 that I am just trying to pass through. I call x12tox12 for the translation which just does
#mapping-script import bots.transform as transform def main(inn,out): transform.inn2out(inn,out)
The only thing that is strange is that if I pass a P for production
At the moment I have the route set to blank instead of Only Test or Only Production (neither of those have the intended consequences instead the file gets stuck)
I realize I am doing something somewhat strange... but it is so close I think it should work?
the x12 message(s) are not really 'passed though'; the messages are read, parsed, go to the mapping script and are generated again. The envelope is created again. Normally one would have a 'real' mapping script here which converts to an inhouse file. So that is the reason why this happens - the test indicator used is a default value. as you see, more values in the envelope are different.
you can set other defaults with the syntax parameter of a grama; or use the values in de received envelop to set the values in the generated envelope.
Mellerbeck wrote: > Ok, I am almost there! Just one last issue. So I have an inbound x12 > 858 that I am just trying to pass through. I call x12tox12 for the > translation which just does
> At the moment I have the route set to blank instead of Only Test or > Only Production (neither of those have the intended consequences > instead the file gets stuck)
> I realize I am doing something somewhat strange... but it is so close > I think it should work?
> the x12 message(s) are not really 'passed though'; the messages are > read, parsed, go to the mapping script and are generated again. The > envelope is created again. > Normally one would have a 'real' mapping script here which converts to > an inhouse file. > So that is the reason why this happens - the test indicator used is a > default value. > as you see, more values in the envelope are different.
> you can set other defaults with the syntax parameter of a grama; or use > the values in de received envelop to set the values in the generated > envelope.
> kind regards, > henk-jan
> Mellerbeck wrote: > > Ok, I am almost there! Just one last issue. So I have an inbound x12 > > 858 that I am just trying to pass through. I call x12tox12 for the > > translation which just does
> > At the moment I have the route set to blank instead of Only Test or > > Only Production (neither of those have the intended consequences > > instead the file gets stuck)
> > I realize I am doing something somewhat strange... but it is so close > > I think it should work?
> the x12 message(s) are not really 'passed though'; the messages are > read, parsed, go to the mapping script and are generated again. The > envelope is created again. > Normally one would have a 'real' mapping script here which converts to > an inhouse file. > So that is the reason why this happens - the test indicator used is a > default value. > as you see, more values in the envelope are different.
> you can set other defaults with the syntax parameter of a grama; or use > the values in de received envelop to set the values in the generated > envelope.
> kind regards, > henk-jan
> Mellerbeck wrote: > > Ok, I am almost there! Just one last issue. So I have an inbound x12 > > 858 that I am just trying to pass through. I call x12tox12 for the > > translation which just does
> > At the moment I have the route set to blank instead of Only Test or > > Only Production (neither of those have the intended consequences > > instead the file gets stuck)
> > I realize I am doing something somewhat strange... but it is so close > > I think it should work?
in the grammar of the message there is a syntax section, something like: syntax = { 'ISA15':'P', }
in bots/grammar.py are all syntax options. it works a bit like CSS: - in grammar.py are the defaults values of the syntax - you can overrule the syntax values in the grammar of your message - you can overrule the syntax values per partner (in bots/usersys/<editype>/<partnerid>.py)
Mellerbeck wrote: > Ok, that makes sense. I have tried to figure this out but so far no > luck :(
> Looking in \bots\grammar.py it looks like ISA15 is default to 'P'
> I have tried
> out.put({'ISA15':'P'})
> or
> out.put({'BOTSID':'ISA','ISA15':'P'})
> in the mapping but I think that at this point we are inside the > envelope so it is not valid?
> hmm a little more reading led me to try this
> out.ta_info['testindicator'] = 'P'
> hmmm I think I am maybe close?? but so far I haven't hit on it?
> Any pointers in the right direction?
> Thanks,
> Michael
> On Jan 23, 7:00 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>> Hi Michael,
>> the x12 message(s) are not really 'passed though'; the messages are >> read, parsed, go to the mapping script and are generated again. The >> envelope is created again. >> Normally one would have a 'real' mapping script here which converts to >> an inhouse file. >> So that is the reason why this happens - the test indicator used is a >> default value. >> as you see, more values in the envelope are different.
>> you can set other defaults with the syntax parameter of a grama; or use >> the values in de received envelop to set the values in the generated >> envelope.
>> kind regards, >> henk-jan
>> Mellerbeck wrote:
>>> Ok, I am almost there! Just one last issue. So I have an inbound x12 >>> 858 that I am just trying to pass through. I call x12tox12 for the >>> translation which just does
>>> At the moment I have the route set to blank instead of Only Test or >>> Only Production (neither of those have the intended consequences >>> instead the file gets stuck)
>>> I realize I am doing something somewhat strange... but it is so close >>> I think it should work?
> in the grammar of the message there is a syntax section, something like: > syntax = { > 'ISA15':'P', > }
> in bots/grammar.py are all syntax options. > it works a bit like CSS: > - in grammar.py are the defaults values of the syntax > - you can overrule the syntax values in the grammar of your message > - you can overrule the syntax values per partner (in > bots/usersys/<editype>/<partnerid>.py)
> kind regards, > henk-jan
> Mellerbeck wrote: > > Ok, that makes sense. I have tried to figure this out but so far no > > luck :(
> > Looking in \bots\grammar.py it looks like ISA15 is default to 'P'
> > I have tried
> > out.put({'ISA15':'P'})
> > or
> > out.put({'BOTSID':'ISA','ISA15':'P'})
> > in the mapping but I think that at this point we are inside the > > envelope so it is not valid?
> > hmm a little more reading led me to try this
> > out.ta_info['testindicator'] = 'P'
> > hmmm I think I am maybe close?? but so far I haven't hit on it?
> > Any pointers in the right direction?
> > Thanks,
> > Michael
> > On Jan 23, 7:00 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >> Hi Michael,
> >> the x12 message(s) are not really 'passed though'; the messages are > >> read, parsed, go to the mapping script and are generated again. The > >> envelope is created again. > >> Normally one would have a 'real' mapping script here which converts to > >> an inhouse file. > >> So that is the reason why this happens - the test indicator used is a > >> default value. > >> as you see, more values in the envelope are different.
> >> you can set other defaults with the syntax parameter of a grama; or use > >> the values in de received envelop to set the values in the generated > >> envelope.
> >> kind regards, > >> henk-jan
> >> Mellerbeck wrote:
> >>> Ok, I am almost there! Just one last issue. So I have an inbound x12 > >>> 858 that I am just trying to pass through. I call x12tox12 for the > >>> translation which just does
> >>> At the moment I have the route set to blank instead of Only Test or > >>> Only Production (neither of those have the intended consequences > >>> instead the file gets stuck)
> >>> I realize I am doing something somewhat strange... but it is so close > >>> I think it should work?
> I wonder if there is something strange with my channels? I am not > specifying a Toeditype or Tomessagetype, could that be related?
> -Michael
> On Jan 26, 8:51 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> > in the grammar of the message there is a syntax section, something like: > > syntax = { > > 'ISA15':'P', > > }
> > in bots/grammar.py are all syntax options. > > it works a bit like CSS: > > - in grammar.py are the defaults values of the syntax > > - you can overrule the syntax values in the grammar of your message > > - you can overrule the syntax values per partner (in > > bots/usersys/<editype>/<partnerid>.py)
> > kind regards, > > henk-jan
> > Mellerbeck wrote: > > > Ok, that makes sense. I have tried to figure this out but so far no > > > luck :(
> > > Looking in \bots\grammar.py it looks like ISA15 is default to 'P'
> > > I have tried
> > > out.put({'ISA15':'P'})
> > > or
> > > out.put({'BOTSID':'ISA','ISA15':'P'})
> > > in the mapping but I think that at this point we are inside the > > > envelope so it is not valid?
> > > hmm a little more reading led me to try this
> > > out.ta_info['testindicator'] = 'P'
> > > hmmm I think I am maybe close?? but so far I haven't hit on it?
> > > Any pointers in the right direction?
> > > Thanks,
> > > Michael
> > > On Jan 23, 7:00 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> > >> Hi Michael,
> > >> the x12 message(s) are not really 'passed though'; the messages are > > >> read, parsed, go to the mapping script and are generated again. The > > >> envelope is created again. > > >> Normally one would have a 'real' mapping script here which converts to > > >> an inhouse file. > > >> So that is the reason why this happens - the test indicator used is a > > >> default value. > > >> as you see, more values in the envelope are different.
> > >> you can set other defaults with the syntax parameter of a grama; or use > > >> the values in de received envelop to set the values in the generated > > >> envelope.
> > >> kind regards, > > >> henk-jan
> > >> Mellerbeck wrote:
> > >>> Ok, I am almost there! Just one last issue. So I have an inbound x12 > > >>> 858 that I am just trying to pass through. I call x12tox12 for the > > >>> translation which just does
> > >>> At the moment I have the route set to blank instead of Only Test or > > >>> Only Production (neither of those have the intended consequences > > >>> instead the file gets stuck)
> > >>> I realize I am doing something somewhat strange... but it is so close > > >>> I think it should work?
I was just looking at this, and doing some testing. a workaround for envelope.py (around line 348): if self.ta_info['testindicator'] and self.ta_info['testindicator']!='0': should be: if self.ta_info['testindicator'] and self.ta_info['testindicator']!='P':
this works for this situation, but I am going to test more situatons.
>> I wonder if there is something strange with my channels? I am not >> specifying a Toeditype or Tomessagetype, could that be related?
>> -Michael
>> On Jan 26, 8:51 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>>> in the grammar of the message there is a syntax section, something like: >>> syntax = { >>> 'ISA15':'P', >>> }
>>> in bots/grammar.py are all syntax options. >>> it works a bit like CSS: >>> - in grammar.py are the defaults values of the syntax >>> - you can overrule the syntax values in the grammar of your message >>> - you can overrule the syntax values per partner (in >>> bots/usersys/<editype>/<partnerid>.py)
>>> kind regards, >>> henk-jan
>>> Mellerbeck wrote:
>>>> Ok, that makes sense. I have tried to figure this out but so far no >>>> luck :(
>>>> Looking in \bots\grammar.py it looks like ISA15 is default to 'P'
>>>> I have tried
>>>> out.put({'ISA15':'P'})
>>>> or
>>>> out.put({'BOTSID':'ISA','ISA15':'P'})
>>>> in the mapping but I think that at this point we are inside the >>>> envelope so it is not valid?
>>>> hmm a little more reading led me to try this
>>>> out.ta_info['testindicator'] = 'P'
>>>> hmmm I think I am maybe close?? but so far I haven't hit on it?
>>>> Any pointers in the right direction?
>>>> Thanks,
>>>> Michael
>>>> On Jan 23, 7:00 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>>>>> Hi Michael,
>>>>> the x12 message(s) are not really 'passed though'; the messages are >>>>> read, parsed, go to the mapping script and are generated again. The >>>>> envelope is created again. >>>>> Normally one would have a 'real' mapping script here which converts to >>>>> an inhouse file. >>>>> So that is the reason why this happens - the test indicator used is a >>>>> default value. >>>>> as you see, more values in the envelope are different.
>>>>> you can set other defaults with the syntax parameter of a grama; or use >>>>> the values in de received envelop to set the values in the generated >>>>> envelope.
>>>>> kind regards, >>>>> henk-jan
>>>>> Mellerbeck wrote:
>>>>>> Ok, I am almost there! Just one last issue. So I have an inbound x12 >>>>>> 858 that I am just trying to pass through. I call x12tox12 for the >>>>>> translation which just does
>>>>>> At the moment I have the route set to blank instead of Only Test or >>>>>> Only Production (neither of those have the intended consequences >>>>>> instead the file gets stuck)
>>>>>> I realize I am doing something somewhat strange... but it is so close >>>>>> I think it should work?
> I was just looking at this, and doing some testing. > a workaround for envelope.py (around line 348): > if self.ta_info['testindicator'] and > self.ta_info['testindicator']!='0': > should be: > if self.ta_info['testindicator'] and > self.ta_info['testindicator']!='P':
> this works for this situation, but I am going to test more situatons.
> kidn regards, > henk-jan
> Mellerbeck wrote: > > I tried to put the
> > syntax = { > > 'ISA15':'P', > > }
> > in the bots/usersys/<editype>/<partnerid>.py as well. But it still > > keeps putting out a T
> > I guess it doesn't like me :(
> > On Jan 26, 9:29 am, Mellerbeck <mellerb...@gmail.com> wrote:
> >> I wonder if there is something strange with my channels? I am not > >> specifying a Toeditype or Tomessagetype, could that be related?
> >> -Michael
> >> On Jan 26, 8:51 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >>> in the grammar of the message there is a syntax section, something like: > >>> syntax = { > >>> 'ISA15':'P', > >>> }
> >>> in bots/grammar.py are all syntax options. > >>> it works a bit like CSS: > >>> - in grammar.py are the defaults values of the syntax > >>> - you can overrule the syntax values in the grammar of your message > >>> - you can overrule the syntax values per partner (in > >>> bots/usersys/<editype>/<partnerid>.py)
> >>> kind regards, > >>> henk-jan
> >>> Mellerbeck wrote:
> >>>> Ok, that makes sense. I have tried to figure this out but so far no > >>>> luck :(
> >>>> Looking in \bots\grammar.py it looks like ISA15 is default to 'P'
> >>>> I have tried
> >>>> out.put({'ISA15':'P'})
> >>>> or
> >>>> out.put({'BOTSID':'ISA','ISA15':'P'})
> >>>> in the mapping but I think that at this point we are inside the > >>>> envelope so it is not valid?
> >>>> hmm a little more reading led me to try this
> >>>> out.ta_info['testindicator'] = 'P'
> >>>> hmmm I think I am maybe close?? but so far I haven't hit on it?
> >>>> Any pointers in the right direction?
> >>>> Thanks,
> >>>> Michael
> >>>> On Jan 23, 7:00 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >>>>> Hi Michael,
> >>>>> the x12 message(s) are not really 'passed though'; the messages are > >>>>> read, parsed, go to the mapping script and are generated again. The > >>>>> envelope is created again. > >>>>> Normally one would have a 'real' mapping script here which converts to > >>>>> an inhouse file. > >>>>> So that is the reason why this happens - the test indicator used is a > >>>>> default value. > >>>>> as you see, more values in the envelope are different.
> >>>>> you can set other defaults with the syntax parameter of a grama; or use > >>>>> the values in de received envelop to set the values in the generated > >>>>> envelope.
> >>>>> kind regards, > >>>>> henk-jan
> >>>>> Mellerbeck wrote:
> >>>>>> Ok, I am almost there! Just one last issue. So I have an inbound x12 > >>>>>> 858 that I am just trying to pass through. I call x12tox12 for the > >>>>>> translation which just does
> >>>>>> At the moment I have the route set to blank instead of Only Test or > >>>>>> Only Production (neither of those have the intended consequences > >>>>>> instead the file gets stuck)
> >>>>>> I realize I am doing something somewhat strange... but it is so close > >>>>>> I think it should work?