B2B Gateway

Back Next

Partner interchange IDs

B2B Gateway

adds a partner interchange ID to all EDI X12 and EDIFACT messages, including outgoing acknowledgments.

In inbound messages,

B2B Gateway

adds the ID as the interchange sender ID. In outbound messages,

B2B Gateway

adds the ID as the interchange receiver ID. In acknowledgments,

B2B Gateway

returns the interchange sender ID that it received in the message that it acknowledges.

When you create a partner, you need to define at least one type of partner interchange ID. You can define an interchange production ID, an interchange test ID, or both.

To identify segments within the partner organization, you can define multiple partner interchange production IDs and multiple interchange test IDs. For example, define an ID for each department in the partner organization that you exchange EDI X12 and EDIFACT messages with. You can define up to 50 interchange production IDs and 50 interchange test IDs for a partner.

If you define multiple interchange IDs of the same type for a partner, you must pass the interchange ID to use in outbound flows as a parameter in the process-from-backend mapping that you assign to the partner, so that

B2B Gateway

can determine which partner interchange ID to use in outbound flows. You add the ID to the source that contains the message details and map it to the appropriate field in the mapping target.

For more information, see Creating a process-from-backend mapping for outbound EDI message flows.

B2B Gateway

can't determine which partner interchange ID to use in outbound flows, it can't run outbound flows and the flows fail.

B2B Gateway

can't determine which partner interchange ID to use if you don't define an interchange ID in the mapping when the partner interchange IDs have one of the following configurations:

Multiple IDs are defined for both the interchange production ID and the interchange test ID.

Multiple IDs are defined for one type of interchange ID and the other type of the interchange ID isn't defined. For example, if you define multiple IDs for the interchange production ID and don't define the interchange test ID.

B2B Gateway

passes the sender interchange ID and qualifier to the target of the mapping which runs the inbound flow that receives the message. If you use a process-to-backend mapping in the inbound flow, you can map the sender interchange ID and qualifier from the mapping source to the backend target.

EDI X12 and EDIFACT Messages

Download Guide

Watch

Comments

Cloud B2B Gateway Homepage