Micros 9700 Duplicate Check Numbers Separated by Day Part

[vengaoperations]

We utilize a Micros 9700 POS.
When going to look up individual checks from the previous day, are seeing duplicate check numbers.

They are separated by "Day Part": Lunch and Dinner. Is there a way to change the settings so that instead of re-using check numbers on the same day, it continues on from the last check number at which it left off? Or starts a new check number range? We would like to be able to record each day's check under an individual check number instead of having duplicates for each day.

I cannot seem to find any documentation on Micros 9700 check numbering settings/day part settings.

 

[hosehead78]

If I understand correctly, your Lunch and Dinner service have the same/similar Transaction numbers for the same business day?

Open EMC, and click on Configurator. Select the RVC in question, then to go RVC Information > PARAMETERS.
On the General Tab, go to the Miscellaneous options and check the Max Guest Check #'s. If it isn't already changed, change it to a higher number or 9999. If the number here is 50 or 100, and your oulet can go through 100 transactions in a Service period, then you will get duplicates.

If the above is already set to a high number that a service period shouldn't hit then check the Workstation settings.
While in EMC > Configurator, go to System Hardware > Device Table.
Select the Workstation that is in the RVC in question. Click on the Workstation Tab.
Find the 'Next Transaction Number' field, make note of the number, then select another workstation in the same RVC and check it's number as well.

I generally have about a 200 Transaction number difference between the workstations. I also make the Workstation that is used the most have a higher Transaction number than the others so it will pretty much never catch up with the others.

The example below, a Single RVC has 3 Workstations, 1 is a cashier and the other 2 are only for servers to enter their orders.

Example: Workstation A (Cashier Workstation) has a next transaction number of 3138. Workstation B has 2863, Workstation C has 2352. This way it keeps the transaction numbers so there shouldn't be any duplicate transaction numbers for a while. You could put them closer together if you want, it's up to you. But this should help with any duplicates.

 

[vengaoperations]

So it looks as though the duplicate checks are due to the fact that two revenue centers are using the same check numbers on the same day.

I.E., Revenue Center A (Cafe) opens with check number 101 at 11PM. Later that day, Revenue Center B (Dining Room)opens with check number 101 at 5:30PM.

What is the best way to modify the system to no longer use the same sets of numbers regardless of what revenue center it is coming from?

Would the same methodology be employed; set the first revenue center to start at check #100 and the second to start at check #2000?

Could you provide detailed instructions on how to make this change in the Micros 9700 system?

 

[hosehead78]

Yes, my response in the previous post is what should be done.

First, setup Both Revenue Center's Max Guest Check to 9999 (if it isn't already configured like this).
To do this Open EMC, and Click on the Configurator.
Locate the Revenue Center Selector drop down box and select the correct RVC to make changes to.
Then Locate the RVC Information, and Click on the Parameters. Under the General Tab, look for the Miscellaneous group of options.
Change the Max Guest Check # to 9999 (if it isn't already set to this). This will allow the RVC checks to go up to 9999, once they hit that they will start back at 1.
Don't for get to save, and do this for any RVC you need to.

I've found a better solution for the second part, as my original one was only for Transaction Numbers, which are different than check numbers. The Query below will return all RVC's and their next check numbers.

-- Micros 9700 - Return each RVC's Next Check Number
-- Usage: 
--  Open SQL Query or SQL Management Studio and Connect to your Micros DB.
--  Open a New Query Window and paste this code

SELECT
	rvc.revenueCenterPOSRef as RVC_NUM
	,rvc.nameMaster as RVC_NAME
	,cnp.MinCheck
	,cnp.MaxCheck
	,cnp.NextCheck

FROM MCRSPOS.microsdb.CHECK_NUMBER_PARAMETER cnp

Join MCRSPOS.microsdb.REVENUE_CENTER rc on ObjectNumber = cnp.ChkNumParamID
Join LOCATION_ACTIVITY_DB.dbo.REVENUE_CENTER rvc on rvc.revenueCenterPOSRef = rc.ObjectNumber

Order by rvc.revenueCenterPOSRef ASC

Make note or save the output of the Current Check numbers.

*** Note the Following information is to be used at your own risk. If you are unsure or do not know about SQL and Databases, have a DBA preform the next steps as it could cause issues with your Database and check information. ***
*** It is Suggested to do this before the Outlets open or After the Outlets close ***

In SQL Management Studio, Connect to your Micros DB, Open another Query Window. Copy and paste the Update command below.
Example for code below, Lets say RVC # 2 has a starting check number of 138 and you want to change it to 1138.

UPDATE MCRSPOS.microsdb.CHECK_NUMBER_PARAMETER
Set NextCheck = '1138'		-- New Check Number; DO NOT USE A LOWER CHECK NUMBER THAN THE CURRENT ONE
Where ChkNumParamID = '2'	-- RVC TO UPDATE; If you Do Not add this line it will update all NextCheck numbers for all of your OutLets.

Once you have ran the Update command, run the other query again and make sure it updates to the new value you've set. Then go to a workstation and start a new check. It will start with the number you set it to.

Keep in mind the Number spacing between each Outlet. Set the Outlet that has the most checks in a service higher than the ones that don't, set the second highest service above the least and so on.

For instance, Outlet 1 is a Bar and has about 500+ checks during their weekend nights, were as Outlet 2 (Cafe) is about 300+ and Outlet 3 (Coffee Shop) is only about 150 on their most busiest day/night.
Example, Set Outlet 1 to start at something like 5000, Outlet 2 to 2500 and Outlet 3 to 1000. This kind of spacing will make it so you should pretty much not have any duplicates, or at least not duplicating for a long time.

Let me know if you have any questions.