Transmission Structure

The following four sub-tabs are available in the Transmission Structure tab:

Interchange Header

In the Interchange Header tab, you can specify the settings to use in composing the interchange header (ISA segment) for documents sent to this trading partner.

The following table lists the fields in the Interchange Header tab:

Interchange Header Fields
Field Description

Outbound

Authorization Information:
* ISA01 Qualifier

Required. Code identifying the type of information specified in the ISA02 Information field.

The default value is 00, indicating that no authorization information is present.
ISA02 Information Information used for additional identification or authorization of the interchange sender or the data in the interchange.
Security Information:
* ISA03 Qualifier

Required. Code identifying the type of information specified in the ISA04 Information field.

The default value is 00, indicating that no security information is present.
ISA04 Information Security information about the interchange sender or the data in the interchange.
Date and Time Formats:
* ISA09 Date Format Required. The date when any outbound interchanges are prepared. The macro YYMMDD can be specified to have the current system date inserted in the designated format into this field when an interchange is being prepared.
ISA10 Time Format Required. The time when any outbound interchanges are processed. The macro HHMM can be specified to have the current system time inserted in the designated format into this field when an interchange is being prepared.
Others:
ISA11 Control Standard (4012 and Lower)

The agency responsible for the interchange control standard used by the transaction that is enclosed by the interchange header and trailer.

The default value is U.
ISA11 Repeating Separator (4020 and Higher)

Character used to separate repeated occurrences of a simple data element or a composite data structure. This character must differ from the data element separator, component element separator, and the segment terminator.

The default value is *.

Earlier versions of X12 do not specify a repeating separator. In these earlier versions, an interchange control standard identifier is specified in the interchange segment instead.
* ISA14 Ack Requested

Required. Code sent by the sender to request an interchange acknowledgment.

The default value is 0, indicating that no interchange acknowledgment is requested
* ISA15 Usage Indicator

Required. Code indicating whether data enclosed by this interchange envelope is test, production or information.

The default value is P, indicating Production.
*ISA16 Component Element Separator

Character used to separate component data elements within a composite data structure. This character must differ from the data element separator, segment terminator, and repeating separator.

The default value is +.

Group Header

In the Group Header tab, you can specify the settings to use in composing the functional group header (GS segment) for transactions sent to this partner.

The following table lists the fields in the Group Header tab:

Group Header Fields
Field Description

Outbound:

Application Code:
GS02 Sender The application sender's code in the GS segment of an X12 document that identifies the party sending the X12 group. Codes are agreed upon between trading partners
GS03 Receiver The application receiver’s code in the GS segment of an X12 document. This code identifies the party sending the X12 group. Codes are agreed upon between trading partners.
Date and Time Formats
*GS04 Date Format

Required. The date when any outbound groups are prepared.

  • The macro CCYYMMDD can be specified to have the current system date inserted in the designated format into the GS04 field when a group is being prepared.
  • The macro YYMMDD is used for earlier X12 versions where the GS04 field is designated as a 6-character field.
*GS05 Time Format

Required. This is the time when any outbound groups are prepared and must be specified in 24-hour clock format.

  • The macro HHMM can be specified to have the current system time inserted in the designated format into the GS05 field when a group is being prepared.
  • The macro HHMMSSD can also be specified to have the current system time inserted in the designated format into the GS05 field. SS indicates the current seconds, and must be a value between 00 and 59. D indicates one tenth of a second, and must be a value between 0 and 9.

For example, if the current time is 16:50:23 618 and the HHMMSSD format is set in GS05, the value in the converted X12 data is 1650236.
When an XML document is sent over the X12 protocol from the private process, if the values GS02/GS03 are not overridden by the private process InitiatorRequest message, these values from the GS02/GS03 fields under Trading Partner > X12 Protocol > Group Header are used during the XML-to-EDI conversion. If no values are specified in these GS02/GS03 fields, the values GS02/GS03 (Application Code Sender/Receiver) from Operations Editor > X12 > Group Version are used instead in the final EDI output.

Control Numbers

In the Control Numbers tab, you can specify settings, which affect the validation or generation of control numbers for this trading partner.

The inbound settings affect the validation of control numbers in documents received from this trading partner. The outbound settings affect the generation of control numbers to be included in documents sent to this trading partner.

For more information on control numbers, see TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® User’s Guide, Control Number Management.

The following table lists the fields in the Control Numbers tab:

Control Numbers Fields
Field Description
Inbound
Group Control Number Increment across Interchanges Select True or False to specify whether to validate that group control numbers increment across interchanges.
Interchange Control Number Sequence Check

Specify how interchange control numbers are validated across a sequence of transactions.

  • None No validation is performed.
  • Incremental Successive interchange control numbers must increase by 1.
  • Chronological Successive interchange control numbers must increase by >= 1.
Group Control Number Sequence Check

Specify how group control numbers are validated across a sequence of interchanges or transmissions.

• None No validation is performed.

• Incremental Successive group control numbers must increase by 1.

• Chronological Successive group control numbers must increase by >= 1. If you select Incremental, you must avoid some possible problems.

For more information, see TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® User’s Guide, "Senders and Receivers Falling out of Sync with Incremental Control Numbers."
Transaction Control Number Sequence Check

Specify how transaction control numbers are validated within a group or an interchange.

  • None No validation is performed.
  • Incremental Successive transaction control numbers must increase by 1.
  • Chronological Successive transaction control numbers must increase by >= 1.
Reset on Save

Select this check box to force the recycling of control numbers on demand. This applies to control numbers for inbound. On inbound documents, the resetting of the control numbers can reset the inbound trading partner control numbers, which are used in control number validation. As a result, the validation starts again based on the next incoming document from the trading partner.

By default, this check box is cleared.
Outbound
Increment Group Control Number across Interchanges

Select True or False to specify whether to increment group control numbers across interchanges.

The default value is True.
Increment Transaction Control Number Sequentially Across Interchanges

Select True or False to specify whether to increment transaction control numbers sequentially.

The default value is False.
Interchange Control Number Seed

Specify the interchange control number starting point.

The default value is 0.
Interchange Control Number End Specify the interchange control number ending point. The next interchange after the ending point is numbered with the seed. The default value is 999999999.
Group Control Number Seed Specify the group control number starting point. The default value is 0.
Transaction Control Number Seed

Specify the transaction control number starting point.

The default is 0.
Reset on Save Select this check box to force the recycling of control numbers on demand. This applies to control numbers for inbound. By default, this check box is cleared. If you select this check box, on outbound documents, the resetting of the control numbers force the outbound control numbers for a trading partner to start from the seeding value again before reaching the ending value. As a result, the control number of the next outbound document is generated based on the seeding value.
Reset Across ALL domains

Select this check box to reset the control numbers across all domains.

By default, the check box is cleared.

Delimiters

In the Delimiters tab, you can specify the delimiters to be used when composing X12 documents to be sent to this trading partner.

Only one character per delimiter can be used for the X12 Protocol.

Each delimiter value must be unique. For example, the Segment Delimiter value cannot be set for the Element Separator, or for other delimiters.

The following table lists the fields in the Delimiters tab:

Delimiters Fields
Field Character Description
Outbound
*Segment Terminator ’ (apostrophe) The character indicating the end of a segment. A segment terminator must be a single character.
*Data Element Separator ~ (tilde) The character used to separate data elements in a segment. A data element separator must be a single character.
*Replacement Char | (vertical bar) The character used to replace values in XML data that are the same as delimiters defined in configuration. A replacement character cannot be identical to any other delimiters. The required value format is a single character or a hexadecimal number.
Extra Segment Terminators (e.g. 0x0d,0x0a)  

The additional characters of the segment terminator when the segment terminator consists of more than one character. The first character of the segment terminator is always specified in the Segment Terminator field. The additional segment terminator characters are specified in this field.

Extra Segment Terminators cannot have the same values as the ones used for Data Element Separator or Segment Terminator.