Operations on the POS Workstation

Support Added for Oracle Linux for MICROS on Specific Devices

Specific workstation devices can be converted to run the Oracle Linux for MICROS operating system. The Simphony EMC workstation setup steps for these devices remains the same as previous releases. These workstations and tablets listed here have been validated to run the Oracle Linux for MICROS operating system:

  • Oracle MICROS Workstation 5a

  • Oracle MICROS Workstation 6 Series:

    • Oracle MICROS Workstation 610

    • Oracle MICROS Workstation 620

    • Oracle MICROS Workstation 650

  • Oracle MICROS Compact Workstation 310 and 310R

These Kitchen Display System (KDS) devices have been validated to run the Oracle Linux for MICROS operating system:

  • Oracle MICROS Kitchen Display Controller (KDC) 210 (also known as DT Research DT166CR)

The Oracle Linux for MICROS platform is compatible with the System Interface Module (SIM).

See the Oracle Hospitality Food and Beverage Hardware documentation for instructions to convert supported devices to the Oracle Linux for MICROS platform.

See the Oracle MICROS Simphony Client Deployment Guide for information about installing the Client Application Loader (CAL) on Oracle Linux for MICROS devices.

See the Oracle MICROS Simphony System Interface Module (SIM) Manual, specifically Chapter 7: ISL System Variables, for more information about the supported variable for the Oracle Linux for MICROS platform.

Support Removed for Microsoft POSReady 2009

Support is no longer available for POS client and KDS client devices running Microsoft POSReady 2009.

Enhanced Support for Data Export Reliability

This release improves the reliability of data exports from Simphony workstations to Reporting and Analytics. Export Reliability enhancements provide Reporting and Analytics with more information about the status of workstations and transactions. This includes information such as whether a workstation has been taken offline or manually closed using the Close Application button. Other statuses reported on include locked workstations, and whether all transactions have been posted or not in order to run their daily reporting. Changes have also been made the Close Application button functionality and the Unlock workstation functionality.

Workstations now send a message to CAPS when they are closing. CAPS knows which offline workstations are deliberately closed and which are offline for other reasons (for example, network communication issues). If a workstation sends a Closed message to CAPS, CAPS can ignore it in the Data Export Reliability tasks. When the workstation starts, the Data Export Reliability workstation task is triggered with an Online status.

When a workstation is closed using the Close Application button, the system counts the number of service totaled checks and pending transactions. If data export reliability tasks are configured and there are outstanding service totaled checks or pending transactions, the POS client prompts the workstation operator (with Yes or No) to complete those transactions before closing.

When a workstation is locked, the unlock message now contains the additional option Close Application. Selecting Unlock checks whether the database is up-to-date. If so, the workstation will be unlocked. If the database is not up-to-date, the system prompts the workstation operator to update the datastore.

The new Task Type 7 - Export Reliability has been added to the Task Schedules module. This option lets you run and identify Export Reliability tasks separately from the EOD Settlement tasks in logs.

Several Posting Status Descriptors have been added to provide information to Reporting and Analytics regarding the status of workstations and transactions.

See the Oracle MICROS Simphony Configuration Guide—specifically the Configuring Task Schedules for Export Reliability topic, and the Oracle MICROS Simphony Manager User Guide—specifically the Locking and Unlocking POS Operations From the Property and Closing a Workstation topics for more information.

Menu Item Screen Look Up (SLU) Enhancements

Support for Additional SLUs per Menu Item

You can now assign each menu item definition to a maximum of eight different SLUs (increased from one SLU) in the Menu Item Maintenance module. This allows flexibility in building workstation pages that are customized to use dine in, take away, and carry out, and shows the menu items supported by the order type.

See the Oracle MICROS Simphony Configuration Guide—specifically the Configuring Screen Look Ups for Menu Items topic—for more information.

Support for Menu Item Master Group SLUs

You can now assign a Menu Item Master Group to a SLU that is applied to a workstation page, which enables easy addition to the page without hard coding individual menu items on the page. The system automatically generates the Master Group SLU button on the page, hastening configuration of the items. You can configure a maximum of 32 Menu Item Master Group SLUs in the new Menu Item Master Group SLU Names module. The Menu Item Maintenance module shows the Master Group column with the Menu Item Master Group SLU assignments. The Page Design module now contains a new Screen Lookup Type value of Master Group.

See the Oracle MICROS Simphony Configuration Guide—specifically the Configuring Menu Item Screen Look Ups by Menu Item Master Group topic—for more information.

Support to Reduce Combo SLU Size Using Menu Levels

You can use Menu Levels to configure the SLU menu item sizes that appear on a workstation page. This enhancement reduces the number of items shown in a SLU, making it easier for workstation operators to locate the right combination of menu items and sizes for a combo meal without scrolling through many lists. The list of items in the SLU changes based on the Menu Level. If there are no Menu Levels configured, all SLU items appear.

See the Oracle MICROS Simphony Configuration Guide—specifically the Creating Combo Meals topic—for more information.

Menu Item Printing Enhancements

Support to Exclude Printing of Unpriced Condiments

You can now prevent a condiment from printing on the guest check and customer receipt if it does not have an associated price. For example, if there is no charge for lettuce on a sandwich, you can configure the lettuce condiment to not print. If there is a charge for avocado on a sandwich, you can configure the avocado condiment to print. The new options 79 - Do not print unpriced condiments on Guest Checks and 80 - Override do not print unpriced condiments on Guest Checks in the Menu Item Classes module let you define the printing of unpriced condiments.

See the Oracle MICROS Simphony Configuration Guide—specifically the Configuring Menu Item Classes topic—for more information.

Support for Printing Combo Meal Side Items with Combo Meal Parent Item

You can now configure side items within a combo meal to print to the same order device as the combo meal parent item. For example, you can configure a ribeye steak as the combo parent item, Side 1 as mashed potatoes, and Side 2 as broccoli. When printing to the kitchen order device, it is preferable that the side items also print at the same order device with the steak. You can configure this type of printing using the new option 11 - Send to Combo parents order devices in the Combo Meal Groups module.

See the Oracle MICROS Simphony Configuration Guide—specifically the Creating Combo Meal Groups topic—for more information.

Support for Authorizing Zero Amount Tip

An administrator can require authorization to declare that $0 tips were collected. When an employee clocks out, the system can prompt them to declare direct tips. If the employee enters a zero amount, the system checks to see if the employee user is authorized to do so before accepting the amount. If they are not privileged to enter a zero amount, an authorized user must approve the action before the employee can continue. This feature is useful in environments where the tip information is reported to government agencies for tax reporting because it helps to ensure that wait staff are not under reporting the tips earned.

The new transaction role privilege 303 - Authorize/Perform a zero Direct Tip lets you disable a $0 direct tip for some users and enable it for others.

See the Oracle MICROS Simphony Configuration Guide—specifically the Configuring Tip Tracking and Reporting topic—for more information.