Skip to main content
Feedback

Trading Partner information document properties

Use Trading Partner information properties to retrieve values related to a document framework.

Trading Partner information properties represent various values related to a document framework, such as X12 EDI, including sender/receiver ID, ISA control number, etc. These properties are set automatically by the Trading Partner components configured in the Start step and are primarily used only for retrieval.

For example, if you have a process that receives documents from multiple trading partners, you could inspect the "Sender ID" property to route or map individual documents accordingly. Or if you have documents coming from an inbound X12 or HL7 Trading Partner step, you could use a Route step or a Decision step to check the “Message Is Valid” property to determine whether the document passed or failed schema validation.

Although you can technically set outbound trading partner information property values, you should use a Trading Partner step instead to take advantage of the reusable configuration and acknowledgment handling.

The following list shows the types of document properties supported by each document standard:

Custom
  • Interchange document properties
EDIFACT
  • Interchange document properties
  • Functional Group document properties
  • Message document properties
HL7
  • Message document properties
ODETTE
  • Interchange document properties
  • Message document properties
RosettaNet
  • Message document properties
  • Is Standalone - When set to True, the standalone attribute is removed from the RosettaNet service content body
  • (RosettaNet v2.0) Is Secure Transport Required - Defaults to Yes if the property is either not set or is set to a value other than Yes or No.
  • (RosettaNet v2.0) Known Initiating Partner Domain
  • (RosettaNet v2.0) Known Initiating Partner Location
  • (RosettaNet v1.1) Global Process Code
  • (RosettaNet v1.1) Global Document Function Code
  • (RosettaNet v1.1) Process Instance Identifier
  • (RosettaNet v1.1) Attempt Count
  • (RosettaNet v1.1) Sender Global Partner Classification Code
  • (RosettaNet v1.1) Receiver Global Partner Classification Code
  • (RosettaNet v1.1) Time To Acknowledge Acceptance - Formatted CCYYMMDDThhmmss.sss, preceded by an optional sign (+ or -). For example, a value of 00000000T003000.000 denotes 30 minutes.
  • (RosettaNet v1.1) Time To Acknowledge Receipt - Formatted CCYYMMDDThhmmss.sss, preceded by an optional sign (+ or -). For example, a value of 00000000T003000.000 denotes 30 minutes.
  • (RosettaNet v1.1) Time To Perform - Formatted CCYYMMDDThhmmss.sss, preceded by an optional sign (+ or -). For example, a value of 00000000T003000.000 denotes 30 minutes.

For cases in which the known initiating trading partner for a document is different than the sending trading partner, set the following document properties:

  • Known Initiating Partner ID
  • (RosettaNet v2.0 only) Known Initiating Partner Domain
  • (RosettaNet v2.0 only) Known Initiating Partner Location

These property values are used to populate the corresponding fields in the service header in the outbound document or acknowledgment document only if the Known Initiating Partner ID property is set. Otherwise, the sending trading partner information is used to populate those fields.

Of those three properties, only Known Initiating Partner ID is accessible in Process Reporting. The Signal Version property is not accessible in Process Reporting.

Tradacoms
  • Interchange document properties
  • Message File document properties
X12
  • Interchange document properties
  • Functional Group document properties
  • Transaction Set document properties