Oracle® Application Server Integration B2B User's Guide
10g Release 2 (10.1.2.0.2) B19370-01 |
|
Previous |
Next |
If trading partners are using a value-added network (VAN) with EDI EDIFACT or EDI X12, then, to use the ISA/GS identifier, add the following property in tip.properties
. This property specifies how the sending trading partner of incoming messages is identified.
oracle.tip.adapter.b2b.edi.identifyFromTP = Interchange | Group | Exchange
You have the following ways to identify the sending (from) trading partner:
Interchange Sender ID—UNB for EDIFACT AND ISA 06 FOR X12
Application's Sender Code—UNG for EDIFACT and GS 02 for X12
Exchange Protocol identification (default)
For Trading Partner Identification Type, use one of the following types:
EDI Interchange ID
EDI Group ID
Create a new Trading Partner Identification for the target trading partner with the corresponding EDI sender value for the Interchange or Group envelope. Specifically, you must create one EDI Interchange ID for the host trading partner and one EDI Interchange ID for the remote trading partner. For the incoming message, the host trading partner is the receiving trading partner and the remote trading partner is the sending trading partner.