We track labor to Work orders thru DC-A and post thru DC-H.  When checking labor status pending labor I get a report showing a long list of seemingly random dates for which employees clocked in/out with no time attributed to a WO ( which is not possible in our shop).  The WO field is 0-0
 
The dates vary between employee with some overlap but no rhyme or reason tha we can figure. Labor dates go back to 12/09/02.
 
Tried posting again, but get error message copied below:
 
Labor/Production Exception Report
 
                                                               Page #     1
Emp  WO#        Seq  Date     Exception
---- ---------- ---  -------- -------------------------------
   3      0-  0   0 06/02/03 This Work Order doesn't exist.
   3      0-  0   0 06/02/03 This Work Order doesn't exist.
   3      0-  0   0 06/02/03 The Routing status is not R or I.
   4      0-  0   0 06/04/03 This Work Order doesn't exist.
   4      0-  0   0 06/04/03 This Work Order doesn't exist.
   4      0-  0   0 06/04/03 The Routing status is not R or I.
   4      0-  0   0 06/05/03 This Work Order doesn't exist.
   4      0-  0   0 06/05/03 This Work Order doesn't exist.
   4      0-  0   0 06/05/03 The Routing status is not R or I.
 
I then ran DC- D again and the list ( 4 pages) remains.  What does this mean??
 
Thanks

I will try.  But why set stop/start default to N if I want to collect hours worked data in DBA?  
 
Another note of info.  This is a recent occurence - started a few weeks agowhen I updated ISTS (though the dates go back into 2002) and defaults have not been changed.
 
JO