Validation and ACK Generation Settings Page (X12)

The properties included in the Validation and ACK Generation Settings page serve two functions:

  • To define how BizTalk Server generates acknowledgments in response to X12-encoded interchanges received from the party. This includes determining whether BizTalk Server splits or preserves received batched interchanges.

  • To define how BizTalk Server validates those interchanges and acknowledgments.

The role of the party is as an interchange sender to BizTalk Server; the role of BizTalk Server is as an interchange receiver from the party.

This page of the EDI Properties dialog box is displayed by right-clicking a party in the Parties node of the BizTalk Server Administration Console, clicking EDI Properties, and then clicking Validation and ACK Generation Settings under the X12 Properties and Party as Interchange Sender nodes in the console tree.

Route ACK to send pipeline on request-response receive port

Route ACK to send pipeline on request-response receive port
Check to return an EDI acknowledgment over the open connection of a two-way request-response receive port, after an EDI interchange has been received.

Clear to return an EDI interchange over the open connection of a two-way request-response receive port. In this case, an EDI acknowledgment must be returned to the sender by a separate send port.

The default value is checked.

noteNote
This property will be ignored if an AS2 message containing an EDI interchange is received over a two-way request-response receive port.

X12 ACK

Generate TA1
Select to generate a technical acknowledgment on the interchange sender.

The default value is cleared.

Do not batch TA1
If you have selected Generate TA1, select to disable batching of technical acknowledgments.

The default value is cleared.

Generate 997
Select to generate a functional acknowledgment on the interchange sender.

The default value is cleared.

Do not batch 997
If you have selected Generate 997, select to disable batching of functional acknowledgments.

The default value is cleared.

ST2 (Transaction set control number)
Enter the values for the Transaction set control number.

This number consists of four fields: a prefix, minimum and maximum number, and suffix. The prefix and suffix are optional alphanumeric fields. The minimum and maximum numbers are required numeric fields. The maximum length of all three fields together is nine digits; the maximum length of the prefix and suffix together is eight digits. The minimum length of the number field is one character; the maximum, 9.

The default value of the number fields is 1 to 999999999.

Reset to lower limit when out of bound
When set, if the transaction set control number exceeds the maximum specified value BizTalk Server will set the transaction set control number of the next ACK to the minimum specified value.

The default is checked.

Transaction set status acceptance reporting

Generate AK2 loop for accepted transaction sets (if unchecked, loop will be generated only if AK501 is not equal to A)
Select to generate AK2 loops in a 997 acknowledgment for accepted transaction sets (where AK501 == A). If cleared, AK2 loops will only be generated for rejected transaction sets.

The default value is cleared.

Document validation properties

EDI type
Select to enable EDI (data elements) validation on the interchange sender, which includes validation of field length, optionality, and repeat count in addition to EDI data element validation.

The default value is checked.

noteNote
Even if this property is not selected, cross-field/segment validation will be performed if it is turned on in the schema annotation.

Extended validation
Select to enable extended (BizTalk XSD) validation on the interchange sender, which includes validation of field length, optionality, and repeat count in addition to XSD data type validation.

The default value is cleared.

Allow leading and trailing zeroes and spaces
Select to specify that an EDI interchange received from the party will not fail validation if a data element in an EDI interchange does not conform to its length requirement because of leading (or trailing) zeroes or trailing spaces, but does conform to its length requirement when they are removed. This covers the following cases:

  • For the X12-N data type, selecting this property allows leading zeroes irrespective of minimum length requirements.

  • For the X12-R data type, selecting this property allows leading zeroes irrespective of the minimum length requirement, and allows trailing zeroes after the decimal point.

  • For the X12-ID and X-12 AN data types, selecting this property allows trailing spaces irrespective of the minimum length requirement.

The default value is cleared.

Allow trailing separators
Select to allow trailing delimiters and separators on the interchange sender so that they do not cause messages to be declared invalid.

The default value is cleared.

Create empty XML tags for trailing separators
If you have selected Allow trailing delimiters/separators, select to create empty XML tags for each of the trailing separators.

The default value is checked.

Security/Password information in context property

Mask security/authorization/password information
Select to mask authorization/password security information (the ISA2 and ISA4 fields) in the context property to prevent information disclosure.

When BizTalk Server receives a message, it promotes the ISA header into the context of the message. (If BizTalk Server receives and splits a batched interchange, it will promote the interchange header into the context of each transaction set within the interchange.) Without masking, the security information within the context would be available to anyone with administrative privileges.

To mask this information, BizTalk replaces each character of the information with a # character. This is a one-way process: the # characters cannot be converted to actual characters.

The default value is checked.

X12 Nn data type

Convert implied decimal format Nn to base 10 numeric value
Select to convert an EDI number that is specified with the format Nn into a base-10 numeric value in the intermediate XML in BizTalk.

The default value is cleared.

noteNote
After this conversion, the intermediate XML may fail length validation. This occurs because the number in the base-10 numeric format includes a decimal, making its length one greater than the number in Nn format. You can resolve this issue by adding a value of 1 to the minimum/maximum length value.

Inbound batch processing options

Inbound batch processing options
Specify whether to pass an interchange through intact (preserving the interchange) or to split the interchange.

Can be Split Interchange as Transaction Sets - suspend Transaction Sets on Error, Split Interchange as Transaction Sets - suspend Interchange on Error, Preserve Interchange - suspend Interchange on Error, or Preserve Interchange - suspend Transaction Sets on Error.

The Preserve Interchange commands specify that the batch received is processed as a single unit. If, however, one or more transaction sets in that interchange fail validation, you can specify either that each transaction set in error is suspended, or you can specify that the entire interchange is suspended.

The default value is Split Interchange as Transaction Sets.

  © 2009 Microsoft Corporation. All rights reserved.
Show: