Routing X12 Documents in Productions
Settings for X12 Business Services
Provides reference information for settings of an X12 business service.
X12 business services have the following settings:
Specifies what to do when a validation error is detected in a batch Interchange document. Options include:
Reject With All Errors
Reject the whole batch if any error is found in any document within it. Enumerate all errors found in the batch if Batch Reply Type
allows for reporting them. This prevents forwarding any documents in a batch until all have been read and validated.
Reject On First Error
Reject the whole batch when the first error is found in any document within it. Do not bother checking for more errors or parsing any further contents of the Interchange. This prevents forwarding any documents in a batch until all have been read and validated.
Reject Individual Errors
Reject only those documents within the Interchange that have errors. Forward each acceptable child document to its target(s) as soon as it has been read and validated. This is the default.
X12 Transaction Set documents are often packaged in a batch document called an Interchange
which contains nested sub-batches called Functional Groups
. The Batch Handling
setting specifies how InterSystems IRIS treats received document batches. The options are:
Do not process child documents individually; accumulate and send the whole batch as one composite document.
Forward all documents in the batch together in one session; the session includes objects representing the parent document header and trailer segments. This is the default.
Forward each document in the batch in its own session, including the objects representing the batch header and trailer segments.
Forward each child document in the batch in its own session; do not forward objects representing the parent batch document’s header and trailer segments.
Specifies the type of batch reply to create for an Interchange batch that has been received. The following table lists the possible choices:
||Do not generate a batch reply. If an error occurs, do not create any immediate notification reply to the sender.
||Generate a reply Interchange containing a reply notification for every TransactionSet received in the Interchange.
||Generate a reply Interchange containing a TA1 segment that indicates acceptance or error status for the entire Interchange, and a reply notification for every TransactionSet received in the Interchange.
Whether or not errors are found, generate a reply Interchange. If no errors are found, generate an empty reply Interchange. If errors are found, generate an Interchange that contains reply notifications only for TransactionSets in which errors are detected.
This is the default setting if no choice is specified.
||If errors are found, generate a reply Interchange that contains reply notifications only for TransactionSets in which errors are detected.
||Whether or not errors are found, generate a reply Interchange. If errors are found for every TransactionSet, generate an empty reply Interchange. Otherwise, generate a reply Interchange that contains reply notifications only for TransactionSets in which no errors are detected (successes).
||Generate a reply Interchange containing only a TA1 segment that indicates acceptance or error status for the whole Interchange received.
||If errors are found, generate a reply Interchange that contains only a TA1 segment that indicates error status for the whole Interchange received.
||If field ISA:14 of the incoming ISA header segment is set to 1, generate a reply Interchange containing only a TA1 segment; otherwise return nothing.
||If errors are found and field ISA:14 of the incoming ISA header segment is set to 1, generate a reply Interchange containing only an error TA1 segment; otherwise return nothing.
||Generate a reply consisting of a single character code: 'A' if the entire Interchange is accepted, 'R' if it is rejected due to one or more errors.
All of the options that relate to TA1 segments are used to force a TA1 segment to be generated, often as the only body segment of the reply interchange. This convention is used to represent the presence or absence of errors in the entire inbound Interchange. However, if an error is found in the incoming ISA or IEA that can only be reported in a TA1 segment, then a TA1 is generated even if the configured setting does not force a TA1 to appear.
Specifies the character set of the input data. InterSystems IRIS automatically translates the characters from this character encoding. Supported values are UTF-8
or any member of the Latinn
family. The value Native
means to use the native encoding of the InterSystems IRIS server.
Placing a @
(at sign) character at the beginning of this field means that the field identifies an internal NLS Translation Table instead of a logical character encoding.
The default depends on the adapter.
code that represents the facility and application that receive X12 documents via this business service. These are used to create reply document headers. The @
(at sign) character represents using the corresponding field from the incoming document. If your ID must contain a literal @
symbol, escape it with back slash: \@
Specifies how to issue X12 reply documents (such as TA1 and 997). Options include:
Do not send back any reply.
Send a reply from the business service immediately upon receipt of an Interchange. This is the default.
Wait for a response from the target configuration item. When it arrives, relay the reply back to the sender. If validation fails or some other error occurs, generate an immediate reply according to the option selected for BatchReplyType
only) Specifies a comma-separated list of configuration items within the production to which the business service should relay any X12 reply
documents that it receives (such as TA1 and 997). Usually the list contains one item, but it can be longer. The list can include business processes or business operations, or a combination of both.
True or False. If True, the business service processes an incoming X12 file without error, even if new lines have been inserted into the file after (or in place of) segment terminators to enhance readability. If False, these extra new lines trigger an error in parsing the file. The default is True.
Content Date/Time: 2019-02-23 01:10:56