We have a process that posts labor start and stop transactions into SF010500. These are processed by the ADC workstation that is always running. When the ADC processor finds a record in SF010500, it checks to see if there is a match already in SF010501 and if so, it posts the labor transaction to WIP. That means that when a "start operation" transaction hits SF010500, then the ADC processor puts it into SF010501 - where it will sit until the "stop operation" gets posted. When the "end operation" transaction hits SF010500, ADC finds the start and the WIP labor is off on it's merry way into the MO.
We have been having some problems with an inordinate number of "mismatched" transactions staying in SF10501 and after doing a lot of digging and monitoring, we finally realized that it is a lot of "end" transactions with no start that get hung up. Going further, we have discovered that the SF010501 table is being cleared every night at midnight. I have checked all over the database to see if we have a job or procedure running that is doing that and we cannot find anything that does this.
Is anyone aware if this is standard GP behavior - does the ADC clear it's queue every night at midnight?
Thanks,
Kevin