Tuning the partner-specific EDITPA

Trading Partner Agreement (TPA) definitions are a set of parameters that help you tailor how documents are exchanged between two trading partners.

You can define a partner-specific agreement when you have one or more sender-receiver pairs that require a unique set of configurations.Partners can use TPAs to agree upon different parameters to meet the SLAs.

Consider partner Tyre Fitters and partner Car Assemblers using EDI documents for their business transactions. The sender-receiver pair of partners, in this case, Tyre Fitters and Car Assemblers need a different type of processing compared to the rest of the partners.

In webMethods.io B2B, an EDI trading partner agreement (EDITPA) has a set of variables that let you tailor how EDI business documents are exchanged between two trading partners.

You can use the parameters to tune aspects such as response time, expected delivery time, fail-over percentage and so on.

For example, you can configure the autogenerateFA variable to generate functional acknowledgment for every inbound transaction (Example : X12 4010 997).

Let’s see how autoGenerateFA is tuned.

Document Used: X12 4010 850 Document
Channel: AS2 inbound and outbound channels

Before you Begin

1. Create the partners between which the document needs to be exchanged

In this case, Tyre Fitters(Sender) and Car Assemblers(Receiver) are created with Identity Types DUNS and EDIINT AS2.

Refer to this link

2. Create Partner users and associate it with the partners

Partner user with name ‘tyreFitters_user’ is created and associated with the partners.

Refer to this link to create partner user

3.Create AS2 inbound and outbound channel for exchange of Document and associate it with Tyre Fitters(Sender)

Refer to this link to create channels

Refer to this link to associate an inbound channel with a partner

Refer to this link to associate an outbound channel with a partner

4.Create TPA Definition

You can create a EDITPA definition for a specific sender-receiver pair by referring to EDIV1 template.

EDIV1 is a predefined template that is available with webMethods.io B2B by default. It enables the partners using certain types of business documents to function as intended. It cannot be modified.

Go to Agreements > TPA definitions > Add Definition

Refer to this link to create TPA

Important: To capture the complete information exchange between sender and receiver, you need to create a TPA for the sender-receiver pair.

Create Sender-Receiver Pair of TPA

Agreement Name: EDITPA
Sender: Tyre Fitters
Receiver: Car Assemblers
Template: EDIV1

Set autoGenerateFA to “ON

5.Submit a payload to emulate the document exchange between the sender-receiver pair.

Post an EDI 850 payload over the AS2 Inbound channel Endpoint URL.

Method: POST
URL: AS2 Inbound channel Endpoint URL
Basic Authentication: Partner user’s username and password must be used.
Headers:
AS2-From: “AS2 Sender Profile”
AS2-To: “AS2 Receiver Profile”
AS2-Version: 1.2
Accept-Language: en-US,en;q=0.5
Cache-Control: no-cache
Content-type: application/edi-x12
EDIINT-Features: multiple-attachments
Message-ID: Test-012
Mime-Version: 1.0
X-b2b-stageID: stage00

In Headers ,
AS2-From should have the Identity value of EDIINT AS2 type of Tyre Fitters
AS2-To should have the Identity value of EDIINT AS2 type of Car Assemblers

Body:
In Body > choose ‘Other’ and the content is

(see the attachment for the payload in .txt format)

tpa_850.txt (1.1 KB)

On sending the post request, transactions will be generated as shown below.

In the above screenshot, the highlighted transactions indicate that X12 4010 850 Document is transferred from Tyre Fitters to Car Assemblers and FA (X12 4010 997) is autogenerated from Car Assemblers to Tyre Fitters.

Similar to this, you can tune other variables in EDITPA and configure the behaviors. For more details check here