Biztalk EDI mapping

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.
[b:f69c076ace]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.[/b:f69c076ace]
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: