(particularly considering an extisting Drink Dispenser connection)
A GC booking transaction in the MICROS Retail OSCAR POS system requires the existence of CLIENT databases. Before being booked on the client, the whole GC is copied to the local client database (or is created there). This is necessary to allow further processing of GCs in the offline mode – always to the last client that booked on the GC.
A copy of the current GC state is always existent on the server database, too.
The administration of which client is currently to process which GC is done by the MICROS Retail OSCAR POS server. If a GC is currently on another client, this client will be directly addressed (cp. SALESDEBUG:releaseGC) and queried if it is willing to release the GC. If the process unit currently entered as the processing client is not accessible, this GC cannot be booked on by other clients (GC locked).
This GC processing involves the following dangers:
After using the function “UNLOCK GC” for a terminal, all GCs that are assigned to this terminal as the “last processing unit” will be accessible for all other process units again (because the entry “last processing unit” will be set to zero). In cases of system unit defects, the other terminals will thus go on booking according to the last GC booking state of the client. If the client database of the defect system unit is not erased or if a client of which the GCs have been unlocked carries out further booking transactions for this GC after the function “UNLOCK GC” has been utilized, this will lead to severe booking differences in ONLINE cases since the processing states of the GC differ between the server and the client..
Click on the image
to return to the Table of Contents.