X12 batch standard

You can select a batch type for inbound and outbound EDI batch type.

Inbound

Inbound X12 batches are supported with an EDI Batch attribute for inbound threads. If the X12 EDI Batch type is specified for an inbound thread, then all inbound messages are treated as batches.

Version options for the GS segment date file length:

  • "3XXX" indicates the length is 6 bytes.
  • “4XXX” indicates the length is 8 bytes.

Split to options:

  • "Groups" option: Each inbound message is split into individual groups for processing. Values from the batch header and trailer are attached to the group message metadata. For example:

    msgUserData : {ISA {ISA 00 { } 01 {PASSWORD } ZZ {SUBMITTERS.ID } ZZ {RECEIVERS.ID } 020711 1253 U 00401 000000905 1 T :}}

  • "Transaction Sets": Each inbound message is split into individual transactions for processing. Values from the batch header and trailer are attached to the individual transaction metadata. For example:

    msgUserData: {ISA {ISA 00 { } 01 {PASSWORD } ZZ {SUBMITTERS.ID } ZZ {RECEIVERS.ID } 020711 1253 U 00401 000000905 1 T :}} {GS {GS HB {SENDER CODE} {RECEIVER CODE} 20020711 1102 2 X 004010X092}}

Outbound batch

The outbound batch has an edit screen with these parameters. These are configured from the Outbound tab of the Network Configurator Thread Configuration dialog box.

Version options for the GS segment data field length:

  • "3XXX" indicates the length is 6 bytes.
  • “4XXX” indicates the length is 8 bytes.