Creating trading partner agreement definitions

Edit online

Create a TPA definition to tailor how documents are exchanged between two trading partners.

About this task

The following list describes the types of TPA definitions:

System TPA
These TPAs enable partners that use certain types of business documents to function as intended. The TPA data is editable, but the TPA definition cannot be altered.
User-defined TPA
You create these TPAs in webMethods B2B and are modifiable.

You can create the following TPA types in webMethods B2B :

Partner-specific TPA
It is specific to the sender and the receiver. A partner-specific TPA contains partner-specific variables that are used by only the particular pair of trading partners (sender and receiver) that are defined in the TPA.

The same partner-specific TPA can be used even when the sender acts as a receiver and the receiver acts as a sender.

Sender-specific TPA
Specifies a sender but leaves the receiver that is defined as unknown. The value unknown equates to any, thus allowing any partner to be a receiver.
Receiver-specific TPA
Specifies the receiver but leaves the sender that is defined as unknown. The value unknown equates to any, thus allowing any partner to be a sender.

Procedure

  1. In webMethods B2B , from the side navigation menu, click Assets > TPA definitions.
  2. Click the Add icon.
    In the Create TPA definition dialog, add the details and click Create.

    The agreement name for RNIF-PIP business documents must be the document type name, and for EDI business documents, it must be EDITPA.

    When you create a template for EDI that you can use to duplicate for other TPAs, use the default values of Unknown for both Sender and Receiver.

    You can copy the system-defined TPA definitions and the user-defined TPA definitions to create new ones. You can also import and export the TPA definitions along with the referenced templates.

What to do next

Edit TPA definition: You can update the values and the status of a TPA definition. Load and download the TPA data. You can load the data in JSON and XML format. The XML file must be in IDataXMLCoder format. You cannot save the data in XML format. When you load the TPA data in JSON format, if the values mentioned for any of the TPA data variables are not supported in webMethods B2B , then you must handle the errors in your business logic when you create the integration.

Delete TPA definition: You can delete the TPA definition not in use.