This is what I am looking to do, I will create an x12 EDI doc externally. I want to pass this doc through Bots (I'm guessing I need and incoming and outgoing route for this) into an AS2 service (basically it will send what ever is dropped into it's outgoing folder) if it could capture the status of the MDN it would be cool but not needed.
Then I would like to receive the 997 and have it matched up to the sent EDI doc. It looks like confirmations is related to this?
I put a plugin on the web site for MDN-confirmations (called 'demo_mdn_confirmations'). Also I added documentation about his on the web site. I will try to make a plugin for X12-997 this weekend. If you look at the plugin for MDN's you will get a good idea of how it works. 997 work quite similar to this.
Mellerbeck wrote: > I'm a fairly Bots newby so please forgive...
> This is what I am looking to do, I will create an x12 EDI doc > externally. I want to pass this doc through Bots (I'm guessing I need > and incoming and outgoing route for this) into an AS2 service > (basically it will send what ever is dropped into it's outgoing > folder) if it could capture the status of the MDN it would be cool but > not needed.
> Then I would like to receive the 997 and have it matched up to the > sent EDI doc. It looks like confirmations is related to this?
> Thanks for any pointers in the right directions!
Thank you henk-jan for the example, I think I am beginning to understand. In order to register a request for a 997 confirmation I would need to create a confirmation rule of ask-x12-997 and assign it to a channel etc.. or just ALL to request for all.
What I am next trying to investigate is if it is possible to display the Identifying number of the EDI document on the confirmation screen.
For example if I sent an invoice the BIG line might be BIG~20100107~1140774~20091230~6099918122* it would pull 1140774
or an 856 it would need to pull BSN~00~1143754~20100108~0816* it would pull 1143754
So it would need to be user definable.
If I could have a column on the confirmation screen with an additional column maybe doc ID then it could be used to verify that a specific doc was received. This is important for accounts payable to verify there invoice has been received.
Doable, or is there a different way to approach this?
Thanks,
Michael
On Jan 8, 6:56 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> I put a plugin on the web site for MDN-confirmations (called > 'demo_mdn_confirmations'). > Also I added documentation about his on the web site. > I will try to make a plugin for X12-997 this weekend. > If you look at the plugin for MDN's you will get a good idea of how it > works. > 997 work quite similar to this.
> let me know if this is understandable
> kind regards, > henk-jan
> Mellerbeck wrote: > > I'm a fairly Bots newby so please forgive...
> > This is what I am looking to do, I will create an x12 EDI doc > > externally. I want to pass this doc through Bots (I'm guessing I need > > and incoming and outgoing route for this) into an AS2 service > > (basically it will send what ever is dropped into it's outgoing > > folder) if it could capture the status of the MDN it would be cool but > > not needed.
> > Then I would like to receive the 997 and have it matched up to the > > sent EDI doc. It looks like confirmations is related to this?
> > Thanks for any pointers in the right directions!
Mellerbeck wrote: > Thank you henk-jan for the example, I think I am beginning to > understand. In order to register a request for a 997 confirmation I > would need to create a confirmation rule of ask-x12-997 and assign it > to a channel etc.. or just ALL to request for all.
> What I am next trying to investigate is if it is possible to display > the Identifying number of the EDI document on the confirmation screen.
No, bots does not do this yet.
> For example if I sent an invoice the BIG line might be > BIG~20100107~1140774~20091230~6099918122* it would pull 1140774
> or an 856 it would need to pull BSN~00~1143754~20100108~0816* it > would pull 1143754
> So it would need to be user definable.
> If I could have a column on the confirmation screen with an additional > column maybe doc ID then it could be used to verify that a specific > doc was received. This is important for accounts payable to verify > there invoice has been received.
> Doable, or is there a different way to approach this?
doable. there is a field for something like invoice number, order number (the reference to the ERP system for a document). the field is filled as defined by the user.
the incoming and outgoing views focus upon edi FILES; what you what is a view for edi DOCUMENTS. this would be a new view (query logic, screen).
> On Jan 8, 6:56 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>> hi Michael,
>> I put a plugin on the web site for MDN-confirmations (called >> 'demo_mdn_confirmations'). >> Also I added documentation about his on the web site. >> I will try to make a plugin for X12-997 this weekend. >> If you look at the plugin for MDN's you will get a good idea of how it >> works. >> 997 work quite similar to this.
>> let me know if this is understandable
>> kind regards, >> henk-jan
>> Mellerbeck wrote:
>>> I'm a fairly Bots newby so please forgive...
>>> This is what I am looking to do, I will create an x12 EDI doc >>> externally. I want to pass this doc through Bots (I'm guessing I need >>> and incoming and outgoing route for this) into an AS2 service >>> (basically it will send what ever is dropped into it's outgoing >>> folder) if it could capture the status of the MDN it would be cool but >>> not needed.
>>> Then I would like to receive the 997 and have it matched up to the >>> sent EDI doc. It looks like confirmations is related to this?
>>> Thanks for any pointers in the right directions!
Could you tell me the name of the field for this reference number? Oh, I think I have found it, is it Ta.reference?
I have been able to get fairly close to what I want to accomplish now! I can pass an EDI doc through BOTs and trigger the confirmation request!
Now I just need to experiment with storing the reference number, and then I want to pass the reference number as part of the file name. It looks like this (from your previous post) will get me there
in a mapping script: import bots.transform as transform ... reference = inn.get({'BOTSID':'UNH'}, {'BOTSID':'BGM','1004':None}) #get the message ID from incoming messge out.ta_info['reference']=reference #messageID is stored as field 'reference' in tabel ta myfilename = 'prefix' + transform.unique('filename') #the filename is generated transform.persist_add('contentfilename',reference,myfilename) #filename is stored in bots database, using a domain, key and value. #place filename in content etc ...
in communication.py I have access to this stored value (in my test I added this after line 610): #*************** import transform ta_from.syn('reference') #get reference field for this ta instance myfilename = transform.persist_lookup ('contentfilename',ta_from.reference) #***************
wish me luck!
On Jan 11, 2:15 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> Mellerbeck wrote: > > Thank you henk-jan for the example, I think I am beginning to > > understand. In order to register a request for a 997 confirmation I > > would need to create a confirmation rule of ask-x12-997 and assign it > > to a channel etc.. or just ALL to request for all.
> > What I am next trying to investigate is if it is possible to display > > the Identifying number of the EDI document on the confirmation screen.
> No, bots does not do this yet.> For example if I sent an invoice the BIG line might be > > BIG~20100107~1140774~20091230~6099918122* it would pull 1140774
> > or an 856 it would need to pull BSN~00~1143754~20100108~0816* it > > would pull 1143754
> > So it would need to be user definable.
> > If I could have a column on the confirmation screen with an additional > > column maybe doc ID then it could be used to verify that a specific > > doc was received. This is important for accounts payable to verify > > there invoice has been received.
> > Doable, or is there a different way to approach this?
> doable. > there is a field for something like invoice number, order number (the > reference to the ERP system for a document). > the field is filled as defined by the user.
> the incoming and outgoing views focus upon edi FILES; what you what is a > view for edi DOCUMENTS. > this would be a new view (query logic, screen).
> kind regards, > henk-jan > -
> > Thanks,
> > Michael
> > On Jan 8, 6:56 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >> hi Michael,
> >> I put a plugin on the web site for MDN-confirmations (called > >> 'demo_mdn_confirmations'). > >> Also I added documentation about his on the web site. > >> I will try to make a plugin for X12-997 this weekend. > >> If you look at the plugin for MDN's you will get a good idea of how it > >> works. > >> 997 work quite similar to this.
> >> let me know if this is understandable
> >> kind regards, > >> henk-jan
> >> Mellerbeck wrote:
> >>> I'm a fairly Bots newby so please forgive...
> >>> This is what I am looking to do, I will create an x12 EDI doc > >>> externally. I want to pass this doc through Bots (I'm guessing I need > >>> and incoming and outgoing route for this) into an AS2 service > >>> (basically it will send what ever is dropped into it's outgoing > >>> folder) if it could capture the status of the MDN it would be cool but > >>> not needed.
> >>> Then I would like to receive the 997 and have it matched up to the > >>> sent EDI doc. It looks like confirmations is related to this?
> >>> Thanks for any pointers in the right directions!
just a quick response: the field is ta.botskey ta.reference is for the edi reference of a message (not the reference to the ERP system). BigMike seems to do something similar to what you are doing, so look in the mailing list.
(I am going to read your email more thoroughly tomorrow. It is getting late here)
Mellerbeck wrote: > Could you tell me the name of the field for this reference number? Oh, > I think I have found it, is it Ta.reference?
> I have been able to get fairly close to what I want to accomplish now! > I can pass an EDI doc through BOTs and trigger the confirmation > request!
> Now I just need to experiment with storing the reference number, and > then I want to pass the reference number as part of the file name. It > looks like this (from your previous post) will get me there
> in a mapping script: > import bots.transform as transform > ... > reference = inn.get({'BOTSID':'UNH'}, > {'BOTSID':'BGM','1004':None}) #get the > message ID from incoming messge > out.ta_info['reference']=reference > #messageID is stored as field > 'reference' > in tabel ta > myfilename = 'prefix' + transform.unique('filename') > #the filename is generated > transform.persist_add('contentfilename',reference,myfilename) > #filename is stored in bots database, using a domain, key and value. > #place filename in content etc > ...
> in communication.py I have access to this stored value (in my test I > added this after line 610): > #*************** > import transform > ta_from.syn('reference') #get reference field for > this ta instance > myfilename = transform.persist_lookup > ('contentfilename',ta_from.reference) > #***************
> wish me luck!
> On Jan 11, 2:15 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>> Hi Micheal,
>> Mellerbeck wrote:
>>> Thank you henk-jan for the example, I think I am beginning to >>> understand. In order to register a request for a 997 confirmation I >>> would need to create a confirmation rule of ask-x12-997 and assign it >>> to a channel etc.. or just ALL to request for all.
>>> What I am next trying to investigate is if it is possible to display >>> the Identifying number of the EDI document on the confirmation screen.
>> No, bots does not do this yet.> For example if I sent an invoice the BIG line might be
>>> BIG~20100107~1140774~20091230~6099918122* it would pull 1140774
>>> or an 856 it would need to pull BSN~00~1143754~20100108~0816* it >>> would pull 1143754
>>> So it would need to be user definable.
>>> If I could have a column on the confirmation screen with an additional >>> column maybe doc ID then it could be used to verify that a specific >>> doc was received. This is important for accounts payable to verify >>> there invoice has been received.
>>> Doable, or is there a different way to approach this?
>> doable. >> there is a field for something like invoice number, order number (the >> reference to the ERP system for a document). >> the field is filled as defined by the user.
>> the incoming and outgoing views focus upon edi FILES; what you what is a >> view for edi DOCUMENTS. >> this would be a new view (query logic, screen).
>> kind regards, >> henk-jan >> -
>>> Thanks,
>>> Michael
>>> On Jan 8, 6:56 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>>>> hi Michael,
>>>> I put a plugin on the web site for MDN-confirmations (called >>>> 'demo_mdn_confirmations'). >>>> Also I added documentation about his on the web site. >>>> I will try to make a plugin for X12-997 this weekend. >>>> If you look at the plugin for MDN's you will get a good idea of how it >>>> works. >>>> 997 work quite similar to this.
>>>> let me know if this is understandable
>>>> kind regards, >>>> henk-jan
>>>> Mellerbeck wrote:
>>>>> I'm a fairly Bots newby so please forgive...
>>>>> This is what I am looking to do, I will create an x12 EDI doc >>>>> externally. I want to pass this doc through Bots (I'm guessing I need >>>>> and incoming and outgoing route for this) into an AS2 service >>>>> (basically it will send what ever is dropped into it's outgoing >>>>> folder) if it could capture the status of the MDN it would be cool but >>>>> not needed.
>>>>> Then I would like to receive the 997 and have it matched up to the >>>>> sent EDI doc. It looks like confirmations is related to this?
>>>>> Thanks for any pointers in the right directions!
Mellerbeck wrote: > Could you tell me the name of the field for this reference number? Oh, > I think I have found it, is it Ta.reference?
> I have been able to get fairly close to what I want to accomplish now! > I can pass an EDI doc through BOTs and trigger the confirmation > request!
> Now I just need to experiment with storing the reference number, and > then I want to pass the reference number as part of the file name. It > looks like this (from your previous post) will get me there
> in a mapping script: > import bots.transform as transform > ... > reference = inn.get({'BOTSID':'UNH'}, > {'BOTSID':'BGM','1004':None}) #get the > message ID from incoming messge > out.ta_info['reference']=reference > #messageID is stored as field > 'reference' > in tabel ta > myfilename = 'prefix' + transform.unique('filename') > #the filename is generated > transform.persist_add('contentfilename',reference,myfilename) > #filename is stored in bots database, using a domain, key and value. > #place filename in content etc > ...
> in communication.py I have access to this stored value (in my test I > added this after line 610): > #*************** > import transform > ta_from.syn('reference') #get reference field for > this ta instance > myfilename = transform.persist_lookup > ('contentfilename',ta_from.reference) > #***************
> wish me luck!
> On Jan 11, 2:15 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>> Hi Micheal,
>> Mellerbeck wrote:
>>> Thank you henk-jan for the example, I think I am beginning to >>> understand. In order to register a request for a 997 confirmation I >>> would need to create a confirmation rule of ask-x12-997 and assign it >>> to a channel etc.. or just ALL to request for all.
>>> What I am next trying to investigate is if it is possible to display >>> the Identifying number of the EDI document on the confirmation screen.
>> No, bots does not do this yet.> For example if I sent an invoice the BIG line might be
>>> BIG~20100107~1140774~20091230~6099918122* it would pull 1140774
>>> or an 856 it would need to pull BSN~00~1143754~20100108~0816* it >>> would pull 1143754
>>> So it would need to be user definable.
>>> If I could have a column on the confirmation screen with an additional >>> column maybe doc ID then it could be used to verify that a specific >>> doc was received. This is important for accounts payable to verify >>> there invoice has been received.
>>> Doable, or is there a different way to approach this?
>> doable. >> there is a field for something like invoice number, order number (the >> reference to the ERP system for a document). >> the field is filled as defined by the user.
>> the incoming and outgoing views focus upon edi FILES; what you what is a >> view for edi DOCUMENTS. >> this would be a new view (query logic, screen).
>> kind regards, >> henk-jan >> -
>>> Thanks,
>>> Michael
>>> On Jan 8, 6:56 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>>>> hi Michael,
>>>> I put a plugin on the web site for MDN-confirmations (called >>>> 'demo_mdn_confirmations'). >>>> Also I added documentation about his on the web site. >>>> I will try to make a plugin for X12-997 this weekend. >>>> If you look at the plugin for MDN's you will get a good idea of how it >>>> works. >>>> 997 work quite similar to this.
>>>> let me know if this is understandable
>>>> kind regards, >>>> henk-jan
>>>> Mellerbeck wrote:
>>>>> I'm a fairly Bots newby so please forgive...
>>>>> This is what I am looking to do, I will create an x12 EDI doc >>>>> externally. I want to pass this doc through Bots (I'm guessing I need >>>>> and incoming and outgoing route for this) into an AS2 service >>>>> (basically it will send what ever is dropped into it's outgoing >>>>> folder) if it could capture the status of the MDN it would be cool but >>>>> not needed.
>>>>> Then I would like to receive the 997 and have it matched up to the >>>>> sent EDI doc. It looks like confirmations is related to this?
>>>>> Thanks for any pointers in the right directions!
Thank you for this, one question. How does bots handle if a 997 is sent back but a rejection status was sent. This might be a further enhancement to not just mark it as confirmed but also take note of status? Although it might already I haven't tested :)
-Michael
On Jan 13, 5:44 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> I release a plugin for x12/997 confirmations on the bots web site. > maybe this is usefull to you.
> kind regards, > henk-jan
> Mellerbeck wrote: > > Could you tell me the name of the field for this reference number? Oh, > > I think I have found it, is it Ta.reference?
> > I have been able to get fairly close to what I want to accomplish now! > > I can pass an EDI doc through BOTs and trigger the confirmation > > request!
> > Now I just need to experiment with storing the reference number, and > > then I want to pass the reference number as part of the file name. It > > looks like this (from your previous post) will get me there
> > in a mapping script: > > import bots.transform as transform > > ... > > reference = inn.get({'BOTSID':'UNH'}, > > {'BOTSID':'BGM','1004':None}) #get the > > message ID from incoming messge > > out.ta_info['reference']=reference > > #messageID is stored as field > > 'reference' > > in tabel ta > > myfilename = 'prefix' + transform.unique('filename') > > #the filename is generated > > transform.persist_add('contentfilename',reference,myfilename) > > #filename is stored in bots database, using a domain, key and value. > > #place filename in content etc > > ...
> > in communication.py I have access to this stored value (in my test I > > added this after line 610): > > #*************** > > import transform > > ta_from.syn('reference') #get reference field for > > this ta instance > > myfilename = transform.persist_lookup > > ('contentfilename',ta_from.reference) > > #***************
> > wish me luck!
> > On Jan 11, 2:15 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >> Hi Micheal,
> >> Mellerbeck wrote:
> >>> Thank you henk-jan for the example, I think I am beginning to > >>> understand. In order to register a request for a 997 confirmation I > >>> would need to create a confirmation rule of ask-x12-997 and assign it > >>> to a channel etc.. or just ALL to request for all.
> >>> What I am next trying to investigate is if it is possible to display > >>> the Identifying number of the EDI document on the confirmation screen.
> >> No, bots does not do this yet.> For example if I sent an invoice the BIG line might be
> >>> BIG~20100107~1140774~20091230~6099918122* it would pull 1140774
> >>> or an 856 it would need to pull BSN~00~1143754~20100108~0816* it > >>> would pull 1143754
> >>> So it would need to be user definable.
> >>> If I could have a column on the confirmation screen with an additional > >>> column maybe doc ID then it could be used to verify that a specific > >>> doc was received. This is important for accounts payable to verify > >>> there invoice has been received.
> >>> Doable, or is there a different way to approach this?
> >> doable. > >> there is a field for something like invoice number, order number (the > >> reference to the ERP system for a document). > >> the field is filled as defined by the user.
> >> the incoming and outgoing views focus upon edi FILES; what you what is a > >> view for edi DOCUMENTS. > >> this would be a new view (query logic, screen).
> >> kind regards, > >> henk-jan > >> -
> >>> Thanks,
> >>> Michael
> >>> On Jan 8, 6:56 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >>>> hi Michael,
> >>>> I put a plugin on the web site for MDN-confirmations (called > >>>> 'demo_mdn_confirmations'). > >>>> Also I added documentation about his on the web site. > >>>> I will try to make a plugin for X12-997 this weekend. > >>>> If you look at the plugin for MDN's you will get a good idea of how it > >>>> works. > >>>> 997 work quite similar to this.
> >>>> let me know if this is understandable
> >>>> kind regards, > >>>> henk-jan
> >>>> Mellerbeck wrote:
> >>>>> I'm a fairly Bots newby so please forgive...
> >>>>> This is what I am looking to do, I will create an x12 EDI doc > >>>>> externally. I want to pass this doc through Bots (I'm guessing I need > >>>>> and incoming and outgoing route for this) into an AS2 service > >>>>> (basically it will send what ever is dropped into it's outgoing > >>>>> folder) if it could capture the status of the MDN it would be cool but > >>>>> not needed.
> >>>>> Then I would like to receive the 997 and have it matched up to the > >>>>> sent EDI doc. It looks like confirmations is related to this?
> >>>>> Thanks for any pointers in the right directions!
it is quite easy to add, so I will add this. I use status rejected or not rejected (partially rejected is as rejected).
I am not sure how this is dealt with in edi practice. in my experience, if there is an error, contact is needed: what went wrong, what actions are needed. when an edi file is rejected, all of the transactions are rejected.
Mellerbeck wrote: > Thank you for this, one question. How does bots handle if a 997 is > sent back but a rejection status was sent. This might be a further > enhancement to not just mark it as confirmed but also take note of > status? Although it might already I haven't tested :)
> -Michael
> On Jan 13, 5:44 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>> Hi Micheal,
>> I release a plugin for x12/997 confirmations on the bots web site. >> maybe this is usefull to you.
>> kind regards, >> henk-jan
>> Mellerbeck wrote:
>>> Could you tell me the name of the field for this reference number? Oh, >>> I think I have found it, is it Ta.reference?
>>> I have been able to get fairly close to what I want to accomplish now! >>> I can pass an EDI doc through BOTs and trigger the confirmation >>> request!
>>> Now I just need to experiment with storing the reference number, and >>> then I want to pass the reference number as part of the file name. It >>> looks like this (from your previous post) will get me there
>>> in a mapping script: >>> import bots.transform as transform >>> ... >>> reference = inn.get({'BOTSID':'UNH'}, >>> {'BOTSID':'BGM','1004':None}) #get the >>> message ID from incoming messge >>> out.ta_info['reference']=reference >>> #messageID is stored as field >>> 'reference' >>> in tabel ta >>> myfilename = 'prefix' + transform.unique('filename') >>> #the filename is generated >>> transform.persist_add('contentfilename',reference,myfilename) >>> #filename is stored in bots database, using a domain, key and value. >>> #place filename in content etc >>> ...
>>> in communication.py I have access to this stored value (in my test I >>> added this after line 610): >>> #*************** >>> import transform >>> ta_from.syn('reference') #get reference field for >>> this ta instance >>> myfilename = transform.persist_lookup >>> ('contentfilename',ta_from.reference) >>> #***************
>>> wish me luck!
>>> On Jan 11, 2:15 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>>>> Hi Micheal,
>>>> Mellerbeck wrote:
>>>>> Thank you henk-jan for the example, I think I am beginning to >>>>> understand. In order to register a request for a 997 confirmation I >>>>> would need to create a confirmation rule of ask-x12-997 and assign it >>>>> to a channel etc.. or just ALL to request for all.
>>>>> What I am next trying to investigate is if it is possible to display >>>>> the Identifying number of the EDI document on the confirmation screen.
>>>> No, bots does not do this yet.> For example if I sent an invoice the BIG line might be
>>>>> BIG~20100107~1140774~20091230~6099918122* it would pull 1140774
>>>>> or an 856 it would need to pull BSN~00~1143754~20100108~0816* it >>>>> would pull 1143754
>>>>> So it would need to be user definable.
>>>>> If I could have a column on the confirmation screen with an additional >>>>> column maybe doc ID then it could be used to verify that a specific >>>>> doc was received. This is important for accounts payable to verify >>>>> there invoice has been received.
>>>>> Doable, or is there a different way to approach this?
>>>> doable. >>>> there is a field for something like invoice number, order number (the >>>> reference to the ERP system for a document). >>>> the field is filled as defined by the user.
>>>> the incoming and outgoing views focus upon edi FILES; what you what is a >>>> view for edi DOCUMENTS. >>>> this would be a new view (query logic, screen).
>>>> kind regards, >>>> henk-jan >>>> -
>>>>> Thanks,
>>>>> Michael
>>>>> On Jan 8, 6:56 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>>>>>> hi Michael,
>>>>>> I put a plugin on the web site for MDN-confirmations (called >>>>>> 'demo_mdn_confirmations'). >>>>>> Also I added documentation about his on the web site. >>>>>> I will try to make a plugin for X12-997 this weekend. >>>>>> If you look at the plugin for MDN's you will get a good idea of how it >>>>>> works. >>>>>> 997 work quite similar to this.
>>>>>> let me know if this is understandable
>>>>>> kind regards, >>>>>> henk-jan
>>>>>> Mellerbeck wrote:
>>>>>>> I'm a fairly Bots newby so please forgive...
>>>>>>> This is what I am looking to do, I will create an x12 EDI doc >>>>>>> externally. I want to pass this doc through Bots (I'm guessing I need >>>>>>> and incoming and outgoing route for this) into an AS2 service >>>>>>> (basically it will send what ever is dropped into it's outgoing >>>>>>> folder) if it could capture the status of the MDN it would be cool but >>>>>>> not needed.
>>>>>>> Then I would like to receive the 997 and have it matched up to the >>>>>>> sent EDI doc. It looks like confirmations is related to this?
>>>>>>> Thanks for any pointers in the right directions!
My experience is the same, if I see that a Doc has been rejected I will go back to the original and look for errors. If I don't see what the problem is I will contact the receiver to see what the matter is. Thanks for adding this! Thanks also for the passing through of the filename script, I will be using that as well.
-Michael
On Jan 19, 10:23 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> it is quite easy to add, so I will add this. > I use status rejected or not rejected (partially rejected is as rejected).
> I am not sure how this is dealt with in edi practice. > in my experience, if there is an error, contact is needed: what went > wrong, what actions are needed. > when an edi file is rejected, all of the transactions are rejected.
> what is your experience with this?
> kind regards, > henk-jan
> Mellerbeck wrote: > > Thank you for this, one question. How does bots handle if a 997 is > > sent back but a rejection status was sent. This might be a further > > enhancement to not just mark it as confirmed but also take note of > > status? Although it might already I haven't tested :)
> > -Michael
> > On Jan 13, 5:44 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >> Hi Micheal,
> >> I release a plugin for x12/997 confirmations on the bots web site. > >> maybe this is usefull to you.
> >> kind regards, > >> henk-jan
> >> Mellerbeck wrote:
> >>> Could you tell me the name of the field for this reference number? Oh, > >>> I think I have found it, is it Ta.reference?
> >>> I have been able to get fairly close to what I want to accomplish now! > >>> I can pass an EDI doc through BOTs and trigger the confirmation > >>> request!
> >>> Now I just need to experiment with storing the reference number, and > >>> then I want to pass the reference number as part of the file name. It > >>> looks like this (from your previous post) will get me there
> >>> in a mapping script: > >>> import bots.transform as transform > >>> ... > >>> reference = inn.get({'BOTSID':'UNH'}, > >>> {'BOTSID':'BGM','1004':None}) #get the > >>> message ID from incoming messge > >>> out.ta_info['reference']=reference > >>> #messageID is stored as field > >>> 'reference' > >>> in tabel ta > >>> myfilename = 'prefix' + transform.unique('filename') > >>> #the filename is generated > >>> transform.persist_add('contentfilename',reference,myfilename) > >>> #filename is stored in bots database, using a domain, key and value. > >>> #place filename in content etc > >>> ...
> >>> in communication.py I have access to this stored value (in my test I > >>> added this after line 610): > >>> #*************** > >>> import transform > >>> ta_from.syn('reference') #get reference field for > >>> this ta instance > >>> myfilename = transform.persist_lookup > >>> ('contentfilename',ta_from.reference) > >>> #***************
> >>> wish me luck!
> >>> On Jan 11, 2:15 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >>>> Hi Micheal,
> >>>> Mellerbeck wrote:
> >>>>> Thank you henk-jan for the example, I think I am beginning to > >>>>> understand. In order to register a request for a 997 confirmation I > >>>>> would need to create a confirmation rule of ask-x12-997 and assign it > >>>>> to a channel etc.. or just ALL to request for all.
> >>>>> What I am next trying to investigate is if it is possible to display > >>>>> the Identifying number of the EDI document on the confirmation screen.
> >>>> No, bots does not do this yet.> For example if I sent an invoice the BIG line might be
> >>>>> BIG~20100107~1140774~20091230~6099918122* it would pull 1140774
> >>>>> or an 856 it would need to pull BSN~00~1143754~20100108~0816* it > >>>>> would pull 1143754
> >>>>> So it would need to be user definable.
> >>>>> If I could have a column on the confirmation screen with an additional > >>>>> column maybe doc ID then it could be used to verify that a specific > >>>>> doc was received. This is important for accounts payable to verify > >>>>> there invoice has been received.
> >>>>> Doable, or is there a different way to approach this?
> >>>> doable. > >>>> there is a field for something like invoice number, order number (the > >>>> reference to the ERP system for a document). > >>>> the field is filled as defined by the user.
> >>>> the incoming and outgoing views focus upon edi FILES; what you what is a > >>>> view for edi DOCUMENTS. > >>>> this would be a new view (query logic, screen).
> >>>> kind regards, > >>>> henk-jan > >>>> -
> >>>>> Thanks,
> >>>>> Michael
> >>>>> On Jan 8, 6:56 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >>>>>> hi Michael,
> >>>>>> I put a plugin on the web site for MDN-confirmations (called > >>>>>> 'demo_mdn_confirmations'). > >>>>>> Also I added documentation about his on the web site. > >>>>>> I will try to make a plugin for X12-997 this weekend. > >>>>>> If you look at the plugin for MDN's you will get a good idea of how it > >>>>>> works. > >>>>>> 997 work quite similar to this.
> >>>>>> let me know if this is understandable
> >>>>>> kind regards, > >>>>>> henk-jan
> >>>>>> Mellerbeck wrote:
> >>>>>>> I'm a fairly Bots newby so please forgive...
> >>>>>>> This is what I am looking to do, I will create an x12 EDI doc > >>>>>>> externally. I want to pass this doc through Bots (I'm guessing I need > >>>>>>> and incoming and outgoing route for this) into an AS2 service > >>>>>>> (basically it will send what ever is dropped into it's outgoing > >>>>>>> folder) if it could capture the status of the MDN it would be cool but > >>>>>>> not needed.
> >>>>>>> Then I would like to receive the 997 and have it matched up to the > >>>>>>> sent EDI doc. It looks like confirmations is related to this?
> >>>>>>> Thanks for any pointers in the right directions!
just a question...am I right if I remember that you where talking about using edi software from altova? I never used their software (it is supposed to be quite good). are you using bots next to altova or how do you work? I'm also interested in knowing what you 'miss' in bots (of course I am ;-)
Mellerbeck wrote: > My experience is the same, if I see that a Doc has been rejected I > will go back to the original and look for errors. If I don't see what > the problem is I will contact the receiver to see what the matter is. > Thanks for adding this! Thanks also for the passing through of the > filename script, I will be using that as well.
> -Michael
> On Jan 19, 10:23 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>> Hi Michael,
>> for now bots does nothing with status rejected.
>> it is quite easy to add, so I will add this. >> I use status rejected or not rejected (partially rejected is as rejected).
>> I am not sure how this is dealt with in edi practice. >> in my experience, if there is an error, contact is needed: what went >> wrong, what actions are needed. >> when an edi file is rejected, all of the transactions are rejected.
>> what is your experience with this?
>> kind regards, >> henk-jan
>> Mellerbeck wrote:
>>> Thank you for this, one question. How does bots handle if a 997 is >>> sent back but a rejection status was sent. This might be a further >>> enhancement to not just mark it as confirmed but also take note of >>> status? Although it might already I haven't tested :)
>>> -Michael
>>> On Jan 13, 5:44 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>>>> Hi Micheal,
>>>> I release a plugin for x12/997 confirmations on the bots web site. >>>> maybe this is usefull to you.
>>>> kind regards, >>>> henk-jan
>>>> Mellerbeck wrote:
>>>>> Could you tell me the name of the field for this reference number? Oh, >>>>> I think I have found it, is it Ta.reference?
>>>>> I have been able to get fairly close to what I want to accomplish now! >>>>> I can pass an EDI doc through BOTs and trigger the confirmation >>>>> request!
>>>>> Now I just need to experiment with storing the reference number, and >>>>> then I want to pass the reference number as part of the file name. It >>>>> looks like this (from your previous post) will get me there
>>>>> in a mapping script: >>>>> import bots.transform as transform >>>>> ... >>>>> reference = inn.get({'BOTSID':'UNH'}, >>>>> {'BOTSID':'BGM','1004':None}) #get the >>>>> message ID from incoming messge >>>>> out.ta_info['reference']=reference >>>>> #messageID is stored as field >>>>> 'reference' >>>>> in tabel ta >>>>> myfilename = 'prefix' + transform.unique('filename') >>>>> #the filename is generated >>>>> transform.persist_add('contentfilename',reference,myfilename) >>>>> #filename is stored in bots database, using a domain, key and value. >>>>> #place filename in content etc >>>>> ...
>>>>> in communication.py I have access to this stored value (in my test I >>>>> added this after line 610): >>>>> #*************** >>>>> import transform >>>>> ta_from.syn('reference') #get reference field for >>>>> this ta instance >>>>> myfilename = transform.persist_lookup >>>>> ('contentfilename',ta_from.reference) >>>>> #***************
>>>>> wish me luck!
>>>>> On Jan 11, 2:15 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>>>>>> Hi Micheal,
>>>>>> Mellerbeck wrote:
>>>>>>> Thank you henk-jan for the example, I think I am beginning to >>>>>>> understand. In order to register a request for a 997 confirmation I >>>>>>> would need to create a confirmation rule of ask-x12-997 and assign it >>>>>>> to a channel etc.. or just ALL to request for all.
>>>>>>> What I am next trying to investigate is if it is possible to display >>>>>>> the Identifying number of the EDI document on the confirmation screen.
>>>>>> No, bots does not do this yet.> For example if I sent an invoice the BIG line might be
>>>>>>> BIG~20100107~1140774~20091230~6099918122* it would pull 1140774
>>>>>>> or an 856 it would need to pull BSN~00~1143754~20100108~0816* it >>>>>>> would pull 1143754
>>>>>>> So it would need to be user definable.
>>>>>>> If I could have a column on the confirmation screen with an additional >>>>>>> column maybe doc ID then it could be used to verify that a specific >>>>>>> doc was received. This is important for accounts payable to verify >>>>>>> there invoice has been received.
>>>>>>> Doable, or is there a different way to approach this?
>>>>>> doable. >>>>>> there is a field for something like invoice number, order number (the >>>>>> reference to the ERP system for a document). >>>>>> the field is filled as defined by the user.
>>>>>> the incoming and outgoing views focus upon edi FILES; what you what is a >>>>>> view for edi DOCUMENTS. >>>>>> this would be a new view (query logic, screen).
>>>>>> kind regards, >>>>>> henk-jan >>>>>> -
>>>>>>> Thanks,
>>>>>>> Michael
>>>>>>> On Jan 8, 6:56 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
>>>>>>>> hi Michael,
>>>>>>>> I put a plugin on the web site for MDN-confirmations (called >>>>>>>> 'demo_mdn_confirmations'). >>>>>>>> Also I added documentation about his on the web site. >>>>>>>> I will try to make a plugin for X12-997 this weekend. >>>>>>>> If you look at the plugin for MDN's you will get a good idea of how it >>>>>>>> works. >>>>>>>> 997 work quite similar to this.
>>>>>>>> let me know if this is understandable
>>>>>>>> kind regards, >>>>>>>> henk-jan
>>>>>>>> Mellerbeck wrote:
>>>>>>>>> I'm a fairly Bots newby so please forgive...
>>>>>>>>> This is what I am looking to do, I will create an x12 EDI doc >>>>>>>>> externally. I want to pass this doc through Bots (I'm guessing I need >>>>>>>>> and incoming and outgoing route for this) into an AS2 service >>>>>>>>> (basically it will send what ever is dropped into it's outgoing >>>>>>>>> folder) if it could capture the status of the MDN it would be cool but >>>>>>>>> not needed.
>>>>>>>>> Then I would like to receive the 997 and have it matched up to the >>>>>>>>> sent EDI doc. It looks like confirmations is related to this?
>>>>>>>>> Thanks for any pointers in the right directions!
I do use the altova mapforce product. It is very good, it is a visual way of doing translations. For example drag and drop from an XML element to an EDI element also while querying a database for relevant info.
This isn't anything you couldn't do with BOTS but it is very quick to do it in mapforce.
I will be passing an already created edi doc through BOTS (and then on through mendelson AS2). I will be using BOTS primarily to keep track of the EDI docs and whether they have been accepted or not. Eventually, when I get more time I would like to learn how to do the mappings in BOTS but for now this is my workflow.
What I miss from BOTS is an EDI document tracking screen (talked about in a different post) that would show either accepted or rejected at a document level.
I think some simple examples would be very cool as well. Maybe a very simple XML file to flatfile conversion.
An open source visual mapper would of course be excellent (but out of scope at the moment I believe :) There are four that I see out there talend, CloverETL, Pentahoo, and apatar although all of them are not able to do EDI.
Well, those are my thoughts for the moment :)
-Michael
On Jan 19, 4:04 pm, henk-jan ebbers <hjebb...@gmail.com> wrote:
> just a question...am I right if I remember that you where talking about > using edi software from altova? > I never used their software (it is supposed to be quite good). > are you using bots next to altova or how do you work? > I'm also interested in knowing what you 'miss' in bots (of course I am ;-)
> kind regard > henk-jan
> Mellerbeck wrote: > > My experience is the same, if I see that a Doc has been rejected I > > will go back to the original and look for errors. If I don't see what > > the problem is I will contact the receiver to see what the matter is. > > Thanks for adding this! Thanks also for the passing through of the > > filename script, I will be using that as well.
> > -Michael
> > On Jan 19, 10:23 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >> Hi Michael,
> >> for now bots does nothing with status rejected.
> >> it is quite easy to add, so I will add this. > >> I use status rejected or not rejected (partially rejected is as rejected).
> >> I am not sure how this is dealt with in edi practice. > >> in my experience, if there is an error, contact is needed: what went > >> wrong, what actions are needed. > >> when an edi file is rejected, all of the transactions are rejected.
> >> what is your experience with this?
> >> kind regards, > >> henk-jan
> >> Mellerbeck wrote:
> >>> Thank you for this, one question. How does bots handle if a 997 is > >>> sent back but a rejection status was sent. This might be a further > >>> enhancement to not just mark it as confirmed but also take note of > >>> status? Although it might already I haven't tested :)
> >>> -Michael
> >>> On Jan 13, 5:44 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >>>> Hi Micheal,
> >>>> I release a plugin for x12/997 confirmations on the bots web site. > >>>> maybe this is usefull to you.
> >>>> kind regards, > >>>> henk-jan
> >>>> Mellerbeck wrote:
> >>>>> Could you tell me the name of the field for this reference number? Oh, > >>>>> I think I have found it, is it Ta.reference?
> >>>>> I have been able to get fairly close to what I want to accomplish now! > >>>>> I can pass an EDI doc through BOTs and trigger the confirmation > >>>>> request!
> >>>>> Now I just need to experiment with storing the reference number, and > >>>>> then I want to pass the reference number as part of the file name. It > >>>>> looks like this (from your previous post) will get me there
> >>>>> in a mapping script: > >>>>> import bots.transform as transform > >>>>> ... > >>>>> reference = inn.get({'BOTSID':'UNH'}, > >>>>> {'BOTSID':'BGM','1004':None}) #get the > >>>>> message ID from incoming messge > >>>>> out.ta_info['reference']=reference > >>>>> #messageID is stored as field > >>>>> 'reference' > >>>>> in tabel ta > >>>>> myfilename = 'prefix' + transform.unique('filename') > >>>>> #the filename is generated > >>>>> transform.persist_add('contentfilename',reference,myfilename) > >>>>> #filename is stored in bots database, using a domain, key and value. > >>>>> #place filename in content etc > >>>>> ...
> >>>>> in communication.py I have access to this stored value (in my test I > >>>>> added this after line 610): > >>>>> #*************** > >>>>> import transform > >>>>> ta_from.syn('reference') #get reference field for > >>>>> this ta instance > >>>>> myfilename = transform.persist_lookup > >>>>> ('contentfilename',ta_from.reference) > >>>>> #***************
> >>>>> wish me luck!
> >>>>> On Jan 11, 2:15 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >>>>>> Hi Micheal,
> >>>>>> Mellerbeck wrote:
> >>>>>>> Thank you henk-jan for the example, I think I am beginning to > >>>>>>> understand. In order to register a request for a 997 confirmation I > >>>>>>> would need to create a confirmation rule of ask-x12-997 and assign it > >>>>>>> to a channel etc.. or just ALL to request for all.
> >>>>>>> What I am next trying to investigate is if it is possible to display > >>>>>>> the Identifying number of the EDI document on the confirmation screen.
> >>>>>> No, bots does not do this yet.> For example if I sent an invoice the BIG line might be
> >>>>>>> BIG~20100107~1140774~20091230~6099918122* it would pull 1140774
> >>>>>>> or an 856 it would need to pull BSN~00~1143754~20100108~0816* it > >>>>>>> would pull 1143754
> >>>>>>> So it would need to be user definable.
> >>>>>>> If I could have a column on the confirmation screen with an additional > >>>>>>> column maybe doc ID then it could be used to verify that a specific > >>>>>>> doc was received. This is important for accounts payable to verify > >>>>>>> there invoice has been received.
> >>>>>>> Doable, or is there a different way to approach this?
> >>>>>> doable. > >>>>>> there is a field for something like invoice number, order number (the > >>>>>> reference to the ERP system for a document). > >>>>>> the field is filled as defined by the user.
> >>>>>> the incoming and outgoing views focus upon edi FILES; what you what is a > >>>>>> view for edi DOCUMENTS. > >>>>>> this would be a new view (query logic, screen).
> >>>>>>> On Jan 8, 6:56 am, henk-jan ebbers <hjebb...@gmail.com> wrote:
> >>>>>>>> hi Michael,
> >>>>>>>> I put a plugin on the web site for MDN-confirmations (called > >>>>>>>> 'demo_mdn_confirmations'). > >>>>>>>> Also I added documentation about his on the web site. > >>>>>>>> I will try to make a plugin for X12-997 this weekend. > >>>>>>>> If you look at the plugin for MDN's you will get a good idea of how it > >>>>>>>> works. > >>>>>>>> 997 work quite similar to this.
> >>>>>>>> let me know if this is understandable
> >>>>>>>> kind regards, > >>>>>>>> henk-jan
> >>>>>>>> Mellerbeck wrote:
> >>>>>>>>> I'm a fairly Bots newby so please forgive...
> >>>>>>>>> This is what I am looking to do, I will create an x12 EDI doc > >>>>>>>>> externally. I want to pass this doc through Bots (I'm guessing I need > >>>>>>>>> and incoming and outgoing route for this) into an AS2 service > >>>>>>>>> (basically it will send what ever is dropped into it's outgoing > >>>>>>>>> folder) if it could capture the status of the MDN it would be cool but > >>>>>>>>> not needed.
> >>>>>>>>> Then I would like to receive the 997 and have it matched up to the > >>>>>>>>> sent EDI doc. It looks like confirmations is related to this?
> >>>>>>>>> Thanks for any pointers in the right directions!
|
