Trade Partner Management in EDIConnect

EDIConnect is a complete solution for accurate and efficient bi-directional EDI data integration. It offers EDI data integration capability in an intuitive user interface with visual tools to build bi-directional integration. This blog will discuss how to set up a trade partner relationship in EDIConnect, including how to define incoming and outbound condition maps, how to define separators for the segment elements, and how to customize standards and use them inside the trade partner definition.

First, let’s review the EDIConnect process for receiving and sending messages.

1_EDI1

You define your trade partner and specify the settings to receive incoming messages.

Once you receive the message, it goes into the system, where you can validate it and generate acknowledgements such as X12, 997, and 999 or Tier One.

Now let’s take a closer look at the process for defining a trade partner and specifying the settings to receive incoming messages.

Begin by creating a new trade partner. Go to file/new and click on EDI Trade Partner Profile.

2_EDI1

In the screen, you can specify the partner name and also specify your settings, inbound maps, outbound maps, and sequences.

3_EDI1

Let’s look at these options one by one.

First, select the dialect for the partner, in this case X12.

4_EDI1

Within the X12 settings, you can specify information for the interchange headers, functional groups, validation settings, and acknowledgement.

5_EDI1

Within the Functional Group you can specify GS properties as shown below.

6_EDI1

Similarly, for Interchange Header you can specify all ISA properties, as well as separators for your data elements, as shown below.

7_EDI1

For the validation settings, you can specify what should be validated when a message is received for the partner.

8_EDI1

You can specify acknowledgements such as what kind of acknowledgement you want to convey when the messages arrive, such as FunctionalAckTransactionSet, GenerateAk2ForAcceptedTransactionSet, or SendTechnicalAcknowledgement.

9_EDI1

Now we’ll move on to how to specify inbound maps. This is where you specify how specific transactions from the partner are treated and how many you are expecting from that partner. For example, from this partner I am expecting only 850 transactions.

10_EDI1

So I’m going to add one 850 as an incoming transaction set and specify how I want it to be processed in the system. You can have a standard 850 or you can have a customized version of it. In the case of a customized version, you will pick your customized 850 version as a mapping so that when the messages arrive the customized information is used to process that message.

11_EDI1

Similarly, for outbound messages you specify what maps you are going to send out to this partner and if there is any customization, in which case you map the standard message to the customized message in the customization window as shown below.

12_EDI1

Now we’ll move on to sequences. All the sequence generation for this EDI partner is controlled by the properties specified in this tab.

13_EDI1

Here you specify where your sequence object resides, your database information, and your functional group control numbers, interchange control numbers, and conditions of control numbers.

Now that you know how to set up a trade partner relationship, our next blog will show you how to use the EDI builder and EDI destination file in EDIConnect.