Oracle AS B2B provides Identification of Trading partner at various levels.
1. Exchange level : This is the default identification based on the exchange Identifier. For e.g if the Exchange protocol used is AS2, then AS2 identifier i.e AS2-FROM is used for identification by comparing against the AS2 Identificer of the Trading partner.
2. Interchange/Group
This is a latest enhancement in B2B where in the identification happens in the order of sequence. Ideally it should be Exchange, Interchange and group. Currently B2B has facility to turn on TPIdentification based on Interchange or Group. This can be done by setting property in tip.properties
Example:
oracle.tip.adapter.b2b.edi.identifyFromTP=Interchange
OR
oracle.tip.adapter.b2b.edi.identifyFromTP=Group
If property is set to Interchange, B2B tries to identify TP using Interchange and if property is set to Group, B2B tries to identify TP using Group.
3. Trading partner Identification Any (newly Added)
If property is set to ANY, B2B will first try to identify TP using Interchange. If no TP found using Interchange, B2B will next try to find TP based on Group.
Example:
oracle.tip.adapter.b2b.edi.identifyFromTP=Any
Sunday, August 26, 2007
Trading Partner Identification in EDI Domain
Posted by Ramesh Nittur at 8:27 AM
Labels: EDI, TP-Identification
Subscribe to:
Post Comments (Atom)
3 comments:
Very informative article.
Exactly what I needed. :)
Thanks
Pär
Very Informative
Thanks and Regards
Sahil
Post a Comment