- This topic has 12 replies, 1 voice, and was last updated 8 years ago by
.
-
Posts
-
-
This is the error shown in the Covast EDI Accelerator 2006 Reports.
I have the sender party alias defined and I have the recipient party alias defined as EDI://MAGATT:ZZ
Covast tells me I only need the sender party alias defined. Which is it, do I need both sender and recipient party alias defined?
Here is the complete error:
recipient: [] [MAGATT][ZZ][MAGATT], source format: [5 00401 ,X12-4010]
source document: [unknown]
source segment: [data#0,def#0,tag=GS , name=unknown] (msgnr:0 segnr:0)(line:0 pos:153 filepos:153)Possible referenced error: The recipient of the document cannot be found.
Possible Cause: The recipient’s EDI address is not defined in the BizTalk party information..
Possible Solution: Make sure a party is defined for the recipient with a proper EDI alias. The format of the EDI alias value should be \”EDI://<identification>:<identification code qualifier>:<routing address>. -
Here’s some more information. These are EDI 811 headers of two documents, one gives an error, the other does not.
Gives error \”The recipient of the document isn’t recognized\”:
ISA~00~ ~00~ ~01~619448418 ~ZZ~MAGATT ~060512~1027~U~00401~000001074~0~P~>
GS~CI~AT&T-CBS/VTN~MAGATT~20060512~1027~1074~X~004010
ST~811~10740125
BIG~20060511~0901435660~~~~~DR
No error, same sender as the other document:
ISA~00~ ~00~ ~01~619448418 ~01~CDHFVTNS ~050911~0526~U~00401~000001051~0~P~>
GS~CI~AT&T-CBS/VTN~CDHFVTNS~20050911~0526~1051~X~004010
ST~811~10510001
BIG~20050911~0793106473~~~~~CD
-
Covast is telling me that I don’t need the recipient and if I have only the sender it works for one document.
The failing document doesn’t work if I have both sender and recipient. I set:
Sender: EDI://619448418:01:
Recipient: EDI://MAGATT:ZZ:-
I have found Microsoft BizTalk documentation that tells me to set up a Party Alias for both sender and recipient. It also says to use \”EDI\” in name and qualifier field.
I have done all that but still get the error \”The recipient of the document isn’t recognized\”.
I don’t know what steps to take to track this down. Any suggestions on what else I have to do?
-
This is how I have it configured now:
Sender for both documents:
Name: EDI Qualifier: EDI Value: EDI://619448418:01:AT&T-CBS/VTNRecipient 1, Document 1:
Name: EDI Qualifier: EDI Value: EDI://CDHFVTNS:01:CDHFVTNSRecipient 2, Document 2:
Name: EDI Qualifier: EDI Value: EDI://MAGATT:ZZ:MAGATTIs there something here that you see is a problem and if so, how would I correct it?
-
Here’s the bird’s eye view. I have a single Receive Location. This is a File Transport Type using the CovastEDIReceivePipeline. In this location is dropped an EDI 811 file. We are processing 811 documents for multiple customers so the Recipients can be multiple. I have been trying to get this to work with just one Recipient, but there will be more.
An Orchestration calls a Mapping which converts this document to XML. The XML is sent to a Send Port, which is another File Transport Type using the XML Transmit Send Pipeline.
Once the file is dropped in the Send Port it is processed by a windows service that imports it into a database.
-
Thanks a lot, that got me going. What’s confusing is there is the Covast Trading Partner Management and the BizTalk Parties which have different values in them. Also the EDI Adapter Send Properties I set the EDI Address to EDI://:: I don’t know if this is necessary or right but it works.
-
You have to have two diferent parties configured. One with the receive identification, the other with the sender identification.
You probably have the sender id wrong.
-
[quote:5229962d2d=\”nickka\”]Covast is telling me that I don’t need the recipient and if I have only the sender it works for one document.
The failing document doesn’t work if I have both sender and recipient. I set:
Sender: EDI://619448418:01:
Recipient: EDI://MAGATT:ZZ:[/quote:5229962d2d]That is strange, on the contact I’ve been having with EDI files (EDIFACT), I always need two parties configured. One as a receive and the other as a sender.
But, is your problem solved?
-
[quote:92ba16e9cf=\”nickka\”]I have found Microsoft BizTalk documentation that tells me to set up a Party Alias for both sender and recipient. It also says to use \”EDI\” in name and qualifier field.
I have done all that but still get the error \”The recipient of the document isn’t recognized\”.
I don’t know what steps to take to track this down. Any suggestions on what else I have to do?[/quote:92ba16e9cf]
have you set up a PARTY sender and receiver with equivalent adress to sender and recipient adress… (in biztalk explorer)
you also need to configure your edi adapter in biztalk administrator consol / … / adapters / edi:
the send port needs edi adress and port no
receive port only needs port no …-
-
ok… forget about biztalk for a minute.
lets talk covast…all this is done through the covast pipeline component, covast envelope or through context properties of the file.
yes, you dont need a recipient address IFF covast can find it elsewhere. that is, in the envelope (if it originates as an XML) or in the context, if you are doing it dynamically.
That way, in your pipeline configuration, leave the recipient URI blank and just set the sender.
Mind you, you do need to have all the parties configured. I suggest using the Covast administration to add parties and party aliases. I personally have a recipient party for each business application. within these, i have different aliases for each trading party. Within that, you can define the particular element delimiter (in your case its not default(*) its ~) but also the document you want ( an 811 in your case )
If you could, send me the scenario that you are trying to do in particular. you seem to be recieving an EDI file, in which you are configured as several recipients (??) are you then routing them along or saving them somewhere? if you could post a birds eye view of the scenario it would be very helpful
-
ok that seems pretty standard.
go ahead and type in EDI:\\\\:: ( a catch all URI for edi) inside your recieve pipeline. This will correspond to an alias within your party and basically acts like a * ( in file masks for example ) for any other party alias within that party. ** this is what covast means when they say that the sender URI is the only required one. **note**** depending on the build you are using 1.03, 1.07 or 1.20 this may or may not work. if it doesnt work, then delete that all together from your pipeline config and just leave it blank… it will basically substitute whichever party you have configured in biztalk that comes in that file.
from the descriptions that you have given (one working and the other not) i would say that you have that particular party in the pipeline config, hence, one works and the other doesnt. but everything else youve provided, included the samples, seem to be in order.
-
-
-
-
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.