X12 outbound trade links

Edit online

Trade links can be added, changed, or deleted. In addition, existing Trade Links can have their individual Applications (also known as "Documents") added, changed, or deleted.

To add a new X12 Outbound trade link, use the following tags:

To change an existing X12 Outbound Trade Link, use the tags:

To delete an entire X12 Outbound Trade Link, see X12OBTradeLinkDelete.

There are 4 levels of data in an Outbound Trade Link:

  • The Trading Partner (ISA)
  • Application Partner (GS)
  • Applications (Versions/Functional ID's)
  • Transaction Levels (ST)

Unlike Inbound Trade Links, there is no such thing as an Unknown Outbound Trade Link, and like Inbound Trade Links, the lowest level (transactions) is not supported in the AutoLoad input; all transactions for a given Version/Functional ID is written to the Transaction tables (with a blank ST Reset value). In the unusual case the ST Reset values are required on an Outbound Trade Link use Partner Manager after the AutoLoad is completed.

Complicating this structure is the fact that the Trading Partner level (ISA) may already exist, but for different Application Partners (GS) than the one being added by the AutoLoad Utility. If this is detected, then any entry in the Trading Partner level is ignored, a warning is issued, and the Link is added. Note the Trading Partner level is required in the input file even if the user knows this level exists.

Nesting is similar to Inbound Trade Links. If multiple Application Partners are specified, they have to be nested under the Trading Partner, and if multiple Applications (Versions/Functional ID's) are specified then they have to be nested under the Application Partner. For example, one trade link, two application partners, each having one application during an "add" operation:


<X12OBTPLink>
 	<X12OBApPartnerLnk>
 		<X12OBAppLink>
 		</X12OBAppLink>
 	</X12OBApPartnerLnk>
 	<X12OBApPartnerLnk>
 		<X12OBAppLink>
 		</X12OBAppLink>
 	</X12OBApPartnerLnk>
</X12OBTPLink>

Adding an Application (also known as a Document) to an existing Trade Link is supported in the following tags:

  • X12OBTPLinkChange
  • X12OBApPartnerLnkChange
  • X12OBAppLinkAddChangeDelete

During a change operation, you can change the Trading Partner Level, change the Application Partner Level, or add, change, or delete the Application level.

Example nesting of these "Change" tags is:

<X12OBTPLinkChange> (required)

<X12OBApPartnerLnkChange>

(optional, but required if changing a document)

<X12OBAppLinkAddChangeDelete>

(optional Document level)

</X12OBAppLinkAddChangeDelete>

</X12OBApPartnerLnkChange>

</X12OBTPLinkChange>

The following table, field, and tag descriptions are for X12 outbound trade links: