ScanMaster Version 2.3.1-110 Release Table


	Name of Link:	FTP Site for 2.3.1-110 Patch
	Link to "The Patch":	FTP Site for "The Patch"
	Code Distribution:	N/A
	Posting Date:	6-Feb-07
ScanMaster Version 2.3.1-110 Release Table Last updated February 6, 2007 See the table below for a description of the new features provided and faults addressed in this release. Printing Instructions: many browsers do not support correct color and format printing directly from the Web. For best results, with your cursor highlight the section of the table you wish to print and copy to the clipboard. Then paste from the clipboard into a blank Word document and print the Word document to a color printer.

Enhancement or Fault Number	Item Description
WD 8944	SM2BAPLY.EXE End of Day batch apply is applying batches 3 times -- Creating three OFFSale batches -- Standard Batching The BuildBatchList routine in Sm2baply which is called during an end of day has a logic bug in the SQL statement which causes the batch apply list to have each eligible batch put in the sm2baply.lst file 3 times. It also causes the batches to be in the wrong order of application, i.e., OFFSale, Host, Local. If any batches are marked to produce an OFFSale batch, three OFFSale batches are created, two of which are invalid. This behavior is only seen in the v2.03.01-050 release. v2.03.00 and v2.04.00 work as designed. Detected in v2.03.01.06 Scenario: 1. Set some batches (OFFSale, host and local) start date so they should activate in the end of day. Have at least one batch set to create an OFFSale batch. 2. Have Sm2baply in the EOD script. 3. Run an end of day. Expected Results: Check the batchapp.log - it should show only one activation per batch and the batches should be activated in OFFSale, host and local order. Only one OFFSale batch should be created for any given batch set to create OFFSale. Actual Results: The batches are: not activated in the correct order, are activated 3 times and 3 OFFSale batches are created for each batch set to create OFFSale.