Resolution:
The configuration parameters for Scheduled Batch Transmission - "Number of Transactions reached" ' and "Frequency" - should be interpreted as threshold values. The batch transmision depends on whichever threshold is triggered first.

There is one more parameter defined in &ltBC>/resource/EDI.cfg file that affects the behavior of scheduled batching:

edi.task.scheduler.pollingInterval: 60000

This is a polling interval to poll the database for any new EDI transactions - set to a default value of 60 seconds.

In the case where 7 EDI files are sent in succession, the following is a possible explanation:
As per the polling interval, BC checks the database for new transactions each minute. It finds 3 of them in one poll,
so BC batches them up and since this number is > 2 (Number of Transactions reached), the batch is sent. Same thing happens for the next set of 4 docs.

Please try the following:

1> Increase the value specified for "Frequency" and make sure the "Number of Transactions reached" parameter works as expected.

2> Then increase the "Number of Transactions reached" setting to a large value and reduce the value of "Frequency" to ensure that all pending transactions go out in a single batch when the interval expires.

EDI batching does not work as expected, I have set the number of transactions to batch as 2 and the interval to 5 minutes. But, when I send a set of 7 transactions in succession, I don't see 2 transactions per batched file; one has 3 and the other has 4.