Enhancement or Fault Number

Item  Description

WG2.EXE

Error on POS: No Qty Entry Due to Favor EC

The Problem :Error: No Qty Entry Due to Favor EC

Scenario:

1.favor flag on EC with '0' report code

2.EC is first in file

3.ring any item using qty key

4.error occurs

SM2EOD.EXE

EOD Date not being updated correctly in LASTZ.RUN file on last day of the week.

The Problem: EOD Date not being updated correctly in LASTZ.RUN file on last day of the week.  On the last day of the week, the EOW processing happens which updates the WEEK and LWEEK files.  The EOD also updates the LASTZ.RUN file to update the 9th line with the last EOW date.  In the process of updating the EOD for the EOW date, the process incorrectly changes the "index" number saved in the first line of the file.  This causes all of the subsequent EOD applications to use the incorrect date for the financial EOD processing.  In very serious situations it can cause the financial applications to not find any date, and thus not process properly.  i.e. Tlog not processed into a consolidated TLog file, DR and other enhanced department report files are not created, etc. 

Scenario:

1. Using the attached LASTZ.RUN file, and with the EOW set to the current day of the week process an EOD

2. After the EOD is processed, examine the LASTZ.RUN file, the index number should not be greater than 7. 

Expected Results:

The "index" value of the LASTZ.RUN file should be only 1 greater than it was before the EOD was started, and if it was 7 prior to the EOD it should now be 1. 

Actual Results:

If the "index" value was 7 when it started the EOD, and an EOW was processed it puts a value of 9 in the file, which causes the EOD date of the next EOD to not be written to the LASTZ.RUN file.  It works correctly for the last day of the week, because the routines that read the value read the date from the EOW line, which has the correct date/time for the last EOD.