webMethods step by step creation of Trading Partner Agreement
Feb 07, 2012 15:29 0 Comments B2B Neelima


Task: Creation of Trading Partner Agreement

OS: WindowsOS

Platform: webMethods 6.1


                                      Trading Partner Agreement(TPA):


Optionally, you can define trading partner agreements for pairs of partners. Each TPA contains specific information for two trading partners, where one partner represents a sender and the other represents the receiver. You can create applications that use TPA information to tailor how documents are exchanged.


Each TPA must have a unique combination of the following:


Partner that represents the sender

Partner that represents the receiver

Type of TPA, represented by the "Agreement ID"


TPA field TPA1 TPA2
Partner that represents the sender A B
Partner that represents the receiver B A
Type of TPA(Agreement ID) EDITPA EDITPA


Note:  Trading Networks does not use TPAs when determining the processing rules to use for a document.  Rather the parameters that you specify in the TPA are available purely for your  own use.


           For TPA set the below parameters.Give the Agreement id As uniqe.Set the same TPA profile between both sender and receicver TN Console.


The TPA data that contains the application‐specific variables to use to tailor the processing of documents exchanged between the sender and receiver. You specify this data by defining an IS document type that defines the structure of the data to provide.

You supply values for the variables defined by the IS document type. For example, the webMethods EDI Module ships with an IS document type (the wm.b2b.editn.TPA:EDITPA IS document type) to use for TPAs for partners exchanging EDI documents.  This IS document type contains a set of variables that are used for processing EDI documents.



TPA Status:

TPAs have two types of statuses—agreement status and data status.

1 Agreement status. Indicates the status of the TPA agreement between the receiver and sender. There are three TPA agreement statuses.

- > Proposed

When the agreement status is Proposed, a TPA is in a draft status. You do most of the  modification to the TPA fields and data input in this Proposed state(design time).

->  Agreed

An Agreed status means that the TPA is final. When the agreement status is Agreed, the data statuses take affect (run time).  Additionally, after the agreement status is Agreed, you cannot delete the TPA agreement.

->  Disabled

The Disabled status means the TPA should not be used.  If you are using a TPA and no longer want to use it, you can disable it. When you disable a TPA, the TPA remains in the Trading Networks system, but is considered inactive.  Later, if you decide that you need the TPA, you can change the agreement status to Proposed or Agreed.

Data status. The data status determines whether you can modify the TPA data, which is  data that you supply for the IS document type you define for the TPA. That is, the TPA data is the data for the application‐specific variables to use to tailor the processing of documents exchanged between a sender and receiver. 

The TPA data status can be:

->  Modifiable. You can change TPA data; that is you can change the values of the variables in the IS document type associated with the TPA.

->  Non-modifiable. You cannot change the TPA data; that is you cannot change the values of the variables in the IS document type associated with the TPA.

Prev Next
About the Author
Topic Replies (0)
Leave a Reply
Guest User

You might also like

Not sure what course is right for you?

Choose the right course for you.
Get the help of our experts and find a course that best suits your needs.

Let`s Connect