EDI party resolution in BizTalk r2

Biztalk can be used for EAI or B2B. For EAI, It is an information hub or bus within an enterprise. For B2B, it is equivalent to an external gateway of the enterprise. Different partowners have different platforms, standards, and settings. Therefore, in addition to integration, BizTalk also needs to manage these contracts and metadata.

Assume that enterprise A uses EDI for integration and information exchange with different upstream and downstream companies. How many questions does EDI often ask?

• Which version does this enterprise use? EDI has many versions. Corresponding to BizTalk, which Schema should be used to explain after I receive the enterprise's EDI?
• Use X12 or EDIFACT
• Do you want to handle the double posting problem.
• Batch inbound/outbound processing.
• ACK or not
• File format, for example, Cr or CRLF.

In the face of this problem, the EDI of BizTalk R2 is implemented through a new party identification mechanism.

Each party has specific settings for the above issues. Biztalk applies the setting of this party by setting another party.

Let's take a look at the typical EDI header.

ISA * 00 ** 00 ** 01 * FedEx * ZZ * montaque * 070607*1555 * u * 00401*000000025*0 * T *> ~

The IS5-6 actually says who the sender is? For example, * 01 * FedEx

* ZZ * montaque * indicates who to send it. Because a company may have different subsidiaries. The following section details the version 00401.

Biztalk's party recognition is based on the two information. First, check whether there is a party setting that matches the sender and receiver completely.

If the match exists, use the settings of the party. The above shows that we have a party named FedEx. Its sending and receiving exactly match. Set the default schema to parse EDI.

Generally, the targetnamespace of a party is the same. For different files, 810 or 850 is used for detailed cropping.

Then, if the sender and receiver do not match exactly. We may only specify sender, and the receiver is empty. At this time, it is suitable for a company with multiple subsidiaries. When vendor sends it to you, BizTalk serves as the gateway to ignore these differences.

If we want multiple sender from different companies, use the same set of settings. Then you can set qualifiedname

If none of these are done, the system uses global setting by default.

How do I know the received message so that party? Once a message is parsed into a specific party, the message will have a promotedproperty called partyname, as shown in. If none of them are hit, it is displayed as a guestparty.

R2 EDI is largeProgramDepends on the party settings. Including as2. So learn about this party ParsingAlgorithmImportant.

 

The above mentioned is to accept EDI from the partner. In Party setting, it is called sender setting.

What if it is sent?

How do I know which party should I use to send the settings to the vendor?

This is exactly the opposite. You need to promote partyname in the system. If there is no party, the global executor setting will be used.

The sender and receiver here are relative to BizTalk. Sender indicates that a partner sends a message to BizTalk. Biztalk actually accepts messages. The IS5-8 at this time is to identify the party.

The receiver indicates that a partner needs to add BizTalk messages. Biztalk sends a message to him. The IS5-8 at this time is to develop the head on EDI.