X12 Rebatcher

Rebatch Level

The level at which the message should be re-batched:

• AK3 (997 transaction set, loop 2100).
• IK3 (999 transaction set, loop 2100).
• Interchange (ISA-IEA) (default).
• Functional Group (GS-GE).
• Transaction Set (ST-SE).
• Claim (837 transaction set, loop 2300).
• Claim (IBC U277 transaction set, loops 2200D and 2200E).

Each of the messages being re-batched may have multiple copies of the Rebatch Level, but must only have a single copy of any level containing the Rebatch Level. For example, when re-batching on claims, each message being re-batched must have a single interchange (ISA-IEA), functional group (GS-GE), transaction set (ST-SE) and so on, down to the claim.

Group Property

If a group property is configured, messages will only be re-batched with messages that share the same group property. If the collector collects messages with more than one value in the group property, then a message will be output for each group of messages.

Rebatch Index Property

When the Rebatch Index Property is set and used in the X12 Splitter filter, and the messages are split and re-batched using the same Split/Rebatch Level, without the messages being structurally changed, then the Rebatch Index Property optimization can speed up the re-batching process.

ISA-GS: Ignore Times

When comparing messages for identical ISA and GS segments, whether to ignore the fields ISA08 (Interchange Date), ISA09 (Interchange Time), GS04 (Date) and GS05 (Time):

• Enabled.
• Disabled (default).

This option is useful when responses to an interchange are generated independently and then merged together.

ISA-GS: Ignore Control Numbers

When comparing messages for identical ISA and GS segments, whether to ignore the fields ISA13 (Interchange Control Number) and GS06 (Group Control Number):

• Enabled.
• Disabled (default).

This option is useful when responses to an interchange are generated independently and then merged together.

Set Identifier Property

When a batch message enters the Rhapsody route it can be identified by setting a property prior to splitting by the X12 Splitter filter. This property is used within this field to identify the original batch message for each split, in order to rebatch the splits together correctly.

Total Count Property

The property which contains the total number of messages within a set. The Split Count Property defined in the X12 Splitter filter configuration is used here.

Index Base

The number base for indexes, that is zero- or one-based.

Index Property

The message property which contains the index position of a message within the set. The Split Index Property defined in the X12 Splitter configuration is used here.

Message Set Timeout

Identifies the length of time the messages must wait in the collector before the message collection is considered complete, if the full size is not reached. Set this to zero (0) for no limit on time, that is size-based collection only.

Timeout Units

Identifies the units of measure for the timeout:

• Seconds.
• Minutes (default).
• Hours.
• Days.

Timeout Destination

Identifies the location which messages that are part of an incomplete collection are sent to, once the timeout period is reached:

• Error Connector.
• No-Match Connector.
• Process as Usual (default).