| Author |
Topic  |
|
|
nelsonpw
    
USA
1113 Posts |
Posted - 07/27/2012 : 13:28:30
|
I know HOW to clear a pump on hold. Someone asked me WHY a pump ends up in that state and how it could affect cash balancing. I couldn't come up with a good answer. For me it's pop in, clear it and go. Anyone have any clues??? Also - the 'reserved' state. Can anyone clarify how that happens? I thought it was a prepay that didn't get dispensed and sat for too long on the FP.
***EDIT*** I am surprised nobody chimed in on this one... So I changed the title and sort of bumped the topic. If nobody knows then I'll drop it. THANKS!
|
This is my signature. There are others like it but this one is mine. |
|
|
ScottW
    
USA
892 Posts |
Posted - 07/30/2012 : 20:04:41
|
I have had pumps go on hold that were either prepay or cc preauth - but a known comm issue (intermittent offline) would put thenm into the reserved state. That much I have proven. I have also had , on older verifoen software, sites that would have a cc sale come back in as due - thus the only way to clear was to bring down under a cash sale, thus duplicating the trans as a cc and a cash sale. I have heard that cc preauths will also timeout thus going to a reserved state. I hope this helps....Don't know why I am using "thus" so much....
|
 |
|
|
jgar477
  
USA
241 Posts |
Posted - 07/30/2012 : 20:30:19
|
| In my experience I've only seen pumps end up in a reserved state when a new cashier starts working and has never seen a Ruby before. Not sure what they do that causes them to go into a reserved state but it's always the new cashier that causes that. |
 |
|
|
jingwak
  
192 Posts |
Posted - 08/01/2012 : 10:43:37
|
| I've seen this more at sites with two or more Rubys which makes me believe it has something to do with the workstation(s) not syncing with or matching the master. When this happens I always check for proper lan termination settings and use of required verifone lan cables. Could also happen because of simultanous key inputs on the workstation and the master. |
 |
|
|
DaveWilkinson
 
USA
59 Posts |
Posted - 08/01/2012 : 20:10:55
|
| I have seen it happen when a prepay is set, then a shift change occurs or someone initializes fuel (full or prices only) before the transaction is started (??) Really JACKS things up if you are running a fusion that is not set up correctly |
http://www.math.ucr.edu/home/baez/physics/General/occam.html |
 |
|
|
nettech
  
USA
183 Posts |
Posted - 08/01/2012 : 20:20:55
|
| Pretty cashier prepays the pump for the guy who is trying to get her number, and after about 5 minutes the pump goes into reserve because the software thinks the customer didn't pump and drove off. this is to stop someone else from pumping the fuel. The same holds true when the lottery scratch person prepays and then scratches the tickets he just bought with the rest of his $20 and because he is winning he plays for 15-20 min before he tries to pump his gas. |
 |
|
|
DaveWilkinson
 
USA
59 Posts |
|
|
TechTim
 
USA
86 Posts |
Posted - 08/03/2012 : 10:40:34
|
| Just wondering if Greg has any insight into what causes the pump on hold condition, or the 'reserved' state to happen? |
 |
|
|
cbloom87

USA
20 Posts |
Posted - 08/14/2012 : 23:37:45
|
| pretty cashier? lol I didn't think those existed.... at least not at most of the gas stations I've serviced. The "pretty" ones typically figure out that it takes a certain kind of person to work in a station, and they're not one of them. |
 |
|
|
fossilfueler

USA
40 Posts |
Posted - 08/15/2012 : 01:29:14
|
from my experience:
"normal" scenario for HOLD - register A tries to claim the same fuel sale that is already brought up on register B. from the other register press the p ump # then VIEW. it is to let you know another terminal is supposed to be taking care of it. if you really have to ring it up on register A then void ticket the sale on register B first. this is one of the reasons most ruby/sapphire applications do not allow the use of SUSPEND with a fuel sale.
"abnormal" scenario for HOLD - tries to tender out a post pay and something causes either the workstation or the controller to restart.
"normal" scenario for RESERVE - prepay remains in an authorized state for too long or you view the pump while the prepay is still on the total screen
"abnormal" scenario for RESERVE - something causes the controller to shut down after a prepay was set up or trying to prepay certain pump types for amounts less than $1. |
RTFM |
 |
|
|
mj1964
 
USA
66 Posts |
Posted - 08/22/2012 : 12:23:47
|
| thank you,fosselfueler,you actually aswered the question! |
 |
|
| |
Topic  |
|