What do i like Most in 11g - TP cloning

This feature can be used only if there is a need to create a trading partner for a similar business use case as the existing one.

e.g consider a retail use case with host as Acme and trading partner as Globalchips and Globalcorp. Host is buying electronics from GlobalChips and Apparels from Globalcorp exchanging Order/Invoice/Advance Shipment messages using EDI Document protocol. Globalcorp can be created by cloning the Globalchips


TP cloning would enable the Admin to create a TP based on an existing Trading partner, with the same set of document definition and the delivery channels. This would not copy Identifiers,contact information, users etc. as these are specific to Trading partner

Changes to be done after cloning, if there is any.

1. Document Definition

a. Override Version Param b. Override Version Param - Refer B2B guide for more details.

Please note that it is not possible to change the xsd and ecs. For any user specific document definition e.g xsd, ecs changes it is required to create the corresponding definition as Admin, and the same has to be used in the trading partner after deleting the earlier definition. Conventiaonally it is a good practice to add the trading partner name as part of the definition name in the admin section.

2. Delivery Channel

Update the end point specific to trading partner and also the naming convention for the channel as per the cloned trading partner. Please note that MLLP channels are excluded from cloning.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

To Discover and discuss the capability of B2B in the world of Trading Partner Integration. This blog is primarily intended to share thoughts on Oracle B2B Product and to share best practices in performance, scalability and various topologies.

Search

Archives
« May 2015
SunMonTueWedThuFriSat
     
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
      
Today