Batching Tab
Use the Batching tab to manage outbound batching for your X12 partners that are using this transporting Gateway. These settings are used if this Gateway trading partner name is entered in the Gateway (override scheduler and transport settings) field in a trading partner's X12 Batching tab. See Product Overview for more information.
Field | Description |
---|---|
Outbound | |
Allow Single Transmission for Multiple Exclusively- batched Interchanges |
If the Batch Option list for a transaction action is set to Exclusively, then the interchange containing this transaction can only contain this type of transaction. But you can still put multiple interchanges, each containing different types of transactions, into a single batch and send it to the trading partner. This option and the option “Increment Interchange Control Number by Operation ID for Exclusive Batch” are mutually exclusive. |
Increment Interchange Control Number by Operation ID for Exclusive Batch |
Select the check box to increment control numbers based on transaction types in addition to partner ID qualifiers. Used only for exclusive batching. If the option “Always Create Batch per Trading Partner” is disabled and the document is routed from different trading partners, then the outbound document would contain 'n' number of outbound interchanges, each interchange represented for each trading partner per transaction type, since the documents are exclusively batched. This option and the option “Allow Single Transmission for Multiple Exclusively-batched Interchanges” are mutually exclusive. |
Regenerate Control Number For Batch Resend |
You can override generation of a control number for batch resend for a trading partner using X12 protocol by selecting/unselecting this check box. To select control number regeneration for these protocols, see TIBCO BusinessConnect Container Edition EDI Protocol powered by Instream, X12 Configuration, Regenerate Control Number For Batch Resend. |
Destination File Mask for Batch |
|
Always Create Batch per Trading Partner |
Normally, when partners share a gateway or VAN, a single batch may contain mixed document types such as 850 and 101 that are intended for different partners. Example: One batch of 850s and 101s for distribution at the VAN to different trading partners. If you check this field, separate batches are created for each partner, but each batch can now contain a mixture of different document types such as 850 and 101. |
Outbound XML to EDI Data Encoding for Batch* |
Specify the type of encoding for outbound XML to EDI data. This field is required. The default value is US-ASCII. |