- This topic has 6 replies, 1 voice, and was last updated 8 years, 4 months ago by
.
-
Posts
-
-
I understand that BT (2006) ignores or strips off the envelope information(ISA and GS segments) from EDI documents when they are picked up. Can anyone confirm this and is there a way to access this document meta-data at any point so that I can direct the various document types to different process streams within my orchestration(s)? I have one FTP pickup site for all documents and all customers/vendors… I need to be able to utilize the envelope information to determine what map to send it to etc…
thank you for any information you can provide.
-
Anonymous,
This "stripping off" is called parsing, and the translator breaks the EDI document into each ST-SE as it transforms them from EDI to their XML representation.
You can select fields to carry across into "property bag", which goes along side each individual ST-SE transaction from the batch and it is available to allow the document to be "routed" via the publish-subscribe mechanism. So you make receive ports that subscribe to the flow of particular transactions on an arbitrary basis. These ports are then linked to maps.
– weak architect
-
Mr. Weak Architect
I dont suppose you could clue me in on where I might get more information on the 'selection of these fields to carry across'…or better yet examples of utilizing 'property bags' with EDI? Just looking for a starting point… Biztalk help was less than specific when executing a search
– AS400 RPG programmer being converted to Biztalk specialist (long way to go!!!)
-
-
Hi!
Promoting properties doesn't seam to be supported in the base EDI adapter. At least that's my experience,
if anyone has managed to promote properties with the base EDI adapter successfully I would be very happy to learn
how you did…
Routing failed messages doesn't seam to work either with this base EDI adapter. Failed EDI messages doesn't seam to be published to the
messageboxDB…
-
Hi all – Here is the super secret trick for using a CorrelationSet to promote context properties.
http://blogs.msdn.com/dhtoran/archive/2005/07/07/436395.aspx
Enjoy!
– Weak Architect
-
-
-
-
-
Here is the sample location:
C:\Program Files\Microsoft BizTalk Server 2006\SDK\Samples\EDI\MessageEnrichment
It is an orchestration that binds the header information to the split files as an “Enriched Message”
FYI: It failed to install for me because of trust permissions. I had to manually created the ports and filters, then it worked.
-weak architect
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.