I'm using biztalk 2004, and covast edi accelerator.

I have 2 different types of documents that have to come into the
same receive location, since you can't have more than 1 per partner.

So.. I have 1 map that translates an 810 to xml.
And, 1 map that translates an 855 document to xml.

These documents will go to different file locations to be processed.

Will biztalk understand which map to use, if I put them both on the receive
location?
Or should I create 2 send ports... Each with a different map... then Filter
on
the Receive Port, and a promoted document type?
Will the 2nd scenario even work?

[ Post a follow-up to this message ]

Scot hi,

I don't understand what you've described on that second scenario as receive
ports have no filter.
You might have meant performing the mapping in the send port for which you
can set subscription to help you.

However, while I did not use the Covast EDI Accelerator, I can tell you that
if in the pipeline the messages are assigned different message type by the
disassembler and you have added two maps, each one uses a different one of
these message types as input then you can use the same port and the correct
map will be invoked.

Hope this helps

Yossi Dahan




"Scot S" <ScotS@discussions.microsoft.com> wrote in message
news:33CB2E99-6F3D-4CC8-B9BE-568F776BE593@microsoft.com...
> I'm using biztalk 2004, and covast edi accelerator.
>
> I have 2 different types of documents that have to come into the
> same receive location, since you can't have more than 1 per partner.
>
> So.. I have 1 map that translates an 810 to xml.
> And, 1 map that translates an 855 document to xml.
>
> These documents will go to different file locations to be processed.
>
> Will biztalk understand which map to use, if I put them both on the
> receive
> location?
> Or should I create 2 send ports... Each with a different map... then
> Filter
> on
> the Receive Port, and a promoted document type?
> Will the 2nd scenario even work?

[ Post a follow-up to this message ]

A single receive location can receive more than one type of EDI documents.
I am guessing that you have two orchestraions for each EDI type, so Biztalk
will route the document to correct the orchestration base on the receive
port and schema type (EDI document), and your orchestration can specify
different send ports, then different documents will send to different file
locations.

Benson.

"Scot S" <ScotS@discussions.microsoft.com> wrote in message
news:33CB2E99-6F3D-4CC8-B9BE-568F776BE593@microsoft.com...
> I'm using biztalk 2004, and covast edi accelerator.
>
> I have 2 different types of documents that have to come into the
> same receive location, since you can't have more than 1 per partner.
>
> So.. I have 1 map that translates an 810 to xml.
> And, 1 map that translates an 855 document to xml.
>
> These documents will go to different file locations to be processed.
>
> Will biztalk understand which map to use, if I put them both on the
receive
> location?
> Or should I create 2 send ports... Each with a different map... then
Filter
> on
> the Receive Port, and a promoted document type?
> Will the 2nd scenario even work?

[ Post a follow-up to this message ]

Here's my scenario.
Any edi documents I get in, I want to convert to XML...
Then, have another project pick up the xml... and feed it to the database.

So...
I've got a receive location, where I have a 2 inbound maps.
One map would be for the 810... the other for the 855.
Then..
I would have two different send ports, going to a file location.
Each, send port would be tied to the receive port thru a filter.
The XML files would be sent to different directories.

Is biztalk smart enough to use the correct inbound map?
And...
Will I have to promote a property, and check for it
on the filter... in order for the send port to actually pick
up the correct xml file?
I don't want the same xml file going to both send ports.
I want the 810's to go to one directory, and 855's to another

I hope this makes sense.

"Benson Cheng" wrote:

> A single receive location can receive more than one type of EDI documents.
> I am guessing that you have two orchestraions for each EDI type, so Biztal
k
> will route the document to correct the orchestration base on the receive
> port and schema type (EDI document), and your orchestration can specify
> different send ports, then different documents will send to different file
> locations.
>
> Benson.
>
> "Scot S" <ScotS@discussions.microsoft.com> wrote in message
> news:33CB2E99-6F3D-4CC8-B9BE-568F776BE593@microsoft.com... 
> receive 
> Filter 
>
>
>

[ Post a follow-up to this message ]

Scot,

What I understand from you description is that you have one receive port for
a particular EDI partner and that port will receive 2 different documents. A
n
810 and an 855. You have maps on that receive port to translate the 810 and
the 855 respectively. I would think you are receiving X12-810 and an X12-855
into that port? What are you mapping to?

1. BizTalk will execute the correct map because as a previous person
responded the document will hit the pipeline and as long as the pipeline
recognizes the document type (e.g. as an X12-810) then when it gets to the
lists of maps available on the port it will match the document to the correc
t
map.

2. If you promote a field from both the 810 and 855 post-mapping messages
(you did not indicate what you are mapping to) then this promoted field can
be used in a send port to help filter. So in your scenario you would have 2
send ports. One send port would have a filter like"receive port =
<yourreceive port> AND <promoted property> = <value for 810>" and the second
send port would have a filter like "receive port = <yourreceive port> AND
<promoted property> = <value for 855>"

This should work.

Dean

"Scot S" wrote:
[vbcol=seagreen]
> Here's my scenario.
>     Any edi documents I get in, I want to convert to XML...
> Then, have another project pick up the xml... and feed it to the database.
>
> So...
>      I've got a receive location, where I have a 2 inbound maps.
> One map would be for the 810... the other for the 855.
> Then..
>     I would have two different send ports, going to a file location.
> Each, send port would be tied to the receive port thru a filter.
> The XML files would be sent to different directories.
>
> Is biztalk smart enough to use the correct inbound map?
> And...
> Will I have to promote a property, and check for it
> on the filter... in order for the send port to actually pick
> up the correct xml file?
> I don't want the same xml file going to both send ports.
> I want the 810's to go to one directory, and 855's to another
>
> I hope this makes sense.
>
> "Benson Cheng" wrote:
> 

[ Post a follow-up to this message ]

That's the approach I ended up taking...
Looks like that will work for me.  Thanks for all your help

"Dean Cyril Wood" wrote:
[vbcol=seagreen]
> Scot,
>
> What I understand from you description is that you have one receive port f
or
> a particular EDI partner and that port will receive 2 different documents.
 An
> 810 and an 855. You have maps on that receive port to translate the 810 an
d
> the 855 respectively. I would think you are receiving X12-810 and an X12-8
55
> into that port? What are you mapping to?
>
> 1. BizTalk will execute the correct map because as a previous person
> responded the document will hit the pipeline and as long as the pipeline
> recognizes the document type (e.g. as an X12-810) then when it gets to the
> lists of maps available on the port it will match the document to the corr
ect
> map.
>
> 2. If you promote a field from both the 810 and 855 post-mapping messages
> (you did not indicate what you are mapping to) then this promoted field ca
n
> be used in a send port to help filter. So in your scenario you would have 
2
> send ports. One send port would have a filter like"receive port =
> <yourreceive port> AND <promoted property> = <value for 810>" and the seco
nd
> send port would have a filter like "receive port = <yourreceive port> AND
> <promoted property> = <value for 855>"
>
> This should work.
>
> Dean
>
> "Scot S" wrote:
> 

[ Post a follow-up to this message ]