Biztalk EDI mapping

I am having some problems mapping and wondered if anyone had any ideas. I am using the standard 850 schema that comes with biztalk, and have a schema for an xml output file, and I have a map set up, and some of the fields mapped.. I have that working, but I need to get to the ISA record in the inbound 850, and it isn't in the schema. I really need to map the partner id (ISA06) to a field in my xml schema, but I can't seem to get to it. Any ideas ? I've been scouring the web for the past couple of days, and am finding nothing.

Hello.

I do not have a lot of experience with EDI.

But, maybe you could do your mapping inside an Orchestration and use a 2nd message on the input of the map with the partner id?

Don’t know if that help you out.

I used covast edi for biztalk a lot.

The incoming 850 is translated to xml by covast edi accelerator.
I have seen the header for the ISA and it has the partner id (sender).

You are using base EDI biztalk right?
Maybe the base edi don't have it. In the Covast EDI schema, there is a thing called CovastEnvelope

Look for it even if you are using the base EDI.

If not, then go to Covast website and send an email and ask. They wrote the Base EDI too.

Base Edi does not have this information.
You should use full Covast EDI Accel.
http://support.microsoft.com/default.aspx?scid=kb;en-us;840113
Here is a quote from Microsoft on Base EDI limitation (Covast wants you to buy the full version:))
Miscellaneous EDI schema limitations
• No floating segment support. This limitation is the same as in Microsoft BizTalk Server 2002.
• Very limited binary segment support. This limitation is the same as in BizTalk Server 2002.
• EDI Envelope data is not conveyed on the inbound. Therefore, the data is not available for use in the BizTalk Mapper or in orchestrations. This limitation is the same as in BizTalk Server 2002.
• EDI Envelope layouts cannot be customized or modified. This limitation is the same as in BizTalk Server 2002.
• The list of supported X12 Functional Group Identifiers is fixed according to the 4050 version. This means you cannot use transaction sets that were introduced after the 4050 version, because the system does not know which functional group identifier belongs to it (because that is not part of the schema).
• The EDI Annotation <b:RecordInfo count_ignore=\"yes\"> is ignored by the Base EDI Adapter. The Base EDI Adapter uses hard-coded technology to count the segments in EDI transactions.
• The BizTalk Server 2004 Base EDI Adapter uses stricter EDI character set validations than BizTalk Server 2002. For example, when an EDIFACT UNOA interchange is received, it will validate the characters in the interchange according to the defined character set that belongs to the UNOA syntax (which is a subset of ISO-646).
For additional information, click the following article number to view the article in the Microsoft Knowledge Base: