AutoForward Implications

With AutoForwarding, the data flows as follows between trading partners. PartnerA sends to PartnerB. OpenText then AutoForwards the data from PartnerB to PartnerC. In this scenario, before an AutoForward partnership is set up, there must be active trading partnerships between

PartnerA and PartnerB

PartnerB and PartnerC

Based on this scenario described:

When data is AutoForwarded from PartnerB to PartnerC, PartnerC sees the data coming from PartnerB, not PartnerA.

When PartnerA sends an interchange to PartnerB, PartnerA's address is in the sender's position of the interchange header, and PartnerB's address is in the receiver's position.

When OpenText AutoForwards the data, PartnerB's address is placed in the sender position of the interchange header and PartnerC's address is placed in the receiver position. This is because Partner A did not send to PartnerC; PartnerB did. Therefore, the data received by PartnerC must show that PartnerB sent it.

OpenText sends a copy of the interchange from Partner B to PartnerC. Most likely PartnerC creates a Functional Acknowledgment (or control message) and sends it back to PartnerB. Unfortunately, since PartnerB's EDI Translator software did not send the original document to PartnerC, it does not know how to reconcile the FA.

It is OpenText policy that after data is put on the network it becomes the property of the receiver. Therefore, only the original receiver (PartnerB) can request an AutoForward partnership.

Both senders and receivers can set up AutoForwarding partnerships.

Note: For an AutoForwarding partnership established by the sender on the sender's account, Trading Grid Online does not inform the receiver about the partnership, and vice versa.

16.2 release. Updated October 23, 2016 Trading Grid Online User Guide PDF

Copyright © 2016 Open Text. All rights reserved. Trademarks owned by Open Text.