Custom Trading Partners

Document created by matthew_hartmann817867 Employee on Jul 23, 2018Last modified by sheng_liao462475 on Jul 23, 2018
Version 4Show Document
  • View in full screen mode

This article will cover the uses of Custom Trading Partners, as well as how they are configured within the Atomsphere platform. 

 

 

 

What are Custom Trading Partners

Within the Atomsphere platform, B2B requirements are managed through Trading Partners. Trading Partners are used to perform Direct EDI or point-to-point electronic business transactions. This is done by designating two partners: both a host and remote partner, who connect through a specific communication protocol. One of the biggest perks of using Trading Partners over a standard connector is its cost. A trading partner can effectively be used for communication at a fraction of the price.  

 

Most trading partners commonly exchange X12 data. Other methods supported by the trading partner include HL7, EDIFACT, and ROSETTANET. When performing direct EDI, some trading partners do not exchange X12 data, or any of the other standards mentioned. The purpose of the custom trading partner is to allow for the exchange of data standards not previously mentioned (such as XML/JSON in the trading partner framework), but to still consider anyone who exchanges files with a trading partner.

 

Configuring the Trading Partner

Within both the Start Shape and Trading Partners Shape, the ‘My Standards’ tab can be configured for a Custom Trading Partner. By clicking on the ‘Add My Company Standard’ tab, you can change the standard to Custom. This is shown in the image below: 

 

 

By changing the document standard to Custom within process reporting, you can view the deployed Custom Trading Partners. After adding filters such as Atoms, Tracked Fields, and To/From Trading Partners, four data elements for these instances will be shown: Actions, Date Processed, Atom and Size (in kB). This is shown below:

 

 

Attachments

    Outcomes