server checkout question micros 3700

[jeffnLR]

Ok something i just noticed... when a server runs there checkout they can ring up more items after they run it. This could cause problems if they found out and started ringing up more stuff then giving me the wrong totaled checkout. Is there a way to not allow tabs or tables after running a checkout?? i looked and looked and couldnt find anything..

Thanks for any help!

 

[MZ117]

Not an expert here by any means, however...

Could you not force the check out on Clock Out and then restrict re-clocking in without a manager authorization? Also, do you not have a report you can pull that would show everything at end of day without needing the employee check out chit?

Again, not saying I'm an expert but that seems like it would work, in principal...

 

[CathalMF]

What do you mean by checkout?

What exactly are they doing to perform this? Is it just the printing of a employee report?

 

[mpj3700]

How do you have your server checkout's resetting? by clock out? after it is run? If your server reports are not resetting to zero after they run then yes you have an issue if they reset to zero then there is no way for them to balance out that specific report, yes they could the dollars but you would see multiple reports for them in the system.

Also, as they previous person mentioned you may want to have it set like that or you could even have they need manager auth for doing their report.

 

[jeffnLR]

Hey and thanks for the help! Been real busy and havent had a chance to mess with this for a minute. Ok to CathalMF yes i am talking about the server closeout or employee closeout that has the total $ amounts that the servers owe me at the end of night. I just noticed you can ringup items after running this checkout and before clockout. I may need to investigate this more to see exactly what all can be done and what i would see at the end of night.
MZ117 as far as having totals at the end of night yes i do get a printout for grand totals for the day. I will look into the options of forcing manager auth for re clockin. I wouldnt really want to do this all the time for every server on a initial shift though.
mpj3700 it seems that servers are able to clock out with closed checks that are not on the report they ran before those checks. Im away from the micros server at the moment but what i would like to do is have it where once you run your closeout the only thing you can do from there is clockout. That is how it works in aloha so its what im use to. Or if there are some settings you could tell me about to have it setup somewhat secure i will give it a try.

Thanks again for all the help everyone!

 

[Moregelen]

The easiest way to prevent this from happening is to edit the Employee Report / Employee Checkout autosequence (Configurator -> Reporting -> Autosequence Steps ; to find out which auto sequence it is running, you can go into the touchscreen design and track down the button) and add this step:

Type stored procedure, stored procedure Lock Employee (it is #146 on the system I am using).

Now what this means is that while they can clock out, they can't take any orders. Typically, I then go into the End of Day autosequence and add this step:

Type stored procedure, stored procedure Unlock All Employees (it is #149 on the system I am using).

This way, when they come in the next day for a new shift, they are unlocked already. If you have certain employees that sometimes work double shifts and thus need to be able to keep going after running their report, you will have to add a button in the manager screen that lets you unlock a specific employee.

The button needs to be Category type of Autosequence, Employee Prompt, linked to an autosequence with a stored procedure of Unlock Employee with a Parameter of Employee Parameter, and Source of Object Number.

And there ya go.. when they run their employee report, they can't log back into the transaction screen until either the end of day runs, or a manager manually unlocks them.

 

[Moregelen]

Oh, and to prevent them from clocking out with open checks, just go to Configurator -> Employees -> Employee Classes and make sure that Clock out with open checks is NOT checked.

 

[Moregelen]

*sigh* I typed that in a bit of a rush, forgot to include for the Lock Employee stored procedure you use the same Parameters and Object Source as the Unlock Employee stored procedure, that is to say, Parameter: Employee Parameter and Source: Object Number.

 

[pmegan]

Make sure you set the Range in the Lock Employees to Inherit.
You'll also want to create an autosequence to unlock a single employee. Stored procedure 148, Employee parameter, source = object number, range = prompt. This will let you unlock a single employee when you have someone who has to work a double and runs a report after their first shift.