9700 MAN AtoZFeatureRef

Large Enterprise Solutions
A to Z
Feature
Reference
Manual
Copyright 2002
MICROS Systems, Inc.
Columbia, MD USA
Part Number: 100151-506
Declarations
Warranties
Although the best efforts are made to ensure that the information in this manual is
complete and correct, MICROS Systems, Inc. makes no warranty of any kind with
regard to this material, including but not limited to the implied warranties of
marketability and fitness for a particular purpose. Information in this manual is
subject to change without notice. No part of this manual may be reproduced or
transmitted in any form or by any means, electronic or mechanical, including
photocopying, recording, or information recording and retrieval systems, for any
purpose other than for personal use, without the express written permission of
MICROS Systems, Inc.
MICROS Systems, Inc. shall not be liable for errors contained herein or for
incidental or consequential damages in connection with the furnishing,
performance, or use of this manual.
Trademarks
Windows is a registered trademark of Microsoft Corporation.
FrameMaker is a registered trademark of Adobe Corporation.
Printing History
New editions of this manual incorporate new and changed material since the
previous edition. Minor corrections and updates may be incorporated into reprints
of the current edition without changing the publication date or the edition number.
Edition Month Year Software Version
1st February 2002 1.5
2nd July 2002 1.7
ii
Table of Contents
Preface
1-ii Why Read This Manual?

1-vi Notation Conventions
A
A-1 @/For Function
A-3 Add Check
A-10 Adjust Closed Check
A-13 Amount Paid vs. Amount Due Display Option
A-14 Audit Trail
A-15 Autofire
A-22 Autocut Printing
A-24 Auto Menu Level
A-26 Autosequences
B
B-1 Backup PC
B-2 Banquet Team Service
B-7 Bar Code Reader Interface
B-8 Batch Autosequences
B-10 Begin/Pickup Check
B-14 Beverage Control
B-22 Block Settle Checks
B-23 Block Transfer Checks
B-26 Breaks
B-28 By-Round Guest Check
9700 HMS A to Z Feature Reference Manual iii

Table of Contents
C
C-1 Cancel Transaction
C-4 Cash Drawer
C-12 Cashiers
C-16 Chain & Fire
C-18 Charged Tip
C-22 Check Number
C-24 Clock In/Out
C-26 Coin Changer Interface
C-27 Condiment Handling
C-34 Confidence Test
C-35 Configurable Number of Guests Confirmation Prompt
C-36 Consolidation
C-37 Cover Charge Handling
C-39 Credit Authorization Interface
C-40 Credit Card
C-45 Currency
C-50 Customer Display
C-53 Customer Receipt
D
D-1 Data Redundancy
D-2 Database Backup and Database Restore
D-4 Database Maintenance
D-8 Date and Time Format
D-10 Default Touchscreens
D-13 Descriptors
D-16 Discounts
D-27 Disk File
D-30 Disk Full Warning
D-33 Dopplebon Printing
E
E-1 Edit Detail
E-6 Employee Class Field Editing Privileges
E-7 Employee Magnetic Cards
E-11 Employee Meals
E-16 Enhanced Backup and Takeover (EBUTO)
E-18 Error Corrections
E-19 Error Log
E-21 Euro Currency Conversion
E-28 Euro Printing
iv
F
F-1 Family Group
F-4 Fast Transaction
F-9 Fixed Price Meal
F-24 Food & Beverage Interface
F-27 Function Keys
F-30 Function Look Up Keys
G
G-1 Grace Periods
G-4 Guest Check
G-19 Guest Check Identification
G-26 Guest Check Information Detail Lines
G-30 Guest Count
H
H-1 Hand-held Touchscreen
H-2 Help Screens
H-8 Hexadecimal Entry
H-11 High Amount Lockout (HALO)
H-13 Hold & Fire
I
I-1 Itemizers
I-5 Interface File
I-7 Interface Script Language
J
J-1 Job Codes
J-4 Job Rates
K
K-1 Keyboards-User Workstation
K-11 Keyboard Workstation
9700 HMS A to Z Feature Reference Manual v

Table of Contents
L
L-1 Labor Day Start Time
L-3 Labor Week Start Day
L-5 Language Support
L-6 Limited-Availability Menu Items
L-8 Line-By-Line Customer Receipt
L-11 Local Order Output
M
M-1 Macros
M-4 Magnetic Card Reader
M-7 Major Group
M-10 Media Pickup/Loan Tendering Keys
M-12 Multi-tasking Capability
N
N-1 No Sale Key
N-3 Number Lookup (NLU)
O
O-1 On-Demand Guest Check
O-4 Open Check Block Settlement
O-8 Open and Closed Check Files
O-12 Order Output
O-19 Order Redirection
O-21 Order Types
O-25 Overtime
vi
P
P-1 PC Workstation
P-2 Period Totals
P-5 Pickup Check SLU/On Hold Items
P-6 PMS Interface
P-8 PMS Inquire
P-10 PMS Posting
P-15 PMSwait
P-20 Pop-up, Stay-down Functions
P-24 Post Sales
P-27 Preserve Formatting Time Field
P-28 Prices
P-32 Print Final Tender at Top of Form
P-33 Print Groups
P-35 Printers
P-40 Print Two Guest Checks
R
R-1 Reference Entry
R-5 Remote Database Maintenance
R-7 Re-open Closed Check
R-10 Repeat Round Function
R-12 Report Groups
R-14 Report Writer
R-17 Reprint Check
R-20 Return Items
R-24 Revenue Centers
R-33 Round Balance Due (Finnish Rounding)
R-36 Round Tender to Next Highest Dollar
9700 HMS A to Z Feature Reference Manual vii

Table of Contents
S
S-1 Sales Itemizers
S-2 Scale Interface
S-3 Screen Display Features
S-10 Screen Lookup (SLU)
S-11 Seat Handling
S-17 Security - Access Levels
S-18 Servers - Employee Definition
S-19 Service Charge
S-26 Service Total
S-30 Serving Periods
S-33 Shared Definition Files
S-35 SLU Sort Priorities
S-36 Soft Check
S-38 Sort Options
S-45 Special By-Round Operator
S-47 Split Check Functions
S-48 SQL Access
S-49 Stay-down
S-50 System Interface Module
T
T-1 Table Management System
T-12 Tables
T-17 Tax
T-28 Tax - Canadian (GST)
T-31 Tax Exempt Coupon
T-34 Tax - Florida Surcharge
T-38 Tax - Japanese
T-41 Tax - Philippine
T-43 Tax - Singapore
T-44 Tax - Taiwanese
T-46 Tax - Thai
T-51 Tender/Media
T-57 Tender Multiplication
viii
T
T-61 Time Cards and Time Chits
T-63 Time Clock Schedule
T-66 Time Periods
T-69 Tips Handling
T-80 TouchAdvantage
T-82 TouchDetail
T-84 TouchEdit
T-102 Touchscreen Icons
T-123 TouchShare
T-124 TouchSplit
T-141 Tracking Groups
T-149 Training Mode
T-151 Transfer Checks
T-156 Translation Utility
T-164 Two-Color Printing on Guest Check Header/Trailer
U
U-1 User Workstation
U-9 User Workstation Procedures
V
V-1 Validation Printing
V-4 Video Display Unit (VDU)
V-7 Video Display Unit (VDU) - Line-By-Line Display
V-18 Void Item
V-24 Void/Return Reason Codes
V-30 Voucher Printing
WXYZ
WXYZ-1 Weighed Menu Items
WXYZ-4 Zero-Payment Transactions
Index
9700 HMS A to Z Feature Reference Manual ix

Table of Contents
x
Preface
In This Chapter
In this preface, you will find information about the organization,
conventions, and contents of this manual.
Why Read This Manual?........................................................................... ii

Notation Conventions............................................................................... vi
9700 HMS A to Z Feature Reference Manual i

Preface
Why Read This Manual?
Purpose
The purpose of this manual is to provide MICROS customers with an easy-to-
find, complete, and cross-referenced description of all 9700 features. Cross-
referenced information will guide you to the 9700 User’s Manual for more
information on how to use the features, and to the 9700 Programming Manual for
more information on how to enable or program the features.
This manual is not intended as a training manual or a site survey manual. It does
not contain information about how to program any feature.
Who Should Use This Manual?

Trained MICROS installers and dealers should read this manual as a reference for
descriptions of 9700 features.
ii
Preface
Finding Additional Information

The MICROS 9700 HMS System comes with a complete documentation suite
comprising hardware and software reference libraries, and individual manuals that
support optional 9700 System modules or features. Each manual is listed in the
table below and can be ordered by part number directly from MICROS Systems,
Inc.
The 9700 and can be

is comprised of these which include information
HMS ordered by part
manuals... about...
System... number...
9700 HMS A to Z Feature w all 9700 System features 100151-506

Reference Manual w modifying the database for
each feature
9700 Feature Overview w an introduction to the 9700 100151-523
Manual System and descriptions of
major features
9700 HMS Property w basic instructions on how to MD0006-008
Maintenance Guide maintain and update an
Software existing 9700 System
Library database
9700 HMS SQL Manual w importing and exporting data 100151-502
into and out of the 9700
database
w 9700 System files, fields, and
status flags
9700 HMS System Setup w installing/upgrading the 9700 100151-507
Manual System software
Hardware 9700 Site Preparation w preparing a site for MICROS 100151-508

Library Guide equipment installation
w AC power requirements
w environmental considerations
9700 HMS A to Z Feature Reference Manual iii

Preface
How This Manual is Organized

This manual is a features encyclopedia and serves as the primary reference for the
9700 System. Features are sorted alphabetically, with each section listing the
related features, large or small. This manual will be particularly useful to new
installers, who are unfamiliar with MICROS products.
Each topic in the A to Z Feature Reference provides the following information
if applicable:
w Description
w Usage
w Examples
w Reports
w Enabling
w Related Topics
Description
This section will provide a brief definition and description of the feature.
Usage
This section provides information about the typical use of this feature and any
choices that you must make. For example, various layouts are discussed in the
Usage section of the keyboard feature. More information about the use of a
feature can be found in the 9700 User’s Manual.
Examples
This section will provide an extended example for features that may be complex
or difficult to understand. However, short examples may be found in any of the
other sections.
Reports
This section will provide a list of all report fields affected by the feature. More
information about reports may be found in the 9700 Reports Manual.
Enabling
This section will provide a summary of the files, fields and options that must be
programmed to make the feature work. Additional programming information can
be found in the 9700 Help system within the 9700 application.
iv
Preface
Related Topics
This section will guide you to another section if you need more information about
a topic related to the feature.
9700 HMS A to Z Feature Reference Manual v

Preface
Notation Conventions
Keys
Throughout this manual, keys on a PC or User Workstation keyboard are shown
enclosed in square brackets. Examples:
[Enter]
[Shift]
[Page Up]
Prompts
Messages that may appear on the screen during the programming process are
shown in quotes. Example:
“Select Menu Item Range”
vi
Preface
Symbol
This symbol is used to bring special attention to a related

feature.
This symbol is used to indicate a special tip for using the

current feature..
This symbol indicates that care should be exercised when

programming a feature or performing an action.
Design and Production

This manual was written with Adobe FrameMaker. Some illustrations and
diagrams were designed in CorelDraw and Microsoft Visio.
9700 HMS A to Z Feature Reference Manual vii

Preface
viii
A
@/For Function
Description
The [@/FOR] key is used to:
w Post a quantity of items via an NLU
w Split pricing of menu items that have an “open” price. (Split pricing allows an
operator to order odd quantities of items that are usually sold in fixed
amounts.)
Usage
This key can be used to enter three NLU items (item #5), e.g, press 3 @ 5 [Menu
Item NLU].
The @/For key can also be used to enter split pricing. If you order 3 items @ “4/
1.00”, this key would be pressed twice in the sequence 3 @ 4 FOR $1.00 [Menu
Item].
9700 HMS A to Z Feature Reference Manual A-1

@/For Function
Enabling
1 Keyboards
2 Touchscrns & Keyboards | Keyboards | Key Configuration | [Type =
Function] | [Function Key Categories = Transaction] | Link
R 600 - @/For
1 WS Touchscreens
2 Touchscrns & Keyboards | WS Touchscreens | Touchscreen Screen |
[Function Key Categories = Transaction] | Number
R 600 - @/For
Related Topics
w “Function Keys” on page F-27
w “Prices” on page P-28
A-2
Add Check
Add Check
Description
The Add Check feature is a function of the Add/Transfer key. It provides the
ability to combine the transaction detail of two or more guest checks. Transaction
detail from the original check is added to that of the destination check. And,
because all of the detail from the original check is added to the destination check,
the System automatically reduces the balance of the original check to zero and
closes it. Once the original check is closed, it cannot be adjusted.
Usage
Adding Checks
George and Samantha arrive separately, are seated at separate tables, and a new
guest check is begun for each. They meet at the salad bar and exclaim, “I didn’t
see you come in!”, then they decide to sit together. Samantha wins the coin toss,
and asks that George’s check be added to hers.
To combine two guest checks, perform the following steps:
w Pick up the destination guest check.
w Press the appropriate [Add/XFR] key.
w Enter the identity of the of the original check (can be table number, check
number, or Guest Check ID). The UWS prompts, “ADD THIS CHECK?”
w Press [Enter].

Add Check
The transaction detail from the original check is now added to the destination
check, and the original check is closed to 0.00. When the guest check is printed,
the System includes information indicating that detail was added from another
check. For example, the printed check would look like this:
George’s check,
MICROS 87009700 before being added to
Fine Dining System Samantha’s.
411 GUSTINO
------------------------------
CHK 196 JUL24’94 11:29AM GST 1
------------------------------
MICROS 87009700
1 TURKEY CLUB 3.75 Fine Dining System
1 LARGE FRIES 1.25
1 COLD SLAW 1.00
1 CRAB SOUP 4.75
2 IMPORTED BOTTLE 5.70 411 GUSTINO
------------------------------
SUBTOTAL 16.45 CHK 195 JUL24’94 11:27AM GST 1
SALES TAX 0.83 ------------------------------
BALANCE DUE 17.23
---ADD TO CHK 195 01:25PM--- 1 PERRIER 1.25
1 SPINACH SALAD 5.25
HOUSE
1 CRAB SOUP 4.75
1 GLASS WINE 2.50
SUBTOAL 13.75
SALES TAX 0.56
BALANCE DUE 14.31
ADDED FROM CHK 196

1 TURKEY CLUB 3.75
1 LARGE FRIES 1.25
1 COLD SLAW 1.00
1 CRAB SOUP 4.75
2 IMPORTED BOTTLE 5.70
Samantha’s check, after
George’s check has been SUBTOTAL 30.20
SALES TAX 1.39
added. BALANCE DUE 31.59
Add Check Methods

The Add Check function can be initiated in a number of ways—Once the
destination check has been picked up, the Add Check function can be initiated by
pressing any one of the following keys:
w Add/Trans By Check Number—This method provides the ability to use the
check number as the means of identifying the original guest check. The
selected check can reside in the operator’s assigned revenue center or in the
current revenue center.
w Add/Trans By #, RVC?—This method provides the ability to use the check

number as the means of identifying the original guest check. Additionally, the
System will prompt the operator for the identity of the revenue center in
which the original guest check resides.
A-4
Add Check
w Add/XFR By # RVC1 - Add/XFR By # RVC 8—This method provides the

ability to use the check number as the means of identifying the original guest
check from one of the eight revenue centers that may be assigned to the
UWS.
w Add/Trans By Table—This method provides the ability to use the table

number as the means of identifying the original guest check. The selected
check can reside in the operator’s assigned revenue center or in the current
revenue center.
w Add/XFR Tbl RVC ?—This method provides the ability to use the table
number as the means of identifying the original guest check. Additionally,
the System will prompt the operator for the identity of the revenue center in
which the guest check resides.
w Add/XFR Tbl RVC 1 - Add/XFR Tbl RVC 8— This method provides the
ability to use the table number as the means of identifying the original guest
check from one of the eight revenue centers that may be assigned to the
UWS.
w Add/XFR Check By ID—This method provides the ability to use a guest

check ID as the means of identifying the original guest check.
w Add/Trans Check SLU—This method generates a touchscreen that displays a

key for each open guest check (with the exception of the currently open
check) within the revenue center. Open guest check keys are sorted in the
SLU according to the following criteria:
If... Then...
...a guest check includes an ID, a check ...the ID becomes the primary
number, and/or a table number... sort criteria, and all guest checks
with an ID are displayed first in
alphabetical order.
...a guest check includes a table number ...the table number becomes the
and a check number, but no ID... primary sort criteria, and all
guest checks with table numbers
are sorted by table/group. They
are displayed after checks with
an ID.
...a guest check includes a check number ...the check number becomes the
only... primary sort criteria, and all
guest checks are sorted
numerically by check number.
They are displayed after checks
that have an ID and a table
number.

Add Check
If... Then...
...guest checks belonging to other ...they are sorted according to

employees are displayed... the above criteria, and displayed
after all of the current
employee’s checks. These
checks appear with an asterisk
(*) which indicates they belong
to another employee.
Any of these functions (by check, table number, or Guest Check ID to any
Revenue Center or to a specific one) can be included in a Function Lookup (FLU)
key.
If Guest Checks are to be added across Revenue Centers, the Order

Type tax type programming must be identical in each Revenue Center.
Adding Detail to the Destination Check

Detail being added to the destination check may be posted to the transaction detail
in one of the following ways:
w By adding the detail to seat zero (System default)—Transaction detail from
the original check is posted to seat 0 on the destination check.
w By adding the detail to newly assigned seat numbers—(RVC Information |

RVC Parameters | Options | General | Assign seat numbers to added check
detail)—When this option is enabled, transaction detail from the original
check is posted to the next available seat number(s) on the destination check.
A-6
Add Check
w By keeping the seat numbers from the original check—RVC Information |

RVC Parameters | Options | General | Keep seat numbers on added check
detail—When this option is enabled, the seat number associated with the
transaction detail from the original check is carried forward to the destination
check. This means that it is now possible to maintain seat number identity
from one check to another when using the Add Check Feature. It also means
that it is possible to combine transaction detail by seat number. Consider this
example:
1 1 Coke 1.00 1* 1 1 Chardonnay 2.50 1*
2 1 Crab 4.50 1* 2 1 Clams Casino 3.50 1*

3 1 Coke 1.00 2*
4 1 Crab 4.50 2*
Detail associated with the Original check Detail associated with the Destination check
1 1 Chardonnay 2.50 1*
2 1 Clams Casino 3.50 1*
3 1 Crab 4.50 1* Detail from the Original check
4 1 Coke 1.00 1* remains associated with seat 1
on the Destination check
5 1 Crab 4.50 2*
6 1 Crab 4.50 2*
Detail on the Destination check after the Add transaction is completed
Reports
Financial Reports (Revenue Center and Employee)

If checks are added between Revenue Centers or between operators, the checks
post to the following totals on these reports:
w Begun
w Transferred In
w Paid
w Transferred Out

Add Check
Employee Closed Check Report - Report Writer Version

w An “A” prints next to the original check. A status line prints “Added to Check
nnnn”, where nnnn is the number of the destination check.
w An “a” prints next to the destination check. A status line prints “Contains n
Checks”, where n is the number of checks that were added to this check.
Employee Closed Check Report - UWS Version

w An “A” prints next to any check involved in an add transaction (i.e., either an
original check or a destination check.)
Enabling
1 Keyboards
Function] | [Function Key Categories = Check Begin/Pickup] | Link
R 437 - Add/Trans Check

Function] | [Function Key Categories = Check Operations] | Link
R 499-519 - Add/Trans Check
1 WS Touchscreens
[Function Key Categories = Check Begin/Pickup] | Number
R 437 - Add/Trans Check

[Function Key Categories = Check Operations] | Number
R 499-519 - Add/Trans Check
1 Employee Class
2 Personnel | Employee Maintenance | [Sort By Class] | Guest Checks |
Guest Check Control
R Authorize Adding of Checks in Same Revenue Center

R Authorize Adding of Checks Between Revenue Centers
A-8
Add Check
Optional Settings
The following options may be set on a discretionary basis:
1 Revenue Center Parameters

2 RVC Information | RVC Parameters | Format | Format Options
R Service Round Totals Include Current Round Only—If this option
is enabled, and the Add function is used, the System will not recognize
the summary totals as having changed simply as a result of combining
two or more checks together. As a result, summary totals will not be
printed. In order to print combined summary totals, after the Add
transaction is completed, use the [Reprint] key to service total the
check. The System will recognize that the summary totals have
changed and print the new combined total.
2 RVC Information | RVC Parameters | Options | General
R Assign Seat Numbers to Added Check Detail—Set ON to post detail
from the original check to the next available seat number on the
destination check.
R Keep Seat Numbers on Added Check Detail—Set ON to keep the
seat numbers assigned to the detail on the original check the same
when it is added to the destination check. This option overrides the
setting of the option Assign New Seat Numbers to Added Check
Detail mentioned previously. This option is ignored if there are fixed
price meals on the original check.
2 RVC Information | RVC Parameters |General
R Add/Transfer Revenue Center fields—Specify up to eight specific
revenue centers that are addressed by an [Add/XFR] key.
Related Topics
w “Block Transfer Checks” on page B-23
w “Transfer Checks” on page T-151

Adjust Closed Check
Adjust Closed Check
Description
This function allows an operator to change the type of tender that was used to
close a check. It also allows an operator to add or change a charged tip.This
function is available on all UWS devices except for the Hand-held Touchscreen.
Usage
This feature uses the line number void function to remove any or all payments
(along with their charged tips, if any). If there was change due when the check
was originally tendered, that entry must be removed first.
Example
A guest check is closed with a tendering key. After the customer pays and leaves,
the server realizes that the customer paid with a VISA card and the check was
closed to American Express. The server uses the [Adjust Closed Check] key to
change the tender from VISA to American Express.
If a cashier declaration is required for tendering (Cashier

Totals Declaration Req with TMed and Tips Paid option
under RVC Information | RVC Parameters | Posting &
Control | Control) is enabled, a cashier must be declared
in order to adjust a closed check.
A-10
Adjust Closed Check
When a closed check is adjusted, the result prints at the designated guest check
printer. The detail that prints is determined by the nature of the original check:
w If the adjusted check was an On-demand guest check, or a fast transaction
that was service totalled by an On-demand operator, the entire check is
reprinted, showing the new information (e.g., the new method of payment).
w If the adjusted check was a By-round guest check, a Special By-round guest
check, or a fast transaction that was service totalled by a By-round operator, a
chit prints that shows the nature of the adjustment (e.g., the void of the
original payment, and the posting of the new payment).
In either case, the line ADJUST CLOSED CHECK prints at the top of the
transaction detail in double-wide characters.
Reports
Employee Closed Check Reports

For Report Writer reports, a “j” prints in the status field for any check that has
been adjusted. The UWS reports use a capital letter (“J”).
Enabling
1 Keyboards
Function] | [Function Key Categories = Check Begin/Pickup] | Link
R 422 - Adjust Closed Check
1 WS Touchscreens
[Function Key Categories = Check Begin/Pickup] | Number

Adjust Closed Check
Optional Settings
The following privilege options may be set on a discretionary basis:
1 Employee Class
2 Personnel | Employee Maintenance | [Sort By Class] | Printing | Check/
Receipt
R Authorize/Perform Reprinting of a Closed Check

2 Personnel | Employee Maintenance | [Sort By Class] | Guest Checks |
Guest Check Control
R Authorize/Perform Closed Check Pickup

R Authorize/Perform Closed Check Adjust

R Fast Transactions Do Not Generate Closed Check Records
2 RVC Information | RVC Parameters | Posting & Control | Control
R Cashier Totals Declaration Required with Tender/Media and Tips Paid
R Allow Overtender of Closed Checks
Related Topics
w “Guest Check” on page G-4
w “Line Number Void” on page V-18
w “Re-open Closed Check” on page R-7
A-12
Amount Paid vs. Amount Due Display Option
Amount Paid vs. Amount Due Display Option
Description
This feature allows the flexibility of displaying the amount paid versus the
amount due on the 8-character customer display.
Enabling
1 Workstation File
2 System Hardware | Devices | Options | Type Definition
R Show Amount Paid on Rear Display

Audit Trail
Audit Trail
For a complete description of this feature, see “Audit Trail” in Chapter 7 of the
9700 Feature Overview Manual.
A-14
Autofire
Autofire
Description
The Autofire function allows a server to add items to a guest check and hold the
order until a pre-set “fire” time, when the order is sent to the remote order
devices. Unlike the Hold & Fire function, where the server must manually select
the “fire” key to send the order, Autofire lets you schedule an order in advance,
then, when the scheduled time arrives, the order is automatically fired by the
System and the charges are posted. Menu items post at the time the check is fired,
with the remaining totals (e.g., discounts, service charges, gratuities, etc.) posting
when the check is tendered for payment.
Usage
The Autofire function is ideal for situations such as room service orders, where
the order can be entered into the System, then held for posting and firing at a
specified date and time. You simply ring up the menu items, press the Autofire
button, then enter the date (e.g., 31202) and time (e.g., 16:30 for 4:30 pm,
military format must be used) when the order is to be fired. After confirming this
entry, the check is scheduled in the System.
The Time To Fire field is available for use in SIM scripts

and SQL queries.
Printing
Autofire checks are printed from the default Autofire workstation defined in the
RVC Parameters file. If a default workstation is not specified, the last
workstation from which a check was created will be used. Autofire printing is
sent to the backup printer if the primary printer is not functioning; however, if the
backup printer is not functioning, the print job is lost and totals will be posted.
The workstation will notify the user when a print job is being sent to the backup
printer.

Autofire
Check Pickup and Editing

Autofire checks can be picked up by check number or by using the Pickup SLU
key. New menu items can be added, while items that have not been fired can be
voided. After adding new items, you must press the Autofire key again. The
System will then display a prompt that allows you to confirm the original fire time
of the check or change it to a new time. An Autofire check can be cancelled in full
by simply voiding all menu items from the check. You can also pick up an
Autofire check at any time and manually fire it by pressing the Service Total key.
Autofire checks can be picked up from a Mobile MICROS hand-held device,
however, you can only service total the check immediately or cancel out of the
transaction.
When the Autofire functionality is enabled, these checks will be included in the
Open Check SLU used to generate the Open Check Report. When the open checks
are displayed on the screen, Autofire checks will be listed last. They will display
in inverse mode (except on UWS/3s and WinStations), sorted by fire time, with an
AUTOFIRE CHECK banner printed at the top of the check. If multiple checks
have the same “fire” time, the checks will be sorted by check number.
Touchscreen Programming
There are several touchscreen programming requirements for the Autofire
function. You must create an Autofire button on an appropriate touchscreen, that,
when pressed, displays a date/time entry screen for specification of the order fire
date and time. On page A-19 you will find an example of how the date/time entry
touchscreen might be programmed.
Autofire Delays
If, for some reason, an Autofire check is not fired within ten minutes of its
scheduled time, a banner will be printed at the bottom of the check stating the date
and time it was originally set to be fired. Autofire checks that have not been fired
within 24 hours of their scheduled time will be purged from the System. The
message CHECK NUMBER ### PURGED! will be displayed on the default
workstation to inform the user of this action.
Autofire Rules
And now, the official Autofire Rules list:
w An Autofire check can be scheduled from 1 to 150 days in advance, with the
default being 30 days.
w A previously posted guest check cannot be used as an Autofire check.
w Once an Autofire check has been fired, it then becomes a regular check and all
related check functions can be performed.
A-16
Autofire
w Menu item additions and voids on Autofire checks are treated as previous
round items, while tender changes are treated as current round items.
w Split checks are not allowed.
w If the check is paid in full or changed to a different tender, all menu items are
immediately fired to the remote order devices.
Reports
w Autofire Check Report
w Open Check Report
Enabling
1 System Parameters
2 System Information | System Parameters | General
R Use DDMMMYY Format—This option may be enabled to support
international sites that require this date format. Dates will be displayed
and printed as 25SEP’02, for example, instead of SEP25’02.
1 RVC Parameters
2 RVC Information | RVC Parameters | Autofire
R Autofire Workstation—Select the workstation from which Autofire
checks will be fired and printed.
R Autofire Checks Allowed—Specify the number of Autofire checks
that may be scheduled. The maximum allowed is 9999.
R Default Autofire Tender/Media—
R Print Autofire Memo at time of entry—Enable this option to have a
memo chit automatically print when an Autofire check is entered into
the System.
R Print Guest Check at time of Autofire—Enable this option to have a
guest check print when an Autofire check is fired. Once an Autofire
check has been fired, it then becomes a regular check and all related
check functions can be performed.

Autofire
1 Tender Media
2 System Information | Tender Media | General
R Create a new Tender Media record.
R Name—Enter Autofire as the name of the new key.
R Key Type—Select Service Total.
2 System Information | Tender Media | <Select Autofire Key> | Key Type |
Category=POS Ops Behaviors
R Hold Entire Check for Autofire—Select this option to enable

Autofire functionality for this Tender Media key. All other Service
Total options are disabled when this option is enabled.
2 System Information | Tender Media | <Select Autofire Key> | Menu Levels
R Specify the menu levels on which the Autofire key is active.
2 System Information | Tender Media | <Select Autofire Key> | Output
R Tender Output—Select the output device(s) for Autofire checks.
2 System Information | Tender Media | <Select Service Total Key> |
R Preserve Hold Status From Previous Round—When using the

Autofire feature, this option must be disabled for the Service Total key.
Since all menu items on Autofire checks are already on hold, these
items will not fire if this option is enabled.
A-18
Autofire
1 Touchscrns & Keyboards

2 Touchscrns & Keyboards | WS Touchscreens | Touchscreen Screen
R Create a touchscreen, similar to the one shown below, for date and
time entry for Autofire checks.
w Screen Name—Enter a name for this touchscreen, such as

Autofire Screen.

Autofire
w Key—Current MMDDYY
w Legend—Specify Current MMDDYY for the key label.
w Type—Select 9 - Keypad.
w Number—Select 22 - Current MMDDYY.
w Key—Enter
w Legend—Specify Enter for the key label.
w Number—Select 12 - Enter.
w Key—Clear
w Legend—Specify Clear for the key label.
w Number—Select 13 - Clear.
w Key—Cancel
w Legend—Specify Cancel for the key label.
w Type—Select 11 - Function.
w Function Key Categories—Select Movement.
w Number—Select 20 - Cancel.
w Key—Numbers 0-9 and 00 (repeat these steps for each number)
w Legend—Specify a number 0-9 for the key label.
w Number—Select the appropriate Numeric setting (0-9 or 00).
w Key—Decimal Point
w Legend—Specify “.” for the key label (do not include the
quote marks).
w Number—Select 11 - Decimal “.” key.
R Add an Autofire button to an appropriate touchscreen, such as the
Food shell.
w Legend—Enter a key label, such as Autofire.
w Type—Select 7 - Tender/Media.
2 Touchscrns & Keyboards | WS Touchscreens | Touchscreen Assign

R Autofire Time Edit Screen—Select the Autofire screen you created
previously (for date/time entry).
A-20
Autofire
1 UWS Autosequences
2 Reporting | UWS Autosequences
R Create a new Autosequence.
w Autosequence Name—Enter a name for the Autosequence, such
as Autofire Reporting.
2 Reporting | UWS Autosequences | <Select Autosequence> | <Add

Autosequence Step>
R Type—Select Report.
R Report #—Select 30-Autofire Open Check.
R Set the remaining fields on the General tab as appropriate.

Autocut Printing
Autocut Printing
Description
This feature is provided by the Epson U200B Stand-alone Autocut Roll Printer.
After Guest Checks, Receipts, etc., are printed, the printer will automatically cut
the paper below the printed information.
Epson U200B Rollcut Printer
Usage
Autocut printers are often used as remote printers. When several orders print at
the same time, the autocut feature helps separate orders quickly.
Enabling
1 Device Table
2 System Hardware | Devices | General
R Device Type—Select 2 - Roll Printer.
2 System Hardware | Devices | Printers
R These fields assign certain printers for specific tasks (e.g., Customer
Receipt Printer, Credit Card Voucher Printer, etc.)
A-22
Autocut Printing
1 Order Devices
2 System Hardware | Order Devices
R Fields in this file assign specific printers to remote and local order
printing.
Optional Settings
1 System Parameters
2 System Information | System Parameters | Reporting | Reporting Options
R Partial Cut Between Pages and Full Cut Between UWS Rpts—This
option causes a partial cut (if not set as unlimited - page length=0) to
be made between UWS Report pages and a full cut to be made
between UWS Reports.

R Partial Cut Between Customer Receipts (Autocut Printers
Only)—This option determines if a full or partial cut will be made
after the customer receipt prints.
1 Order Devices
2 System Hardware | Order Devices |General | Order Device Options
R Partial Cut on Autocut Printer—This option determines if a full or
partial cut will be made after the order output. A full cut completely
separates an order receipt from the paper roll. A partial cut leaves it
attached by a small section.
Related Topics
w “Printers” on page P-35

Auto Menu Level
Auto Menu Level
Description
This Menu Levels tab in the Revenue Center Parameters file displays the Auto
Menu Level table and option boxes to indicate active days. These fields allow you
to program default transaction main menu levels and default transaction sub-menu
levels for up to eight time slots in a day or a week.
The Type Definition fields allow you to program the default main and sub-menu
levels to be active on specific days of the week.
When enabled, the default transaction main and sub-menu levels will
automatically change based on the time of day and the day of the week. They will
take precedence over the transaction menu levels defined in Revenue Center
Parameters File but otherwise are affected the same way by manual selection of
menu levels during a transaction.
Usage
This feature will allow you to change the menu level, and therefore the price or
availability of certain menu items at specified times. For example, a happy hour
price for drinks could begin automatically at 5:00 and end at 7:30, but only
Monday through Thursday.
A-24
Auto Menu Level
Enabling

2 RVC Information | RVC Parameters | Menu Levels
R For each Auto Menu Level, set the appropriate fields (e.g., Menu
Level, Start Time, End Time, etc.).
Auto Menu Levels cannot be programmed to have overlapping start

and end times on the same day.
1 Revenue Center Descriptors

2 RVC Information | RVC Descriptors | General | [Select a Category]
R Main Menu Level Names
R Sub-Menu Level Names
Related Topics
w “Menu Level Concepts” in Chapter 3 of the 9700 Feature Overview Manual

Autosequences
Autosequences
Description
An Autosequence is a pre-defined set of reports or other commands. An
autosequence can be used to:
w Access all reports
w Print to disk
w Print to the operator display or PC monitor
w Reset reports
w Select different report periods

Once an autosequence is created, any employee with the proper privileges may
generate a specific set of reports with a few keystrokes. This saves managers’ time
and, by keeping the procedures simple, reduces employee training time. A UWS
Autosequence can also be programmed as a macro, reducing the required number
of keystrokes even further.
There are two types of Autosequences—User Workstation Autosequences and PC
Autosequences.
Autosequence Viewing Options

Unlike most files in System Configurator, the PC Autosequence File and UWS
Autosequence File offer three viewing selections. In addition to the standard
Overhead and Detail displays, the contents of the file can be viewed as a Step
Summary. An example of a Step Summary is shown below.
The Step Summary view of an autosequence shows every step in the
autosequence, in a horizontal format. The size of this display limits the amount of
information that can be reproduced here.
A-26
Autosequences
UWS Autosequences
These are designed to be taken from a User Workstation. Reports may be output
to:
w the operator display
w a printer defined in the Workstation Table (usually a roll printer)
w a disk file.
Note that saved totals sets are not accessible by UWS Autosequences.
PC Autosequences
These autosequences may display on the PC monitor, may print to disk, or may
print at the defined report printer, usually a line printer connected to the PC on
which the report is taken. A PC Autosequence may be run while User
Workstations are operating, without interfering with transactions. PC
Autosequences can include tasks other than reports. You may also program
autosequences to:
w change the totals set(s)
w save a totals set(s)
w export database information
w save or reset the Audit Trail File or the Error Log File
w run an external program (i.e., non-9700 System application)
w call (execute) another autosequence in the midst of the current one. This
feature is described on page A-33.
PC Autosequences may be started from the Autosequencer module on the PC

screen.

Autosequences
Printers
Up to four line printers may be configured for each PC in the System. Printer
Setup String and Parameter fields are provided for each printer. Refer to “Printers”
on page P-35.
The Income Audit Report may be programmed to print as many as 30 columns,
which may require special printing considerations. For example, you may wish to
print this report in compressed mode and/or landscape format. For this reason, a
separate set of four Printer Setup String and Line Printer Parameters fields are
available in the Report Configuration File for the Income Audit Report.
If an autosequence is created that prints several reports, including the Income
Audit Report, and if there are separate Line Printer Parameters programmed for
the Income Audit Report, the autosequence selects the same printer entry from
each file.
PC Autosequence Type 4—Call Autosequence

Select this Type to cause the autosequence to execute another autosequence and,
upon its completion, continue with the next step in the original autosequence.
Autosequence Autosequence
#10 #27
Step 1
Step 1: System Tip Report
Step
Step 2: Call #27
Step
Step 3: Table Sales Report

Step 16
Step 4...
Step 3 in Autosequence #10 executes after

Autosequence #27 is complete.
A-28
Autosequences
Any autosequence parameters that are changed in the “called” autosequence are
returned to their original settings when the called autosequence is complete and
the next step commences. In the example shown below, the View parameter in
Step 3 of Autosequence #10 is programmed to Inherit. It will inherit “System”
from Step 2, not “Revenue Center” from Step 16 in Autosequence #27.
#10 #27
Step 1
Step 1: System Tip Report View: RVC
View: System
Step 16
Step 2: Call #27 View: RVC

View: Inherit
The View parameter in Step 3 inherits “System,” not

. “Revenue Center” from Step 16 of Autosequence #27.
If a report number is selected in the step that calls the autosequence, its
parameters (view, range, etc.) may be inherited by the called autosequence.
#10 #27
Step 1 inherits
Step 1
Step 1: System Tip Report View: Inherit “RVC” from Step
View: System
Step 5
Step 2: Call #27 View: System
View: RVC
Step 3 inherits
Step 16 inherits
“RVC” from Step 16
Step 2. Step 3: Table Sales Report “System” from
View: Inherit View: Inherit
The called Autosequence may inherit report parameters

from the original Autosequence, but the reverse is not

Autosequences
A called autosequence may in turn call another autosequence, to a maximum of 10

nested calls. Called autosequences may also be chained.
Step Step Step
Step Step Step
Step Step Step
Chain
Step Step
Step Step
Step Step
Remember to leave a trail of bread crumbs.
A-30
Autosequences
PC Autosequence Type 5—Report & Call Autosequence

Select this Type to cause the autosequence to generate a report, and then call
another autosequence. Refer to the description for Type #4 (Call Autosequence)
for an explanation of called autosequences.
#10 #27
Step 1
Step
Step 2: Job Code Report
Call #27
Step

Step 16
Step 4...
Autosequence #27 executes after the Job Code Report runs.

Autosequences
Control Step
Select this Type to cause the autosequence to pause, in order to allow the operator
to change the View of the next autosequence or the next step (e.g., from RVC #1
to RVC #3). All UWS activity is suspended for the duration of a control step. A
control step is usually used in conjunction with called autosequences.
#10 #27
Step 1
Step
Step 2: Control Step
Step
Step 3: Call #27

Step 16
Step 4...
Autosequence #10 pauses to allow the operator to select

the View for Autosequence #27.
Transaction Posting During PC Autosequence Execution

Picture the following series of events, which take place early one morning in an
establishment that is open for business 24 hours a day:
04:00 - PC Autosequence #1 begins.
04:01 - Revenue Center Financial Report is run.
04:02 - Transaction #357 begins at UWS #20.
04:03 - Transaction #357 posts.
04:04 - Employee Financial Report is run.
As a result of this series of events, the Employee Financial Report in this

autosequence will include transaction #357, but the Revenue Center Financial
Report will not. The sum of the Employee Financial Reports totals will be greater
than the total on the Revenue Center Report.
A-32
Autosequences
As you can see, allowing transactions to begin during an autosequence can result
in balancing problems. The Autosequence File offers the following Step Type
Definition to address this problem:
w Lock User Workstations in this Report’s View—(Reporting | PC
Autosequences | [Select Autosequence] | [Select Step] | Options)—Enable
this option to prevent operators from being able to perform certain
transactions on any UWS that is included in this step of the autosequence.
These transactions include beginning or picking up checks, posting totals,
etc. If operators are required to declare tips when clocking out, this Step Type
Definition prevents clocking out for the duration of this autosequence. The
UWSs are released if this autosequence cancels or finishes, or if the next step
in this autosequence has this type definition disabled.
If this feature is used, operators may complete any transaction that is in

progress when the autosequence begins. This may create another problem
situation, if transactions that were in progress when an autosequence began
are allowed to post during its execution. The following Step Type Definition
addresses this problem:
w Suspend Totals Posting—(Reporting | PC Autosequences | [Select

Autosequence] | [Select Step] | Options)—Enable this option to cause
transactions to be queued for posting after this step of the autosequence.
Transactions that are buffered to memory do not post to totals until the steps
that are programmed to suspend totals posting are completed.
Closed Check File Posting During PC Autosequence

Execution
Picture another series of autosequence events:
04:00 - PC Autosequence #1 begins.
04:00 - Revenue Center Financial Report is run.
04:00 - Employee Financial Report is run.
04:01 - Employee Tip Report is run.
04:01 - Transaction #357 is closed.
04:02 - Employee Closed Check File is reset.
Given these circumstances, one might expect that transaction #357 would not
appear on the Financial Reports and the Tip Report, but would appear on the
Closed Check Report, and would be reset with that report.

Autosequences
If the Step Type Definition Suspend Totals Posting is enabled, closed checks are
masked out of the reset. Any checks that are closed after the autosequence is
begun are masked out of the Closed Check File reset. These checks are retained in
the file, and will print and reset the next time the File is reset.
As shown in the example below, any closed checks that have a closed time stamp
later than 04:00 (the time that the autosequence began) will be masked out of the
report and reset of the Closed Check File that occurs at 04:02.
CHK OPENED/CLOSED PAYMENT

--- ----------------- --------
355 SEP25’94 03:55AM 33.09
SEP25’94 03:57AM
356 SEP25’94 03:58AM 16.25
CHK OPENED/CLOSED PAYMENT
SEP25’94 03:59AM --- ----------------- --------
357 SEP25’94 03:59AM 4.87 357 SEP25’94 03:59AM 4.87
SEP25’94 04:01AM SEP25’94 04:01AM
358 SEP25’94 04:00AM 21.86 358 SEP25’94 04:00AM 21.86
SEP25’94 04:01AM SEP25’94 04:01AM
Closed Check File at the time the Closed Check File after being reset
file is reset. as part of the autosequence. Any
checks with a closed time stamp later
than the autosequence start time
(4:00) are not reset and do not print
on the report. They remain in the file
until the next reset.
PMSwait Program
The PMSwait program is an 9700 program that sends a PMS inquire message over
a PMS interface, to determine whether or not the PMS is active. It is set up as an
External Program in a PC Autosequence. PMSwait is intended for use in an
environment in which the PMS interface is periodically shut down, and certain PC
Autosequences should not run if the interface is still active. Refer to “PMSwait”
on page P-15.
A-34
Autosequences
Embedded Filename Variables

When a PC Autosequence is set up to save a report to a file on the PC’s hard disk,
the Filename field may be programmed to include certain variables:
w $v—will cause the Revenue Center Number (the value entered in or inherited
by the Revenue Center field in this step) to be appended to the filename.
w $t—will cause the Totals Set Number (the value entered in or inherited by the
Revenue Center field in this step) to be appended to the filename. In the case
of a flexible report, the value will be the number of the first Totals Set defined
for the report.
Example 1
If 5 is entered in the Revenue Center Number field, and tips_for_RVC.$v is
entered in the Filename field, this step can create a file named
tips_for_RVC.5.
Example 2
A called autosequence is set up that saves the report to a file, and uses a
variable in its Filename field. Other autosequences can then call this
autosequence, each time creating new files with the correct Revenue Center
Number or Totals Set Number imbedded in the filename.
MICROS recommends against using the $ character as a real part of the
filename. If it is necessary to do so, the character must be repeated. For
example, using the filename menu$$ will create a file named menu$.
Usage
As an example, a UWS autosequence is set up to run the following reports:
w Employee Open Check
w Employee Financial
w Employee Closed Check
w Employee Tip
The autosequence is assigned to Privilege Group #1 and given the name

Employee Closeout. Employees who sign in as servers are privileged to access
UWS Reports, and are also assigned to Privilege Group #1. Thus, they are
privileged to run this autosequence.

Autosequences
The Open Check Report is output to the display. The others are output to the UWS
report printer. The employee is shown if there are any checks still open at the end
of the shift. Then the employee receives hard copies of reports to use to close out
the shift.
For security purposes, these reports may be programmed to print only the
information for the signed-in employee.
Enabling
1 UWS Autosequences
2 Reporting | UWS Autosequences | General
R You can define up to 32 UWS Autosequences. Each autosequence can
include up to 16 steps. A step is a complete report or other action. An
autosequence can be chained to another autosequence so that when one
autosequence is completed, the system will automatically run the next,
until the end of the chain is reached.
1 PC Autosequences
2 Reporting | PC Autosequences | General
R You can define up to 255 PC Autosequences. Each autosequence can
include up to 16 steps. A step is a complete report or other action. An
autosequence can be chained to another autosequence so that when one
autosequence is completed, the system will automatically run the next,
until the end of the chain is reached.
1 Workstations
2 System Hardware | Devices | Printers | Printers
R UWS Report
1 Keyboards or WS Touchscreens
Function] | [Function Key Categories = General] | Link
2 Touchscrns & Keyboards | WS Touchscreens | Touchscreen Screen | [Type

= Function] | [Function Key Categories = General] | Number
R 300 - Mode—This key is used to change from the Transaction Mode to

UWS Procedures and UWS Reports.
A-36
Autosequences
Optional Settings
1 UWS Autosequences
1 PC Autosequences
R Several options are provided for each report in an Autosequence, such
as the scope (System or Revenue Center), the output (printer or
display), and whether the report will reset totals or be for examination
only. A PC Autosequence can define any totals set to use in a report. A
UWS Autosequence cannot access saved totals sets. To address the
Audit Trail File or the Error Log through a PC Autosequence:
w Type—Set this to 3-External Program
w External Program User Interface Type—Set this to 0-No User

Interface
w Filename—Enter one of the following commands:
Command Remarks
atrail_b reset These commands reset the

specific file.
errlog_b reset
atrail_b save <filename> These commands save the
file to the file specified in
errlog_b save <filename> the variable <filename>.
atrail_b save_reset <filename> These commands save the
file to the file specified in
errlog_b save_reset <filename> the variable <filename>,
and then reset the file.
If no directory path is specified, a saved file will be created in the

directory \Micros\LES\POS\9700\Log. If a file name already exists, the
file is saved to the file <filename>.MMDD, where MMDD is the
current month and day.

Autosequences
Your System may be configured to require an employee to have a

certain Access Level in order to use or reset the Audit Trail. If the
Autosequence must be available to employees who do not have the
correct Access Level, you may wish to include an employee argument
in the syntax.
The syntax for this optional argument is -e<empl_obj_num>.
Insert this argument after the atrail_b argument: atrail_b -e27
reset
1 System Parameters File

2 System Information | System Parameters | Workstations
R Default UWS Autosequence Help Screen—If this feature is used,
pressing the [Help] key while in UWS Reports mode will automatically
open the Help Screen whose record number is entered here.
1 PC Table
2 System Hardware |Devices | Select PC | General | Printer Settings
R Rpt Printer Setup String (1 - 4)—These fields are used to configure
the PC’s line printer according to the specifications provided with each
printer.
R Line Printer Parameters (1 - 4)—These fields are used to configure
the PC’s line printer(s). Each field must contain the string -d
<printername>, which may be followed by any parameters
required by the printer.
R Lines/Report Page—This field determines the number of lines that a
report will print before starting a new page and printing another header.
A-38
Autosequences
1 Report Configuration File

2 Reporting | Report Configuration | <Select Report Type>
The following fields can also be programmed for the Income Audit Report
Configuration. The values programmed in this file take effect when this
report is run, and they revert back to the values programmed for the
System in the PC Table when this report is finished printing.
R Report Printer Setup Code String (1 - 4)—These fields are used to
configure the PC’s line printer according to the specifications provided
with each printer.
R Line Printer Parameters (1 - 4)—These fields are used to configure
the PC’s line printer(s). Each field must contain the string -d
<printername>, which may be followed by any parameters
required by the printer.
1 Totals Sets
2 System Information | Totals Sets | General
For each saved totals set defined in a PC Autosequence, complete all fields in
this file.
Optional Settings
1 UWS Autosequences
R Privilege Group
1 PC Autosequences
R Privilege Group

Autosequences
1 Employee Class
2 Personnel | Employee Maintenance | [Sort By Class] | Procedures &
Reports | UWS PC Auto Sequences
R Run UWS Reports In Another Revenue Center

R Reset UWS Reports
R Reset UWS Reports without Printing—if Reset UWS Reports is
enabled.
R Run PC and UWS Reports Autosequences in Priv Groups 1-8—
Each Autosequence may be given a privilege code (1-8) and you must
be privileged for each. In this way, waiters may be allowed to run only
a limited group of Autosequences while managers could be allowed to
run a larger group.
Related Topics
w “Batch Autosequences” on page B-8
w “PMSwait” on page P-15
w “Report Writer” on page R-14
w “Using Autosequencer” in Chapter 1 of the 9700 Reports Manual
A-40
B
Backup PC
Description
This feature allows PMS and other interfaces to run in Backup Active Mode. This
field, when used with Enhanced Backup, MUST refer to the secondary PC in the
enhanced pair (as do the devices).
Usage
PMS will start and run under Backup and Enhanced Backup, if the Backup PC #
field is programmed to “follow the Database” to the backup machine in the
Interface file (i.e., if PC 1 is backed up by PC 2 and the Interface is programmed
to run on PC 1, the Backup PC # field should be PC 2).
Emon (VSS) will start and run under Backup and Enhanced Backup, if the
Backup PC # field is programmed to “follow the Database” to the backup machine
in the Interface file (i.e., If PC 1 is backed up by PC 2 and Emon (Interface Table
interface type 2: security) is programmed to run on PC 1, the Backup PC # field
should be PC 2).
Enabling
Interfaces
2 System Hardware | Interface | General
R Backup PC #
9700 HMS A to Z Feature Reference Manual B-1

Banquet Team Service
Description
The Banquet Service feature is designed to allow more than one server to be
assigned to a single check. The intent of this feature is to allow servers to evenly
split a charged tip, service charges, and sales on the Employee Tip Report. In
addition to the original owner of the check, seven servers may be added to the
check, which means a maximum of eight servers may be assigned to a single
check.
Usage
The Employee ID number must be known to use the Add/Remove Team Member
function keys. Team checks may be picked up at the UWS by any team member
(even if the option Authorize/Perform Pickup Checks Belonging to Another
Operator is enabled under Personnel | Employee Maintenance | Sort By Class |
Select Class | Guest Checks | Guest Check Control.
Once a check is started, the Add Team Member key is used to add additional
servers to the check. Press this key and you will be prompted to enter the
employee ID. The Remove Team Member operates in the same manner. A server
may be added or deleted at any time prior to applying payment to a guest check.
B-2
UWS Display
The team members will be displayed on the UWS only, the banquet service team
members will not print anywhere (guest checks, customer receipts, journal printer,
etc.).
1 ---- TEAM MEMBERS---------------------------------

2 Rose, Mikey Ready For Your Next Entry
3 Downe, Mark
4 Ender, Bart Medium Lunch Rose
5 ---------------------------------------------------------------
6
7
1 Fried Cheese
1 Bread Sticks
2.95
1.50 CHK 61
8 2 Glass Rose 3.00 Mikey #1 00
JAN 25 ‘96 8:30PM GST 1
9 1 Iced Tea .75
10 1 Spiced Shrimp 7.95 SUBTOTAL
11 23.49
1 New York Strip 9.95 TAX 1.17
12 AUTO SVC CHG
13 3.52
OTHER SVC CHG 3.50
14 PAYMENT 31.68
15 TOTAL DUE 0.00
16
17
18 Eat In TTL 0.00
If the team member has a Check Name defined in the Employee File, that name
will appear in place of the first and last name in the team member listing on the
UWS.
Pickup Guest Check SLU

If the Pickup Guest Check SLU key is used, the banquet service checks will be
identified by a double asterisk (**). A single asterisk means the check belongs to
another operator.

Guest Check Functions

Whether team information stays with a check or is lost, depends on which guest
check function is performed.
Function Team Information Status
Add check with team info to a check Lose team information on original
without team information check
Add check with no team info to an Team information stay with existing
existing check which includes team check
information
Transfer check with existing team Check employee of original check
information will be replaced with the check
employee of the new check. The
remaining team information will stay
with the check1
Memo Tender Team information stays with each
check
Splitting Team information stays with each
check
1. If the new check employee already existed as a team member on the previous check, that team
member’s name will now be displayed first on the UWS.
If a team member guest check contains any tenders,

that guest check cannot be added or transferred
unless the tender is removed from the guest check.
The same rule applies to adding/removing team
members.
B-4
Reports
The totals from a Banquet Team check are posted to the Employee Tip Report
and will be split evenly among all servers on the check. This includes any total
that is programmed to add to an individual total on the Employee Tip Report. For
example, Autogratuties and Service Charges.
No other report is affected by the Banquet Service

feature. For example, on the Employee Financial
Report, the total sales and tip amount will be posted
to the employee who owns the check.
As an example, the report below shows four different employees. A single check
was closed, which included all four employees as team members, and the total
paid on the check was $19.50 (15.50 Gross F&B Sales and a $4.00 Charged Tip).
The totals were split among each employee on a Banquet Service check.

SQL
A detail file containing Banquet Service information has been added to the
exported open and closed check detail files. The new file has an extension of
.team (open_chk_dtl.team and clsd_chk_dtl.team). These new exported .team
files include the check number, time, employee number, etc. Please see the 9700
HMS SQL Manual for detailed information.
Enabling

R Use Team Information on Guest Check
2 Touchscrns & Keyboards | Keyboards | Keyboard Overhead | <Select

Keyboard> | Key Configuration | Type=Function | Function Key
Categories=Check Operations | Link
2 Touchscrns & Keyboards | WS Touchscreens | Key Configuration |

Type=Function | Function Key Categories=Check Operations | Number
R 549 - Add Team Member—This key will add an employee as a Team

Member for the current transaction.
R 550 - Remove Team Member—This key will remove a team member
from the team for the current transaction.
1 Employee Class File
2 Personnel | Employee Maintenance | Sort By Class | Guest Checks |

Editing Checks
R Authorize/Add Team Members to Check

R Authorize/Remove Team Members from Check
Related Topics
Refer to the 9700 SQL Manual.
B-6
Bar Code Reader Interface
Bar Code Reader Interface
Description
A bar code reader allows an operator to post items for sale by scanning the UPC
(bar code) rather than selecting an item from the keyboard. This is especially
useful in a retail establisment which sells bar coded items.
Bar code readers connect to the RS232 Interface on the User Workstation. For
further information about the Bar Code Reader, refer to “Retail” in Chapter 11 of
the 9700 Feature Overview Manual.

Batch Autosequences
Batch Autosequences
Description
Batch Autosequences allow PC Autosequences to be run without using the
Autosequencer function. Batch Autosequences do not prompt the operator for
parameters and cannot output reports to the display.
Usage
Batch mode allows autosequences to be executed by other UNIX programs. Batch
autosequences are run from the UNIX prompt as the m9700 user. To execute a PC
Autosequence in Batch mode, take the following steps:
w Log in as root (the superuser).
w Enter su - m9700
(Make sure there is a space before and after the dash {–} character.)
w Enter the Batch Autosequence commands, followed by arguments, as shown

below:
aseq_b -e<employee #> -L<printer #><aseq1> <aseq2> <aseq3>... <aseqn>
Argument Remarks
<employee #> Enter the Employee Number (not the ID number) of the
employee running the batch autosequence. This
employee need not be privileged to run this
autosequence— the m9700 login provides all necessary
privileges. This Employee Number is posted to the
Audit Trail File.
<printer #> Enter the record number of the printer to which this
autosequence should print. This number displays in the
PC Table in System Configurator and in the
Autosequencer module. Valid numbers are 1 - 4.
<aseq1> Enter the number of the PC Autosequence. This
number displays in the PC Autosequence File in
System Configurator and in the Autosequencer
module.
B-8
Batch Autosequences
Argument Remarks
<aseqn> Multiple PC Autosequences may be run in a single

batch.
Enabling
1 PC Autosequences
2 Reporting | PC Autosequences | <Select Step> | General

R Print/Display—A drop-down list displays the output selections. The
following selections cannot be used for autosequences that will be run
in batch mode:
w 0-Prompt
w 2-Display
R External Program User Interface Type—When running Batch

Autosequences from a script or the command line, the value in this
field must be set to anything other than 0-No user interface.
Related Topics
w “Autosequences” on page A-26

Begin/Pickup Check
Begin/Pickup Check
Description
There are several ways to begin (open) a guest check:
w Begin check by check ID
w Begin check by check number
w Begin check by table number
w Begin a fast transaction.

When you begin a check, you become the Check Employee for the check. If
another employee later picks up that check that person is called the Transaction
Employee.
Once an open check has been service totalled, it can be picked up again using the
table number or check number. When a guest check is service totalled, all check
detail is retained in the memory, but it is removed from the UWS display to free it
for other activity, such as opening another guest check. To post sales to a guest
check, it must be “picked up” first.
Usage
The particular method for beginning a guest check will depend on the employee’s
job function. A waiter who has a section of tables typically begins checks by table
number and lets the system assign a check number. However, a bartender who is
setup as a “fast transaction” operator will not use table numbers and will let the
system assign a check number. A manager or cashier may be allowed to assign
their own check numbers (like 99 for complimentary meals).
B-10
Begin/Pickup Check
Reports
Financial Reports (System, Revenue Center, Employee,

and Serving Period)
w Checks Begun field
Employee Open Check Report, Employee Closed Check

Report
Each of these reports prints a detail entry for a check that was begun by an
employee, except in the event of a Block Check Transfer. The checks that were
transferred print on the report for the operator to whom the checks were
transferred, as though that operator had originally opened them. Checks that were
transferred using the Block Transfer feature do not appear on the report for the
operator who opened the checks.
Enabling

Type=Function | Function Key Categories=Check Begin/Pickup | Number

Categories=Check Begin/Pickup | Link
R 400 - Begin Check by Number

R 401 - Begin Check by Table
R 402 - Pickup Check by Number
R 403 - Pickup Check, Check #, RVC ?
R 404 through 411 - Pickup Check, Check #, RVC 1 through Pickup
Check, Check #, RVC 8
R 412 - Pickup Check by Table

Begin/Pickup Check
R 413 - Pickup Check, Table #, RVC ?

R 414 through 421 - Pickup Check, Table #, RVC 1 through Pickup
Check, Table #, RVC 8
R 435 - Begin Check by ID
R 436 - Pickup Check by ID
Optional Settings
1 Employee Class
2 Personnel | Employee Maintenance | Sort By Class | Guest Checks | Guest

Check Control
R Create New Checks Using the Begin Check key

R Authorize/Perform Pickup Check that is “Open On System”
R Authorize/Perform Pickup Checks Belonging to Another Operator
2 Personnel | Employee Maintenance | Sort By Class | Transactions |

Transaction Control
w Authorize/Use Table Number key
1 Operators
2 Personnel | Employee Maintenance | Sort By Operator | Options | Check

Options
R Cannot Perform Fast Transactions
Options
1 Workstations
2 System Hardware | Devices | Select Workstation | Workstation | Options

R Auto Begin Check when Check Operator ID/#
1 Operators
2 Personnel | Employee Maintenance | <Sort By Operator> | Select

Operator & RVC | Options | Check Options
B-12
Begin/Pickup Check
R Table Number Entry Required to Begin/Pickup Checks
2 RVC Information | RVC Parameters | Posting & Control | Posting

R Post Totals to Transaction Operator (if disabled, totals are posted to the
Check Operator)
R Post Tenders to Transaction Operator (if disabled, tenders are posted to
the Check Operator)
2 RVC Information | RVC Parameters | Options | Prompt & Confirm

R Begin Check key Confirmation Not Required
R Pickup Check key Confirmation Not Required

R Require Cashier Totals to Begin a Transaction

R Allow Fast Transactions
R Do Not Allow Service Total of Fast Transactions
Related Topics
w “Add Check” on page A-3
w “Fast Transaction” on page F-4

Beverage Control
Beverage Control
Description
The Beverage Control feature provides the ability to monitor and report whether
or not predefined guest check sales information (typically beverages) is included
in the detail of every guest check before the transaction is closed.
Sales information is monitored at the transaction level via the display of a
confirmation prompt during service total or Tender/Media activities. The prompt
notifies the operator that predefined sales requirements for a specific item have
not been met. The operator has the option of ignoring the prompt or adding the
appropriate item(s) to the guest check.
The results of the operator’s response to the confirmation prompt are reported on a
System level via the Tracking Group Section of System reports. Two types of
tracking totals are used to detail the operator’s response. The first total includes
count and amount information for each guest check that was closed without
satisfying the sales requirement. The second total provides a count and amount for
sales that were added as a result of the confirmation prompt. It includes
information about both open and closed checks
Consider using this feature to encourage the sale (suggestive selling) of speciality
items or, as the name implies, to remind the server to post self service beverage
items (coffee, soft drinks, etc.) to the guest check.
B-14
Beverage Control
Usage
How Does Beverage Control Function?

When the Beverage Control feature is enabled, the System evaluates the detail of
every guest check to determine whether or not the appropriate number of
beverages have been posted. The System makes the determination by comparing
the number of posted beverages to zero or to the guest count.
Transaction detail is evaluated each time a Service Total or Tender/Media key is
pressed. If the evaluation of the detail indicates that an insufficient number of
beverages have been posted, the System displays a confirmation prompt. The
prompt alerts the operator that an insufficient number of beverages have been
posted to the guest check. It also provides the opportunity to add additional
beverages.
How Does the System Make the Comparison?

As indicated, the System uses one of two possible comparison methodologies to
determine whether or not a sufficient number of beverages have been added to the
transaction detail of a guest check. Each method is described here.
Comparison to Zero
When Revenue Center Option #39 - Use Guest for Beverage Control is set
OFF, the System will compare the number of beverages posted to the guest
check to the value of zero (0). 1 If, as a result of the comparison, the number
of beverages posted to the guest check is equal to zero (0), the System will
display the following confirmation prompt when a service total or tender key
is pressed: No beverages?
This prompt provides the operator with the opportunity to take one of the
following actions:
w Remain in the current service round (by pressing Clear) and then
adding the correct of number of beverage items.
w Bypass the prompt (by pressing Enter, Service Total, or Tender) and
continuing the guest check transaction.
1. In addition to enabling Revenue Center Option # 39 (Use Guest for Beverage Control) the System must
also be programmed to recognize the Beverage Control feature (Revenue Center Option #38 - Use
Beverage Control). If this option is not set ON, the System will ignore the setting of Revenue Center
Option #39 (Use Guest for Beverage Control).

Beverage Control
If the number of beverages posted to the guest check is greater than zero, the
POS transaction process continues in the usual manner.
The System will ignore the Beverage Control feature

anytime the guest count is reduced to zero (0) or the
transaction total is reduced to a negative value.
Comparison to Guest Count

When Revenue Center Option #39 - Use Guest for Beverage Control is set
ON, the System will compare the number of guests associated with the
transaction to the number of posted beverages. 2 If, as a result of the
comparison, the number of beverages is less than the number of guests the
System will display the following prompt: # beverage(s), # covers.3
This prompt provides the operator with the opportunity to take one of the
following actions:
w Remain in the current service round (by pressing Clear) and then adding
the correct of number of beverage items.
w Bypass the prompt (by pressing Enter, Service Total, or Tender) and
continuing the guest check transaction.
If the number of beverages posted to the guest check is greater than the
number of guests, the POS transaction process continues in the usual manner.
2. Keep in mind that the System can calculate the number of guests in one of several ways. For example, by
using the number of seats (Revenue Center Option #8 - Use Number of Seats for Guest Count), or by
using menu items that are programmed to increase the guest count (Menu Item Class Type Definition #4
- Increment Seat Number With Sale of These Menu Items).
3. In addition to enabling Revenue Center Option # 39 (Use Guest for Beverage Control) the System must
also be programmed to recognize the Beverage Control feature (Revenue Center Option #38 - Use
Beverage Control). If this option is not set ON, the System will ignore the setting of Revenue Center
Option #39 (Use Guest for Beverage Control).
B-16
Beverage Control
Beverage Control Considerations

When the Beverage Control feature is active, consider the following:
Split Check Transaction

When the Beverage Control feature is enabled and the Split Check function is
used, make sure that the appropriate number of beverages are added to each
check. Otherwise, the System will prompt for them when the check is service
totalled or tendered. Beverage Control tracking totals(#18 and #19) will be
updated appropriately for each split check.
Memo Check
When the Memo Check function (prints separate checks by seat number) is
used in conjunction with the Beverage Control feature, remember that
Tracking Total # 18 (Insufficient Bvg) count and amount information is not
recorded until the check is paid in full. Keep in mind that the System does
not create a new guest check identity for each Memo Check.4 Rather, the
System views Memo Check activities as being associated with the original
guest check. This means that, although the System may display the Beverage
Control confirmation prompt for a particular memo check, it will be ignored
unless the tender amount reduces the balance due to zero (0). For example,
consider the following scenarios:
w Memo Tender When Tracking Total #18 Isn’t Updated
w A Guest check contains four seats.
w The Memo Check function was used to create a memo check for
Seats 1 and 2. During the memo check process, the System displayed
the Beverage Control prompt for each seat. In both cases, the operator
ignored the prompts and completed the memo tender process.
Because an unpaid balance remained on the check, Tracking Total
Type # 18 (Insufficient Bvg) was not updated.
If the operator had added beverages to the memo check as a result of
the prompt, Tracking Total Type #19 (Bvg After Prompt) would have
been updated to reflect the activity.
w The outstanding balance on the guest check (sales for Seats 3 and 4)
was tendered in the usual manner. During the tendering process the
System did not display the Beverage Control prompt. As a result,
there was no need to update the information included in Tracking
Total Type # 18 (Insufficient Bvg).
4. Remember that, unlike the Split Check function, a new guest check is not created for each memo check.

Beverage Control
w Memo Tender When Tracking Total # 18 is Updated
w A Guest check contains four seats.
w The Memo Check function was used to create a memo check for
Seats 1 and 2. During the memo check process, the System displayed
the Beverage Control prompt for each seat. In both cases, the operator
ignored the prompts and completed the memo tender process.
Because an unpaid balance remained on the check, Tracking Total
Type # 18 (Insufficient Bvg) was not updated.
If the operator had added beverages to the memo check as a result of
the prompt, Tracking Total Type #19 (Bvg After Prompt) would have
been updated to reflect the activity.
w The outstanding balance on the guest check (sales for Seats 3 and 4)
was tendered in the usual manner. During the tendering process the
System did display the Beverage Control prompt and the operator
ignored it. Tracking Total Type #18 (Insufficient Bvg) is updated by a
count of 1 and only the dollar amounts from seats 3 and 4 were added
to the guest check dollar value. The information from the memo
checks that were created for seats 1 and 2 were not included in the
data for Tracking Total Type # 18 (Insufficient Bvg) because guest
check had not been paid in full.
How Do I Enable Beverage Control?

The System uses four option settings to govern the operation of the Beverage
Control feature. Each is described below:
w Use Beverage Control Option—RVC Information | RVC Parameters |
Options | General—This option activates the feature. It must be enabled in
conjunction with the Use Guest for Beverage Control described below.
w Use Guest for Beverage Control—RVC Information | RVC Parameters |

Options | General—This option controls the methodology used to calculate
whether or not the appropriate number of beverages have been posted to a
guest check. Revenue Center Parameters File Option #38 (Use Beverage
Control Option) must be set ON in order for the System to recognize the
setting of this option.
w Item is Beverage—Menu Items | Menu Item Maintenance | Sort By Menu

Item Class | <Select Menu Item> | General | Type Definitions— This option is
used to identify each menu item that should be recognized by the Beverage
Control feature.
w Insufficient Beverage/Beverage After Prompt—Reporting | Tracking

Groups | General | Detail | Type—These Tracking Totals Types are used to
track the operator’s response to Beverage Control confirmation prompts.
B-18
Beverage Control
Reports
How is Beverage Control Information Tracked and

Reported?
Beverage Control information can be tracked and reported in two ways. You have
the option of tracking the number and dollar value of all checks that were paid in
full but did not include a sufficient number of beverages. You also have the option
of tracking the number and dollar value of beverages that were added as a result of
the Beverage Control Confirmation Prompt.
Tracking an Insufficient Number of Beverages

The Tracking Total Insufficient Bvg is used to track the number of guest
checks that were paid in full but did not include a sufficient number of
beverages. Information is posted to this tracking total at the time a guest check
is paid in full.
Tracking total information appears on all System reports that include a
Tracking Total Section. The tracking total name is user-definable and can
contain up to 12 alphanumeric characters. Use the Name field of the Tracking
Group file to define a tracking total name.
This tracking total includes a count and amount values. The count value
represents the number of guest checks that were paid in full and failed to
include a sufficient number of beverages. The amount value is the
accumulated dollar value of all guest checks that were paid in full.
Operator response to a Beverage Control Confirmation Prompt is included in
one of two different types of tracking totals. The first tracking total type
(Insufficient Bev) maintains count and amount information for each guest
check that was paid in full with an insufficient number of beverages.

Beverage Control
Tracking Beverages Added After the Confirmation Prompt

The Tracking Total Bvg After Prompt is used to track the number and dollar
value of beverages that were added to a guest check as a result of the
Beverage Control Confirmation Prompt. Information is posted to this tracking
total each time a guest check is service totalled or tendered.
Tracking total information appears on all System reports that include a
Tracking Total Section. The tracking total name is user-definable and can
contain up to 12 alphanumeric characters. Use the Name field of the Tracking
Group file to define a tracking total name.
When included in the Tracking Totals Section of a System report, Beverage
Control Tracking Total information could look like this:
This count and total

will appear when a
check has been paid
in full without the
required item(s).
This count and total will

appear when the required
item was added after the
operator prompt “No
Enabling

R Use Beverage Control
R Use Guest for Beverage Control (Use Beverage Control must also be
enabled)
1 Menu Item Class
2 Menu Items | Menu Item Maintenance | <Sort By Menu Item Class> |

<Select Menu Item Class> | General | Type Definitions
R Item is Beverage
B-20
Beverage Control
1 Tracking Group
2 Reporting | Tracking Groups | General | Detail | Type

R Insufficient Bvg
R Bvg After Prompt
Optional Settings

R Use Number of Seats for Guest Count
1 Menu Item Class
2 Menu Items | Menu Item Maintenance | Sort By Menu Item Class | <Select
Menu Item Class> | General | Type Definitions
R Increment Seat Number with the Sale of These Menu Items
1 Service Charge
2 System Information | Service Charge | General | Type Definitions

R Service Charge Adds to Guest Count
1 Operator
2 Personnel | Employee Maintenance | Sort By Operator | <Select

Operator> | Options | Check Options
R Number of Guests Entry Required for New Checks
Related Topics
Refer to the 9700 Reports Manual and the 9700 field level context-sensitive help.

Block Settle Checks
Block Settle Checks
Refer to “Open Check Block Settlement” on page O-4.
B-22
Block Transfer Checks
Description
This function key allows one server to transfer some or all of their checks to
another server. A block of checks may only be transferred within the same
Revenue Center.
Usage
Example
It’s 5:00 in the afternoon at a bar called The Eight Tootha. The daytime bartender
is ending her shift and the evening bartender is clocking in. The first bartender is
ready to leave, but she still has 20 open checks for the 20 active parties in the bar.
The incoming bartender uses the Block Check Transfer key to transfer all of the
outgoing bartender’s open checks to herself.
To transfer a block of guest checks, confirming each check transfer:
w The operator to whom the checks will be transferred must sign in to the UWS.
w Press the Block Transfer key. The UWS prompts for the Employee ID or the
Employee Number of the employee whose checks are to be transferred.
w Enter the ID or the Number. For each open check, the UWS displays
summary totals and prompts for confirmation of the transfer of the individual
check.
w For each check, press Enter to confirm the transfer, or press Clear to prevent
the transfer.
To automatically transfer a block of checks:
w Press the Auto Block Transfer key. The UWS prompts for the Employee ID or
the Employee Number of the employee whose checks are to be transferred.
w Enter the ID or the Number. The UWS prompts for confirmation for the
transfer of all open checks.
w Press Enter to confirm, or press Clear to abort.

Reports
Employee Financial Report

If a block of checks is transferred between operators, the checks post to the
following totals on these reports:
w Begun
w Transferred In
w Paid
w Transferred Out
Any transaction detail posted by the original operator is reported to that operator’s
totals on The Employee Financial Report.
Employee Closed Check Report- Report Writer and UWS

Versions
Checks that were transferred using the Block Transfer feature do not appear on the
report for the operator who opened the checks. The checks that were transferred
print on the report for the operator to whom the checks were transferred, as though
that operator had originally opened them.
Enabling
1 Keyboards

Categories=Transaction | Link
R 520 - Block Transfer—This key displays summary totals for each

open check and requires confirmation (Enter/Clear) to transfer each
one.
R 521 - Auto Block Transfer—This key transfers all open checks
without prompting for confirmation.
B-24
1 WS Touchscreens

Function Key Categories = Transaction | Number
R 520 - Block Transfer—This key displays summary totals for each

open check and requires confirmation (Enter/Clear) to transfer each
one.
R 521 - Auto Block Transfer—This key transfers all open checks
without prompting for confirmation.

R ON = Use Employee # to Transfer a Block of Checks; OFF = Use
ID Number—If enabled, the “transferring” operator’s employee ID is
required. If disabled, the transferring operator’s employee number is
required.
Optional Settings
1 Employee Class
2 Personnel | Employee Maintenance | <Sort By Class> | <Select Class> |

Guest Checks | Guest Check Control
R Authorize/Use Block Transfer and Auto Block Transfer keys
Related Topics

Breaks
Breaks
Description
A break is a rest period for hourly workers, such as lunch break, that can be
tracked by the 9700 Timekeeping system. Breaks can be either paid or unpaid.
The time spent on unpaid breaks subtracts from the total time credited for pay by
the 9700 System.
The 9700 System can be programmed to set time limits on breaks. Since some
labor laws establish different minimum break requirements for minors and non-
minor (regular) employees, separate break parameters may be defined for each
kind of employee.
Reports
Clock In Status Report

This report lists every employee that is currently clocked in to the system. This
report will not list any employees that are on break.
Labor Availability Report

This report lists all employees currently clocked in or on break.
Enabling
1 System Parameters
2 System Information | System Parameters | Timekeeping

R Time Clock Parameters fields—Enter the number of minutes for the
minimum and maximum break periods. Breaks can be set for both
regular and minor employees, and be either paid or unpaid.
R Time Clock Parameters Options—These selections determine
various User Workstation prompts when clocking in/out.
B-26
Breaks
1 Employee Class
2 Personnel | Employee Maintenance | Sort By Class | <Select Class> |

General | Time & Attendance
R Authorize Clock In
Optional Settings

R Authorize/Perform Clock In/Out Outside Schedule or Scheduled

Breaks
Related Topics
w “Grace Periods” on page G-1
w “Time Clock Schedule” on page T-63

By-Round Guest Check
Description
A By-round Guest Check is a printing option that causes a guest check to print
each time it is service totalled. A By-round operator is forced to print the check
after every service round. However, only the detail posted in the recently
completed round will print.
Usage
A By-round guest check provides the server, at the end of every service round,
with a complete guest check that is ready for immediate presentation to the
customer. In contrast, an on-demand operator has a check for the customer only
when the operator uses a Print Check service total type key.
This feature may be used in situations where you want the server to be able to
immediately present the customer with a check showing the balance due.
The disadvantage of By-round guest checks is that they tend to be longer and less
“tidy” in appearance.
A By-round guest check is normally printed at a slip printer. When printed, the
slip printer advances the check past the last printed line and then prints the detail
from the latest round. The original guest check is appended at each service round.
When a By-round guest check is printed at a roll printer, the header prints first.
This may be followed by a line showing the balance at the end of the previous
round, and then the detail posted in the round just completed.
The following illustrations show how By-round guest checks are printed. The top
left check shows the first round. The guest check was opened, two drinks were
posted and the check service totaled and printed at a slip printer.
B-28
Next, at lower left, the check was picked up, another drink was posted and the
check service totaled again. The check was picked up a third time, at right, and
another drink and a hamburger were posted. Then it was tendered to cash ($15.00)
and closed.
-------------------------------------- --------------------------------------
1 Call Cocktail 3.00 1 Call Cocktail 3.00
1 Import Draft 2.25 1 Import Draft 2.25
BALANCE DUE 5.25 BALANCE DUE 5.25
1 Domestic Draft 1.85

BALANCE DUE 7.10

-------------------------------------- 1 Hamburger 3.50
1 Call Cocktail 3.00 SUBTOTAL 12.45
1 Import Draft 2.25 SALES TAX 0.62
BALANCE DUE 5.25 BALANCE DUE 13.07

BALANCE DUE 7.10 CASH 15.00
SUBTOTAL 12.45
SALES TAX 0.62
CHANGE DUE 1.93
Note: Guest Check headers have been omitted for clarity.
Enabling


Type=Function | Function Key Categories=Transaction | Number

R 402 - Pickup Check by Number
R 403 - Pickup Check, Check #, Rvc ?

R 404 through 411 - Pickup Check, Check #, Rvc 1 through Pickup

Check, Check #, Rvc #8
R 412 - Pickup Check by Table
R 413 - Pickup Check, Tbl #, Rvc ?
R 414 thorugh 421 - Pickup Check, Check #, Table #, Rvc 1 through
Pickup Check, Check #, Table #, Rvc 8
R Service Total key
1 Operator

Operator> | Options | Printing
R ON = On-demand; OFF = By-round
Optional Settings

R Print Previous Balance Each Round
R Print Transaction Employee # and UWS # on Guest Check Each Round
1 Operator
2 Personnel | Employee Maintenance | Sort By Operator | <Select Operator

& RVC> | Options | Printing
R Special By-round; Same as 4700 “Temporary, On-demand”
Related Topics
w “On-Demand Guest Check” on page O-1
w “Special By-Round Operator” on page S-45
B-30
C
Cancel Transaction
Description
The [Transaction Cancel] key will delete an entire service round, as long as the
order has not been service totalled. When this key is used to exit a guest check, no
totals are affected other than the Transaction Cancel totals. The Transaction
Cancel key is also used to sign off a “stay-down” operator, that is, the system will
prompt for the re-entry of an Employee ID number.
Usage
Transaction Cancel is useful in the transaction mode when a mistake is made or
when there isn’t enough time to complete a task.
9700 HMS A to Z Feature Reference Manual C-1

Cancel Transaction
Reports
Transaction cancel posts to the Cancel Total on the following reports:
w System Financial Report
w Revenue Center Financial Report
w Employee Financial Report
These postings track the number of times the [Transaction Cancel] key was used
and the net value of all entries cancelled. Cancellations do not add to any other
values on these reports.
Employee Closed Check Report

Cancelled checks are marked by a “C”.
Enabling

R 605 - Transaction Cancel
Optional Settings
1 Employee Class
2 Personnel | Employee Maintenance | <Sort By Class> | <Select Class>
Transactions | Transaction Control
R Authorize/Use [Transaction Cancel] key - Transaction Privilege #40
C-2
Cancel Transaction
Related Topics
w “Void Item” on page V-18

Cash Drawer
Cash Drawer
Description
Your UWS may have one or two cash drawers attached. A cash drawer can be
permanently assigned to an operator through the Operator file or programmed to
determine which keys on the keyboard (and which operators) can open which
drawer. The drawer may also be locked or opened in emergencies with a cash
drawer key.
Usage
Link by Operator File

The simplest method of assigning cash drawers is to assign the drawer to an
operator in the Operator File. Any number of operators can be assigned to and
access the same cash drawer. Since there is less control over who can open a cash
drawer, this method is most commonly used when only one operator at a time is
assigned to the UWS.
Link with Cash Drawer Keys

There are two sets of keys used to assign cash drawers. Each set uses a slightly
different assignment method. The choice of which set of keys to use depends on
the needs of the establishment. Using both sets of keys is not recommended.
[Assign Cash Drawer 1], [Assign Cash Drawer 2] keys

Depending on your operation, various cash drawer configurations are
possible. The most common use is to assign a cash drawer to one person who
is responsible for the money at that workstation. A privileged operator may
use one of these two keys to assign a cash drawer to any operator. Once an
operator is assigned a cash drawer, that person is the only one who can access
the cash drawer at that workstation. This provides the highest level of
security. The operator remains assigned to this cash drawer until the key is
pressed again and a new operator is assigned.
However, bartenders may be allowed to use the same cash drawers at different
UWS’s. This will allow them to “float” between work areas.
Finally, it may be advantageous to keep the base currency in drawer #1, and a
foreign currency in cash drawer #2.
C-4
Cash Drawer
[Assign Cash Drawer], [Unassign Cash Drawer] keys

The [Assign Cash Drawer] key assigns the signed-in operator to the first
available cash drawer on this UWS, then opens that drawer. This operator
remains assigned to this cash drawer until the [Unassign Cash Drawer] key is
used to clear the assignment. This operation generates a journal entry, noting
the cash drawer number and the employee’s check name and Employee
Number.
The function of the [Unassign Cash Drawer] key depends on whether or not
the operator is privileged to assign cash drawers (Employee Class Options
Privilege “Authorize/Perform Assignment of Cash Drawer”).
If the operator is privileged and presses [Unassign Cash Drawer], the UWS
prompts the operator to confirm that the cash drawer should be unassigned. If
two cash drawers are currently assigned, the UWS displays a help window
containing the cash drawer numbers and the names of the operators to whom
they are assigned. The operator may then select the cash drawer to be
unassigned, and the drawer opens. Operators who are not privileged may only
unassign themselves.
Using the [Unassign Cash Drawer] key creates a journal entry.

Cash Drawer
Comparison
The following table illustrates the differences between these two sets of cash
drawer keys.
[Assign Cash Drawer

[Assign Cash Drawer]
1]
[Unassign Cash
[Assign Cash Drawer
Drawer]
2]
To assign a Press either key to Press [Assign Cash

drawer... assign that specific Drawer] to assign the
drawer to the signed-in first available drawer to
operator. the signed-in operator.
If an operator is Press either key to An error message
already replace any current displays if both drawers
assigned to that assignment for that are currently assigned.
drawer... specific drawer.
To unassign a Press either key to Press [Unassign Cash
drawer... assign that specific Drawer] to generate a
drawer to the signed-in prompt displaying the
operator, replacing any operators assigned to all
previous assignment. cash drawers that you
are privileged to
unassign. Select an
operator to unassign, or
confirm the operator to
be unassigned.
Employee Class Must be set ON to allow Must be set ON to
Option you to use these keys. allow you to unassign
“Authorize/ other operators.
Perform
Assignment of
Cash Drawer”
Do these keys No Yes, for each action
generate a (assign and unassign).
journal entry?
Do these keys No Yes, for each action
open the cash (assign and unassign).
drawer?
C-6
Cash Drawer
Opening the Drawer

A cash drawer may be opened inside a transaction (as part of or at the end of a
transaction, or it may be opened outside of a transaction (when no transaction is
taking place).
Inside a Transaction
Any Tender/Media key may be programmed to open the cash drawer when it
is pressed.
A Revenue Center may be programmed to prevent the cash drawer from
opening unless the balance due is 0.00. This option is used by some
establishments that wish to discourage opening the drawer for partial tenders.
A Revenue Center may be further programmed to prevent the cash drawer
from opening if the subtotal of the transaction is 0.00. This may be used to
prevent the cash drawer from opening for a non-cash transaction (e.g., if a
100% discount (a comp) is applied to a check, or if the Void Check feature is
used.)
Outside a Transaction
The [No Sale] key may be used by a privileged, signed-in operator to open the
cash drawer when no transaction is in progress (e.g., to make change for a
customer).
The [Assign Cash Drawer] and [Unassign Cash Drawer] keys open the cash
drawer, as described on the previous page.
Reports

w No Sale field—This field tracks the number of times that an employee opened
the cash drawer using the [No Sale] key.

Cash Drawer
Enabling
1 Workstations
2 System Hardware | Devices | <Select Workstation> | Workstation
R Number of Cash Drawers field—Define the number of cash drawers
attached to a UWS.
1 Tender/Media
2 System Information | Tender Media | General | <Key Type Payment> |
Key Type | Ops Behavior
R Open Cash Drawer—When a check is closed with one of these

tendering keys, the cash drawer will open, provided the amount
tendered is greater than zero and the employee has been assigned a cash
drawer.
Assign a Cash Drawer to One Operator
1 Workstations
R Cash Drawer 1 Operator field—Enter the Employee Number of the
person who will be permanently assigned to cash drawer 1 (refer to
Type Definition #4 below).
R Cash Drawer 2 Operator field—Enter the Employee Number of the
person who will be permanently assigned to cash drawer 2 (refer to
Type Definition #4 below).
R Assign Cash Drawer By Workstation—If this is ON, the System will
ignore the Operator File and refer to the operator number entered in the
following two fields in the Workstation Table: Cash Drawer 1 Operator
and Cash Drawer 2 Operator. This limits cash drawer access to one
operator for each cash drawer on this UWS.
C-8
Cash Drawer
1 Keyboards or WS Touchscreen File

Function] | [Function Key Categories = Non-Sales Operations] | Link

[Function Key Categories = Non-Sales Operations] | Number
R Use one of these two sets of keys to assign drawers (i.e., change Cash
Drawer 1 & 2 Operator link in the Workstation Table).
w 839 - Assn Cash Drawr 1
w 840 - Assn Cash Drawr 2
w 848 - Assn Cash Drawer
w 849 - Unasgn Cash Drawer
Assign a Cash Drawer to Several Operators
1 Workstations
w Assign Cash Drawer By UWS—If this option is disabled, the
System will ignore the Workstation setting and refer to the Cash
Drawer field in the Employee Maintenance file (Personnel |
Employee Maintenance | Sort By Operator | <Select Operator> |
General). All operators assigned to the same cash drawers (1 or 2)
will be able to open cash drawers on this UWS, or any other UWS
with this option disabled.
1 Operators
Operator> | General
R Cash Drawer field—Assign the cash drawer number (1 or 2) for each

operator with access to a cash drawer.

Cash Drawer
Optional Settings

w 830 - No Sale
1 Workstations
R Require Cash Drawer to be Closed Before New Transaction
R Cash Drawer 2 for Other Currency—This option will enable the
second cash drawer to be used during foreign currency conversion.
1 Currency
2 System Information | Currency | Alternate
R Issue Change in Alternate Currency
R Prompt for Issuing Change

R Employee ID required with [No Sale] key—Set this ON to cause the
System to prompt for the signed-in operator’s Employee ID when the
[No Sale] key is pressed. This is intended for stay-down operators who
may need to walk away from the UWS (e.g., bartenders, sales clerks).
R Open Drawer Only If Balance Due Is 0.00
R Do Not Open Drawer If Subtotal Is 0.00
C-10
Cash Drawer
1 Employee Class
2 Personnel | Employee Maintenance | Sort By Class | Options |
Miscellaneous
R Authorize/Perform Assignment of a Cash Drawer—The function of

this option depends on which set of assignment keys (#839 & #840, or
#848 & #849) are being used at this establishment. This option
authorizes an employee (usually a manager) to:
w authorize/perform assignment of a cash drawer
w authorize/perform assignment & changes of cashiers
2 Personnel | Employee Maintenance | <Sort By Class> | Transactions |

Transaction Control
R Authorize Opening Cash Drawer Using the [No Sale] key
Related Topics
w “No Sale Key” on page N-1

Cashiers
Cashiers
Description
Cashier totals are usually assigned to individual operators so that they may
balance the flow of money into and out of a UWS’s cash drawer(s). Thus, the
purpose of a cashier designation is to assign responsibility and accountability of
revenue through the 9700 tracking system.
Usage
The personnel files are used to create Employee, Operators, and Cashiers. These
names do not refer to different people, but represent the “link” between various
totals (labor totals, job code totals, sales totals, posting totals, etc.) which are
maintained in the system. The totals are linked together depending on the function
of a particular person who uses the system.
Cashier totals may be used in one of two ways: they may be linked to an
individual operator, or they may be linked to a specific UWS.
Cashier Totals Linked to an Operator

Cashier totals may be linked to individual operators with the [Assign Cashier]
key. This type of cashier link may be needed if:
w Each operator needs to balance an assigned cash drawer.
w Each operator needs more records for Tracking Totals than are provided by
the 128 entries in the Operator Tracking Totals.
Cashier Totals Linked to a UWS

Cashier Totals may be linked to a specific UWS. This method is used if cashier
totals are to be used to balance an entire shift. This method may only be used with
a UWS that is assigned to a single Revenue Center. Cashier Totals may not be
assigned to a UWS that is available in multiple Revenue Centers.
C-12
Cashiers
This type of cashier link may be needed if:

w the operator who begins checks is not the same operator who tenders checks.
w a consolidated shift total of several operators is required.
If cashier totals are linked to a UWS, they remain in

effect even when operators sign in who are linked to
their own cashier totals. In other words, the UWS
cashier assignment overrides the operator
assignment.
Enabling
Link an Operator to a Cashier Total (Cash Drawer

Balancing)
If the UWS is programmed to assign cashier totals by operator, a single operator
may be linked to a cashier total.
w Sign in to the UWS.
w Type a valid cashier number, and press [Assign Cashier].
The operator is linked to that cashier total, and will remain so until their cashier
assignment is changed.
Employee File Operator File

This link may be
Operator #1 Employee Number Employee Number programmed in
System
Cashier Number Configurator or it
may be linked to
Operator Tracking # the signed-in
operator with the

Cashiers
Link Several Operators to a Cashier Total (Shift Balancing)

If the UWS is programmed to assign cashier totals by UWS, several operators
may be linked to a cashier total. This feature is used to obtain a combined total for
several operators. The procedure is the same as for single operators:
w Sign in to the UWS.
w Type a valid cashier number, and press [Assign Cashier].
Each operator who signs in to this UWS after this will be linked to this cashier
total, until the cashier assignment is changed
Employee File Operator File Cashier File
Operator #1 Employee Number Employee Number Cashier Number
Cashier Number
Operator Tracking #
Operator #2 Employee Number Employee Number
Cashier Number
These links may be
Operator Tracking # programmed in
System Configurator
or they may be linked
to a UWS with the
[Assign Cashier] key.
Optional Settings
1 Workstations
R ON = Link Cashier Totals to UWS; OFF = Link to Operator - Type
Definition #9
C-14
Cashiers

R 845 - Assign Cashier

R Require Cashier Totals to Begin Transaction
R If No Transaction Operator Cashier Totals, Post to Check Operator
Cashier Totals
Optional Settings
1 Employee Class
2 Personnel | Employee Maintenance | <Sort By Class> | <Select Class> |
Options
R Authorize/Perform Assignment & Changes of Cashiers
Related Topics
w “Defining Cashiers” in Chapter 4 of the 9700 Feature Overview Manual
w “Tracking Groups” on page T-141

Chain & Fire
Chain & Fire
Description
The Chain & Fire function allows a server to post detail and to service total a
series of checks without sending check detail to order printers until a separate
service total key is pressed. This allows orders that may be received and posted
separately to be sent in a consolidated order to the remote order devices. Thus,
several checks may be posted together and output to the kitchen as if they were
one order.
Usage
Chaining orders is useful when serving large groups that require separate checks.
The kitchen can more effectively manage a large group of orders if all the orders
are printed on a single chit (as though it is one large order-- which, in fact, it is!)
Example
A convention group of twenty from the mid-west is visiting N.Y. City. The group
informs the waiter that they are on an expense account and require separate
checks.
The waiter enters each order separately, pressing the specially programmed
[Chain] key which will “chain” the orders together. After the last order is entered
(chained), the waiter may “fire” the order. To do so, he simply presses the regular
[Service Total/Fire] key.
Once chaining has begun, the waiter must fire the order before attempting any
other actions (e.g., beginning or picking up another check, signing out, etc.)
C-16
Chain & Fire
Enabling
1 Tender Media
R Key Type field—To create a [Chain] key, set this field to Service Total
2 System Information | Tender Media | Key Type=Service Total | Key Type |
Category=POS Ops Behaviors | Ops Behaviors
R Chain Order—The service total key that combines the order output is
called a [Chain] key and has this option enabled.
R Fire Order—Any service total key without the Chain Order option
enabled will serve to “fire” the buffered checks to the remote order
devices.
2 Touchscrns & Keyboards | Keyboards | Key Configuration | Type=Function
| Function Key Categories=Transaction | Link

Function Key Categories=Transaction | Number
R [Fire] key—a [Service Total] key with Tender Media Service Total
option Fire Order enabled
R [Chain] key—a [Service Total] key with Tender Media Service Total
option Chain Order enabled
Related Topics
w “Hold & Fire” on page H-13

Charged Tip
Charged Tip
Description
A Charged Tip is a voluntary gratuity that the guest adds to his payment by
writing the tip amount on the charge voucher.
Like the meal payment, the tip is “charged” to a credit card, hotel room account,
etc. A charged tip is credited to the check operator when the guest check is
tendered. The operator is paid the charged tip in cash through a separate action
with the [Tips Paid] key.
All credit card processing companies or processing banks charge a fee for credit
card processing (e.g., 5% of the total). This fee applies to the charged tips as well
as the sales total. Some restaurants charge their servers for the portion of the credit
card processing fee that applies to the charged tip. For example, if the processing
fee is 5%, and a server earns a $10.00 charged tip, the restaurant pays the server
$9.50 in cash and uses the other $0.50 to pay the credit card processing fee.
Reports
Employee Tip Report

The following totals are included in each employee’s Tip Report:
w Gross Receipts—total sales credited under the employee’s name
w Charged Receipts—total charged sales that included a charged tip credited to

the employee
w Service Charge Receipts—total service charges payable to the employee
w Charged Tips—total of tips included in all charged sales credited to the

employee
C-18
Charged Tip
Tracking Totals
The Charged Tips and Tips Paid totals may be included in the Tracking Groups
assigned to certain reports.
When tips are paid out automatically and a percentage of these tips are retained
for paying credit card fees, subtracting Tips Paid from Charged Tips within your
Tracking Group will provide you with the credit card fee total. Having this
calculation done within your Tracking Group is the only way to obtain this
information without manually doing the calculation yourself.
Enabling
Charged Tips can either be entered manually with a [Charged Tip] key placed on
the keyboard, or calculated automatically as guest checks are posted. For both
accuracy and convenience, most restaurants use the automated procedure. A [Tips
Paid] key is used to record cash payments to operators who have earned charged
tips.
Manual Tips Paid
2 Touchscrns & Keyboards | Keyboards | Key Configuration | Type=Tender/
Media | Link

Type=Tender/Media | Number
R [Tips Paid] key—a Tender/Media key set up as a media pickup key to

record cash paid to operators.
Automatic Tips Paid
1 Tender/Media File
2 System Information | Tender Media | <Select Key Type Payment> | Key
Type
R Charged Tip Service Charge field—Link each applicable Tender/

Media key (Visa, Amex, etc.) with a Service Charge key (using the
record number) designated to post charged tips.

Charged Tip
1 Service Charge File

2 System Information | Service Charges | General
R Tips Paid Tender/Media field—Link the service charge key to a
Tender/Media key that “acts” as a Tips Paid key. This key must have
Tender Media Type Definition Cash Tips Paid (Key Type Pickup)
enabled.
Optional Settings
1 Tender/Media File
2 System Information | Tender Media | Key Type=Payment | Key Type |
Category=Charge Tip Options | Options
R Charged Tip Required—Credit card keys like American Express can

be programmed to treat any overpayment as a charged tip. If the
amount due is $44.00 and $50.00 is entered as the tender, this key
assumes a $6.00 tip and prompts the operator to confirm it.
R Charged Tip Amounts: Must be Less Than Payment—Enable this
option to require that the charged tip be less than the amount of
payment. Disable this option to allow the charged tip to equal the
payment.

2 System Information | Service Charges | General | Type Definitions
R Post to Charged Tips Total on Tip Reports—The charged tip can be
set to automatically add to the Charged Tips total on the Employee Tip
Report.
R Post to Service Charges Total on Tip Reports—The charged tip can
be set to automatically add to the Service Charges Total on the
Employee Tip Report.
R Percent to Tips Paid field—A restaurant can elect to pay a server the
percentage of the credit card invoice that the credit card company pays
the restaurant. For example, if Amex charges the restaurant 4% of
credit card sales charged to Amex, then the restaurant may want to pay
the employee only 96% of the Amex credit card Charged Tip that they
earn.
C-20
Charged Tip
Related Topics
w “Cashiers” on page C-12
w “Defining Cashiers” in Chapter 4 of the 9700 Feature Overview Manual
w “Tips Handling” on page T-69

Check Number
Check Number
Description
Every guest check or fast transaction that is begun at a User Workstation is
assigned a guest check number. The check number may be used to “pick up” or
track a guest check.
In the 9700 System, check files are unique to each

Revenue Center. Therefore, check numbers are
Revenue Center specific. There are no system-wide
check numbers.
Guest check numbers can be assigned automatically (by the System) or manually
(by an operator).
Usage
Guest check numbers can be assigned by the 9700 System automatically. To
avoid duplicating a guest check number in two Revenue Centers, we recommend
that each Revenue Center be assigned an exclusive range of guest check numbers.
For example, in Revenue Center #1, check numbers could range from 1 to 1000.
In Revenue Center #2, check numbers could range from 1001 to 2000.
Alternatively, check numbers can be assigned by the operator. Some restaurants
issue servers a stack of guest checks printed with the restaurant logo and
consecutive check numbers. If operators assign their own guest check numbers,
the guest check number used by the 9700 system can be made to match the
number on the guest check used by the operator.
A manager may use specific check numbers (e.g., 999) to ring complimentary
menu items.
The Next Check Number may be reset at any User Workstation using UWS
Procedure #1 - Change Revenue Center Parameters.
C-22
Check Number
Enabling
1 Revenue Center Configuration

2 RVC Information | RVC Configuration | General | PCs
R PC With Check and Status Files field—Enter the number of the PC
(from the PC Table) that is used to store the Open Check File and the
Closed Check File.
1 Revenue Center Parameters File

2 RVC Information | RVC Parameters | General
R Min. Check #, Max. Check # fields—Enter the lower and upper range
for check numbers for each Revenue Center. We recommend the range
be unique for each Revenue Center. Check numbers can range in value
from 0 to 99999.
| Function Key Categories=Check Begin/Pickup] | Link

Type=Function | Function Key Categories=Check Begin/Pickup| Number

R 402 through 411 - Pickup Check by Number
Related Topics
w “Begin/Pickup Check” on page B-10

Clock In/Out
Clock In/Out
Description
Clock in and out procedures tell the 9700 Timekeeping system when to begin and
end crediting an employee for payable work hours. Employees who are required
to clock in (hourly, as opposed to salaried, workers) cannot sign in to a Revenue
Center unless they are first clocked in to that Revenue Center.1
Usage
All employees can use the 9700 for timekeeping even if they don’t use the System
for any other purpose. An employee may clock in and out at any UWS by pressing
the [Clock In/Out] key. When they do, they are prompted for an Employee ID
number.
Reports
The Clock In Status Report lists all employees currently (as of the time the report
is taken) clocked in system-wide.
Enabling
| Function Key Categories=Non-Sales Operations | Link

Type=Function | Function Key Categories=Non-Sales Operations |
Number
R 833 - Clock In/Out
1. If the Job Code file Type Definition Prompt for Clock In Revenue Center is enabled, the employee will
be prompted to select their Revenue Center during the Clock In procedure.
C-24
Clock In/Out
1 Employee Class
2 Personnel | Employee Maintenance | Sort By Class | Time & Attendance
R Clock In at Pay Rates 1-8
R Authorize Clock In
R Authorize/Perform Clock In/Out Outside Schedule or Scheduled
Breaks
R ON = Minor Employees; OFF = Regular Employees
R Clock Out with Open Checks
R Authorize Changing Revenue Centers at Clock-In
R Authorize Changing Revenue Center at Clock-In—Employees can
be allowed to authorize and/or change revenue assignments by
clocking in or out to a job code linked to another Revenue Center.
R Authorize/Perform Clock Out in the Future
1 Job Code
2 Personnel | Job Code | General | Type Definitions
R Prompt for Clock In Revenue Center—Enable this option to allow
an employee to select their Revenue Center when they are clocking in.
When this option is enabled, it will override any Revenue Center
assignments in the Job Code file and will change any existing Revenue
Center assignment in the Employee Maintenance file for the employee
who is clocking in.
Related Topics
w “Clock In/Out” on page C-24
w “Job Codes” on page J-1

Coin Changer Interface
Coin Changer Interface
Description
The 9700 System’s coin changer interface allows communication between a UWS
and a coin changer, such as the Brandt Coin Changer.
A coin changer is a device that issues the coin portion of a customer’s change
when the customer pays a check or transaction. The coin changer increases the
operator’s speed (no coins to count) and reduces mistakes caused by giving
incorrect change.
Enabling
1 Workstations
2 System Hardware | Devices | <Select Workstation> | Workstation | Type
Definition
R Enable Coin Changer—One of the RS232 ports on the UWS must be

set for coin changer interface operation using the UWS Configuration
Mode.
Related Topics
See “Configuration Mode” in the 9700 Hardware Installation Guide.
C-26
Condiment Handling
Condiment Handling
Description
Each group of menu items in the Menu Item Class File can be given one or more
of the following designations:
w being a member of a condiment group
w requiring an entry from a condiment group
w allowing an entry from a condiment group
Condiments can only be ordered after ordering a menu item and are often
programmed to print in red on remote printers that have two-color ribbons.
Condiments allow servers to customize their orders to meet a customer’s specific
request.
The Menu Item Class File is unique to each Revenue Center. Therefore, Menu
Item condiments defined in the Menu Item Master File (a System-level file) can
have different uses in different Revenue Centers. For example, the menu item
EXTRA OLIVES has different meanings in the Bar and in the Dining Room (and
may even have different price structures!).
Definitions
Condiment Groups
A condiment group serves to limit the condiment selections offered for a
particular class of menu items. For example, when ordering a hamburger, an
operator should be offered condiment choices such as “Rare”, “Mayo”, etc., but
not “Vanilla” or “Vinegar & Oil.” Examples of condiment groups include “Prep
Instructions”, “Side Vegetable”, “Desserts”, “Toppings”, etc. Condiment groups
are named in the Revenue Center Descriptor File.
Condiment groups are created by designating a menu item class to be a Member
Of up to 32 condiment groups. For example, a menu item class that contains only
the item “See Server” might be a member of every condiment group, while the
menu item class that includes “Rare”, “Medium”, and “Well” might only be a
member of the condiment group “Meat Temp”.
Classes of menu items can also be linked to Required Condiment Groups and
Allowed Condiment Groups.

Condiment Handling
Usage
Required Condiments
When a menu item class is programmed to require a condiment group, the User
Workstation requires a condiment to be selected from that group when one of
those menu items is ordered.
Members of a menu item class may have more than one required condiment link.
If so, the system forces a selection from each required group in turn. The order of
presentation is in condiment group order. Thus, if you want “Meat Temp” to be
presented before “Vegetable” make sure that “Meat Temp” is a lower number
condiment group.
Allowed Condiments
Members of a menu item class may be linked to one or more condiment groups by
an Allowed Condiment link. When one of these items is ordered, the system does
not prompt for the condiment or display a condiment selection window. However,
the allowed condiment group(s) can be accessed via direct select keys or NLU
keys, or through Touchscreen SLU keys. Allowed condiment groups may be
selected in any order.
Preparation instructions are typically programmed as allowed condiments. They
may include menu items such as “No Salt,” “VIP”, or “See Server”.
Condiments Requiring Other Condiments

Condiment can require other condiments. For example, the menu item, “Sandwich
Platter”, requires a choice of condiments, “Soup” or “Salad”. Soup in this case is a
condiment which requires a choice of soups (another condiment group). Likewise,
Salad is a condiment which requires a choice of dressings (another condiment
group).
Up to two levels of condiments can be programmed. (i.e., a condiment of a
condiment may not require or allow a condiment-- that would constitute three
levels. Any requirement or allowance in excess of two levels is ignored by the
System.)
C-28
Condiment Handling
Priced Condiments
Condiments can be priced just like regular menu items. For example, you may
want to charge 50 cents for Extra Cheese on a sandwich. Optionally, you can
include the additional charge in the price of the menu item.
Non-Priced Condiments
A menu item class may be programmed to be non-priced. (This is not the same as
being assigned a price of 0.00.) Non-priced menu items do not require a record in
the Menu Item Maintenance file and do not generate report totals. This is useful
for menu item condiments that you do not want to price or track (e.g., “Rare”).
Modify Parent Print Group

Guest checks may be programmed to use print groups to sort menu items for
printing. A condiment may be assigned to a print group and be used to change the
print group of the menu item that it follows (the “parent” menu item). With this
feature you could setup a condiment called, “As Entrée”, and link it to the entrée
print group. Selecting “As Entrée” would then change the print group of an
appetizer, for example, and force it to print with other entrées. In the event that
there is more than one such condiment, the last one entered determines the print
group of the parent menu item.
NLU Condiment Masking

To avoid displaying all the menu items linked to an NLU Group, regardless of
their applicability to the last menu item posted, you can program the System to
control what is displayed on the Menu Item Help screen. When the Revenue
Center Control option Enable Condiment Masking is enabled, only those
condiments (allowed with the parent menu item) will be included on the Menu
Item NLU that are linked to this NLU key. Non-condiment menu items linked to
this key will also be displayed.
Condiment Hiding (Previous Round)

When enabled, this option will hide (not display on the UWS) all condiments
from previous rounds when the check is picked up. This will maximize the
amount of space for the check detail on the UWS.
This feature is only supported on the PCWS. It is

not supported on the HHT.

Condiment Handling
Used in conjunction with this feature, the Disp/Hide function key is used as a
toggle for displaying or hiding condiments from a previous round. For example,
pickup a check with hiding condiments. Press the Disp/Hide key once, the
condiments will appear on the UWS. Press the Disp/Hide key again, the
condiments will disappear.
Reports
Condiments can be included in the Menu Item Report. This report has a flexible
format, specified in the Menu Item Report Configuration File. The overall format
of the report is to display, for each menu item in a selected range, a line of
definable totals, subtotalled by report group, and ending with a summary block of
predefined information. If this report is used, all priced condiments should be
included.
Priced condiments can also be included in the Menu Item Engineering Report
which provides sales ratios based on purchase cost vs. preparation cost, as well as
a performance rating.
Enabling

2 RVC Information | RVC Parameters | Format
R Hide Previous Round Condiments on Display

2 RVC Information | RVC Descriptors | Group Names | Select a Group
Name=Condiment Group Names
R Condiment Group Name fields—Enter the name for each condiment

group (up to 32). These names appear in the Workstation message
prompt.
1 Menu Item Master

Menu Item Class> | Output
R Print Group field—Enter the Print Group number (1 - 8) to which

each menu item should belong.
C-30
Condiment Handling
1 Menu Item Class

Menu Item Class> | Condiment Groups | Menu Item Type
R Regular
R Condiment—Enable this option for each class defined as a condiment
group. Menu Items in this class may only be ordered as condiments;
they may not be posted as individual items.
R Allow Menu Items in This Class to be Non-Priced

Menu Item Class> | Condiment Groups
R Required Condiment Groups field—Program this menu item class to

require a following entry from any of up to 32 condiment groups.
R Allowed Condiment Groups field—Program this menu item class to
allow a following entry from any of up to 32 condiment groups.
R Member of Condiment Groups field—Program this menu item class
to be a member of up to 32 condiment groups.
R Print Group field—Enter the print group (1 - 8) to which this class of

menu items is to belong.
R Output Links # 9 through #16—Output To Order Devices 1 through
15
1 Menu Item Price

2 Menu Items | Menu Item Maintenance | <Select Menu Item> | Pricing |
Prices
R Price field—Enter the price for every priced condiment.
1 Keyboards
Keyboard> | Key Configuration |
R Disp/Hide Cond - Keycode #11 - 648

Condiment Handling
Optional Settings

R Wrap Condiments on Guest Check—Enable this option to force as
many condiments as possible to print together on each line of the guest
check and customer receipt. Disable this option to print each condiment
on a separate line.
2 RVC Information | RVC Parameters | Format | Posting & Control | Control
R Enable Condiment Masking—Enable this option if you want the
System to display only those condiments that are allowed with the
parent menu item and are linked to this NLU key.
1 Order Device File

2 System Hardware | Order Devices | General | Order Device Options
R Print Condiments in Red—Enable this option to print condiments in
red ink (on roll printers with two-color ribbons). Disable this option to
print condiments in black ink.
R Wrap Condiments—Enable this option to force as many condiments
as possible to print together on each line of the order output. Disable
this option to print each condiment on a separate line.
1 Menu Item Class File

2 Menu Items | Menu Item Maintenance | Sort By Class | <Select Menu Item
Class> | Output | Options
R Condiment Changes Print Group of Parent Menu Item

R Consolidate Parents with Matching Condiments on Order Output
R Add Condiment Price to the Parent Item’s Price on Check Only
R Sort Condiments by Print Group
Class> | Output | Print Tender Media Color
R Print Red
R Print Black
C-32
Condiment Handling
Class> | Condiment Groups | Output Link
R Use Own
R Use Parent’s (Condiments Only)
1 Operator File
Operator> | Options | NLU
R Display Condiment Help—When enabled, display condiment help

windows when condiments are required or allowed. When disabled,
suppress the display of help windows.
Related Topics
w “Programming Menu Items” in Chapter 3 of the 9700 Feature Overview
Manual

Confidence Test
Confidence Test
Description
The Confidence Test module is designed to provide the technician/installer with a
complete diagnostics tool for testing an 9700 System. The Confidence Test can
also be used to perform the task of downloading 9700 System Application
Software to a User Workstation, PCWS, and a Remote Cluster Controller.
For additional information about the functionality and use of the Confidence Test
module, refer to the 9700 Hardware Installation Guide.
C-34
Configurable Number of Guests Confirmation Prompt
Configurable Number of Guests Confirmation

Prompt
Description
This feature offers the ability to change the number, up to 3 digits, for the “More
than 9 guests?” prompt. New Revenue Centers will default to 9. If zero is entered,
there will be no prompting.
Enabling

R Confirm # of Guests Threshold field

Consolidation
Consolidation
See “Sort Options” on page S-38.
C-36
Cover Charge Handling
Description
A Cover Charge is a preset amount which is added to a guest check on a per
person basis. A cover charge is often used when live entertainment is provided.
For example, during music performances, a 5.00 charge may be added to check
for each person at a table.
Enabling

2 System Information | Service Charge
R Service Charge Type field—A cover charge can use any Service
Charge key that is programmed to have a preset dollar amount. Select
an Open or Preset Amount type.
R Amount field—Enter the dollar amount of the cover charge (maximum
9999.99).
Automatic Cover Charge

The cover charge can be set to increment automatically by the number of covers
entered at the covers prompt when a check is begun.

R Cover Charge field—In this field specify the service charge to be
used; it should be a preset $ type.
R # Guests Before Auto Service Charge field—This field must be set to
a value of at least 1.

Related Topics
C-38
Credit Authorization Interface
Credit Authorization Interface
Refer to the 9700 CA/EDC Installation Manual related to the CA/EDC Driver that
the establishment is using. See “Related Manuals” in the Preface.

Credit Card
Credit Card
Description
Credit cards, such as a VISA and American Express, are defined in the Tender/
Media File as “Payment Type” keys. When a payment key is used, the amount
entered subtracts from the amount due on the current transaction balance, e.g.,
open check. If the result is 0, the check is closed and the transaction terminated.
Definitions
Credit Card Preamble

A credit card preamble is the first one to four digits of a credit card account
number that serves to identify the credit card type. For example, VISA account
numbers begin with 4 and American Express account numbers all begin with 37.
Thus, for VISA cards the preamble is “4*”, which will cause the System to
recognize as a VISA any credit card number that begins with a 4.
Usage
A Direct Access Key Placed on the Keyboard

Each credit card has its own appropriately labeled “hard key,” and is selected by
simply pressing the key. These keys provide the fastest access and are usually
placed on a cashier keyboard.
Linked to a Tender/Media NLU key

Pressing this NLU key will display a help screen of payment keys to select from.
Credit cards are selected by entering the credit card’s NLU number. By linking
credit cards to one NLU key, keyboard space is conserved.
Linked to a Tender/Media SLU key

This is only available when using the UWS/3 Touchscreen. Pressing the SLU key
would generate a “menu” of payment keys to select from. Credit cards are
selected by pressing the appropriately labeled key. By linking credit cards to one
SLU key, keyboard space is conserved.
C-40
Credit Card
Credit Card Lookup

When an account number is entered or read by the magnetic card reader, the
system “looks” for a match in the preamble field in the Tender/Media File. This
reduces the risk of charging a payment to the wrong card or a type that is not
accepted by the property.
This method requires the Credit Card Select and Credit Card Recall keys be
placed on the keyboard.
Credit Card Recall

A tender key may be programmed for use with credit card recall. If this feature is
used, the tender key may be used to post the credit card information to the check,
using the [Credit Card Lookup] key. This may be done at any time in the
transaction, even as the first item, without entering a payment amount and without
closing the check. This information is then recalled by entering the amount paid
and pressing [Credit Card Recall].
In the event of multiple credit card tenders to a single guest check, the [Credit
Card Recall] key recalls the credit card information that was posted last. If the
Seat Filter is active, it recalls the last information that was posted to the current
seat number.
Credit Card Number Validity: The Mod 10 Check

A tender key may be programmed to perform the Mod 10 check on the credit card
number. The Mod 10 check uses the check digit (the last digit of the credit card
number) to test certain credit cards (including AMEX and most Visa and
MasterCard) for a valid credit card number. This is intended as a check for an
erroneous entry-- it does not authorize the credit card charge.
The Mod 10 algorithm works as follows for credit card numbers with an even
number of digits.
Example
A credit card with the account number 3712-3456-7890-1234 is entered. The
9700 System adds every other digit, starting with the left-most digit, and
multiplies the sum by 2:
(3+1+3+5+7+9+1+3) x 2 = 64
Next, the system counts the number of these digits that are greater than 4, and
adds that number to the total. In this example, 3 of the digits (5, 7, and 9) are
greater than 4.
3+64 = 67. The system adds this sum to the sum of all the still uncounted
digits, excluding the last digit:
(67+7+2+4+6+8+0+2) = 96

Credit Card
The last digit of any credit card number is always the difference between the
product of this formula (in this example, 96) and the next highest number that
ends in zero (in this example, 100). In this example, the difference is 4, which
is used as the check digit (the last digit) of the account number. If the formula
total and the final digit do not add up to a number ending in zero, the System
prompts, “INVALID CREDIT CARD NUMBER”.
This formula works regardless of the number of digits in the account number.
If the account number is an odd-numbered series of digits, the formula works
in reverse: digits in the even numbered positions are added and doubled;
digits in the odd numbered positions are added next.
The credit card tendering features described above

are not to be confused with Credit Authorization.
The 9700 System can be configured to use CA/EDC
features. Refer to 9700 CA/EDC User’s Manual.
Enabling
1 Tender Media
2 System Information | Tender Media
R Key Type field—Select Payment.
2 System Information | Tender Media | General | Key Type=Payment |
Category=POS Ops Behavior | Ops Behaviors
R Reference Entry Required—The credit card number is a reference

entry.
2 System Information | Tender Media | Key Type=Payment |
Category=Credit Card Options
R Check Credit Card Expiration Date
R [Tender/Media] key programmed for use with a credit card
C-42
Credit Card
Options
1 Tender/Media File
R Preamble field
R Use With Credit Card Recall
R Credit Card Validity Test
R PMS or Credit Card Reference Entry field—Select from the
following options:
w 19 Digit
w 16 Digit

Category=Charge Tip Options
R Charged Tip Required—Enable this option to assume overpayment

to be a charged tip. Disable this option to require charged tips to be
entered separately.
R Charged Tip Amounts—Select from the following options:
w Must Be Less Than Payment Amount
w May Be Less Than or Equal To Payment Amount
1 Keyboard File or Touchscreen File


R 627 - Credit Card Recall

R 626 - Credit Card Lookup
R [Charged Tip] key
1 Service Charges
R Post to Charged Tips Total on Tip Reports

Credit Card
Related Topics
w “Tender/Media” on page T-51
C-44
Currency
Currency
Description
The Currency File establishes the following standards for the primary (Base)
currency used by the 9700 System:
w Currency Name
w Number of decimal places
w Punctuation used to delimit thousands and decimals
w Currency symbol used and its placement (before or after the numeral)
w Degree of rounding to use for amounts due
The number of decimal places set for the Base currency establishes the number of
decimal places used in amount fields in other files in the Configurator module.
For example, the Price field in the Menu Item Price File uses the number of
decimal places that is programmed for the Base currency in the Currency File.
The currency conversion feature provides the ability to use and convert up to 30
currencies as tender/media during transactions and track currencies received for
balancing purposes. The 9700 System can define a base currency (usually the
local currency) and 30 other currencies and convert between the base currency the
other currencies using just one key per currency.
Usage
Currency conversion is particularly useful in countries that cater to foreign
visitors, some of whom may not have exchanged their currency. Hotel and
restaurant operations near airport terminals, train stations, and resorts may find
this feature useful.

Currency
Example
Currency conversion is a function of the conversion rate. The conversion rate is
used to multiply an amount in the base currency to produce the equivalent amount
in the foreign currency.
The table on the next page provides a sample of conversion rates from a local
paper (in this case, the base currency is $US). The left column is the rate for
converting to the base currency (Other=$US). The right column is the reciprocal
rate ($US=Other). Some papers will express the conversion rate both ways, others
in only one.
Country Currency Other=$US $US=Other
Canada Dollars 1.1494 0.9700

Britain Pounds .5705 1.7530
France Francs 5.758 0.1737
Hong Kong Dollars 7.7912 0.1283
Indonesia Rupiah 1922.01 0.000520
Japan Yen 137.20 0.007289
Greece Drachma 184.45 0.005422
Reports
A line item total of each currency used is defined in the Tracking Group Reports.
The scope of the total is determined by the scope of the report to which the
Tracking Group is linked. These may include any of the Financial Reports or the
Income Audit Report.
C-46
Currency
Enabling
1 Currency
R For each Currency Conversion, fill in all fields. Up to 30 Currency
Conversion keys can be defined.
Currency conversion rates may be updated as often

as necessary, using UWS Procedures.
Type=Function | Function Key Categories=Currency | Number

Categories=Currency | Link
R 720-749 and 752-781 - Currency Conversion—Place the appropriate

Currency Conversion keys on the keyboard or link them to a Function
Lookup Key (FLU).
R [Tender/Media] key programmed as a [Foreign Cash] key—The
[Foreign Cash] key you use with the Currency Conversion key(s) must
be direct access. The Tender/Media keys must also be direct access(i.e.,
NLU keys cannot be used with the Currency Conversion keys).
1 Tender/Media
Category=POS Ops Behaviors | Ops Behaviors
R Use with Currency Conversion—Any Tender/Media key that can be

used with the currency conversion keys must have this option enabled.

Currency
Optional Settings
The following options may be enabled on a discretionary basis:
1 Workstation Table
2 System Hardware | Devices | <Select Workstation> | Type Definition
R Cash Drawer 2 for Other Currency
1 Currency File
R Base Currency field—Select from the following options:
w Divide By Rate
w Multiply By Rate
R Issue Change in Alternate Currency—Enable this option if change

should be issued in other currency.
The Amount Due is $US 50.00, the customer tenders

$CANADA 60.00, and the Conversion Rate is 1.149.
Set #2 OFF if you give change in US dollars, or set
#2 ON if you return Canadian dollars. If set to
OFF, change will be removed from the [Cash] key
specified in the Revenue Center Parameters File in
the amount of $US 2.21. If set to ON, change will be
removed for the CASH total used in the transaction
in the am ount of $C AN 2 .55. F or b alancing
purposes, it is useful to have different [Cash] keys
for the base and other currency.
C-48
Currency
Set Up Extra BASE EQUIVALENT Keys

Although you can use the same [Cash] key for the base currency and all other
currencies when tendering, we do not recommend it, because without at least one
separate [Cash] key for other currencies, there is no accountability for the other
currency receipts, except in terms of that currency. Since banks often guarantee
exchange rates for a day, you can get a total deposit that reflects receipts in a base
currency. To illustrate this, the Tracking Group shown below, lists the items that
track all receipts when you accept other currencies:
CASH 15.00 BASE CASH
-TIPS 5.00-
BASE DEPOSIT 10.00
CANADIAN $ 75.00 OTHER CASH
BASE EQUIVALENT 50.00 OTHER CASH

(in Base)
TOTAL DEPOSIT 60.00
The Tendering key that we call BASE EQUIVALENT in the Tracking Group
above could be called OTHER CASH on the keyboard (the names are
independent); set Tender/Media #4 ON (Use with Currency Conversion) for the
OTHER CASH key, not the CASH key. This key will accumulate the receipts
posted to the Currency Conversion key(s), but in terms of the Base Currency, not
the other currencies.
1 Employee Class
Procedures & Reports | UWS Procedures
R Use UWS Procedure #16: Update Currency Rates
Related Topics

Customer Display
Customer Display
Description
The Customer Display is an optional hardware device which can be used with a
workstation to display information to a customer. The display is available in a
variety models; rear mount display, turret mount display, and remote pole display
Usage
The Customer Display is typically used in cash-and-carry operations (i.e., gift
shops, fast food outlets, cafeterias, and ticket sale booths) to provide the customer
with a visual status of their transaction. The information that appears on the
display depends on the type of workstation (to which it is connected) and System
programming.
Types of Display Devices

Rear, Turret, and Remote Pole Mount displays are available. Refer to Chapter 1 of
the 9700 HMS Feature Overview Manual for a list of the Customer Display
configuration options.
Display Content
The following table identifies the information that appears on the Customer
Display (by workstation) according to the specified condition.
Condition Workstation displays...
UWS is idle optional - blank screen or

Closed1
Operator signed in - no transaction in progress blank screen
Transaction started - no sale posted 0.00
Transaction in progress - sale posted price of the item sold2
Transaction in progress - sale posted, waiting current total, e.g. Total 5.95
for next entry
Partial payment posted Paid $.$$
Due $.$$
C-50
Customer Display
Condition Workstation displays...
Full payment posted, no change due Paid $.$$ Chng 0.00

Full payment posted, change due Paid $.$$ Chng $.$$
1. If Revenue Center Parameters file Option #20 (If No Employee is Signed In, Blank the Rear
Customer Display) is set ON, CLOSED will appear on the Customer Display. When this option
is set OFF, a blank screen will be displayed.
2. If you are using a PCWS, an environment variable can be used to control the amount of time sales
information appears on a customer display.
Display Format
The Customer Display provides for the display of a single line of information that
includes brightly illuminated, 1/2-inch characters. As many as 20 alphanumeric
characters can be included on the display.
As sales are posted at the workstation, the Customer Display shows the price for a
few seconds, and then the current total amount due for the transaction. The total
amount due remains displayed until the next item is posted.

Customer Display
Enabling
The customer display is installed as a separate add-on device. Refer to the 9700
Hardware Installation Manual for specific installation instructions.
1 Workstations
Definition
R Enable Rear Display

R Display an “E” in Customer Display if Exempt
R If No Employee Is Signed In, Blank Rear Customer Display
C-52
Customer Receipt
Customer Receipt
Description
A customer receipt is a paper copy record of a Fast Transaction. Customer
receipts may be programmed to print all of the transaction detail, or just the
summary data (i.e., subtotal, tax, gratuity if any, amount paid, etc. Customer
receipts are usually printed on roll printers).
Usage
Customer receipts are usually printed on a roll printer, and may be programmed to
print in one of three ways:
Line-By-Line Customer Receipt

Each detail item prints as keys are pressed. If this method is used, voids print as
individual entries on the receipt. Items do not consolidate and are not sorted, as
each item prints as soon as it is posted. This method of printing provides faster
service, because when the transaction is completed, the receipt is ready to be
presented to the customer. Other printing tasks, such as validation chits, cannot
print on a printer designated as a line-by-line customer receipt printer. When a
transaction is picked up after being service totalled, it is no longer in line-by-line
mode.
Buffered Customer Receipt

All transaction detail is buffered (held in memory) until the transaction is
complete. The [Tender/Media] key used to close the transaction (e.g., [Cash]) is
programmed to print the customer receipt. If items were voided during the
transaction, the posting and the void cancel each other out, and neither appears on
the receipt. Sort and consolidation programming may affect the appearance of
items on the receipt.

Customer Receipt
On-Demand Customer Receipt

All transaction detail is buffered (held in memory) until the transaction is
complete. The Tender/Media key used to close the transaction is not programmed
to print a customer receipt. The operator may use the [Print Customer Receipt]
key to generate a receipt at any time after the transaction ends, as long as the
following are true:
w a receipt printer is assigned in the Workstation Table, and,
w the Revenue Center has the On-Demand Customer Receipts option enabled
(RVC Information | RVC Parameters | Options | General). This option
overrides the Workstation option Do Not Clear Screen After Trans. (System
Hardware | Devices | <Select Workstation> | Options | Type Definition),
preventing the transaction from being cleared from the workstation display. If
this option is disabled, the receipt prints automatically; use of the [Print
Customer Receipt] key is not required.
Sort and consolidation programming may affect the appearance of items on the
receipt.
Credit Authorization
Only one credit card payment may be posted to a line-by-line fast transaction. If
multiple payment types are used in a single line-by-line fast transaction (e.g.,
credit card and cash), the credit card payment must be last.
The [Credit Card Lookup] key is used for credit authorization in this type of
transaction. The Type Definition for Credit Card [Tender] keys must be
programmed to either of the following settings:
w Amount Required
w Assume Paid in Full
The latter option is the usual choice for retail operations, in which charged tips
and change due generally do not occur.
C-54
Customer Receipt
Operation
To post a credit card payment to a line-by-line fast transaction,
w Press the [Credit Card Lookup] key. The workstation prompts Enter
credit card info.
w Swipe the credit card through the magnetic stripe reader, or type the credit
card number and press [Enter]. The workstation prompts for the amount
to be tendered, if the credit card [Tender] key is programmed to do so.
w Enter the amount tendered (if required). The UWS submits the credit card
transaction for authorization. Upon approval, it posts the tender.
Enabling
1 System Descriptors
2 System Information | System Descriptors | General
R Property Name field

2 RVC Information | RVC Descriptors | Category=Miscellaneous
R Transaction Related Total Names fields—These include Subtotal,
Tax, Payment, etc.
2 RVC Information | RVC Descriptors | Headers and Trailers
R Printing Names fields—These include Customer Receipt Header
Lines, Order Receipt Header Lines, Check Header Lines, etc.
1 Workstations
2 System Hardware | Devices | <Select Workstation> | Printers | Printers
R Customer Receipt Printer field—Specify the printer used to print
customer receipts.

Customer Receipt

R 524 - Print Customer Recpt

2 RVC Information | RVC Parameters | Format | Sorting
R Customer Receipt Sort Type field—Choose from among 8 options
controlling sorting and consolidation of menu items on customer
receipts.
1 Menu Item Class

Menu Item> | Output | Menu Item Type | Devices
R Print On Customer Receipt—Select this option to cause Menu Items

in this Class to print on customer receipts.
1 Discounts
2 System Information | Discounts | Output | Options
R Print On Customer Receipt—Select this option to cause this
Discount to print on customer receipts.
1 Service Charges
2 System Information | Service Charges| Output | Options
R Print On Customer Receipt—Select this option to cause this Service
Charge to print on customer receipts.
C-56
Customer Receipt
1 Tender Media
2 System Information | Tender Media | <Select Key Type> | Output |
Options
R Print Customer Receipt—Select this option to force the customer

receipt to print when this key is pressed.
R Print On Customer Receipt—Select this option to cause this tender/
media entry to be included among the things that are printed on the
customer receipt.
Optional Settings
Here is a list of some of the possible options that may influence the format and
content of a Customer Receipt. Some of these options may not be compatible with
one another. Before incorporating them in your database, refer to the 9700 HMS
Programming Manual for additional information and considerations.
1 Workstations
Definition
R Do Not Clear Screen after Trans—Enable this option if On-Demand

printing is to be used.

R Customer Receipt Header Lines fields 1, 2, and 3—Three lines of up
to 32 characters can be used to create a header for customer receipts.
R Training Check/Receipt Header Lines fields 1, 2, and 3—Three
lines of up to 32 characters can be used to create a separate header for
customer receipts that are printed by employees who have been placed
in the training mode.

Customer Receipt

2 RVC Information | RVC Parameters | Format | Print Output
R Minimum Lines Per Roll Check/Receipt field—This feature is used
if customer receipts are presented to the customer in a folder and the
page must be a certain length to fit properly in the folder.
R Print Tenders after Summary Totals on Checks & Receipts
R On-Demand Customer Receipts
R Print Checks & Receipts Unsupervised if on Roll Printer—Enable
this option to prevent the UWS from issuing a prompt and requiring
confirmation when sending to a backup printer.
R Don’t Print Check Open Time on Customer Receipts
R Print Amount Paid Double Wide on Checks
R Print “Your order number is: XXXX” at Bottom of Receipts
R Print Order Type Name on Customer Receipt and Guest Check
1 Tender/Media File
2 System Information | Tender Media | <Select Key Type Payment> | Key
Type | Ops Behavior
R Amount Entry Is Required

R Assume Paid in Full
System Information | Tender Media | <Select Key Type Payment> | Key

Type | Printing Options
R Print Guest Check Trailer on Fast Transaction Customer Receipt
1 Operator File
R Line-By-Line Customer Receipt
C-58
Customer Receipt


R 626 - CCard Lookup/Ask
Related Topics
w “Line-By-Line Customer Receipt” on page L-8
w “Sort Options” on page S-38

Customer Receipt
C-60
D
Data Redundancy
Description
The Data Redundancy feature creates and maintains an exact copy of a PC’s
primary hard disk database and the PC’s Redundant Update File on a backup PC’s
hard disk. Thus, at any time, all information necessary to completely reconstruct
the database is available.
For a complete description, see “Data Redundancy” in the 9700 System Setup and
Maintenance Manual.
9700 HMS A to Z Feature Reference Manual D-1

Database Backup and Database Restore
Description
The database that is stored on a PC (including the primary database files and the
Redundant Update Files) may be backed up to another PC using the Database
Backup module in the 9700 Application Program Group. A database may be
restored to a PC from another PC using the Database Restore module.
Usage
These two modules can be used to create a backup database to protect you from
data loss in the event that the primary PC completely fails. These two modules can
also have maintenance uses in a variety of circumstances.
Example 1
Extensive changes are required in the current database. The person in charge of
making the changes is extremely busy, and can only devote short periods of time
to the task. In this case, the database can be backed up to another PC, where the
programmer can make the changes at their leisure. When reprogramming and
testing is complete, the database can be restored to the primary PC, replacing the
old database. No interruption to restaurant operations is necessary during the
reprogramming period.
Example 2
Your restaurant chain has opened a new branch location on the other side of town.
The database from the existing site can be backed up, and restored to the PC at the
new site. The need for some reprogramming at the new site is inevitable (e.g., a
new Employee File). However, some large files are identical in both locations
(e.g., all Menu Item Files, Employee Class File, Tax Class and Tax Rate Files,
etc.). By using the restored database as a base, much of the programming
necessary for the new restaurant’s database can be recycled.
D-2
Enabling
1 Employee Class

Other Utilities
R Run the Database Backup Program
R Run the Database Restore Program

Database Maintenance
Description
Database Maintenance is an on-going requirement. Changes to menu item files,
employee files, etc., are a constant requirement in a busy restaurant. The 9700
System offers six methods to update a database. In each case, changes may be
implemented without interrupting POS Operations.
Database changes may be implemented at any of the following times:
w Some changes are implemented immediately by the System (e.g., changes to

the Menu Item, Discount, Service Charge, and Tender/Media files).
w Some are implemented at the beginning of the next transaction. (e.g., System
Parameter, Revenue Center, and Keyboard files are included in this group.)
w Some are implemented the next time an employee signs in (e.g, Employee,
Operator, and Cashier files).
w Some are implemented only when the database is reloaded using the Reload
button in the Control Panel module (e.g., hardware configuration files).
Usage
System Configurator
System Configurator provides complete control over the database. In multiple
PC systems, System Configurator can be run from any PC even while the
system is running POS Operations. This is particularly useful in busy
establishment and for 24-hour operations where “down time” must be
avoided.
UWS Procedures
UWS Procedures include actions managers may take, “on-the-fly,” to modify
or update the contents or status of the system and database. This method
provides the most convenient way to maintain the database. However, UWS
Procedures are limited to essential files such as the Employee File, Menu
Item, Currency Conversion File, and the Remote Printer Redirection File.
D-4
Remote Log-In to System

Authorized users can log into the System via modem from a remote location
using Windows NT’s Remote Access Service (RAS) through VNC or
pcAnywhere. For example, a dealer could dial into a customer’s system and
use System Configurator without having to physically visit the site.
Timed Database Changes

SQL functions may be used to make changes to the database. These changes
can be programmed in advance and then executed at a specified time. This
provides unattended operations and the ability to maintain the database during
non-business hours.
External Program from an Autosequence

An external “batch” file can be created in advance and then executed at the
time reports are taken. This batch file will contain the SQL functions
necessary to modify or update the contents or status of the system and
database.

The database can be backed up to another PC, where changes can be made,
and then restored to the primary PC, replacing the current database.
Audit Trail
The Audit Trail module keeps a record of all changes made to the 9700 database,
as well as the identity of the employee who made the changes.
Reports
Audit Trail Report

Each record in the Audit Trail Report includes:
w The module to which the change was made (e.g., Configurator)
w The date and time that the change occurred
w The type of change made (e.g., field edit, record deletion, autosequence reset)
w The identity of the employee who made the change
w In the case of database changes made in Configurator or UWS Procedures, the

Audit Trail record also includes the Previous and Current data entered in
the field.

Enabling
Optional Settings

Categories=General | Link

Type=Function | Function Key Categories=General | Number
R 300 - Mode
R 303 - Field Help
1 PC Autosequences
2 Reporting | PC Autosequences | <Select Step>

R Type field—Select 3 - External Program. When the Autosequence
reaches this step in the report sequence, the external program executes
automatically. An external program can be used to update the database.
R Filename field—Enter the filename of the external program.

1 Workstations
2 System Hardware | Devices | <Select Workstation> | Options | Type

Definition
R Close Cash Drawer Before New Trans.
R Do Not Clear Screen After Trans.
D-6
1 System Parameters

R PC Containing Audit Trail File field—If this field is set to 0 - None,
then no Audit Trail is kept.
1 Access Levels
2 Personnel | Access Levels | General

R Eight security access levels can be programmed in this file. Each file in
the database (e.g., Employee File) can then require one of the eight
access levels for access or editing.
1 Employee Class

Privileges
R Configurator Level field—Link each Employee Class with a security
level in the Configurator Access Level File.
R Reset the Audit Trail
R Run the Audit Trail Program

R Enable each selection for each procedure an employee is allowed to
use.
Related Topics
w “Access Levels” in Chapter 7 of the 9700 Feature Overview Manual.
w “Audit Trail” in Chapter 7 of the 9700 Feature Overview Manual.
w “User Workstation Procedures” on page U-9

Date and Time Format
Description
The 9700 System prints and displays the date and time on the following:
w Guest checks
w Customer receipts
w Output printers and VDUs
w Journals
w Reports
w Operator display
w Clock-in/out entries
Date and Time Formats

You may select from two formats for both the date and time. The available
formats are as follows:
Item Format Example
Date month-day-year 06-12-2001

day-month-year 12-06-2001
Time 12-hour (AM/PM) 08:30AM 12:00PM 05:00PM 12:00AM
24-hour (military) 08:30 12:00 17:00 00:00
The Configurator module always uses 24-hour time

for calculations and for field entries, such as the
start and end times of a Serving Period, or of a shift
in the Time Clock Schedule.
D-8
Enabling
1 System Parameters
2 System Information | System Parameters | General | Options

R Use DDMMMYY Format
R Use 24 Hour Clock
Optional Settings
1 System Parameters

R Include Time Check Was First Printed in UWS Clsd Chk Rpt—
Enable this option to print a line in the UWS version of this report
showing the time the check was first printed.
R Include Time Check Was First Printed in PC Clsd Chk Rpt—
Enable this option to print a line in the Report Writer version of this
report showing the time the check was first printed.

R Print Open and Closed Time on Checks
R Print Service Total Time Stamp on Checks

Default Touchscreens
Description
A Default Touchscreen automatically displays under a certain condition unless
or until a different condition overrides it. Default touchscreens may be assigned at
the system level for each Revenue Center and operator.
Usage
These are the initial Touchscreens that display when an employee signs in at a
UWS. Higher priority screens will take precedence even if other Touchscreens are
programmed. For example, a Serving Period Touchscreen (level 5) will display
only if other Touchscreens at levels 1-4 are not active.
Priority Level Default Touchscreen File defined in
1 Training Mode Touchscreen Assignment File

2 Operator Operator File
3 Employee Employee Class File
4 User Workstation Workstation Table File
5 Serving Period File Serving Period File
6 Revenue Center Touchscreen Assignment File
D-10
Enabling
1 Operators
2 Personnel | Employee Maintenance | Sort By Operators | <Select

Operator> | General
R Default Transaction Touchscreen and HHT Default Touchscreen
fields—Select the touchscreen to appear after each operator signs in to
the system.
1 Employee Class

General
R Default Transaction Touchscreen and HHT Default Transaction
Touchscreen fields—Select the touchscreen to appear after an
employee in this Employee Class signs in to the system.
1 Workstations
2 System Hardware | Devices | <Select Workstation> | Revenue Centers

Touchscreen fields (1 - 8)—Assign a default touchscreen for each
User Workstation to use in each Revenue Center in which it is active.
1 Serving Periods
2 RVC Information | Serving Periods | <Select Serving Period> | General

Touchscreen fields—Select the touchscreen to appear when this
Serving Period becomes active.

1 Touchscreen Assignment

R Default Sign-In Screen field
R Default Transaction Screen field
R Default Training Screen field
R Default UWS Procedures Screen field
R Default UWS Reports Screen field
R Numeric Entry Screen field
R Alpha Entry Screen field
1 EHT Touchscreen Assignment
2 Touchscrns & Keyboards | EHT Touchscreens | Touchscreen Assign

R Default Sign-In Screen field
R Default Transaction Screen field
R Default Training Screen field
R Numeric Entry Screen field
R Alpha Entry Screen field
Related Topics
w “Touchscreen Configuration” in Chapter 2 of the 9700 Feature Overview
Manual
D-12
Descriptors
Descriptors
Description
Descriptors are various transaction terms which appear on the UWS display,
guest checks, and customer receipts. Some descriptors are defined for the whole
system, while others are Revenue Center-specific.
Example
Below is an example of a guest check header:
Ocean City Seafood Company

The Best Crabs in Maryland
Catering and Private Parties Available
Enabling
Enabling descriptors is simply a matter of entering the descriptor name or phrase
in the appropriate fields in the System Descriptor and the RVC Descriptor files.
2 System Information | System Descriptors | General

R Property Name field
Tax, Payment, etc.
R Discount, Service Charge, and Tender/Media SLU Touchscreen Names
fields
R HHT Discount, Service Charge, and Tender/Media SLU Touchscreen
Names fields
R Discount and Service Charge Itemizer Name fields

Descriptors
2 RVC Information | RVC Configuration | General

R Revenue Center Name
1 Report Configuration
2 Reporting | Report Configuration |

R Report Type
R Report Name
1 Menu Item Class
Class> | Output
R Print Name 2 On Order Output Instead of Name 1
Class> | General
R Use Name 2 on Touchscreens Instead of Name 1
R Use Name 2 on HHT Instead of Name 1
1 Order Devices
2 System Hardware | Order Devices |

R Order Device Header field
R Display/Print Revenue Center Name on Orders—This option prints
the Revenue Center Name in double-wide characters.
R Print Both Menu Item Names

R Do Not Print Revenue Center Name Line in Journal Entry Headers
R Print Trailer Lines on Split Check if On-Demand
2 RVC Information | RVC Parameters | Order Types

R Print on Order Printers
D-14
Descriptors
R Output to VDUs
2 RVC Information | RVC Descriptors | <Select Category>

Tax, Payment, etc.
R Printing Names fields—These include Customer Receipt Header
Lines, Order Receipt Header Lines, Check Header Lines, etc.
R Labels for Seat Number Entries
R Time Clock Adjustment Names
R Main and Sub-Menu Level Names
R Condiment Group Names
R Menu Item NLU Names
R Sales Itemizer Names
R Thai Tax Descriptor Lines

Discounts
Discounts
Description
A Discount reduces the price of an item or the subtotal of a check. Discounts may
be applied using one of four methods:
w as a fixed dollar amount (e.g., $1.00)
w as an open dollar discount, for which the operator enters the dollar amount of
the discount
w as a fixed percentage (e.g, 15%)
w as an open percentage discount, for which the operator enters the percentage
to be discounted.
Discountable items are determined in the programming of the Menu Item Class
File and the Discount File. A discount may be applied to a menu item if the menu
item is programmed with the same itemizer as the discount. In this way, discounts
may be programmed to affect all or only some types of menu items (e.g., food,
liquor, etc.).
Usage
Item Discounts
Discounts may be applied to individual menu items. If a discount key is
programmed as an Item Discount key, the discount will apply to the last item
entered. Menu item classes may be programmed to be item discountable.
Subtotal Discounts
Discounts may be applied to an entire transaction or to all menu items included in
a specific discount itemizer.
D-16
Discounts
Discount Itemizers
A menu item class may be programmed to post the sales price to one of fifteen
discount itemizers. This posting defines which itemizers are used to calculate the
discount when a discount key is used.
For percentage discounts, the amount of the discount is computed as a percentage
of the total value in all discount itemizers set for this key.
Example 1
Assume a 50% discount key is programmed only to compute on discount
Itemizer 1. If two items are entered in the transaction, SALAD for 5.00
(programmed to add to discount itemizer 1) and STEAK for 10.00
(programmed to add to discount Itemizer 2), this key would discount 50% of
Itemizer 1 only, or 2.50.
For amount discounts, the discount amount is compared to the total in all
discount itemizers linked to the discount. If the amount in the itemizers is
equal to or greater than the discount amount, the discount amount will apply.
If the itemizer total is less, no discount is applied, and the operator receives
the prompt, “DISCOUNT AMOUNT TOO LARGE”.
Example 2
Assume a 6.00 discount is programmed to compute only on discount Itemizer
1. Using the example above, the discount is 5.00, since the total in the
itemizer is less than 6.00.
If you attempt to give a discount and none of the menu items on the check
have the same discount itemizer as the discount, the error message, “NO
SALES TO DISCOUNT”, will display and the discount does not take place.

Discounts
Subtotal Discount Itemizers

A subtotal discount may be programmed to post against either the total
original amount of the itemizer or against the amount of the itemizer less any
item discounts. This feature is controlled by the System Parameter option
Item Discounts Net Subtotal Discount Itemizers (System Information |
System Parameters | General). This feature is best illustrated by the following
example, which uses a subtotal percentage discount.
Burger 5.00
Item Discount 1.00
Subtotal 4.00
Percentage Subtotal Discount 50%
Subtotal
Option #12 OFF (2700 style) Option #12 ON (4700 style)

5.00 x 50% = 2.50 (5.00 - 1.00) x 50% = 2.00
Discount Type Definition Discount Type Definition
Reset Itemizers must be Reset Itemizers may be enabled
disabled for the Item Discount. or disabled for the Item Discount.
Resetting Itemizers
Discount itemizers may be programmed to reset, which prevents multiple
discounts from being applied to the same itemizer.
Prorating Itemizers
Discount itemizers may be programmed to prorate, allowing successive
applications of a discount to decrease the itemizer. This feature is controlled
by the Discounts Type Definition Prorate Discount Itemizers (System
Information | Discounts | General). In the example shown below, all menu
items posted, as well as the discount applied, are linked to the same discount
itemizer.
Transaction Balance
Type Def. #9 set OFF Type Def. #9 set ON

Transaction Activity
Type Def. #15 set: Type Def. #15 set:
ON OFF ON OFF
Menu Items are entered $10.00 10.00 10.00

50% disc. is applied to balance 5.00 5.00 5.00
D-18
Discounts
Transaction Balance
Type Def. #9 set OFF Type Def. #9 set ON

Transaction Activity
Type Def. #15 set: Type Def. #15 set:
ON OFF ON OFF
50% disc. applied to remaining balance 2.50 0.00 UWS prompts:

“NO SALES ARE
50% disc. applied a 3rd time 1.25 -5.00 DISCOUNTABLE”
50% disc. applied a 4th time 0.62 -10.00 (Balance remains 5.00)
Allocate Subtotal Discounts as Item Discounts

Subtotal discounts may be programmed to post to reports as though they were
item discounts. This allows Net Sales figures on reports, particularly those on the
Menu Item Sales Report, to include the effect of these discounts. Tracking Totals,
which may be used on many reports, include item discounts but not subtotal
discounts. This feature allows all menu item totals (including Tracking Totals) to
post net of subtotal discounts.
This feature is controlled by the Discounts Type Definition Allocate Subtotal
Discounts as Item Discounts (System Information | Discounts | General).
Example 1: Percentage Subtotal Discount

A customer orders a salad, a steak, a beer, and dessert. When paying the
check, the customer presents a discount coupon for 20% of the price of all
non-alcoholic items (i.e., the discount does not apply to the beer). The table
below illustrates report posting when Type Definition #16 is set ON for this
discount.
Percentage Subtotal Discount
Net Sales
Item Price Discount Discount Discount Posted to
Itemizer Allocation Amount Reports1
1. Steak 12.00 1 20% x 12.00 2.40 9.60
2. Salad 2.00 1 20% x 2.00 0.40 1.60
3. Beer 3.00 2 0 02 3.00
4. Dessert 6.00 1 20% x 6.00 1.20 4.80

Discounts
Gross Sales 23.003

Discount 4.00 1
Net Sales 19.005 = 19.004
1. The figures in this column equal the Price minus the Discount Amount that is allocated to
this menu item.
2. Because beer is not linked to Discount Itemizer #1, it is not discounted. The Discount
amount allocated is $0.00, and the full price posts to reports.
3. This figure equals the sum of all menu items in the transaction.
4. This figure equals the sum of all menu item sales posted to Reports. This is the total Net
Sales posted for this transaction.
5. This figure equals Gross Sales minus the Discount amount. This is the guest check total for
this transaction.
D-20
Discounts
Example 2: Amount Subtotal Discount

A customer orders a salad, a steak, a beer and dessert. When paying the check,
the customer presents a discount coupon for $2.00, applicable to any non-
alcoholic items (i.e., the discount does not apply to the beer). The table below
illustrates report posting when Allocate Subtotal Discounts as Item
Discounts is enabled for this discount.
Amount Subtotal Discount
Net Sales
Item Price Discoun Discount Discount Posted to
t Allocation1 Amount2 Reports3
Itemizer
1. Steak 12.00 1 12.00 / 20.00 = 0.6 0.6 x 2.00 = 1.20 10.80
2. Salad 2.00 1 2.00 / 20.00 = 0.1 0.1 x 2.00 = 0.20 1.80
3. Beer 3.00 2 0 04 3.00
4. Dessert 6.00 1 6.00 / 20.00 = 0.3 0.3 x 2.00 = 0.60 5.40
Gross Sales 23.005
Discount 2.00 1
Net Sales 21.007 = 21.006
1. Figures in this column equal the menu item price divided by $20.00 (the sum of the price of all menu items
linked to Discount Itemizer #1).
2. Figures in this column equal the Discount Allocation for this menu item, multiplied by $2.00 (the amount
of the discount.)
3. Figures in this column equal the Price minus the Discount Amount allocated to this menu item.
4. Because the beer is not linked to Discount Itemizer #1, it is not discounted. The Discount amount allocated
is $0.00, and the full price posts to reports.
5. This figure equals the sum of all menu items in the transaction.
6. This figure equals the sum of all menu item sales posted to Reports. This is the total Net Sales posted for
this transaction.
7. This figure equals Gross Sales minus the Discount amount. This is the guest check total for this transaction.

Discounts
Considerations
In order to maintain the integrity of totals posted to reports, the following
operations are restricted for transactions that include this type of discount
(i.e., Allocate Subtotal Discounts as Item Discounts is enabled):
w Split the check
w Memo tender the check
w Add this type of discount while the seat filter is active
w Add to another check (but a check may be added to this one)
Reports
If the reports below print total sales as “Net Sales”, then item discounts (including
subtotal discounts programmed to act as item discounts) affect the sales totals. If
the report prints total sales as “Gross Sales”, then totals sales do not reflect
discounts. The reports include:
w Menu Item Food Cost Report
w Major Group Food Cost Report
w Family Group Food Cost Report
The net value of all discounts is recorded on the following:

w System Financial Report
w Employee Financial Report
w Income Audit Report
D-22
Discounts
Item Discounts and Subtotal Discounts may be recorded in Tracking Groups on

the following reports:
w Income Audit Report
w Cashier Financial Report
w Time Period Report
w Serving Period Report
w Menu Item, Major Group, Family Group

Sales Reports
Total Item Discounts and Total Other Discounts are tracked in the Sales Summary
Block, which can be programmed to print on the following reports:
w Menu Item Sales Report
w Major Group Sales Report
w Family Group Sales Report
Enabling
1 Discounts
2 System Information | Discounts
This file defines each type of discount used in the system. Discount privilege
groups and discount itemizers are among the fields assigned in this file. The
file also includes a Tax Class field that determines which, if any, tax classes
are forgiven by each discount.

Categories=Transactions | Link

Type=Function | Function Key Categories=Transactions | Number
R [Discount] key

Discounts
1 Menu Item Class
Class> | General
R Item Discounts May be Applied to These Menu Items
R Discount Itemizer field—This field links the menu item class with a
particular discount itemizer. Discounts will only apply to menu items
which are linked to the same discount itemizer. Selecting “0” in this
field means the menu item class is not linked to any of the discount
itemizers and is not discountable.
Optional Settings
1 System Parameters

R Post Food Cost Totals Net of Item Discounts
R Item Discounts Net Subtotal Discount Itemizers

R Round Discount and Service Charge % Entries
R Round To 0, 10 Discount and Service Charge % Rounding
R Discount and Service Charge % Rounding: Round to Nearest 0 or 10

R Allow Void Of Discount in Current Service Round Only
2 RVC Information | RVC Parameters | Posting & Control | Taxes

R Allow Discounts to Affect Japanese Excise Tax Threshold
2 RVC Information | RVC Parameters | Posting & Control | HHT

R Display Prices of Menu Items, Discounts, & Service Charges When a
Check Initially Displays
D-24
Discounts
1 Discounts
2 System Information | Discounts | General

R Tax Class field—By linking to a particular Tax Class, discounts may
be programmed to forgive some or all types of tax computed on the
discounted items, depending on what is allowed by local tax laws.
R Discount Type field—There are several options available for this
field:
w Select Open Amount Discount or Open Percentage Discount (as
appropriate) to require the operator to enter an amount every time
this discount is used.
w Select Preset Amount Discount or Present Percentage Discount

to cause the discount to be calculated on the basis of a percentage
of the discountable transaction total.
R Employee Meal—If this option is enabled, the discount amount will be

added to the Employee Meals total. An [Employee Meal] discount key
should not be used in conjunction with an [Employee Meal] Tender/
Media key that posts to the same total. Discounts post as a negative
entry and tender/media keys post as a positive entry (a payment).
R Discount 100% up to Amount—Enable this option to limit the
amount of a discount.
R If No Amount is Entered, Use the Full Discountable Amount—
Enable this option to apply the discount to the full discountable balance
of the check. Disable this option to prompt the operator to enter an
amount.
R Item Discount
R Prorate Discount Itemizers
R Allocate Subtotal Discounts as Item Discounts on Reports

Discounts
1 Employee Class

Transactions | Service Charges
R Authorize/Perform Posting of Discounts in Privilege Groups 1, 2,
and 3—Discount keys may be linked to one of three privilege groups
to limit operator access. If you try to use a discount key that is linked to
a privilege group for which you are not privileged, the system will
prompt to enter the ID of an authorized person. Discounts not linked to
a privilege group (privilege group = 0) may be posted by any operator.

Transactions | Other Employees Checks
R Post Discounts to Checks Belonging to Another Operator

Voids & Returns| Voids
R Authorize/Perform Void of Discounts from a Previous Round
Related Topics
w “Itemizers” on page I-1
w “Service Charge” on page S-19
D-26
Disk File
Disk File
Description
A Disk File is created on the PC’s hard disk to record output from the 9700
System. A disk file can be used as an electronic journal, or it can store reports.
Usage
During POS Operations, transactions are posted to the Open Check File and the
Closed Check File. An electronic journal creates an ASCII file of every
transaction throughout the system. This “archive” is usually used to audit checks.
If Time In Attendance is used, timeclock files and other labor files are stored.
If the Audit Trail or Transaction Log are enabled, they generate an ASCII file on
the PC’s hard disk.
Report Writer reports, PC Autosequences, and UWS Autosequences can be
programmed to send their output to a disk file instead of a printer.
Totals Sets may also be saved to files on the PC’s hard disk.
Enabling
1 Devices
2 System Hardware | Devices | <Select Device> | General

R Device Type field—You can define several Disk Files, with each
having a unique file name.
2 System Hardware | Devices | <Select Device> | Printers

R Journal field—For each device defined as a Disk File, select a disk file
to receive all output directed to this device.

Disk File
1 Workstations
2 System Hardware | Devices | <Select Device> | Workstation

R Journal Printer field—Select a disk file to receive the journal output.
1 PC Autosequences

R Print/Display field—Select an output option.
R Disk File Device field—Select a device to receive the disk file output.
1 UWS Autosequences

R Print/Display field—Select an output option.
R Disk File Device field—Select a device to receive the disk file output.
1 System Parameters

R PC Containing Audit Trail field—If this field is set to 0, then no
Audit Trail is kept.
R Enable Transaction Log
1 Employee Class

Privileges | Other Utilities
R Reset the Audit Trail

R PC Name List—Select the active PCs for this Revenue Center.
R PC With Check and Status Files field
D-28
Disk File
Related Topics
w “Audit Trail” in Chapter 7 of the 9700 Feature Overview Manual
w “Journal” in Chapter 7 of the 9700 Feature Overview Manual
w “Open and Closed Check Files” on page O-8
w “Transaction Log” in Chapter 7 of the 9700 Feature Overview Manual

Disk Full Warning
Disk Full Warning
Description
The 9700 System may be programmed to display a prompt at both the PC and the
UWS indicating that the PC’s hard disk is in danger of becoming full.
The Disk Full Warning feature monitors the PC currently in use, not the primary
PC programmed for the database. This prevents warnings from being displayed
when the primary PC’s hard disk is in danger of becoming full, but the System is
running on a backup PC.
Usage
The PC’s hard disk is used to store many data files for the 9700. These may
include:
w the Open Check file
w the Closed Check file
w a Journal
w saved Totals Sets
w reports printed to disk files
w Time Clock files
w a Transaction Detail Log
w an Audit Trail file
These files must be cleared periodically to prevent the hard disk from becoming
full. (This may be done in a variety of ways, including printing the contents of the
files, transferring the data to other storage media, etc.) When a potential Disk Full
situation arises, the System issues a warning prompt in a number of locations.
D-30
Disk Full Warning
User Workstation Prompt

If the hard disk is in danger of becoming full, a warning prompt appears on the
customer display of the UWS whenever an operator attempts any of the following
check operations:
w Begin
w Pickup
w Transfer
w Adjust
w Reopen
The warning message informs the user of how much disk space remains on the
PC. Pressing the [Clear] button will remove the message from the display.
System Configurator Prompt

If the hard disk is in danger of becoming full, a prompt appears on the PC monitor
under the following conditions:
w when the user starts System Configurator
w when the user begins a new edit session (e.g., opens a file)
w before the user adds records to a file
w after the successful addition of records to a file
The prompt informs the user of how much disk space remains on the PC. Pressing
the [Clear] button will remove the message from the display.
Control Panel Prompt

If the hard disk is in danger of becoming full, the following display appears on the
PC monitor if . . .
w the Control Panel is started, or
w the amount of free space dips below the threshold while the Control Panel is
running (even if it is an icon).
The prompt informs the user of how much disk space remains on the PC. Pressing
the [Clear] button will remove the message from the display.

Disk Full Warning
Enabling
1 PC Table
2 System Hardware | Devices | <Select PC> | General

R Disk Full Threshold field—Enter the level of remaining space on the
PC’s hard disk (in megabytes) at which the System issues prompts (on
both the PC monitor and all UWS’s) that the disk is in danger of
becoming filled. The suggested setting for this field is 10 megabytes. If
the system will be required to save a large number of reports or other
files to the PC’s hard disk, the setting should be higher.
D-32
Dopplebon Printing
Dopplebon Printing
Description
Dopplebon order printing prints a separate order chit for each item in the current
service round.
Usage
This style of printing is often used in Europe where orders are distributed
manually to various food stations, i.e., salad station, dessert station, grill station,
etc.
Enabling
1 Order Devices
2 System Hardware | Order Devices | <Select Order Device>

R Print Doppelbon—Select this option to enable Doppelbon printing for
this order device.
R Print Doppelbon Summary—Select this option if you want the
Doppelbon printer to print a summary to the output device.

Dopplebon Printing
D-34
E
Edit Detail
Description
The Edit Detail feature uses the System Interface Module (SIM) to recall a
customer’s last guest check from a third-party database. Some or all of the detail
items from that previous guest check can then be posted to the current guest
check.
Usage
SIM uses the Interface Script Language (ISL) to capture a customer’s last guest
check from a third-party software package (such as a database of guest
information) and display it on a touchscreen beside the current open guest check.
Example
A customer calls Personal Pizza and says, “This is Joe Decker. Give me my usual
order, please.” The operator replies, “Good evening, Mr. Decker”, and presses the
[Delivery] key on the UWS/3. The [Delivery] key generates a SIM script, which
displays the touchscreens described on the following pages.
9700 HMS A to Z Feature Reference Manual E-1

Edit Detail
This SIM script is programmed to display an entry box that prompts for the
customer’s name. The operator enters Decker, and the script executes a search in
the third-party database.
The search finds a matching record, and the script prompts for confirmation.
E-2
Edit Detail
The operator presses [Yes] to confirm that this is the correct customer. The SIM
script then opens a guest check and prints guest check information lines for this
customer, as shown in lines 1 through 13 on the touchscreen below.
The customer’s last order appears in the right side of the display, with the first
menu item highlighted. The operator can perform any of the following actions:
w Press [Enter] to post a highlighted menu item to the new check.
w Press the [Up] or [Down] arrow keys to move through the detail of the
previous check.
w Press [Edit Detail, Transfer All] to post the entire contents of the previous
check to the new check.
w Press [Clear] to reject all menu items on the previous check, and display an
order screen.
Guest check information

detail lines, captured
from th is cus tom er ’s Guest check detail from
record in the third-party t h i s c u s t o m e r ’s l a s t
database, and posted to c h e c k , re a d y t o b e
this guest check. posted to the current
open guest check.

Edit Detail
The customer says, “Give me everything I ordered last time, except for the
mineral water.”
The operator can highlight each menu item from the previous check except for the
mineral water, and post each one individually.
Instead, the operator presses [Edit Detail, Transfer All] to post all menu items to
the new check. She then highlights the mineral water on the new check, and
presses [Void] to remove it.
The operator then presses [Clear] to exit this screen, and return to the UWS’ main
menu screen.
E-4
Edit Detail
Enabling
1 WS Touchscreens

R 548 - Edit Dtl Xfr All
Related Topics
w “Guest Check Identification” on page G-19
w “Guest Check Information Detail Lines” on page G-26
w “System Interface Module” on page S-50.
For additional information about the System Interface Module, refer to the 9700
System Interface Module Manual.

Employee Class Field Editing Privileges
Employee Class Field Editing Privileges
Description
Employee Class Field Editing Privileges provide additional control as to which
employees are able to change an employee’s class in Manager Procedures.
Enabling
1 Employee Class

Procedures & Reports
R Can Change Employee Class in Employee File and UWS Procedures
E-6
Employee Magnetic Cards
The Custom Employee Card feature is designed to allow any employee card, other
then a MICROS employee card, to be used to sign-in an employee to a UWS, or
any other function that the MICROS employee card is capable of performing.
In order to support this feature, an ACSII file named “magcard.cfg” must be
created in the /usr/9700/etc directory to define the record format of the custom
magnetic card. Since this file is a “user-defined” file, it is not supplied with the
9700 Software.
Any ASCII text editor (e.g., Notepad) may be used to create the magcard.cfg file.
Usage
Each UWS will read the magcard.cfg file when any of the following conditions
occur:
w When POS Operations is started
w The Reload button is pressed
w A UWS is stopped and started
w The database is downloaded to the UWS
In reading the file, the UWS will search for either a matching UWS #, Revenue
Center, or the System symbol (*). If a match or the System symbol is found, the
UWS will store the record in memory.
If a match is not found, only the MICROS employee card will be able to be used
as an employee card.
The custom employee card may also be used on a Remote Card Reader.
Permissions
The magcard.cfg file permissions should be read/write. To set these permissions,
log in to Windows NT as Administrator and use Explorer to set the File Attributes
for the file.

Record Format
The magcard.cfg file is programmed in the /usr/9700/etc directory and each line
entry must have a carriage return.
The record format is as follows:
[* or R<rvc#> or W<uws#>] <track#> <field#> <start#>
<length#>
Spaces are required between each field.
Field Description
* The record is valid for all UWS and Revenue

Centers.
R# The record is valid for all UWS in the specific

Revenue Center.
The record is valid for this UWS only.
W#
Track# Track 1 or 2. Only one track may be read.
Field# Field within the track.
Start# Starting position on the track to read.
Length# The number of characters to read. If a field
separator is encountered, or the end of track is
encountered, then the length will be truncated.
For example, let’s say our custom employee magnetic card can be used by all
UWSs and is formatted as follows:
Track 2, the employee number is the first field, the first field is 15 Digits, with the
last 8 digits being the employee ID. The following would be the correct entry in
the magcard.cfg file:
*2178
As an additional support, the word “debug” may be included in the magcard.cfg
file. This command must be on its own separate line in the file. The debug
command will help in debugging the custom card configuration, if there is a
problem.
If the debug command were added to the above example, it would look like this:
*2178
debug
E-8
NOTE
If a change is made to the magcard.cfg file while

POS Operation is running, POS Operation must be
stopped and started, the Reload button must be hit,
or the UWS must be stopped and started in the
Control Panel, in order for the change to take
affect.
Hierarchy
If there are several different types of employee cards used at one site, there is a
hierarchy of how the magcard.cfg file is read. For example, let’s say the following
records appear in a magcard.cfg file:
*2178
R51 2 1 7 7
W4 2 1 7 8
The hierarchy for the example above would be as follows:
If Record is... ...then it is overridden by:
*2178 R51 2 1 7 7
R51 2 1 7 7 W4 2 1 7 8
Employee Setup Procedure

Assuming that the magcard.cfg file is programmed correctly, the custom card can
be used in UWS Procedure #3: Employee Setup (Personnel | Employee
Maintenance | <Sort By Class> | <Select Class> | Procedures & Reports) to
program an Employee ID. If the employee ID on the custom ID is greater than 10
digits the number will be truncated. The custom card is used in the same manner
as the MICROS employee card.

Prompts
Prompt What it Means Action Required
Magnetic card is the The magcard.cfg file is Verify

wrong type programmed programming.
incorrectly.
Magnetic card This UWS requires all Press [Clear] and
required for employee ID entries to swipe card.
employee ID entry
be card swiped rather
then manually entered.
Enabling
The file magcard.cfg file must be programmed correctly in the
/usr/9700/etc directory.
Related Topics
w Refer to the 9700 Hardware Installation Manual.
E-10
Employee Meals
Employee Meals
Description
An Employee Meal may be a “shift meal” that an employee consumes during the
course of a shift, or it may be a meal that the employee consumes while dining in
the establishment off-duty.
A restaurant may offer an employee meal using a variety of methods:
w The employee may be offered a percentage discount (e.g., 50% off, 100% off,
etc.)
w The employee may be offered a dollar amount discount (e.g., $3.00 towards
the purchase of any meal)
w The employee may be offered any item from a special employee menu
w The restaurant may ask that the employee pay for the meal at time of purchase
w The restaurant may use payroll deduction to charge for employee meals
The 9700 System offers two methods of tracking such specially priced meals—by
entering the reduction as a discount, or by closing the transaction with a tendering
key reserved specifically for that purpose.
A discount key is usually used when employees are offered some percentage (e.g.,
50% off the regular price) or a discount with a fixed ceiling (e.g., 50% off up to
$5.00).
A tendering key is usually used instead of a discount when the employee meal is
offered as a 100% benefit, or where the discount is computed manually by an
operator.

Employee Meals
Usage
If Employee Meals are entered using a discount key:
Begin a transaction and enter the menu items desired. Press the [Employee Meal]
discount key. The system prompts the operator for either the Employee Number or
the Employee ID number of the employee purchasing the meal. Enter the number
and tender the transaction.
If Employee Meals are entered using a tender key:

Begin a transaction and enter the menu items desired. Press the [Employee Meal]
tendering key. The system prompts the operator for either the Employee Number
or the Employee ID number of the employee purchasing the meal. Enter the
number. The transaction is closed.
Employee Vouchers
Each Revenue Center can be programmed to print vouchers when an employee
discount or employee tender is used, to be signed by the employee receiving the
employee meal. Vouchers print at the validation printer designated for the UWS
being used. The illustrations below show an example of each type of voucher,
followed by a description of each line item.
1 EMPLOYEE DISCOUNT VOUCHER

2 -------------------------------------------------------
3 CHECK: 474
4 SERVER: 101 JOE
5 DATE: SEP25’94 8:30AM
6 RVC: LOUNGE
7 DISCOUNT: 50% EMPL MEAL
8 PERCENT: 50 %
9 AMOUNT: 3.25–
10 EMPLOYEE: 501 WILEY
11 X -------------------------------------------------
Employee Discount Voucher
1 EMPLOYEE DISCOUNT VOUCHER

2 -------------------------------------------------------
3 CHECK: 474
4 SERVER: 101 JOE
5 DATE: SEP25’94 8:30AM
6 RVC: LOUNGE
7 PAYMENT: MANAGER MEAL
9 AMOUNT: 6.83
10 EMPLOYEE: 501 WILEY
11 X -------------------------------------------------
Employee Payment Voucher
E-12
Employee Meals
The table below provides a line-by-line description of the data printed on the
voucher.
Line
Description
No.
1 This line describes the voucher being printed.

2 A single line prints between the header and the detail items.
3 This line prints the guest check number (or transaction number) in
double-wide format.
4 This line prints the Employee Number and Check Name of the
transaction operator.
5 This line prints the date and time that the voucher printed.
6 This line prints the name of the Revenue Center in which this
discount was applied.
7 This line prints the type of transaction, followed by the descriptor
for the key used. As shown in the examples above, “Discount”
prints when a [Discount] key is used; “Payment” prints when a
[Tender] key is used.
8 This line prints the percentage that is applied to the transaction
total. This line does not print if an amount discount or a tender key
is used.
9 The item printed on the Amount line varies with the type of key
used. For a [Discount] key, this line prints the amount discounted.
For a [Tender] key, this line prints the amount paid.
10 This line prints the Employee Number and Last Name of the
employee who is receiving the employee meal.
11 A single line prints to allow the employee receiving the meal to
sign the voucher.

Employee Meals
Reports

w Total number and dollar amount of employee meals posted.
Employee Labor Detail Report

w Total number and dollar amount of employee meals posted.
Employee Labor Summary Report

w Total number and dollar amount of employee meals posted. Employee Meals
may be added as a Tracking Group entry to any other reports.
Enabling

R ON = Use Employee Number With Employee Meals; OFF = Use
ID#—[Employee Meal] keys require a reference entry. This option
determines whether to use the employee file record number or the
employee ID number.
1 Discounts

R Employee Meal
1 Tender Media

Category to Display=Charge Tip Options
R Post Amount to Gross Receipts on Tip Reports—This type
definition is usually disabled for employee meal keys.

Category to Display=POS Ops Behaviors
R Employee Meal
E-14
Employee Meals
Optional Settings

R Print Voucher When Employee Discount or Employee Meal Tender is
Used
1 Discounts
2 System Information | Discounts | <Select Discount> | General

R Privilege Group field—An employee meal discount key may be
assigned to one of three privilege groups that restricts its use to certain
employee classes (e.g. managers).
1 Tender Media
2 System Information | Tender Media | <Select Tender Media> | General

R Privilege Group field—An employee meal tender key may be
assigned to one of three privilege groups that restricts its use to certain
employee classes (e.g. managers).
1 Employee Class

Transactions | Service Charges
R Authorize/Perform Posting Of Discounts In Privilege Groups 1, 2, and
3

Transactions | Tenders
R Authorize/Perform Posting Of Tender/Media In Privilege Groups 1, 2,
and 3

Enhanced Backup and Takeover (EBUTO)
Description
Enhanced Backup and Takeover (EBUTO) allows a Backup PC to take over
9700 operations in the event that the primary PC loses power or fails. The backup
PC allows all the workstations that were connected to the failed PC to continue
operating.
Usage
EBUTO is used as a security measure. If a PC fails, an establishment can continue
to operate without downtime if the operational redundancy option is enabled.
EBUTO requires double wiring, a LAN environment, and data redundancy, which
is a security measure that copies the database from the original PC to the backup
PC.
Enabling
1 PC Table
2 System Hardware | Devices | <Select Server PC> | General

R Backup PC# field—Connect User Workstations to both PC’s (primary
and backup). Click the PC Status button in the 9700 Control Panel
module, then make the Backup PC active.
E-16
Optional Settings
1 Employee Class

Privileges | Control Panel
R Make PCs Active or Inactive from the Control Panel
R Make PC Active on its Backup from the Control Panel
R Change Backup PC Number from the Control Panel

Error Corrections
Error Corrections
For more information on this feature, see “Void Item” on page V-18
E-18
Error Log
Error Log
Description
The Error Log module records operational information while the 9700 System is
running, and the contents of this file can be used by trained personnel to diagnose
activity in the System. The System creates an Error Log File for each PC in the
System.
Usage
The Error Log File grows continuously while the 9700 System is in operation.
Each PC’s Error Log File should be reset periodically to prevent it from
consuming too much space on that PC’s hard disk.
Enabling
The Error Log module does not require any specific programming in the System
Configurator module. Any employee with a valid PC Functions ID can open the
Error Log module, and print, save, or reset the file.

Error Log
Related Topics
For a complete description of Error Log functions and file management, refer to
“Error Log” in the 9700 System Setup and Maintenance Manual.
E-20
Euro Currency Conversion
Description
Euro currency support prepares European users to cope with dual currency
transactions that will be common during transition to the new monetary unit
known as the euro.
The euro is a common currency used throughout most of Europe by countries that
are members of the European Union. Rather than using marks in Germany and
francs in France, for example, both countries will use the euro.
Euro coins and notes will be introduced on January 1, 2002, with national
currencies being phased out by the end of the transition period on July 1, 2002. At
this time, only the euro will be recognized as currency in the member countries.
All non-member countries will continue to accept only their local currency.
Euro support entails handling transactions involving:
w National currency—Pre-euro currency (e.g., the deutschemark in Germany,
the lira in Italy).
w Base currency—The primary currency of the database (either the euro or the
national currency).
w Alternate currency—The secondary currency (either the euro or the national

currency).
w Foreign currency—Other currencies, such as the U.S. dollar, or other

European currencies.

Usage
Full implementation of the euro will take place over three years from 1999 to
2002 in order to provide a smooth transition. During this transitional period, both
the euro and local currencies will be recognized as legal tender; however, all
currency conversions must be performed according to the European Union’s
“triangulation” formula (the first currency is converted to the euro, which is then
re-converted into the second, target currency).
The sections that following describe the planned phasing-in of the euro.
Phase I—Base Currency is the National Currency

January 1, 1999 until December 31, 2001—During this phase, The national
currency remains the base currency. All currency conversions must go through the
euro, even though the euro is not yet the base currency [e.g., In converting
Deutsche Marks (DEM) (Germany) to French Francs (FFR) (France), you must
convert from DEM to euro to FFR].The guest check will print the totals in both
the national and euro currencies.
Payments will be accepted in the euro during this phase for some non-cash
payments such as check and debit cards. A Tender Media option for Payment key
types, This Tender Media is Euro Currency, is similar to the Use With
Currency Conversion option, but will be restricted to the euro only.
When programming conversion rates, program as if the euro is the base currency.
9700 HMS Operations interprets these conversion rates correctly until euro
implementation is complete in 2002. This interpretation means that currency
conversion rates will not have to be changed as users progress through the phases
of euro implementation.
Phase 2—Base Currency is the Euro

January 1, 2002 until June 30, 2002—During this phase, the national currency is
the alternate currency. Euro currency is issued as legal tender on January 1, 2002.
Until euro hard currency is available, change cannot be given in the euro. As such,
a Euro Cash key should not be programmed on the system, and all foreign
payments should be configured to dispense change in either the alternate
(national) or foreign currency. Once euro hard currency is available, change can
be given in either the euro or foreign currencies.
Guest checks will continue to print totals in both the euro and the national
currency. Tips may be declared in both the euro and alternate currencies.
Historical data will be converted.
E-22
Phase 3—Alternate Currencies are Discontinued

July 1, 2002 Onward—National currencies cease to be legal tender on July 1,
2002. National coins and bank notes are cancelled. The euro becomes the sole
currency of the European Union (Belgium, Germany, Spain, France, Ireland, Italy,
Luxembourg, Holland, Austria, Portugal, and Finland). The euro is handled like
any other currency. All special handling of the euro by the 9700 HMS System will
be disabled by clearing the field that identifies this as a Euro System.
The table below defines all countries, including their currency symbols and final
currency rates, which will participate in the European Monetary Union, effective
January 1, 1999.
Final
National
Country Symbol Currency Rate
Currency Name
1 EURO =
Belgium Franc Belge BEF 40.3399

Germany Deutsche Mark DEM 1.95583
Spain Peseta ESP 166.386
France Franc francaise FRF 6.55957
Ireland Irish pound IEP 0.787564
Italy Lira italiana ITL 1936.27
Luxembourg Franc Lux LUF 40.3399
Netherlands Nederlandse Gulden NLG 2.20371
Austria österr. Schilling ATS 13.7603
Portugal Escudos PTE 200.482
Finland Markka FIM 5.94573
A currency rate must consist of six significant figures. All calculations with
currency rates must be performed with six digits after the decimal point. Currency
rates of member states of the European Monetary Union (EMU) are irrevocably
fixed and can not be changed by the property in order to include a “conversion
service charge.”
Currency rates of member States of the European Monetary Union (EMU) are
irrevocably fixed and cannot be changed by the property in order to include a
“conversion service charge” (see conversion table for all participating currencies).

Conversion from a national currency1 to euro must be done via a division:

euro = Amount to be converted / Conversion Rate
Conversion from euro to a national currency must be performed with a
multiplication:
National Currency = euro x Conversion Rate
Conversion from a national currency unit to another national currency unit must
be performed via the triangulation method. For example, converting from Belgian
Francs to Deutsche Marks must be calculated utilizing the following method: First
convert the Belgian Franc to euro, and, after that, from euro to Deutsche Mark,
always with the appropriate conversion rates and under strict observance of the
above conversion and rounding rules.
Conversion from a third currency (e.g. U.S. Dollars) to a national currency will
also require the strict observance of the triangulation method.
Rounding is not permitted during calculation except for displaying and printing
totals.
Accepting Other National Currencies

To accept other currencies, both currencies of the European Monetary Union
participating Countries and States, as well as Countries and States which do not
participate in the EMU, the following conversion and rounding rules must be
performed.
If your systems runs on base currency = euro (not recommended before
January1, 2002), only one of the steps below must be performed to convert a
foreign currency into euro.
If your system runs on base currency = national currency (at least only valid
until June 30, 2002), all conversions must be performed via the euro. This
conversion method is called the Triangulation method.
1. If ‘national currency’ or ‘national currency unit’ is mentioned in the text, only the currencies of member
states for the European Monetary Unit will be included in the definition or formula. All other currencies
(from states which are not participating in the European Monetary Unit, e.g. US Dollar, British Pound) will
be called a ‘third currency’ or ‘other currency.’
E-24
Triangulation Method
Converting from a Belgian Franc to a Deutsche Mark, for example, it must be
calculated by the following method: First converting the Belgian Franc to euro,
and then from euro to Deutsche Mark, always with the appropriate conversion
rates and under strict observance of the conversion and rounding rules.
For the following examples, it is assumed that 1 euro = 1.95583 DEM.
w Conversion: National Currency to euro
Converting the amount of 15.50 DEM to euro would invoke the following
method of conversion:
15.50 / 1.95583 = 7.925024 euro
All conversions from national currency to euro will require the division of the
national currency amount by the conversion rate.
w Conversion: euro to National Currency
Converting the amount of 27.50 euro to DEM would invoke the following
method of conversion:
27.50 x 1.95583 = 53.785325 DEM
All conversions from euro to national currency have to be multiplied by the
conversion rate.
The formulas mentioned above are part of the legal requirements and must be
performed exactly as published.
Rounding and/or truncating of the currency rate before calculation is
prohibited.
Rounding and/or truncating is only allowed for printing and displaying totals.
Rounding and/or truncating of totals in the middle of a calculation is
prohibited.
All results must be calculated with six digits after the decimal point.
All subsequent versions to those listed above will also include euro
functionality.
There is no special activation code required to enable euro functionality as an
additional feature, as it is part of the foundation software.

Enabling
1 System Parameters

R Enable Euro Dollar System—This option must be enabled in order to
make the euro functionality and all requirements available in this
System. After enabling this option, you must stop and restart the 9700
System.
R Euro Dollar is Base Currency—This option will be used during the
Transition period where both national currency and euro currency may
coexist.
R Issue Change in National Currency—This option will be used during
the Transition period where both national currency and euro currency
may coexist.
R Euro or National Currency field—This field directly corresponds to
the Currency File of the 9700 System and depends on the enabling of
option Euro Dollar is Base Currency. If this option is disabled, the
national currency is base currency. Enter the object number for the euro
from the Currency file here.
R If the option Euro Dollar is Base Currency is enabled, the euro is base
currency. Enter the object number for the national currency from the
Currency file here (this would mean that euro is the base currency, and
therefore the “old” national currency must be entered as a currency in
the Currency file).

R Eliminate Blank Lines from Guest Check
R Print Tenders After Summary Totals on Checks & Receipts
2 RVC Information | RVC Parameters | Taxes

R Print VAT Lines Before Summary Totals
1 Currency
2 System Information | Currency |

R Euro Conversion Rate to your National Currency
E-26
1 Tender Media

Category to Display=Printing Options
R Print Sales Itemizers
R Print Summary Totals
R Print VAT Lines on Check or Receipt

R This Tender Media is Euro Currency
Related Topics
w “Euro Printing” on page E-28

Euro Printing
Euro Printing
Description
The following options accommodate euro printing. They are as follows:
w The System Parameters option Print Alt Summary Totals Before Base
reverses the print order of the Base and Alternate Summary Totals sections on
euro checks and receipts.
w The System Paremeters option Print Simplified Alt Summary Totals

reduces the Alternate Summary Totals section to the section header and a
single Amount Due/Payment.
w Alternate Summary Totals print the Payment total or Amount Due in single-
wide characters on euro Guest Checks and Customer Receipts.
E-28
Euro Printing
Usage
Check Printout Samples

You may change the appearance of a printed check by enabling/disabling the
options listed in the Enabling section. All of these options described are common
9700 options. Please refer to the 9700 Programming Manual.

Euro Printing
The check shown below has been done via Fast Transaction.
E-30
Euro Printing
On the check shown below, the customer is paying in euro (e.g. bank check), and
the change due will be displayed and issued in the base currency (in this example,
the French Franc).

Euro Printing
Enabling

R Eliminate Blank Lines from Guest Checks

R Print VAT Lines Before Summary Totals
1 System Parameters

R Print Alt Summary Totals Before Base
R Print Simplified Alt Summary Totals
1 Taxes

R Print VAT Lines before Summary Totals
E-32
F
Family Group
Description
A Family Group is a grouping of related menu items for reporting sales
summaries and food cost summaries.
Usage
The Family Group Sales report and Family Group Food Cost report provide sales
and cost information for each family group programmed in the 9700 System.
Example
In Samantha’s restaurant, beer, wine, and mixed drinks are menu items that are
included in family group #3, which is labeled Liquor.
Each time a beer is ordered at a User Workstation, the record of the sale is posted
to, among other places, family group sales.
When Samantha runs a Family Group Sales report for a given day, the line entry
for family group #3, Liquor, shows a single sales count and single dollar amount
totalling all beer, wine, and mixed drinks sold that day.
9700 HMS A to Z Feature Reference Manual F-1

Family Group
Reports
Family Group Sales Report

The flexible format of this report may be programmed to include any of the
following fields:
w Gross Sales count
w Gross Sales total
w Item Discount count
w Item Discount total
w Net Sales count
w Net Sales total
w Subtotal fields
A subtotal line prints for all Family Groups that are programmed with the same
number in their Report Group field.
Family Group Food Cost Report

w Quantity Prepared
w Quantity Sold
w Yield Percentage
w Total Prep Cost
w Total Sales Amount (less Item Discounts)
w Food Cost Percentage
F-2
Family Group
Enabling
1 System Parameters
2 System Information | System Parameters | Reporting

R Post Menu Item, Major Group, and Family Group Sales Totals Net of
VAT
1 Family Groups
2 Menu Items | Menu Item Maintenance | Sort By MI, Major/Family Group |

<Insert> | Type=Family Group
R For each Family Group, complete all fields.
1 Menu Item Master

General
R Family Group field
Related Topics
w “Major and Family Group Files” in Chapter 6 of the 9700 Feature Overview
Manual
w “Major Group” on page M-7

Fast Transaction
Fast Transaction
Description
A Fast Transaction is begun by pressing a menu item key. The operator does not
need to begin the transaction with a [Begin Check] key.
Usage
An operator begins a fast transaction by pressing a menu item key instead of a
[Begin Check] key. The workstation begins a check and posts the menu item or
items. A fast transaction is usually tendered immediately. The workstation may be
programmed to issue a customer receipt.
Examples of typical fast transaction environments include a retail shop, cash bar
or, carryout counter.
Each revenue center may be programmed to allow fast transactions to be service
totalled. If a fast transaction is service totalled, it may be picked up and service
totalled again, or picked up and closed, just like an ordinary guest check.
If Operator option Line-by-line Customer Receipt) is enabled, the operator may
service total a fast transaction. When the transaction is picked up after being
service totalled, it is no longer in line-by-line mode.
transaction. The Type Definition for Credit card [Tender] keys must be
w Amount Required
F-4
Fast Transaction
Operation
w Press the [Credit Card Lookup] key. The UWS prompts Enter credit
card info.
card number and press [Enter]. The UWS prompts for the amount to be
tendered, if the credit card [Tender] key is programmed to do so.
Reports
Fast transaction counts and totals post to all financial and sales reports as part of
the Checks profile section; they are not reported separately.
Fast transactions may be programmed to generate a closed check, in which case
the transaction also posts to the Employee Closed Check Report. An “F” in the
Status field indicates a Fast Transaction.

Fast Transaction
Enabling

R Allow Fast Transactions
R Fast Transactions Do Not Generate Closed Check Records—
Disable this option to generate a closed check record.

R Print “Your order number is: XXXX” at Bottom of Receipts
2 RVC Information | RVC Parameters | Order Types | General Options

R Print on Customer Receipt and Guest Check
1 Operators

R Line by Line Customer Receipt
1 Tender Media

R Amount Required
F-6
Fast Transaction

R Print Customer Receipt—When enabled, this option causes a
buffered customer receipt to print when this Tender Media key is
pressed.
R Print Check Trailer on Fast Transaction Customer Receipt
2 System Information | Tender Media | Key Type=Payment | Output

R Print On Customer Receipt—When enabled, this option causes this
tender media entry to print on the customer receipt.
1 Menu Item Class
R Print On Customer Receipt
1 Discounts
2 System Information | Discounts | <Select Discount> | Output

1 Service Charges
2 System Information | Service Charges | <Select Service Charge> | Output

1 Devices
2 System Hardware | Devices | <Select Workstation> | Printers

R Customer Receipt field—Select a printer for customer receipt
printing, which includes fast transactions.

Fast Transaction


R [Print Customer Receipt] - keycode #524


R [Credit Card Lookup] - keycode #626
Optional Settings
The following privilege options may be enabled on a discretionary basis:
1 Operators

R Cannot Perform Fast Transactions
1 Employees
2 Personnel | Employee Maintenance | Sort By Employee | <Select

Employee> | General
R International LDS Posting without Table Number Starts an LDS Fast
Transaction
Related Topics
w “Customer Receipt” on page C-53
w “Line-By-Line Customer Receipt” on page L-8
F-8
Fixed Price Meal
Fixed Price Meal
Description
A fixed price meal is a menu item that usually includes several courses of food
items, all for a pre-set price. The price of the meal is posted to the guest check
when an employee presses a Fixed Price Meal menu item key, such as [Brkfst
Combo] or [Steak Spcl]. A fixed price meal key can be defined as a direct access,
a screen lookup (SLU), and/or a number lookup (NLU) key.
The fixed price meal (the parent menu item) is composed of one or more courses
(the child menu item), from which one or more selections may be made.
Child menu items are posted separately, during the course of the meal. They are
regular priced menu items. However, when they are posted as courses of a fixed
price meal, their prices do not post to the guest check.

Fixed Price Meal
Fixed Price Meal Concepts

Listed below are brief descriptions of the concepts used in conjunction with the
Fixed Price Meal feature.
Concept Description
Child Menu Item A Child Menu Item represents the actual item ordered for each
of the courses included in a fixed price meal. When satisfying
a course requirement, the child menu item can appear on the
guest check as a non-priced, zero priced, or upcharged item.
Course Group A Course Group functions in one of two ways—it either
identifies the number of courses included with a fixed price
meal, or it identifies the menu item selections included with a
particular course. As many as 32 course groups can be
associated with a particular meal, and a course group can
contain as many selections as there are menu items. Course
groups are defined on the Fixed Price Meals tab when sorting
by Menu Item Class in the Menu Item Maintenance file.
Course Mask The Course Mask field is used in two different ways—to
identify which of the 32 course groups are associated with a
fixed price meal, or to specify the course group to which an
item belongs.
Fixed Price Meal The following keys are available for use with the Fixed Price
Keys Meal feature:
w Menu Item Course NLU Key—a number lookup key that
is used to make a menu selection for the specific course of a
fixed price meal.
w Menu Item Course SLU Key—a screen lookup key that is
used to make a menu selection for a specific course of a
fixed price meal.
Parent Menu The Parent Menu Item specifies the price of a fixed price meal
Item and identifies each of the associated course groups. For
example, the Menu Item file might contain an item described
as the Dinner Combo Meal. This fixed price meal is
programmed to cost $15.00 and include course groups one
through five. When selected, the System will post the price of
the meal to the guest check and allow the selection of a menu
item from each of the five courses.
Upcharge A menu item that is defined as an upcharge represents a fixed
price meal course selection that satisfies a fixed price meal
course selection but appears on the guest check as a priced
item. For example, an establishment might elect to offer a
larger sized portion of a menu item course selection for an
additional cost or upcharge.
F-10
Fixed Price Meal
Usage
The system uses the Seat Handling feature to organize fixed price meals on a
guest check. The system may be programmed to assign seat numbers
automatically, or to allow an employee to do it. Typically, the employee selects a
seat number and posts the fixed price meal.
NOTE
The Seat Handling feature does not need to be enabled in
order to post a fixed price meal to a guest check; the first
fixed price menu item added to the guest check will
automatically activate the feature.
Example #1 describes a guest check for a single customer who ordered a fixed
price meal. Since there is only one customer, the seat number remains at #1 for the
duration of the meal. This scenario illustrates the basic steps of a fixed priced
meal. Example #2, which follows on page F-9, describes using the seat feature to
order fixed price meals for several customers on the same guest check.
Example 1: A Basic Order

The Special Value Combo Meal includes an entree, a vegetable, a dessert, and a
soft drink, for $10.00. A customer orders the meal with chicken, rice, and a soda,
and wishes to order dessert after the meal. Samantha, the employee, takes the
following steps:
1. Presses the [Combo Meal] key. Combo Meal 10.00 appears on the display
and posts to the guest check.
2. Presses the [Courses] key. A touchscreen with course keys displays.
3. Presses the [Entree] course key. A touchscreen with entree keys displays.
4. Presses the [Chicken] key.
5. Repeats Steps 2 through 4 for the vegetable course and the soda.
6. Service totals the check.
Chicken, rice, and soda are priced menu items. However, since each has been
ordered as a course in a fixed price meal, each posts to the guest check without a
price. The chicken and rice orders print on the remote printers in the kitchen. The
employee delivers the soda, followed by the food when it is ready.

Fixed Price Meal
After dinner, the customer selects a slice of apple pie as part of the Special Value
Combo Meal. Samantha continues with the following steps:
7. Picks up the guest check.
8. Presses the [Dessert] course key. A touchscreen of dessert choices displays.
9. Presses the [Apple Pie] key. The order for the apple pie prints on the remote
printer in the kitchen.
10. Service totals the guest check again.
Apple pie is a priced menu item. However, since it has been ordered as a course in
a fixed price meal, it posts to the guest check without a price.
F-12
Fixed Price Meal
Courses
Soda Entree
Course Course
Veggie Dessert
Course Course
Fish Chickn
Pasta Ham
Touchscreens that display for this restaurant’s fixed price meal
MIKE ROSE RESTAURANT & GRILL MIKE ROSE RESTAURANT & GRILL
A WORLD OF POS-SIBILITIES A WORLD OF POS-SIBILITIES
504 504
-------------------------------- --------------------------------
TBL 1/1 CHK 237 GST 1 TBL 1/1 CHK 237 GST 1
SEP25’00 08:30PM SEP25’00 08:55PM
--------------------------------
Parent --------------------------------
1 COMBO MEAL 10.00 1 COMBO MEAL 10.00

CHICKEN CHICKEN
RICE RICE
SODA SODA
Child
SUBTOTAL 10.00 SUBTOTAL 10.00
TAX 0.50 TAX 0.50
TOTAL DUE 10.50 TOTAL DUE 10.50
APPLE PIE
SUBTOTAL 10.00
Child TAX 0.50
TOTAL DUE 10.50
Guest checks showing service rounds for this restaurant’s fixed price meal

Fixed Price Meal
Example 2: Seat Handling

George is waiting on a table of four. The first, second, and fourth diners order the
Combo Meal; the third orders a hamburger. The customers who ordered the
combo meal want the same vegetables and soft drinks, but they want chicken,
fish, and pasta, respectively, as the entree.
Ordering Fixed Price Meals by Seat

1. George begins the guest check. This system is programmed to default to
seat #1.
2. He presses [Combo Meal]. Combo Meal 10.00 appears on the display
and posts to the guest check for seat #1. The UWS advances to seat #2.
(Fixed price meal menu items in this system are programmed to
increment the seat number).
3. George presses [Combo Meal] again. Combo Meal 10.00 appears on the
display and posts to the guest check for seat #2. The UWS advances to
seat #3.
4. He presses [Hamburger].
5. George uses the [Seat] keys to advance to seat #4.
6. He presses [Combo Meal] for the last diner.
At this point, George has posted all of the fixed price meals (the parent menu
items), but none of the courses (the child menu items).
Ordering Courses by Seat

To post the courses for the fixed priced meals,
7. George presses the [Entree] course key. The UWS advances to seat #1,
the first seat for which the entree course has not been ordered.
8. He presses [Chicken]. The UWS advances to seat #2.
9. George presses [Fish]. The UWS advances from seat #2 to seat #4. 1
10. He presses [Pasta].
Each of these priced menu items post to the display and the guest check
without a price because they have been ordered as courses of a fixed price
meal. George continues to order the vegetable and soft drink courses for seats
#1, #2, and #4.
1. The UWS advanced from seat #2 to seat #4 because the customer at seat #3 did not order a fixed price
meal. When a course requirement has been satisfied (e.g., the entree for seat #2), the system searches for
the next seat number for which that course has not yet been ordered, and advances to that seat number.
F-14
Fixed Price Meal
Extra Course Items

If a guest orders more than one item in a course group, the price of the second
item posts to the guest check. For example, if a guest orders a fixed price meal that
includes a vegetable, but the guest wants french fries and a baked potato, the price
of the french fries does not post to the check (it is included in the price of the
meal), but the price of the baked potato does post (it has been ordered a la carte).
To order an extra course, the employee presses the appropriate [Course] key. The
system prompts, “Course Selection Completed – Continue Course Entry?”. The
employee presses [Enter] to continue, and orders the extra course.
The price for this second course item posts to the guest check, since the course
requirement of the fixed price meal has already been posted.
Upcharge Items
Fixed price meals can be programmed to offer a group of course items as part of
the regular price, and one or more course items for an additional charge. For
example, a fixed price meal that offers fish, chicken, or pasta as the entree may
also offer steak for an additional charge.
Operational Rules
When you activate the Fixed Priced Meal feature, it changes the way sales
information is added to a guest check. It also changes the way information is
edited, displayed, and printed. Use the information in this section to get
acquainted with these changes.
Add/Transfer Guest Check

Use the information provided below to help you understand how the Add/
Transfer feature is used in conjunction with a guest check that includes a fixed
price meal.
w When a check is added or transferred, and the check being added includes
a fixed price meal, the system assigns the meal a new seat number if the
revenue center is programmed to keep seat numbers when adding checks.
w If the revenue center is not programmed to keep seat numbers and an

employee tries to add a check that contains a fixed price meal, the System
prompts Cannot Add Without Saving <seat name>.
w If the Add procedure is used for a guest check that includes a fixed price
meal and all seats are used before the meal is posted to the check, the
System prohibits the Add transaction from occurring. In addition, if the
Add procedure is being used and the number of seats included on the
transferred check and the number of seats on the current check are greater
than 63, the System will not allow the transfer function to occur and will
display the following error message No SEAT Available.

Fixed Price Meal
w When combining checks, the System will not attempt to interleave seat
numbers. For example, if the current check contains menu items on seats
1, 3, and 5, then the System assumes that seats 1 through 5 are in use.
New detail would be assigned to seat 6.
Discounts and Service Charges

Use the information provided below to help you understand how Discounts
and Service Charges apply to a fixed price meal.
w Item discounts can be applied to a fixed price meal and to priced courses
for both percentage and flat dollar amounts.
w Percentage discount calculations include upcharged menu items.
w Service charge calculations include upcharge menu items.
w If a course selection includes a discount and the course is subsequently

removed (line item void) the discount is also removed.
Edit Seat
The Edit Seat feature can be used to change the seat assignment of a fixed
price meal to one that does not contain a fixed price meal. If you attempt to
move a fixed price meal to a seat that already contains one, the System
prompts Cannot Move Item From Seat.
Florida Surcharge Tax

If the Florida Surcharge Tax feature is enabled and a fixed price meal includes
a beverage to which the charge applies, the System calculates the surcharge
amount and posts it to the guest check in the usual manner.
Guest Check Display and Printing

The basic format of the guest check is unchanged by the Fixed Price Meal
feature. If the operator is a By-round operator, the guest check will print in the
by-round format. If an operator is an On-demand operator, the guest check
will print in the on-demand format. Guest checks containing a Fixed Price
Meal will continue to print in the usual format.
If a fixed price meal is posted to a guest check, the System always sorts
previous round detail by seat number, even if the Revenue Center is
programmed not to do so.
F-16
Fixed Price Meal
Posting Fixed Price Meal Sales

Use the information provided below to get acquainted with how the System
posts a fixed price meal to a guest check.
w The system will not allow more than one fixed price meal to post to the
same seat number.
w The [Fixed Price Meal] key can be used in connection with a quantity
key. If more than one meal is being ordered, a quantity can be entered
before the [Fixed Price Meal] key is pressed. Each meal is automatically
posted to a separate seat.
w The [Repeat Round] key can be used with fixed price meals. Items from
the previous round that are programmed to be included in a repeat round
will post to the guest check. Because course requirements were satisfied
in the previous round, these items post to the guest check as priced items.
w Open priced and weighed menu items cannot be included as a part of a

fixed price meal. They can be added to the guest check but will appear as
priced menu items.
w Fixed Price Meal and A La Carte menu items can be posted to the same
guest check. A La Carte items will always appear grouped after fixed
price meal menu item unless print groups are used to control the manner
in which information is sorted. If such is the case, the print group sort
options will override the default sort order.
w The [Course] key can be used to post course menu item selections to the
appropriate seat number. The name that appears on the key is governed by
the descriptor programmed on the Touchscreen Assign form. When a
[Course] key is used to post fixed price meal selections, the System is
responsible for identifying each seat that requires a selection for a
particular course group.
Printing
Use the information provided below to help you understand how printing
options are impacted by a fixed price meal.
w Upcharge prices will appear on order chits if the Menu Item Class option
Print Price on Order Chit is enabled.
w Upcharges will always appear on the guest check regardless of the setting
of Revenue Center Parameters Format option Do Not Print Fixed Price
Meal Courses on Guest Checks. This option also suppresses the printing
of course information on a guest check.

Fixed Price Meal
w Courses will sort by their assigned print group unless Menu Item Class
option Use Parent’s Print Group for a Fixed Price Meal is enabled.
When this option is enabled, course detail will print in the print group of
the fixed price meal.
w If a condiment associated with a course has Menu Item Class option

Condiment Changes Print Group of Parent Menu Item enabled, the
condiment print group will change the parents print group regardless of
the setting of Menu Item Class option Use Parent’s Print Group for a
Fixed Price Meal.
w You can use Menu Item Class option Add Course Price to Fixed Price
Meal’s Price on Check Only to control the way fixed price meal
information is printed on guest checks/customer receipts. When this
option is enabled, the System will add the price of each course to the price
of the fixed price meal and will print the consolidated price on customer
receipts and guest checks. When this option is disabled, the System will
include the fixed price meal price only in the information that is printed
on customer receipts and guest checks.
Before implementing this fixed price meal printing option, consider the
following:
w Manage the way fixed price meal revenue posts to major and
family group sales—This printing option provides an effective way
to manage the way menu items are posted to major and family group
totals without compromising the format of the guest check/customer
receipt.
w A selection for each course is required—This printing option relies

on the consolidation of course prices in order to arrive at the cost of a
fixed price meal. Therefore, a selection must be made for each course
associated with a fixed price meal.
w To handle those occasions when a guest foregoes a course selection

(for example, no dessert), make sure that your database includes
menu items that will add the appropriate course cost without ordering
a selection. For example, menu items like No Salad, No Dessert, etc.
w Manage course pricing carefully—As the cost of a fixed price meal

is based on the consolidation of course prices, it is imperative they
sum to the correct price.
F-18
Fixed Price Meal
w Avoid using By-Round Printing—As the price of the fixed price

meal will not be correct until a selection is made for each defined
course, By-Round printing is not appropriate.
w Upcharge pricing is not identified separately—The upcharge

amount will simply increase the price of the fixed price meal.
Reporting
Use the information provided below to get acquainted with how fixed price
meal information is reported.
w Non-priced course information will not be reported.
w Zero-priced (0.00) course information will appear on the appropriate

reports.
w Fixed price meal information will post to the major and family groups of
the fixed price meal item, not to the individual course. The exception to
this rule is upcharged items. Upcharged menu items will post to the
respective major and family group of the course item. For example, if the
price of a cocktail were treated as an upcharge, the totals for that item
would post to the family and major groups for cocktails, not for the fixed
price meal.
Touchscreen Concepts
The Touchscreen files are used to define each of the keys needed to use the
Fixed Price Meal feature. There are a variety of key possibilities but, at a
minimum, keys that facilitate the following functions need to be included on
the touchscreen:
w A key to post a fixed price meal menu item to a guest check. It is
recommended that a direct access key be used in lieu of a SLU key for
this function since Course SLUs are stay-down only until the last course
selection is made, and revert to pop-up after the last requirement is
satisfied. The System will revert to the original screen when the pop-up
takes place.
w A key that is used to post course selections to a guest check. It is

recommended that you program a SLU key for each course. This type of
key will cause the System to display the choices that are available with
the selected course. When the choice is made for a seat, the System will
automatically increment the seat number to the next seat requiring a
selection for the current course.

Fixed Price Meal
Touch Void
Use the information provided below to get acquainted with how the Void
feature functions with a fixed price meal menu item.
w If a fixed price meal is removed from a guest check using Touch Void, the
seat used by that meal will be re-used when a new fixed price meal is
entered.
w Touch Void can be used to void a single course, or the entire fixed price
meal. The System will not allow you to void just the fixed price meal
parent menu item.
w When the Void procedure is used, the System will automatically display
all detail, for previous service rounds as well as the current round, by seat,
by fixed price meal.
w A Direct Void or a Transaction Void cannot be used to remove course

information from a guest check. They can be used to remove a fixed price
meal. However, keep in mind that, due to the one fixed price meal per seat
rule, the total number of fixed price meals on a seat at any time may be 1,
0, or -1 (fixed price meal ordered, fixed price meal direct voided, direct
void of a fixed price meal).
w If a course is fulfilled and then voided, selecting another item for the same
course will fulfill the course requirement.
w A Line Item void can be used with both the fixed price meal and course
selections.
w A Last Item Void will not remove multiple fixed price meal or course
entries. Essentially, this is because a multiple fixed price meal or course is
conceptually a macro that enters the same menu items the specified
number of times and the System does not have the information needed to
void the entire last item.
Reports
Fixed price meals post to sales reports in the same manner as other menu items.
The sales count of course menu items posts to reports, while the sales amount
does not.
F-20
Fixed Price Meal
Enabling
2 RVC Information | RVC Descriptors | Group Names | <Select Course

Names>
R Course Names field—Define the name associated with each course
group. You may have up to 32 Course names.
1 Menu Item Class

2 Menu Items | Menu Item Maintenance | Sort By Menu Item Class | Insert
R Fixed Price Meal Menu Item Class Record—Add a menu item class
record for each fixed price meal.
R Consolidate Menu Items with Condiments on Order Output
Menu Item Class> | General
R Fixed Price Meal—Select this option to identify the class as a fixed
price meal menu item class.
R Free Repeat Course—Select this option if fixed price meal menu
items in this class allow a free repeat course.
R Use Parent’s Print Group for a Fixed Price Meal Course—Select
this option to use Fixed Price Meal Print Group for a course.
R Add Course Price to Fixed Price Meal’s Price on Check Only—
Select this option to consolidate fixed price meal course prices into the
price of the fixed price meal when printing a guest check or customer
receipt.
Menu Item Class> | Fixed Price Meals
R Course Mask field—Identify the course groups associated with a fixed
price meal.

Fixed Price Meal
1 Menu Item Master

2 Menu Items | Menu Item Maintenance
R Menu Item Record—Add a menu item record for each fixed price
meal.
2 Menu Items | Menu Item Maintenance | <Select Master Record> | Insert
R The Menu Item Definition is used to define the “parent” portion of the
FPM (i.e., the FPM is the menu item). Add a Menu Item Definition
record for each FPM (e.g., Breakfast Combo, Weekend Special, Steak
Night).
w Be sure to select the appropriate Master record for each definition.
w Select all Revenue Centers in which the FPM will be available.
w Specify the necessary number of price records, as well as any

default price.
2 Menu Items | Menu Item Maintenance | <Sort By Class> | <Select FPM

Class> | <Select Menu Item> | General
R Set Type Definition options as appropriate.

2 Menu Items | Menu Item Maintenance | <Sort By Class> | <Select FPM
Class> | <Select Menu Item> | Pricing
R Specify the prices for each fixed price meal record.

R Price For Fixed Price Meal Course—Select this option for each price
record that applies only to a fixed price meal.
R Price For Fixed Price Meal Course and Regular Menu Item—
Select this option if you want to use the same price record for a fixed
price meal menu item and a non-fixed price meal menu item.
NLU Method
| Function Key Categories=Sales NLU | Link

Function Key Categories=Sales NLU | Number
R [Course NLU]—Key codes #148-172.
F-22
Fixed Price Meal
1 WS Touchscreens
SLU Method
2 Touchscrns & Keyboards | WS Touchscreens | Touchscreen Style

R Course SLU—Define Course SLU key style.

R In the SLU Styles section, choose MI Course SLU styles. There should
be a SLU style for each course group defined in the Course Mask field
on the Menu Item Class form. In the Style field, select the FPM SLU
key style created previously.
R Select or create the touchscreen that will include the fixed price meal
keys. It is recommended that keys that post menu items to a guest check
be a “direct access” key type.
R Type field—Select Key Type #18 - Course SLU.
R Number field—Specify the Course SLU to which the key is linked. It
is recommended that keys that post course selections to a guest check
be a “SLU” key type. If you are defining a Course SLU key, set the
Type field to 18-Course SLU and set the Number field to the
appropriate course.

R Don’t Print Fixed Price Meal Courses on Guest Checks—Select this
option if you do not want non-priced course selections to appear on the
guest check.

Food & Beverage Interface
Description
The Food & Beverage Interface feature provides a means of linking menu item
sales activity in the 9700 System to the MICROS F & B Management System.
When the F & B System reads sales records from the 9700’s Transaction Log, the
sale of any 9700 menu item must be matched to a record in the F & B’s recipe list.
In cases where a menu item has only one recipe, it is easy to match the menu item
sale to its corresponding recipe, even if the menu item has multiple prices (e.g.,
Lunch, Happy Hour, Dinner).
However, when a menu item has multiple prices at which it can be sold, there may
be multiple recipes to which that menu item can be matched. Matching those
prices to a recipe becomes a challenge, as illustrated in the example below.
9700 F&B
Menu Item Master Menu Item Pricing Recipe List

# Name Price # Price
324 Soup Soup 1 2.50
? 27 8 oz. cup
Soup 2 3.50
? 28 12 oz bowl
Soup 3 4.00 ?
Soup 4 4.25
The Menu Item Recipe Link file provides links that allow you to match multiple
entries for a menu item’s price to specific Recipe records in the F & B System.
9700 F&B
Menu Item Master Menu Item Pricing Recipe List

# Name Recipe Link Price # Price Recipe #
324 Soup 19 Soups Soup 1 2.50 1 Cup
Soup 2 3.50 2 Bowl 27 8 oz. cup
Soup 3 4.00 2 Bowl 28 12 oz bowl
Soup 4 4.25 2 Bowl
Each record in the Menu Item Recipe Link file includes eight Recipe Name fields
for each available Menu Item price definition.
F-24
Separate entries in the Menu Item Recipe Link file are required only when
multiple recipes for a single menu item are listed in the F & B System. In most
cases, multiple recipes are used only when a difference in sale price reflects a
change in portion size.
Multiple recipes are usually not used when multiple prices are charged for the
same-sized menu item. For example, the illustration above shows that there is a
different recipe for a cup of soup and a bowl of soup. There are three different
prices for a bowl of soup (lunch, happy hour, and dinner). But because the same
menu item (bowl of soup) is served each time, a single recipe represents all three.
Many installations with a large number of menu items in the 9700 database may
require only a handful of entries in the Menu Item Recipe Link file.
Example
The Blue Parrot Cafe serves breakfast, lunch and dinner, and stocks a full bar. The
9700 database contains over 1,000 menu items. However, most of these menu
items are only offered in one size. Therefore, most menu items share the same
entry in the Menu Item Recipe Link File. There are six other records in the Menu
Item Recipe Link File, which are used for menu items that come in varying sizes,
and therefore have separate recipes in the F & B Management System.
Altering Menu Item Files: Status Options

The F & B Management System must be notified when records are altered in the
9700 System. To accomplish this, the 9700 System uses three Status options in the
Menu Item Master file to tag menu items that have changed. 9700SQL queries can
be written to create lists of changed menu items, for export to the F & B System.
These Status options are set by the System:
w 5 - F & B Added - SET BY SYSTEM ONLY
w 6 - F & B Edited - SET BY SYSTEM ONLY
w 7 - F & B Deleted - SET BY SYSTEM ONLY
The appropriate options are automatically enabled when activity takes place in
any of the following areas:
w Menu Item Master
w Menu Item Definition
w Menu Item Pricing

Resetting the Status Options

Status options #5, #6, and #7 may be reset when necessary using the utility
program resetmistat. This utility may be run as an External Program in a PC
Autosequence.
Enabling
1 Menu Item Recipe Link
2 Menu Items | MI Recipe Link |

w Complete all fields in both the Overhead and Detail views.
1 Menu Item Maintenance
2 Menu Items | Menu Item Maintenance | Sort By MI Master, Major/Family

Group | <Select Menu Item> |
R Menu Item Recipe Link field
Menu Item> | Pricing
R Recipe Number field
1 PC Autosequence
2 Reporting | PC Autosequences | <Select Step> | General

R Type field—Set this field to External Program.
R Filename field—Enter \micros\les\pos\9700\bin\resetmistat to run
the utility that resets the Menu Item Master File’s Status options.
Related Topics
w “Menu Items” in Chapter 6 of the 9700 Feature Overview Manual
F-26
Function Keys
Function Keys
Description
Function Keys are programmed onto a workstation’s keyboard or touchscreen in
order to allow an employee to perform specific operations on the 9700 system.
For ease of programming, function keys are divided into the 11 categories in the
table below.
Key
Category Function
Movement These keys are used to move the cursor or highlight bar around
Keys the operator display, or to move between screens on the
operator display. Examples include: [Down] and [Page Up].
Sales NLU These are the Number Look-up (NLU) keys used for menu
Keys items, discounts, service charges, and tender/media.
General These keys perform a variety of miscellaneous functions.
Keys Examples include: [Help], [Display Time], and [Mode].
Touchscreen A special set of keys are required to perform certain
touchscreen operations. Examples include: [TS SLU Page Up],
[TS Contrast Down], and [TS Previous Screen].
Check This category includes a variety of keys that are used to begin
Begin/ guest checks and to pick up guest checks that have been
Pickup service totalled. Examples include: [Begin Check By Table],
[Pickup Check By Number], and [Adjust Closed Check].
Check Keys in these two categories are used on guest checks that
Operations have already been opened. Examples include: [Add/Transfer
Check], [Print Customer Receipt], [Exempt Tax Rate 4], [Split
Check], [Level Select], [Transaction Cancel], and [Order
Transactions Type] keys.
Currency These keys are used for currency conversion.

Function Keys
Key
Category Function
Seats Keys in this category are used to operate the seat handling
feature. Examples include [Seat Number] and [View/Edit
Seat].
Keyboard Changes between programmed keyboards on a User
Select Workstation are performed by using the keys in this category.
Non-Sales These keys perform functions that are not directly related to
Operations guest check operations. Examples include: [No Sale], [Clock
in/Out], [Direct Tips], and [Inquire PMS 3].
Usage
Any key that an employee presses (other than a numeric key or an alpha key) is a
function key. An employee must use time clock function keys to clock in. [Begin
Check] and menu item keys begin a transaction, and discount, service charge, and
tendering keys are used to close the transaction.
Keys may be placed on the keyboard in one of two modes:
w Unshifted mode - to perform a function, press the assigned key.
w Shifted mode - to perform a function, hold down the [Shift] key and press the
assigned function key.
The shifted/unshifted key feature allows two key codes to be assigned to the same
physical space on the keyboard.
Function keys may be assigned to a Function Look Up (FLU) key, which can
combine up to eight functions on a single key. Function keys that prompt the
operator are intended for use with FLUs, in order to allow the operator to enter
information necessary to complete the function.
Assignable Function Keys

Eight [Add/Transfer] keys may be used to add or transfer checks from a specific
Revenue Center. The Revenue Center assigned to each key is programmed in the
Revenue Center Parameters File.
Sixteen [Keyboard] keys (8 for Keyboard #1, 8 for Keyboard #2) may be used to
change the current keyboard configuration to a specific keyboard configuration
from the Keyboard File. The keyboard assigned to each key is programmed in the
Keyboard File.
F-28
Function Keys
Enabling

R Add/Transfer Revenue Center fields 1 - 8
1 Keyboards or WS Touchscreen

Keyboard> | Key Configuration
R Place function keys on the keyboard or touchscreen

R Assignable Keyboard configuration keys are programmed in the
Keyboard File.
Optional Settings
1 Employee Class

R Transaction Privileges—Define the function keys that each Employee
Class is authorized to use.
Related Topics
w “Function Look Up Keys” on page F-30
w “Keyboards-User Workstation” on page K-1

Function Look Up Keys
Description
There are two types of Function Look Up (FLU) keys—Functions and Sales:
w Function key FLU keys are used to combine several functions in one key,
conserving space on a keyboard or touchscreen. These FLUs may be
programmed to select any one of up to eight functions, based on a numerical
entry preceding the keystroke.
w A Sales FLU key allows you to post a sales item that corresponds to the
current main menu level or sub-menu level with one keystroke. Sales FLUs
include either Menu Items, Discounts, Service Charges, or Tender/Media, and
may be programmed to interact with current menu level assignments.
Usage
Function Key FLUs

FLU keys may be placed on the keyboard in one of two modes:
w Unshifted—To perform a function, press the assigned key.
w Shifted—To perform a function, hold down the [Shift] key and press the
assigned function key.
To conserve space on a keyboard, Function key FLU keys are used to combine
several functions in one key. These FLU keys may be used in one of two ways:
w An operator presses the number of the required function (1 through 8),
followed by the FLU key.
w An operator presses the FLU key without first pressing a number. A help
screen displays, listing all of the functions programmed for this FLU key. The
operator selects the required function from the display and presses the number
for that function.
F-30
Example - Function Key FLU

An FLU key labeled “Check Ops” is assigned to the keyboard. This key is
programmed to offer the following set of functions:
w [Begin Check]
w [Pickup Check]
w [Adjust Closed Check]
w [Reopen Closed Check]
w [Split Check]
w [Add/Transfer Check]
George, a server in the restaurant, wants to adjust one of his closed checks. He
does not know the FLU number for the [Adjust Closed Check] function. So he
presses [Check Ops] and a help screen similar to the one shown below
displays:
1 Begin Check
2 Pickup Check
3 Adjust Closd Chk
4 Reopen Closd Chk
5 Split Check
6 Add/Transfer Chk
George presses [3] to adjust his check. When he becomes more familiar with
the System, he can adjust a closed check by pressing [3] [Check Ops].

Sales FLUs
A Sales FLU key allows you to post a sales item that corresponds to the current
main menu level or sub-menu level with one keystroke.
Example - Sales FLU

A restaurant serves an “Omelette Special” during each of its three daily meal
periods—breakfast, lunch, and dinner. During breakfast, the Omelette Special
is served with toast and hash browns. At lunch, the omelette is served with
french fries and a small salad. For dinner, the omelette is accompanied by rice
and a choice of vegetable.
The Omelette Special requires different side dishes and different condiments
for each meal, and is priced differently during each meal. For these reasons, it
is entered in the 9700 System as three different menu items.
The first menu item is active only on main menu level #1 (Breakfast), the
second only on main menu level #2 (Lunch), and the third only on main menu
level #3 (Dinner).
An FLU key labeled “Omelette Special” is assigned to the keyboard. All three
menu items are linked to this key. When Main Menu Level #1 (breakfast) is
active, pressing this key posts the first menu item. When Main Menu Level #2
becomes active, pressing this same key posts the second menu item. When
Main Menu Level #3 (Dinner) becomes active, pressing this key posts the
third menu item.
F-32
Enabling
Function Key FLU
1 Keyboards
2 Touchscrns & Keyboards | Keyboards | Keyboard Overhead

R Select or create a keyboard.
R Display—Select Shifted or Unshifted, depending upon the type of key
you wish to define.
R Select the key to be programmed. You will be switched automatically
to the Key Configuration tab.
R Preset MLvl—Select the Main Menu Level that is to become active
before the function key assigned to this location is processed. If 0 is
entered, the menu level is not changed prior to processing the keystroke
(menu levels may still be changed by the action of the key— for
example, pop-up menu levels assigned to Menu Item keys).
R Preset SLvl—Select the Sub Menu Level that is to become active
R Complete either the Unshifted Key or Shifted Key section based on the
Display type selected.
w Type—Select 10 - FLU.
w Link—Select the Link button. On the FLU Assignment form,

select the functions (up to 8) to assign to this FLU key. When
finished, select the Assign button.
R Legend Lines—These fields default to the following display for FLU

keys and cannot be modified:
****
FLU
****
R When through programming, you must reload the System in order for
the changes to take effect.

Sales Key FLU
1 Keyboards

R Select or create a keyboard.
R Display—Select Shifted or Unshifted, depending upon the type of key
you wish to define.
R Select the key to be programmed. You will be switched automatically
to the Key Configuration tab.
R Preset MLvl—Select the Main Menu Level that is to become active
R Preset SLvl—Select the Sub Menu Level that is to become active
R Complete either the Unshifted Key or Shifted Key section based on the
Display type selected.
w Type—Select 2 - Menu Item FLU, 4 - Discount FLU, 6 - Service
Charge FLU, or 8 - Tender Media FLU.
w Link—Select the Link button. On the FLU Assignment form,

select the functions (up to 8) to assign to this FLU key. When
finished, select the Assign button.
R Legend Lines—These fields default to the following display for FLU

keys and cannot be modified:
****
FLU
****
R When through programming, you must reload the System in order for
the changes to take effect.
F-34
Privilege Considerations
1 Personnel
2 Personnel | Employee Maintenance | <Sort by Class> | <Select Class>

R Various options on these tabs are used to allow employee classes access
to certain function keys (e.g., [Adjust Closed Check]) and to restrict
access to sales items. Set these options as appropriate for the selected
class.
Related Topics
w “Number Lookup (NLU)” on page N-3

F-36
G
Grace Periods
Description
A Grace Period is used to allow employees some flexibility in clocking in and
out when the time clock schedule is used.
A grace period determines how much time, in minutes, each employee will have
as grace on either side of the time they are scheduled to clock in or out in the Time
Clock Schedule File. The grace period provides a range of time within which the
employee can clock in or out without being considered early or late.
Usage
If an employee attempts to clock in or out, outside of their scheduled time, the
system may display a prompt or may prevent the clock-in or clock-out. A grace
period allows employees to arrive or leave within a reasonable number of minutes
on either side of their scheduled time.
A clock in grace period can be programmed for each employee. It overrides the
clock in grace period set for the revenue center.
Example
George, Dave, and Samantha are restaurant employees who are scheduled to clock
in at 4:00 p.m. The grace period for their revenue center has been set at ten
minutes.
At 4:06 p.m., George clocks in. He is six minutes late, according to the time clock
schedule. However, since he is within the ten minute grace period, the system
allows him to clock in.
9700 HMS A to Z Feature Reference Manual G-1

Grace Periods
At 4:11 p.m., Dave attempts to clock in. Since he has missed the grace period by a
minute, the system prevents him from clocking in. The system displays a prompt
informing Dave that manager authorization is required to enable him to clock in
now.
At 4:12 p.m., Samantha attempts to clock in. She has missed the grace period by
two minutes. However, management decided long ago that Samantha is a trusted
and highly valuable employee, and that if she clocks in late she probably has a
good reason. Therefore, the late clock in grace period field in Samantha’s
Employee File has been set to a whopping 15 minutes. Because the employee
grace period overrides the revenue center grace period, Samantha is able to clock
in 12 minutes late without requiring manager authorization.
Enabling
1 System Parameters
2 System Information | System Parameters | Timekeeping | Time Clock

Options
R Enable Time Clock Schedule
R Check For Early Clock-In
R Require Authorization For Early Clock-In
R Check For Late Clock-In
R Require Authorization For Late Clock-In
R Check For Early Clock-Out
R Require Authorization For Early Clock-Out
R Check For Late Clock-Out
R Require Authorization For Late Clock-Out
2 System Information | System Parameters | Timekeeping | Time Clock

Parameters
R Early Clock In Grace Period field
R Late Clock In Grace Period field
R Early Clock Out Grace Period field
R Late Clock Out Grace Period field
G-2
Grace Periods
1 Employees

Employee> | General | Allowances
R ON = Employee Grace Period; OFF = System Grace Period—
Enable this option to use the employee late clock in grace period
instead of the system late clock in grace period.
R Late Clock In Grace field—Enter the amount of time (in minutes) that
an employee is allowed to clock in late.
Related Topics
w “Grace Periods” in Chapter 8 of the 9700 Feature Overview Manual

Guest Check
Guest Check
Description
A Guest Check is a record of all sales to one or more customers, from the
customer’s first order to final payment (or transfer to another customer’s check).
Detail entries include menu items, discounts, service charges, voids, returns, and
tender/media entries.
The guest check record is transferred from the 9700 system’s memory to a printed
guest check that can be presented to the customer for payment.
Usage
An operator begins a guest check by pressing a [Begin Check] key. The system
may be programmed to require certain information from the operator at this point,
such as the check number, the table number, or the number of guests in the party.
During the course of the meal, the operator enters menu items in response to
customer orders. These items may be printed on the guest check in one of three
ways:
w By-round- Menu items and a subtotal print every time the guest check is
service totalled.
w On-demand - Guest check detail is retained in the system’s memory until the
check is closed. The entire check detail is printed at that time.
w Special-By-round - As in the case of On-demand, guest check detail is

retained in the system’s memory until the first time the check is printed. If
additional detail is added (e.g., menu items) after the first printing, any service
rounds that follow are also printed, just as with By-round printing.
In addition to menu items, the operator may enter any discounts or service charges
that apply to the transaction.
At the end of the meal, the check is presented to the guest for payment and then
closed with a tendering key.
G-4
Guest Check
Example
Samantha, a server in a full service restaurant, is told by the hostess that she has a
new party of four seated at table 27. Samantha takes the party’s order and then
proceeds to a UWS.
Samantha presses [2] [7] followed by the [Begin Check By Table] key. The
System assigns a guest check number to her transaction and prompts her to enter
the number of customers. She presses [4].
The system is programmed to treat Samantha as a By Round operator.
After entering the menu items that the customer ordered, Samantha takes a blank
guest check from her apron and places it in the slip printer. She presses [Service
Total]. The 9700 system prints the guest check header at the top of the check,
followed by the menu items ordered. The list of menu items is followed by a
subtotal for this service round.
After dinner, the party at table 27 orders coffee and dessert. Samantha goes to a
UWS and presses [2] [7] [Pickup Check By Table]. After pressing the appropriate
Menu Item keys, Samantha places the guest check in the slip printer and presses
[Service Total] again. The Menu Items for coffee and dessert print, followed by a
new subtotal.
Table 27 asks for the check. Samantha takes the guest check from her apron
pocket and writes “Thanks, come again” across the bottom in flowing script. (She
has recently resolved to adopt a more professional demeanor at work, and so
resists the temptation to dot the “i” with a little heart.) She presents the check to
the customers, who return it in a few minutes with cash.
Samantha picks up the check again, places the guest check in the slip printer, and
tenders the check. The system prints the total, the tender amount and type, and a
guest check trailer on the check. The guest check is now closed.

Guest Check
Reports
Financial Reports
(System, Revenue Center, and Employee)
w Total number and dollar amount of guest checks begun
w Total number and dollar amount of guest checks paid
w Total number and dollar amount of guest checks transferred
w Total number and dollar amount of guest checks outstanding
w Total number and dollar amount of guest checks carried over from the
previous period
If the report is programmed to include the optional Order Type Sales Profile
section, the following fields print for each Order Type:
w Number of checks
w Net Sales/Number of Checks average
Employee Open Check Report (User Workstation

Report)
w Check number
w Table/Group number
w Date and time opened
w Revenue center name
w Amount due
G-6
Guest Check
Employee Open Check Report (Report Writer)

w Check number
w Amount due
w Number of guests
w Number of times printed
w Summary totals (subtotal, tax, service charges, payments)
Employee Closed Check Report (User Workstation

Report)
w Check number
w Date and time closed
w Amount paid
w Status (Fast Transaction, Transferred, Cancelled, Adjusted, Training, Split,

Re-opened, and Added)
Employee Closed Check Report (Report Writer)

w Check number
w Amount paid

Guest Check
w Status (Fast Transaction, Transferred, Cancelled, Adjusted, Training, Split,

Re-opened and Added)
w Number of guests
w Transfer/split check information
w Charge tip, payment, change due
w Summary totals (subtotal, tax, service charges, payments)
Table Sales Report (User Workstation Report)

w Check count
w Checks/Sales Amount average
Enabling
1 System Parameters

R Max. Number Check Detail Entries field—The entry in this field
determines the amount of memory that will be set aside in the PC for
guest check detail.
2 RVC Information | RVC Configuration | General | Checks

R Maximum Number Open field (1 - 9999, Default=100)
R Maximum Number of Detail Blocks field (1 - 9999, Default=200)
G-8
Guest Check

R Lines on First Guest Check Page field—Enter the total number of
lines (at six lines per inch) the system prints on the first page of a check
before prompting the operator to insert a new check.
R Line Feeds Before First Guest Check Page field—Enter the total
number of lines (at six lines per inch) that the slip printer should skip
before beginning to print guest check information.
R Lines on Other Guest Check Pages field (Slip Printers)
R Line Feeds Before Other Guest Check Pages field (Slip Printers)

R Operator Assigns Check Numbers
R Print Checks & Receipts Unsupervised if on Roll Printer—Enable
this option to disable the prompt that requires confirmation in order for
output to be sent to a backup printer.

R Allow tender media to Print 2 Guest Checks and Receipts
R Print Guest Check/Receipt Header in Red
R Print Guest Check/Receipt Trailer in Red
2 RVC Information | RVC Parameters | Order Types | General Options

R Print Order Type Name on Customer Receipt and Guest Check
2 RVC Information | RVC Descriptors | Headers and Trailers | <Select

Header>
R Check Header Lines 1, 2, and 3
2 RVC Information | RVC Descriptors | Headers and Trailers | <Select

Trailer>
R Check Trailer Lines 1 through 12

Guest Check
1 Menu Item Class
R Print On Guest Check
1 Discounts
2 System Information | Discounts | Output | Options

1 Service Charges
2 System Information | Service Charge | Output | Options

G-10
Guest Check
1 Tender/Media
2 System Information | Tender Media | <Select Key Type Service Total> |

Key Type | Printing Options
R Reprint Check
R Print Summary Totals—Summary totals include the subtotal, tax,
amount due, and change due.
R Print Check Trailer
R Print Check on Demand
R Print 2 Guest Checks/Receipts (RVC Parameters Format Option Allow
tender media to print 2 guest checks and receipts must also be enabled)
R Prompt for 2 Guest Checks/Receipts (Optional)
2 System Information | Tender Media | <Select Key Type Service Total> |

Output | Options
1 Operators
2 Personnel | Employee Maintenance | <Sort By Operator> | <Select

R Number Of Guests Entry Required for New Checks
2 Personnel | Employee Maintenance | <Sort By Operator> | <Select

R On = On-demand; Off = By-round
R Special, By-round (Same as 4700 Temporary, On-demand)
1 Workstations

R Max. Num. Check Detail Entries field
R Guest Check Printer field

Guest Check


R 402-411 - Pickup Check by Number
R 412-421 - Pickup Check by Table
R [Service Total] key
R [Tender/Media] key
Optional Settings
The following options can be enabled on a discretionary basis:
1 System Parameters

R Use DDMMMYY Date Format
R Use 24 Hour Clock
1 Currency
2 System Information | Currency | Base

R Print Currency Symbol field: Before Numeral or After Numeral
G-12
Guest Check

R Minimum Lines Per Roll Check/Receipt field
R Print Unit Price as well as Line Total on Checks—This option prints
the menu item’s price if more than one is ordered.
R Print the Check Number Double Wide on Guest Checks and Customer
Receipts
R Wrap Condiments on Guest Check
R Print the Table Number Double Wide on Guest Checks Only
R Eliminate Blank Lines from Guest Check
R Print “Closed to” Check Number Double Wide on Memo Guest Check
R Print “REPRINTED CHECK” Header
R Print Open And Closed Time On Guest Check
R Print Previous Balance Each Round
R Service Round Totals Include the Current Round Only
R Print Service Total Time on Checks
R Print “VVV VOID VVV” Line on Checks
R Don’t Center Header Printing

R Tax Options field—This field includes tax options that affect guest
check printing.

R ON = Use Employee number to Transfer a Block of Checks; OFF =
Use ID #
R Print Split Check if Table Number is 0

Guest Check

R Prompt On-demand Operator to Print Split Check
R [Begin Check] key Confirmation Not Required
R [Pickup Check] key Confirmation Not Required
R Zero or Negative Transactions Do Not Add to Guest Count or Guest
Check Count

R Number of Checks Printed Before Authorization field
R Require Finalization of a Check after a Partial Tender
R Allow Changes to Menu Items on Closed Checks
R Allow Service Total of Closed Checks

R Check Sort Type field—Check detail may be sorted by seat, by print
group, or both; and check detail may be consolidated or
unconsolidated.
R Minimum Check Number field
R Maximum Check Number field
2 RVC Information | RVC Descriptor | Headers and Trailers | <Select Header

Training Check>
R Training Header Lines 1, 2, and 3—These descriptors are used to
give guest checks printed in the Training Mode a special header (e.g.,
“TRAINING ONLY - DO NOT PAY THIS CHECK”).
1 Menu Item Class

Output
R Print Name 1 and Name 2 on Checks
R Add Condiment Price to the Parent Item’s Price on Check Only
R Print Main Menu Level Prefix and Suffix
R Print Sub-Menu Level Prefix and Suffix
G-14
Guest Check

General
R Do Not Put in Transaction Detail
1 Tender/Media File

<Select Category Printing Options>
R Print VAT Lines on Check or Receipt


R 500-519 - Add/Trans Checks
R 520 - Block Transfer
R 521 - Auto Block Transfer
R 535 - Split Check
R 423 - Re-open Closed Check
Optional Settings
1 Job Codes
2 Personnel | Job Code | General

R Clock Out With Open Checks

Guest Check
1 Employee Class
2 Personnel | Employee Maintenance | Sort By Class | General Time &

Attendance
R Clock Out with Open Checks
2 Personnel | Employee Maintenance | Sort By Class | Guest Checks | Guest

Check Control
R Create New Checks Using [Begin Check] key
R Authorize/Perform Pickup Check that is “Open On System”
R Authorize/Use the [Split Check] key and Perform Memo Tenders
R Authorize/Perform Pickup Checks Belonging to Another Operator
R Authorize Opening of Multiple Groups at a Table
R Authorize Adding of Checks in Same Revenue Center
R Authorize Adding of Checks Between Revenue Centers
R Authorize Transfer of Checks Between Revenue Centers
R Authorize Transfer of Checks in Same Revenue Center
R Authorize/Use [Block Transfer] and [Auto Block Transfer] keys
R Allow Pickup of Checks in Other Revenue Centers
2 Personnel | Employee Maintenance | Sort By Class | General | Transaction

Sign In
R Change Revenue Centers
2 Personnel | Employee Maintenance | Sort By Class | Transactions | Other

Employee Checks
R Post Menu Items To Checks Belonging To Another Operator
R Post Discounts to Checks Belonging to Another Operator
R Post Service Charges to Checks Belonging to Another Operator
R Post Payments to Checks Belonging to Another Operator
G-16
Guest Check
2 Personnel | Employee Maintenance | Sort By Class | Printing | Check/

Receipt
R Authorize/Perform Unlimited Reprinting/Printing of a Check
R Authorize/Perform Reprinting of a Closed Guest Check
2 Personnel | Employee Maintenance | Sort By Class | Voids & Returns |

Returns
R Authorize/Perform Return of MI Entered on the Current Check
R Authorize/Perform Direct Voids
2 Personnel | Employee Maintenance | Sort By Class | Voids & Returns |

Voids
R Authorize/Use [Void Check] key
R Authorize/Perform Void of Menu Items on Closed Checks
R Authorize/Perform Void of Discounts on Closed Checks
R Authorize/Perform Void of Service Charges on Closed Checks
2 Personnel | Employee Maintenance | Sort By Class | Procedures & Reports

| UWS Procedures
R Use UWS Procedure #1: Change Next Guest Check Number
1 Operators

R Require Check Employee Number With New Checks—This feature
is typically used for cashiers who place take-out orders, banquet
charges, or checks for other employees.
R Use Employee Number to Open Check for Another Employee—
Enable this option to use employee numbers; disable to use ID
numbers.
R Cannot Perform Fast Transactions—This option prevents an
operator from performing Fast Transactions.
R Require Seat Number Entry

Guest Check

R Special, By-round (Same as 4700 Temporary, On-demand)—This
option allows a By-round operator to act as a Special, By-round
operator.
1 PC Autosequences
2 Reporting | PC Autosequences | <Select Autosequence> | Options

R Do Not Run if There are Open Checks in the System
R Search for Open Checks Only in the First Revenue Center Defined in
Autosequence
1 UWS Autosequences
2 Reporting | UWS Autosequences | <Select Autosequence> | Options

R Do Not Run if There are Open Checks in the System
R Do Not Run if Signed-in Employee has Open Checks
R Only Check for Open Checks in Signed-In Employee’s Revenue
Center
G-18
Guest Check Identification
Description
The Guest Check Identification feature allows an operator to enter a descriptor up
to 16 alphanumeric characters. This descriptor is referred to as a Guest Check ID
and can be used in conjunction with a check number, a table number, or both. The
Guest Check ID can also be assigned and accessed using the 9700 System
Interface Module. For more information, please see the 9700 System Interface
Module Manual.
Usage
Use the Guest Check ID feature to attach a label of up to 16 alphanumeric
characters to uniquely identify a guest check. The ID can be added when the guest
check is begun or during a subsequent service round. The Type Definition for
each operator may be programmed to require the entry of a Guest Check ID, or it
can be an option for a guest check. It can be used in conjunction with any table
number or guest check number requirements.
For example, if the operator’s file is programmed to required a Guest Check ID,
the operator may use [Begin Check by Table #] to begin a guest check, and the
System will prompt for a Guest Check ID.
The [Begin Check By ID], [Pickup Check By ID], and [Transfer Check by ID]
function keys are used just as other [Begin], [Pickup] or [Transfer] keys. In each
case, the Guest Check ID is used to reference the check. If necessary, ID
information can be edited while the check is open, or after it is closed, using the
[Guest Check ID] key.
The local country club lounge uses the Guest ID to

identify their club members. After playing a round
of golf, Graham, Richard, Norm, and Adam decide
to have lunch at the bar. As usual, they ask for
separate checks. Since they are members of the
country club and are regulars at the restaurant, the
server knows them by name. The server starts an
individual guest check for each of them, using their
names as the Guest ID.

Guest Check ID Specifications

A Guest Check ID can include up to 16 alphanumeric characters, including
spaces. Leading spaces are eliminated, so a Guest Check ID should not include a
leading space.
A Guest Check ID must be unique among all open guest checks within a revenue
center. A Guest Check ID may be duplicated between the Open Check and the
Closed Check files.
The alphanumeric Guest Check ID is case-sensitive. The entries SAM, sam, and
Sam are unique Guest Check IDs.
Check Operations
Begin Checks
An operator who is privileged to begin checks may use the [Begin Check by
ID] key to begin checks by guest check ID. If the operator begins a check with
another type of [Begin Check] key, and the operator’s type definition is
programmed to require the entry of a Guest Check ID, the System prompts for
the ID.
A Guest Check ID can be used in conjunction with the check number, a table
number, or both.
Pickup Checks
An operator may use the [Pickup Check By ID] key to pickup open checks.
The System may be programmed to provide Pickup Check SLU screens.
Refer to “Pickup Check SLU” in Chapter 5 of the 9700 Feature Overview
Manual.
Transfer Checks
An operator may use the [Trans Check By ID] key to transfer checks from
another operator. The System may be programmed to provide Pickup Check
SLU screens. Refer to “Add/Trans Check SLU” in Chapter 5 of the 9700
Feature Overview Manual.
G-20
Editing a Guest Check ID

A Guest Check ID can be edited by a privileged operator in both the open and
closed check files using the [Guest Check ID] key.
To ensure that Guest Check IDs are unique within a Revenue Center, the System
updates Guest Check ID information in real time. This means that once the [Enter]
key is pressed, the ID becomes a permanent part of the guest check record.
Although the ID can be edited, it cannot be deleted.
The [Trans Cancel] key can be used in conjunction with a guest check that
contains an ID. However, if after the first service round a change is made to an ID,
the [Trans Cancel] key will not cancel any changes made to the ID in that service
round.
Printing Guest Check ID

The Guest Check ID prints with check information on the Guest Check, Customer
Receipt, Order Requisition, System reports, and CP9700. The format may vary,
depending on whether or not a table number is also used for the check.
Guest Check with Check Number

If a Guest Check ID is used with a check number only, the ID appears in the
same line of information as the check number. For example:
MICROS 9700
FINE DINING SYSTEM
411 MARY
--------------------------------
CHK 73 SAMPLE GST CK ID GST 2
JAN14’94 11:36PM
--------------------------------

Guest Check with Table Number and Check Number

If a Guest Check ID is used in conjunction with a table and a check number,
the ID will appear on a separate line. The line of information will appear
immediately after the table and guest check number information. For
example:
MICROS 9700
FINE DINING SYSTEM
411 MARY
--------------------------------
TBL 2/1 CHK 74 GST 2
SAMPLE GST CK ID
JAN14’94 11:36PM
--------------------------------
Order Chit
The Guest Check ID information appears as a separate line of information on
a local or remote order chit. The ID appears immediately after employee
number information. Like the table number, the ID prints double wide. For
example:
RESTAURANT
** HOT PRINTER **
411 MARY
--------------------------------
SAMPLE GST CK ID
CHK 81 GST 2
--------------------------------
G-22
Credit Card Voucher

The Guest Check ID information appears as a separate line of information on
a Credit Card Voucher. If an ID does not exist, the System does not print this
line of information
MICROS
FINE DINING SYSTEM
PH# (301)210-6000
FAX# (301)210-7077
DATE: MAY23’94 01:50PM
CARD TYPE: MASTERCARD
ACCT #: 54123456789632 *
EXP DATE: 12/95
AUTH CODE: DEMO1
CHECK: 86
TABLE: 2/1
GST CHK ID: SAMPLE GST CK ID
SERVER: 1 JANICE
SUBTOTAL: 34.70
TIP_________________________________
TOTAL______________________________
SIGNATURE__________________________
Enabling
1 Operators
2 Personnel | Employee Maintenance | Sort By Operators | <Select

Operator> | Options | Guest Check Options
R Require Guest Check ID



R 435 - Begin Check by ID
R 436 - Pickup Check by ID
R 437 - Transfer Check by ID
R 438 - Guest Check ID
Optional Settings
1 Touchscreen Style
2 Touchscrns & Keyboards | WS Touchscreens | Touchscreen Style | Style

Options
R Show Tbl/Grp in Open Check SLU
R Show Check # in Open Check SLU
R Show Other Employee’s Name in Open Check SLU
R Show Open Time in Open Check SLU
R Show Amount Due in Open Check SLU
R Display Keys Vertically Starting at Top Left
R Display Keys Horizontally Starting at Top Left
1 Employee Class

Guest Checks | Editing Checks
R Authorize/Perform Edit of a Guest Check ID in an Open Check
R Authorize/Perform Edit of a Guest Check ID in a Closed Check
G-24
Related Topics
w “Edit Detail” on page E-1
w “Guest Check Information Detail Lines” on page G-26
w “Key Icons” in Chapter 5 of the 9700 Feature Overview Manual
w “System Interface Module” on page S-50

Guest Check Information Detail Lines
Description
The Guest Check Information Detail Lines feature uses the System Interface
Module (SIM) to create reference information that can then be included in a guest
check’s detail.
Up to 30 detail lines of 32 characters each may be added to the guest check detail.
These lines may be programmed to print on the guest check, customer receipt, and
on specific order devices. Guest Check Information Detail Lines are not included
in journal entries.
Once added to a check, guest check information detail lines cannot be voided or
edited.
Usage
SIM uses the Interface Script Language (ISL) to capture information from a third-
party software package (such as a database of guest information) and store it in the
guest check detail. SIM can also be set up to allow the operator to enter Guest
Check Information Detail at the UWS.
Check information detail lines are often used to store customer information, such
as names and addresses, or to add special handling instructions to a guest check.
G-26
A customer calls Personal Pizza and says, “This is

Joe Decker. Give me my usual order, please.” The
operator replies, “Good evening, Mr. Decker” and
consults the third-party customer database. Based
on the information found there, the operator
continues, “Are you still located at 123 Main
Street? You usually order a large pizza with
everything. Is that what you’d like tonight? We’re
very sorry that our last delivery arrived in 35
minutes instead of our target 30 minutes. We’ll take
steps to avoid that happening tonight.”
The operator then posts an order for a large pizza

with everything at the UWS. The operator then
presses a key on the UWS that initiates an ISL
script. The ISL script retrieves the following
information from the customer database, and enters
it as Guest Check Information Detail Lines.
DELIVER TO:
MR. JOE DECKER
123 MAIN ST.
THIRD HOUSE ON LEFT

WHITE HOUSE/BLUE SHUTTERS
NO HOUSE NUMBER
PERSONAL CHECK IS OK
The operator then presses another ISL key that

enables direct input from the UWS, and types two
additional Guest Check Information Detail Lines:
LATE LAST TIME - PRIORITY 1 ! ! !

WATCH OUT FOR THE DOG!

Enabling

R Number of Guest Check Information Lines (0 - 30, Default 0)
Optional Settings
1 System Parameters

R Max. Number Check Detail Entries field—Make sure this field is set
to a level that will accommodate the expected number of Guest Check
Information Detail Lines, in addition to expected transaction
information lines.

R Skip Blank Lines When Print or Display Guest Check Info Lines
R Do Not Display Guest Check Info Lines on User Workstation
R Print Guest Check Info Lines Before Header on Guest Checks
R Print Guest Check Info Lines After Header on Guest Checks
R Print Guest Check Info Lines After Trailer on Guest Checks
1 Order Devices

R Print Guest Check Info Lines Before Header on Order Output
R Print Guest Check Info Lines After Header on Order Output
R Print Guest Check Info Lines After Trailer on Order Output
G-28
Related Topics
w “Edit Detail” on page E-1
w “Guest Check Identification” on page G-19
w “System Interface Module” on page S-50
For additional information about the System Interface Module, refer to the 9700
System Interface Module Manual.

Guest Count
Guest Count
Description
The 9700 System can keep track of the number of guests being served in each
transaction. This information may be used in reports.
Usage
The number of guests being served in a transaction can be counted in any of
several ways:
w Seat Count—The number of seats entered for the guest check can be used as
the guest count. If this method of guest counting is used, the Manual Entry
method of adding to the guest count is disabled. Also, the Number of Guests
Entry Required for New Checks Option is disabled.
w Service Charge—A service charge can be programmed to add to the guest

count each time it is posted manually. A service charge can also be
programmed with the Auto Cover Charge feature by using the Number of
Guests Entry Required for New Checks Option and the cover charge link in
the Revenue Center Parameters file. Programming the service charge can be
useful in a nightclub environment that uses a cover charge for each guest.
w Menu Item—The members of a Menu Item Class can be programmed to add

to the guest count each time they are ordered. For example, some restaurants
only consider the sale of an entree as a guest count. If this method of guest
counting is used, the Manual Entry method of adding to the guest count can
override the Menu Item guest count.
w Manual Entry—The operator can enter the number of guests for a

transaction using the [Number of Guests] key.
G-30
Guest Count
Reports
Financial Reports
(System, Revenue Center, Employee, Time Period, Serving Period)
An Order Type Profile section may be programmed to print on these reports. This
section includes the following totals for each Order Type that is programmed as
“active” in the System Parameters File or the Revenue Center Parameters File:
w Number of Guests—This total records the total number of guests recorded
for this Order Type.
w Sales/Guest—This total equals the total net sales recorded for this Order
Type, divided by the total number of guests recorded for this Order Type.
Table Sales Report

w Guest Count—This total is recorded for each table.
Employee Open Check Report and Employee Closed

Check Report
Number of Guests—This total records the number of guests recorded for each
guest check.
When Revenue Center Posting Option Zero or

Negative Trans Do Not Add To Guest or Check is
enabled, cover and guest check count totals are not
updated unless the balance due is a positive value
that is greater than zero.

Guest Count
Enabling


R 523 - Number of Guests
1 System Parameters

R Do Not Print The Order Type Breakdown On Financial Reports
1 Interface
2 System Hardware | Interface | General | Options

R Force the Number of Guests to Zero When Creating a TMS
Check—Enable this option to allow the guest count to be set by some
means other than the TMS (operator entry, seat count, etc.)
Optional Settings

R Number of Seats May Not Exceed Number of Guests
R Cover Charge field—In this field specify the service charge to be used;
it should be a preset $ type.

R Do Not Prompt for Guests when Prorating PMS Itemizers
G-32
Guest Count

R Zero or Negative Transactions Do Not Add to Guest or Guest Check
Count
1 Service Charges

R Service Charge Adds to Guest Count
1 Menu Item Class
R Add to Guest Count
1 Interfaces

R Use 5 Digits for Number of Guests
1 Employee Class

R Authorize/Perform Change of Number of Guests
1 Operators

R Number Of Guests Entry Required for New Checks
Related Topics
w “Table Management System” on page T-1

Guest Count
G-34
H
Hand-held Touchscreen
Description
The Hand-held Touchscreen terminal (HHT) is a portable, wireless User
Workstation that communicates with the 9700 System by radio.
For more information, refer to “Hand-held touchscreen” in Chapter 12 of the 9700
Feature Overview Manual.
9700 HMS A to Z Feature Reference Manual H-1

Help Screens
Help Screens
Description
A Help Screen is a “window” temporarily displayed on the current User
Workstation display to show information to the operator.
Usage
Help screens are generated automatically by the system when one of the following
occurs:
w An NLU or function FLU key is pressed with no numeric entry preceding it.
w A key is pressed for a menu item that requires a prep instruction or condiment.
w An employee clocks in to the system, and has more than one Job Code from
which to choose.
Help Screens may also be generated from a programmable Help Screen File when
the [Help] key is pressed.
Example
Beers are ordered using a single NLU key, and George has forgotten the NLU
number for draft. He presses [Beer NLU], and the help screen shown below pops
up in a window, displaying NLU numbers and brand names.
1 Colorado Light
2 Australian Lager
3 Holland’s Beer
4 Frisco Steam
10 Domestic Draft
11 Import Draft
H-2
Help Screens
George enters [1] [0] to place an order for domestic draft.

George presses the [Hamburger] menu item key. Hamburgers are programmed in
this system to require a prep instruction, so the help screen shown below appears
in the display:
1 RARE
2 MEDIUM RARE
3 MEDIUM
4 MEDIUM WELL
5 WELL DONE
George enters [4] to order the hamburger cooked medium well.

The customer intends to pay the bill with one of the restaurant’s gift certificates.
There are special instructions on handling gift certificates, but George has
forgotten them, too. Returning to the User Workstation, George presses the [Help]
key. The first help screen has been programmed as an index, as shown below.
HELP SCREEN TOPICS

1 Serving Wine
2 Seating Large Parties
3 Personal Check Policy
4 Gift Certificates
5 Employee Meal Policy
6 Birthday Cake Orders
George enters [4] to display the help screen programmed with notes on the
restaurant’s gift certificates.
Field Help
Some of the User Workstation Procedures include fields that require entries drawn
from the 9700 database. For example, when using Procedure # 3, Employee
Setup, you are required to link the employee to a specific Employee Class.
The [Field Help] key can be used to avoid the necessity of maintaining printed
lists of Employee Class numbers, or of having to start the System Configurator
module and open the Employee Class File.

Help Screens
Press the [Field Help] key when editing a field that requires an entry from a
database file. The System superimposes a pop-up window on the User
Workstation display. The window lists the names and object numbers of the
records in the file.1 These fields may not be edited, and no other fields from the
file are displayed.
Procedures 9700 Ops 2.00 Johnson Restaurant

Employee Setup LOCATE FIELD AND ENTER CHANGE
101 Joe Smith
Last Name: Smith ID Number: 747

First Name: Joe
Check Name: Joe S. Info Line 1: 123 Common Lane
Class: Waiter10Info
10 Waiter
10 Waiter
Line 2: Any Where
Group: 0 20Info
Bus Line 3: Small Town, USA
Level: 0
Clk In Grace 10 30Info Line 4: (123)456-7890
Bartender
Payroll ID
40 Cook
Rate Job Code50 Manager
Regular Pay Overtime Pay
1 2 Waiter 2.01 3.20
2 3 Host 6.00 9.00
3 0 Not In File 0.00 0.00
4 0 Not In File 0.00 0.00
5 0 Not In File 0.00 0.00
6 0 Not In File 0.00 0.00
7 0 Not In File 0.00 0.00
8 0 Not In File 0.00 0.00
To close the pop-up window, enter one of the numbers displayed and press
[Enter], or press [Clear].
Due to the size of Menu Item files, Menu Item fields do not offer the [Field Help]
feature.
1. When the [Field Help] key is used in conjunction with an employee name field, the System will display an
alphabetized list of names. This will allow you to distinguish employees with the same last name from
one another.
H-4
Help Screens
Enabling

Type=Tender/Media | Number

Keyboard> | Key Configuration | Type=Tender/Media | Link
R [Menu Item NLU] - keycodes #101 - #132 - 32 per Revenue Center

R [Discount NLU] - keycode #200 - 1 per System
R [Service Charge NLU] - keycode #201 - 1 per System
R [Tender/Media NLU] - keycode #202 - 1 per System
R [Field Help] - keycode #303
R [Help] - keycode #301
R [Help, Prompt for Number] - keycode #302 (designed for use with
FLUs)
1 System Parameters

R Default Transaction Help Screen field
R Default UWS Procedures Help Screen field
R Default UWS Autosequence Help Screen field

R NLU, Condiment Help Screen Sort Type field

Help Screens
2 RVC Information | RVC Descriptors | Group Names | <Select Group

Name>
R Main Menu Level Names field
R Sub-Menu Level Names field
R Condiment Group Name fields
R Menu Item NLU Names field
1 Help Screens
2 System Information | Help Screens | General

R Help Screens 1 through 99 may each be programmed with 12 lines of
up to 70 characters.
1 Menu Item Class
2 Menu Items | Menu Item Maintenance | Sort By Menu Item Class |<Select
Class> | Condiment Groups | Menu Item Type
R Regular or Condiment—Select Condiment o designate this menu item
as a condiment.
R Required Condiment Groups field
R Allowed Condiment Groups field
R Member of Condiment Groups field
1 Menu Item Definition
2 Menu Items | Menu Item Maintenance | Sort By Menu Item | General

R NLU Group field
R NLU Number field
1 Discounts
2 System Information | Discounts | NLU/SLU

R NLU field
H-6
Help Screens
1 Service Charges
2 System Information | Service Charge | NLU/SLU

R NLU field
1 Tender Media
2 System Information | Tender Media | NLU/SLU

R NLU field
1 Operator File
2 Personnel | Employee Maintenance | Sort By Operator | Options | NLU

R Display Menu Item NLU Number
R NLU List is Stay-down
R Display Condiment Help—Enable this option to display the
condiment help window when a menu item requiring condiments is
ordered.
Related Topics
w “Condiment Handling” on page C-27

Hexadecimal Entry
Hexadecimal Entry
Description
Hexadecimal entry is a method of programming certain fields, such as type
definitions, options, etc., that requires converting binary numerals into
hexadecimal numerals for entry.
Each option or type definition represents a binary value. An option is either
enabled or disabled.
A string of four options is entered into a data field as a single hexadecimal digit.
In the 9700 database, fields of this type may use up to 20 hexadecimal digits, each
representing four options.
Usage
The 9700 System Configurator is designed as a user-friendly interface that does
not require its operators to use hexadecimal entry. Option fields (or type
definitions, etc.) may be programmed in Symbolic Mode by clicking the field’s
Zoom Box and using the mouse to set each option ON or OFF.
However, System Configurator retains hexadecimal entry as an alternative for
entering fields, because many experienced programmers and installers are familiar
with this method, and prefer it for its speed. If the same setting for a field is to be
used in multiple records in a file, the hexadecimal entry can be copied, and then
pasted to as many records as necessary, using the mouse.
Hexadecimal Digits
Hexadecimal notation uses a base 16 numbering system. There are 16
hexadecimal digits: 0 to 9 followed by A to F. The corresponding decimal value
of the hexadecimal digits is shown below.
Hexadecimal 0 1 2 3 4 5 6 7 8 9 A B C D E F
Decimal 0 1 2 3 4 5 6 7 8 9 1 1 1 1 1 1
0 1 2 3 4 5
As the table shows, a hexadecimal digit can represent any decimal value between
0 and 15.
H-8
Hexadecimal Entry
A hexadecimal digit represents the total value of a string of four binary digits. A
binary digit can have values of 0 or 1 only. A single hexadecimal digit represents
a unique string of four binary digits, as the following comparisons show.
Decimal 1111 = “one thousand, one hundred eleven” because:

= “one”
= “ten”
= “one hundred”
= “one thousand”
We are accustomed to recognizing that the actual value of the digit “1” is based on
its position. In binary notation, where the only digits are 1 and 0, the same rule is
true, as the following illustrates:
Binary 1111 = decimal “15” = hexadecimal “F” because:

= “1”
= “2”
= “4”
= “8”
15
Thus, every value between 0 and 15 is a unique combination of one or more of the
numbers: 8, 4, 2, and 1.
Calculate a Hexadecimal
The preceding section showed that a hexadecimal (or hex) digit is a string of four
options. Each option has a value based on its position in the string. From top to
bottom, the values are 8, 4, 2, and 1. Since a binary digit can only be 0 or 1, an
option’s value is always 8 or 0, 4 or 0, 2 or 0, and 1 or 0. Thus, the value of a
position adds to the hexadecimal digit value only if the bit in that position is ON,
that is, equal to 1. The resulting hexadecimal digit value shows which options are
ON.
A byte is a string of eight binary digits represented by two hexadecimal digits.
The first digit represents the value of the first four options and the second digit
represents the value of the last four options. Hexadecimal fields always contain an
even number of hexadecimal digits.

Hexadecimal Entry
Example
Determine the hexadecimal digit value of a two-digit field with options 2, 4,
5, and 7 set ON.
Option Binary Hex Value of

Setting Value Value this byte
OFF = 0 x 8 = 0
ON = 1 x 4 = 4
5
OFF = 0 x 2 = 0
ON = 1 x 1 = 1
ON = 1 x 8 = 8
OFF = 0 x 4 = 0
A
ON = 1 x 2 = 2
OFF = 0 x 1 = 0
Answer: 5A
Thus, the hexadecimal entry for a field with this mix of option settings is
“5A”. If this same setting is to be used for multiple records in the file, this hex
entry can be copied, and then pasted to as many records as necessary, using
the mouse.
Employee File
w Default to Symbolic Mode when Editing Hexadecimal Fields - Type
Definition #6
H-10
High Amount Lockout (HALO)
Description
High Amount Lockout (HALO) is a programmable limit on the dollar amount of
menu items or tenders that may be entered by the operator. A HALO is used to
filter out erroneously high entries.
Usage
When a tender/media HALO is active, dollar amount entries are compared to the
HALO amount. The HALO may be programmed to limit either the tender amount
entered or on the amount overtendered.
Authority to override a Tender/Media HALO may be restricted to certain
employees.
When a menu item HALO is active, the quantity of the item ordered times the
item price is compared to the HALO amount. For example, if a menu item is
priced at $3.00, and the HALO for this menu item class is set at $30.00, then
ordering 11 of these menu items would exceed the HALO amount
(11 x $3.00 > $30.00).
If the HALO is exceeded in an entry, the user workstation prompts “AMOUNT
TOO LARGE- CONTINUE?”. The operator may then change the entry or may
continue with the large amount.

Enabling
1 Menu Item Class
R HALO field—This is a two-digit numeric field that determines the size
of the HALO. The first digit is a number between 0 and 9. The second
digit is a tens multiplier from 0 through 7. Example: 21 = 20.00, 22 =
200.00, 27 = 20,000,000.00.
1 Tender/Media
2 System Information | Tender Media | Key=Type Payment | Key Type |

HALO Options
R Enable HALO—Enable this option to require authorization to exceed
the HALO.
R Compute HALO On: Amount Entered or Amount Overtendered
Optional Settings
1 Employee Class

R Authorize Over HALO Amounts on [Tender/Media] keys
H-12
Hold & Fire
Hold & Fire
Description
The Hold & Fire feature allows a server to service total a guest check and hold
the order until the server is ready to “fire” it (i.e., send it) to order devices.
Usage
Hold & Fire Entire Service Round

In order to use this feature, a server places an order and presses the [Service Total]
key that is programmed to hold all Menu Items in the current service round. This
service totals the guest check, but the menu items are not output to order printers.
When the server is ready for the kitchen to begin preparing the selected items, the
server picks up the check and presses a separate [Service Total] key that is
programmed to fire orders. Any menu items that have not already been output to
order devices are then “fired” to those devices.
Example
Table 27 has given Samantha an order for their drinks, appetizers, and entrees,
all at the same time. Samantha goes to the User Workstation and places the
order for the drinks and appetizers, then service totals the check.
Samantha picks up the check, places the order for the entrees, and this time
she presses the [Service Total/Hold] key, which service totals the check. The
entire order is now posted to the check, but the entrees are not sent to the
remote printers.
Samantha serves the drinks and appetizers. Halfway through the appetizer
course, Samantha picks up the check and presses the [Service Total/Fire] key,
which service totals the check again. The orders for the entrees are now
dispatched to the remote printers in the kitchen.

Hold & Fire
Hold Individual Menu Items

There are several methods by which to Hold & Fire individual menu items.
Line Item Hold

A line item hold is performed by entering the line number of the menu item
you wish to hold and pressing the [Hold Menu Item] key. An “H” appears
next to the specified menu item on the operator display. Press the [Service
Total/Hold] key. This service totals the guest check, but the menu items
designated as hold items are not output to order printers.
Last Item Hold

A last item hold is performed by posting a menu item and pressing the [Hold
Menu Item] key twice. An “H” appears next to the specified menu item on the
operator display. Press the [Service Total/Hold] key. This service totals the
guest check, but the menu items designated as hold items are not output to
order printers.
Direct Hold
A direct hold is performed by pressing the [Hold Menu Item] key and then
posting the Menu Item. The menu item will appear on the operator display
along with an “H” to specify that the item is on hold. Press the [Service Total/
Hold] key. This service totals the guest check, but the menu items designated
as hold items are not output to order printers.
Fire Individual Menu Items

When the server is ready for the kitchen to begin preparing the selected items, the
server picks up the check and presses a separate [Service Total] key that is
programmed to fire orders. Any menu items that have not already been output to
order devices are then “fired” to those devices.
For your consideration—Using the Memo Print function while menu items are
being held will cause the items to be fired.
H-14
Hold & Fire
Enabling


R [Service Total] key - programmed to Hold orders

R [Service Total] key - programmed to Fire orders
R [Hold Menu Item] key - keycode #647
1 Tender Media

R Key Type field—Select Service Total.

Ops Behaviors
R Preserve Hold Status from Previous Menu Items
R Hold All Menu Items in Current Round
Related Topics
w “Chain & Fire” on page C-16

Hold & Fire
H-16
I
Itemizers
Description
When items are entered on a guest check, various subtotals known as Itemizers
are maintained in the background. As an analogy, an Itemizer is a “bucket” where
totals accumulate. For example, all food items could be subtotaled in one itemizer,
and all liquor items in another. Various calculations such as subtotal discounts,
subtotal service charges, and sales tax can be set to apply to all or only certain
itemizers. This provides a way to selectively apply each calculation.
Usage
Sales Itemizers
These 16 itemizers are used for the purpose of separating menu item sales into
categories, such as Food, Beverage, and Merchandise. Optionally, Sales Itemizers
may appear on a guest check as separate subtotals.
Discount Itemizers
Every Menu Item Class may be programmed to post to one of sixteen Discount
Itemizers. A percentage Discount key may be programmed to compute a Discount
on any mix of Discount Itemizers. For example, a discount coupon for 10% off of
the cost of a meal may apply only to food sales (not liquor). In this example, you
would assign food items to one discount itemizer and liquor items to another.
9700 HMS A to Z Feature Reference Manual I-1

Itemizers
Service Charge Itemizers

Every Menu Item Class may be programmed to post to one of eight Service
Charge Itemizers. A percentage Service Charge key may be programmed to
compute a Service Charge on any mix of Service Charge Itemizers. For example,
you may wish to have food items post to the first service charge itemizer, liquor to
post to the second, and so on. This way a service charge can be used to apply only
to food and not to liquor.
Itemizer Descriptors
Descriptors for Discount, Service Charge, and Sales Itemizers may be
programmed in various files in the 9700. (See “Enabling” on the next page.)
These descriptors appear for reference when programming other files.
Consider, for example, a restaurant in which Discount Itemizer #4 is programmed
with the descriptor “Seniors.” When the programmer is setting up the Menu Item
Class File, classes must be linked to various Discount Itemizers. The programmer
does not need to remember (or write notes to remind himself) that Discount
Itemizer #4 is “Seniors.” When programming the Discount Itemizers for each
class, the descriptors appear in pop-up windows. The programmer can see, while
in the Menu Item Class File, that Discount Itemizer #4 is “Seniors.”
Sales Itemizers, in addition to providing an aid to programming, may also be
programmed to print on Guest Checks and Customer Receipts beside the sales
total for each itemizer.
Prorating Itemizers for Partial PMS Posting

Some PMS products record sales postings by Itemizers. To meet the needs of
these types of systems, the 9700’s Revenue Centers may prorate Itemizer posting
when a partial tender is made to a PMS. If this is the case, the percentage of all
itemizers posted to the PMS is equal to the percentage of the tender.
Example
The amount due for a guest check in the hotel restaurant totals $10.00. The
customer elects to charge $7.00 to his room account, and to pay $3.00 in cash.
The operator posts a $7.00 charge to the account in the PMS, and tenders the
balance to cash. In this example, 70% of the total of all itemizers accumulated
for this transaction (i.e., menu item, discount, and service charge itemizers) is
posted to the PMS.
If prorated itemizer posting is not used, all itemizers are included in each
posting.
I-2
Itemizers
Enabling
2 System Information | System Descriptors | Category=Discount Itemizers

R Discount Itemizer Name fields—Enter the sixteen Discount Itemizer
descriptor names. Example: Coupon, Employees, Seniors, etc.
2 System Information | System Descriptors | Category=Service Charge

Itemizers
R Service Charge Itemizer Name fields—Enter the eight Service
Charge Itemizer descriptor names. Example: Charged Tips, Cover
Charge, Delivery, etc.
2 RVC Information | RVC Descriptors | Group Names | <Select Group Name

Sales Itemizer Names>
R Sales Itemizer Names fields—Enter the Sales Itemizer descriptor
names. Example: Food, Liquor, Merchandise, etc.
1 Menu Item Class
R Sales Itemizer field
R Discount Itemizer field
R Service Charge Itemizer field
1 Discounts
2 System Information | Discounts | Itemizers

R Compute on Discountable Itemizers 1 through 15—For each
Itemizer to which this Discount will apply, enable the appropriate
selections.

R Reset Itemizers

Itemizers
1 Service Charges
2 System Information | Service Charges| Itemizers | Options

R Compute on Discountable Service Charge Itemizers 1 through 8 -
Itemizers 1 through 8—For each Itemizer to which a percentage
Service Charge will apply, set the appropriate selections ON. Also,
specify the Tax Class on which this Service Charge will compute.

R Reset Itemizers
Optional Settings

R Prorate Itemizers When Posting a Partial Tender to a PMS

1 Tender/Media

Category=Printing Options | Printing Options

Category=PMS Options
R Reverse PMS Itemizers on Void Postings
Related Topics
w “Descriptors” on page D-13
w “Post Sales” on page P-24
I-4
Interface File
Interface File
Description
The Interface File is used to define communication between the 9700 system and
a number of peripheral systems.
Usage
The 9700 System is designed to communicate with up to eight peripheral systems
per Revenue Center, and up to 255 per System. These peripheral systems may
include:
w Property Management Systems (PMS)
w Table Management Systems (TMS)
w Credit Authorization/Electronic Draft Capture (CA/EDC)
More than one Revenue Center may access the same peripheral. Communication
may be established using either of two methods:
w A TCP interface may be set up to communicate through the System’s LAN.
w An Asynchronous Serial Interface (also referred to as a TTY interface) may

be set up to communicate through the COM port on the PC.
The 9700 System’s communication parameters are designed to be flexible enough

to allow communication with a wide variety of third-party PMS programs. Refer
to the PMS to POS System Interface Communications Programming and
Operations Manual.

Interface File
Enabling
1 Interface

R Complete all fields in this file.
2 RVC Information | RVC Parameters | Interfaces | PMS Links

R PMS Link field—Enter the names of each PMS.
Related Topics
w “Backup PC” on page B-1
I-6
Interface Script Language
Description
The Interface Script Language (ISL) is used by the System Interface Module
(SIM) to interface with a variety of other data systems, including sophisticated
Property Management Systems (PMS), automated delivery systems, and other
electronic database systems.
For a complete description of ISL and of SIM, refer to the 9700 System Interface
Module Manual, P/N 100068-084.

I-8
J
Job Codes
Description
A Job Code is an accounting entity that enables a system to track the labor
activity of a group of employees by category of work. Job codes are used for two
purposes. First, they link hourly employees to a specific wage rate when they
clock in, and second, for management analysis, they group labor hours and costs
into job categories on reports.
Usage
Linked to Employees
Typically employees are grouped by job-related categories such as Waiter,
Bartenders, Managers, Cooks, Dish Washers, etc. An employee may be linked to
eight different Job Codes.
When an employee clocks in for a shift, their hours worked and wages earned are
added to the totals for one of the Job Codes to which they are linked. The Job
Code to which the employee’s totals are reported is determined in one of three
ways:
w The Job Code field in the Time Clock Schedule may be programmed to
automatically clock the employee in at a specific Job Code.
9700 HMS A to Z Feature Reference Manual J-1

Job Codes
w The Report Group field in the Time Clock Schedule may be programmed to
prompt the employee to select a Job Code from among those included in a
specific Report Group.
w The Job Code field and the Report Group field in the Time Clock Schedule
may both be blank. If this is the case, the employee is prompted to select a Job
Code from among those listed in the employee’s record in the Employee File.
Each Job Code may be programmed to prompt an operator to declare tips, to

prevent an operator from clocking out with open checks, and to use the scheduled
time in labor calculations if an employee clocks in early.
Labor Analysis
Job Codes can be used to group labor hours and costs into job categories on
reports. This information can be useful in analyzing scheduling, staffing, and
labor costs. For example, you may discover that you have scheduled too many
chefs, or that you could afford to hire more waiters. You could even use the
information on this report to establish a hiring ceiling for specific departments.
Reports
Job Code Report - User Workstation Report

The User Workstation version of this report includes the following information:
w Regular hours worked and regular pay earned
w Overtime hours worked and overtime pay earned
w Total hours worked and total pay earned
w Subtotals for up to 255 report groups
In addition, this report lists, for each Job Code, the percentage of labor cost (total
pay) to Net Sales generated by all employees in that Job Code.
Job Code Labor Report - Report Writer Version

The Report Writer version of this report includes all of the information listed
above. In addition, this report displays labor vs. sales information.
J-2
Job Codes
Enabling
1 Job Code
R Define a Job Code for each labor category in each Revenue Center.
Assign each Job Code to a Report Group, both for reporting purposes
and for use in a Time Clock Scheduling option (see below).
R Assign each Job Code to a specific Revenue Center, or select 0-All in
this field to make a Job Code available in all Revenue Centers.
1 Employees
2 Personnel | Employee Maintenance | <Sort By Employee> | <Select
Employee> | Job Codes/Pay Rates
R Job Code fields—Assign up to eight Job Codes for each employee.
1 Time Clock Schedule

2 Personnel | Schedules | General
Use either the Job Code field or the Report Group field.
R Job Code Number field—Assign a specific Job Code for each
employee shift.
R JC Report Group field—Assign a Report Group number to which
several Job Codes are linked in the Job Code File.
Related Topics
9700 HMS A to Z Feature Reference Manual J-3

Job Rates
Job Rates
Description
A Job Rate is a wage associated with a specific Job Code in the Employee File.
Since it is programmed by employee, employees can have different wage rates
associated with the same Job Code.
Usage
George and Samantha are both bartenders. They are both linked, in their
respective Employee File entries, to a Job Code called Bartender. However,
George is new to the job and somewhat unpolished. Samantha has been working
the bar for six years and is a consummate professional.
In Samantha’s Employee File record, her Job Rate is set at $10.00 per hour;
George’s is set at $6.75.Accordingly, when Samantha clocks in as a bartender, she
is paid $10.00 per hour. When George clocks in as a bartender, he is paid $6.75.
George is watching Samantha like a hawk, trying to acquire some of the polish
and aplomb she exhibits.
Enabling
1 Employee File
2 Personnel | Employee Maintenance | <Sort By Employee> | <Select
Employee> | Table View
R Regular and Overtime fields—These fields display in Table view of

the file. Enter the wage rate and overtime rate for each Job Code
assigned to the employee.
Related Topics
w “Job Rates” on page J-4
J-4
K
Keyboards-User Workstation
Description
A Keyboard on a User Workstation includes a set of on-screen keys that are used
to enter information. The type and location of keys included are user definable.
The flexibility of the 9700 System allows you to tailor a set of keyboards to the
needs of an establishment. Establishments may define as many keyboards as they
need for different functions (order entry, cashiering, etc.) and different revenue
centers.
For each keyboard, determine the functions needed and map them out on the
keyboard. For example, direct access menu items are generally grouped together
on the keyboard so that all appetizers are located in the same area. A numeric
keypad is included to facilitate numeric entry and is laid out like a calculator
keypad.
There are twelve categories of keys, each is identified here:
w Menu Items w Tender/Media

w Menu Item FLUs w Tender/Media FLUs
w Discounts w Keypad
w Discount FLUs w FLUs
w Service Charges w Function
w Service Charge FLU w Macros
9700 HMS A to Z Feature Reference Manual K-1

Definitions
Keyboard Layouts
A keyboard layout is the format of the keys. A PCWS uses the 100-key
programmable layout shown below.
K-2
Usage
Direct Access Keys vs. Lookup Keys

There are two types of keys on the keyboard—direct access and lookup.
Direct Access Keys

A direct access key posts an item without any intermediate steps, except
possibly a confirmation. For example, a [Shrimp Cocktail] key posts a shrimp
cocktail.
Lookup Keys
A lookup key lists a set of items on the operator display and allows the
operator to choose one. It optimizes keyboard space by linking multiple menu
items or functions to a single key. For example, one set of menu items might
be linked to an appetizer lookup. When an operator presses the appetizer
lookup, a help window displays a numbered list of appetizers:
1 Shrimp Cocktail
2 Chicken Wings
3 Egg Rolls
4 Stuffed Mushrooms
The operator enters a number to select an appetizer.

An experienced operator (i.e., one who knows the lookup numbers) may
simply enter the number and press the lookup key. If this shortcut is used, the
help window does not display.
Lookup keys include Number Lookups (NLUs) and Function Lookups
(FLUs).
w Number Lookup (NLU) Keys - NLU keys are used for menu items,
discounts, service charges and tender/media.
w Function Lookup (FLU) Keys - FLUs include function FLUs and Sales
FLUs.
A S c re e n L o o k u p ( S L U ) i s o n l y u s e d f o r
touchscreens.

Standard vs. Extended Character Sets

There are two different Keyboard Types available for keyboards—Standard or
Extended.
w The Standard Keyboard Type is limited to using ASCII characters in the range
of 20H to 5FH.
w The Extended Keyboard Type allows ASCII characters in the range 20H to
FFH to be entered on the keyboard. This allows the 9700 to make use of
lower-case letters, as well as characters and punctuation used in some
languages (e.g., the umlaut).
ASCII characters 19H and below are reserved for use as printer control characters,
and should not be used in keyboard entry. For example, one IBM character set
font uses character 15H as the section (§) character. This character cannot be used
in the 9700 System.
Shifted, Unshifted, and Alpha Keyboards

Each key location has three possible states: unshifted, shifted, or alpha.
w Unshifted and shifted keys work just like those on a computer or typewriter
keyboard. Shifted and unshifted keys save key space, because two different
features can be accessed through the same key. For example, two functions,
such as [Begin Check] and [Split Check], may be programmed into the same
key. To access the Split Check function, press [Shift] and the [Begin Check]
key.
w The alphanumeric keys make it possible to enter text when a reference

number is required or when performing manager procedures that require
modification of descriptor fields. The alphanumeric keys provide a way to
assign letters, symbols, and numbers to keys on the keyboard. For certain
operations, these keys automatically become active when needed. For
example, if an operator presses a [Discount] key, the UWS may prompt for a
reference entry. The alphanumeric keyboard becomes active until the operator
types a character string (e.g., “Chronicle Coupon”) and presses [Enter].
K-4
Enabling
Keyboard File
For each keyboard, fill all fields in the Overhead tab of the file. Each keyboard
record on the Overhead tab of the file is linked to a Configuration tab, which
defines all of the keys available on each keyboard. The Configuration tab is
comprised of three basic areas: Keys, Entry Fields, and Keyboard Legend. Each
of these areas is described in the pages that follow.
Keys
Entry fields
Keyboard Legend Generation

Keys
In order to program a specific key, do the following:
w Click that key with the mouse.
w Assign specific functions to that key in the entry fields.
Entry Fields
For each key on the keyboard, do the following:

w If this is a Menu Item key, select a preset main menu level and sub-menu level
that are to become active for the duration of this keystroke.
w Select a key type and a specific key for the Unshifted function.
w Select a key type and a specific key for the Shifted function.
w Assign an alphanumeric value.
K-6
Key Identifiers
When programming is completed for a key, a letter appears in the center of the
key on the display. This is the Key Identifier, an abbreviation of the Unshifted key
category. Its purpose is to let you know, at a glance, which keys on the keyboard
have been programmed. For example, if a menu item was programmed as the
Unshifted function, the letter “m” appears in the center of the key. A list of Key
Identifiers is shown in the table below:
Category Key Identifiers
1 - Menu Item m
2 - Menu Item FLU M
3 - Discount d
4 - Discount FLU D
5 - Service Charge s
6 - Service Charge FLU S
7 - Tender/Media t
8 - Tender/Media FLU T
9 - Keypad 0 through 9, sh, cl, en
10 - FLU F
11 - Function f, or, an abbreviation for the specific
function, e.g., $ for Currency, vd for
void, etc.
12 - Macro ma
Example
This key has been
programmed as a Discount
key. The other 5 keys shown
are not programmed for an
unshifted function.

Key Identifiers Display Option

The Key Identifiers may be changed to display the Unshifted, Shifted, or
Alphanumeric key functions.
w Use the Display field on the Key Configuration tab to select which of three
sets of abbreviations (Unshifted, Shifted, or Alphanumeric) appear in this
display for programmed keys.
Moving a Key
You can easily move keys around to rearrange a keyboard to the desired
configuration. To relocate a key assignment using the mouse, do the following:
w Click the key to be moved and hold the left mouse button down.
w Drag the key to the desired location.
w Release the left mouse button.
The key programming from the first key location (including any keyboard legend)
is erased, and is relocated to the new key location (except for the alpha
assignment). Any key programming that was already located there is overwritten.
Click Drag Place

and (box and
Hold appears) Release
A key movement can be reversed by clicking the Undo selection in the Edit menu.
If you click Undo, the last edit made to the file (including key movements) is
undone.
K-8
Optional Settings
1 Workstations

Definition
R Enable Error Beeper
R Keyboard #2 Installed
1 Keyboards

R Type field
R Default MLvl and Default SLvl fields—These fields determine the
menu levels that become active when this keyboard is selected.
2 Touchscrns & Keyboards | Keyboards | Keyboard Configuration |

Type=Function | Function Key Categories=Keyboard Select
R 816-KB1 Select, NLU
R 817-KB2 Select, NLU
1 Employee Class

Options | Miscellaneous
R Authorize/Use [Keyboard Select] Key—Enable this option to give an
employee the privilege to change keyboards.

R No Confirmation Required When Changing Keyboards Using the
[Keyboard Select] keys—Enable this option to allow privileged
employees to select keyboards without receiving a confirmation
prompt.

Related Topics
w “Macros” on page M-1
w “Preset Menu Levels in Chapter 6 of the 9700 Feature Overview Manual
w “Translation Utility” on page T-156
w “PC Keyboard” on page U-4
K-10
Keyboard Workstation
Description
The Keyboard Workstation (KBWS) is a user workstation that is designed for
multi-revenue center high volume operations that need a simple to use but feature-
rich terminal. The KBWS is virtually water resistant and will work well in
environments where weather is a factor (e.g., arena, theme park, and stadium
environments).
For a complete description of the KBWS, refer to the 9700 Keyboard Workstation
Configuration and Installation Manual.

K-12
L
Labor Day Start Time
Description
The Labor Day Start Time is the pivot point used by the system to calculate
daily labor totals. It is set by a manager (or an installer) as the start of the business
day.
Usage
The labor day start time allows the 9700 System to accumulate daily time keeping
totals. These totals are used by the System to calculate labor hours and overtime.
The labor day start time should be set at a time after closing and before opening,
when no employees are clocked in to the System.
Example
Restaurant employees begin work at 9:00 a.m. for the 10:00 a.m. opening. The
restaurant closes at 3:00 a.m., and employees are usually out by 4:00 a.m. The
Labor Day Start Time is set for 6:00 a.m.
4:00 6:00 9:00

12:00 3:00 Last Labor Day First 10:00 12:00
Midnight Closing Clock-Out Start Time Clock-In Opening Midnight
At a 24-hour establishment, the start time should be set at a time when the fewest
number of people are clocked in, or at a time agreed on as the end of one business
day and the beginning of the next.
9700 HMS A to Z Feature Reference Manual L-1

Labor Day Start Time
Some employees may clock in before the Labor Day Start Time and clock out
after that start time. In this case, all of the hours for that employee’s shift are
credited to the day when the majority of the shift took place. For example, if a
cleaning person clocks in at 3:00 a.m. and works until 7:00 a.m., all of that
person’s hours are credited to the first day because three hours (3:00 to 6:00)
occurred in the first day and only one (6:00 to 7:00) occurred in the second.
Reports
The labor day start time determines which hours that an employee works are
overtime and which are regular. This determination affects all totals in the
following reports:
w Employee Labor Detail
w Employee Labor Summary
w Job Code Labor
Enabling
1 System Parameters

R Start of Labor Day field
Related Topics
w “Labor Week Start Day” on page L-3
w “Time and Attendance” in Chapter 8 of the 9700 Feature Overview Manual
L-2
Labor Week Start Day
Description
The Labor Week Start Day is the pivot point used by the system to calculate
weekly labor totals. It is set by a manager (or an installer) as the first day of the
work week.
Usage
The labor week start day is the day that the System uses as the restart time for
calculating overtime for each week. For example, if the start day is Sunday, the
System will begin counting labor hours for each employee on Sunday. The next
Sunday, the System will reset to zero and start counting again.
If the System finds the hours worked by one employee during the week are greater
than the number entered into the Job Code File as the overtime number of hours,
the employee is credited overtime hours and pay.
Each work week is treated as a separate unit, usually of 40 hours. The “work
week” can begin on any day of the week, to match any payroll cycle.
Reports
The labor day start time determines which hours that an employee works are
overtime and which are regular. This determination affects all totals in the
following reports:
w Employee Labor Detail
w Employee Labor Summary
w Job Code Labor

Enabling
1 System Parameters

R Start of Labor Week field
Related Topics
w “Calculating Time Worked” in Chapter 8 of the 9700 Feature Overview
Manual
w “Labor Day Start Time” on page L-1
w “Time and Attendance” in Chapter 8of the 9700 Feature Overview Manual
L-4
Language Support
Language Support
Description
The 9700 has several features that make up its language support. The System has
an easy-to-convert text file, in which an installer or dealer may convert all the text
that the system uses to another language.
The 9700 also provides full, eight-bit, character codes, including character values
128 to 255. These codes allow the 9700 to display and print characters from many
different languages.
Related Topics
w “Credit Card Handling” in Chapter 11 of the 9700 Feature Overview Manual
w “Standard vs. Extended Character Sets” on page K-4

Limited-Availability Menu Items
Description
A Limited-availability Menu Item is a menu item that has a user-defined limit
on the quantity available. The 9700 System keeps track of limited-availability
menu items in order to restrict employees from:
w placing an order for a limited availability item that has run out, or
w placing an order for more of an item than are available
For example, if a restaurant has a limited number of lobster tails available for each
shift, that menu item may be programmed as a limited-availability menu item.
Usage
Menu Item Counts for limited-availability menu items are set by privileged
employees through UWS Procedures. The 9700 System automatically checks the
availability each time the item is ordered. The beginning count (Spcl Cnt) is
decremented each time the item is ordered. When the count becomes zero and
another of the menu item is ordered, the system responds with the prompt, “NO
MORE [menu item name] REMAINING.” If an order is placed for more of an
item than is on hand, the system responds with the prompt, “ONLY # ITEMS
REMAINING.”
L-6
Enabling
1 Menu Item Class
R Check Menu Item Special Count—Enable this option to identify
these items as having limited availability.
1 Menu Item Master
Menu Item> | General
R Count on Hand field—Enter the number of items available for sale.
R Out of Menu Item—Enable this option to make this menu item
unavailable for posting.
Optional Settings
2 Personnel | Employee Maintenance | Sort By Class | Procedures & Reports

| UWS Procedures
R Use UWS Procedure #14: Change Menu Item Availability
Related Topics

Description
A Line-by-line Customer Receipt is used for fast transactions. A line-by-line
customer receipt prints each detail item as keys are pressed. For example, if a
bartender is programmed to print line-by-line and she presses a [Strawberry
Daiquiri] key, it prints immediately.
Other methods of printing receipts include:
w Buffeted Customer Receipt - No printing takes place until a tender key (that is
programmed to print customer receipts) is pressed.
w On-demand Customer Receipt - No printing takes place until after the

transaction is tendered, and then only if the [Print Customer Receipt] key is
pressed.
Usage
All customer receipts are used to record sales for a customer. The line-by-line
feature is used to print receipts quickly. Detail entries (e.g., menu items, discounts,
service charges, tender/media) print as the key is pressed, rather than after the
entire order is tendered.
Line-by-line printing provides faster customer service, since the receipt is ready to
present to the customer when the transaction is closed.
When line-by-line customer receipts are used, the designated customer receipt
printer is “dedicated” to the customer receipt being printed (i.e., no other printing
may take place while engaged in a transaction).
Service total of line-by-line fast transactions is also supported. When the
transaction is picked up after being service totalled, it is no longer in line-by-line
mode.
L-8
transaction. The Type Definition for Credit card [Tender] keys must be
w Amount Required
Operation
w Press the [Credit Card Lookup] key.
w The UWS prompts Enter credit card info.
card number and press [Enter]. The UWS prompts for the amount to be
tendered, if the credit card [Tender] key is programmed to do so.
Enabling
1 Operators

R Line by Line Customer Receipt—Enable this option to allow an
operator to print receipts line-by-line.


R Don’t Print Check Open Time on Customer Receipts

R Do Not Allow Service Total of Fast Transactions—Enable this
option when line-by-line printing is used.
Optional Settings


R 626-Credit Card Lookup
1 Tender/Media
2 System Information | Tender Media | Key Type=Payment | <Select

Category POS Ops Behaviors> | Ops Behaviors
R Amount Entry is Required
Related Topics
w “By-Round Guest Check” on page B-28
w “Customer Receipt” on page C-53
L-10
Local Order Output
Local Order Output
See “Order Output” on page O-12

Local Order Output
L-12
M
Macros
Description
A Macro is a key that is programmed to act as if a number of keys are pressed in
sequence. Macros can be programmed to include menu item, service charge,
discount, tender/media, function, and alphanumeric keys, or a link to another
macro.
Some keys prompt for an entry. Keys of this type might include an [Employee
Meal] key that prompts for an ID number, a [Misc Food] key that prompts for an
alphanumeric entry, or a discount or tender/media key that prompts for an amount
entry. These alphanumeric entries may be programmed into the macro, if they are
known in advance. If they are not pre-programmed, the macro pauses in its
execution to prompt for the entry. After the operator responds to the prompt by
making an entry, the macro continues executing any remaining keystrokes in its
program.
The 9700 system allows a maximum of 255 macros. Each macro can be
programmed to include up to 16 steps (keys). Up to 20 macros can be linked
together.
9700 HMS A to Z Feature Reference Manual M-1

Macros
Usage
Macros are used to save time when employees frequently enter certain sequences
of keystrokes.
Example
A restaurant is offering a combination special that features a hamburger, fries,
soda, and a discount. This special could be entered in the System as a single menu
item, using a single key. Using this method, however, the individual items
included in the special could not be tracked on sales reports.
By programming the combination special as a macro, each menu item (and the
discount) in the special can be tracked separately. This macro consists of the
following keys:
w Hamburger (menu item key)
w Fries (menu item key)
w Soda (menu item key)
w Combo Coupon (discount key)

When an operator presses this macro key, the three menu items and the discount
are entered in the transaction.
Enabling
1 Macros
2 RVC Information | Macros
R For each macro, complete all fields in this file.
R Prompt for Entries—Enable this option to show a prompt message if
the macro contains a key with entry requirements.
R Download to HHTs—Enable this option to prevent the System from
signing out a pop-up operator while in a keyboard macro function. The
operator will be signed out when the macro terminates provided the
employee is not currently in a transaction, UWS report, or UWS
Procedure.
R No Employee PopUp While in Macro—Enable this option to control
operator pop-up while in a macro.
M-2
Macros
Keyboard> | Key Configuration | Type=Macro | Link

Type=Macro | Number
R [Macro] key
R [Macro NLU] key
Optional Settings
The following option may be set on a discretionary basis:
1 System Parameters
R Do Not Check for Macro Loop Limit - Testing Purposes Only—
Enable this option to disable the limit of 20 macro executions. This
option is intended for use in installing and testing a system. This option
should be disabled for normal operations.
Related Topics

Magnetic Card Reader
Description
A Magnetic Card Reader is a component of a User Workstation’s hardware. The
magnetic card reader scans the information off the magnetic stripe on an
employee card or a credit card. Magnetic employee cards contain employee
identification numbers, which are numbers that employees use to sign in and
clock in. The same magnetic card reader can also read credit cards.
Usage
Magnetic card readers may be used in a number of ways.
As an employee card reader, a magnetic card reader allows greater security in
timekeeping and system access. To clock in or sign in to the system, an employee
swipes their employee ID card.
If an operator is attempting to perform a function that requires authorization (e.g.,
voiding menu items), the authorizing employee (e.g., a manager) can enter their
ID number to authorize the activity by swiping their card.
As a credit card reader, a magnetic card reader is faster and more accurate than
typing the credit number and expiration date manually. If credit authorization/
electronic draft capture (CA/EDC) is used, a magnetic card reader may also be
less expensive than authorizations of manually entered credit card numbers.
Some types of cards are encoded with two tracks (two lines) of magnetic data.
UWS/1 and UWS/2 card readers can only read Track 2, which is used by Micros
employee cards and all major credit cards. The UWS/3 magnetic card reader can
read Track 1 and Track 2. Some membership organizations (e.g. country clubs)
use Track 1 to encode member information.
M-4
Enabling
Employee Card Reader
1 Employee Class
w Use UWS Procedure #3: Employee Setup—When using a mag card
reader to enter employee ID numbers, place the cursor on the
Employee ID field. Swipe an employee card. The number that is
encoded on the card is entered in the Employee ID field.
w Access Employee Job Code and Pay Rates in UWS Procedure #3
w Use UWS Procedure #4: Employee Revenue Center Setup

w Hide Employee IDs in Employee Setup UWS Procedure—This
option must be disabled.
Credit Card Reader
1 Tender/Media
R Preamble field
R Use With Credit Card Recall
R Check Credit Card Expiration Date
R PMS or Credit Card Reference Entry field: 19 Digit or 16 Digit
R Reference Entry Required

Related Topics
w “Employees and Transactions” Chapter 7 of the 9700 Feature Overview
Manual
w “Credit Card” on page C-40
M-6
Major Group
Major Group
Description
A Major Group is a grouping of related menu items for reporting sales
summaries.
Usage
The Major Group Sales Report and Major Group Food Cost Report provide sales
and cost information for each major group programmed in the 9700 System.
Example
In Samantha’s restaurant, liquor, sodas, coffee, and milk are menu items that are
included in major group #3, which is labeled “Beverages”.
Each time a soda is ordered at a Workstation, the record of the sale is posted to,
among other places, major group sales.
When Samantha runs a Major Group Sales report for a given day, the line entry
for major group #3, Beverages, shows a single sales count and single dollar
amount totalling all drinks sold that day.

Major Group
Reports
Major Group Sales Report

w Gross Sales count
w Gross Sales total
w Item Discount count
w Item Discount total
w Net Sales count
w Net Sales total
w Subtotal fields—A subtotal line prints for all Major Groups that are
programmed with the same number in their Report Group field.
Major Group Food Cost Report

w Quantity Prepared
w Quantity Sold
w Yield Percentage
w Total Prep Cost
w Total Sales Amount (less Item Discounts)
w Food Cost Percentage
M-8
Major Group
Enabling
1 System Parameters
R Post MI, Major/Family Group Sales Totals Net of VAT
1 Major Group
2 Menu Items | Menu Item Maintenance | Sort By MI, by Major/Family
Group | <Select Major Group> | Major Group
R For each Major Group, fill in all fields.
1 Menu Item Master

2 Menu Items | Menu Item Maintenance | Sort By MI, by Major/Family
Group | <Select Menu Item> | General | Menu Item Master
R Major Group field
Related Topics
w “Family Group” on page F-1
w “Major and Family Group Files” in Chapter 6 of the 9700 Feature Overview
Manual

Media Pickup/Loan Tendering Keys
Description
Media Pickup and Loan Tendering Keys are two non-payment type tender/
media keys.
Usage
Media [Loan] keys are used to record non-sales transactions that place cash in a
UWS cash drawer. Media [Pickup] keys are used to record non-sales transactions
that remove cash from a drawer. Examples of non-sale transactions may include:
w Money placed in a drawer at the beginning of a shift to be used for making
change (often called an “Opening Bank”).
w Money removed from a drawer during the shift to be used to purchase

supplies (often called a “Paid-Out”).
w Money removed from a drawer during the shift to pay servers for charged tips.
w Money removed from drawer during a shift to reduce losses in the event of a
robbery (sometimes called a “Drop”, a “Pickup”, or a “Bleed”).
w Money removed from a drawer at the end of a shift to repay the opening bank
(often called an “Ending Bank”).
Reports
This feature may be tracked in a Tracking Group and linked to Financial Reports.
The [Tips Paid] key is a Media Pickup key, which oosts to the following reports:
w Establishment Tip Report
w Revenue Center Tip Report
w Employee Tip Report
M-10
Enabling
1 Operators
Operator> | Options | Miscellaneous
R Bank Entry Required at Beginning of Shift

R Cashier Totals Declaration Required with [Tender/Media] and [Tips
Paid] keys
R Allow Void of Tender/Media in Current Service Round Only
1 Tender/Media
R For each media [Pickup] and [Loan] key, fill in all fields in this file.
Related Topics
w “Tips Handling” on page T-69

Multi-tasking Capability
Multi-tasking Capability
Description
The Multi-tasking Capability used by the 9700 system allows different
components of the software to be active at the same time.
Usage
Managers may make changes to the database (e.g., changing prices, adding
employees) while the POS system is posting sales, and while still another
manager is using the Report Writer module.
Related Topics
w “The Operating System” in Chapter 7 of the 9700 Feature Overview Manual
M-12
N
No Sale Key
Description
No Sale is a function key that opens the cash drawer outside of a transaction.
Usage
[No Sale] keys are usually used when an operator wants to make change.
Reports

w No Sale Count field
Serving Period Financial Report

w No Sale Count field
Income Audit Report

w The flexible format of this report can be programmed to include a No Sale
Count field.
9700 HMS A to Z Feature Reference Manual N-1

No Sale Key
Enabling
1 Keyboard File or WS Touchscreen File


R 830 - No Sale

R Authorize Opening Cash Drawer Using the [No Sale] key—Set this
ON to allow an employee to use the [No Sale] key.
Optional Settings
1 Workstation Table
R Close Cash Drawer Before New Trans.

R Employee ID required with [No Sale] key—Set this ON to cause the
System to prompt for the signed-in operator’s Employee ID when the
[No Sale] key is pressed. This is intended for stay-down operators who
may need to walk away from the UWS (e.g., bartenders, sales clerks).
Related Topics
w “Cash Drawer” on page C-4
N-2
Number Lookup (NLU)
Number Lookup (NLU)
Description
A Number Look Up (NLU) is a key that, when pressed, will access a numbered
list of one of the following:
w Menu items
w Discounts
w Service charges
w Tender/media
w Menu levels
w Keyboards
Usage
Number Look Ups are used to save space on a keyboard. One NLU key can take
the place of an unlimited number of keys. Instead of one key for each brand of
soda, one NLU key could be programmed to display a numbered list of all the
brands.
NLU vs. SLU

Number Look Ups are similar to, but not the same as, Screen Look Ups (SLUs).
An SLU is used to access a specific touchscreen. An SLU accesses a screen, but
an NLU accesses a numbered list.

Number Lookup (NLU)
Enabling
For All NLUs

R 101-132 - Menu Item NLU

R 200 - Discount NLU
R 201 - Service Charge NLU
R 202 - Tender/Media NLU]
1 Operators
Operator> | Options | NLU
R NLU List is Stay-down

R NLU/Condiment Help Screen Sort Type field
For Menu Item NLUs

R Barcode Menu Item NLU Group # field
R Enable Condiment Masking—Only display those condiments that are
allowed with the parent menu item
N-4
Number Lookup (NLU)

2 RVC Information | RVC Descriptors | <Select Group Name Condiment
Group Names>
R Menu Item NLU Name fields 1 - 32

2 Menu Items | Menu Item Maintenance | Sort By Menu Item | <Select
Menu Item> | General | Menu Item Definitions
R NLU Group field

R NLU Number field
1 Operators
Operator> | Options
R Display Menu Item NLU Number

R Display Condiment Help
R Display Menu Item NLU Number on HHT
For Tender/Media NLUs
1 Tender/Media
2 System Information | Tender Media | <Select Key Type> | NLU/SLU
R NLU field
For Discount NLUs
1 Discounts
2 System Information | Discounts | NLU/SLU
R NLU field

Number Lookup (NLU)
For Service Charge NLUs
1 Service Charges
2 System Information | Service Charges | NLU/SLU
R NLU field
For Keyboard NLUs
1 Keyboards
R Keyboard 1 and 2 Select fields—Up to eight possible keyboard NLUs

may be assigned.
Related Topics
w “Changing ASCII Sort Order: The collate Program” on page S-43
w “Hand-held Touchscreen” on page H-1
w “Keyboards-User Workstation” on page K-1
N-6
O
On-Demand Guest Check
Description
An On-demand Guest Check is a printing option that prints a guest check only
when the operator orders it by pressing a [Tender/Media] key that is programmed
to print the guest check.
An On-demand guest check may be printed by pressing a [Service Total] key or a
[Tender/Media] key that is programmed to print the guest check.
An alternative guest check printing option is By-round. By-round means that the
check is printed at the end of every service round, at any time the guest check is
service totaled.
Usage
On-demand printing is often used in a restaurant environment that generates many
service rounds. On-demand printing eliminates the need to print each time orders
are added to a guest check.
Example
A server places orders for a meal that includes the following courses, which are
ordered in separate service rounds:
w Drinks
w Appetizers
w Salads
9700 HMS A to Z Feature Reference Manual O-1

w Entrees
w Drink Refills
w Dessert & Coffee
The guest check detail is retained in memory during the course of the meal. The
guest check is printed once, at the end of the meal, and presented to the customer.
On-demand printing reduces the chances of having guest checks become lost or
soiled before being presented. On-demand printing saves paper if the guest check
is printed on a slip printer, because the subtotals from each service round are not
printed, and sort and consolidate options can be used to combine items from
multiple service rounds.
Enabling
2 RVC Information | RVC Parameters | Posting & Control

R Number Checks Printed Before Authorization field

R Prompt On-demand Operator to Print Split Check

R Print Trailer Lines on Split Check if On-Demand - Format Option #5
O-2
1 Employee Class

Printing | Check\Receipt
R Authorize Unlimited Reprinting of a Check
1 Tender Media
2 System Information | Tender Media | KeyType=Payment | Key Type |

Printing Options
R Print Check On Demand
1 Operators

R ON = On-demand; OFF = By-round—Enable this option.
Related Topics
w “Special By-Round Operator” on page S-45

Open Check Block Settlement
Description
The [Open Check Block Settlement] keys allow an operator to close all open
checks for a specific operator to cash. Operators may use an [Open Check Block
Settlement] key to close their own open checks, or they may be prompted for the
employee number or employee ID of another employee.
Usage
This feature is used in server banking operations in which a large number of
checks are closed at once to cash.
Example 1
Samantha works as a cocktail waitress at a nightclub. During the course of the
show, she orders drinks and delivers them to 25 different tables. In the process,
she opens 25 different guest checks. Samantha uses server banking. Therefore, she
collects the payments for the drinks and makes change.
Three of Samantha’s tables pay their checks with credit cards. The rest pay in
cash. Samantha closes those three tables to the appropriate credit card tender.
At the end of the show, the crowd files out, and Samantha is left with 22 open
checks of varying amounts, and an apron pocket full of cash. Rather than close
each check to the exact amount, making 22 payments to the cashier, Samantha
presses the [Open Check Block Settlement - Signed In Operator] key.
The System closes all of her open checks to cash. The UWS displays a list of the
check numbers, table numbers, and amounts due for each of her open checks,
followed by the total number of checks, and the total amount due. This same
information prints on a receipt at the guest check printer. Samantha pays the
cashier the amount due for these closed checks, and keeps the rest of the cash as
her tips.
Example 2
Samantha used to work at another nightclub (which also had the sagacity to install
a MICROS 9700). At that nightclub, the bartender acted as the cashier. At the end
of a show, he would close Samantha’s checks, using the [Open Check Block
Settlement - Prompt Operator] key. He was prompted to enter her employee
number, after which her open checks were closed to cash, and he presented her
with the printed total and collected her payment.
O-4
A typical settlement receipt is shown below, followed by a description of each line

item.
1 101 JOE
---------------------------------------------------------------
2 RESTAURANT SEP25’94 10:13AM
---------------------------------------------------------------
3 OPEN CHECK BLOCK SETTLEMENT
4 123 SMITH 123
5 CLOSED
6 CHK 328 TBL 2/1 10.50
6 CHK 329 TBL 37/4 15.80
6 CHK 330 TBL 3/1 2.65
--------------
7 3 TOTAL CLOSED 28.95
Line Description...
1 This line prints the employee number and check name of the operator
who pressed the [Open Check Block Settlement] key.
2 This line prints the name of the Revenue Center in which the checks
were closed, followed by the date and time the key was pressed.
3 This line prints the title of the operation: the name of the key that was
pressed.
4 This line prints the employee number and last name of the operator
whose checks were closed.
5 This line indicates that the operation successfully closed all open
checks. If something prevented closure (for example, the current
operator is not privileged to use the [Cash] key), this line would read
“STILL OPEN”.
6 These lines print information for each check closed: the check number,
followed by the table number and group number (if table numbers are
used), followed by the amount due for each check.
7 This line prints the total number of checks that were closed to cash,
followed by the total amount of cash due.
Reports
Checks that are closed using this key appear on reports as though they were closed
using the System’s [Cash] key. Use of this key does not affect reports in any other
way.

Enabling
1 Devices

R Guest Check field—The block settlement receipt prints on this device.
1 Keyboard File or Touchscreens


R 433-OCBS - Signed Operator

R 434-OCBS - Prompt Operator

R Default Cash Tender/Media field—The [Open Check Block
Settlement] keys post to the Tender/Media key entered in this field.
This field should be programmed as the [Cash] key.
Optional Settings
1 Operators

R Use Employee Number to Open Check for Another Employee—
Enable this option to cause this operator to be prompted for employee
numbers. Disable the option to prompt for ID numbers.
1 Employee Class

O-6
R Authorize/Perform Posting of Tender/Media in Privilege Groups 1,

2, 3—The employee attempting a block settlement must be privileged
to post amounts to the [Cash] key.
R Authorize/Perform Open Check Block Settlement
Related Topics
w “Server Banking” in Chapter 7 of the 9700 Feature Overview Manual

Open and Closed Check Files
Description
Open and Closed Check Files are files within the 9700 Database which store the
totals and detail of open and closed checks. The Open Check File stores open
check totals and detail in memory (i.e., in RAM) until the check is closed and
posted to the Closed Check File. The closed check file is written to disk in the PC.
Each Revenue Center must designate a specific PC on which to store check files.
Usage
The Closed Check File stores the detail of guest checks that have been closed. The
information stored in the closed check file allows operators to adjust or reopen a
closed guest check.
Open Check Files hold active guest check data so that operators may service total
a guest check and then pick it up again later.
The amount of space that the PC devotes for each Revenue Center to open checks
must be specified in the Checks section of the Revenue Center Configuration file.
There are two fields that must be programmed:
Maximum Number of Open

This field is used to specify the maximum number of open checks that each
Revenue Center should be expected to handle at one time. Each open check
allocation requires approximately 100 bytes.
For example, if a Revenue Center has 30 tables, and there are seldom more
than two checks open for each table, one might set this field to 60 (or perhaps
to 75, since memory is relatively cheap, and running out of checks when you
are busy is inconvenient).
O-8
Maximum Number of Detail Blocks

This field is used to specify the sum of the maximum number of detail blocks
that each Revenue Center should be expected to handle at one time. A detail
block corresponds to approximately ten lines of transaction detail items (e.g.,
menu items, discounts, tenders, etc.). This number is only approximate
because some detail entries require two lines. For example, a discount with a
reference entry counts as two lines. Some Credit Authorization entries can use
up to eight lines. Each Detail Block requires approximately 500 bytes.
Continuing the example begun on the previous page, suppose a large check in
this Revenue Center might contain as many as 32 items. That large check
would require four detail blocks (32 / 10 = 3.2, rounded up to 4). With 75
open checks allotted to the Revenue Center, this field would be set to at least
300. (75 open checks X 4 detail blocks each = 300).
Reports
Employee Open Check Report

w All fields

w All fields
Financial Report
w Checks Begun field
w Transferred In field
w Checks Paid field
w Transferred Out field
Enabling

R PCs box—Select the PC to be active in this Revenue Center.
R PC With Check and Status Files field

R Maximum Number of Open field

R Maximum Number of Detail Blocks field

R Zero or Negative Transactions Do Not Add to Guest Count or Guest
Check Count
R Allow Changes to Menu Items on Closed Checks
R Allow Service Total of Closed Checks
2 RVC Information | RVC Parameters | Options

Optional Settings
1 Employee Class

Printing
R Authorize/Perform Reprinting of a Closed Check

Guest Checks

Voids & Returns
R Authorize/Perform Voids in the Current Round
R Authorize/Perform Void of Menu Items on Closed Checks
R Authorize/Perform Void of Discounts on Closed Checks
R Authorize/Perform Void of Service Charges on Closed Checks
O-10
Related Topics
w “Adjust Closed Check” on page A-10
w “Re-open Closed Check” on page R-7

Order Output
Order Output
Description
Order Output sends a work order to a printer or VDU. Items posted in a
transaction (e.g., menu items, discounts, service charges, and tender/media) may
be automatically printed or displayed at devices placed at remote locations, such
as a kitchen or bar.
Up to 15 order devices can be defined in each Revenue Center. Order devices may
include printers (usually roll printers) and Video Display Units (VDUs). Items can
be programmed to output to any combination of these devices.
Order output is triggered when a transaction (that includes detail items that are
programmed to output to order devices) is service totalled or tendered by the
operator. Orders may be posted to remote order devices or to a local order device
specified for each UWS.
Usage
Local Order Output

Local order output is often used to print an order for menu items that have
controlled access. For example, if a restaurant has a wine cellar, the managers may
want to use local order output. The operator enters the order; a local printer prints
the order; and the server takes the chit to a manager or sommelier, who retrieves
the wine.
Remote Order Output

Remote order output is used when you do not want the employee who posts orders
in a transaction to hand-deliver the orders to the persons who prepare them.
O-12
Order Output
Example
A large restaurant has two remote printers installed in its kitchen: one at the
grill, where hot food is prepared, and one at the cold food prep area, where
salads are made. A printer is installed at the UWS to print local orders.
Samantha places an order for a steak, a salad, a cup of soup, and a bottle of
champagne. She service totals her guest check.
A remote order for the steak prints at the grill in the kitchen. At the same time,
another remote order, for the salad, prints at the cold food prep area. The local
order printer produces a chit for the champagne. Servers are responsible for
getting their own soup orders; soup does not print on any remote or local
devices. Samantha uses the local order chit to retrieve the champagne and
soup, then delivers them to the table.
The diagram on page O-20 illustrates the files and fields that are involved in
order output.
Maximum Size
Each printer may be programmed to begin a second page when a certain number
of lines have printed on an order chit. This may be useful in a kitchen that has
limited space to display or store chits.
Example
Orders that print at the salad printer are hung in a rack over the salad chef’s
counter. The rack is mounted 12 inches above the counter. If an order chit
prints that is longer than 12 inches, the end of the paper dangles in the
tomatoes.
To avoid this, the salad printer is programmed to print a maximum of 72 lines
on a chit before beginning a second page. (Most MICROS printers print 6
lines per inch. 6 lines times 12 inches = 72 lines maximum.)
This feature is controlled by the Lines in Requisition Chit field in the Order
Devices file.

Order Output
CHK 1233
Order ------------- Check Devices File for order
posted 1 STEAK devices enabled
at UWS 1 SALAD for this UWS
1 DOM PERIGNON
1 CUP SOUP
1 2 3 4 5 6
Check Tender Media File

Output tab for order
devices enabled for the
key that posted this order
1 2 3 4 5 6
Check Menu Item Class

Output tab for
destination order devices
1 2 3 4 5
Check Order Devices File

for properly programmed
order devices. Establish
formatting and sorting criteria.
1 2 3 4
Was order output redirected

in the Order Devices File
(or by using UWS Proc #10)?
1 2 3 4
Check Order Devices File

Order Device Type field:
Is device type Local or Remote?
L R R
Check Devices File for the 2 3 4

Local Order Receipt Printer
designated for the UWS
that posted this order
Local Order Printer Remote Printer Remote Printer

*UWS #1* **KITCHEN** *PREP AREA*
1 DOM PERIGNON 1 STEAK 1 SALAD
O-14
Order Output
Enabling
1 Menu Item Class
R Output to order devices 1 through 15
1 Discounts
2 System Information | Discounts | Output

1 Service Charges
2 System Information | Service Charges | Output

1 Tender Media
2 System Information | Tender Media | Output

R Order Output Disable fields—Disable Order Device Number 1 through
15
1 Workstations
2 System Hardware | Devices | <Select Order Device> | Printers

R Order Device Enable fields—Enable output devices that can be
addressed by each UWS.
1 Order Devices
2 System Hardware | Order Devices | General

R Enable the output devices for each revenue center.
Optional Settings

Order Output
1 Workstations

R Local Order Receipt field—Designate the printer where local orders
should print
1 Menu Item Class
Class> | Output
R Print Price on Order Chit
R Print Name 2 on Order Output Instead Of Name 1
R Consolidate Menu Items with Condiments on Order Output
Class> | General
R Print Name 2 on Touchscreens Instead of Name 1
O-16
Order Output
1 Order Devices

R Order Device Header
R Backup Device Number field
R Order Device Type field
R Sort/Consolidation Method field—This field determines the method
by which menu items are sorted for printing (e.g., by seat, by print
group, by both) and determines whether or not multiple items are
consolidated.
R VDU Screen Configuration
R Max # Lines on Order Chit—This field may be used to specify the
maximum number of lines that print on an order chit before a new page
is started. If no maximum limit is required, set this field to 0. (Most
MICROS printers print 6 lines per inch.)
R Order Device Options
R Order Device Redirect field
2 System Hardware | Order Devices | VDU

R VDU Type Definitions
R VDU Order Timeout—For order printers, this field is used to specify
the maximum number of lines that should print before a new page is
started. If no maximum limit is required, set this field to 0. (Most
MICROS printers print 6 lines per inch.)

R Line Feeds Before Order Output Header field
Related Topics
w “Autocut Printing” on page A-22
w “Condiment Handling” on page C-27
w “Order Device File” in Chapter 3 of the 9700 Feature Overview Manual

Order Output
w “Dopplebon Printing” on page D-33
w “Printers” in Chapter 1 of the 9700 Feature Overview Manual
O-18
Order Redirection
Order Redirection
Description
Order Redirection allows an operator (usually a manager) to change the routing of
order output (remote or local) to a different order device in the same revenue
center. When the order prints at the new order device, it includes the header of the
original destination device.
The order devices for any printing item, such as a menu item, are defined in the
item’s definition file.
Redirection takes place in response to deliberate intervention by an operator,
unlike backup printing, which the system performs automatically when it is
unable to output to an order device.
Usage
UWS Procedure #11 controls order redirection. It may be used by any operator
with the proper privileges. This procedure allows the output to any order device in
the system to be redirected to any other order device in the system.
Example
A large restaurant has two bars in two different dining rooms. During busy
periods, orders placed by servers in each room print at the bar in that room.
During non-peak hours, the bar in one dining room is closed. Order output
from that dining room is redirected to the bar that remains open.
Enabling
1 Order Device

R Order Device Redirect field
Optional Settings

Order Redirection
1 Employee Class

R Use UWS Procedure #11: Redirect Order Output
R Run UWS Procedures In Another Revenue Center
O-20
Order Types
Order Types
Description
Order Types are menu item sales categories that also control the Tax Classes in
effect. Examples of order types may include “take out” and “dine in.” There are
eight order types available in the 9700 system.
Usage
Order Types are used to separate sales for reports and for tax purposes. Some
jurisdictions require different sales tax structures for take-out food. Order Types
allow menu items to be taxed differently in such situations.
Every transaction, before it is service totalled (or, in the case of a Fast Transaction,
before it is tendered), must have an Order Type declared. An operator may be
required to choose an Order Type for each transaction, and/or a default Order
Type may be programmed for all transactions.
Each transaction can have only one Order Type declaration. The Order Type may
be changed after service totalling or tendering, but totals remain posted to the
original Order Type.
The order type name may be programmed to print on output devices. In the case
of “take-out” vs. “dine-in” orders, the Order Type name can be used to let the
kitchen staff know whether to place an order on a plate or in a bag.
Order Type used as Subtotal

A Revenue Center can be programmed to use [Order Type] keys for subtotalling.
If this feature is used, summary totals (subtotal, tax, amount due, and change due)
are not displayed until the operator presses an [Order Type] key.
If a menu item is entered after an Order Type is declared, the Order Type entry is
removed (un-declared, if you will), and the summary totals are cleared from the
operator display.
The last-item void function will not work for transaction items that were entered
before the Order Type was declared.

Order Types
Transaction items that were entered before the Order Type was declared are
considered “previous round” items for voiding purposes. This means that
operators must be privileged to void these items.
A transaction cannot be cancelled using the [Transaction Cancel] key after an
Order Type has been declared.
Until the Order Type is declared, the guest check cannot be service totalled or
tendered, and currency conversion is not allowed.
Reports
Financial Reports
(System, Revenue Center, Employee)
w An Order Type Profile section may be programmed to print on these reports.
This section prints totals for each Order Type that is programmed as “active”
in the System Parameters File or the Revenue Center Parameters File.
Income Audit Report

w Order Type totals may be programmed to post as part of this report’s flexible
format.
Enabling
1 System Parameters
2 System Information | System Parameters | Order Types & Activation Codes

R Define, name, and activate Order Types on this tab.
O-22
Order Types

R Order Type is Active
R Default Order Type field—Set in either the Revenue Center
Parameters file for a Revenue Center, or in the Devices file, for each
User Workstation. The Devices file Order Type takes precedence.
R Taxes 1 through 8—Enable the active tax for each Order Type.
If guest checks are to be added or transferred across

Revenue Centers, the Order Type tax programming
must be identical in each Revenue Center.
1 Devices

R Default Order Type field—Set in either the Revenue Center
Parameters file for a Revenue Center, or in the Devices file, for each
User Workstation. The Devices file Order Type takes precedence.
Optional Settings
1 System Parameters

R Do Not Print The Order Type Breakdown On Financial Reports

R Print On Customer Receipt and Guest Check
R Print On Order Printers—Enable this option to print the Order Type
name on order chits.
R Output to VDUs

Order Types

R Display Summary Totals Only after Order Type Declared—Enable this
option to cause [Order Type] keys to function as subtotals.

R Allow Void Of Discount in Current Service Round Only
R Allow Void Of Service Charge in Current Service Round Only
R Allow Void of Tender/Media in Current Service Round Only

Keyboard> | Key Configuration
R If you program both the Order Type Defaults to 0 in the Revenue

Center Parameters file and the Devices file, you may program keys to
determine the order type in this file.
1 Employee Class

R Authorize/Use the [Order Type] key

Voids & Returns | Voids
R Authorize/Perform Void of Menu Items from a Previous Round
R Authorize/Perform Void of Discounts from a Previous Round
R Authorize/Perform Void of Service Charges from a Previous Round
R Authorize/Perform Void of Tender/Media from a Previous Round
O-24
Overtime
Overtime
Description
Overtime refers to the hours worked and the wage paid to employees after a
specified number of hours in a day or period, such as a week. The 9700 System
can be programmed to have the same pay for overtime as for regular working
hours.
Usage
Overtime is used to determine pay for employees and to keep track of hours and
pay on reports.
Reports
Employee Labor Detail

w Overtime Hours/Rate field
w Pay field
Employee Labor Summary

w Overtime Hours field
w Overtime Pay field
w Total Hours field
w Total Pay field
Job Code Labor

w Overtime Hours field
w Overtime Pay field
w Total Hours field

Overtime
w Total Pay field
Enabling
1 Employee

Employee> | Job Codes/Pay Rates
R Overtime Pay Rate field
1 Employee Class

General
R Number of Hours/Day Before OT field or Number Hours/Period
Before OT field—Enter the number of regular hours that employees in
this class can work before being paid at the overtime rate.
Related Topics
w “Overtime” on page O-25
O-26
P
PC Workstation
The PC Workstation (PCWS) is a personal computer that functions both as a PC

and a User Workstation. For a description of PCWS features, refer to Chapter 1 of
the 9700 Feature Overview Manual.
9700 HMS A to Z Feature Reference Manual P-1

Period Totals
Period Totals
Description
Period Totals are sales activity totals over a user-defined time period. The 9700
keeps track of all sales activities, such as:
w Cash received
w Number of each menu item sold
w Sales by operators
w Labor costs
Usage
Use period totals to keep track of any totals set for any period of time, such as a
week, month, or quarter.
The 9700 keeps track of every activity from the first day it is installed. The
System automatically generates Current period totals. The System may also be
programmed to generate a Previous period total and up to eight user defined to-
date period totals. When an autosequence is run to “close out” the day, current
totals are added to previous totals, then the current totals are reset to zero.
P-2
Period Totals
Add
Current Totals Period Total 1 (P1)
Period Total 0 (P0) Previous Totals
Current total reset
Period Total 1 (P1) Add Period Total 2 (P2)

Previous Totals
Add Period Total 3 (P3)
Current total reset
Enabling
1 Totals Sets
2 System Information | Totals Sets | General

R Total Set Definition Name
R Total Set Period Number
R Do not enter any name into the Use Directory Name field; this field is
for saved totals only.
1 UWS Autosequences or PC Autosequences
2 Totals Set—Enter 0 to cause the autosequence to prompt for the total

period, or enter 1 - 9 to designate the total period to be reported and/or
reset by each autosequence.

Period Totals
Related Topics
w “Descriptors” on page D-13
P-4
Pickup Check SLU/On Hold Items
Pickup Check SLU/On Hold Items
Description
The Pickup Check SLU can now display all guest checks with menu items on hold
in reverse video.
Enabling
1 WS Touchscreen Style

R Show Checks w/Held Items in Inverse in Open Check SLU

PMS Interface
PMS Interface
Description
The PMS Interface allows the 9700 system to communicate with a PMS (e.g., a
hotel’s front desk system).
Usage
A PMS Interface is used to link the 9700 System to a PMS. The 9700 System is
designed to communicate with up to eight Property Management Systems (PMS)
per Revenue Center and 128 per system. (More than one Revenue Center may
access the same PMS.) Communication may be established using either of two
methods:
w A TCP interface may be set up to communicate through the System’s LAN.
w An Asynchronous Serial Interface (also referred to as a TTY interface) may

be set up to communicate through the COM port on the PC.
The 9700 System’s communication parameters are designed to be flexible enough

to allow communication with a wide variety of third-party PMS programs. Refer
to the PMS to POS System Interface Communications Programming and
Operations Manual.
Enabling
1 Interfaces

R Complete all fields on this form.
2 RVC Information | RVC Parameters | Interfaces

R Interfaces—Enter the name of each PMS.
P-6
PMS Interface
Related Topics
w “Interface File” on page I-5

PMS Inquire
PMS Inquire
Description
PMS Inquire is a function key that accesses a property management system
(PMS), usually a hotel’s front desk system. A cashier might inquire a PMS to see
if a customer’s charge may be posted to the room folio.
Usage
The [PMS Inquire] key is used to verify the occupancy of a room. The inquiry
allows the cashier to verify that the charge can be posted to the room number
provided by the guest. The inquire function is used to see that the customer has a
folio (a room or account with the hotel).
The Interface File may be programmed to allow the 9700 System to use either a
16-digit or a 19-digit reference entry for inquiries to a PMS.
Enabling
1 Interfaces

R Complete all fields on this form.
1 WS Touchscreen or Keyboards

Type=Function | Function Key Categories=Non-Sales Operations | Number

| Function Key Categories=Non-Sales Operations | Number
R 841 - [Inquire PMS 1]
P-8
PMS Inquire
1 Tender/Media
2 System Information | Tender Media | <Select Payment Tender Media> |

Key Type | Category=PMS Options |
R PMS Link
Optional Settings
1 Interface

R Use 19-Digit Reference Entry for PMS Inquiries
R Allow Inquire without Sign-In
Related Topics
w “Interface File” on page I-5
w “PMSwait” on page P-15

PMS Posting
PMS Posting
Description
PMS Posting is a function performed by a tendering key. It allows an operator at
a UWS to access a property management system and to transfer a charge to a
customer’s folio.
Usage
PMS posting is used when a customer wants to pay his restaurant check by having
it added to his hotel bill. The PMS decides whether or not to accept the charge,
based on the status of the customer’s account in the PMS.
The PMS then transmits a message of acceptance or denial to the 9700 System. If
the charge is accepted, the tender is complete. (If the tender amount was for full
payment, the transaction is closed.) If the charge is not accepted, the denial
message appears on the UWS display.
Detail entries that have been posted to the PMS (e.g., menu items, discounts,
service charges, tender/media) cannot be removed using last item void.
Prorating Itemizers for Partial PMS Posting

Some PMS products record sales postings by Itemizers. To meet the needs of
these types of systems, the 9700’s Revenue Centers may prorate Itemizer posting
(i.e., Sales, Discount, or Service Charge Itemizers) when a partial tender is made
to a PMS. If this is the case, the percentage of all itemizers posted to the PMS is
equal to the percentage of the tender.
Example
The amount due for a guest check in the hotel restaurant totals $100.00. The
customer elects to charge $70.00 to his room account and pay $30.00 in cash.
The operator posts a $70.00 charge to the account in the PMS and tenders the
balance to cash. In this example, 70% of the total of all Itemizers accumulated
for this transaction is posted to the PMS.
If prorated Itemizer posting is not used, all Itemizers are posted to each tender.
P-10
PMS Posting
Prompting For Guests When Prorating Itemizers

If prorated Itemizer posting is used, the system may be programmed to prompt for
the number of guests to post to the PMS during a partial tender.
Continuing the example above, suppose the number of guests entered for the guest
check is 5. When the partial tender is posted to the PMS, the 9700 System
prompts, “ENTER NUMBER OF GUESTS”. Following hotel policy the operator
enters 1. The guest count of the PMS increments by one, and the remaining
number of guests (4) is posted to the 9700 System’s totals.
Search for Alternate Tender

The system makes repeated attempts to perform a PMS posting within a set space
of time. This “timeout” is specified in the Interface File. If a posting cannot
successfully be completed within this period (for example, if the PMS is inactive),
the system “times out” and stops attempting to perform the posting.
The system may be programmed to automatically post to an alternate [Tender/
Media] key in the event of a PMS timeout. If this feature is used, and a PMS
posting times out, the System searches for another [Tender/Media] key with the
same NLU number as the first key, and posts to that key instead.
This allows an installation to create a “Manual PMS Posting” key for PMS
postings that occur when PMS posting is not available. The totals posted to this
key can be posted to the PMS later, when communication is restored.
When the System posts to an alternate [Tender/Media] key after a PMS timeout,
that alternate (manual posting) key uses the Type Definition and Tender Output
Links of the original [Tender/Media] key. If an establishment wants the alternate
key to follow its own Type Definition and Output, a SIM script can be written to
redefine these fields for the alternate key.
If the posting required Credit Authorization, any previous CA entries are changed
to reflect the new [Tender/Media] key number.
Reports
Tracking Group Reports

PMS posting keys can be tracked.

PMS Posting
Financial Reports, Time Period Report, Serving

Period Report, Income Audit Report
Payment tender/media are used in a variety of calculations (e.g., Check payment,
Count, and Total fields).
Closed Check Report

PMS posting information is included.
Employee Tip Reports

If PMS posting keys are programmed to post to Gross Receipts and/or Charged
Receipts, posting information is included.
Enabling
1 Interface File

1 WS Touchscreens File or Keyboards File

2 Touchscrns & Keyboards | WS Touchscreens | [Type = Function] |

R [Post to PMS] tender/media key(s)

R [Inquire PMS] - keycodes #841 - #844 and #850 - #853
1 Tender Media File
2 System Information | Tender Media | [Key Type=Payment] | Key Type |

[Category=PMS Options]
R PMS Link field—Select the PMS to which this Tender/Media key
posts. Select None to disable PMS posting for this key.
2 System Information | Tender Media | [Key Type=Payment] | Key Type |

[Category=POS Ops Behaviors]
P-12
PMS Posting
Optional Settings
1 System Parameters File

R HRGAS PMS Compatibility—Select this option to cause all tenders
entered on a check to be voided when the check is reopened and the
first tender is voided.

R Prorate Itemizers When Posting a Partial Tender to a PMS—Select
this option to prorate itemizers (sales, tax, discount, service charge) of a
partially tendered transaction and post those amounts to the PMS.
R Do Not Save PMS Response if Credit Authorization Required
1 Tender Media

R ON = Post 0.00 Transactions to PMS; OFF = Do Not Post—Set this
ON to allow automatic inquiry when an operator attempts to post to the
PMS.
R ON = Print PMS Response; OFF = Print Only Posting Message
R ON = PMS & Credit Cards Use 19 Digit Account Number; OFF = 16
Digit
R ON = Post Amount Tendered to PMS; OFF = Post Amount Due
R Charged Tip Must be Less Than Payment
R Partial Tender Not Allowed
R Call ISL TMED Procedure Instead of PMS Posting
R Reverse PMS Itemizers on Void Postings
R Switch to Alternate Tenders if PMS Timeout

PMS Posting
Record Number Requirements

The posting message sent by the 9700 System to a PMS can only transmit a fixed
number of digits in the record numbers of certain files. If the 9700 System uses
PMS posting, these record number requirements must be observed:
Records allowed Records included in 9700

File
in 9700 System PMS posting message
UWS 1 - 999,999,999 1 - 99
Employee 1 - 999,999,999 1 - 9,999
Tender/Media 1 - 999,999,999 1 - 999
Serving Period 1 - 999,999,999 1 - 999
The 9700’s PMS posting message truncates any record numbers that exceed the
requirements stated here. For example, Tender/Media record number 100999
posts as 999.
Related Topics
“Interface File” on page I-5
“PMS Inquire” on page P-8
“PMSwait” on page P-15
P-14
PMSwait
PMSwait
Description
PMSwait is an 9700 program that sends a PMS inquire message over a PMS
interface, to determine whether or not the PMS is active. It is set up as an External
Program in a PC Autosequence.
Usage
PMSwait is intended for use in an environment in which the PMS interface is
periodically shut down, and certain PC Autosequences should not run if the
interface is still active. PMSwait provides a means of checking the status of the
PMS interface, and allowing the results to determine whether the autosequence
cancels or continues its remaining steps.
Once started, the PMSwait program sends PMS Inquire messages every few
minutes (this interval is programmable). The program continues until one of two
events occurs:
w The Inquire fails, meaning that the PMS interface is inactive (and it is OK to
continue with the rest of the autosequence), or,
w The amount of time set for the program duration expires, meaning that the
PMS interface is still active.
If the Inquire fails, the program ends and returns a successful status of 0 to the
autosequence. If the duration expires (meaning that the PMS interface is still
active), the program ends and returns a non-zero error status to the autosequence.
Autosequence programming then determines whether to continue or to cancel,
based on the status that is returned from PMSwait.

PMSwait
Implementation of switch style command line processing for the PMS Wait
function was enhanced in Version 2.01. Each PMSwait argument has been
replaced with a command line switch. This style of command line processing
provides you with the flexibility to quickly and easily add or change switch
settings. Use the table that follows to preview the new command line switches.
then the New and it has a default

If the Argument was....
Switch Setting is... value of...
pms_num -n 0
acct_id -a 0
uws_num -u 0
empl_num -e 0
interval -i 1 minute
duration -t 60 minutes
msg_file -m 0
PMSwait - R Switch
The manner in which the PMSwait function can confirm the status of a PMS was
enhanced in Version 2.01. Added to the list of available PMSwait command
arguments is the -r (retry_count) switch. Use this argument if you want the ability
to reconfirm the “inactive” status of a PMS prior to initiating a PC Autosequence.
When the retry_count argument is part of the PMSwait command, format it as
follows:
-r <retry count value>.
The value specifies the number of times that the 9700 System will send an inquiry
message to a PMS to reconfirm that it is inactive. The System will allow 15
seconds to elapse (interval is not modifiable) between each retry attempt.
This argument can be placed anywhere within the command and there are no
restrictions placed on the possible number of retry messages that can be specified.
A retry attempt is in addition to the initial message that is sent to the PMS.
Therefore, if the retry_count is 1, the System will make 2 attempts to send a PMS
message.
P-16
PMSwait
To use the retry_count argument, you must add it to the appropriate Autosequence
in the PC Autosequence file. You will find PMSwait command line arguments in
the Filename field of the PC Autosequence file. If you are adding this argument to
an existing PMSwait command that does not use the switch style command line
format, you must re-enter the entire command using the appropriate switches.
Enabling
1 PC Autosequence File
2 Reporting | PC Autosequences
To execute PMSwait as a step in a PC Autosequence, set up an External
Program, as described below:
R Type - Select External Program.
R External Program User Interface Type - Select No User Interface.
R Filename - Enter the pmswait command followed by six arguments, as
shown in the line below. The six arguments are described in the table
that follows.
Argument Description
-n Enter the PMS definition number, from the PMS File.

-a Enter the account ID (e.g., the room number or other
account) to be sent in the inquire message.
-u Enter the terminal ID to be sent in the inquiry
message. This number MUST be different from any
UWS number used in the System. If 2-digit terminal
IDs are in use (i.e., if PMS Configuration #8 is set
OFF), only the last two digits must be unique.
-e Enter the employee number to be used in the inquiry.
-i Enter the amount of time (in minutes) that should
elapse between inquiries.
-t Enter the amount of time (in minutes) the PMSwait
program should continue to repeat inquiries.

PMSwait
R Do Not Cancel Autosequence if External Program Returns an Error -

Step Type Definition #1
R Do Not Display Error if External Program Returns an Error - Step
Type Definition #2—Enable both of these options if the autosequence
should continue even if the PMS interface is still active. Disable both
options if the autosequence should halt if the PMS interface is active.
Options
The pmswait program may be programmed to send the contents of a file instead of
a standard PMS inquiry. This option is intended for use with the System Interface
Module (SIM). To send the contents of a file instead of an inquiry, use the
following syntax:
1 PC Autosequence File
2 Reporting | PC Autosequences
R Filename field—Enter the pmswait command followed by six
arguments, as shown in the line below. The six arguments are described
in the table that follows.
Argument Description
-n Enter the PMS definition number, from the PMS File.

-u Enter the terminal ID to be sent in the inquiry message. This
number MUST be different from any UWS number used in
the System. If 2-digit terminal IDs are in use (i.e., if PMS
Configuration #8 is set OFF), only the last two digits must
be unique.
-i Enter the amount of time (in minutes) that should elapse
between inquiries.
-t Enter the amount of time (in minutes) the PMSwait
program should continue to repeat inquiries.
-m Enter the name (including the path) of the file that contains
the message to be sent.
Example: pmswait -n4 -u29 -i1 -t10 -msim.msg

The message file to be sent should contain the body of a message,
starting with the character that should follow the STX (start of text
character), and ending with the character that should precede the ETX
(end of text character). The header and framing characters will be
generated by pmswait.
P-18
PMSwait
If this file contains a SIM message, it should begin with an FS (file

separator) character, a “00” sequence number, and a space (i.e., hex 1C
30 30 20), followed by a message in a format appropriate for the
receiving system.
The program sends messages as specified by the arguments until either
the request fails due to no response or the duration expires. If you want
a PC Autosequence to continue even though the duration expires
without the interface being down, make sure that PC Autosequence
Step Type Definition Option #1 (Do Not Cancel Sequence If External
Program Returns an Error) and #2 (Do Not Display Error If External
Program Returns an Error) are both set ON.
Related Topics
“Autosequences” on page A-26
9700 System Interface Module Manual

Pop-up, Stay-down Functions
Description
Pop-up and Stay-down refer to certain operational conditions at the UWS. Stay-
down means that the current condition remains active. Pop-up means that the
previous (or default) condition will become active when the current operation is
finished.
Pop-up and Stay-down are characteristics of:
w Menu levels
w Signed-in employees (especially cashiers and operators)
w Touchscreens
w NLU list
Usage
Menu Levels
A pop-up can be used to change menu levels before or after a menu item is
ordered. For example, all soft drinks (small, medium, or large) may be
programmed to pop-up to medium after they are ordered. When a soft drink is
ordered, the menu level always returns to medium.
Touchscreens
A Stay-down setting can be used to keep a condiment SLU screen active when
several condiments may be allowed for a single menu item.
Operators
Pop-ups can also be used to sign an operator off automatically after a transaction.
Bartenders and cashiers who are assigned to a single UWS and its cash drawer are
usually programmed as stay-down operators. Servers who share a common UWS
are usually programmed as pop-up operators.
P-20
Automatic Operator Pop-up Interval

Pop-up operators who sign in and do not begin a transaction, or who sign in
and then perform non-transaction activities (e.g., UWS Procedures) are
automatically signed out when the Automatic Pop-up Interval expires. This
field is set in the Revenue Center Parameters File.
This Interval may also be applied to specific staydown operators. This option
is controlled by Type Definition #15 (If Staydown Operator, Enable the Auto
Popup Timeout) in the Operator File.
The pop-up interval is programmed for each Revenue Center, but it may be
disabled for a specific UWS or HHT. If the Interval is disabled for a UWS or
HHT, it overrides Operator File and Revenue Center Parameters File
programming.
Employee Pop-up During Macro Execution

The System also provides the option to control operator pop-up during macro
processing. When Macro file Type Definition # 4 (Employee Popup While In
a Macro) is set ON, the System will not sign out a pop-up operator if, during
the execution of the macro the operator would normally be signed out. The
operator will be signed out when the macro terminates provided the employee
is not currently in a transaction, UWS Report, or UWS Procedure.
NLU Lists
A stay-down NLU list remains on the screen, allowing an operator to select items,
until the [Clear] key removes the NLU help screen.
Enabling
Menu Item Pop-ups/Stay-downs
Menu Item Class File

w Main Level Pop-up field
w Sub Level Pop-up field
w Keep Main Menu Levels With Repeat Rounds
w Keep Sub-Menu Levels With Repeat Rounds

Touchscreen Pop-ups/Stay-downs
Touchscreen Style File

w Stay Down SLU Screen
Operator Pop-ups/Stay-downs
Workstation Table
w Disable Auto Signout
w Disable Employee Auto Sign Out on HHTs
Operator File
w Pop-up Operator
w NLU List is Stay Down
w If Staydown Operator, Enable the Auto Popup Timeout
w HHT Pop-up Operator
Revenue Center Parameters File

w Automatic Operator “pop-up” Interval field—Set the amount of time (in
minutes and seconds) to elapse before an inactive operator is
automatically signed out.
w Staydown Operators Return to Original Revenue Center after [Change

Transaction Revenue Center] Keys
w To Save Batteries, Turn Off HHT on Employee Sign Out
Discounts
Discount File
P-22
Service Charges
Service Charge File

Tender/Media
Tender/Media File

w Retain Current Main Menu Level After a Transaction - Option #23
w Retain Current Sub-Menu Level After a Transaction - Option #24
Related Topics
w “Touchscreen Concepts” in Chapter 2 of the 9700 Feature Overview Manual

Post Sales
Post Sales
Description
To Post Sales means to record transactions. Any time a menu item is ordered or
paid for, the transaction is posted to totals files in the database (i.e., recorded in
memory).
Usage
Sales posting is used by reports to keep track of the quantity of each item sold and
the revenue generated by the sales.
Reports
Because this feature affects all sales totals, it affects all reports except Clock in
Status Reports and Labor Availability Reports.
Enabling
Options
System Parameters File

w Post Menu Item, Major Group, and Family Group Sales Totals Net of
VAT - Option #5
w Post Food Cost Totals Net of Item Discounts - Option #6

w ON = Post Totals to Transaction Operator; OFF = Post Totals to Check
Operator - Posting Option #6
w ON = Post Tenders to Transaction Operator; OFF = Post Tenders to Check

Operator - Posting Option #7
P-24
Post Sales
w If No Transaction Operator Cashier, Post to Check Operator Cashier - Posting

Option #8
w Require Cashier Totals to Begin a Transaction - Control Option # 2
w Post Error Corrects as Voids - Control Option #8
Tender/Media File
w Post to Gross Receipts on Tip Reports - Type Definition #10
w Post to Charged Receipts on Tip Reports - Type Definition #11
w HHT: Auto Send When Paid in Full - Type Definition #53

w Privilege Group field
Designate a privilege group to restrict the ability to post this Menu Item Class
to certain employees
Discount File
Designate a privilege group to restrict the ability to post this discount to
certain employees
Service Charge File

Designate a privilege group to restrict the ability to post this service charge to
certain employees
Tender/Media File
Designate a privilege group to restrict the ability to post this tender/media to
certain employees
Employee Class File

w Post Menu Items to Checks Belonging to Another Operator - Transaction
Privilege #19
w Post Discounts to Checks Belonging to Another Operator - Transaction

Privilege #20

Post Sales
w Post Service Charges to Checks Belonging to Another Operator - Transaction

Privilege #21
w Post Payments to Checks Belonging to Another Operator - Transaction

Privilege #22
w Authorize/Perform Posting of Payments - Transaction Privilege #37
w Authorize/Perform Posting of Menu Items in Privilege Groups 1, 2, 3 -

Transaction Privileges #49, #50, and #51
w Authorize/Perform Posting of Discounts in Privilege Groups 1, 2, 3 -

w Authorize/Perform Posting of Service Charges in Privilege Groups 1, 2, 3 -

w Authorize/Perform Posting of Tender/Media in Privilege Groups 1, 2, 3 -

Related Topics
“Repeat Round Function” on page R-10
“Service Total” on page S-26
P-26
Preserve Formatting Time Field
Preserve Formatting Time Field
Description
The ability to consolidate debugging information into the PMS log without having
to run the PMS process from the command line was added. This was previously
accomplished by using the -c command line switch.
Enabling
To enable this new functionality, create a file in the /usr/9700/etc directory (via
the touch command) entitled pms###.con_log, where the ### symbol is the object
number of the PMS interface (from the Interface Table) from which you wish to
obtain debugging information. You must either perform a Reload from the Control
Panel, or perform a kill -1 <process id>, inserting the process ID of the
PMS process you wish to monitor.
To disable this functionality, you must delete the pms###.con_log file, and
perform either a Reload or kill -1 <process id> again.

Prices
Prices
Description
Prices are the amount of money each menu item posts to reports and guest checks.
Both menu items and condiment menu items may be priced.
Menu items may be assigned a negative price. For example, a menu item
condiment named NO CHEESE might be priced at -$0.15.
Usage
Open Prices
Open pricing means the menu item has a 0.00 price entered in the Menu Item
Price Definition File.
Open pricing is used for menu items that are usually sold as part of a combination
dish or for menu items that change price frequently. Open-priced menu items can
also be used to charge for items that are not on the menu, but which the restaurant
agrees to sell. (e.g., “Yes ma’am, I’m sure the chef can make a peanut butter &
jelly sandwich for your little boy.”)
An operator enters a price when the item is ordered. If an open-priced menu item
is accessed through an NLU, the UWS prompts for the price amount. If an
operator presses an open-priced menu item key before entering an amount, the
UWS displays an error prompt.
When an item is open priced, it may have a HALO (high amount lock-out)
associated with it. A HALO is an upper limit on the amount that may be charged
for this item.
Fixed Prices
Fixed prices are those that are entered for a menu item in the Menu Item Price
Definition File. Each menu item may be programmed with up to eight different
prices. These prices may correspond to different times of day, sizes of menu item
or other price changes that occur regularly.
Split Pricing
The UWS automatically calculates split prices. Split prices are entered using the
[@/For] key. For example, split pricing is used to charge for an order of 10
doughnuts when doughnuts are priced at $5.00/dozen.
P-28
Prices
Price by Weight
Menu items may be programmed to be priced by weight. The Menu Item Price
Definition File may be programmed to price menu items by the pound or by the
kilogram.
Non-priced Menu Items

Menu items may be programmed not to have a price assigned to them. For
example, prep instructions, such as MEDIUM RARE, are non-priced. The
advantages of non-priced menu items (as opposed to menu items with an assigned
price of 0.00) include:
w No record is required to be created in the Menu Item Price File, thus saving
memory.
w Non-priced items can be programmed to be omitted from guest check or

customer receipt printing.
w Non-priced menu items are not included in any menu item reports.
Reports
Because this feature affects all sales totals, it affects all reports except Clock in
Status Reports and Labor Availability Reports.
Non-priced menu items do not affect or appear on any reports.
Enabling

w ON = Open-priced menu items; OFF = Preset Menu Items - Type Definition
#1
Set ON for Open-priced and Weighed Items.
Menu Item Price File

w Complete all fields in this file; the Preparation Cost field is optional.
Options

w Negative-priced Menu Items - Type Definition #3

Prices
w Allow Menu Items in This Class to be Non-priced - Type Definition #8
w ON = Use Sub-Menu Level Pricing; OFF = Use Main Level Pricing - Type
Definition #10
w Print Price on Order Chit - Type Definition #13
w Weighed Items - Type Definition #15
w Require Decimal Quantity Entry When Ordering - Type Definition #20
w Add Condiment Price to the Parent Item’s Price on Check Only - Type
Definition #23
w Print Main Menu Level Prefix and Suffix - Type Definition #28
w Print Sub-Menu Level Prefix and Suffix - Type Definition #29

w Print Unit Price as well as Line Total on Checks - Format Option #1
w Display Prices of Menu Items, Discounts, & Service Charges When a Check
Initially Displays - HHT Option #1

w ON = Item Weight in Kilograms; OFF = In Pounds - Option #4
Keyboard File or Touchscreen File

w [@/For] - keycode #600
w [Change Price Main Menu Level] - keycode #638
w [Change Price Sub-Menu Level] - keycode #639
Employee Class File

w Authorize/Use the [Item Weight] key - Transaction Privilege #6
w Use UWS Procedure #13, #17, & #18: Menu Item Assignment - Supervisory
Privilege #14
This UWS procedure may be used to change the price of a menu item.
w Use UWS Procedure #15: Print Menu Item Price List - Supervisory Privilege
P-30
Prices
#16
Related Topics
“@/For Function” on page A-1
“Menu Items” in Chapter 3 of the 9700 Feature Overview Manual

Print Final Tender at Top of Form
Print Final Tender at Top of Form
Description
This feature is intended for use in slip printer environments where, to ease in
manual audit functions, it is desirous to have all payments placed in the same
physical location as the guest check form. When enabled, Operations will prompt
the operator for a continuation form where the final tender information will print,
rather than following the default by round method of appending a guest check.
Enabling

w Print Final Tender at Top of Form - Option Code #41
P-32
Print Groups
Print Groups
Description
A Print Group categorizes menu items so that they are printed together on output
devices, guest checks, and customer receipts.
Usage
Up to eight print groups are used to sort menu items when they are printed. Each
menu item must belong to a print group. Some features of print groups include:
w Sorting by preparation time (longer prep time items first)
w Sorting by meal course (appetizers before entrees)
w Sorting by major groups (food together, liquor together on guest checks)
When menu items are printed, those items with a lower- numbered print group are
printed before items with a higher- numbered print group. (Within print groups,
menu items print in the same order as they are listed in the menu item file.)
A menu item’s print group assignment may be changed using UWS Procedure
#13, Change Menu Item Assignment.
Enabling

w Print Group field
Assign all menu items to print groups (1 - 8) in this field. To disable this
feature, assign all menu items to group 1.
Options

w Condiment Changes Print Group of Parent Menu Item - Type Definition #9
w Sort Condiments by Print Group - Type Definition #30

Print Groups
w Output to Order Dvc #1 - 15 - Output Links #9 through #23

Output may be sorted by print group, by assigned seat number or both. Output
may also be consolidated or unconsolidated.
w Screen Sort Type field
w Customer Receipt Sort Type field
w Guest Check Sort Type field
Order Device File

w Do Not Sort - Sort/Consolidation Type #0
w Sort by Print Group, Consolidated - Sort/Consolidation Type #3
w Sort by Print Group, No Consolidation - Sort/Consolidation Type #4
w Sort by Seat and then by Print Group, Consolidate Identical Items - Sort/
Consolidation Type #5
w Sort by Seat and then by Print Group, No Consolidation - Sort/Consolidation

Type #6
w Sort by Print Group and then by Seat, Consolidate Identical Items - Sort/
Consolidation Type #7
w Sort by Print Group and then by Seat, No Consolidation - Sort/Consolidation

Type #8
P-34
Printers
Printers
Description
A printer is a hardware component that prints certain reports and receipts. The
types of printers used by the 9700 User Workstations to print guest checks or
customer receipts include:
w Roll printers (modular-integrated, stand-alone, and autocut)
w Slip printers (modular-integrated or stand-alone)
w Thermal printers (standalone only)
Standard line printers and laser printers may also be used to print reports from the
PC.
Usage
Roll Printers
Roll printers print on continuous-feed paper rolls. They are usually used for:
w Customer receipts
w Time chits
w Validation chits
w Dopplebon dupes
w Local order receipts
w Remote order receipts
w Credit card vouchers
w Backup printing
w UWS reports
w Journal entries

Printers
w Memo checks and Seat checks
Stand-alone roll printers may be equipped with a take-up reel for journal printing.
Slip Printers
Slip printers print individual pieces of paper, usually card stock. They are usually
used for:
w Guest checks
w Time cards
w Endorsement lines for personal checks
w Credit card vouchers
Stand-alone slip printers may be programmed to eject the slip after printing.
Slip printers may be programmed to skip down several lines before beginning
print. This allows restaurants to use guest checks that have their logo, address, etc.
preprinted at the top of the card.
Many restaurant guest checks include a tear-off bottom section that functions as
the customer’s receipt. The number of available lines for each slip may be
programmed for slip printers, to prevent printing on this detachable portion of the
check.
Thermal Printers
Thermal printers offer a faster and quieter variation on the standard, impact-
printing roll printer.
Line Printers
Line printers, such as laser printers or dot-matrix printers, may be connected to the
PC to print 80-column or 120-column reports, using the 9700 System’s Report
Writer or Autosequencer modules.
Up to four line printers may be configured for each PC in the System. Printer
Setup String and Parameter fields are provided for each printer.
If a PC is connected to more than one line printer, include a destination command
in the Line Printer Parameters field, in the format:
-d <printername> <parameters>
where:
-d is the UNIX syntax indicating that this print job is intended for a specific
destination.
P-36
Printers
w <printername> is the name assigned to each printer when it was

installed. (To display a list of the names of printers installed at a PC, enter
lpstat -t at the UNIX prompt.)
w <parameters> are any special instructions required for this printer, as

specified in the printer’s documentation.

Printers
Enabling
Device Table
w Complete all fields in this file.
Workstation Table
w For each printer, complete all fields in this file.
Order Device File

w Complete all fields in this file for remote and local printers.
Options
PC Table
w Report Printer Setup String fields (1 - 4)
w Line Printer Parameters fields (1 - 4)
w Keyboard Overlay Line Printer Parameters
w Lines per Report Page
Report Configuration File

The following fields can also be programmed for the Income Audit Report
Configuration. The values programmed in this file take effect when this report is
run, and they revert back to the values programmed for the System in the PC
Table when this report is finished printing.
w Report Printer Setup String fields (1 - 4), Income Audit Report Configuration
w Line Printer Parameters fields (1 - 4), Income Audit Report Configuration

w Partial Cut Between Pages and Full Cut Between UWS Reports - Report
Writer/UWS Reports Option #16
This option is used only for autocut roll printers.
Currency File
w ON = Print Currency Symbol after Numeral; OFF = Print Before - Base
Currency Option #1
P-38
Printers

w Line Feeds Before Order Output Header field
w Lines on First Guest Check Page field
w Line Feeds Before First Guest Check Page field
w Lines on Other Guest Check Pages field
w Line Feeds Before Other Guest Check Pages field
w Lines on Time Card field
w Line Feeds Before Time Card Header field
w Lines per User Workstation Report Page field
w Minimum Number Lines Per Roll Check/Receipt field
w Automatic Retry if Printer Busy - For Testing Only - Option #21
w Print Checks & Receipts Unsupervised if on Roll Printer - Option #22
w Partial Cut Between Customer Receipts (Autocut Printers Only) - Format

Option #20
Related Topics
“Printers” in Chapter 1 of the 9700 Feature Overview Manual

Print Two Guest Checks
Print Two Guest Checks
Description
This feature will print two copies of either a guest check or a customer receipt. It
will work with either a tender or service total key. The two checks may either print
out automatically, or the operator may be prompted to print the second check.
This feature also applies to the Adjust Closed Check and Reopen Closed Check
functions and Fast Transactions. The Operator may be either On-Demand or By-
Round.
This feature does not apply to Memo Checks.
Enabling
Tender/Media File
w Print 2 Guest Checks/Receipts - Type Definition #62. (Revenue Center
Format Option #36 must also be enabled)
w Prompt for 2 Guest Checks/Receipts - Type Definition #63 (Optional)
Revenue Center Parameter File

w Allow Tmed to Print 2 Guest Checks/Receipts - Format Option #36
P-40
R
Reference Entry
Description
In the 9700 System, a Reference Entry is a string of numbers or characters that
can be required to be entered with a transaction entry. Reference entries print and
display with the item entered as additional information. Reference entries print on
guest checks, customer receipts, remote printers, and journal printers.
Usage
A reference entry may be used to add an employee number, coupon number or
name to a transaction entry to provide greater control and audit capability. A
reference entry also is used to record credit card numbers for credit card tendering
keys. In addition, PMS posting uses [Tender/Media] reference entries for room
numbers or other account number postings.
Menu Items, Discounts, Service Charges, Tender/Media, and Tax Exemptions,
can all be programmed to prompt the user to enter a reference entry.
If a Tax Exemption is programmed to require a reference entry, the entry is
prepended with “TAX #:”.
9700 HMS A to Z Feature Reference Manual R-1

Reference Entry
Example
An establishment accepts numbered discount coupons, and a discount key called
[Coupon] is programmed in the system. The establishment also wants to have an
audit trail for coupon use, therefore, the [Coupon] discount key is programmed to
require a reference entry.
When the [Coupon] key is used, the operator is prompted to “Enter Coupon Info”,
where “Coupon” is the name assigned to the key used.
The operator enters the number of the coupon. The reference entry prints with the
detail entry on the guest check.
1 CALL COCKTAIL 3.00

1 IMPORT DRAFT 2.25
BALANCE DUE 5.25
TATTLER AD 9/25/93
1 COUPON -0.50
Reference
Entry
Reports
Reference entries for [Tender/Media] keys print on the Closed Check Report.
Enabling
1 Interfaces

R Use 19-Digit Reference Entry for PMS Inquiries

R Require a Reference Entry with Tax Exemptions
R-2
Reference Entry

R Require Reference Number Entry with Price Override
2 RVC Information | RVC Parameters | HHT

R Use Numeric Screen for Reference Entry with [Credit Card Store] Key
1 Menu Item Class
1 Discounts

1 Service Charges
2 System Information | Service Charge | <Select Service Charge> | General

1 Tender Media

Key Type | Category to Display=POS Ops Behaviors
R Use Numeric Screen for Reference Numbers on HHT—This feature is
provided for the HHT due to the small size of the unit’s touchscreen.
On the HHT, the Numeric touchscreen contains larger keys than the
Alphanumeric touchscreen, which must use smaller keys in order to
include the alphabet characters. The numerals-only Numeric
touchscreen is often easier to use when entering numerals, such as a
credit card account number.

Key Type | Category to Display=Credit Card Options
R PMS or Credit Card Reference Entry field

Reference Entry
1 Keyboards, WS Touchscreens, or EHT

Touchscreens
2 Touchscrns & Keyboards | WS Touchscreens
2 Touchscrns & Keyboards | EHT Touchscreens
2 Touchscrns & Keyboards | Keyboards

R Alphanumeric characters must be available at the UWS and HHT when
the System prompts for a reference entry.
R-4
Remote Database Maintenance
Description
Remote Database Maintenance allows support personnel at a remote location
(i.e., the dealership or technical support center) to perform System maintenance,
including:
w Remote login
w File Transfer
w Running remote X-Window applications, including the 9700 HMS (e.g.,

System Configurator), on the local display.
A remote location can be any PC connected to the 9700 System LAN (physically
or by modem). The remote PC does not need any 9700 System Software installed.
Usage
This feature is useful if a single office or person is responsible for maintaining the
databases in several separate systems. A large company can have a single
technical support center for many sites, minimizing the need for technicians to
travel to sites.
Enabling
XVision: Windows
XVision, and its companion program, XRemote, may be used to support a remote
9700 System from a PC running Microsoft Windows 3.1 or later.

Related Topics
w The 9700 X Server Installation Guide describes XVision.
R-6
Re-open Closed Check
Description
The Re-open Closed Check feature allows a privileged employee to make
changes to a closed (tendered) check.
Usage
The [Re-open Closed Check] key allows a closed check to be opened and assigned
a new check number. Payments, menu items, discounts, and service charges may
then be added or removed. If there was change due when the check was closed,
the last tender entry must be removed (voided) before any other changes are made
to the check.
Once re-opened, the check may be service totalled and kept open for further
transaction posting. The tender posting that originally closed the check must be
voided before the check can be service totalled.
To add a check to a re-opened check, you must service total the re-opened check,
and pick it up again.
When a check is re-opened, the state of the autogratuity (ON or OFF) is returned
to its setting at the time the check was closed. For example, if autogratuity was
ON when the check was closed, but is now OFF, it is turned back ON when the
check is re-opened, and remains ON for that check until it is service totalled,
transferred, or closed.
When the re-opened check is closed again, a new check number is issued, or the
Revenue Center may be programmed to allow the check to retain its original
check number.
Example
A guest check is closed with a tendering key. The customer then decides that he
will have that piece of pie for dessert after all. The server presses the [Re-open
Closed Check] key. The UWS prompts for the check number, which the server
enters. The check is reopened. The server enters the pie and tenders the check to
close it for (probably) the last time.

Reports

This report prints a “j” next to any check that was re-opened.
Enabling

R 423 - Re-open Closed Check

R Allow Changes to Menu Items on Closed Checks—Enable this
option to allow existing menu items to be changed (i.e., voided,
returned, etc.)
R Allow Service Total of Closed Checks—Enable this option to allow
closed checks to be re-opened.
Optional Settings

R Keep the Same Check Number When a Check is Reopened

R-8
1 Employee Class

Printing | Check/Receipt
R Authorize/Perform Reprinting of Closed Guest Check


Voids & Returns
R Authorize/Perform Void of Menu Items on a Closed Check
R Authorize/Perform Void of Discounts on a Closed Check
R Authorize/Perform Void of Service Charges on a Closed Check
Related Topics
w “Adjust Closed Check” on page A-10

Repeat Round Function
Description
This feature allows a server to re-order those menu items from the previous
service round that are enabled for use with the [Repeat Round] key.
Usage
Repeat round is intended for use in situations where customers may want to order
the same set of items in another round. The best example of this is a group of four
customers in a cocktail lounge who tell the server, “We’ll have another round.”
The server picks up their guest check and presses the [Repeat Round] key.
A menu item must be specifically enabled for use with the [Repeat Round] key.
Continuing the example above, in addition to their drinks, the guests ordered the
nachos, chicken wings, and two bowls of chili. When they later tell the server,
“We’ll have another round”, they obviously mean only another round of drinks.
For this reason, food items in the lounge are not enabled for use with the [Repeat
Round] key.
When the server picks up the check, the transaction display on the UWS shows a
less-than mark (<) on the line of all items that may be re-ordered, using the
[Repeat Round] key. An asterisk (*) appears on the line of all items that are not
programmed to respond to the [Repeat Round] key.
Quantity
Line Price
Number Menu Item
1
2
1 Nachos
1 Chicken Wings
4.50
5.25 ** Will not respond
to [Repeat Round]
3
4
2 Bowl Chili
1 Martini
7.50
4.25 *< Will be ordered again
5 2 Domestic Draft 5.00 < if [Repeat Round]
6 1 Bourbon 3.75 < is pressed
When the server presses the [Repeat Round] key, only the drinks, not the food,
from the previous round are repeated.1
1. Menu Items that were removed from the check via the line item void procedure will not be included in
repeat round detail.
R-10
Establishment prices may change from time to time, such as changing to and from
Happy Hour pricing. If a price change takes effect between a previous round and a
current round, the establishment can force repeat rounds to take effect with the
current main and/or sub-menu levels or with the previous round main and/or sub-
menu levels by selecting the appropriate Menu Item Class Type Definition
options.
The [Repeat Round] key cannot be used for weighed

menu items or menu items that are programmed to
require a decimal amount entry. You cannot re-open
a check and press [Repeat Round] to re-order the
last round on the check.
Enabling


R 606 - Repeat Round
1 Menu Item Class
R Use With [Repeat Round] key—Select this option to enable each menu
item to repeat last round.
R Keep Main Menu Levels With Repeat Rounds
R Keep Sub-Menu Levels With Repeat Rounds

Report Groups
Report Groups
Description
A Report Group provides a means of subtotalling and sorting items on a report.
It also provides a means of selecting items to include in a report. The following
items can be assigned a report group number:
w Major Groups (99 report groups available)
w Family Groups (99)
w Menu Items (8)
w Job Codes (255)
w Employees (300)
Usage
Items assigned the report group number 0 do not appear on reports. However, any
totals associated with the item are included in the report totals. For example, you
may want to assign unpriced menu item condiments (e.g., “RARE”) to Report
Group #0 to avoid cluttering menu item reports with condiments.
Reports that include more than one report group sort in order of report group
number. That is, all items assigned to Report Group #1 are listed and subtotalled
before items assigned to Report Group #2.
Enabling
1 Major/Family Groups

<Select Major/Family Group> | General
R Report Group field
R-12
Report Groups
1 Job Codes

R Report Group field

Report Writer
Report Writer
Description
Report Writer is one of the main modules of the 9700 System Software. It can be
run independently of the System Configurator module or the POS Operations
module.
Report Writer is used to instruct the 9700 System to prepare a specific report.
Reports can be run automatically using the 9700 Autosequence features. See
“Autosequences” on page A-26.
Usage
When Report Writer is run and a report selected, a report options window
displays. Report options available include:
w Select a totals set from which to take the report.
w Select whether or not to reset the totals.
w Assign the report a name for reports printed to disk.
w Define an output destination: display, one of four printers, or file.
w Select the scope of the report: System or Revenue Center.
w Define the range of items to include, in applicable reports.
w Decide whether or not to omit items with zero totals.
R-14
Report Writer
Enabling
1 Devices
2 System Hardware | Devices | <Select Server PC> | General | Printer

Settings
The following three fields are used to enter settings that may be required
by some line printers:
R Rpt Printer Setup String fields
R Line Printer Parameters fields
R Lines/Report Page
Optional Settings
1 System Parameters

R Canadian GST: Combine Rates 2 through 8 on System Tax Report
R Omit Sum Sections and Ttl Lines from RW and UWS Time Pd Reports
R Enable French VAT Reporting
R Do Not Print Grand Total and Change in Grand Total Fields
R Do Not Print Table Section On Financial Rpts
R Do Not Print Tracking Group Names on Financial Rpts
R Do Not Print Order Type Breakdown On Financial Rpts
R No Form Feeds Between Employees on Empl Rpts Except Financial
R Do Not Print Separator Line Before Tracking Section in Rpts
R No Form Feeds Between Employees on Employee Financial Rpts
R Partial Cut Between Pages and Full Cut Between UWS Rpts

Report Writer
1 Employees
2 Personnel | Employee Maintenance | Sort By Employees | <Select

R Do Not Print Tracking Totals in Employee Financial Reports
1 Employee Class
2 Personnel | Employee Maintenance | Sort By Employee Class | <Select

Employee Class> | Privileges | Privilege Levels
R Report Writer Access Level—The Access Level programmed for
each Employee Class determines whether or not those employees are
able to take certain reports, reset reports, and reset reports without
printing.
Related Topics
w “Access Level Required by Report Writer” in Chapter 10 of the 9700 Feature
Overview Manual
w “Printers” on page P-35
R-16
Reprint Check
Reprint Check
Description
To Reprint a Check is to print a check in its entirety.
Usage
This feature is accessed through a tender/media key programmed to reprint a
check.
The reprint check function does not allow you to reprint a closed check. But if you
are privileged to open a closed check, then you can reprint it.
A By-round operator will find the reprinted check has consolidated and sorted
entries from the previous rounds according to the programming of the print groups
which the previous By-round printing of the check does not.
The main use of the reprint check feature is to allow an employee to replace a
check that has been damaged or misplaced.
Check Copy Number

The total number of times that a reprinted check has been printed appears on the
guest check.
By-Round
If the REPRINTED CHECK header is programmed to print on guest checks
in this Revenue Center, the total number of times the check has been printed is
included on the reprint line.
MICROS 9700
Fine Dining System
411 MARY
--------------------------------
JAN14’94 3:30PM
* * * REPRINT 3 * *
--------------------------------
Check copy number

Reprint Check
On-Demand
For On-demand guest checks, the number of times the check has been printed
appears on the line with operator’s name and Employee Number. This field is
used to print page numbers (when checks are programmed to print on multiple
pages), but the page number is never printed for page 1.
MICROS 9700
Fine Dining System
411 MARY 3
--------------------------------
JAN14’94 1:30PM
-------------------------------- Check copy number
Reports
Closed Check Report

The number of times a check is printed appears in the Print Count field.
Enabling
2 Touchscrns & Keyboards | WS Touchscreens | Touchscreen Screen | Type

Keyboard> | Key Configuration | Type
R Tender/Media key - (service total or payment)
1 Tender Media

R Reprint Checks
R-18
Reprint Check

R Print “REPRINTED CHECK” Header
Optional Settings

R Number Checks Printed Before Authorization field
1 Tender Media

R Privilege Group field
1 Employee Class

Printing
R Authorize Unlimited Reprinting/Printing of a Check—Authorize
printing a check more than the maximum number of times specified in
the Revenue Center Parameters File.\Authorize/Perform Post Of
Tender/Media In Privilege Groups 1, 2, 3.

Return Items
Return Items
Description
A Returned menu item is one that is prepared and then rejected by the customer
or, for some other reason, it is not delivered to the customer. A menu item that is
ordered but not prepared can be voided from the customer’s check. A return is
treated as a different action than a void because inventory and preparation costs
are incurred when a menu item is prepared but not consumed or paid for.
A return is performed using a [Return] key programmed on the keyboard or
touchscreen. The return is posted to the check as a negative amount to reduce the
check total.
Usage
The return feature is used when an item has been prepared but will not be charged
to the customer or consumed by the customer.
If you are going to let the customer consume the

item but not charge for it, you should set up a
House Account tendering key or a 100% item
discount key
R-20
Return Items
Example
A customer ordered Cream of Broccoli Soup which was prepared and delivered,
then rejected by the customer as too watery. Naturally, the soup is returned. The
server uses the [Return] key to post the Cream of Broccoli Soup as a negative item
on the check. The resulting check detail will look like this.
1 DUCK A L’ORANGE 13.95

1 BROCCOLI SOUP 2.75
1 HOUSE SALAD 1.00
SUBTOTAL 17.70
SALES TAX (6%) 1.06
BALANCE DUE 18.76
1 BROCCOLI SOUP 2.75- R

SUBTOTAL 14.95
SALES TAX (6%) .90
BALANCE DUE 15.85
Reports
Financial Reports (System, Revenue Center, and

Employee)
w The Returns field tracks the number and dollar amount of returns for the
report period.
Income Audit Report

w The flexible format of this report can be programmed to include Returns.

Return Items
Enabling


R 604 - Return
Optional Settings

R Validation Required for Menu Item Returns


R 642 - Transaction Return
1 Employee Class

Voids & Returns
R Authorize/Perform Void and Return of MI Not on Check
R Authorize/Perform Return of MI Entered on the Current Check
R-22
Return Items
Related Topics
w “Void Item” on page V-18

Revenue Centers
Revenue Centers
Description
Revenue Centers are defined within a system for sales tracking and accounting.
Usually, a Revenue Center matches an outlet in the establishment, such as a bar,
restaurant, or retail outlet.
Usage
Revenue Centers serve three general purposes:
w To provide accounting information for outlets in the system, as a subset of the
system.
w To control or restrict operator access.
w To define functional characteristics for the outlet.
UWS Assignment
The Revenue Center on which a UWS is active may be determined in one of two
ways:
w The UWS is “dedicated”, that is, programmed to operate in only one specific
Revenue Center.
w The UWS is “open”, that is, programmed to allow an operator to select from a
list of active Revenue Centers. (If this method is used, and cashiers are
assigned by UWS, cashier totals must exist in a Revenue Center in order for
operators from that Revenue Center to sign in to the UWS.
A dedicated UWS has only one Revenue Center link programmed in its record in
the Workstation File in System Configurator. An open UWS has several Revenue
Center links.
R-24
Revenue Centers
To sign in on a UWS, the operator’s Revenue Center link in the Employee File
must match a Revenue Center in the UWS.
Yes
1. Bar Employee File 1. Dining

Rev Cntr Link: 2. Bar
1. Bar
No
1. Dining 1. Dining
2. Room Svc
Revenue Center Operations

An operator must be privileged in order to change Revenue Centers. To post
transactions, an operator must have operator totals in the sign-in Revenue Center.
Signing In To a Specific Revenue Center

A privileged operator may press a [Sign in to UWS RVC #] key to sign in to
any of the eight Revenue Centers listed in the UWS Table.
If the operator is currently assigned to another Revenue Center, the System
prompts, “Change to <Revenue Center Name>?”. The operator must confirm
or cancel the change. If the Time and Attendance features are in use, the
System clocks the operator out of the original Revenue Center and clocks in
to the new Revenue Center.
Changing to Another Revenue Center

An operator who is signed in to a UWS may change to a different Revenue
Center without having to sign out and then sign back in.
The operator may press a [Change Transaction Revenue Center] key to
change to one of the eight Revenue Centers listed in the UWS Table, or the
System may be programmed to prompt for one of the eight Revenue Centers.
Operators who change to another Revenue Center may perform any operation
for which they are privileged, including guest check operations.
Revenue Center programming determines whether a staydown operator who
uses a [Change Transaction Revenue Center] key returns automatically to
their original Revenue Center at the end of the next service round, or remains
in the new Revenue Center. This Option does not affect pop-up operators. A
pop-up operator is automatically signed off at the end of a service round or
transaction. When a pop-up operator signs back in, the System defaults to
their original Revenue Center.

Revenue Centers
Picking Up Checks in Another Revenue Center

An operator who is signed in to a UWS may pick up checks in another
Revenue Center without having to change to that Revenue Center.
The operator may press a [Pickup Check] key to pick up checks (by check
number or table number) in one of the eight Revenue Centers listed in the
UWS Table, or the System may be programmed to prompt for one of the eight
Revenue Centers.
Operators who simply pick up a check (as opposed to changing Revenue
Centers) remain in their original Revenue Center at the end of the service
round.
UWS Download
An operator may load a UWS with the database from any Revenue Center on
the PC to which this UWS is connected, even if that Revenue Center is not
one of the eight listed in the UWS Table.
The operator may press the [UWS Download] key to change the first entry in
the UWS’ list of available Revenue Centers. The System prompts, “Select
new Revenue Center”, and displays a list of the Revenue Centers programmed
for the System. This allows the UWS access to all Revenue Centers on this
PC, beyond the eight that are listed in the UWS Table.
This feature may be used in a situation in which a master cashier station must
be able to perform transactions (e.g., check adjustments or tips paid
operations) in any Revenue Center.
In the case of a large Revenue Center database, the UWS may take several
minutes to download all of the files. One of the largest of these files is
typically the Menu Item Definition File. In cases where speed is a
consideration, and the Menu Item Definitions do not need to be changed (i.e.,
Menu Items are not needed for the intended operation), the operator may elect
to use the [UWS Download, No Menu Item] key.
This key loads the entire Revenue Center database, except for the Menu Item
Definition File. As a result, the time required for the download is significantly
reduced. Since the Menu Item Definition File houses the Menu Item SLU
links, Menu Item SLUs are not available when using this key. Menu Items are
available, however, if listed on an NLU key, or if the Menu Items are
programmed on touchscreens as separate keys.
If the size of the database to be downloaded exceeds the available memory in
the UWS, the message Database will not fit in UWS memory appears on the
UWS display, and a message posts to the Error Log module.
R-26
Revenue Centers
HHT Download
A privileged operator may load an HHT with the database from any Revenue
Center on the PC to which the HHT’s Base Station is connected.
When an operator presses the [Load HHT Database] key, the HHT prompts
“Select new Revenue Center”, and displays a list of the Revenue Centers
programmed for the PC.
Downloading an HHT database takes significantly longer than performing the
same operation on a UWS, due to the fact that the data is transmitted first
from the PC to the Base Station, and then from the Base Station to the HHT.
Shared Definition Files

Revenue Centers may be programmed to share a set of seven definitions files.
This allows a UWS to be shared by several Revenue Centers. It also saves space
on the PC’s hard disk, since the files are stored only once. It also speeds database
maintenance, since changes are made in only one place. The set of shared
definitions files consists of:
w Menu Item Class File
w Menu Item Definition File
w Menu Item Price File
w Touchscreen Assignment File
w Touchscreen Screen File
w Touchscreen Style File
w Keyboard File

Revenue Centers
Revenue Center Revenue Center Revenue Center

#1 #2 #3
Parent Child Child
Parameters Parameters Parameters

Descriptor Descriptor Descriptor
Operator Operator Operator
Cashier Cashier Cashier
Time Period Time Period Time Period
Serving Period Serving Period Serving Period
Table Table Table
Order Device Order Device Order Device
Macro Macro Macro
MI Class
MI Definition
MI Price
TScrn Assign
TScrn Scrn
TScrn Style
Keyboard These seven files are not programmed
for these two Revenue Centers. They
share the definitions files programmed
in the first Revenue Center.
Parent Revenue Centers may not be deleted from the database if they have
dependent children. In the illustration above, for example, the System will not
allow Revenue Center #1 to be deleted from the database, because Revenue
Centers #2 and #3 are child Revenue Centers that depend on #1.
Reports
The following Revenue Center reports are available:
w Revenue Center Tax Summary
w Revenue Center Tip Report
All other Revenue Center reports may be run except for the following:
w Employee Labor Reports (Detail and Summary)
w Employee Open LDS Report
R-28
Revenue Centers
When Operators Work in More Than One Revenue

Center
Sales Totals
Financial totals post to the Revenue Center in which they take place. Guest
Check totals post to the Revenue Center in which the check was begun, unless
the check is transferred to another Revenue Center.
If an operator posts totals to more than one Revenue Center, the Employee
Financial Report must be taken for a System view in order to give a complete
accounting of that person’s activity.
Labor Totals
When an operator uses a [Change Transaction Revenue Center] key or picks
up checks in another Revenue Center, labor totals continue to accrue to the
Revenue Center to which that operator first signed in.
If an operator who is already signed in uses a [Sign in to UWS RVC #] key to
sign in to a different Revenue Center, the System clocks the operator out of
the original Revenue Center and clocks in to the new Revenue Center.
Since Employee Labor Reports are only available for a System view, they will
give a full accounting of that person’s time.
Enabling
2 RVC Information | RVC Configuration

R A Revenue Center is defined on the system level with a Revenue
Center Number, Revenue Center Name, and the specific PCs that will
support sales activity in that Revenue Center. Shared Revenue Centers
are specified in this file.
1 Devices
2 System Hardware | Devices | <Select Workstation> | Revenue Centers

R Revenue Center link fields 1 - 8
2 System Hardware | Devices | <Select Workstation> | Options

R Link Cashier Totals to UWS—If this option is disabled, cashier totals
will be linked to the Operator.

Revenue Centers
1 Employees
2 Personnel | Employee Maintenance | Sort By Employees | General

R Current RVC field
2 RVC Information | RVC Parameters

The operational characteristics of each Revenue Center are defined in the
Revenue Center Parameters file.
Optional Settings
1 System Parameters

R Prompt Operator to Confirm Loading a New RVC to the
HHT
2 RVC Information | RVC Parameters

R Staydown Operators Return to Original Revenue Center after [Change
Transaction Revenue Center] Keys - Option #5
1 Menu Item Class
R Do Not Download to HHT
1 Cashiers
2 Personnel | Cashiers | General

R If cashier totals are linked to a Workstation instead of to Operators, the
cashier number must exist in a Revenue Center in order for operators
from that Revenue Center to sign in to that UWS.
R-30
Revenue Centers


R [Pickup Check, Check #, Rvc ?] - keycode #403
R [Pickup Check, Check #, Rvc 1] - keycode #404
through
R [Pickup Check, Check #, Rvc 8] - keycode #411
R [Pickup Check, Table #, Rvc ?] - keycode #413
R [Pickup Check, Table #, Rvc 1] - keycode #414
through
R [Pickup Check, Table #, Rvc 8] - keycode #421
R [Chg Trn Rvc, Rvc?] - keycode #424
R [Chg Trn Rvc, Rvc 1] - keycode #425
through
R [Chg Trn Rvc, Rvc 8] - keycode #432


R [Sign In UWS Rvc 1] - keycode #305
through
R [Sign In UWS Rvc 8] - keycode #312

Revenue Centers

Categories=Non-Sales Operations | Link

Number
R [UWS Download] - keycode #846
R [UWS Download, No MI] - keycode #847

R No Change in Revenue Center without Operator Totals
1 Employee Class

Guest Checks
R Allow Pickup of Checks in Other Revenue Centers

Options
R Download Database to an HHT
R Authorize/Perform UWS Download New Revenue Center

General | Transaction Sign In
R Change Revenue Centers
R Authorize Changing Revenue Centers
Related Topics
w “Shared Definition Files” on page S-33
w “Types of Database Files” in Chapter 4 of the 9700 Feature Overview Manual
R-32
Round Balance Due (Finnish Rounding)
Description
Finnish Rounding forces the balance due on a transaction to be rounded up or
down to the nearest 5 or 10 to meet the requirements of currencies that do not have
unit denominations; that is, the smallest unit of currency is 5 or 10, not 1.
This feature is often referred to as Finnish Rounding since it was originally
developed for applications in the Republic of Finland.
When this feature is active, financial reports will still reflect actual sales totals, but
will include an additional line, “ROUNDING TTL”, to account for the difference
between the Change in Grand Total (revenues) and the total of Checks Begun/
Paid (receipts) caused by the rounding. Because rounding options can result in
rounding up or down, the “ROUNDING TOTAL” field may be positive or
negative.
Usage
Use this feature when the smallest unit of base currency is 5 or 10. This feature
may be implemented for the base currency and/or for any alternate currencies
used.
Reports
A “Rounding Total” field prints on all Financial Reports (i.e., System, Revenue
Center, Employee, and Serving Period) when this feature is used. This figure can
be either positive or negative. It represents the difference between the Total
Revenue field and the Change In Grand Total field. Total Revenue records the
rounded amount that was posted to the guest check. Change In Grand Total
records the actual sale price of all the menu items sold.

Enabling
1 Currency

R Enable Amount Due Rounding—This option must be enabled.
Optional Settings
1 Currency File

R Round Amount Due To field—Select Nearest 10 to round to the
nearest 0 or 10, or Nearest 0 to round to the nearest 0, 5, or 10.
R Round Amount Due On field—Select 10s Digit to round the amount
due on the 10s digit, or Units to round amount due on the units digit.

R Enable Amount Due Rounding field
R Round Amount Due To field—Select Nearest 10 to round to the
nearest 0 or 10, or Nearest 0 to round to the nearest 0, 5, or 10.
R Round Amount Due On field—Select 10s Digit to round the amount
due on the 10s digit, or Units to round amount due on the units digit.
R-34
Example
The effects of the combinations of the possible rounding options are shown in this
table.
If Option #4
If Option #3 2.53 2.47 2.62 2.32
(Round to
(Round to 0, rounds rounds rounds rounds
units or tens
5, or 10) is: off to: off to: off to: off to:
digit) is:
OFF OFF 2.55 2.45 2.60 2.30

ON OFF 2.50 2.50 2.60 2.30
OFF ON 2.50 2.50 2.50 2.50
ON ON 3.00 2.00 3.00 2.00
Related Topics
w “Currency” on page C-45

Round Tender to Next Highest Dollar
Round Tender to Next Highest Dollar
Description
When used in conjunction with Tender/Media Type Definition #3 (Assume Paid
in Full), a tender key with this feature enabled will tender the transaction to the
next highest dollar above the total amount due if no amount is entered prior to
pressing the tender key.
For example, if the total due is $9.35 the transaction will be tendered for $10.00.
This feature is overridden by the Open Check Block Settlement feature.
This feature will not work with currencies which do

not use a decimal place, or if Tender/Media Type
Definition #3 is not enabled.
Enabling
1 Tender Media

Category to Display=POS Ops Behaviors | Ops Behaviors
R Round Tender to Next Highest Dollar
R-36
S
Sales Itemizers
Description
Sales Itemizers are the 16 categories of sales which print as subtotals on the guest
check. For example, you could group sales into Food, Liquor, and Merchandise.
For a complete discussion of Sales Itemizers see, “Itemizers” on page I-1.
9700 HMS A to Z Feature Reference Manual S-1

Scale Interface
Scale Interface
Description
The 9700 System supports a scale interface for the UWS/2 and UWS/3, for use
with menu items that are priced by weight. Refer to “Weighed Menu Items” on
page WXYZ-1.
S-2
Screen Display Features
Description
The User Workstation Screen Display displays transaction information during
POS Operations. The same screen format is used by the UWS/1 and UWS/2. The
UWS/3 has a slightly different format which provides the same information.
This illustration shows the screen display format for UWS/ 1 and UWS/2.
Employee Check Name

Employee Last Name
Service Total Marker
Transaction Line #
Transaction Detail
Message Prompt
Last Entry Line

Current Entry
Seat Number
Main Level
Sub Level
Flag Field
Quantity
Price
1 1 Fried Cheese 2.95 1 * Lunch Medium Jones

2 1 Bread Sticks 1.50 2 *
3 1 Glass Rose 3.00 1 * Press [CLEAR] To Continue
4 1 Iced Tea .75 2 *
5 1 Spiced Shrimp 7.95 1 *
6 1 New York Strip 9.95 2 *
7 10.00&
8 1 Dinner Discount 2.61-
9 Charge Tip 4.50
10 5291019359329194 1002 Tom
11 Visa/MC 29.16
12 CHK 1234 TBL 1/1 Cov 2
13 JUL29’92 2:51PM
14
15 Subtotal 23.49
16 Tax 1.17
17 Service Charge 4.50
18 Amount Tender 29.16
19
20
21 Eat In TTL 29.16
22
Dinner Keyboard Dining Room Happy Hour Bar PreChk

Transaction Summary
Check Information
Revenue Center
Keyboard Name
UWS Name
Order Type
Serving
Period
Name
Name

S-4
Transaction Line #
Quantity
Transaction Detail Last Entry Line

Keyboard.
Touchscreen Keys
Price
Check Information
Transaction Summary
Seat Number
*
*
Service Total Marker
Order Type
Prompt Lines
Employee Check Name
Main & Sub Levels

The LCD display splits the screen into two sections; Operator Display and
Employee Last Name

This illustration shows the screen display format for the PCWS and the UWS/3.
The operator display (top half of the screen) is used to provide guest check
transaction detail and summary information. The Keyboard (lower portion of the
screen) is used to enter information and perform System functions.
About the Operator Display

The Operator Display section contains two separate areas of information—
Transaction Detail and Summary Information. Optionally, the Operator Display
can be touch sensitive by activating TouchAdvantage.
TouchAdvantage changes the traditional look of the Operator Display by adding
Scroll Buttons. These buttons allow the operator to scroll Transaction Detail up
and down with the touch of a finger.1 Touch the appropriate detail entry to select,
its as easy as that. When TouchAdvantage is active, the display will look like this:
Transaction
Detail
Operator Display
Transaction Summary
Keyboard
1. For additional information about TouchAdvantage refer to the Encyclopedia section of this manual.

w Transaction Detail—The Transaction Detail portion of the display appears on

the left side of the screen. It contains the same information as the traditional
UWS/1 and UWS/2 displays, but in a graphics format. If TouchAdvantage is
active, scroll buttons are added to the display and line number information is
no longer associated with transaction detail.
w Summary Information—The Summary Information portion of the display

appears on the right side of the screen. It contains the same information as the
traditional UWS/1 and UWS/2 displays, but in a graphics format.
About the Keyboard

The Keyboard (lower half of the screen) is fully programmable with up to 60
keys, varying in key size and legend character size. The smallest size key is
approximately the size of a key on the UWS/2 keyboard, and the largest key can
be the size of the entire touchscreen area. When a key is touched, it is displays in
inverse video.
Regardless of the key sizes, touchscreen keys may be programmed to perform all
functions and operations offered by the traditional keyboards. The real advantage
is that the user only sees the keys he or she needs, or is allowed to use.
For a complete discussion of Touchscreen features, see “UWS Touchscreen” in
Chapter 5 and “Hand-held Touchscreen” in Chapter 12 of the 9700 Feature
Overview Manual.
Screen Display Fields Explained

The screen display provides the operator with information and several prompts
which makes it easy to use the 9700 System. These include the:
Prompt Line
The prompt line describes the type of entry the UWS expects or requires next.
This is also called the operator prompt.
Flag Field
This line displays messages, or flags, to alert the operator to the current
operation, for example, VOID, RETN, TAX XMPT, etc.
Last Entry Line

This information reflects the last entry made.
Current Entry Line

This line shows the current keyboard input prior to recording the information.
S-6
Status Information Fields

This group of fields indicates the current Main and Sub-menu Levels, and
keyboard in use, as well as the name of the active Revenue Center and User
Workstation. This provides the operator and/or manager with information that
is useful when making menu item selections, changing keyboards, and
diagnosing errors. This line also displays the currently active Serving Period.
Check Information Fields

These fields identify the check operator, check number, table number, and
group number for the current guest check. Also, the date and time the check
was begun is shown.
Transaction Summary Fields

This group of fields displays the current sales totals for the guest check. These
figures increment in “real time” after each entry.
Seat Numbers
When used, Seat Numbers display on the same line after each menu item.
Service Total Markers

Menu items which have been ordered in a previous service round are marked
by an asterisk (*). These menu items can only be voided by an operator with
the proper privileges. Menu items which have been ordered in the last service
round and have Type Definition # 25 ON (Use with Repeat Round Key), are
marked by a (<). These menu items can be ordered again simply by pressing
the [Repeat Round] key.
Items remain repeatable until replaced, i.e., until a round of different
repeatable items is ordered.
Screen Save Function

If, after two minutes, a key has not been pressed, the screen automatically
darkens and remains dark until a key is pressed. This feature extends the life
of the screen’s backlight. No information is lost, only the backlight is turned
off. Press the [Shift] key to turn the backlight on without making an entry.
The UWS/3 may be programmed (in Diagnostics/Configuration mode) to
ignore the first keystroke it receives when the backlight is turned off. If this
feature is used, the first keystroke will simply turn the backlight on. Any
subsequent keystrokes will be accepted and acted upon. Refer to the 9700
Hardware Installation Guide (MICROS P/N 100038-093) for a description of
the Diagnostic and Configuration functions of the UWS/3.

Enabling
The screen display is active whenever the system is in POS Operations. If the
POS Operations module is not active, a box displays the message, “System
Closed”.
Options
Help Windows
The operator display can pop-up help windows of additional data (such as
lists of NLU items), superimposed on the basic format. The selections in the
help windows may be programmed to be sorted in numerical or alphabetical
order.
Brightness/Contrast
The brightness control knob for the CRT screen on the UWS/1 is located on
the back, in the lower left corner (as you face the unit). Position yourself at a
normal viewing angle and turn the knob to adjust the brightness of the screen.
The contrast control for the UWS is also located on the back, in the lower left
corner (as you face the unit). Position yourself at a normal viewing angle and
turn the knob to adjust the contrast.
If you have a UWS/3, there are two contrast function keys, which must be
assigned to keyboard locations. These keys adjust the contrast “Up” and
“Down”. Each UWS/3 automatically “remembers” the contrast setting of the
last 20 employees that signed in. Thus, an employee only has to adjust the
contrast once at each UWS/3.
Transaction Descriptors
The labels for each of the sales transaction names (Total, Subtotal, Tax, etc.)
are programmed in the System Descriptor File.
TouchAdvantage
In order to take advantage of the TouchAdvantage feature, set Workstation
Type Definition # 17 (Use Enhanced User Interface) ON.
S-8
Related Topics
w “User Workstation Features” in Chapter 1of the 9700 Feature Overview
Manual

Screen Lookup (SLU)
Screen Lookup (SLU)
Description
A Screen Lookup (SLU) key is similar to a Number Lookup (NLU) key in that it
can give access to any number of items. When an SLU key is pressed, the system
scans the appropriate definition file (discount, service charge, tender/media, menu
item, or guest checks) and generates a Touchscreen key for each item with a
matching SLU number. Using a format defined by instructions in the associated
style, the SLU generates a new Touchscreen.
For a complete discussion of this feature, see the following:
w “About the User Workstation Touchscreen” in Chapter 5 of the 9700 Feature
Overview Manual.
S-10
Seat Handling
Seat Handling
Description
Many restaurants assign Seat Numbers to positions at a table. This way, food can
be delivered to the guest by a food runner without asking the guest to identify their
food. The 9700 allows operators to assign seat numbers as each menu item is
ordered. The seat numbers are then printed on Remote Order Chits to aid in
preparation timing and in assembling orders for delivery.
This feature provides a way to improve order service for groups of guests and to
allow checks to be split and printed for any combination of guests at time of
payment. A single guest check may also be printed that provides the total due for
each guest.
Seat Handling
1 Order Devices

R Print Seat Numbers with Individual Items
1 Keyboards or Touchscreens
2 Touchscrns & Keyboards | WS Touchscreens | Function Key

Categories=Seat
2 Touchscrns & Keyboards | Keyboards | Key Configuration

R [Seat #] - keycode #700—This key is used by the operator when
placing orders, to identify individual guests at a table or on a check.
R [View/Edit Seat] - keycode #701—This key is used to view the guest
check sorted by seat number, or to change or move a seat number’s
menu items to another seat number. For example, if a server
inadvertently orders COFFEE for seat #2 rather than seat #4, the menu
item may be moved to the correct seat number.

Seat Handling
To edit a seat after its detail has been printed, the operator
must be privileged to reprint memo checks.
R [Filter Seat] - keycode #702—This key may be used to display guest

check detail that is comprised solely of the items assigned to a specified
seat or group of seats.
R [Split Check] - keycode #535—This key is used to begin the process
of splitting a check.
If memo check printing is used, a separate tender/media key must be placed on the
keyboard for printing memo checks.
1 HHT Touchscreens
2 Touchscrns & Keyboards | HHT Touchscreens | Touchscreen Screen

The following touchscreen keys are used solely on the HHT:
R [HHT Seat Status] - keycode #382
R [Toggle Seat View] - keycode #383
1 Tender Media

R Key Name—Select 1 - Cash.
R Key Type—Select Payment or Service Total.
2 System Information | Tender Media | Key Type

R Display Options—Select Printing Options.
R Print Memo Checks
1 Operators
2 Personnel | Employee Maintenance | <Sort By Operator> | Options

R Require Seat Number Entry
S-12
Seat Handling
1 RVC Descriptors
2 RVC Information | RVC Descriptors | Category=Seat Number Entry Labels

R Enter the seat number descriptor names, such as SEAT, SHARED,
ALL SEATS.
Optional Settings
Here is a list of all of the possible options that may influence the way the Seat
Handling feature operates. Some of these options may not be compatible with one
another. Before enabling them in your database, refer to the 9700 HMS
Programming Manual for additional information and considerations.
1 Keyboards or Touchscreens
2 Touchscrns & Keyboards | WS Touchscreens | Type=Function | Function

Key Categories=Seat

| Function Key Categories=Seat
R 703 - Change Active Seat—This key performs the same function as
the [Seat #/Next Seat] key, but is reserved for use with Function Look-
up (FLU) keys.1
R 704 - Add Seat To Filter—This key performs the same function as the
[Seat Filter] key, but is reserved for use with FLU keys.
R 705 - Edit Seat, Ask Seat #—This key performs the same edit function
as the [View/Edit Seat] key, but is reserved for use with FLU keys.
1 Menu Item Class
2 Menu Items | Menu Item Maintenance | <Sort By Class> | General

R Increment Seat Number with Sale of These Menu Items
R Prompt for Seat Numbers with Each Menu Item
1. FLU keys function slightly differently than Direct Access keys, in that, the first step (which is to enter a
number) is used to select the FLU key from a pop-up window. The user is then prompted for the seat
number entry. Refer to “Function Look Ups” in Section F of the 9700 A to Z Feature Reference Manual.

Seat Handling
1 RVC Parameters

R Prompt On-Demand Operator to Print Split Check
R Confirmation Required for Seat Number Changes

R Print Trailer Lines on Split Check if On-Demand
R Print “Closed to” Check Number Double Wide on Memo Guest Check

R Assign Seat Numbers to Added Check Detail—This option
determines the seat count status of a check that is added to another
check.
R Keep Seat Numbers on Added Check Detail
R Default Seat Number to 1 at the Beginning Of a Transaction
R Number of Seats may not Exceed Number of Guests—This option
prevents the number of seats from exceeding the number of guests.
2 RVC Information | RVC Parameters | Options | HHT Options

R Display of Seats in Transaction Detail Display
R Display Seats on Initial Callup of Transaction Detail Display
1 Discounts
2 System Information | Discounts | General | Type Definitions

R Affects Auto Service Charge (Only for Subtotal Discounts)—If a
percentage subtotal discount is applied while the seat filter is active, the
discount will not affect the automatic service charge regardless of the
setting of this option.
S-14
Seat Handling
R Treat Percentage Discount as an Amount Discount When

Calculating Taxes—This option is intended to improve the accuracy
of tax calculation in situations where:
w there is a need to apply a percentage subtotal discount to a filtered
seat or group of seats,
w the transaction detail may potentially include items with different

tax classes, or taxable and non-taxable items,
w you wish to continue the transaction without being required to

immediately memo tender the filtered seat(s).
R Do Not Allow Subtotal Discount While Seat Filter is Active—The

discount reset itemizer has no effect on subtotal discounts when seat
filtering is active, allowing subtotal discounts to be posted more than
once. To prevent this situation, disable this option.
1 Tender Media
2 System Information | Tender Media | Key Type=Payment | Printing

R Print Memo Checks (Payment and Service Total key types only)
R Print Seat Checks (Service Total key types only).
R Increment Active Seat # After Memo Or Seat Check Print
(Payment and Service Total key types only)—This option increments
the active seat number every time a memo check or seat check is
printed, allowing all memo checks or seat checks for a guest check to
be printed in succession.
1 Order Devices
2 System Hardware | Order Devices | General | Sort | Consolidation Method

R Do Not Sort
R 1 - Seat, Consolidated
R 2 - Seat, No Consolidation
R 5 - Seat & Print Group, Consolidated
R 6 - Seat & Print Group, No Consolidation
R 7 - Print Group & Seat
R 8 - Print Group & Seat, No Consolidation

Seat Handling

R Print Seat Number in Red
1 Employee Class
2 Personnel | Employee Maintenance | <Sort By Class> | Guest Checks |

Guest Check Control
R Authorize/Use the [Split Check] Key and Perform Memo Tenders
2 Personnel | Employee Maintenance | <Sort By Class> | Printing | Check/

Receipt
R Authorize/Perform Print of Memo Checks
R Authorize/Perform Reprint of Memo Checks
2 Personnel | Employee Maintenance | <Sort By Class> | Transactions |

Transaction Control
R Authorize/Perform Change of Number of Guests
S-16
Security - Access Levels
Security - Access Levels
Access levels are used to control the ability to open and modify files in System
Configurator and take and reset reports. For a complete discussion of the use of
Access levels to secure System information, refer to “Access Levels” in Chapter
10 of the 9700 Feature Overview Manual..

Servers - Employee Definition
Servers - Employee Definition
Description
A server is any employee authorized to sign on to a UWS and perform sales
transactions. In MICROS terminology this person is known as an “Operator”.
For a complete discussion, see “Employees and Transactions” in Chapter 7 of the
9700 Feature Overview Manual.
S-18
Service Charge
Service Charge
Description
A Service Charge is an amount that is added to the sales transaction for a service
rendered. Service Charges are determined from a base amount (e.g., cover charge
$5.00) or by percentage (e.g., room charge 15%), and they may be taxed like a
menu item. Typical service charges include: Autogratuities, Room Service
Charge, Entertainment Cover Charge, etc.
Service Charge Itemizers

All items sold may be programmed to post the sales price to one of eight service
charge itemizers. Percentage service charges will affect menu items which are in
the same itemizer as the service charge. This way you can selectively apply a
service charge to certain items.
Example: Assume a 15% service charge key is programmed to compute on
service charge Itemizer 1 only. If two items are entered in the transaction, for
example, SALAD for 5.00 (programmed to add to service charge Itemizer 1) and
TABLE RENTAL for 10.00 (programmed to add to service charge Itemizer 2),
this key would add 15% of Itemizer 1 only, or a service charge of 0.75.
Your system may be set to reset the Itemizer total after the service charge is
applied (Type Definition #9). This will prevent the service charge from being
applied again, to items the next time the service charge key is pressed.
Usage
The 9700 System may be programmed to apply one or more of the following
types of service charges:
Open $ Service Charge

The dollar amount for this type of service charge is entered by the operator.
Preset $ Service Charge

The dollar amount for this type of service charge is programmed in the
Service Charge File. For example, a $5.00 entertainment cover charge may be
set up as a preset dollar amount service charge.

Service Charge
Open % Service Charge

The percentage amount for this type of service charge is entered by the
operator. This service charge will be applied to the total of all menu items that
are linked to the service charge itemizer on which this service charge
operates.
Preset % Service Charge

The percentage amount for this type of service charge is programmed in the
service charge file. For example, a 15% gratuity that is applied to parties of
six or more may be set up as a preset percentage service charge.
Autogratuity
An Automatic Service Charge is a percentage service charge which may be
selectively or automatically applied to every check opened in a Revenue
Center. The taxability of an Automatic Service Charge is not affected by the
Serving Period’s Tax Mask.
When a closed check is re-opened, the state of the autogratuity (ON or OFF)
is returned to its setting at the time the check was closed. For example, if
autogratuity was ON when the check was closed, but is now OFF, it is turned
back ON when the check is re-opened, and remains ON for that check until it
is service totalled, transferred, or closed.
Non-Revenue Service Charge

A non-revenue Service Charge is one that records the payment of funds
without posting the payment to sales totals.
A non-revenue [Service Charge] key can be used when a Credit Card
Authorization request is interrupted after it posts to the 9700 but before it
clears the CA server. Posting the amount a second time, in order to acquire the
authorization, would result in the totals being posted to the 9700 again. By
entering the amount of the authorization in a separate transaction as a non-
revenue Service Charge, the authorization request may be made to the CA
server without the amount posting a second time to the 9700.
A non-revenue Service Charge may also be used to record the payment of a
deposit (e.g., for a banquet) that does not reflect actual sales.
If Revenue Center Option #35 (Require Cashier Totals for Tender/Media or
[Tips Paid]) is ON, cashier totals are also required to post a non-revenue
Service Charge.
S-20
Service Charge
Reports
Financial Reports
System, Revenue Center, Employee, Time Period, and Serving Period
Income Audit Report

The flexible format of this report can be programmed to record Service Charges.
Establishment Tip Report

A service charge can be programmed to post to Service Charges Receipts on the
Establishment Tip Report (Service Charge File - Type Definition #4). The tip
report is designed to meet the requirements of the IRS Form 8027, which requires
that the Service Charge Receipts to represent all tips will (a) be paid to the
employee as wages, and (b) are greater than 10% of the check total.
A service charge can be set to add automatically to the Tips Paid total (Service
Charge File - Type Definition #12).
Closed Check Report

This report records autogratuities in a separate column. Charged Tips are recorded
in the Amount column.
Enabling
System Descriptor File

w Service Charge Itemizers field

w [Service Charge] key
w [Service Charge NLU] - keycode #201
w [Service Charge SLU] key
w [Exempt Auto Service Charge] - keycode #534

Service Charge
Service Charge File

w Complete all fields in this file.

w Service Charge Itemizer field—Link the menu item class with 1 of 8
itemizers.

w Automatic Service Charge field—Specify the percentage service charge (from
the Service Charge File) which will be used for autogratuity.
w # Guests Before Auto Service Charge field—If the autogratuity is only active
for parties of a certain size, enter the number of guests that must be entered in
a transaction in order to activate the autogratuity.
w Auto Service Charge Defaults to Off - Option #10—Set this OFF if an

Autogratuity is to be applied to every check.

w Add to Automatic Service Charge Itemizer - Type Definition #12
Set this ON for each Menu Item Class that will be affected by the autogratuity
calculation.

w Automatic Service Charge field— Specify the percentage service charge
(from the Service Charge File) that will be used for autogratuity.
w # Guests Before Auto Service Charge field—If the autogratuity is only active
for parties of a certain size, enter the number of guests that must be entered in
a transaction in order to activate the autogratuity.
w Auto Service Charge Defaults to Off - Option #10—Set this ON.

w Add to Automatic Service Charge Itemizer - Type Definition #12—Set this
ON for each Menu Item Class that will be affected by the autogratuity
calculation.
S-22
Service Charge

w [Exempt Auto Service Charge] - keycode #534
When this feature is active, the [Exempt Auto Service

Charge] key serves to turn off the auto service charge once
it has been active for a check. The service total will post a
“credit” of calculated auto service charges.
Options
Discount File
w Affects Auto Service Charge - Type Definition #11
Service Charge File

w Non-Revenue Service Charge - Type Definition #7
w Add to Guest Count - Type Definition #10—This selection is most often

used with service charge keys that will be used to post cover charges
(usually defined as fixed-price service charges). This selection saves the
operator the task of entering the number of guests by posting the guest
count when entering the cover charge.
w Tax Class field—By linking to a particular Tax Class, service charges

may be programmed to be taxable by some or all tax types.
Tender/Media File
w Exempt Auto Service Charge - Type Definition #12

Service Charge

w “Other SVC” name field
w Auto Service Charge Defaults to Off - Option #10
w Round Discount and Service Charge % Entries - Posting Option #2
w Round To 0, 10 Discount and Service Charge % Rounding - Posting

Option #3
w Discount and Service Charge % Rounding: Round to Nearest 0 or 10 -

Posting Option #4
w Cashier Totals Declaration Required with Tender/Media and Tips Paid

Keys - Control Option #1
w Allow Void Of Service Charge In Current Service Round Only - Control

Option #5
w Validation Required for Menu Item, Service Charge Voids - Control

Option #10
w Display Prices of Menu Items, Discounts, & Service Charges When a

Check Initially Displays - HHT Option #1
Employee Class File

w Authorize/Perform Automatic Service Charge Exemptions - Transaction
Privilege #12
w Post Service Charges to Checks Belonging to Another Operator -

Transaction Privilege #21
w Authorize/Perform Void of Service Charges from a Previous Round -

S-24
Service Charge
w Authorize/Perform Posting of Service Charges in Privilege Groups 1, 2,

or 3 - Transaction Privileges #55, #56, #57—Service Charge keys may be
linked to one of three privilege groups. Service charges not linked to a
privilege group (the same as a privilege group=0) may be posted by
anyone.
w Authorize/Perform Void of Service Charges on Closed Checks -

Related Topics
w “Discounts” on page D-16
w “Itemizers” on page I-1

Service Total
Service Total
Description
A Service Total ends the current service round, triggering output to order devices.
It temporarily removes a guest check from the UWS display, and saves the check
information in the Open Check Totals and Detail Files for later recall.
Usage
Print Check
A [Service Total] key is usually programmed to print the items posted during the
service round. Output may include local and remote order printing, guest check
printing, journal printing, and validation printing.
Reprint Check
This key is used for a by-round operator. For example, a check may need to be
reprinted when the original check has been lost, mutilated, or overprinted. This
feature is enabled by using a [Service Total] key with Tender/Media Type
Definition #19 set ON (Reprint Guest Check).
Chain & Fire

This key allows an operator to post detail to and service total a series of checks
without sending check detail to order printers until a separate service total key is
pressed. This allows orders that may be received and posted separately to be sent
together to the remote order devices. The buffer feature is enabled by using a
[Service Total] key with
Tender/Media Type Definition #3 set ON (Chain & Fire).
Any service total key with Type Definition #3 set OFF will serve to “fire” the
buffeted checks to the remote order devices.
S-26
Service Total
Hold & Fire

This key allows an operator to post order detail to a guest check and to service
total the check without sending the order detail to remote order devices. Thus, the
operator can post a check and later “fire” the order to the kitchen to better control
preparation timing. The hold feature is enabled by using a [Service Total] key
with Tender/Media Type Definition #2 set ON (Hold & Fire).
The “fire” function is enabled by picking up the check and service totaling it with
a [Service Total] key that has Type Definition #2 set OFF.
Print Memo Check

A memo check is a printed check that includes the detail and subtotals for one or
more (but not all) seats assigned to the check. For example, a table of four guests
has requested separate checks at the end of their meal. The entire meal is on one
guest check and now must be separated into four memo checks, one for each of
the four guests.
The Memo Check feature creates individual checks for each guest, while the
original check remains intact. The feature is enabled by setting Tender/Media
Type Definition #13 ON (Print Memo Check).
Fast Transactions
Normally, a Fast Transaction is completed (tendered and closed) before another
guest check is opened or picked up on the same UWS. When this is the case, Fast
Transactions do not print a guest check but a customer receipt. However, each
Revenue Center may be programmed to allow Fast Transactions to be service
totalled. When a Fast Transaction is service totalled, the transaction prints as a
guest check when it is tendered.
If Operator Type Definition #9 (Line-by-line Customer Receipt) is set ON, the
operator may service total a fast transaction. Support for service total of line-by-
line fast transactions began in Software Version 1.02. When the transaction is
picked up after being service totalled, it is no longer in line-by-line mode.
Require Credit Authorization

A [Service Total] key may be programmed to require that the operator perform a
credit authorization before a service total is allowed. This may be useful in a busy
service environment, such as a bar, in which customers frequently ask to run a tab.
Setting Tender/Media Type Definition #41 ON (Require Credit Authorization
Before Service Total) ensures that the bartender does not allow anyone to run a
tab without first presenting a credit card for authorization. If the customer
“forgets” to settle up, the check can still be closed to the credit card.

Service Total
Reports
[Service Total] keys do not record the payment of cash, and therefore do not post
to any reports. If they are tracked on reports, using Tracking Groups, they always
post a total of $0.00.
Enabling
Tender/Media File
w Tender/Media Type field—Service total keys are defined as Type 2.
The Type Definition selections change automatically

for each Tender/Media type.
Options
Operator File
w Line by Line Customer Receipt - Type Definition #9

w Do Not Allow Service Total of Fast Transactions - Option #16
w Print Previous Balance Each Round - Format Option #11
w Service Round Totals Include the Current Round Only - Format Option
#13
w Print Service Total Time on Checks - Format Option #14
w Cashier Totals Declaration Required with Tender/Media and Tips Paid

Keys - Control Option #1—Set this ON to require that an operator declare
Cashier totals before being able to Service Total a check.
S-28
Service Total
Tender/Media File
w Print Memo Check - Type Definition #13
w ON = HALO Computed on Amount Entered; OFF = Amount

Overtendered - Type Definition #19
w Require Credit Card Authorization Before Service Total - Service Total

Type Definition #41
Related Topics
w “Open Check Block Settlement” on page O-4
w “Reprint Check” on page R-17

Serving Periods
Serving Periods
Description
A Serving Period is any time span for which sales totals tracking and reporting is
desired by management. Serving periods are not changed automatically by the
system; when the current serving period ends, the system may be programmed to
prompt for the period to be changed.
Usage
Serving Periods may be assigned specific beginning and ending times. When a
Serving Period time expires, the operator is prompted to manually change the
Serving Period.
Serving Periods are not required in the 9700 System. However, if Serving Periods
are defined, a Serving Period must be active in order to begin a transaction,
because the Serving Period’s Tax Mask field determines the sales tax applied.
Serving Periods have a variety of uses listed below:

Each Serving Period may be linked to a separate tracking group defined in the
Tracking Group File (see “Tracking Groups” on page T-141). Serving Period
tracking is used to supplement 9700 Revenue Center reports and provide sales
tracking information for Major Groups, Family Groups, Menu Items, Discounts,
Service Charges, and Tender/Media during specific times. For example, happy
hour drinks, daily specials, or Cash may be tracked by Serving Period.
Main and Sub Menu Levels

A serving period can be used to change the current Main and Sub Menu Levels.
For example, a serving period may used to make available certain menu items or
change the prices. For example, you could have a serving period that would pop
up to Menu Level 1 (Breakfast). Then, have another serving period that would
pop-up to Menu Level 2 (Brunch).
The advantage of controlling menu levels by serving period is that the manager
can determine the start and end times. Otherwise, automatic menu level shifts can
be defined in the Revenue Center Parameters File.
S-30
Serving Periods
Tax Mask
A serving period may be used to exempt, or “mask”, a Tax Rate from being
applied. For example, an entertainment tax may be required when live music is
played. This tax would be masked for all regular serving periods (no music), and
applied only when there is entertainment. The serving period tax mask does not
affect the taxability of an auto service charge.
Disable Japanese Tax Threshold

Type Definition #1 (Disable Japanese Threshold) applies to Japanese Tax
calculations. Set #1 ON to disable the Threshold amount on which Excise Tax is
calculated during this serving period. Serving Periods are changed manually,
using UWS Procedures.
Reports
Serving Period Report

This report is a summary of sales activity by serving period. Tracking Groups may
be linked to serving periods to track specific totals.
In the Serving Period File, the number of tables in a Revenue Center can be
specified. This is used in the Serving Period Report to calculate time and sales
averages per table.
Enabling
Serving Period File

w Tracking Group field—For each serving period enter the Tracking Group
which will track and format the information required.
w Enter the appropriate information for the Start and End times, Menu Levels,
Tax Mask, etc. A Start and End Time can be specified for each serving period.
These times are only used to alert an operator, with a UWS prompt, that the
serving period should be changed through Workstation Procedure #2. Set the
times to 0:00 to disable the prompt.

Serving Periods
Unlike Time Periods, Serving Period times cannot

overlap.

w Serving Period field—Enter the default Serving Period for each Revenue
Center.
Employee Class File

w Use UWS Procedure #2: Change Serving Period - Supervisory Privilege
#2
Related Topics
w “Revenue Centers” on page R-24
w “Time Periods” on page T-66
S-32
Description
In the 9700 System, the database is divided between Totals Files and Definition
Files. Totals Files record numeric sales information about an item, while
Definition Files define what an item is. For example, every menu item is defined
by name, prices, item number, etc.
In the 9700 System, the Revenue Center definition files are downloaded to each
UWS/3 during POS Operations. This speeds operations because the PC is
accessed less often.
However, operators from different Revenue Centers may need to use the same
UWS/3, which has only stored one set of definition files. This is overcome by
allowing several “child” Revenue Centers to share the Definition Files of a single
“parent” Revenue Center, which acts as a “master list.” Thus, each UWS/3 is
downloaded with only the Shared Definition Files. Totals files are still unique
for each Revenue Center and are stored on the PC.
The files listed below are downloaded to the UWS/3 during POS Operations:
w Menu Item Definition File
w Menu Item Price File
w Menu Item Class File
w Touchscreen Assignment File
w Touchscreen Style File
w Touchscreen Screen File
Usage
This feature is required when operators from different Revenue Centers use the
same UWS/3.
The second use of this feature is that by using one Revenue Center as a master list
(referred to as the “parent”), you also can avoid entering the same records again in
other Revenue Centers (referred to as “children”). This can save programming
time, system maintenance, disk space, and memory usage.

Enabling
Revenue Center Configuration File

w Revenue Center with Shared Definition Files field—Assign which Revenue
Center will provide the Shared Definition Files. This is the parent Revenue
Center, housing the definition records that will be shared with this child
Revenue Center.
Related Topic
w “Types of Database Files” in Chapter 4 of the 9700 Feature Overview Manual
S-34
SLU Sort Priorities
SLU Sort Priorities
Description
This feature, if enabled, will allow items within a SLU to be sorted by priority
group. Additionally, Alpha sorting, if enabled, will occur within each sort priority.
This feature is valid for the PCWS only.
Enabling
Menu Item Definition File

w SLU Sort Priority field -Valid values are zero through 3, with 1 being the
highest priority (sorting first), and zero being no priority.

w Sort Screen using Menu Item Sort Priorities-Key Type Definition #11
PCWS Application
w PCWS Application 2.11 must be loaded on the PCWS

Soft Check
Soft Check
Description
A Soft Check is a guest check printed on a continuous paper roll.
Usage
Soft checks are less expensive than pre-printed checks made from card stock.
Typically soft checks are presented to the guest in a check folder.
Enabling
The following programming is required to print a soft check:
Device Table
w Device Type field—Specify a roll printer (Device Type #2).
Tender/Media File
w Output Links field
w Print Check On-demand - Type Definition #23—This selection is normally

set for service total keys that should print the check for On-demand operators.
Menu Item, Service Charge, and Discount Files

w Output Links—Menu items, service charges, and discounts each have an
Output Links field in their respective files. Set the selection #4 ON (Print on
Guest Check) for each item which will print on the guest check.
S-36
Soft Check
Options

w Lines on First Guest Check Page field
w Line Feeds Before First Guest Check Page field
w Lines on Other Guest Check Pages field
w Line Feeds Before Other Guest Check Pages field
w Minimum Number Lines Per Roll Check/Receipt field
w Partial Cut Between Customer Receipts (Autocut Printers Only) - Format

Option #20

Sort Options
Sort Options
Description
Transaction Detail
When transaction detail items such as menu items, discounts, and service charges
are sorted, they display or print on the guest check, guest receipt, order printers,
they may be sorted in an order determined by the system, or in the order in which
they were posted.
Transaction items print on the journal in the order in which they were posted. Sort
options do not affect the journal.
Sorting is a programmable option in the 9700 System. There are three sort criteria:
w Seat Number: If seat handling is used, printing may be sorted by the seat
number to which an item was assigned.
w Print Group: Printing may be sorted by the print group number (1 - 8)

assigned to each item.
w Consolidation: Identical items may be combined on a single line with a

numeric entry.
NLUs and SLUs

The items that display in an NLU help window may be programmed to sort
alphabetically or numerically (i.e., in the order in which their records occur in
their respective files).
The keys that display in an SLU may also be programmed to appear in either
alphabetic or numeric order.
S-38
Sort Options
Usage
Transaction Detail
Seat Numbers
A seat number is a means for identifying individual guests on a check. When
seat handling is used, check detail can be assigned to individual seat number
and printed in seat order. See “Seat Handling” in Chapter 9 of the 9700
Feature Overview Manual for more information.
Print Groups
Menu items, service charges, and discounts can each be linked to one of eight
print groups. A lower-numbered group prints before a higher-numbered
group. This provides a variety of applications. For example:
w One remote printer is used by an expeditor who calls out orders to the
kitchen staff. If the meat items are placed in one group, fish items in a
second, and cold food in a third, the expeditor can easily call out each
station’s entire order.
w At a service bar, it may be more efficient to have all beers print first and
all mixed drinks print next.
Consolidation
When menu items are posted separately to a guest check and consolidation is
used, only one line prints for the item indicating the total quantity actually
posted. If the menu item, SALAD, is posted three separate times to a check, a
regular listing displays as follows:
1 SALAD 5.00
1 SALAD 5.00
1 SALAD 5.00
A consolidated listing displays one line:
3 SALAD 15.00

Sort Options
The following types of menu item entries do not consolidate:

w Menu items with condiments or modifiers
w Menu items with Item Discounts
w Open priced menu items
w Weighed menu items
w Menu items with a decimal amount entry.
Enabling
Transaction Detail
The following sort/consolidation criteria are used for menu items, discounts, and
service charges in the 9700 system:
0 = no sort
1 = sort by seat only with consolidation
2 = sort by seat only without consolidation
3 = sort by print group only with consolidation
4 = sort by print group only without consolidation
5 = sort by seat and print group with consolidation
6 = sort by seat and print group without consolidation
7 = sort by print group and seat with consolidation
8 = sort by print group and seat without consolidation
These criteria may be programmed in each of the following fields:
w Revenue Center Parameters File
w Screen Sort Type field
Order Device File

w Sort/Consolidation Type
S-40
Sort Options
Options

w Print Group field—For each Menu Item Class specify the Print Group (1-
8) to which this item belongs.
w Condiment Changes Print Group of Parent Menu Item - Type Definition

#9—Condiments can be used to change the print group of the parent item.
For example, you may have print groups defined as Appetizer, Entree,
and Desserts. If a guest orders a SALAD, and would like it served as an
entree, then a condiment can be created called “AS ENTREE”, which will
change the print group of the salad and force it to print as an entree.
NLUs and SLUs

w NLU, Condiment Help Screen Sort Type field
0 = Do Not Sort
1 = Sort Alphabetically
2 = Sort Numerically

w Sort Screen Alphabetically - Key Type Definition #1—This file only
applies to UWS/3 Touchscreens. If Type Definition #1 is set OFF (Sort
Screen Alphabetically), generated keys will be displayed in item record
order. If #1 is set ON, all generated keys will be displayed in alphabetical
order by item name.
Displaying items in alphabetical order will increase

the time required to generate each screen.
w Show Tbl/Grp in Open Check SLU - Key Type Definition #3—This type
definition applies only to the Pickup Check and Add/Transfer SLUs. Set
this ON to display the table and group, along with the check ID, when a
Guest Check SLU is generated by this style. Set this OFF to display the
table and group only if there is no guest check ID.

Sort Options
w Show Check # in Open Check SLU - Key Type Definition #4—This type
definition applies only to the Pickup Check and Add/Transfer SLUs. Set
this ON to display the check number, along with the check ID or table
number, when a Check SLU is generated by this style. Set this OFF to
display the check number only if there is no guest check ID or table
number.
w Show Other Employee’s Name in Open Check SLU - Key Type—

Definition #5
This type definition applies only to the Pickup Check and Add/Transfer
SLUs, and only to checks that belong to other operators. Set this ON to
display the Check Name of the other operator to whom this check
belongs, along with the check ID, when a Check SLU is generated by this
style.
w Show Amount Due in Open Check SLU - Key Type

Definition #6—This type definition applies only to the Pickup Check and
Add/Transfer SLUs. Set this ON to display the time the check was
opened, along with the check ID, when a Check SLU is generated by this
style.
w Show Open Check SLU Amount Due on Key - Key Type Definition #7—
This type definition applies only to the Pickup Check and Add/Transfer
SLUs. Set this ON to display the amount due, along with the check ID,
when a Check SLU is generated by this style.
w Display Keys Vertically Starting at Top Left - Key Type

Definition #8—Set this ON to display the keys generated by this style in a
vertical format. Set this OFF to allow Type Definition #9 to determine the
key display pattern.
w Display Keys Horizontally Starting at Top Left - Key Type Definition

#9—This Type Definition is active only if Type Definition #8 is OFF. Set
this ON to display the keys generated by this style in a horizontal format
that begins in the top left corner of the screen. Set this OFF to display the
keys generated by this style in a horizontal format that is centered in the
screen.
S-42
Sort Options
Changing ASCII Sort Order: The collate Program

For alphabetic sorting, the System uses a character’s ASCII code number to
determine sort precedence. For example, ASCII character #90, the upper-case
“Z”, sorts before ASCII character #97, the lower-case “a”. ASCII character
#49, the numeral “1”, precedes them both.
The sort precedence of ASCII characters may be re-defined using the collate
program. This may be useful if your installation requires NLU and SLU
sorting to be case-insensitive (e.g., you want “A” and “a” to sort as the same
character). Changing the sort precedence is also useful in foreign language
applications.
To force the System to use a different sort precedence, use the collate
program to create the file collate.tbl from one of the supplied input files. If
collate.tbl exists in the directory /usr/9700/text, the System uses it to
determine ASCII sort precedence. If the file does not exist in this directory,
the System uses a standard ASCII sort routine. Use the following steps:
1. Edit one of the supplied input files to create a new sort order. Two sample
input files are included with the System:
w /usr/9700/etc/col_dflt.in—This file is a list of 255 ASCII characters

(the standard IBM character set), in their original order.
w /usr/9700/etc/col_us_engl.in—This file is a list of those ASCII

characters that are commonly used in U.S. English. The list includes
numerals, upper- and lower-case letters, and standard punctuation.
The file has been edited to alter the order in which the characters are
sorted. If this file is used to determine sort precedence, the alphabet is
sorted in a case-insensitive pattern (i.e., “A” and “a” are treated as the
same character).
Each line in the input files uses the following format:
<Control character> <space> <ASCII character #> <space> <comment>
Control characters are used to group ASCII characters together:
w * = Sort the entry on this line as a separate character.
w + = Sort the entry on this line as if it were the preceding character.
2. Change to the directory /usr/9700/etc, where collate is located.
3. Create collate.tbl using the following command:
collate /usr/9700/etc/<inputfile> /usr/9700/text/collate.tbl

Sort Options
Related Topics
w “Print Groups” on page P-33
w “Seat Handling” in Chapter 9 of the 9700 Feature Overview Manual
S-44
Special By-Round Operator
Description
Special By-round Operators function as On-demand operators in that they can
service total a guest check without printing it. Once they have printed a check,
they function as a By-round operator for that check, causing a check to print with
each succeeding service total.
Usage
Special By-round printing of guest checks ensures that the operator always has an
updated version of the guest check. At first, the operator is On-demand, so that he
or she doesn’t have to carry the guest check and possibly lose or damage it. After
the first printing, the operator becomes By-round, so that all rounds are printed
and there is no possibility of presenting an outdated version of the guest check.
Example
Mark is a Special By-round operator. Mark takes an order for two chicken dinners
and two Cokes. He rings the order, serves it, and does not print the check. When
his customers ask for dessert and the check, he prints the check and delivers it
along with two cheesecakes. As he presents the check, they tell him they’ve
changed their minds and would like to order two coffees. Mark adds the coffees to
the check.
Because Mark has already printed the check, he has become a By-round operator
for this check. This means that when he service totals the coffees, the system
prompts him to put the guest slip back into the printer. The system adds the
coffees to the check and prints the new balance due.
If the customers request more cheesecake when Mark tries to present the check a
second time, Mark can easily add this to the old guest check. Because he is now a
By-round operator, the system will add each round to the old guest check when
Mark presses a service total key.

Enabling
Operator File
w ON = On-demand; OFF = By-round - Type Definition #5—Set this OFF.
w Special By-Round (Same as 4700 Temporary On-demand) - Type Definition

#6—Set this ON.
Related Topics
w “On-Demand Guest Check” on page O-1
S-46
Split Check Functions
Split Check Functions
Description
A check is split when a portion of the original check detail is split off of the
existing check to form a new one. It is the opposite of the Add Check function. To
split a check, seat handling must be used. Each seat, or group of seats, is “filtered”
and split onto a new check.
The TouchSplit feature combines split check functionality with that of
TouchAdvantage. This allows an employee to select and move detail from one
quest check to another with the touch of a finger. Its just as simple as that. For
more information, refer to TouchSplit in the Encyclopedia section of this manual.
For a complete discussion of the split check function, see “Seat Handling” in
Chapter 9 of the 9700 Feature Overview Manual.

SQL Access
SQL Access
Description
SQL (Structured Query Language) was developed from research conducted by
IBM during the mid-1970s. Since its first commercial introduction in 1979, SQL
has been adopted by many vendors as a database language standard for
mainframe, minicomputer, and microcomputer environments. This means that
companies can continue to standardize their development of database
applications.
Usage
SQL provides a small and concise set of commands that allow you to define,
display, and update information in tables (similar to a typical spreadsheet). By
reducing the number of commands you need to access data, SQL saves you time
and reduces the amount of programming needed to perform complex queries.
SQL commands can be used to access the 9700 Database. This allows you to
import database information into many accounting packages as well as standard
database applications like dBase IV and Paradox.
For a complete listing of SQL commands, with tables of 9700 fields, refer to the
9700 SQL Manual.
Related Topics
w “Database Architecture” in Chapter 4 of the 9700 Feature Overview Manual
S-48
Stay-down
Stay-down
Description
Operators, menu levels, and NLU screens may be defined in the System program
as “stay-down”. In the case of operators and cashiers, it means they are active on a
User Workstation from the time they sign on until they are signed off. In the case
of a menu level, a “stay-down” menu level is active from the point it was activated
by a menu level select key until it is replaced by pressing a menu level select key
for a different menu level.
For a complete discussion of this feature, see “Pop-up, Stay-down Functions” on
page P-20.

System Interface Module
System Interface Module
The 9700 System Interface Module (SIM) is a software module that allows the
9700 to interface with a variety of other data systems, including sophisticated
Property Management Systems (PMS), automated delivery systems, and other
electronic database systems.
SIM offers an Interface Script Language (ISL), which allows the interface
designer to invoke touchscreens, direct operator prompting, define interface
message formats and subsequent 9700 System processing, and execute keyboard
macros on a UWS.
SIM scripts may be written to include tests for four Supervisory Privileges, thus
allowing the designer to create access level protection for scripts.
Enabling
Employee Class File

w ISL Options #1 through #8—ISL Options allow each class of employees to
execute specific Interface Script Language (ISL) scripts using the System
Interface Module (SIM).
Interface File
w ISL Script Name field—Enter the name of the ISL script file that the SIM
should search for if it is to execute an event linked to a PMS or other
interfaced device. The filename may be up to 8 characters, and must not
include an extension. The 9700 System automatically appends the extension
“.isl” to the filename entered here, and searches for the file in the /usr/9700/
etc directory.
For a complete description of SIM, refer to the 9700 System Interface Module
Manual, P/N 100068-084.
S-50
T
Table Management System
Description
The ProHostÔ Table Management System (TMS) is a computerized seating
management system that helps organize table usage and assignment in a
restaurant.
The full-color touchscreen video monitor of the TMS displays the restaurant’s
floorplan and shows the current status of all tables. This system balances server
stations and optimizes seat usage, allowing the operator to tell the restaurant’s
seating status at a glance.
The TMS can communicate with the 9700 System through an RS232 interface.
This allows the TMS to open guest checks in the 9700 System.
The Integrated Waiting List feature in the TMS manages a guest waiting list,
estimates wait times, and pages guests.
Designed and manufactured by Rock Systems, Inc., of Dallas, Texas, ProHost is
marketed exclusively by MICROS Systems, Inc.
9700 HMS A to Z Feature Reference Manual T-1

Usage
When interfaced with the 9700 System, the TMS performs the following
functions:
w Open a guest check by table number in the 9700 System. The TMS opens the
check as a dummy operator (#999999999), but no ownership is assigned to
this check.
w Enter the number of guests when the check is opened. (This feature is
optional.)
w Start the 9700 System’s Table Dining Time clock when the check is opened.
The TMS does not automatically process any changes that take place after an
operator picks up a guest check. Any guest checks opened by the TMS and not
picked up by a server will remain open in the 9700 System. They will post to the
Employee Open Check Report for Employee #999999999 if they are not picked
up and closed. Any checks opened by the TMS and picked up by an employee in
Training mode will become Training checks.
Example
A party of four approaches Samantha at the hostess’ stand and asks for a table in
the nonsmoking section. Samantha consults the TMS monitor, which shows a
graphic diagram of the restaurant floorplan, including the stations assigned to
each waiter, and the active tables in each station. She enters the size of the party
and the smoking preference at the TMS monitor.
The TMS refers to internal information that it has stored, including the number of
parties that each waiter is currently serving, the times at which each party arrived,
etc., and suggests seating the new party at table #37. Samantha touches table #37
on the monitor to confirm the selection.
The TMS opens a guest check by table number in the 9700 System. Table #37 is
entered for the table number, and the check is temporarily assigned to server
#999999999. (All tables opened by the TMS are assigned by the 9700 System to
server #999999999. However, this check is not owned by any operator at this
time; there is no check operator.)
Samantha conducts the party to table #37. Upon arrival, they notice that table #25,
which has a view of the ocean, is unoccupied, and they ask to be seated there
instead. Samantha agrees, and seats the party at table #25.
Returning to the TMS, Samantha closes table #37 and opens table #25. These
actions are repeated in the 9700 System. (Because the check for table #37 was not
picked up by a server, Samantha is able to close it in both systems from the TMS
monitor.)
T-2
Samantha tells George that he has a party at table #25. George greets the guests
and takes an order. He then goes to a UWS and uses the [Pickup Check by Table
#] key to pick up the check for table #25. In doing so, George takes ownership of
the check, and becomes the check operator for this check.
George’s Employee Class Privileges do not allow him to pick up checks
belonging to other operators. However, this privilege is not required to pick up a
check begun by the TMS.
TMS Interface Messages

There are three new messages that may be sent to the TMS (Table Management
System) Interface from the 9700 System and an environment variable which
allows a User-Defined Operator prompt when the guest check update message is
sent to the TMS System:
w Guest check update
w Table transfer update
w Table status update
w User-defined operator prompt
These new messages will update the TMS System with the current status of each
check in the 9700 System.
Guest Check Update Message

This message is used to inform the TMS that a table has changed its status.
There are three different update types:
w Check has been opened
w Check has been printed
w Check has been paid
There are two Tender/Media Output Links that control if the check printed
message will be sent to the TMS Interface on full or partial tenders and/or
whether to prompt the operator to send the message.

User-Defined Operator Prompt

The User-Defined Operator prompt will appear if the Tender/Media Output
link to prompt the operator is enabled. The text used to prompt the operator
(Send Message to TMS) can be user-designed by programming an
environment variable. The environment variable is included in the /etc/
default/micros file and must be in upper case, as shown below. The variable
is set by Revenue Center number:
RVC_<RVC #>_TMS_PRMT=’<text>’
<RVC #> is the Revenue Center number is which the prompt will be active.
The <text> must be enclosed by apostrophes and the maximum number of
characters included in the text string is 32. For example:
RVC_51_TMS_PRMT=’Send Message to ProHost?’
Table Transfer Update Message

This message sends table transfer information to the TMS.
This transfer message is not related to the transfer

functions within the 9700 System.
The keycodes [TMS Xfer Tbl] and [TMS Xfer Tbl Rvc] support this function.
These keys are used to transfer a check from one table to another within the
TMS System before any detail has been added to the check.
DO NOT use these keys if detail has been added to a check. If detail has been
added, use the normal method of transferring a check via POS Operations. If
the [TMS Xfer] keys are used when there is detail on a check, the check will
be transferred to the new table but the old table will remain an open check.
This open check must be picked up and closed manually; the [TMS Xfer] key
will not close the check.
T-4
These transfer keys may be used outside of a transaction. For example, if the
host began a check on one table, then the customer moved to another table
(either in the same Revenue Center or a different Revenue Center), the host
may transfer the check to the other table using the 9700 System.
Procedure—Xfer Table TMS
1. At the UWS, press [TMS Xfer Tbl].
2. Enter the table number of the check you wish to transfer.
3. Enter the new table number (transfer to table). The System will
prompt “One moment, sending message.” There will be no notice or
prompting after the message is sent. The UWS will simply return to
“Ready for next entry” status.
Procedure—Xfer Table RVC
1. At the UWS, pickup table to be transferred.
2. Press [TMS Xfer Tbl Rvc]. The System will prompt “Enter current
table revenue center” and display a listing of the Revenue Center.
3. Enter Revenue Center number.
4. Enter new table number (transfer to table). The System will prompt
“One moment, sending message”. There will be no notice or
prompting after the message is sent. The UWS will return to the
“Ready for next entry” status.
Table Status Update Message

This message is really three different keycodes: [TMS Bus Table], [TMS
Clear Table], and [TMS Close Table], to inform the TMS of the current status
of a particular table.
Procedure—Table Status Keys

The example below will use the [TMS Bus Table] key, but the procedure
may be used for any Table Status Update key (TMS Clear or TMS Close
keys).
1. Press [TMS Bus Table]. The System will prompt “Bus table: enter
table number”.
2. Enter table number. The System will prompt “One moment, sending
message”. There will be no notice or prompting after the message is
sent. The UWS will return to the “Ready for next entry” status.

Reports
Employee Open Check Report

Checks opened by the TMS and not picked up by a server will appear on this
report for Employee #999999999. The report prints a U next to the table number
of the check.

w Number of guests
Financial Report
Financial reports (System, Revenue Center, Employee, Time Period, and Serving
Period) can be programmed to include an optional Table Profile section, which
includes:
w Table Dining Time
w Average Turn Time
The principal effect of the TMS on 9700 Reports is to improve the integrity of the
Table Dining Time and Average Turn Time fields. Since the guest check is
opened as the guest is seated, the clock starts running at that time, instead of after
the server takes the order, walks to the UWS, and begins a check.
T-6
Enabling
ProHost
The TMS must be programmed to match the 9700 System. Elements from the
9700 System that must be entered in the ProHost include the following. The TMS
must be programmed:
w to match the configuration of the desired Revenue Center
w to use 9-digit or 2-digit Terminal ID numbers, depending on the setting of

Interface option ON = Use 9 digits for Terminal ID’s ; OFF = Use 2 Digits
for Terminal ID’s (System Hardware | Interface | General).
w with Table Numbers or Table IDs from the Table File, depending on the
setting of Revenue Center Parameters option ON = Use 5 Digit Table
Number; OFF = Use 4 Character Table ID (RVC Information | RVC
Parameters | Options).
w Table ID
w to include the employee entered in the TMS Operator field in the 9700’s
MICROS (Required)
2 RVC Information | RVC Parameters | Interfaces | Table Management

System Options
R TMS Operator field—Enter the number of the operator to whom a
check that is opened by the TMS is assigned before being picked up by
a server.
R TMS Workstation field—Enter the UWS number to which a check
that is opened by the TMS is assigned.

1 Interface

R Service Type field—Set this to 3, for Table Management.
R Type field—Set this to TTY.
R TTY Baud Rate field—Set this to 9600.
R TTY Word Length field—Set this to 8.
R Parity Check—Disable this option.
R Stop Bits—Select One.
1 Tables
2 RVC Information | Tables | <Select RVC> | Insert

R Table ID field—If 4-character Table IDs are used, the Table IDs must
be numerals. The ProHost System does not accept alphabet characters.
1 Employees
2 Personnel | Employee Maintenance | Sort By Employee

R An employee record must be set up for use by the ProHost System. All
privileges should be disabled. All other fields for this record may be
left blank, or set to their default values.
1 Operators
2 Personnel | Employee Maintenance | Sort By Operator

R An operator record must be created and linked to the Employee record
created above. This operator’s record number is entered in the TMS
Operator field on the Interfaces tab in the Revenue Center Parameters
file. All fields may be left blank or set to their default values.
T-8


R 412 through 421 - Pickup Check by Table—Servers must be able to

pick up checks by table number. The signed-in operator need not be
privileged to pick up guest checks belonging to another operator in
order to pick up checks belonging to the TMS operator (#999999999).
R 439 - Pickup Check, SLU—This key displays an SLU with buttons to
select any one of:
w All open guest checks assigned to the signed-in operator, and
w All open guest checks assigned to the TMS operator (#999999999).

If the signed-in operator is privileged to pick up checks belonging
to another operator, this key displays all open guest checks in the
active Revenue Center. The signed-in operator need not be
privileged to pick up guest checks belonging to another operator in
order to view and pick up checks belonging to the TMS operator
(#999999999).


R 551 - TMS Bus Table—This key will inform the TMS that a table
needs to cleaned.
R 552 - TMS Clear Table—This key will inform the TMS that a table
has been cleaned.
R 553 - TMS Close Table—This key will inform the TMS that a table
has been closed.
R 554 - TMS Xfer Tbl—This key will transfer one check to another in
the TMS.
R 555 - TMS Xfer Tbl Rvc—This key will transfer one check to another
in the TMS.

1 Tender Media

Printing Options
R Send PRINT CHECK Message to TMS on Final Tender Only
R Prompt Operator to send PRINT CHECK Message to TMS
Optional Settings

R Print the Table Number Double-wide on Guest Checks Only
R Print Service Total Time on Checks
R Print Open And Closed Time On Guest Check

R [Pickup Check] key Confirmation Not Required
2 RVC Information | RVC Parameters | Interfaces | Table Management

System Options
R ON = Use 5 digit table Number; OFF = Use 4 character table ID
R Send Check Status Messages to TMS

R Allow only one group per table
1 Interfaces
2 System Hardware | Interfaces | General

R Force the Number of Guests to Zero When Creating a TMS Check
1 Employee Class

R Authorize/Perform Opening of Multiple Groups at a Table
T-10
Related Topics
w “Tables” on page T-12

Tables
Tables
Description
A Table is a separate seating location for one or more guests in the restaurant. In
the 9700 System, tables are identified by the Table number, which can be
programmed as either of the following:
w any four-digit string of numbers or alphanumeric characters
w the five least significant digits of the object number in the Table File
Usage
Table numbers are assigned by operators when a check is begun. Usually, only
servers are required to use table numbers. However, in some restaurants, the
bartender designates each seat at the bar as a separate table.
A restaurant’s uses for table numbering may include:
w Table numbers are used to allow runners to pick up food orders from the
kitchen and deliver them to guests.
w Table numbers are used by operators to pick up a guest check that has been
service totalled.
w Managers can view checks or perform check operations (e.g., voids) without
having the guest check or the server present.
w Sales reporting can be broken down by table.
T-12
Tables
Separate Checks Scenario

A group of customers sitting together at a table may ask the server for separate
checks. The 9700 System provides three different methods of meeting this
request.
Seat Handling
The 9700 System’s seat functions allow the server to assign all of the menu
items ordered by this party to a specific “seat” on the guest check, while
keeping all of the menu items on a single check. In some situations, this offers
the server some assurance that menu items ordered together will be ready at
the same time. Using seat handling also means that the server has to keep
track of less checks than would be required if opening a separate check for
each person.
Groups
When a check is opened by table number, the Revenue Center also assigns the
check a group number. The group number appears to the right of the “/” in the
table number display. For example, 3/1 indicates Table #3, Group #1.
If the Revenue Center is programmed to allow more than one group per table,
the server can open multiple guest checks for a single table. Each successive
guest check opened is assigned a distinct group number, up to a maximum of
99 groups per table.
The Revenue Center may be programmed to re-use group numbers at a table
as those checks are closed, or it may be programmed to sequentially assign
group numbers.
Split Checks
This feature is used to transfer a portion of the original guest check detail to a
new check. A Split Check is a separate guest check for each seat or a
combination of seats at a table.

Tables
Reports
Table Sales Report, Income Audit Report

The flexible format of these reports can be programmed to include table
information.
Financial Report
Financial reports (System, Revenue Center, Employee, Time Period, and Serving
Period) can be programmed to include an optional Table Profile section, which
reports:
w # Tables / $ Average
w # Turns / $ Average
w # Turns / Table
w Table Dining Time
w Average Turn Time
Enabling
1 System Parameters

R System Table Count field
R Do Not Print the Table Section on Financial Reports
T-14
Tables

R Table Count field

R ON = Use 5 digit Table Number; OFF = Use 4 character Table
ID—When 5-digit table numbers are used, the programmer must limit
the record numbers in the Table File to the range 1 - 99999.
R Use the First Available Instead of the Next Highest Group Number

R Print the Table Number Double Wide on Guest Checks
Only

R Allow Only One Group per Table
1 Operators

Operator> | General
R Table Count field

1 Employee Class

R Authorize/Perform Opening of Multiple Groups at a Table

Operator> | Transactions | Transaction Control
R Authorize/Use [Table Number] key

Tables



R 412 through 421 - Pickup Check by Table


R 510 through 519 - Add/Transfer by Table

R 522 - Table Number
1 Tables
2 RVC Information | Tables | General | <Select RVC> | Insert

R Table ID field
Related Topics
w “Check Number” on page C-22
w “Seat Handling” in Chapter 9 of the 9700 Feature Overview Manual
T-16
Tax
Tax
Description
There are two Tax handling files used to assign taxes to menu items, discounts,
and service charges: Tax Rates and Tax Classes.
Tax Rates are the rates that the nation, state, province, or city charge on sales of
menu items or on service charges. For example, a state might charge a 4% tax on
prepared foods, but not on alcoholic drinks. The state may charge a 10% tax on
room rental fees, but not on cover charges.
The combination of all the tax rates that apply to a certain menu item comprise
that item’s Tax Class. For example, if alcoholic drinks are subject to a state tax of
4%, a city tax of 1%, and a federal tax of 1%, the tax class of alcoholic beverages
will include all of these, and 6% tax will be calculated on the menu items.
Definitions
European Value Added Tax (VAT)

VAT is a form of sales tax used in some countries. VAT is an “Inclusive Tax”,
which means the tax is included in the menu item price. In the 9700 System, the
“global” tax type may be set as European or United States (System Information |
Taxes | Options). VAT tax is calculated differently, depending on the global
setting. In Europe only inclusive type tax will be calculated. In the United States,
inclusive type tax and add-on type tax can be used at the same time.
U.S. Inclusive Tax

U.S. inclusive tax uses the item price and a percent value to calculate the tax
amount. The tax is then included in the price of each menu item not added to the
bill. For example, if the tax rate is 5% and the item price is $5.00, then the
inclusive tax method calculates by the formula: $5.00/(1 + 5%) = $4.76. The total
price to the customer remains $5.00, but the net sale price is $4.76 and the tax is
$0.24. If U.S. Inclusive tax is used, only one inclusive tax rate may be applied to a
menu item.

Tax
Add-on Tax
This method uses the item price to calculate tax, which is then added to the bill.
For example, if the tax rate is 5% and the item price is $5.00, the system calculates
5% of $5.00, posting $0.25 tax to the check for a total due of $5.25.
Breakpoint or Threshold Taxes

Breakpoints are used to establish the points at which an increase of one cent in
sales will increase tax by one cent. For example, a breakpoint tax might be one
percent for sales from zero to twenty cents and then two percent from twenty-one
to forty cents. Twenty cents would be the breakpoint for this tax.
Tax Types
The tax type is first defined for the entire system, i.e. European or U.S. Each tax
rate table also has a Tax Type which identifies the calculation method.
Tax Table Type Description
0 - Disabled This setting disables the tax calculation for this

tax type.
1 - Add-on, Breakpoint This Add-on tax is calculated using the
Breakpoint Method and added to the check
total. A Breakpoint chart is obtained from the
government body imposing the tax to facilitate
the programming of the breakpoint entry table.
2 - Add-on, Percentage This Add-on tax is calculated using Flat
Percentage Rate and added to the check total.
3 - Inclusive, Percentage This inclusive tax is calculated using a Flat
Percentage Rate to determine what portion of
the sale price is tax. Since the tax is included in
the price, it is backed out of gross sales on
reports. It cannot be backed out of a check total
using one of the [Exempt Tax] keys.
Note: The inclusive tax is applied differently

depending on the global tax type (European or
U.S.). See the Tax Usage Summary chart on page
T-22.
T-18
Tax
Tax Exemption
Tax exemption may be used to forgive one or more tax types on a sales
transaction. The 9700 system allows taxes to be exempted or masked in a variety
of ways, as listed in the table below.
Method Description
Keyboard [Exempt Tax] key(s) placed on the keyboard

provide a manual method of exempting all tax
rates, or only certain tax rates.
Tender/Media Tender/Media keys can exempt Tax Rates 1- 8.
When one of these tenders is applied to a guest
check, the tax is removed and the balance adjusted.
Tender/Media keys can be programmed to process
tax exempt coupons. Refer to “Tax Exempt
Coupon” on page T-31.
Serving Periods Serving Periods can mask certain tax types. For
example, an Entertainment Tax can be exempted
during serving periods when there is no music.
Order Types Order Types can be used to selectively apply
certain tax rates. For example, “Eat In” vs. “Take
Out” orders may require different taxes. Tax rates
programmed for Order Types are overridden by any
programmed for the active Serving Period.
Menu Item Price File’s Specific Tax Classes may be disabled for each
Tax Class Override field menu item by overriding the tax class link in the
Menu Item Class File.
Tax Exemption can only be applied to add-on taxes.

Tax Exemption has no effect on inclusive or VAT
taxes.
If a Tax Exemption is programmed to require a reference entry, the entry is

prepended with “TAX #:”.

Tax
Tax Exempt Vouchers

A Revenue Center can be programmed to print a voucher for a transaction in
which a tax rate is exempted (either by a [Tax Exempt] key, or by a [Tender] key
that is programmed to exempt taxes). This feature is controlled by the Tax option
Print Tax Exempt Voucher in the Revenue Center Parameters file. The voucher
includes a signature line, to allow the voucher to be signed by either the customer
receiving the exemption, or the employee granting it. Vouchers print at the
validation printer designated for the UWS being used. The illustration below
shows an example of a tax exemption voucher, followed by a description of each
line item.
1 TAX EXEMPTION VOUCHER

2 -------------------------------------------------------
3 CHECK: 474
4 SERVER: 101 JOE
5 DATE: SEP25’94 8:30AM
6 RVC: LOUNGE
7 TAX RATE: STATE - 5%
7 TAX RATE: CITY - 2%
8 REFERENCE: E524-777-585-741
9 X -------------------------------------------------
Line Item Description
1 This line describes the voucher being printed.

2 A single line prints between the header and the detail items.
3 This line prints the guest check number (or transaction
number) in double-wide format.
4 This line prints the Employee Number and Check Name of the
transaction operator.
5 This line prints the date and time that the voucher printed.
6 This line prints the name of the Revenue Center in which this
exemption was applied.
T-20
Tax
7 If the [Exempt All Taxes] key is used, this line prints ALL
TAXES. If an individual tax rate is exempted (either by a [Tax
Exempt] key or by a [Tender] key programmed to exempt
taxes), this line prints the name of the tax being exempted, as it
appears in the Tax Table. If more than one tax rate is
exempted, this line is repeated for each tax rate. Note that in
the example shown, two separate exemptions were performed:
one to exempt Tax Rate 1, the State Tax, and one to exempt
Tax Rate 2, the City Tax.
8 If a [Tax Exempt] or [Exempt All Taxes] key is used, and if
the Revenue Center is programmed to prompt for a reference
entry when tax is exempted, this line prints the reference entry.
If a [Tender] key is used to exempt taxes, or if the Revenue

Center is not programmed to require a reference entry, this
line does not print.
9 A single line prints to allow a signature, if required.
Usage
The 9700 supports tax systems used in many countries, including:
w Canadian GST and PST Taxes
w European Value-added Tax (VAT)
w Japanese Tax
w Philippine Tax
w Singapore Tax
w Taiwanese Tax
w Thai Tax
w United States Taxes (add-on and/or inclusive)

Tax
Tax Usage Summary
Tax Table
Tax Method Type(s) Description
Allowed
Canadian Type 1 or 2 Tax Rate 1 is always GST. Tax rates 2 through 4

GST are used for optional PST (Provincial Tax) and
may be programmed to compound on the GST.
Rates 5 through 8 may be used as non-
compounding provincial taxes.
European Type 3 Tax is an inclusive tax. The difference between
VAT VAT and U.S. Type 3 tax are:
1. VAT must be applied system-wide, although
you may have 8 VAT rates.
2. Tax-exempt sales are not allowed.
3. Tax reports show gross sales, net sales (net of
VAT), and tax.
Japanese Type 1 or 2 Japanese Consumption Tax is always Tax Rate 1
and Type 2 (percentage add-on). Japanese Excise
Tax is always Tax Rate 2 and Tax Type 2
(percentage add-on).
Philippine Type 2 Tax is add-on. The difference between this tax
and U.S. is that all tax rates print on the guest
check, even if they are zero.
Singapore Type 1 or 2 May be flat, add-on, or breakpoint.
The difference between this and U.S. is that the
tax total on a taxable itemizer is always rounded
up to the nearest 5 cents.
Taiwanese Type 3 Tax is a flat 5% inclusive tax.
Thai Type 1 or 2 May be flat, add-on, or breakpoint.
This option prints 4 tax information lines at the
end of guest checks, customer receipts, and
journals.
U.S Add-on Type 2 Tax is add-on. Start amount may be set to be the
lowest price at which menu items are taxed. This
tax type can be exempted. Use when tax is a flat
rate add-on.
U.S. Type 1 Tax is add-on. Start amount may be set to be the
Breakpoints lowest price at which menu items are taxed. Use
when local tax table is breakpoint.
T-22
Tax
Tax Table
Tax Method Type(s) Description
Allowed
U.S. Type 3 Tax is inclusive. Differences between this tax and

Inclusive VAT:
1. Only one U.S. inclusive tax can be active for
each menu item.
2. U.S. inclusive tax can be used with other U.S.
tax types.
3. U.S. inclusive tax does not appear in tax
subtotal on checks.
4. Tax reports show only net sales (net of all tax
types) and tax.
5. U.S. inclusive cannot be tax exempted.
Reports
Establishment Tax Report

This report summarizes tax collections during a period (Current, Previous, or
Periods 1 - 9) for the entire system, a revenue center or a UWS. For the eight
available tax rates, taxes are reported in the following order: sales total, tax
collected, and exempt sales. Additionally, a total of non-taxable items is provided.
When the Value Added Tax (VAT) or Canadian GST Type Tax is used, the
format will be slightly different. Refer to the 9700 Reports Manual for more
information.
Financial Reports
w Tax Collected field

Tax
Enabling
1 System Parameters

R Post MI, Major/Family Group Sales Totals Net of VAT

R Enable French VAT Reporting
1 Taxes
2 System Information | Taxes | General

R Global Tax Options fields
R Tax Rate fields 1 through 8
2 System Information | Taxes | Options | Country=Canada

R Complete fields, if applicable
2 System Information | Taxes | Tax Class

R Fill in all fields, as applicable.
1 Discounts

R Treat Percentage Discount as an Amount Discount When
Calculating Taxes—This option is intended to improve the accuracy
of tax calculation in situations where there is a need to apply a
percentage subtotal discount to a seat or group of seats and
immediately memo tender the filtered seat(s).
R Tax Class field
T-24
Tax
1 Menu Item Class
R Tax Class field
Menu Item Class> | <Select Menu Item> | Pricing
R Tax Class Override field
1 Service Charges

R Tax Class field

R Tax Options, including:
w Do Not Include Tax in Totals on Tip Reports
w Require a Reference Entry with Tax Exemptions
2 RVC Information | RVC Parameters | Order Types | Tax Options

R Order Type fields—Set the active tax rates for each order type.

R Display an “E” in Customer Display if Exempt

R Display Tax & Autogratuity When Chk Initially Displayed
2 RVC Information | RVC Descriptors | Headers and Trailers |

Trailer=Canadian Tax Trailer
R Canadian Tax Trailer Line fields 1 - 6 (Canadian GST only)

Tax
1 Employee Class

R Authorize/Perform Tax Exemptions Using [Exempt Tax] keys
1 Serving Periods
2 RVC Information | Serving Periods | <Select Serving Period>

R Tax Option fields—Set the active tax rates for each serving period.
R Japan Excise Threshold Active field—This field is used for Japanese
Tax only.

Type=Function | Function Key Categories=Check Operations| Number

R 525 - Exempt All Taxes

R 526 through 533 - Exempt Tax Rate 1 -8
T-26
Tax
Related Topics
w “Tax Exempt Coupon” on page T-31
w “Tax - Canadian (GST)” on page T-28
w “Tax - Japanese” on page T-38
w “Tax - Philippine” on page T-41
w “Tax - Singapore” on page T-43
w “Tax - Taiwanese” on page T-44
w “Tax - Thai” on page T-46

Tax - Canadian (GST)
Description
The Goods and Services Tax is a Canadian federal add-on type tax on most
goods and services. Special programming is available in the 9700 System to adapt
to the variety of relationships that may exist between the federal sales tax (GST)
and each provincial sales tax (PST).
Definitions
Goods and Service Tax (GST)

This is a federal tax on goods and services effective in Canada on January 1, 1991;
the rate was set at 7%. It applied to most services and all goods except groceries.
Tax Rate 1 is reserved for the GST.
Provincial Sales Tax (PST)

PST is a tax applied by an individual province. Some provinces charge a local
PST in addition to GST while some do not. A PST may be calculated on the sales
balance, or it may be calculated on the total of sales plus GST. Tax Rates 2
through 8 are available for use for PST rates. (Only rates 2 through 4 may be
programmed to compound on the GST.)
Incremental Tax
Incremental taxes are calculated separately and are added to the sale. For example,
on a $15.00 meal, GST is applied at 7% and PST is applied at 8% on the same
meal. The equation looks like this:
Entree $15.00
GST (7% of 15.00) 1.05
PST (8% of 15.00) 1.20
Total Due $17.49
T-28
Compounding Tax
PST may be calculated on the price of the item plus the GST. Only Tax Tables 2,
3, and 4 can be identified as compounding taxes. An example may be a single
$15.00 item, where PST is applicable and a 7% compounding GST is charged:
Entree $15.00
GST(9% of 15.00) 1.44
Subtotal 16.44
PST (7% of 16.44) 1.15
Total Due $17.59
Taxable Itemizers 1/2, 1/3, and 1/4

Three additional tax itemizers are available when using compounding tax (see the
description on the previous page). An itemizer is considered a bucket that holds
the sale amount of all items taxed at the specific tax rate. At the end of a
transaction, the tax is then applied to the subtotal of all items in the bucket. The
expected taxable itemizers are Taxable Itemizers 1, 2, 3, and 4, which correspond
to the first four tax rates1.
When Canadian GST is enabled, the 9700 creates three additional taxable
itemizers, referred to as Taxable Itemizer 1/4. These itemizers will be used to hold
items taxable at both tax rates 1 and 2, items taxable at both tax rates 1 and 3, and
items taxable at both rates 1 and 4.
Threshold
The threshold for each tax rate is the point of the sale (dollar amount) at which
that tax becomes active. This is similar to the “Start Amount”, but more complex
in that this start amount can be dependent on whether another tax was applied, or
whether this PST is compounding on GST. In programming the 9700 for GST, the
threshold fields will be used differently for Tax Rate 1 than for Tax Rates 2
through 4.
1. Even though tax itemizers are not specifically programmed in the 9700 System, the general concept is the
same as in the 2700 and 4700 Systems. In the 9700 System, Menu Item Classes are linked to Tax Classes
which are, in turn, linked to Tax Rates 1-8. When you link to a tax rate, you are, in effect, creating an
itemizer “bucket” for that item.

Enabling
1 Taxes
2 System Information | Taxes | Options | Country=Canada

R Enable Canadian GST
R Complete fields on this form as applicable

R Tax Rate fields

Trailer=Canadian Tax Trailer
R Canadian Tax Trailer Lines 1 - 6
Optional Settings
1 System Parameters

R Canadian GST: Combine Rates 2 thru 8 on Sys. Tax Report
T-30
Tax Exempt Coupon
Tax Exempt Coupon
Description
Tax exempt coupon is a type of Tender/Media that can act as a partial tender while
exempting a prorated portion of tax. This differs from the standard Tender/Media
tax exempt feature, which exempts the entire amount of tax, regardless of the
amount tendered.
Usage
To enter a tax exempt coupon, type the dollar amount of the coupon and press the
[Tax Exempt Coupon] Tender/Media key. The System deducts the amount of the
coupon from the balance due, and calculates and deducts the amount of tax to be
forgiven.
After a [Tax Exempt Coupon] key is used, additional sales cannot be posted to the
check, nor can the order type be changed.
A [Tax Exempt Coupon] key cannot be used to overtender a guest check, either to
create a charged tip or change due. If the balance due is less than the amount of
the tax exempt coupon, tendering the coupon simply closes the check.
Tax Exempt Calculation

The System forgives tax based on the percentage of the amount of the coupon to
the amount of sales.
Example
The amount of sales on a guest check is $43.00, and the sales tax rate is 5%.
The balance due is $45.15. The customer presents a tax exempt coupon in the
amount of $7.00 as partial payment of the check.
The operator types [7][.][0][0] and presses [Tax Exempt Coupon].

Tax Exempt Coupon
The System subtracts $7.00 from the balance due on the guest check, and
$0.35 of the $2.15 in sales tax is forgiven. The following calculations are used
to determine the amount of tax forgiven:
Coupon Amount 7.00
= = 16.28% forgiven
Sales Amount 43.00
Sales Tax X Percentage forgiven = Tax forgiven

2.15 X 16.28% = .35
The illustration below shows the guest check that would result from this
transaction.
1 CHEF SPECIAL 21.50

1 CHEF SPECIAL 21.50
COUPON 7.00 X
TAX FORGIVEN 0.35
SUBTOTAL 43.00
SALES TAX (5%) 1.80
BALANCE DUE 37.80
Enabling
1 Tender Media

Category to Display=Taxing Options
R Tax Exempt Coupons
R Exempt Tax Rate 1 through 8—These Type Definitions determine
which tax rate(s) will be forgiven when this [Tax Exempt Coupon] key
is used.
T-32
Tax Exempt Coupon

Type=Tender Media | Number

Keyboard> | Key Configuration | Type=Tender Media | Link
R [Tax Exempt Coupon] Tender/Media key
Optional Settings

R Print Tax Exempt Coupon “Tax Forgiven” Amount
1 Tender Media

R Privilege Group field—Designate a privilege group (1, 2, or 3) to
restrict the ability to post this Tender/Media to certain employees.
1 Employee Class

R Authorize/Perform Posting of Tender/Media in Priv. Groups 1, 2, & 3
Related Topics
w “Tax Exemption” on page T-19

Tax - Florida Surcharge
Description
The Florida Liquor Surcharge Tax feature provides the ability to apply a
predefined dollar value surcharge to a menu item. This feature is designed to meet
taxation requirements that are specific to the State of Florida and, therefore,
should only be used by those establishments operating within the State of Florida.
Usage
Overview
The State of Florida has adopted a tax regulation that places a surcharge on the
sales of all alcoholic beverages. The surcharge is referred to as the Florida Liquor
Surcharge and applies whether the beverage is sold by the drink or by the
container (wine, beer, etc.). The 9700 System uses the Tax feature to
accommodate the accounting and reporting requirements associated with this
surcharge.
Tax Regulations
The liquor surcharge applies to alcoholic beverages only. The amount of the
surcharge applicable to alcoholic beverages is governed by the State of Florida. A
surcharge cannot be exempted or discounted and is assessed in addition to any
other applicable taxes. The surcharge itself is not taxable.
Guest Check Display Format

When a menu item that includes a surcharge is posted, the surcharge amount will
post to the Tax amount in the Summary Totals section of the displayed guest
check. Regular sales tax and the surcharge tax are consolidated together in the
same total.
T-34
Guest Check Printed Format

When a guest check that includes a surcharge is printed, the amount of surcharge
is printed separately on the guest check. The System uses the Tax Collected to
display the surcharge total. The name that appears adjacent to the total
corresponds to the descriptor programmed in the Tax Table.
A guest check that includes a Florida Liquor Surcharge could appear as follows:
MICROS 9700
Fine Dining System
1001 Mikey
--------------------------------
6/1 3650 GST 5
JAN03’96 11:36PM
--------------------------------
1 GLASS WHITE 2.50
1 HOUSE COCKTAIL 2.85
1 CALL COCKTAIL 3.00
2 CHICKEN WINGS 4.50
1 HOUSE CORDIAl 3.10
Cash 18.75
SUBTOTAL 15.95
TAX .80
FLA Surcharge FLA Surcharge 2.00
TOTAL 18.75
---1001 CLOSED JAN03 11:55PM---

Prompts
Prompt What it Means Action Required
Surcharge in tare The amount entered in the Change amount in tare

weight field in menu tare weight field in the weight field in the
item definition too
Menu Item Definition Menu Item Definition
large
File exceeds 655.35. File to be below
655.35.
Reports
Tax Report
When the Florida Liquor Surcharge tax option is activated, collected taxes will be
summarized on the Establishment Tax Report. Surcharge tax information will
appear on the report as it was programmed in the Tax Table. The surcharge tax
descriptors appearing on the report will correspond with those defined in the Tax
Table.
For example, the Tax Summary Report contains the Florida Liquor Surcharge
information as follows:
FLA Surcharge
T-36
Enabling
1 Menu Item Class
R Surcharge field—This field is used to indicate the amount of the
surcharge.
1 Taxes
2 System Information | Taxes | General | Type

R Florida Surcharge—Set any Tax 1 - 8 with the tax type of Florida
Surcharge. The descriptor which prints on the guest checks is specified
in the Tax Collected field.
2 System Information | Taxes | Tax Class

R Type field—Program Florida Surcharge
Related Topics
w Refer to the 9700 Reports and Programming Manuals.

Tax - Japanese
Tax - Japanese
Description
Japanese Tax consists of the following two taxes.
w Consumption Tax (Tax Rate 1 is reserved for this.)
w Excise Tax, also called the Local Tax (Tax Rate 2)
An Excise Tax may be imposed by a local government, in addition to the national

Consumption Tax. If the Excise Tax is used, there is usually a threshold sale
amount below which tax is not applied. The Consumption Tax and any Excise
Tax are shown on separate lines on the guest check.
Definitions
Consumption Tax
This is a national, flat percentage add-on tax. The itemizer is calculated on a
subtotal of all items in the transaction. It is always defined as Tax Rate 1, with a
start amount of 0¥.
Excise Tax
This is a local tax calculated by using a subtotal of transaction items that are
subject to the Excise Tax. It is always defined as Tax Rate 2. The start amount is
variable and is applied or not based on the revenue center requirements. The
subtotal on which the Excise Tax is calculated is required to include all service
charges, including any auto service charges.
If Excise Tax is not used, you must disable Tax Rate

2.
T-38
Tax - Japanese
Threshold
When enabled, the threshold is the taxable transaction amount, where an
applicable Excise Tax begins to apply. The threshold value is calculated this way:
IF (Subtotal) divided by (Guest count) >= Tax Rate 2 Start Amount

THEN calculate Tax Rate 2,
OTHERWISE ignore Tax Rate 2.
When a threshold is active, it first determines the average taxable subtotal per
guest and compares it to the Tax Rate 2 Start Amount. If the average amount per
guest is greater, the Excise Tax (Tax Rate 2) is applied. The Excise Tax is always
applied if the guest count is 0.
Enabling
1 Taxes
2 System Information | Taxes | Options | Country=Japan

R Enable Japanese Tax—Enable this option.

R Apply Tax As field—Select Add-On.
R Tax Rate 1 (Consumption Tax)—Set Tax Type to Add-on,
Percentage. Enter the percentage amount, and set the Start Amount
field to 0.
R Tax Rate 2 (Excise Tax)—Set Tax Type to Add-on, Percentage. Enter
the percentage amount and, if the threshold is enabled in any revenue
center, set the Start Amount to equal the threshold value.
2 RVC Information | RVC Parameters | Taxes | Tax Options

R Print Japanese Amount Due
R Allow Discounts to Affect Japanese Excise Tax Threshold—If this
option is enabled, the applicable discounts must be linked to a Tax
Class that has Tax #2 (the Excise Tax) active.

Tax - Japanese
1 Tender Media

R No Japanese Tax Threshold
1 Serving Periods
2 RVC Information | Serving Periods | General

R Japanese Excise Threshold Active
Related Topics
w “Tax” on page T-17
T-40
Tax - Philippine
Tax - Philippine
Description
The Philippine government uses levies, an add-on sales tax. The difference
between Philippine tax and U.S. add-on tax regards guest check printing:
w Tax Rates that have non-blank descriptors print.
w Tax Rates that have zero amounts do not print.
w Tax Rates that have blank descriptors do not print (although posting still
occurs.
Enabling
1 Taxes
2 System Information | Taxes | Options

R Country—Select Other.

R Apply Tax As—Select Add-On.
R Print Tax Itemizers—Enable this option (required).
R Tax Rates Table—For each Tax Rate (1 - 8) used, complete all fields:
w Tax Collected—Enter a descriptor for every Tax Rate that should
print on the guest check and customer receipt. Tax Rates for which
this field is blank do not print.
w Tax Type—Select Tax Type 2 (Add-on, Percentage).
w Start Amount—Enter the amount of sales at which to begin

applying this Tax Rate.
w Percent—Enter the tax percentage.

Tax - Philippine
Related Topics
T-42
Tax - Singapore
Tax - Singapore
Description
Singapore tax may be flat, add-on, or breakpoint. The difference between this and
the U.S. tax is that the amount of the tax total on a taxable itemizer is always
rounded up to the nearest 5 cents.
Enabling
1 Taxes

w Tax Type—Select Tax Type 2 (Add-on, Percentage).

w Percent—Enter the tax percentage.

R Country—Select Singapore.
R Enable Singapore Tax
Related Topics

Tax - Taiwanese
Tax - Taiwanese
Description
Taiwanese Tax is a flat inclusive tax.
Usage
The printing format of the Government Uniform Invoice (GUI) may vary between
establishments. The 9700 System provides all of the necessary information (e.g.,
serial numbers, guest check detail) that is required to create a GUI. A custom-
made GUI guest check is then created for each restaurant using Interface Script
Language (ISL).
The tax rate in effect may change during the course of a business day. This change
can be performed using an ISL script.
In many Taiwanese establishments, certain customers may borrow cash from the
restaurant during the course of the meal, which the customer then repays with a
credit card when the check is presented. In order to satisfy accounting
requirements, a special type of tax-exempt service charge is used to record
payment of the loan.
Enabling
1 System Parameters

R PC Containing System Serial Number field
R Minimum System Serial #1 field
R Maximum System Serial #1 field
R Minimum System Serial #2 field
R Maximum System Serial #2 field
R Tax Number Prefix field
R End of Range Threshold field
T-44
Tax - Taiwanese
1 Taxes

R Country—Select Taiwan.
R Enable Taiwanese Government Uniform Invoice (GUI) Handling
R On System Level

R Number of Guest Check Information Lines field

R Minimum Revenue Center Serial #1 field
R Maximum Revenue Center Serial #1 field
R Minimum Revenue Center Serial #2 field
R Maximum Revenue Center Serial #2 field
R Tax Number Prefix field
R End of Range Threshold field
1 Service Charges

R Taiwanese Paid Out
Related Topics

Tax - Thai
Tax - Thai
Description
Thai tax may be flat, add-on, or breakpoint. This tax format prints up to 4
additional lines of information, including tax numbers and tax ID numbers, on the
journal, guest checks, and customer receipts.
Usage
Thai tax printing for a typical guest check is shown below, followed by a
description of each line item. The format for customer receipts and the journal is
similar.
AMOUNT TENDERED 25.00

1 CHANGE DUE 15.00
2 TAX INVOICE (ABB) 940925–01–00123š

3 ACCOUNT REC š 940925–01–00079
4 TIN 8602718351850842
5 RD NUMš 9372549849284915
6 – – – – 499 CLOSED SEP25 12:35PM – – – –
1 This is the last line of guest check detail before the Thai Tax
trailer lines print.
2 This Tax Invoice Line prints the date (in the format
YYMMDD), followed by the last two digits of the Revenue
Center number, followed by the System Level Running Tax
Number. This last number increments with each transaction.
3 This Account Rec line prints the date (in the format
YYMMDD), followed by the last two digits of the Revenue
Center number, followed by the Revenue Center Level
Running Tax Number. This last number increments with each
transaction.
4 This line prints the Revenue Center Tax ID Number.
T-46
Tax - Thai
5 This line prints the User Workstation Tax ID Number.

6 The check closed line prints at the end of the guest check.
Voiding Tenders
When Thai Tax is in use, tenders should only be voided using direct voids. If line
number void or last item void is used to void a tender, the tax lines will not print.
Adjust or Re-open Closed Checks

If a closed guest check is adjusted or re-opened and altered while Thai Tax is in
use, the System Level Running Tax Number and the Revenue Center Level
Running Tax Number will increment when the check is closed again.
If the tender that uses Thai Tax is voided, the tax lines will not print.
Split Checks
When a tender that uses Thai Tax is split to another check, the tax lines print on
the new check, and not on the original.
Enabling
1 System Parameters

R PC Containing System Serial Number field—Select the PC in which
the System Serial Numbers are stored.
R Minimum System Serial #1 field—Enter the minimum allowable
value for the running tax number for the System. The range for this
entry is a 5-digit integer (00001 - 99998).
R Maximum System Serial #1 field—Enter the maximum allowable
value for the running tax number for the System. The range for this
entry is a 5-digit integer (00002 - 99999).

Tax - Thai
1 Taxes

R Country—Select Thailand.
R Enable Thailand Tax Printing

w Tax Type—Tax may be flat, add-on, or breakpoint.

w Percent—Enter the tax percentage, if applicable.
1 Tender/Media

R Print Tax Invoice Line—Enable this option to print the Tax Invoice
line on guest checks, customer receipts, and the journal. If this is set
ON, it also causes both the Revenue Center Tax ID and the User
Workstation Tax ID lines to print.
R Print Account Record Line—Enable this option to print the Account
Rec line on guest checks, customer receipts, and the journal. If this is
set ON, it also causes both the Revenue Center Tax ID and the User
Workstation Tax ID lines to print.
T-48
Tax - Thai

R Number of Guest Check Information Lines field

R Minimum Revenue Center Serial #1 field—Enter the minimum
allowable value for the running tax number for this Revenue Center.
The range for this entry is a 5-digit integer (00001 - 99998).
R Maximum Revenue Center Serial #1 field—Enter the maximum
allowable value for the running tax number for this Revenue Center.
The range for this entry is a 5-digit integer (00002 - 99999).
R Minimum Revenue Center Serial #2 field—Set to 0 for Thai tax.
R Maximum Revenue Center Serial #2 field—Set to 0 for Thai tax.
2 RVC Information | RVC Descriptors | Headers and Trailers | Trailer=Thai

Tax Trailer
R TIN Descriptor field—Enter the Revenue Center Tax ID Number
(TIN) for this establishment.
R RD Number Decriptor field—Enter the Revenue Center RD NUM.
1 Devices

R Thai Tax RD Number field—Enter the User Workstation Tax ID
Number (RD NUM).
Optional Settings

R Thai Tax Trailer Uses UWS Number Instead of Revenue Center
Number—Enable this option to use the UWS RD number instead of
the Revenue Center RD number in the Tax Invoice and Account Rec
lines.

Tax - Thai
Related Topics
T-50
Tender/Media
Tender/Media
Description
Tender/Media is a generic name for a variety of functions that are used in sales
transactions (i.e., to account for the flow of cash and value of goods and services
rendered when a service round or transaction is completed and totals posting
occurs).
Usage
The Tender/Media File is a variable-length file. Five types of entries are made in
this file:
Payment
An amount entered by this type key subtracts from the amount due on the current
transaction balance, e.g., open check. If the result is 0, the check is closed and the
transaction finalized. Examples of payment keys include: cash, credit cards, and
foreign currency. Payment keys can be created to record special activity, such as
house charges, walk-outs, and employee meals.
Service Total
This key ends the current transaction and saves the check information in the Open
Check Totals and Detail Files for later recall. This type key is also used for
[Reprint Check], [Print Check], [Chain/Fire], [Hold/Fire], [Seat Check], and
[Print Memo Check] keys.
Pickup
This key records the withdrawal of cash from a cash drawer, such as payment of
petty cash, or when deposits are made in the middle of a high-volume shift to
reduce liability at each UWS. It is also used to record tips paid.
Loan
This key records the addition of cash to a cash drawer, such as the beginning bank
for a shift.

Tender/Media
Preamble
This entry is not entered on the keyboard. It is entered in the Tender Media file in
the record immediately preceding the one used for the credit card payment.The
preamble is used in conjunction with a Credit Card payment key when that credit
card has more than one possible preamble to the credit card number. For
information about preambles, see “Credit Card” on page C-40.
Percent Tender
This key is used when a customer wishes to pay a percentage of the check. To use
this feature, the operator presses the [Percent Tender] key. The system prompts,
“Enter payment percent”. The operator types in the percentage being paid, and
presses the appropriate tender key.
Reports

All tender/media types (except service totals and preambles) can be tracked.
Financial Reports, Time Period Report, Serving

Period Report, Income Audit Report
Payment and Preamble type tender/media are used in a variety of calculations
(e.g., Check payment, Count, and Total fields).
Closed Check Report

Tender/media payment information is included.
Employee Tip Reports

If payment keys are programmed to post to Gross Receipts and/or Charged
Receipts, tender/media information is included.
T-52
Tender/Media
Enabling
1 Tender Media

R Define each Tender Media function.
2 Touchscrns & Keyboards | WS Touchscreens | Touchscreen Screen | Type

Keyboard> | Key Configuration | Type
R [Tender/Media] keys
R [Service Total] key
R [Print Check] key
R [Media Loan] key (optional)
R [Media Pickup] key (optional)

R Default Cash Tender/Media field
R Default Bank Loan Tender/Media field
Optional Settings


R [Percent Tender] - keycode #640

Tender/Media
1 Discounts
2 System Information | Discounts |

R Tender Required (Only for Subtotal Discounts)


R Post Tender to Transaction Operator—If this option is disabled,
tenders will be posted to the Check Operator.

R Require Finalization of Check after Partial Tender
R Allow Void Of Tender/Media In Current Service Round Only
1 Tender Media
2 System Information | Tender Media | Key Type=Payment

R Privilege Group field—Designate a privilege group (1, 2, or 3) to
restrict the ability to post this Tender/Media to certain employees.

R Open Cash Drawer
R Use with Currency Conversion
R Employee Meal

R Print Check Trailer
R Print Check On Demand—This option prints the guest check for On-
demand operators.
T-54
Tender/Media

Category to Display=Credit Card Options

R Exempt Rate Tax 1 through 8

R Charged Tip Required—When this option is enabled, any tender
overage is considered a charged tip.
R Charged Tip Amounts field—Select Must be Less Than Payment
Amount.
R Charged Tip Service Charge field—This field is used to link charged
tip with Tips Paid.
R Post Amount to Gross Receipts on Tip Reports
R Post Amount to Charged Receipts on Tip Reports

Output
R Print On Guest Check—This option prints this Tender Media entry
line on the guest check.
1 Employee Class

R Authorize/Perform Posting of Tender/Media in Privilege Groups 1, 2,
and 3

Transactions | Other Employees’ Checks
R Post Payments to Checks Belonging to Another Operator

Tender/Media
Related Topics
w “Charged Tip” on page C-18
w “Credit Card” on page C-40
w “Employee Meals” on page E-11
w “Media Pickup/Loan Tendering Keys” on page M-10
w “No Sale Key” on page N-1
w “Open Check Block Settlement” on page O-4
w “Service Total” on page S-26
T-56
Tender Multiplication
Description
The Tender Multiplication feature provides the ability to quantify a tender entry.
Doing so eliminates the need to individually enter a tender/media of the same
denomination. For example, five $10 gift certificates can be quantified and
entered as a single entry in lieu entering each certificate individually.
Usage
Tender Multiplication can be applied to a transaction in two different ways; in
conjunction with a macro or as a stand-alone function
Using Tender Multiplication With a Macro

The power and flexibility of macros can also be linked to the Tender
Multiplication function. You can use Tender Multiplication to quantify the
content of tender/media in a macro instruction.
When the Tender Multiplication function is used with a macro, the tender is
multiplied, not the macro. The macro is only run once. Multiplied information
will print and display in a consolidated format. 1
Using Tender Multiplication Outside a Macro

The Tender Multiplication feature can also be applied to a transaction by way of
the [@For] key. The [@For] function key is used to separate the count from the
tender amount. For example, 3 [@For] [$10 Cash] will post a payment of $30 to
the guest check. Multiplied information will print and display in a consolidated
format.
1. If Revenue Center Parameters file Format Option # 1 (Print Unit Price as Well as Line Total on Checks) is
set on, the System will also display the unit price. For example, you might see transactions detail that
looks like this: 7 Wings DBL @ 10.95 76.65

Usage Guidelines and Considerations

Before you use the Tender Multiplication feature, review the information that
follows to familiarize yourself with the parameters that are applied to its use and
operation. Notice that this feature requires no special programming to activate it.
Parameter... Explanation...
@For Function When used in connection with the Tender

Multiplication feature, the [@For] key functions
as follows:
w The [@For] key can be used with the Tender

Multiplication feature with tender media keys,
preset tender macros, and tender/media within
a macro as long as Macro Type Definition
Apply Count to Tenders in the Macro is
enabled.
Autosequences, Reports, Does not work in conjunction with a macro key
and Procedures that is used to initiate autosequences, reports,
and/or manager procedures. The System ignores
any entry that precedes this type of macro.
Macro Key - Newly Defined You can multiply the tender content of a macro
(for example, preset tender macro) by entering a
numeric value before pressing the appropriate
[Macro] key. When you do so, the System will
function as follows:
w The specified count (quantity) will be applied

only to the tender component of the macro.
w The System will not quantify a macro unless it
is programmed to do so (Macro Type
Definition Apply Count to Tenders in the
Macro is enabled).
Macro Key - Existing This feature is compatible with existing macro
Definitions key definitions. If you would like existing
macros to respond to a quantity entry, make sure
that Macro Type Definition Apply Count to
Tenders in the Macro is enabled for each of
them.
T-58
Procedure - Tender Multiplication and a Preset Tender

Macro Key
Complete each of the steps in this procedure if you would like to quantify the
contents of a [Preset Tender] macro key.
Step 1—Access the Appropriate Guest Check

As appropriate, use the Begin or Pickup Guest Check procedure to open a
new guest check or access one that is already opened.
Step 2—Tender the Guest Check

Enter a quantity and press the appropriate [Preset Tender Macro] key. For
example 3 + [$10 Coupon]. The System will respond by posting the
quantified tender amount to the guest check.
During this procedure you may encounter the following System prompts
and messages. Use the following information to help you respond to
them:
Prompt What it means Action Required
Percent of total You have attempted to Press [Clear] to

due not allowed use a count with a continue. The Tender
after AT key percent tender. Multiplication feature
cannot be used with the
percent tender function.
Procedure - Tender Multiplication and the @For Key

Complete each of the steps in this procedure if you would like to quantify
the contents of a [Preset Tender] macro key.
Step 1—Access the Appropriate Guest Check

As appropriate, use the Begin or Pickup Guest Check procedure to open a
new guest check or access one that is already opened.
Step 2—Tender the Guest Check

Enter a quantity, press the [@For] key, enter the tender denomination, and
press the appropriate tender key. For example, press 3 + [@For] + $5 +
[Coupon]. The System will respond by posting the quantified tender
amount to the guest check.

During this procedure you may encounter the following System prompts
and messages. Use the following information to help you respond to
them:
Prompt What it means Action Required
Percent of total You have attempted to Press [Clear] to

due not allowed use a count with a continue. The Tender
after AT key macro key that includes Multiplication feature
a percent tender. cannot be used with a
macro key that includes
a percent tender
function.
Enabling
Optional Settings
1 Macros
2 RVC Information | Macros

w Apply Count to Tenders in the Macro—Enable this option if Macro
should acknowledge a count.

w Print Unit Price as Well as Line Total on Checks
Related Topics
w “Macros” on page M-1
T-60
Time Cards and Time Chits
Description
A time card is a record of clock-in and clock-out entries for a single employee for
a single pay period. A time chit is a slip that records a single clock-in or clock-
out. A single clock in/out entry consists of the date and time, clock in or out status,
the job code, the time worked, and the pay accrued.
Time cards may be printed on a slip or roll printer. Time chits are usually printed
on a roll printer; time cards are usually printed on a slip printer. An employee may
reprint an entire time card by pressing a [Reprint Time Card] key. Privileged
employees (usually managers) may also adjust time cards to correct errors or
omissions.
Usage
Time cards provide a hard copy record of attendance. Time cards can be used in
manually calculating payroll and labor percentages.
Time chits provide a “validation” style record of a single time clock action. These
may be issued if the employee wishes a record of his time clock activity for
personal record-keeping purposes. Some restaurants use time chits as a
verification of clock-in status. For example, employees may be required to present
a time chit to show that they are clocked in (or out) in order to receive an
employee meal.
Enabling
1 System Parameters

R PC Containing Time Card Files field—Enable time cards by defining
the PC on which time clock files are stored. Define this PC in the
System Overhead File.
R Lines On Time Card field
R Line Feeds Before Time Card Header field

1 Devices

R Employee Time Chit field
R Employee Time Card field

Number

R 834 - Reprint Time Card key—This allows employees to reprint an

entire time card.
Optional Settings
1 Employee Class

R Authorize/Perform Reprint of a Time Card
R Time & Attendance options—These selections give the employee
privileges to use the 9700 Time & Attendance module.

R Use UWS Procedure #8: Adjust Employee Time Card
Related Topics
T-62
Time Clock Schedule
Time Clock Schedule
Description
The Time Clock Schedule is a security feature that allows only scheduled
employees access to the 9700 System. Additionally, by restricting clock in/out
times and break periods, labor cost can be more effectively controlled.
Definitions
Grace Period
The Grace Period is a window of time, in minutes, in which an employee may
clock in or out before or past their scheduled work time without penalty.
The System Parameters file and the Employee Maintenance file determine how
much time, in minutes, each employee will have as grace on either side of the time
they are scheduled to clock in or out in the Schedules file. Clocking in or out
outside of the grace periods may simply prompt the employee that they are late (or
early) or may require authorization.
Break
A break is a rest period, such as lunch break, for hourly workers that can be
tracked by the 9700 timekeeping system. Breaks can be either paid or unpaid. The
9700 system can be programmed to set time limits on breaks, and to have different
break period lengths for minors. The time spent on unpaid breaks subtracts from
the total time credited, for pay, by the 9700 system.
Usage
Time Clock Schedules restrict employees from clocking in if they are not
scheduled to work. The schedule can also be used to control the job codes for
which an employee is allowed to clock in.
From System Configurator, the Time Clock Schedule can be printed for reference.
The Time Clock Schedule may also be printed using User Workstation Procedure
#9.

Time Clock Schedule
Enabling
1 System Parameters

R Enable Time Clock Schedule—Enable this option.
R Time Clock Parameters—These fields define Paid and Unpaid Break
Periods, Clock In/Out Grace Periods, and Start of Labor Day/Week.
1 Schedules
2 Personnel | Schedules | <Insert>

R For each schedule entry, enter the employee number, clock in/out date/
times, and either the job code or the report group.
1 Employees

R ON = Employee Grace Period; OFF = System Grace Period
1 Employee Class
2 Personnel | Employee Maintenance | Sort By Class | <Select Class > |

R Use UWS Procedure #9: Change Time Clock Schedule—This is
usually set for managers.
R Use UWS Procedure #10: Print Time Clock Schedule—This is
usually set for managers.
T-64
Time Clock Schedule
Related Topics
w “Breaks” on page B-26
w “Labor Week Start Day” on page L-3
w “Job Rates” on page J-4

Time Periods
Time Periods
Description
Time Periods are used to track sales activity during specific time spans for
reporting and analysis purposes.
Usage
Windows of time that the restaurant wishes to track are set up in the Time Period
File. These windows may overlap, and be active on select days of the week.
Tracking Groups may be linked to individual time periods so that time period
reports may reflect sales activity for certain menu items within the specified
window of time. These may be useful in productivity planing.
Serving periods are similar, but not the same as

Time periods. Serving Periods must be changed
manually through Workstation Procedures and,
although up to 10 Time Periods may overlap at a
single time, only one can be active at a time.
Example
A restaurant wants to see when the most Prime Ribs are served on Friday night.
This way, the chef will know how many racks to prepare and when to start baking.
They set up a tracking group which will track the Prime Rib entree. Time periods
are programmed for every hour and the whole shift.
w 6 to 7 p.m.
w 7 to 8 p.m.
w 8 to 9 p.m.
w 9 to 10 p.m.
w 10 to 11 p.m.
T-66
Time Periods
w 6 to 11 p.m.
Reports
Time Period Detail Report

This report may be linked to a tracking group to track specific totals.
Time Period Summary Report

This report has a flexible format when taken from Report Writer or
Autosequencer.
Enabling
1 Time Periods
2 RVC Information | Time Periods | General

R Define each Time Periods (i.e., Start/End Times, Tracking Group link,
etc.).
Optional Settings
1 System Parameters
2 System Information | System Parameters |

w Omit Sum Sections and Ttl Lines from RW and UWS Time Pd Reports

Time Periods
1 Time Periods

w Print Only Tracking Groups on Time Period Detail Reports
w Active Sunday to Saturday—Time Periods can be programmed to be

active only on certain days of the week. For example, if lunch is served
only Monday through Friday, the “lunch” time period would only be
active on those days. (The PC’s clock/calendar knows the day of the week
for every calendar date.)
Related Topics
w “Serving Periods” on page S-30
T-68
Tips Handling
Tips Handling
Description
The 9700 provides Tips Handling features for keeping track of tips received from
either cash, credit card charges, or automatic gratuity. To meet IRS reporting
requirements, it also records tips paid to servers.
Definitions
Indirect Tips and Direct Tips

These represent cash tips from customers. Direct tips are those that a customer
gives in cash directly to a server or bartender. Indirect tips are those that the server
splits with other employees, such as a bus person. Employees use the [Indirect
Tips] key or [Direct Tips] key to enter the amount of tips they’ve received in cash.
(The system may be programmed to require an employee to declare tips when
clocking out.) This information is added to Tips Totals on the Employee Tip
Report and is used for Income Tax purposes.
Charged Tips
A Charged Tip is a gratuity credited to a server by adding it to a charge slip (such
as a credit charge slip or room charge slip). Thus, like the meal, the tip is
“charged” to a credit card, room account, etc. A charged tip is credited to the
check operator.
Service Charge
This is a generic term which refers to a variety of gratuities added to a check, such
as Autogratuties, Room Service Charge, Cover Charge, etc. This does not include
Indirect Tips or Direct Tips.

Tips Handling
Autogratuity
A service charge is automatically applied to all items posted to a check that are
programmed to add to the auto service charge itemizer (Menu Item Class option
Add to Automatic Service Charge Itemizer). The autogratuity is defined in the
Revenue Center Parameters File. It can be set to apply automatically to every
check, or to default to on (and can then be applied selectively by using an [Exempt
Auto Service Charge] key). A 15% auto service charge differs from a 15% regular
service charge in that it is constantly updated, even when checks are split, whereas
a regular service charge is applied all at once, at the end of a transaction.
Tips Paid
Tips which are paid out to the check operator are known as Tips Paid. Usually at
the end of a shift, the check operator is paid the value of the charged tip in cash
through a separate action, using the [Tips Paid] key.
Charged Tips can add automatically to the Tips Paid total on the Employee Tip
Report. In which case, no separate action is required, and the cashier simply
removes the cash from the cash drawer and pays the server. See the Cashier
Banking diagram in this section.
The system can be programmed to cause an operator’s Financial Report to be reset
after that operator receives tips through the [Tips Paid] key. This feature is useful
in 24-hour operations in which operators’ shifts may span the time selected for
resetting reports.
T-70
Tips Handling
Usage
Tip handling is an integral part of any restaurant operation. The 9700 System
provides two convenient and secure methods of recording and distributing tips;
Server Banking and Cashier Banking.
Tips Handling in a Server Banking Operation

This example illustrates a typical server banking operation. An actual restaurant
may vary some of the steps.
1
Server
Bank
$$
Media Loan or Servers close

5 Media Pickup guest checks 2
House Employee
4 Bank Financial Report 3
$$
Step 1
Servers are often issued a bank to make change for customers. Usually this is
performed as a Media Pickup from the house bank.
Step 2
Servers close their own guest checks using tendering keys. Servers usually
keep the closed checks and cash until the end of their shift. The Operator
Tracking Group records each server’s Tender/Media entries and charged tips
received.
Step 3
A manager takes an Employee Financial Report when the server is ready to
end their shift. The Employee Financial Report includes Tracking Group
Totals that add Charged Tips and Autogratuities to equal a subtotal labeled
Tips. This amount is entered for this employee, using the [Tips Paid] key.

Tips Handling
Step 4
After the Employee Financial Report is reviewed by a manager, the report is
used to “cash out”.
Step 5
Tracking Group Totals are used again for cash settlement. Tracking Totals
compute the server’s Total Cash (cash received + bank issued in Step 1) and
subtract the Tips Paid.
If the resulting total is negative, the house owes the server that amount. The
cashier uses a [Media Pickup] key to record the cash paid to the server from
the house bank.
If the resulting total is positive, the server owes the house that amount. The
cashier uses a [Media Loan] key to record placing the cash in the house bank.
Tips Handling in a Cashier Banking Operation

This example illustrates a typical cashier banking operation. An actual restaurant
may vary some of the steps. To use this method, the Revenue Center Parameters
must be set to post tenders to the transaction operator, and must require cashier
totals for tender/media entries.
1
Servers give
checks to cashier
Cashier closes
5 Tips paid out 2
guest checks
Cashier
Employee
4 Bank Financial Report 3
$$
Step 1
Servers give their guest checks and cash to the cashier for tendering.
T-72
Tips Handling
Step 2
The cashier closes guest checks using tendering keys. Cash accumulates in the
cashier bank during the shift. The Operator Tracking Group maintains a
record of the cashier’s tendering operations. Each server is also linked to a
separate Operator Tracking Group. This is done primarily to record charged
tips.
Step 3
A manager takes an Employee Financial Report when the server is ready to
end their shift.
Step 4
After the Employee Financial Report is reviewed by a manager, it is taken to
the cashier to “cash out”. The Employee Financial Report lists the amount of
charged tips owed to the server. The cashier enters the amount owed and
presses the [Tips Paid] key. The money is paid to the server from the cashier
bank.
If charge tips are linked automatically to tips paid,

the cashier simply removes the tips from the cashier
bank and pays the server.
Reports
Sales Balance Reports

Tips are posted to the transaction operator or the check operator, depending on the
setting of Revenue Center Parameters Posting Option #7: ON = Post Tenders to
Transaction Operator; OFF = Post Tenders to Check Operator.
w Service Charge field—Charged tips and autogratuity are combined. To
separate charged tips from autogratuity, they must be assigned to a tracking
group.

Tips Handling

w Tracking Groups (usually linked to the Employee Balance Report) provide a
way to track individual tip totals such as charged tips and autogratuity.
Example
In this Tracking Group Report, the servers tips are subtracted from Cash
receipts. If the server has more cash than was earned in tips, a Media Loan is
performed. If the server earns more in tips than their Cash receipts, a Media
Pickup is performed.
CASH 25.00
- CHARGED TIP 32.00
- AUTO SERVICE 10.50
----------------------------------
MEDIA LOAN/PICKUP 17.50 Pickup
After the report is printed, a Manager would circle either “LOAN” or

“PICKUP”. Then, the report is taken to a cashier for settlement.
Establishment Tip Report and Employee Tip Report

w Gross F & B Receipts—The System can be programmed to prevent certain
totals from posting to Gross F & B. These features provide the ability to
design a Tip Report that conforms to the requirements of the U.S. Internal
Revenue Service’s Form 8027.
The following sales can be included (or excluded) in the Gross F & B total on
Tip Reports:
w Revenue Center Sales (e.g., retail sales)
w Order Type Sales (e.g., carry out)
w Service Charges (e.g., delivery charges, room set-up, etc.)
w Tax Rates (Tax Rates 1 through 8)
w Service Charge Receipts—This is all service charges programmed to post to

the Service Charge field (Service Charge option Post to Service Charges
Total on Tip Reports). The tip report is designed to meet the requirements of
the IRS Form 8027, which requires that the Service Charge Receipts should
represent all tips that (a) will be paid to the employee as wages and (b) are
greater than 10% of the check total.
T-74
Tips Handling
w Direct Charged Tips—This is all tips charged to credit charge keys or

manually entered through the [Charged Tips] key.
w Tips Paid—A service charge can be set to automatically add to the Tips Paid
total (Service Charge option Post to Charge Tips Total on Tip Reports).
Enabling
1 Tender Media

R The Media Loan, Media Pickup, and Tips Paid functions are created in
this file. Fill in all required fields.

R ON = Use Employee Number with Tips Paid; OFF = Use ID Number
1 Service Charges
2 System Information | Service Charge | General

R Post to Charge Tips Total on Tip Reports
R Post to Service Charges Total on Tip Reports—Enable this option
for all service charges that add to the Service Charge field on the
Establishment Tip Report and Employee Tip Report.

Type=Tender/Media

Keyboard> | Key Configuration | Type=Tender/Media
R [Direct Tips], [Indirect Tips] keys

R [Media Loan], [Media Pickup], [Tips Paid] keys1—These function
keys must first be programmed in the Tender Media file.
1. The [Media Pickup] and [Tips Paid] keys are both “Pickup” type Tender/Media except that the [Tips Paid]
key has Type Definition #2 set ON.

Tips Handling
Automatic Tips Paid1
1 Tender Media

w Charged Tip Service Charge field—Link each applicable Tender/Media
key (Visa, Amex, etc.) with a Service Charge key designated for charged
tips.
w Charged Tip Required - Type Definition #9—Credit card keys like

American Express can be programmed to treat any overpayment as a
charged tip. If the amount due is $44.00 and $50.00 is entered as the
tender, this key assumes a $6.00 service charge and prompts the operator
to confirm it.
1 Service Charges

R Tips Paid Tender/Media field—Link the service charge key to the
Tender/Media key that is designated as the Tips Paid key. This key
must be a Pickup Type key and have the Type Definition Tips Paid
enabled.
R Post to Charge Tips Total on Tip Reports—The charged tip can be
set to automatically add to a tender/media entry designated for Tips
Paid. The Tips Paid amount posts to the server’s Tip Report. This
eliminates the need to manually enter Tips Paid for each server.
R Amounts - Percent to Tips Paid—A percentage of Charged Tips can
be withheld by an establishment to cover any credit card handling or
processing fee. For example, if Amex charges the restaurant 4% of
credit card sales charged to Amex, then the restaurant may want to pay
the employee only 96% of the Amex credit card Charged Tip.
1. For a complete explanation of programming the Tips Paid feature, see “Charged Tip” on page C-18.
T-76
Tips Handling
Optional Settings
1 Job Codes

R Prompt for Direct Tips Before Clock Out
R Prompt for Indirect Tips Before Clock Out

R Validated Employee Direct/Indirect Tips Declared Transactions—
Enable this option to print a validation chit when declaring Direct/
Indirect Tips.
R Reset Operator Financial Report for Tipped Employee after a Tips Paid
Operation

R Do Not Post Transactions to Tip Report Totals
R ON = Post Totals to Transaction Operator; OFF = Post Totals to Check
Operator
R ON = Post Tenders to Transaction Operator; OFF = Post Tenders to
Check Operator

R Cashier Totals Declaration Required with [Tender/Media] and [Tips
Paid] keys

R Do Not Include Tax in Totals on Tip Report

R Do Not Post Transactions to Tip Report Totals

R Display the Tax & Autogratuity When a Check Initially Displays

Tips Handling
1 Service Charges

R Do Not Post to Gross Receipts
1 Tender Media

R Charged Tip Amounts—Select Must be Less Than Payment
Amount.
1 Keyboards or WS Touchscreen Screen

Number

R [Direct Tips] key

R [Indirect Tips] key
R [Direct Tips, Ask #] key - for use with FLUs
R [Indirect Tips, Ask #] key - for use with FLUs


R [Open Check Block Settlement - Signed Operator] key

R [Open Check Block Settlement - Prompt Operator] key
T-78
Tips Handling
1 Employee Class

Options
R Authorize/Use [Direct Tips] and [Indirect Tips] keys
R Authorize/Use [Direct Tips] and [Indirect Tips] keys for Another
Employees

R Authorize/Perform Closed Check Adjust Tenders, Charged Tips
Related Topics
w “Charged Tip” on page C-18
w “Open and Closed Check Files” on page O-8
w “Service Charge” on page S-19

TouchAdvantage
TouchAdvantage
Description
TouchAdvantage makes POS functions easier and simpler to use. It also paves the
way for a variety of new POS functions; TouchDetail, TouchEdit, TouchShare,
and TouchSplit.
Usage
TouchDetail
The Devices option Enable TouchDetail (System Hardware | Devices | Options)
allows you to make the Transaction Detail section of the UWS Operator display
touch sensitive. When this type definition is enabled, the System adds scroll
buttons to the operator display. It also removes the line number associated with
transaction detail. Instead of entering a line number to specify the detail you wish
to access, just touch the detail.
When TouchDetail is active, it can be used to scroll through transaction detail or
in conjunction with the Hold, Void, and/or Edit Seat POS transactions. For
additional information, refer to “TouchDetail” on page T-82.
TouchEdit
TouchEdit allows you to move transaction detail between existing seats or to new
seats with the touch of a finger. The TouchEdit feature is key activated. This
means that you must complete the necessary touchscreen programming before
you can take advantage of the TouchEdit feature. TouchDetail does not have to
enabled in order to use TouchEdit. For more information, refer to “TouchEdit” on
page T-84.
TouchShare
TouchShare allows you to share transaction detail between existing seats or to
new seats with the touch of a finger. The TouchShare feature is key activated.
This means that you must complete the necessary touchscreen programming
before you can take advantage of the TouchShare feature. TouchDetail does not
have to enabled in order to use TouchShare. For more information, refer to
“TouchShare” on page T-123.
T-80
TouchAdvantage
TouchSplit
TouchSplit allows you to create a split check with the touch of a finger. The
TouchSplit feature is key activated. This means that you must complete the
necessary touchscreen programming before you can take advantage of the
TouchSplit feature. TouchDetail does not have to enabled in order to use
TouchSplit. For more information about TouchShare, refer to “TouchSplit” on
page T-124.

TouchDetail
TouchDetail
Description
TouchDetail makes POS functions easier and simpler to use. When TouchDetail
is active, scroll buttons are added to the Transaction Detail area of the Operator
Display. This allows the operator to scroll through guest check detail with a touch
of the finger. The TouchDetail also functions with [Void], [Return], [Hold], and
[Edit Seat] keys.
Usage
TouchDetail makes viewing transaction detail simpler and easier than ever. When
it is active, transaction detail line numbers are removed from the screen and
replace by scroll buttons. POS functions that utilized the transaction detail number
will now work by touching the detail in lieu of entering a line number. When this
feature is enabled, the Operator Display screen looks like this:
Scroll Bar
and
Buttons
T-82
TouchDetail
About the Operator Display Screen
Field... Described...
Scroll Buttons Touch a scroll button to move detail up and

down on the display.
Transaction Detail When the TouchDetail feature is active, line
number information is no longer associated with
transaction detail. Touch the appropriate detail to
select it. Once you have done so, use the
appropriate POS function (Void, Return, Edit
Seat Hold).
Enabling
1 Devices
2 System Hardware | Devices | <Select Workstation> | Options

R Enable TouchDetail—Enable this option to activate TouchDetail.
Related Topics
w “TouchEdit” on page T-84
w “TouchShare” on page T-123
w “TouchSplit” on page T-124

TouchEdit
TouchEdit
Description
TouchEdit allows an employee to quickly and easily move transaction detail
between existing seats or to new seats with a single touch.
Usage
TouchEdit offers a quick and convenient alternative way to edit order detail. All
you need to do is touch the detail you want to move, then touch the seat to which
it should be moved and it’s done! It’s as simple as that.
The TouchEdit feature is key activated. When [TouchEdit] is pressed, the System
displays a default Edit Check screen. The default screen contains those
components that allow you to review existing seat detail, add a new seat to the
check, move detail from one seat to another, and to share detail with another seat.
Except for changing color preferences, the format of this screen cannot be
modified.
T-84
TouchEdit
The Edit Check screen looks like this:
Seat Window
Edit Seat
Status
Window
Touchscreen
Buttons

TouchEdit
About the Edit Check Screen

The Edit Check screen contains several components; Seat Window, Edit Seat
Status Window, and Touchscreen Buttons. Each of these components is described
here.
Component... Described...
Seat Window w The format and position of this portion of the Edit Check
screen is not user-definable. The UWS automatically
generates Seat Window information when the TouchEdit
key is pressed.
w The Seat Window contains information about a
particular seat that includes the amount due, the
transaction detail, and the seat number. For a more in-
depth view of amount due, seat number, and transaction
detail information refer to “More About the Seat
Window” on page T-89.
w The UWS will automatically display a seat window for
each seat that is currently in use on a guest check.
w The first Seat Window displayed contains information
about the lowest seat number currently in use on the
guest check.
w The System will, by default, display two seat windows
when there are less than two seats in use. This allows
you to move detail to another seat without having to
press [New].
w The Seat Window portion of the Edit Check screen looks
like this:
7.50 0.00
1 Hamburger
Med Rare Seat
1 Ham Sand Window
2 Lg Coke without
Transaction
Seat 1 Seat 2
T-86
TouchEdit
Edit Seat Status w The Edit Seat Status window is designed to provide you
Window with information about the status of the selected seat.
w In this window you will find the number of the seat that
is currently active and the dollar value of the highlighted
item (excluding taxes and Autogratuties). The UWS
will include a descriptor identifying the type of
transaction that is in progress, e.g., When using
TouchEdit, the System displays Edit Seat as the
descriptor for Edit Check.
Edit Seat Status w The Edit Seat Window portion of the Edit Seat screen
Window looks like this:
(continued)
7.50 0.00 7.50
1 Hamburger 1 Hamburger
Med Rare Med Rare
1 Ham Sand
2 Lg Coke
Seat 1 Seat 2 Seat 3
Edit SEAT
Seat 1 Edit Seat Status
7.50

TouchEdit
Touchscreen w The format and position of the touchscreen buttons are

Buttons controlled by the System and cannot be modified.
However, you can define the Touchscreen Style that is
used to generate these buttons.
w The System includes six buttons in the display; New,
Done, Share, and Cancel, right arrow, and left arrow.
The Touchscreen Button portion of the Edit Check
screen looks like this:
7.50 0.00 7.50
Med Rare Med Rare
1 Ham Sand
2 Lg Coke
Seat 1 Seat 2 Seat 3
Edit SEAT New Done

Seat 1
7.50 Share Cancel
Touchscreen Buttons
T-88
TouchEdit
More About the Seat Window

The Seat Window displays information that pertains to a particular seat. A
maximum of four windows can be displayed at any one time. Seat windows will
be displayed in ascending order by seat number, beginning with the lowest
number.
If there are more seat windows than can be displayed at one time, the System will
display scroll buttons. These buttons include a directional arrow. The right arrow
indicates that additional Seat Windows can be found by paging forward. The left
arrow indicates that additional seat windows can be found by paging backward.
When the last seat window is reached (in any one direction) the System will turn
off the scroll button.
Each Seat Window contains three fields of information; Amount Due, Transaction
Detail, and Seat Number. Each of these fields is described here.
Amount Due This field provides a visual reminder of the total

amount due for each seat. The amount shown is
inclusive of tax and autogratuities and is updated in
real time as detail is moved from one seat to another.
Transaction Detail This portion of the screen lists the detail associated
with the seat. Detail can be moved quickly and easily
from one seat window to another.
To move detail, touch the entry that you wish to move

and then touch the seat window to which the detail is
being moved. Notice that Amount Due field for each
window is updated to reflect the change.
Seat Number This portion of the screen identifies the guest check
seat number.

TouchEdit
In Conclusion
Unlike other touchscreens, the Edit Check Screen does not require any
programming. The Seat Window, Edit Seat Status Window, and the Touchscreen
buttons are all System generated.
The Edit Check screen includes six function keys: New, Share, Done, Cancel, left
arrow, right arrow. These keys function as follows:
Key... Described...
New w Touch this key to create a new seat. The System will
assign the next unused seat number. For example, if the
check currently uses seats 1,2,5, and 6 and [New] is
pressed, the System will create a seat window for seat 3.
w Press[New] for each additional seat required. A guest
check can include a maximum of 64 seats, ranging from
0 to 63 in number value.
w Save your changes by pressing [Done]. If you add a seat
to a guest check and press [Done] without moving detail
to it, the System closes the Edit Seat function without
adding the seat to the check.
For additional information about using [New], refer to

“Editing a Seat” on page T-94.
Share w An item may be shared with more than seat. The
System will ask you to indicate which seats with which
you wish to share the item.
w Highlight the item you wish to share with another seat,
then touch [Share].
w When [Share] is pressed the System will display the
Share SLU. It includes those function keys that are
needed in order to complete the transaction. For
example, a Share SLU might look like this
T-90
TouchEdit
Key... Described...
Share w The SLU includes the following information:

(continued from w Seat Keys— a key for each available seat. The key
previous page)
label includes the seat number and amount due.
w All— Shares the item with all seats
w Enter— shares the item with the highlighted seats
w Clear— returns the user to the previous screen
w Paging Buttons— If more seats are available than
can be displayed on a single screen, the appropriate
paging buttons are illuminated.
For more information about using [Share], refer to
Done Touch this key to complete a TouchEdit transaction.
Cancel Touch this key to cancel the current TouchEdit transaction
and return to the original format of the guest check, or to
cancel the current entry.
Left/Right Arrow Displays only when there are more seats than can be
displayed in a single window. The arrow indicates the
direction in which you should page in order to view the
remaining seats.

TouchEdit
Creating Your TouchEdit Touchscreens

In order to take advantage of the TouchEdit feature, you’ll need to add the
appropriate touchscreens and styles to the 9700 HMS database. In this section,
you will find all of the information needed to accomplish that task. To give you a
quick start, we have also included samples for each.
Getting Started
You can begin using the TouchEdit feature once you’ve completed each of
the following tasks. You can add this information to your database in any
sequence. For ease of discussion, we will add these elements in the following
order:
Programming
Described
Task
Touchscreen Use the Touchscreen Screen tab to add the Share and
Screen Tab Count touchscreens to your database. You will also
use the Touchscreen Screen tab to add the TouchEdit
key the keyboard of your choice.
Touchscreen Use the Touchscreen Style tab to create two new styles
Style Tab to your database; Edit Seat, Share. The System uses
these styles to generate the Edit Seat and the Share
SLU touchscreens
Touchscreen Use the Touchscreen Assign tab to link styles and
Assign Tab touchscreens to the following touchscreen parameters:
w Edit Seat Touchscreen Style Num

w Edit Check Share T/S Style Num
w Edit Check Count T/S Screen
T-92
TouchEdit
Adding TouchEdit to the Touchscreen Screen Tab

You will need to design a new touchscreen screen for the Share SLU and add
the [TouchEdit] key to the appropriate transaction touchscreens. We suggest
that you add the TouchEdit key to your Default Sales touchscreen. To do so,
use key code 556 - TouchEdit.
When you create the Share SLU Touchscreen make sure that you include the
following keys:
w All (Key Code 560)
w Enter (Key Code 12)
w Clear (Key Code 13)
w TS SLU Page Up (Key Code 351)
w TS SLU Page Down (Key Code 352)
Make these additions and enhancements in the usual manner. In our example,
we added the [TouchEdit] key to the Default Sales Screen and named our new
Share SLU screen Share TS.
Once you completed making the necessary additions to the Touchscreen
Screen tab, proceed to the Touchscreen Style tab.
Adding TouchEdit to the Touchscreen Style Tab

In order to use the TouchEdit feature, you will need to add the touchscreen
styles that govern the way the System generates the Edit Seat and the Share
SLU touchscreens. Add these styles to the Touchscreen Style tab in the usual
manner. If you are uncertain about how to do so, quickly review
“Touchscreen Concepts” in Chapter 5 of the 9700 Feature Overview Manual.
To add a style, make sure that you make an entry in each of the following
Touchscreen Style file fields:
w Style Name
w Key Height
w Key Width
w Key Legend Size
w Key Type Definition
w Color Combination

TouchEdit
w Function Key TS For Edit Seat have it set to zero. For Share, enter the
number associated with the Share Touchscreen from the Touchscreen
Screen tab.
w Icon Placement
Adding TouchEdit to the Touchscreen Assign Tab

The last TouchEdit touchscreen programming task involves the Touchscreen
Assign tab. Use this tab to define the default styles and touchscreens that are
used by the TouchEdit feature. Entries are required in the following fields:
w Edit Seat Screen Style Num field—Select the touchscreen style that is
linked to the TouchEdit key.
w Edit Check Share T/S Style field—Select the Share Style that you
defined on the Touchscreen Style tab.
w Edit Check Count Screen field—Select the Count touchscreen that you
created on the Touchscreen Screen tab. A Count touchscreen should
include a numeric key pad, Enter, Clear, Edit Check All (key code 560),
and Edit Check One (key code 561) keys.
Editing a Seat
TouchEdit allows you to touch detail items for an active seat number on a guest
check in order to:
w Move detail items to a NEW or EXISTING seat (see below)
w TouchShare detail items among seats (see page T-96)
Move Detail Items to a New or Existing Seat

To move detail items to a new or existing seat, perform the following steps:
1. Pick up a guest check.
2. Press [TouchEdit].
The screen will display separate seat windows for the first available, non-
closed seats in ascending order. Up to four seat windows will display at
one time. Remember, when the right scroll button appears in the lower
right-hand corner, more seat windows are available for editing.
The example below is displaying two seat windows because only two
seats are active on the selected guest check:
If you want to move items to an existing seat, continue with the next step.
T-94
TouchEdit
amount due for each seat
scroll buttons
detail item(s)
seat number
If you want to move items to a new seat, press [New] before continuing
with the next step. An empty seat window with a new seat number will
appear.
3. Touch the item(s) you want to move. Remember, you may need to scroll
down to access detail items in seat windows containing more items than
can fit on the screen at one time. Once you touch an item, the system
highlights it, and displays the selected seat’s number and highlighted
item’s value (without tax) in the Edit Seat window as shown in this
example:
edit seat window

TouchEdit
4. Touch the seat window where the selected detail item(s) should be
moved.
If you attempt to move a consolidated detail item,

such as four crab cakes, the system will prompt you
for the number of detail items to be moved. In which
case, you must enter the number before continuing.
Quantity items with condiments cannot be quantity
edited.
The detail item(s) now appear in the detail for the selected seat, along
with a new total in the Amount Due field as shown in this example:
5. To save changes and exit this procedure, press [Done] and then [Yes]
when prompted Exit and save changes?
or
To exit without saving, press [Cancel] and then [Yes] when prompted
Changes made. Quit?
TouchShare Detail Items Among Seats
2. Press [TouchEdit].
3. Touch the menu item(s) you want to share. The system highlights your
selection.
T-96
TouchEdit
4. Press [Share]. The Select SEAT(s) window, which displays a separate key
for each seat, is shown in this example:
Remember, when the right scroll button under Select SEAT(s) isn’t
grayed out, more seats than those appearing on screen are available for
sharing.

TouchEdit
5. Touch the seat key(s) for the seat(s) that will share the selected detail
item(s), and then press [Enter].
or
Press [All] to select all seats on the current check.
The detail item(s) appear in each seat window you selected, with the
quantity and cost adjusted accordingly, as shown in this example:
or
Changes made. Quit?
T-98
TouchEdit
A Few Words About Share

In order to share an item, the System must be able to recognize that it is
sharable. Use the System Configurator to designate those items that can be
shared. The following table lists the files that contain items that can be shared.
Configurator File Option
Menu Item Item is Shareable—Enable this option for each

Maintenance— menu item class that contains items that can be
Menu Item Class shared.
Service Charge Item is Shareable—Enable this option for each
service charge that can be shared between guests.
Discounts Item is Shareable—Enable this option for each
service charge that can be shared between guests.
Tender Media Item is Shareable—Enable this option for each
tender media that can be shared between guests.
Enabling
1 WS Touchscreens

Function=Transaction | Function Key Categories=Check Operations |
Number
R 556 - TouchEdit—Add this key to the appropriate touchscreen.
R Share SLU Touchscreen—Create a Share SLU touchscreen that
includes the following keys:
w Edit Check All - Key Code 560
w Edit Check One - Key Code 561
w Enter - Key Code 12
w Clear - Key Code 13
w TS SLU Page Up - Key Code 351
w TS SLU Page Down - Key Code 252

TouchEdit

<Insert>
R Edit Seat Style
R Share Style

R Edit Seat Screen Style field—Select the touchscreen style linked to
the TouchEdit key.
R Edit Check Share T/S Style field—Select the Share Style.
R Edit Check Count T/S Screen field—Select the Count touchscreen
Optional Settings
1 Menu Item Class
R Item is Shareable—Select this option to allow menu items in this class
to be shared between seats.
1 Discounts

R Item is Shareable—Select this option to allow this service charge to
be shared between seats.
1 Service Charges
2 System Information | Service Charge | <Select Service Charge> | General

R Item is Shareable—Select this option to allow this discount or service
charge to be shared between seats.
1 Tender Media

R Item is Shareable—Select this option to allow this payment to be
shared between seats.
T-100
TouchEdit
Related Topics
w “Editing a Seat” on page T-94
w “TouchAdvantage” on page T-80
w “TouchSplit” on page T-124

Touchscreen Icons
Touchscreen Icons
Description
The PCWS supports the use of touchscreen icons in POS Operations. An icon,
may be used represent a menu item, discount, service charge, or tender/media and
can be placed on any touchscreen key. The icon may appear with or without a
descriptor.
A standard set of icons are included with the 9700 System Software. There are
approximately 190 icons included in the standard set.
If so desired, user-defined icons may be created using a program such as
Microsoft Paintbrush. The icons are located in the micros\les\pos\9700\xdt3\
bitmaps\ws_icons directory and are in .BMP format.
Usage
Icon Set
These icons are sorted, in the zoom pop-up System Configurator, where similar
icons are in the same range of number ID’s (i.e, all those icons that may be used
for check operations are located in the same number range). The number range of
the standard icon set is 1 - 500. The ID numbers 1 - 500 contain gaps in the
number sequence, these gaps are in place for future growth. Some icons are the
same graphic picture but different sizes. The standard bitmap size of most icons is
32x32. Not all of the icons come in different sizes.
Icons may be user-defined. User-defined icons, those icons which are created
using a program such as SCOpaint, must have an ID number of 500 or higher. The
ID number of 500 or higher is assigned to the icon when it is created. The standard
icon set includes blank icons of different sizes to be used a template when creating
a user-defined icon.
There are 6 blank icons included in the standard set, these begin with the name
“blank”. These blank icons are available in different sizes (32x32, 40x40, etc.).
T-102
Touchscreen Icons
Icon File Naming Convention

All icons included in the standard set use the file naming convention below. With
the exception of two different icons, all icons have a unique ID number and name
included in the file name. The two icons that have the same ID number (in italics
in the table below) are used with a function called Auto Sizing, see page T-121 for
an explanation.
Icon ID 002_courses.px
Icon Descriptor File Name Extension
Icon File Names
001_oneprinter.px 002_twoprinter.px 003_restaurant.px

004_bar.px 005_employees.px 006_empsign1.px
007_empshift.px 008_empclock.px 009_posterbd.px
010_people.px 011_empsign2.px 012_training.px
013_report.px 014_key.px 015_uwskey.px
016_chair.px 017_balloon_2.px 018_chngcshr_2.px
019_day_2.px 020_key_2.px 021_notepad_2.px
022_chart_2.px 023_wsmagcard_2.px 024_wsmagcard2_2.px
025_journal_2.px 026_calendar_2.px 027_cshdrwrswp_2.px
028_chart2_2.px 029_caution_2.px 030_danger_2.px
031_door_2.px 032_opendoor_2.px 033_enterdoor_2.px
034_wsheart_2.px 035_lips_2.px 036_editmenu_2.px
037_86item_2.px 038_cash2_2.px 039_lock_1.px
040_lock_1.px 040_lock_2.px 041_timeclock_2.px
042_timclckinq_2.px 043_stoplight_2.px 044_caution_2.px
045_greenlite_2.px 046_tmcrdadj_2.px 047_tmcrdadj2_2.px
048_tmcrdadj3_2.px 049_finger_2.px 050_select_2.px
051_yellowdot_1.px 052_fire_2.px 053_fire_2.px
053_fire_3.px 054_fire2_2.px 055_dontfire.px

Touchscreen Icons
Icon File Names
060_courses.px 061_emptytable.px 062_addcheck.px

063_check.px 064_pkupcheck_2.px 065_table2_2.px
066_twotop_2.px 067_check_2.px 068_receipt_2.px
101_apple_1.px 102_cone_2.px 103_cone2_2.px
104_dessert.px 105_cktails1.px 106_entrees.px
107_wine1.px 108_rita.px 109_salad.px
110_burger1.px 111_soups.px 112_happyhour.px
113_coffee.px 114_fish.px 115_cktail2.px
116_lime.px 117_pasta.px 118_btlwine.px
119_glasswine.px 120_beer.px 121_condiment.px
122_cake_2.px 123_sandwich_2.px 124_bowlsoup_2.px
125_openfood_2.px 126_drinks_2.px 127_burger_2.px
128_rocks_2.px 129_breadbskt_2.px 130_pretzel_2.px
131_cake2_2.px 132_lobster_2.px 133_wine_2.px
134_loafbread_2.px 135_gingerbrd_2.px 136_ketchup_2.px
137_pizza_2.px 138_peppermill_2.px 139_shrimpcktl_2.px
140_redhat_2.px 141_shrimp_2.px
142 - 200 are currently unassigned 201_tmed.px
202_cash.px 203_moneysack.px 204_cauth_1.px
205_cauth_2.px 206_manauth.px 207_chgtip_2.px
208_roomchg_2.px 209_currency_2.px 210_cashrgstr_1.px
211_cashrgstr_2.px 212_crncy_1.px
213 - 299 are currently unassigned 300_rndbtn0_2.px
301_rndbtn1_2.px 302_rndbtn2_2.px 303_rndbtn3_2.px
310_rndbtn00_2.px 311_rndbtndot_2.px 312_vertenter_3.px
313_vertclear_3.px 314_horzenter_3.px 315_horzclear_3.px
T-104
Touchscreen Icons
Icon File Names
316_rndbtnclr_2.px 317_rndbtnent_2.px 318_cancel_1.px

319_cancel_2.px 320_cancelbtn_2.px 321_checkmark_1.px
322_checkmark_2.px 323_erase_2.px
324 - 329 are currently unassigned 330_dnarrow1_2.px
331_uparrow1_2.px 332_uparrow2_2.px 333_dnarrow2_2.px
334_blkarrowrt_2.px 335_blkarrwlft_2.px 336_blkarrowup_2.px
337_blkarrowdn_2.px 338_pageup_2.px 339_pagedown_2.px
340_dnarrow3_2.px 341_uparrow3_2.px 342_smarrowdn_1.px
343_smarrowup_1.px 344_redarrwlft_2.px 345_redarrowrt_2.px
346_redarrowdn_2.px 347_redarrowup_2.px 348_bluarrwlft_2.px
349_bluarrowrt_2.px 350_bluarrowdn_2.px 351_bluarrowup_2.px
352_grnarrwlft_2.px 353_grnarrowrt_2.px 354_grnarrowdn_2.px
355_grnarrowup_2.px 356_yelarrwlft_2.px 357_yelarrowrt_2.px
358_yelarrowdn_2.px 359_yelarrowup_2.px
324 - 329 are currently unassigned 370_alphchar.px
371_plusminus.px 372_help.px 373_keypad1_2.px
374_keypad2_2.px 375_frownface_2.px 376_smileface_2.px
377_plussign_2.px 378_keypad_2.px 379_micros_3.px
380 - 500 are currently unassigned
blankbutton_40x40.px blankbutton_40x80.px blankbutton_80x40.px

blankicon_128x32.px blankicon_16x16.px blankicon_32x32.px
blankicon_40x40.px blankicon_48x48.px blankicon_64x64.px

Touchscreen Icons
Standard Set
The following pages include screen captures of the standard icon set. You may
view the icon set through System Configurator. It is recommended any color
monitor attached to the 9700 PC be configured as a 800x600 or higher with 256
colors. This will ensure the icons displayed in System Configurator will be
represented with the correct color scheme
T-106
Touchscreen Icons

Touchscreen Icons
T-108
Touchscreen Icons

Touchscreen Icons
T-110
Touchscreen Icons

Touchscreen Icons
T-112
Touchscreen Icons

Touchscreen Icons
Program Icons in System Configurator

There are six areas in System Configurator used to define touchscreen icons:
w Touchscreen Screen
w Discount (SLU)
w Service Charge (SLU)
w Tender/Media (SLU)
w Menu Item Definition (SLU)
w Touchscreen Style
Touchscreen Screen
The Touchscreen Screen tab in the WS Touchscreens file is used the assign a
specific icon and to place that icon at a specific location on a touchscreen key.
T-114
Touchscreen Icons
Icon ID Field
This field is used to identify which icon is to appear on the touchscreen
key. A pop-up box will display all the icons contained in the
\Micros\Les\Pos\9700\xdt3\bitmaps\ws_icons directory.
1. Click on the drop-down arrow box.
2. Click on the selected icon number.
3. The ID number appears in the field.
Icon Placement Field

This field is used to position the icon on the touchscreen key. An icon can
appear in the following locations, in relation to the text on the touchscreen
key:
w Left
w Right
w Center
w Top
w Bottom
w Icon Only (No Text or Box Around the Key)
Icon Only
Top
Left Right
Bottom
Center

Touchscreen Icons
Placement Rules
The following rules should be taken into consideration:
w Key Height matters with icons that are placed at the top or bottom of
the touchscreen key.
w When Center placement is used, the icon will replace any text on the
touchscreen key.
Depending on the placement of the icon and the size of the touchscreen
key, the text may or may not appear on the touchscreen key.
For example, the touchscreen key labeled “Draft” below (with the mug of
beer icon) is currently programmed with the height = 2 and the icon
placement is set to bottom.
If the key height was to be changed to = 1, only the icon would appear, as
shown below.
T-116
Touchscreen Icons
When an icon is placed in the center, the icon will always replace the text.
In the case of the “Draft” key below, the placement was changed from top
to center and the text has been replaced by the icon. Unlike with the top
and bottom icon placements, the key height has no bearing on the
appearance of the text when the placement is set to center.
Touchscreen Icons on SLUs

Touchscreen icons may appear on Discount, Service Charge and Tender/
Media SLUs. Any key on an SLU, direct access, or another SLU may
contain an icon. Individual items linked to an SLU may also contain
different icons.
Below is example of an SLU (Menu Item in this case) with icons.
SLU Key
Direct Access
Individual Keys
(Cancel Key)

Touchscreen Icons
Discount File
The Discount file is used to identify which icon is to appear on the
touchscreen key when a Discount SLU key is selected.
Icon Field
A drop-down box on the NLU/SLU tab will display all of the icons
contained in the \Micros\Les\Pos\9700\xdt3\bitmaps\ws_icons directory.
Service Charge File

The Service Charge file is used to identify which icon is to appear on the
touchscreen key when a Service Charge SLU key is selected.
Icon Field
T-118
Touchscreen Icons
Tender Media File

The Tender/Media file is used to identify which icon is to appear on the
touchscreen key when a Tender/Media SLU key is selected.
Icon Field
Menu Item Maintenance File

The Menu Item Maintenance file is used to identify which icon is to appear on
the touchscreen key when a Menu Item SLU key is selected.
Icon Field
A drop-down box on the General tab of the Menu Item Maintenance form
(Menu Items | Menu Item Maintenance | Sort By Menu Item Class |
<Select Menu Item> | General) displays all of the icons contained in the
\Micros\Les\Pos\9700\xdt3\ bitmaps\ws_icons directory.
Touchscreen Style Tab

The Icon Placement field on the Touchscreen Style tab is used to position the
icon on the touchscreen SLU key. An icon can appear in the following
locations (in relation to the text on the key):
w Left
w Right
w Center
w Top
w Bottom
w Icon Only (No Text or Box Around the Key)

Touchscreen Icons
POS Operations
Once a touchscreen icon has been defined in System Configurator, it will then
appear on the specified touchscreen key on the PCWS when POS Operations is
started.
If an icon is added or deleted from the 9700

database while POS Operations is running, the
PCWS must be stopped and started in the UWS/
HHT Status screen for the icon database to be
updated at the PCWS.
There are no other functions or procedures which affect the icons displayed in the
POS Operation.
Icon Only
Top
Left Center Right

Bottom
T-120
Touchscreen Icons
Auto Sizing
Auto sizing occurs when the icon selected for a certain touchscreen key has the
same ID number but comes in different sizes. The touchscreen key height and
width controls which size icon will be displayed.
There are two icons which will use auto sizing, as described below:
Icon Size
040_lock_1.px 16x16
040_lock_2.px 32x32
053_fire_2.px 32x32
053_fire_3.px 48x48
As an example, if icon “053_fire_3.px” was programmed to display on a key that

was configured has:
Height = 1
Width = 1
Icon “053_fire_2.px” would be display because icon 053_fire_3.px, would be too
large to fit on the touchscreen key.
On the other hand, if the height and width were changed:
Height = 2
Width = 2
Icon “053_fire_3.px” would be displayed because there would be sufficient room
on the touchscreen key.
Icon Database File

When an icon is assigned in System Configurator, it is stored in an icon database
file named \Micros\Les\Pos\9700\xdt3\bitmaps\ws_icons.dat. This file will
increase or decrease in size when icons are added or removed from the 9700
database. This file is read by the PCWS when POS Operations started. It is also
read by the PCWS when it is stopped and started in the HHT/UWS Status screen.
When the an icon is either added or removed from the 9700 database while POS
Operations is running, the PCWS must be stopped and restarted via the Control
Panel in the HHT/UWS Status screen in order for the PCWS to recognize the
change to the database.

Touchscreen Icons
Icon Database Table

This table is provided for use with the Site and Memory Survey manual. It may be
useful when configuring a 9700 database which will include touchscreen icons.
RVC# and
Icon ID Icon Name Key Legend
Touchscreen Name
T-122
TouchShare
TouchShare
Description
TouchShare provides the ability to share the cost of an item (menu item, discount,
service charge, and/or tender) with another guest.
Usage
TouchShare offers a quick and convenient way to share the cost of an item
between guests. All you need to do is touch the detail you want to share, indicate
the seat or guest check with which it should be shared and it’s done! It’s as simple
as that. You can access the TouchShare function by pressing [TouchEdit] or the
[TouchSplit]. When you do so, the UWS will display the default edit screen which
contains [Share]. If you used [TouchEdit] to access the TouchShare function, the
screen that is displayed will look like this:
Amount Due
for Each Seat
Transaction Detail
Seat Window
Seat Number
Edit Seat Window

displays the identity of
the selected seat along
with the total value of
the highlighted items.
Share a menu item, discount,
service charge, or tender/
media between seats.
For additional information about how to use the Share feature, refer to
“TouchEdit” on page T-84 or “TouchSplit” on page T-124.

TouchSplit
TouchSplit
Description
The TouchSplit feature combines split check functionality with that of
TouchAdvantage. This allows an employee to select and move transaction detail
from one guest check to another with the touch of a finger.
Usage
TouchSplit offers a quick and convenient alternative way to create a split check.
All you need to do is touch the detail you want to move, then touch the guest
check to which it should be moved and it’s done! It’s as simple as that.
The TouchSplit feature is key activated. When [TouchSplit] is pressed, the
System displays a Split Check screen. This screen is used to display the existing
check, display newly created checks, and to move items of detail from one check
to another.
Check Window
Split Check
Status Window
Touchscreen Buttons
T-124
TouchSplit
About Split Check Screen

The Split Check screen contains several components; Check Window, Split
Check Status Window, and Touchscreen Buttons. Each of these components is
described here.
Check Window The format and position of this portion of the Edit Check
screen is not user-definable. The System automatically
generates Check Window information when the TouchSplit
key is pressed.
The Check Window provides you with a snapshot of the

original guest check. It includes information about the
amount due, transaction detail, and the check number.
Check number information can include table number, guest

check number, or guest check id information.
w Guest Check ID—If the original check includes a Guest

Check ID, it cannot be associated with any new checks
that are opened during the split check transaction (a Guest
Check ID must be unique). Accordingly, if table numbers
are being used, the next group number will be assigned. If
check numbers are being used, the next check number
will be assigned.
w Table/Group Number—If the original guest check was
opened using a table number, then each new check that is
created during the split check transaction will include that
number along with a group number.
w Guest Check Number—If the original guest check was
opened using a check number, then each new check that
is created during the split check transaction will include
the next available check number. If the System is
programmed to allow the operator to assign the check
number then the operator will be prompted for a check
number entry.

TouchSplit
Check Window The System will, by default, display two check windows.
(continued) The left most window is always the original check. The
second window is blank. This allows you to move detail to
another check without having to press [New].
The Check Window portion of the Split Check screen looks

like this:
7.50 0.00
1 Hamburger
Med Rare Check
1 Ham Sand Window
2 Lg Coke without
transaction
detail
TBL 5/1 TBL 5/2
Split Check This portion of the display provides you with information
Status Window about the identity of the guest check. The Split Check Status
window is designed to provide you with information about
the status of the selected check.
In this window you will find the number of the Check that is
currently active and the dollar value of the highlighted item
(excluding the appropriate taxes). The System will include a
descriptor identifying the type of transaction that is in
progress, e.g., Split Check is the descriptor that is displayed
when a TouchSplit transaction is underway.
T-126
TouchSplit
Split Check The Split Check Status Window portion of the Split Check
Status Window screen looks like this:
(continued)
7.50 0.00 7.50
Med Rare Med Rare
1 Ham Sand
2 Lg Coke
TBL 5/1 TBL 5/2 TBL 5/3
Split Check
TBL 5/1 Split Check
Selected 7.50 Status Window

TouchSplit
Touchscreen The format and position of the touchscreen buttons are

Buttons controlled by the System and cannot be modified. However,
You can define the Touchscreen Style that is used to
generate these buttons.
The System includes six buttons in the display; New, Done,

Share, and Cancel, right arrow, and left arrow. The
Touchscreen Button portion of the Split Check screen looks
like this:
7.50 0.00 7.50
Med Rare Med Rare
1 Ham Sand
2 Lg Coke
TBL 5/1 TBL 5/2 TBL 5/3
Split Check New Done

TBL 5/1
Selected 7.50 Share Cancel
Touchscreen Buttons
More About the Check Window

The System uses the Check Window to display information that pertains to a
particular check. A maximum of four windows can be displayed at any one
time. Check windows will be displayed in ascending order by check number,
beginning with the lowest number. The original check will always appear in
the left most position on the screen.
If there are more check windows than can be displayed at one time, the
System will display scroll buttons. These buttons include a directional arrow.
The right arrow indicates that additional check windows can be found by
paging forward. The left arrow indicates that additional check windows can
be found by paging backward. When the last check window is reached (in any
one direction) the System will turn off the scroll button.
T-128
TouchSplit
Each Check Window contains three fields of information; Amount Due,

Transaction Detail, and Check Number. Each of these fields is described here
Amount Due This field provides a visual reminder of the total

amount due for each check. The amount shown is
inclusive of tax and is updated in real time as detail is
moved from one check to another.
Transaction Detail This portion of the screen lists the detail associated
with the check. Detail can be moved quickly and
easily from one check window to another.
To move detail, touch the entry that you wish to move

and then touch the check window to which the detail is
being moved. Notice that Amount Due field for each
window is updated to reflect the change.
Seat Number This portion of the screen identifies the guest check
number.
More About Touchscreen Buttons

The Touchscreen Button portion of the Split Check screen displays the default
Split Check Touchscreen. Unlike other touchscreens, it does not require any
programming. The System is designed to automatically generate this
touchscreen anytime [TouchSplit] is pressed.
The Split Check touchscreen includes six function keys; New, Share, Done,
Cancel, left arrow, right arrow. These keys function as follows:
Key Described
New Touch this key to create a new check. The System will
assign the next unused check number. For example, if
the current check is TBL 5/1 [New] is pressed, the
System will create a check window for TBL 5/2.
Press [New] for each additional check required.
Save your changes by pressing [Done]. If you add a

check and press [Done] without moving detail to it, the
System closes the Split Check function without adding
the new check.
For additional information about using [New], refer to

“Splitting a Check” on page T-134.

TouchSplit
Key Described
Share A current round menu item, service charge, discount,

and/or tender/media cannot be shared using
[TouchSplit], you must use [TouchEdit].
An item may be shared with more than seat. The

System will ask you to indicate which seats with
which you wish to share the item.
Highlight the item you wish to share with another seat,

then touch [Share].
When [Share] is pressed the System will display the

Share SLU. It includes those function keys that are
needed in order to complete the transaction. For
example, a Share SLU might look like this:
Share The SLU includes the following information:

(continued from
previous page) w Check Keys— a key for each available check. The
key label includes the seat number and amount due.
w All— Shares the item with all checks
w Enter— shares the item with the highlighted checks
w Clear— returns the user to the previous screen
w Paging Buttons— If more checks are available than
can be displayed on a single screen, the appropriate
paging buttons are illuminated.
For more information about using [Share], refer to

Done Touch this key to complete a TouchEdit transaction.
T-130
TouchSplit
Key Described
Cancel Touch this key to cancel the current TouchEdit

transaction and return to the original format of the
guest check.
Touch this key to cancel the current entry.

Left/Right Arrow Displays only when there are more checks than can be
displayed in a single window. The arrow indicates the
direction in which you should page in order to view
the remaining checks.
Creating Your TouchSplit Touchscreens

In order to take advantage of the TouchSplit feature, you’ll need to add the
appropriate touchscreens and styles to you 9700 HMS database. In this section
you will find all of the information needed to accomplish that task. To give you a
quick start, we have also included samples for each.
Getting Started
Before you begin, take a few moments to review the touchscreen
programming requirements. You can begin using the TouchEdit feature once
you’ve completed each of the following tasks:
Programming
Described...
Task...
Touchscreen Use the Touchscreen Screen file to add the Share,

Screen file Numeric, and Count touchscreens to your database.
You will also use the Touchscreen Screen file to add
the TouchEdit key the keyboard of your choice.
Touchscreen Use the Touchscreen Style file to create two new
Style file styles to your database; Split Check, Share. The
System uses these styles to generate the Split Check
and the Share SLU touchscreens.
Touchscreen Use the Touchscreen Assignment file to link styles
Assignment file and touchscreens to the following touchscreen
parameters:
w Split Check Touchscreen Style Num

w Edit Check Share T/S Style Num
w Edit Check Count T/S Screen
w Edit Check Numeric T/S Screen

TouchSplit
You can add this information to your database in any sequence. For ease of
discussion, we will add these elements in the following order:
w Touchscreen Screen tab
w Touchscreen Style tab
w Touchscreen Assign tab
Adding TouchEdit to the Touchscreen Screen Tab

You will need to design a new touchscreen screen for the Numeric and the
Share SLU, as well as add the TouchSplit key to the most appropriate
touchscreen keyboard. We suggest that you add the TouchSplit key to your
Default Sales touchscreen. To do so, use key code 557-TouchSplit.
When you create the Share SLU Touchscreen make sure that you include the
following keys:
w All (Key Code 560)
w TS SLU Page Up (Key Code 351)
w TS SLU Page Down (Key Code 352)
T-132
TouchSplit
When you create the Numeric SLU Touchscreen make sure that you include
the following keys:
w Cancel (Key Code 20)
w Numeric Keypad (0-9)
Make these additions and enhancements in the usual manner. Once you’ve
completed making the necessary additions to the Touchscreen Screen tab,
proceed to the Touchscreen Style tab.
Adding TouchSplit to the Touchscreen Style Tab

In order to use the TouchSplit feature, you will need to add the touchscreen
styles that govern the way the System generates the Split Check and the Share
SLU touchscreens. Add these styles on the Touchscreen Style tab in the usual
manner. If you are uncertain about how to do so, quickly review
“Touchscreen Concepts” in Chapter 5 of the 9700 Feature Overview Manual.
Before doing so, we suggest that you create a category where all of your
TouchAdvantage related style will be located. In our example, you will notice
that we used **TouchAdvantage as the category.
To add a style, make sure that you make an entry in each of the following
Touchscreen Style file fields:
w Style Name
w Key Height
w Key Width
w Key Legend Size
w Key Type Definition
w Color Combination
w Function Key TS (leave this field set to zero unless you are adding the
Share style. In this case, enter the number associated with the Share
Touchscreen (you’ll create this touchscreen as a part of the next
programming task).
w Icon Placement

TouchSplit
Adding TouchSplit to the Touchscreen Assign Tab

The last TouchSplit touchscreen programming task involves the Touchscreen
Assign tab. Use this tab to define the default styles and touchscreens that are
used by the TouchSplit feature. Entries are required in the following fields:
w Edit Seat Touchscreen Style Num field - enter the number of the
touchscreen style that is linked to the TouchEdit key.
w Edit Check Share T/S Num field - enter the number of the Share Style
that you defined in the Touchscreen Style file.
w Edit Check Count T/S Num field - enter the number of the Count
touchscreen that you created in the Touchscreen Screen file. A Count
touchscreen should include a numeric key pad, Enter, Clear, Edit Check
All (key code 560), and Edit Check One (key code 561) keys.
Splitting a Check
TouchSplit allows you to touch the detail items on a guest check in order to:
w Create one or more new checks at one time (see below)
w TouchShare detail items (see page T-137)
Create One or More New Checks at One Time
2. Press [TouchSplit Check]. The system displays the original guest

check in the left check window and a new, blank guest check in the
right check window as shown in this example:
T-134
TouchSplit
w If you want to create one new check, continue with the next step.
w If you want to create more than one new check, press [New] for as
many new checks as you need before continuing with the next step.
The screen will only display up to four check

windows at one time. More checks are available
when the right scroll button appears. If you press
the Seat Banner (*****Seat 1 *****), all the
associated items are selected.
3. Touch the detail item(s) you want to move to a new check.

Remember, you may need to scroll down to access all detail items on
the check.
The system highlights the item(s) while the Split Check window
displays the table number/group number (or check number depending
on how the system is programmed) and the highlighted items’ value
as shown in this example:
scroll buttons
detail items
split check window

TouchSplit
4. Touch the new check.
If you attempt to move a consolidated detail item,

such as four crab cakes, the system will prompt you
for the number of detail items to be moved. In which
case, you must enter the number before continuing.
The new check now contains the selected detail item(s) and an
amount due total as shown in this example:
amount due
5. To share menu items while splitting the check, move on to the next
procedure, TouchShare Detail Items on page T-137, before exiting.
or
Changes made. Quit?
T-136
TouchSplit
TouchShare Detail Items
2. Press [TouchSplit Check]. The system defaults to the original guest

check window and one new check window. You may need to press
[New] to add additional checks before sharing detail items.
3. Touch the detail item(s) you want to share. The system highlights
your selection and notes the table number/group number and selected
items’ value in the Split Check window.
4. Press [Share]. The Select checks window will display a separate key
for each check as shown in this example:
Remember, when the right scroll button under Select checks isn’t
grayed out, more checks than those appearing on screen are available
for sharing.
5. Touch each check key in the Select checks window that will share the
selected detail item(s), and then press [Enter].
or
Press [All] to select all checks.

TouchSplit
The detail item(s) appear in each check window you selected, with
the quantity and cost divided evenly for the shared detail item(s) as
shown in this example:
shared detail item
or
Changes made. Quit?
T-138
TouchSplit
Enabling
1 WS Touchscreen Screen File

R [TouchSplit] Key Code #557—Add this key to the appropriate
touchscreen.
R Share SLU Touchscreen—Create a Share SLU touchscreen that
includes the following keys:
w All - Key Code 560
w Enter - Key Code 12
w Clear - Key Code 13
w TS SLU Page Up - Key Code 351
w TS SLU Page Down - Key Code 252
w Numeric Keypad

R Split Check Style
R Share Style

R Split Check Touchscreen Style Num field—Enter the number of the
touchscreen style linked to the TouchSplit key.
R Edit Check Share T/S Num field—Enter the number of the Share Style
R Edit Check Count T/S Screen field—Enter the number of the Count
touchscreen
R Edit Check Numeric T/S Screen field—Enter the number of the
Numeric touchscreen

TouchSplit
Optional Settings
1 Menu Item Class
R Item is Shareable—Select this option to allow menu items in this class
to be shared between seats.
1 Discounts

w Item is Shareable—Select this option to allow this service charge to be
1 Service Charges
2 System Information | Service Charges | <Select Service Charge> |

General
R Item is Shareable—Select this option to allow this discount or service
charge to be shared between seats.
1 Tender Media

R Item is Shareable—Select this option to allow this payment to be
Related Topics
w “Editing a Seat” on page T-94
w “TouchAdvantage” on page T-80
w “TouchEdit” on page T-84
T-140
Tracking Groups
Tracking Groups
Description
Tracking Groups are used to customize reports to track specific items or to
perform calculations that are not included in the standard body of 9700 Reports.
Each tracking group can define up to 128 tracking totals, such as menu items,
tender/media, discounts, and service charges. These items can be grouped with
totals, subtotals, or subtracted from each other. A virtually unlimited number of
different tracking groups may be created (subject to the constraints of the PC’s
memory capacity).
Tracking groups simply provide a format for totals to post to reports. Once
tracking groups have been created, they can be linked to:
w Employees
w Operators
w Cashiers
w Revenue Centers
w Time Periods
w Serving Periods
w System
The scope of the tracking group report will vary depending on the link. Whenever
a financial report is taken (for either the employee, operator, revenue center, etc.),
the tracking group report prints after the body of the report.

Tracking Groups
Example
A restaurant wants to see how many of a certain group of special desserts are sold.
A tracking group is created to list these desserts. Then, the tracking group called
“Specials” is linked to each employee, to the “Dining Room” Revenue Center,
and to each Time Period. This way a manager can see:
w Which employee sold the most special desserts.
w How many special desserts were sold in the Dining Room.
w Which Time Period had the most sales of special desserts.
Definitions
A tracking total consists of three items: a name, a count, and a value. The name is
a descriptor programmed in the Tracking Group File. The count is the number of
times the tracked item was posted. The value is the sum of the associated dollar
amounts. Tracking totals are posted whenever a transaction is finalized with a
[Service Total] key or [Tender/Media] key.
The following total types may be included in a Tracking Group:
Entry Type Remarks
0 Disable this Tracking Total.

1 Major Group
2 Family Group
3 Menu Item
4 Discount
5 Subtotal Discount
6 Service Charge
7 Tender/Media
8 Column Subtotal
9 Column Total
10 Print Name Only Prints or displays descriptor only; can be used to
create section titles, insert blank lines, etc.
11 Currency Does not add to column or block Totals and
Conversion Subtotals, and cannot be used in Accumulator
arithmetic in flexible reports.
T-142
Tracking Groups
Entry Type Remarks
12 Form Feed Forces the PC’s line printer to advance to the top
of the next page. This Tracking Total is ignored
if the report is output to a file, a display, or a roll
printer.
13 Tax Total If add-on tax is used, this total tracks the tax
amount.
If VAT tax is used (Tax Option #1 is OFF), this

total tracks the taxable amount instead of the tax
amount.
14 Order Type Sales
15 Block Subtotal If used in a format that has only one column,
they are treated as a Type 8 or Type 9.
16 Block Total
17 Tax Exempt Total Tracks [Exempt Tax] keys only; does not track
exemptions performed by [Tender/Media] keys.
Column Subtotal and Column Total

Totals #8 and #9 allow subtotals and totals to be inserted in columns to sum
specific sets of tracking totals.
Column Subtotals
A tracking group record can contain more than one subtotal. You can define
whether or not preceding information in included in the current subtotal.
Resetting subtotals and totals is controlled by Tracking Total Definition #3:
Do Not Reset Subtotal or Total.
Example 1: Subtotals
Definition #3 is set OFF Definition #3 is set ON

for Subtotal #1. for Subtotal #1.
Result: Subtotal #2 includes only Result: Subtotal #2 includes all
information that follows Subtotal #1. information that precedes Subtotal #1.
Food 2 10.00 Food 2 10.00

Banquet 3 15.00 Banquet 3 15.00
Subtotal #1 5 25.00 Subtotal #1 5 25.00
Liquor 30 122.00 Liquor 30 122.00
Wine 22 62.00 Wine 22 62.00

Tracking Groups
Column Totals
Column totals act as a superset of subtotals. That is, they can be used in a
tracking group to sum specific tracking totals or to sum specific sets of
subtotals.
Example 2: Totals combined with subtotals
Definition #3 is set OFF for Total A. Definition #3 is set ON for Total A.

Result: Total B includes only Result: Total B includes all
information that follows Total A. information that precedes Total A.
Food 2 10.00 Food 2 10.00

Banquet 3 15.00 Banquet 3 15.00
Liquor 30 122.00 Liquor 30 122.00
Wine 22 62.00 Wine 22 62.00
Total A 57 209.00 Total A 57 209.00
T-Shirts 12 120.00 T-Shirts 12 120.00

Hats 9 135.00 Hats 9 135.00
Books 2 20.00 Books 2 20.00
Magazines 11 37.00 Magazines 11 37.00
Packages 4 22.00 Packages 4 22.00
Total B 61 334.00 Total B 95 543.00
Note that resetting column subtotals does not affect the information that is
passed to column totals. In the example above, Subtotal #1 is programmed to
reset. As a result, that information is not included in Subtotal #2. It is,
however, included in Total A.
T-144
Tracking Groups
Block Subtotal and Block Total

Totals #15 and #16, Block Subtotal and Block Total, are also used to sum specific
sets of tracking totals. These totals can be used on both UWS Reports and Report
Writer reports.
On UWS Reports, block subtotals and block totals simply act as column subtotals
and totals, as described in the previous section.
On Report Writer reports that are programmed to print Tracking Totals in 2 or 3
columns, a block subtotal or block total adds all totals that occur above and to
their left. For example:
Name
Count
Amount
Pie 1 2.00 Beer 3 3.00 Gin 2 3.00

Soup 2 3.00 Wine 2 4.00 Rum 3 3.00
Nuts 3 1.00 Soda 1 1.00 Teq 1 4.00
Total 18 48.00
Block Total Name

Sum of all Counts
Sum of all Amounts

Tracking Groups
Column subtotals and column totals may be combined with block subtotals and
block totals as required. The example below shows column subtotals and totals
used with block subtotals and totals.
A B C
1 xxxxxxxx 11 19.00 xxxxxxxx 16 14.00 xxxxxxxx 9 11.00

aaaaaaa 45 49.00 aaaaaaa 32 62.00 aaaaaaa 65 84.00
ddddddd 142 195.00

xxxxxxxx 14 24.00 xxxxxxxx 15 31.00 xxxxxxxx 14 11.00
6
bbbbbbb 30 42.00 bbbbbbb 49 55.00 bbbbbbb 34 36.00
eeeeeee 113 133.00
cccccccc 75 91.00 cccccccc 81 117.00 cccccccc 99 120.00
f f f f f f f f 255 328.00
Total Total Definition

Remarks
Name Type #3 set...
aaaaaa 8 column OFF sums rows 1, 2, and 3 in each column

subtotal
bbbbbb 8 column n/a sums rows 4, 5, and 6 in each column;
subtotal because subtotal aaaaaa resets, this subtotal
does not include any information from rows
1, 2, and 3
cccccc 9 column total n/a sums rows 1 - 6 in each column
dddddd 15 block subtotal OFF sums rows 1 - 3 in columns A - C
eeeeee 15 block subtotal n/a sums rows 4 - 6 in columns A - C; because
subtotal dddddd resets, this subtotal does not
include any information from rows 1, 2, and
3
ffffff 16 block total n/a sums rows 1 - 3, columns A - C
T-146
Tracking Groups
Enabling
1 System Parameters

R Do Not Print Tracking Group Names On Financial Reports
R Do Not Print Separator Line Before the Tracking Section In Rpts
1 Tracking Groups
2 Reporting | Tracking Groups

R Complete all fields for each tracking group.
1 Tracking Group Link

In the following files, link the appropriate tracking group:
R System Parameters File
R Revenue Center Parameters File
R Employee Maintenance File (Employees and Operators)
R Cashier File
R Time Period File
R Serving Period File

R Decrement Tender Media Totals When Voided
1 Time Periods

R Print Only Tracking Groups on Time Period Detail Reports

Tracking Groups
1 Employees

Employee> | General
R Do not Print Tracking Totals in Employee Financial Reports
Related Topics
w “Report Writer” on page R-14
T-148
Training Mode
Training Mode
Description
Training Mode allows an operator to enter sales, without affecting real system
totals. A separate set of training totals is kept to reflect the practice session of the
training employee.
While in Training Mode, order output is disabled and guest checks are printed
with a special header for that employee.
If a table in the 9700 System has an open training check, checks for regular
service may not be opened at that table until the training check is closed.
Usage
Training Status is used to allow new employees to practice using the 9700
System. It can also be used to test new database programming (e.g., new menu
items, new serving periods, etc.)
Reports
Financial Reports (System, Revenue Center, and

Employee)
w Training Total field
Employee Closed Check Report & Employee Open

Check Report
w Training checks are marked by “T”.

Training Mode
Enabling
1 Employees
2 Personnel | Employee Maintenance | Sort By Employees | <Select

Employee> | General
R In Training field—Enable this field to place the employee in training
mode.
1 Employee Class

Procedures & Reports |
R Use UWS Procedure 7: Change Employee Training Status—This
option is usually enabled only for managers.

Header=Training Check/Receipt Header
R Training Header Lines 1 - 3—Enter a header message that will
identify the printed guest check as a training check. For example:
******* TRAINING CHECK ********

********* DO NOT PAY **********
*******************************
T-150
Transfer Checks
Transfer Checks
Description
Transfer Checks is a procedure that changes the ownership of the guest check.
Privileged operators can use the UWS to transfer checks from one server (the
source) to themselves (the destination) by employee numbers or by employee ID
numbers. Unlike the Block Transfer function, checks may be transferred to
servers in other Revenue Centers.
This feature is available at the UWS only; an HHT cannot be used to transfer
guest checks.
The keys chosen when programming the Keyboard File or Touchscreen File
determine the restrictions on this feature. A general-purpose [Add/Transfer
Check] key may be used, which allows an operator to transfer a check from any
Revenue Center in the System. Alternately, an assignable key can be chosen to
restrict an operator to transferring checks from one assigned Revenue Center.
Any of these functions (by check or table number, to any Revenue Center or to a
specific one) can be included in a Function Lookup (FLU) key.
If Guest Checks are to be transferred across

Revenue Centers, the Order Type tax programming
must be identical in each Revenue Center.

Transfer Checks
Usage
Samantha and George have lingered over lunch for hours. Their server’s shift is
ending and rather than ask Samantha and George to pay their check, the check is
transferred to the server arriving for the dinner shift.
In another part of the restaurant, a customer has a drink in the lounge while
waiting for a date. The date arrives, and they are then seated in the dining room.
The check is transferred from the lounge Revenue Center to the dining room
Revenue Center.
To transfer a guest check:
w Sign in to a UWS.
w Enter the check number (or the table number) of the check to be transferred.
w Press the [Add/Trans by Num] key (or the [Add/Trans by Table] key). The
UWS prompts, “TRANSFER THIS CHECK?”.
w Press [Enter] for “Yes”, (or [Clear] for “No”).
If you enter “Yes”, and the transfer is successful, ownership of the check is
transferred to the signed-in operator. (This operator is the “transaction” operator.
The operator who began the check is the “check” operator.
Transferring a guest check creates a journal entry of the event. For an illustration
of this type of journal entry, refer to the example in the “Journal” section Chapter
10 of the 9700 Feature Overview Manual.
T-152
Transfer Checks
Reports
Financial Reports (All)

Any transaction detail posted by the original operator is reported to that operator’s
totals on financial reports.
Financial Reports (Revenue Center and Employee)

If checks are transferred between Revenue Centers or between operators, the
checks post to the following totals on these reports:
w Begun
w Transferred In
w Paid
w Transferred Out
Employee Closed Check Report- Report Writer

Version
An “X” prints next to the original check. A status line prints “Xferred to RRRR/
nnnn”, where RRRR is the name of the Revenue Center, and nnnn is the number of
the destination check.
An “x” prints next to the destination check. A status line prints “Xferred from
RRRR/nnnn”, where RRRR is the name of the Revenue Center, and nnnn is the
number of the source check.
Employee Closed Check Report - UWS Version

An “X” prints next to any check involved in a transfer (i.e., either a source check
or a destination check).

Transfer Checks
Enabling


R [Add/Trans Check] keys—There are many variations of these keys

available. Keys can be programmed which transfer checks:
w By table number or by check number
w In the current Revenue Center, in a defined Revenue Center, or in a

Revenue Center selected by the operator from a prompt.

R Post Totals to Transaction Operator—Enable this option. When
disabled, totals will post to the check operator.
R Post Tenders to Transaction Operator—Enable this option. When
disabled, tenders will post to the check operator.
Optional Settings
1 Employee Class

Guest Checks
R Authorize Transfer of Checks in Same Revenue Center
R Authorize Transfer of Checks Between Revenue Centers
T-154
Transfer Checks
Related Topics
w “Add Check” on page A-3
w “Block Transfer Checks” on page B-23
w “Journal” in Chapter 10 of the 9700 Feature Overview Manual

Translation Utility
Translation Utility
Description
XL9700, the 9700 Translation Utility, is a utility program that modifies the text
files used by the 9700 database so that print and display text can appear in another
language.
The XL9700 Text Translation Utility consists of one file—XL9700.exe. In the
course of operation, XL9700 creates and maintains two additional files:
XL9700.cfg and XL9700.err.
XL9700.cfg stores the entries and preferences selected by the last user who ran
XL9700 in the current directory. XL9700.err records the times that XL9700 was
started and ended, as well as the files edited in each session.
Each software module in the 9700 System uses three files to store text
information: a .txt, .trn, and .off file. XL9700 operates by allowing a user to alter
a .txt file, from which the utility then generates new .trn and .off files.
Text files in
Description
/usr/9700/text
9700aseq.txt Autosequencer text

9700atrl.txt Audit Trail text
9700bkup.txt Backup/Restore text
9700cbatch.txt Credit Card Settlement text
9700ccm.txt Cluster Controller text
9700ccrd.txt Credit Card Authorization text
9700creport.txt Credit Card Settlement text
9700csettle.txt Credit Card Settlement text
9700cfd.txt Confidence Test text
9700cfg.txt System Configurator text
9700cp.txt Electronic Journal/Check Printer
9700cpl.txt Control Panel text
9700dbs.txt Database Services text
9700elog.txt Error Log text
T-156
Translation Utility
Text files in
Description
/usr/9700/text
9700isl.txt SIM/ISL text

9700lds.txt LDS text
9700menu.txt Menu (for Remote Maintenance)
9700ops.txt POS Operations (restaurant text)
9700ops1.txt POS Operations (retail variation)
9700proc.txt UWS Procedures text
9700pup.txt Popup text
9700rcc.txt RCC text
9700rpt.txt UWS Reports text
9700rw.txt Report Writer text
9700sql.txt SQL text
9700sys.txt System text for several modules
9700tms.txt TMS text
9700uws3.txt UWS/3 text
Usage
The steps required to translate text files are illustrated below.
Copy XL9700.exe Load the utility and

1 and the required
.txt file(s) to a 2 the .txt file(s) on a
DOS machine.
DOS floppy. * .txt
XL9700
97 0 0 DOS 3 Run XL9

Generate
.txt, .trn,
.off files.
Restart the Copy the new

5 affected 9700
module(s), so that
new text will be used.
* .off
* .trn
* .txt
4 files back to
/usr/9700/txt on
the 9700 System.

Translation Utility
Generate a New Text File

To generate new .trn and .off files from the copied .txt file, take the following
steps:
1. Create two directories on the DOS machine: one for the existing
English text files (e.g., \English), and one for the new, translated
files (e.g., \French). The directory names may be any 8-character
strings that conform to DOS conventions.
2. Copy the .txt files from diskette to the \English directory on your
DOS machine.
3. Use XL9700 to create new, translated, .trn files and .off files in the
\French directory.
4. Copy the translated files in the \French directory to diskette.
5. Start the Translation Utility by entering XL9700 at the DOS
prompt.
6. Select Edit from the main menu. The first screen in the Edit function
prompts you for the drives, directories, and filenames of the
\English (Source) and \French (Destination) files. XL9700 places a
default entry in most fields that require an entry. You may press
[Enter] to use this entry, or begin typing your own entry to erase the
default.
7. Enter the drive and directory of the English (Source) files. The
cursor then moves to the File selection. The .txt files that you copied
to this directory appear in a help box.
8. Enter the number (from the help box) of the .txt file to be translated.
If the list of .txt files is long, use Ctrl-[PgDn] and Ctrl-[PgUp] to
scroll through pages in the help box.
9. Enter a drive and directory name for the French (Destination) file.
The directory selected for the Source files cannot be used to store the
Destination file. The two directory names must be different.
10. XL9700 prompts you to continue.
11. Select Yes to create a new Destination file. XL9700 creates a new
.txt file, then displays an Edit screen. The path and filename of the
Destination file display on the first line of the screen.
The remainder of the screen is used to display the text file, in the form of six
columns, as described in the following table.
T-158
Translation Utility
Column
Contents Editable?
Name
Num This column displays the line number on which No

translatable text occurs in the .txt file.
XL9700 does not display empty lines or

command lines. The file displayed by XL9700
may therefore appear to skip line numbers.
However, these skipped lines are copied, intact,
to the destination file.
Label This column displays any label appended to the No
translatable text. The label is used by the 9700
software to address each text string.
Len This column displays the length of the character No
string for each line of text. A length of “0”
indicates non-translatable text.
English This column displays the original English text No
for each line. This column displays either the
first 18 or the first 28 characters in the text string
(depending on whether or not the Comments
column is displayed).
Foreign This column is used to enter the translation of Yes
each line of English text. The English text is
copied to this column as a default. Edit this
column to create the translation for each line of
English text. XL9700 displays either the first 18
or the first 28 characters in the text string
(depending on whether or not the Comments
column is displayed).
Comment This column displays any comments which the No
programmer entered for the translatable text.

Translation Utility
12. Edit the new Foreign column in the display, using the menu options
described below.
Menu Selections: First Row
Selection Description
[F1] - This key ends the XL9700 session. If you have edited fields
Cancel in this session, you are prompted to Save or Exit Without
Saving. Select “Yes” to save the translations you have
created to a new .txt file, and generate new .trn and .off
files. Select “No” to return to the Main Menu without
saving your work.This function may also be performed by
pressing the [Esc] key.
[F2] - This key allows you to toggle back and forth between the
More three rows of menu bars.
[F6] - This key allows you to suppress the display of the
Toggle Comments column. If this option is chosen, the Comments
Comments column disappears, and the English and Foreign columns
expand.
[F7] - This key allows you to save your work and exit XL9700
Save & without generating .trn and .off files. At the prompt, select
Exit “Yes” to remain in the edit session. Select “No” to return to
the main menu.
[F9] - This key superimposes a box on the screen that contains the
Zoom entire length of the selected character string from both the
English and Foreign columns. For example, if the text
columns display only the first 28 characters of a 40-
character label, press [F9] to display the entire 40 characters
in both fields. The English field is displayed above the
Foreign field. Enter the new text for the Destination file, or
press [Esc] to close the Zoom box without editing the field.
[F10] - This key prints the XL9700 Edit session to the PC’s line
Print printer, in the same format in which it appears on the screen.
Lines that are larger than the column width will wrap when
printed.
Menu Selections: Second Row
T-160
Translation Utility
[F3] - This key allows you to select the column on which a search
Toggle is performed. A small arrow appears in the column header
of the selected column. The arrow points in the direction
(Backward or Forward) in which the search will be
conducted. Refer to the explanation that follows for the [F4]
(Backward) and [F5] (Forward) keys. Note that the
Comment column cannot be searched.
Menu Selections: Second Row
[F4] - This key allows you to begin a search of the previous

Backward records in the selected column. Type a character string to be
used in the search and press [Enter]. If the search is
successful, the cursor bar moves to the last record in the file
that contains that string. If the search is unsuccessful, that
string does not exist in this column. The screen displays
“Pattern not found”.
[F5] - This key allows you to begin a search of successive records
Forward in the selected column. Refer to the explanation for [F4]
that occurs above.
[F8] - After a successful search, this key allows you to search for
Continue the next record (forward or backward) in which the selected
character string occurs.
[Ctrl]-[F5] This allows you to determine whether or not a search is to
- be case-sensitive. The screen displays “Case sensitivity on”
Toggle or “Case sensitivity off” until another key is pressed.
Case
Menu Selections: Third Row
[Alt]-[F3] - This allows you to search for an identical pair of records to
Repeat be edited. XL9700 ignores any records in which the entry in
Search the Foreign column has already been edited. Non-
translatable records are also ignored.

Translation Utility
Upgrade a Previously Translated File

The Upgrade option creates new, updated versions of translated .txt files when
new versions of 9700 Software are released that result in changes to the .txt files.
Copies of the following three files are necessary in order to create the upgrade:
w The Old English file. This is a copy of the English text file used by the old
version of software.
w The New English file. This is a copy of the English text file used by the
newly released software.
w The Old Foreign file. This is a copy of the Foreign text file used by the old
version of software.
The Upgrade screen prompts for path and filenames. To upgrade to a new text
file:
1. Select the Upgrade option.
2. Enter the drive and directory of the Old English file. The .txt files
available on this directory appear in a help window. Select the .txt file
to be upgraded.
3. Enter the path of the New English file.
4. Enter the path of the Old Foreign file.
5. Enter a path for the file to be created, e.g., the New Foreign file.
The directory selected for the Old Foreign file cannot be used to
store the New Foreign file. The two directory names must be
unique. XL9700 displays an error message if you enter the same drive
and directory for both files.
XL9700 creates the New Foreign using the path selected, and returns to the
Main Menu. The New English file and the New Foreign file may now be used
in the Edit function to translate the text strings that have changed in the new
version of 9700 Software.
T-162
Translation Utility
Configure Printing Parameters

The General Parameters menu option is used to establish parameters for the line
printer used by your PC, so that the Edit screen can be printed. There are four
fields on this screen. Select entries for these fields that are based on the needs of
your printer.
General Parameters
Field Description Range
Lines per Use this field to determine the number of lines to print 10 - 255
Page before the printer performs a form feed.
Output Use this field to specify the linefeed and/or carriage- 1-3
Format return requirements for your printer:
1 - Linefeed and Carriage Return
2 - Linefeed only
3 - Carriage Return only

Printer Use this field to enter a printer setup string, if required 40 char
Setup by your printer. Refer to the documentation provided alpha
with your printer for specific setup strings, if required.
Printer Use this field to direct printer output to a specific LPT 1-3
Number port on the PC.
After entering any necessary printer parameters, press [F7] to save and exit, or
press [F1] to exit without saving any changes.
Related Topics
w “Standard vs. Extended Character Sets” on page K-4

Two-Color Printing on Guest Check Header/Trailer
Two-Color Printing on Guest Check

Header/Trailer
Description
This feature will print the Header and/or Trailer in red on guest checks and
customer receipts. This feature requires a two color ribbon.
The maximum number of Header lines is 3, the maximum number of Trailer lines
is 12.
This feature does not apply to Training Headers and

Credit Card Voucher descriptor lines.
Enabling

R Print Guest Check/Receipt Header in Red
R Print Guest Check/Receipt Trailer in Red

R Guest Check Header and Trailer Lines
R Customer Receipt Header Lines
T-164
U
User Workstation
Description
The User Workstation (PCWS, KBWS, and HHT) is a hardware unit for point-
of-sale operations.
Usage
A user workstation may be used for several purposes, including:
w Clocking in and clocking out employees
w Placing and totalling orders
w Recording payment
w Printing guest checks and customer receipts
w Running UWS autosequences
w Making changes to the database through User Workstation Procedures.
9700 HMS A to Z Feature Reference Manual U-1

User Workstation
Sign In
In order to perform any operations or functions on a UWS, operators must first
identify themselves to the UWS by signing in. This process allows the system to
grant certain privileges or impose certain restrictions on the operator, depending
on system programming. Each operator is assigned an ID number, which is
different from their employee number. The ID number is similar to the PIN
number used by a bank machine card: it is intended to be a secret number, used
only by one person. Only one operator may be signed in to a UWS at one time.
The system may be programmed to accept or require several different methods of
signing in, as described in the paragraphs that follow.
Keypad or Touchscreen Sign-In

This is the standard, most commonly used method of signing in. To sign in, an
operator approaches an inactive UWS (i.e., no transaction or operation is in
progress, and no one else is signed in to the UWS), types their ID number, and
presses the [Enter] key. The operator is then signed in, and their last name (as
programmed in the Employee Maintenance file) appears on the UWS display.
Magnetic Card Sign-In

Some installations may wish to enhance the security of the sign-in process by
issuing cards on which an employee ID is magnetically encoded. The
employee ID on this card is a randomly generated, 10-digit number. This
number is not printed on the card, and does not display in the course of normal
operations. So for all practical purposes, the employee must have this card in
order to sign in.
The UWS may be programmed to require magnetic card entry; that is, to
refuse to accept keypad or touchscreen entry.
Replacement Sign-In
Under normal circumstances, a signed-in operator must sign out before the
next operator may sign in. However, the UWS may be programmed to allow
replacement sign-in outside of a transaction. If this feature is used, the act of
signing in to the UWS automatically signs out the current operator, if no
transaction is in progress.
U-2
User Workstation
Sign Out
Some operators may be programmed to automatically be signed out when they
complete a transaction. They are referred to as “pop-up” operators.
Operators who are programmed to stay signed in until they sign themselves out
are called “stay-down” operators. They sign out by pressing [Transaction Cancel]
while outside of a transaction.
Automatic Operator Pop-up Interval

Pop-up operators who sign in and do not begin a transaction, or who sign in
and then perform non-transaction activities (e.g., UWS Procedures) are
automatically signed out when the Automatic Pop-up Interval expires. This
field is set in the Revenue Center Parameters file.
The pop-up interval is programmed for each Revenue Center, but it may be
disabled for a specific UWS. If the Interval is disabled for a UWS, it overrides
Operator File and Revenue Center Parameters File programming.

User Workstation
PC Keyboard
If you have to enter a large amount of information on the PCWS, a PC keyboard
can be attached as an alternate means of data entry. Data entry through the PC
keyboard is sent to the 9700 System as if it had been entered on a touchscreen.
Any key on the PC keyboard can be remapped to an ASCII key or to an 9700
keycode. This allows you to design international keyboards and to customize keys
for particular operations, such as using the [Esc] key to cancel a transaction.
Each PCWS contains a default keyboard map. The keys on the PC keyboard can
be remapped for every PCWS in the System (the default can be overridden) by
entering the name of a substitute keyboard mapping file in the PC Keyboard File
field on the Workstation tab in the System Parameters file. This setting can, in
turn, be overridden for an individual PCWS by entering the name of yet another
keyboard mapping file in the PC Keyboard File field for a PCWS on the
Workstation tab in the Devices file.
Substitute keyboard files must be located in the /usr/9700/etc directory and must
be named <filename>.kb.
Each record in the PC keyboard file defines the mapping of one PC key. Each
record must contain the following fields:
Code Definition
scan The code returned when a key is pressed from the PC

keyboard. A scan code is independent of whether the
ctrl, alt, or shift keys are also pressed. For example, the
scan code of ‘2’ is returned whenever the numeric ‘1’ is
pressed.
normal The ASCII character returned when a key from the PC
keyboard is pressed.
shift The ASCII character returned when the shift key is
active while a key from the PC keyboard is pressed.
ctrl The ASCII character returned when the ctrl key is active
while a key from the PC keyboard is pressed.
alt The ASCII character returned when the alt key is active
while a key from the PC keyboard is pressed.
num lock The ASCII character returned when the num lock is
active and a key from the PC keyboard is pressed.
key type key The 9700 key type or key number returned when the
number remapped key is pressed. For example, key type 11 and
key number 605 will remap the key to perform a
Transaction Cancel when the key from the PC keyboard
is pressed.
U-4
User Workstation
The following is an example from a keyboard file:
;scan normal shift ctrl alt numlock type number

;------ ---------- ------- ----- ---- ------------ ------ -----------
1st Example 2 ‘1’ ‘!’ 0 0 0 0 0
2nd Example 1 0 0 0 0 0 11 605
In the keyboard file shown above, the first scan code example defines the [1/!] key
on the PC keyboard. In this example, ASCII characters are returned when the
normal and shift keys are active, but not for the ctrl, alt, and num lock keys. In the
second scan code example, the [Esc] key (scan code 1) is remapped to the 9700
[Transaction Cancel] key.
Note the following rules for the format of the keyboard file:
w Lines beginning with a semicolon (;) are ignored.
w Empty lines are ignored.
w All values can be expressed in decimal form (48) or in quotes (‘A’).
w All eight fields must be entered for each scan code.
w A ‘0’ entry indicates that the key should be ignored.
w Each field must be separated by spaces.

User Workstation
In the event of a programming conflict within the keyboard file, the System uses
the following hierarchy to determine the response to a key press:
w If the [Number Lock] key is active, return the numlock character.
w If the type and number fields are non-zero, return the 9700 keycode.
w If the [Alt] key is active, return the alt character.
w If the [Ctrl] key is active, return the ctrl character.
w If the [Shift] key is active, return the shift character.
w If none of the above apply, return the normal character.
Enabling
To enable a UWS for POS operations, connect it to a Remote Cluster Controller.
(RCC functionality will be available in 9700 Version 1.10.)
1 Devices
2 System Hardware | Devices

1 Confidence Test
2 Start | Programs | Micros Systems 9700 | Confidence Test

The Confidence Test Module is used to load the PCWS Application
Software into the RCC. This procedure must be repeated whenever a new
version of the PCWS application is released.
U-6
User Workstation
Optional Settings
1 Devices

R PC Keyboard File field—Enter the name of the file that remaps the
default key settings for this specific PCWS. This filename may be
entered in either of two formats: <filename> or <filename>.kb. In
either case, the System searches for /usr/9700/etc/<filename>.kb.
The setting of this field overrides the setting in the System Parameters
File.
2 System Hardware | Devices | <Select Workstation> | Workstation |

Options
R Auto Begin Check when Operator ID/#
R Disable Auto Sign Out
R Replacement Sign In Outside Trans.
R Mag Card Entry Required for Emp ID
1 System Parameters

R PC Keyboard File field—Enter the name of the file that remaps the
default key settings for every PCWS in the System. This filename may
be entered in either of two formats: <filename> or <filename>.kb. In
either case, the System searches for /usr/9700/etc/<filename>.kb.
The setting of this field is overridden for a specific PCWS by the
setting of this field on the Workstation tab in the Devices file.

R Automatic Operator “Pop-up” Interval field

R No Change in Revenue Center without Operator Totals

User Workstation
1 Employee Class
2 Personnel | Employee Information | Sort By Class | <Select Class> |

General | Transaction Sign In
R Allow Sign in to a User Workstation
R Authorize Sign in to a User Workstation
2 Personnel | Employee Information | Sort By Class | <Select Class> |

R Use UWS Procedure #5: Change Employee Revenue Center
1 Operators
2 Personnel | Employee Information | Sort By Operator | <Select Operator>

| Options | Miscellaneous
R Pop-up Operator
R If Staydown Operator, Enable the Auto Pop-up Timeout
Related Topics
w “Hand-held Touchscreen” in Chapter 12 of the 9700 Feature Overview
Manual
w “User Workstation Features” in Chapter 1 of the 9700 Feature Overview

Manual
U-8
User Workstation Procedures
Description
User Workstation Procedures are actions that a manager may take at a User
Workstation to modify or update the contents or status of the system and database.
Usage
UWS Procedures provide control and security by limiting the actions that may be
taken by any one employee. This protects the database from damaging errors and
mistakes that could be introduced by an employee with access to the entire
database (i.e., access to System Configurator).
UWS Procedures are easy to use. A manager can perform tasks that would require
more comprehensive training and system understanding to reliably obtain the
same result by editing the database using the System Configurator.
To access UWS Procedures, press the [Mode] key. At the prompt, select [2] for
User Workstation Procedures. You may eliminate this step by pressing [2]
[Mode]. A help window displays, listing the User Workstation Procedures.
The list includes all UWS Procedures for which the current operator is privileged
(in the Employee Class File’s Supervisory Privileges). If the operator is not
privileged to perform a specific UWS Procedure, it does not display in the list.
To exit the UWS Procedure mode, press [Save & Exit] to record your changes, or
press [Cancel] to exit without saving.
Changes that you make to the 9700 using UWS Procedures are recorded
immediately in the database files stored on the PC. These changes are
implemented as if they had been made in System Configurator. Refer to the notes
on implementation of database changes included in “Database Maintenance” on
page D-4.

Procedures
There are 20 User Workstation Procedures. Each is described below.
1- Change Next Guest Check Number
This procedure is used in each Revenue Center to change the Next Check
Number, which is printed on guest checks. Some restaurants prefer to start each
day or week with check #0001.
2 - Change Serving Period
This procedure is used to change the Serving Period, for example, from Lunch to
Dinner. Serving Periods are used to track sales activity during meal periods that
are determined by the user.
3 - Employee Setup
This procedure is intended to allow employees to be added when they start
employment. The Employee Definition Fields which can be changed include the
Employee Name, ID Number, Employee Class, Type Definition, Job Rate, Job
Code, etc. Fields in the Employee Class File are not included. Employee Classes
are comparatively fixed in their content and apply to many employees, so that it is
only appropriate to edit them in System Configurator.
4 - Employee Revenue Center Setup
This procedure is used to program operator characteristics for each Revenue
Center in which the employee works. The five fields displayed in this procedure
are the same ones that display in the Operator file:
w Cashier Number
w Table Count
w Drawer Number
w Default Transaction Touchscreen
w Operator Type Definitions
5 - Change Employee Revenue Center

This selection links the employee to a different Revenue Center than the one
currently assigned. This link is required for operator sales tracking and reporting
purposes. If the employee works in more than one Revenue Center, the link must
be changed each time the employee works in a different Revenue Center.
6 - Print Employee List
This procedure allows you to print a range of employees by employee number and
provides the employee number, last name, and ID number. The header on the list
gives the list name, a page number, and the date and time the list was printed.
U-10
7 - Change Employee Training Status

This procedure will place an employee in/out of training mode. An employee in
the training mode creates guest checks that do not post to system totals. All sales
and other check operations posted while in the training mode add to the training
totals shown on reports, but not to the restaurant’s sales. Order output is disabled
for training transactions, and cash drawers do not open.
UWS Procedures 8, 9, and 10 do not display unless

Time and Attendance is enabled for your System.
8 - Adjust Employee Time Card

This procedure allows corrections to the time entries or job code entries in an
employee’s time card file. For example, if an employee began work at 9:00 a.m.
but forgot to clock in until 10:15 a.m. or left without clocking out, the oversights
can be corrected in this procedure.
9 - Change Time Clock Schedule
This procedure allows a manager to establish a time clock schedule for the staff.
The time clock schedule controls employee clock in and out dates and times and
job rates. Some employees may be programmed with the privilege to override the
schedule.
10 - Print Time Clock Schedule
This procedure will print a range of employee names and their time schedule
entries.
11 - Redirect Order Output
This procedure allows you to redirect the remote and local order output (in this
revenue center only). You may wish to do this, for example, when a particular
food preparation area is closed during a non-peak period.
Redirecting output should not be confused with

designating a backup printer. Redirected output
takes place as a result of a deliberate action by an
operator. Backup printing takes place automatically
if the system is unable to send an order to a
designated output device.

12 - Edit Menu Item Class

This procedure allows you to change all of the fields in the Menu Item Class File,
including menu level and privilege group assignments, type definition, printer
links, print group, and condiment links.
13 - Change Menu Item Assignment
This procedure is intended for changing specials and other similar simple tasks in
a particular Revenue Center. The menu item name, class, price, NLU assignment,
and prep cost may be changed. The HHT SLU Group may also be assigned in this
procedure. Information in the Menu Item Master File is not available to this
procedure; it can only be accessed by System Configurator. This feature is
controlled by the Do Not Allow UWS Procedures to Display or Edit in the Menu
Item Master File (Menu Items | Menu Item Maintenance | <Select Menu Item> |
General | Menu Item Master).
14 - Change Menu Item Availability
This procedure allows you to change the availability of a menu item. If a menu
item is ordered that is set “Not Available”, the error message, “CURRENTLY
OUT OF MENU ITEM”, will display and the item will not post to the check. If a
menu is set unavailable it will remain that way until it is set back to available
through this procedure (or through the System Configurator module). Some menu
items may be available in limited quantities. The number available may be set in
this procedure.
15 - Print Menu Item Price List
This procedure prints a summary list of menu items (by range) and their prices.
16 - Update Currency Rates
This procedure allows you to update the currency exchange rates for up to 30
currencies programmed in your system.
17 - Change Barcode Menu Item
This procedure allows you to update certain fields from the Menu Item Definition
File, the Menu Item Price File, and the Barcode File. It is intended to allow retail
operations using barcode scanners to maintain existing menu items.
18 - Change Barcode File
This procedure allows you to update certain fields in the Barcode File. Menu
items may be prevented from displaying or being edited in this UWS Procedure.
This feature is controlled by the Do Not Allow UWS Procedures to Display or Edit
in the Menu Item Master file (Menu Items | Menu Item Maintenance | <Select
Menu Item> | General | Menu Item Master).
U-12
19 - Change HHT Assignment

This procedure allows you to enter a new physical ID for the HHT that is assigned
to a specific BST and RVC. This effectively allows the user to change the physical
HHT unit. This may be used to swap out an HHT that is in need of service, or to
reassign a specific unit to a different BST and RVC. The Physical ID is unique to
each HHT unit. It displays in the HHT’s Diagnostic mode.
20 - Change HHT Guest Check Printing
Use this procedure to quickly redirect Extech Printer output in the event that it
fails to operate. This procedure cannot be used to redirect Credit Card Voucher
printing. In order for this procedure to function correctly, the following
requirements must be satisfied:
w You must know the HHT Workstation Number from which your wish to
redirect printing
w The printer to which information will be redirected must be defined in the

Customer Receipt Printer field, the Guest Check Printer field, and the Memo
Check Printer field of the User Workstation file must be a non-Extech Printer
Field Help
Some of the UWS Procedures include fields that require entries drawn from the
9700 database. For example, when using Procedure # 3-Employee Setup, you are
required to link the employee to a specific Employee Class.
The [Field Help] key can be used to avoid the necessity of maintaining printed
lists of Employee Class numbers or having to start the System Configurator
module and open the Employee Maintenance file.

Press the [Field Help] key when editing a field that requires an entry from a
database file. The System superimposes a pop-up window on the User
Workstation display. The window lists the names and object numbers of the
records in the file. These fields may not be edited, and no other fields from the file
are displayed.
Workstation Procedures Joe S. Restaurant

Employee Setup LOCATE FIELD AND ENTER CHANGE
101 Joe Smith
Last Name: Smith ID Number: 747

First Name: Joe
Check Name: Joe S. Info Line 1: 123 Common Lane
Class: 10 Waiter10Info
10 Waiter Waiter
Line 2: Any Where
Group: 0 20Info
Bus Line 3: Small Town, USA
Level: 0
Clk In Grace 10 30Info Line 4: (123)456-7890
Bartender
Payroll ID
40 Cook
Rate Job Code50 Manager
Regular Pay Overtime Pay
1 2 Waiter 2.01 3.20
2 3 Host 6.00 9.00
3 0 Not In File 0.00 0.00
4 0 Not In File 0.00 0.00
5 0 Not In File 0.00 0.00
6 0 Not In File 0.00 0.00
7 0 Not In File 0.00 0.00
8 0 Not In File 0.00 0.00
To close the pop-up window, enter one of the numbers displayed and press
[Enter], or press [Clear].
Due to the size of Menu Item files, Menu Item fields do not offer the [Field Help]
feature.
Enabling
1 Devices

R PC Keyboard File field—Enter the name of the file in the /usr/9700/
etc directory that remaps the PC keyboard. You may enter <filename>
or <filename>.kb. In either case, the System searches for /usr/9700/etc/
<filename>.kb .
U-14
1 Employee Class

R Use UWS Procedures 1 through 18—You must be specifically
privileged to perform a particular procedure. Only procedures you are
privileged to perform will appear on the Manager Procedure screen.

R Supervisory Privileges 1 through 20—You must be specifically
privileged to perform a particular procedure. Only procedures you are
privileged to perform will appear on the Manager Procedure screen.
1 System Parameters
2 System Information | System Parameters

R Default UWS Procedures Help Screen field—This field defines the
touchscreen that appears on the UWS when the [Mode] key is pressed to
enter UWS Procedures.

R Hide Employee IDs in Employee Setup UWS Procedures
1 Menu Item Master File
2 Menu Items | Menu Item Maintenance | <Select Menu Item> | General |

Menu Item Master
R Do Not Allow UWS Procedures to Display or Edit—This option
affects the following UWS Procedures:
w Change Menu Item Assignment
w Change Barcode Menu Item
w Change Barcode File



R 300-Mode
R 303-Field Help

Type=Function | Function Key Categories=Movement | Number

Categories=Movement | Link
R 20 through 33-Movement keys
Related Topics
U-16
V
Validation Printing
Description
A Validation chit is a receipt or voucher that is printed by the 9700 System to
provide a hard copy of functions such as:
w Menu item or service charge voids
w Menu item returns
w Bank pickups/loans
w Employee meals
w Menu items, discounts, and/or service charges
w Tax Exemptions
w Tips paid and declared
A validation contains the:
w Name and employee number of the employee who entered that function
w Check number
w Revenue Center, date and time
w Item being validated
9700 HMS A to Z Feature Reference Manual V-1

Validation Printing
For example, the following validation slip is for a menu item:
430 JOE CHK 245

----------------------------------------------
THE GRILL SEP25’93 10:23PM
----------------------------------------------
Dom Perignon 96.95
Usage
A discount coupon is programmed to require validation, and a slip printer is
programmed as the validation printer. When the coupon is presented by the
customer, the operator enters the discount and inserts the coupon in the slip printer
to be validated. With the validation printed on the coupon, it cannot be re-used.
The [Tips Paid] key can be programmed to issue a validation chit (usually from a
roll printer), thereby giving the employee a copy of tips paid for their records.
Enabling
Workstation Table
w Validation Printer field

w Validate Employee Direct/Indirect Tips Declared Transactions - Option #7
w Validation Required for Menu Item, Service Charge Voids - Control Option
#10
w Validation Required for Menu Item Returns - Control Option #11

w Validation Required - Type Definition #6
Tender/Media File
V-2
Validation Printing
Discount File
Service Charge File


Video Display Unit (VDU)
Description
A Video Display Unit (VDU) is a video monitor that serves as an order device
that can display menu items, discounts, service charges, and tender/media entries.
Usage
A VDU is used to display orders on a screen instead of printing them. The VDU
can be programmed to display orders in one of three possible configurations.
Single Queue - 4 Frame

In this configuration, the VDU screen is divided into four transaction frames, as
shown below.
#1001 #1002 #1003 #1004
Orders exit Orders enter

to the left from the right
Single Queue - 8 Frame

In this configuration, the screen is divided into eight transaction frames, as shown
below.
Orders exit #1001 #1002 #1003 #1004

to the left
#1005 #1006 #1007 #1008

Orders enter
from the right
V-4
Double Queue
In this configuration, the screen is divided into eight frames, but each row of four
frames operates as a separate order device.
Orders exit #1001 #1002 #1003 #1004 Orders enter

#2001 #2002 #2003 #2004
Orders exit Orders enter
The VDU keypad (connected to the VDU controller) is used to remove (or
“bump”) orders from the VDU screen after they have been processed. The keypad
may also be used to recall up to eight orders after they have been bumped.
Up to 32 orders can be held in a buffer in the memory of the VDU controller while
waiting for displayed orders to be bumped.
Enabling
Menu Item Class File, Discount File, Service Charge

File, Tender/Media File
Output To Order Devices 1 through 15 - Output Links #9 through #23
Order Device File

w Device Number field
w Display/Print Revenue Center Name on Orders - Option #7
w Order Device Redirect field
w VDU Screen Configuration

0 = Single Order Queue, 4 Frames
1 = Single Order Queue, 8 Frames

Dual Order Queue Option
Order Device File

To enable the dual order queue option, each half of the screen (upper queue
and lower queue) must be entered in this file as though they were two separate
devices.
w Device Number field
w VDU Screen Configuration - 2 = Dual Order Queue
w Set To Display in Lower Half Of VDU - VDU Type Definition #1
Options
Order Device File
w Sort/ Consolidation Method
w VDU Order Timeout
w Order Device Options
w VDU Type Definition
V-6
Video Display Unit (VDU) - Line-By-Line Display
Video Display Unit (VDU) - Line-By-Line

Display
Description
A Video Display Unit (VDU) is a video monitor that serves as an order output
device that can display transaction detail instead of printing it. The VDU can be
programmed to display detail in one of two ways:
w The entire transaction at one time
w Line-by-line as menu item detail is added to the guest check. Information

that is programmed to display does so in a manner similar to line-by-line
printing.
Usage
The line-by-line display option allows you to expedite order assembly time. Start
assembling an order as menu items are added to the guest check rather than
waiting until it is complete.
If you would like to take advantage of the line-by-line display option, you will
need to satisfy the following requirements:
w Hardware Configuration
w System Programming
Line-by-Line VDU output is not supported in a Local Area

Network (LAN) environment.

What Hardware is Needed?

Here’s a listing of the hardware required to support the Line-by-Line VDU option.
If you would like more information about the VDU hardware, refer to the 1000/
2000/4000/9700 Hardware
Stand-alone Installation Guide.
Hardware Component... Comments...
VDU Controller Rear Connector Panel illustration and

configuration instructions are provided in the
1000/2000/4000/9700 Hardware Stand-alone
Installation Guide.
VDU Monitor TTL type VDU Monitor required; used to
display order information.
VDU Keypad Operating instructions are provided in the 9700
HMS User’s Manual
What Files Need Programming?

If your System configuration doesn’t already include a VDU device, you will
need to complete programming tasks in several files. Use the information
provided in the table shown below to help you complete these tasks.
File... Programming Requirements...
Device Make sure that each of the VDUs included in your

System’s configuration is defined in the Device
file. If you need information about how to add a
VDU to the Device file, refer to the 9700 HMS
Programming Manual.
V-8
Order Device Define the operating characteristics of each VDU

included in your System’s configuration using the
following guidelines:
w Device Number—Enter the device number

(from the Device Table) of the VDU.
w Backup Device Number—Enter 0. Line-by-line

VDU output cannot be backed up to another
device.
w Order Device Type—Enter 1 to designate the

VDU as a remote order device.
w Sort/Consolidation Method—Select the most

appropriate sort and consolidation criteria that
should apply to the format used to display order
information on the VDU. Because seat number
information is not a part of the VDU display
format, the only valid sort and consolidation
options are as follows:
w 0 - No Sort
w 4 - Print Group No Consolidation
If you select a sort type other than 0 or 4 the

System will ignore your selection.
w Order Device Options—All options should be

set OFF. All Order Device Options are invalid
with line-by-line VDU output. The System will
ignore any other setting.
w Order Device Redirect—Enter the device

number (from the Device Table) of the device
to which VDU output will be redirected.

Order Device w # Lines For Requisition Chit—Enter a 0. This

(continued) field is not applicable to line-by-line VDU
output. The System will ignore any other
setting.
w VDU Type Definition —When the line-by-line

VDU output format is used, Type Definitions
#1,#2,#5,#6,#7,and #8 must be set OFF. Set
Type Definitions #3 and #4 ON if you would
like to activate keypad and order beeper
capabilities.
w VDU Screen Configuration —Designate the

screen configuration used by the VDU to
display information. Select Type #3 - Line-by-
Line
w VDU Order Timeout (Seconds) —Not

applicable to line-by-line VDU output. Leave
this field blank
w Order Device Header —Not applicable to a

VDU. Leave this field blank.
Menu Item Class w Output field —Link each menu item class to
the VDU on which you want menu item
information displayed. Enter the Order Device
Number (from the Order Device file) for the
appropriate VDU.
Revenue Center w Prompt/Confirm Option Code #8 - Display
Parameters Summary Totals Only After Order Type
Declared —Set ON to allow an [Order Type]
key to act as a subtotal key. The use of a
Service Total key without this option set on
will prevent the last item ordered from being
displayed on the VDU.
w Order Type Type Definition #4 - Output to

VDU —Set OFF, not applicable to line-by-line
VDU output.
V-10
Touchscreen Screen w Make sure that the Touchscreen Screen file

includes an [Order Type] key that acts as a
subtotal key. The [Order Type] key should not
be confused with a [Service Total] key; they do
not perform the same functions.
A [Service Total] key ends a service round. An

[Order Type] key does not end the service
round; the check remain opens after they key is
pressed.
w If you need information about touchscreen

programming, refer to the 9700 Programming
Manual.
Display of Line-by-Line Output

Screen display includes frames of information—When Line-by-Line VDU
output is in use, menu item information is displayed on the VDU screen in a
manner similar to line-by-line printing. Four frames of information are displayed
at one time. The display format looks like this:
VDU Display
Header identifies VDU#1001
the VDU by name
and number.
Order information
displays here first.
As this frame is
filled, information
wraps to the top
of the next frame.
Four frames available to display menu item information

Conventions govern how information is displayed—When the Line-by-Line

VDU output option is used, order information begins displaying at the top of the
left most frame. When one frame is filled, information automatically wraps to the
top of the next frame. The VDU keypad (which is connected to the VDU
Controller) is used to remove orders from the display screen after they have been
processed.
When displayed in a line-by-line format, the detail for a single order (menu item)
cannot exceed the length of a single column. If an order contains more detail than
can be displayed in a single column, the System will remove enough detail so that
it will. When this occurs, the System will alert the operator by displaying the
following message when the next menu item is ordered, Line-by-Line VDU Order
Truncated.
Order queuing—The VDU can store up to 32 orders in its own memory or order
buffer. If there is more order detail than can be displayed (all four frames are
filled), the order buffer creates a virtual waiting line to get it onto the screen. If
there are orders waiting to get onto the screen, the number of pending orders
flashes at the top of the screen. 1 If the order buffer should fill and be unable to
accept the next order, it will give new orders priority and purge old orders.
Recall Order Queue—The VDU can store up to four orders that have been moved
off screen and hold them for recall if necessary. The [Recall Order] key on the
VDU keypad can be used to re-display the stored information, one order at a time.
Recalled information is displayed in reverse video.
Order buffering—Menu items do not display (they are buffered) until the next
menu item key is pressed or until an [Order Type] key is pressed. Buffering menu
items insures that they are not displayed (and preparation started) until all of the
modifiers have been added. It also prevents last item voids from displaying on the
VDU.
1. Since orders vary in length, the maximum number of orders may be less than 32.
V-12
VDU display detail—The information that is displayed when Line-by-Line VDU

Output is active includes an order identifier and a display detail section. The
following table describes the content of the display detail.
Displayed
Explained...
Information...
Order Identifier w The Order Identifier includes a text descriptor

and an order number. For example,
--- Order 1001 ---
w A Order Identifier precedes each menu item that

is ordered.
w The System uses Order as the default descriptor

in the Order Identifier.
w The Descriptor can be customized. It is defined

in 9700ops.txt. Use the XL9700 Text
Translation Utility to make modifications. For
more information, refer to Translation Utility
in the 9700 HMS Feature Reference Manual.
w Order number equates to check number. If the

Guest Check ID feature is active, the first 13
characters of the ID will be displayed as the
Order number.

Displayed
Explained...
Information...
Display Detail w Menu Item information follows the Order

Number Banner. For example,
--- Order 1001 ---
1 Cream Crab Soup
w Menu Item detail includes a quantity, the menu

item name, and associated condiments, if any.
w The following items will not be included in the

information that is displayed:
- Weight
- Decimal quantity
- Reference information
- SLU/NLU information
- Service charge information
- Discount information
- Payment information
V-14
Operational Exceptions and Considerations

A few words about Voids—If an order is voided it will display in reverse video.
If at the time the order is voided it is in the storage buffer (waiting display) or one
of the last four orders that were bumped off the display, it will appear in reverse
video when displayed.
Operationally, Line-by-Line VDU Output is not designed for establishments that
service total and pickup checks. However, if a check is service totalled, picked up,
and/or voided and, the order is still on the VDU Monitor, the order will be
displayed in reverse video.
A Quantity Line Number Void is not allowed when Line-by-Line VDU Output is
in use. However, Last Item Void, Line Number Void, Direct Void, Transaction
Void, and Transaction Cancel are all valid procedures when Line-by-Line VDU
Output is in use. Keep the following exceptions and considerations in mind as you
use them.
Last Item Void

Void detail does not appear on VDU monitor—Because information is not
displayed until another menu item is ordered or an [Order Type] key is
pressed, detail that is voided using the Last Item Void procedure will not be
displayed on the VDU.
Last Item Void restrictions—Menu item information that has already been
displayed on the VDU monitor cannot be voided via the Last Item Void
procedure even if it is the last item on the guest check. You must use either the
TouchVoid, Direct Void, or Line Item Void procedure to Void items that are
displayed on the VDU monitor.
Transaction Void
All items are highlighted—All items associated with the order, regardless of
whether they are currently displayed, in the storage buffer, or have been
bumped off the screen (up to the last four orders) will appear in reverse video.
Transaction Cancel
The [Transaction Cancel] key cannot be used after an order type has been
selected.

Order Type
A few words about the [Order Type] key—This key performs a subtotal
function at the end of a transaction. However, it does not end the service
round. Additional menu items may be ordered after an [Order Type] key is
pressed. Pressing the [Order Type] key sends the last menu item posted to the
VDU for display.
An order type must be declared before a transaction can be tendered. If
required, the [Tax Exempt] key may only be used after an order type has been
selected.
If the System has been programmed to display summary totals when an
[Order Type] key, such as [Eat In], [Carry Out], or [Total] has been pressed
and additional menu items are entered, the summary information disappears
until the [Order Type] key is pressed a second time.
VDU Keypad
A few words about the Video Display Unit Keypad—The only keys you
need to use on the keypad are the [Next Order] and the [Order Recall] keys.
For more information about the operation of the keypad, refer to 9700 HMS
User’s Manual.
Enabling
Device
w Make sure that each of the VDUs included in your System’s configuration is
defined in the Device file.
Order Device
w Device Number—Enter the device number (from the Device Table) of the
VDU.
w Backup Device Number—Enter 0.
w Order Device Type—Enter 1.
w Sort/Consolidation Method—Select the most appropriate sort and

consolidation criteria.
w Order Device Options—All options should be set OFF.
V-16
w Order Device Redirect—Enter the device number (from the Device Table) of
the device to which VDU output will be redirected.
w # Lines For Requisition Chit—Enter a 0.
w VDU Type Definition—When the line-by-line VDU output format is used,

Type Definitions #1, #2, #5, #6, #7, and #8 must be set OFF. Set Type
Definitions #3 and #4 ON if you would like to activate keypad and order
beeper capabilities.
w VDU Screen Configuration—Select Type #3 - Line-by-Line
w VDU Order Timeout (Seconds)—Leave this field blank
w Order Device Header—Leave this field blank.
Menu Item Class

w Output field—Link each menu item class to the VDU on which you want
menu item information displayed. Enter the Order Device Number (from the
Order Device file) for the appropriate VDU.
Revenue Center Parameters

w Prompt/Confirm Option Code #8 - Display Summary Totals Only After Order
Type Declared—Set ON to allow an [Order Type] key to act as a subtotal key.
w Order Type Type Definition #4 - Output to VDU—Set OFF, not applicable to

line-by-line VDU output.
Touchscreen Screen
w Make sure that the Touchscreen Screen file includes an [Order Type] key that
acts as a subtotal key.

Void Item
Void Item
Description
A Void is a method of correcting an error made during a sales transaction. Several
types of items can be voided, including:
w Menu items
w Discounts
w Service Charges
w Tender/Media
w Tips Declared
w Charged Tips
Usage
The 9700 has several types of voids, as described below:
Line Number Void

A line number void is performed by typing the line number of the menu item you
want removed and pressing the [Void] key. This method cannot be used to void
condiment menu items; when the parent menu item is voided, all condiments are
voided too. To use line number void to remove a transaction detail item, the
operator must be privileged to post items in that privilege group.
Last Item Void

A last item void is performed by pressing the [Void] key twice. It voids the last
item ordered in the current service round. This method cannot be used to void
entries after a PMS posting.1
1. If Revenue Center Control Option #8 (Post Error Corrects as Voids) is set ON, the System will not allow
the use of the Last Item Void function.
V-18
Void Item
Error Corrections
The 9700 can be programmed to count line item voids and last item voids that are
made in the current round (voids made before the check has been subtotalled) as
error corrections. These error corrections are totaled separately from voids, and do
not require authorization. This action may be restricted to privileged employees.
Direct Void
A direct void is done by pressing the [Void] key and then reringing the entry. It
voids that item off the check. If the employee attempting a direct void has the
appropriate privileges and the direct voids have a greater total than the ordered
items, the balance of a check can become negative. Direct voids add to either the
Void totals, or Error Corrections, depending upon your System configuration.
Price Override—Voiding a Menu Item from a Previous

Round
An operator must have specific transaction privileges in order to perform a
direct void of a menu item from a previous round that has a price override. In
addition to being privileged to perform a direct void, the operator may require
the transaction privileges described below.
w If the override price is lower than the original price, the System doesn’t
recognize the menu item from the previous round during the direct void.
In order to void the menu item, the operator must be privileged to void
menu items that are not on the guest check.
w If the override price is higher than the original price, the operator must be
privileged to void menu items in previous rounds.
Transaction Void
A transaction void is used to create a negative check (or Fast Transaction). To use
a transaction void, begin a new check or pickup a current check and press the
[Transaction Void] key. Then enter each menu item to be voided. Continue until
the check is service totalled or tendered.
Void Check
A void check voids an entire check in one action. Press the [Pickup Check] key,
enter the check number, then press the [Void Check] key. All transaction detail on
the check is voided.

Void Item
Reports
Financial Reports
(System, Revenue Center, Employee, Serving Period, Time Period)
w Void total
w Error-correct total
Because voids automatically remove (or decrement) sales totals, they affect all
reports except Employee Labor, Clock-in Status, and Labor Availability.
Enabling

w [Void] - keycode #601
w [Transaction Void] - keycode #603
w [Void Check] - keycode #602
Options

w HRGAS PMS Compatibility - Option #16—Set this ON to cause all tenders
entered on a check to be voided when the check is reopened and the first
tender is voided.

w Print “VVV VOID VVV” Line on Checks - Format Option #16
w Confirmation Required for Line Number Voids - Prompt/Confirm Option #6
w Allow Void Of Discount In Current Service Round Only - Control Option #4
w Allow Void Of Service Charge In Current Service Round

Only - Control Option #5
V-20
Void Item
w Allow Void of Tender/Media in Current Service Round Only - Control

Option #6
w Post Error Corrects as Voids - Control Option #8—Set ON to post line item
voids and last item voids from the current service round to the Voids totals on
financial reports. Set this OFF to post these two types of voids as error
corrections.
w Validation Required for Menu Item, Service Charge Voids - Control Option
#10
Order Device File

w ON = Print VVV VOID VVV Before Voids; OFF = Print Voids in Red -
Option #9
Tender/Media File
w Reverse PMS Itemizers on Void Postings - Type Definition #47
Employee Class File
w Authorize/Perform Void of Menu Items from a Previous Round -

w Authorize/Perform Void and Return of Menu Item Not on Check -

w Authorize/Perform Void of Discounts from a Previous Round -

w Authorize/Perform Void of Service Charges from a Previous Round -

w Authorize/Perform Void of Tender/Media from a Previous Round -


Void Item
w Authorize/Cause a Transaction to Have a Negative Balance - Transaction

Privilege #31
Beginning with Software Version 1.50, this Transaction Privilege no
longer applies to voids. An operator may use voids to drive a transaction
balance negative, regardless of the setting of this Transaction Privilege.
Computing summary totals after voiding menu items proved detrimental
to optimal performance, especially on the HHT. Therefore, this restriction
was removed.
w Authorize/Perform Close of Checks with a Negative Balance -

w Authorize/Perform Voids in the Current Round - Transaction Privilege

#41
w Authorize/Perform Posting of Menu Items in Privilege Groups 1, 2, and 3

- Transaction Privileges #49, #50, #51.
w Authorize/Perform Posting of Discounts in Privilege Groups 1, 2, and 3 -

Transaction Privileges #52, #53, #54
w Authorize/Perform Posting of Service Charges in Privilege Groups 1, 2,

or 3 - Transaction Privileges #55, #56, #57
w Authorize/Perform Posting of Tender/Media in Privilege Groups 1, 2, and

3 - Transaction Privileges #58, #59, #60.
w Authorize/Use [Transaction Void] key - Transaction Privilege #62
w Authorize/Perform Closed Check Pickup and Adjust Tenders, Charged

Tips- Transaction Privilege #68
w Authorize/Perform Void of Menu Items on Closed Checks - Transaction

Privilege #69
w Authorize/Perform Void of Discounts on Closed Checks - Transaction

Privilege #70
w Authorize/Perform Void of Service Charges on Closed Checks -

Transaction Privilege # 71
w Authorize/Perform Direct Voids - Transaction Privilege #72
V-22
Void Item
Related Topics
w “Return Items” on page R-20
w “Transaction Return” in Chapter 11 of the 9700 Feature Overview Manual
w “Validation Printing” on page V-1

Void/Return Reason Codes
Description
The Void/Return Reason Code feature provides the ability to track void and return
activity for menu items and service charges. Tracking data is generated by
requiring the entry of a reason code during a void and/or return transaction.
Usage
Overview
You will find the Void/Return Reason Code feature useful if you have a need to
monitor and track void and return activities for menu items and service charges.
When this feature is active, the System generates tracking data by requiring the
entry of a valid reason code whenever a void and return transaction is initiated.
Void/return reason code data is tracked via a Tracking Group. The tracking group
accumulates count and amount information for each tracked reason code. Void/
Return Reason Code data can be programmed to appear on those reports that
include a tracking group section.
Void/Reason Code Functionality

The following table lists the parameters that apply to the use and operation of the
Void/Return Reason Code feature:
Error Correction Totals w If the Void/Return Reason Code feature is

active, information about a current round
line item void and/or a last item void will not
be included in tracking total information.
Information about a current round void and/
or a last item void will be included in error
correction totals.
Return w Information about the void of a return will
not be tracked.
SQL w SQL will export (last field) the void/return
reason code for menu items.
V-24
Transaction Log File Detail w Information about a last item void and/or the
void of a menu item or service charge in the
current service round is saved as special
detail in the Transaction Log file. It will not
be displayed or printed.
w Detail type 13 is used to depict a menu item

error correction and detail type 14 to depict a
service charge error correction. The
information is displayed in the same format
as the original detail.
w If Revenue Center Parameters file Control

Option #8 - Post Error Corrects as Voids is
set ON, Void/Return Reason Code
information will be included in the detail
that is set to the Transaction Log file.
Transaction Return w The Transaction Return function will
prompt for a Void/Return Reason Code if
any of the detail on the check will post to the
Void control total (menu items/service
charges).
w Transaction Return Void/Reason Code detail

will also post to the Transaction Log.
Transaction Void w The Transaction Void function will prompt
for a Void/Return Reason Code if any of the
detail on the check will post to the Void
control total (menu items/service charges).
w Transaction Void Void/Reason Code detail

will also post to the Transaction Log.
Void/Return Reason Code w Void/Return Reason code information will
be stored in guest check detail and add to the
tracking totals if so configured.
Void - Check w The Void Check transaction will prompt for
a Void/Return Reason Code if any of the
detail on the check will post to the Void
control total (menu items/service charges).
w Void Check Void/Reason Code detail will

also post to the Transaction Log.

Void - Line Number w When the Void/Return Reason Code feature

is active and a line number void is initiated,
the System will prompt for a reason code.
Void - Current Service w Information about a Last Item Void and/or a
Round Direct Void (of a menu item or service
charge) in the current service round will not
tracked. The System will not prompt for a
Void/Return Reason Code.
Void - Priced Condiment w If a menu item containing a priced
condiment is voided, the priced condiments
will add to the parents void/return reason
code tracking.
Void/Return Reason Code Names
Reason Code Names

Void/Return Reason names are programmed in the System Descriptor file. As
many as 32 Void/Return Reason Code names can be defined. Each name can
include up to 16 alpha/numeric characters. Spaces and special characters are
also acceptable.
Pop-up Dialog Box

The System will use the information included in the Descriptor file to
generate the text for the Void/Return Reason Code Pop-up dialog box that is
displayed anytime an operator initiates a void or return transaction. Void
Reason code fields that are left blank (in the Descriptor file) will not be
included in the pop-up dialog box. If there are no Void/Return Reason Code
names are defined, the System will not display the pop-up dialog box.
Display and Print Conventions

The System will use the information defined in the Descriptor file to generate
the text that accompanies the printing and display activities associated with a
void/return function. To learn more about when reason code information will
be displayed or printed, refer to the sections titled, “Void/Return Reason
Codes and the Journal” on page V-27 and “Void/Reason Codes and POS
Operations” on page V-28.
V-26
Void Reason Codes and the Check Files

Void/Return Reason Code information (for menu items and service charges) will
be included in the detail that is posted to the Open and Closed Check files. As a
result, Void/Return Reason Code information is exportable. For more specific
information about exporting Void/Return Reason Code detail, refer to the 9700
HMS SQL Manual.
Void/Return Reason Codes and the Journal

Void/Return Reason Code information will accompany transaction detail posted
to the Journal.The System will also use the text associated with a reason code as
the descriptor that accompanies void/return detail on the Journal.
The Void/Return Reason Code descriptor will always precede the voided/returned
item. For example, a journal entry for a voided menu item might look like this:

1001 Rose 1
401 BLAINE 1
TRN 6/4978 AUG25’96 8:30AM
---------------------------------------------------------------
EAT IN
Void/Return 1001 Rose
Reason Server Error
1 Iced Tea 1.00-V
Subtotal 25.20
Tax 1.51
Amount Due $26.71
=====================================
Void/Return Reason Code information will also appear in the detail that is posted
to the electronic journal.

Void Reason Codes and Order Types

If an [Order Type] key is used for subtotalling purposes, transaction items entered
prior to the declaration of an order type are considered previous round items for
voiding purposes. This means that operators must be privileged to void these
items. Furthermore, if the Void/Return Reason Code is also active, operators will
be prompted to enter the appropriate reason code during a void/return function.
Void/Reason Codes and the Transaction Log File

Void/Return Reason Code information (for menu items and service charges) will
be included in the detail that is posted to the Transaction Log file. As a result,
Void/Return Reason Code information is exportable. For more specific
information about exporting Void/Return Reason Code detail, refer to the 9700
HMS Version 2.00 SQL Manual.
Void/Reason Codes and Tracking Groups

Void/Return Reason Code activity can be tracked by adding the appropriate Void/
Return Reason Codes to a tracking group. By doing so, Void/Return Reason code
usage activity can appear on any report that contains a Tracking Totals section.
You will find it useful to track this information on a System level or better yet,
create a custom report that helps you track void/return information at the
employee level.
Reason codes can be added to any existing tracking group or included in a group
of their own. We recommend that you add them to an existing tracking group.
Tracking Type 20 is used to indicate void/return reason code tracking. The object
numbers associated with this tracking type can range from 0 to 32. A value of 0
indicates that all void/return reasons should be tracked. Any other object number
value in this range will track the corresponding reason code.
Void/Reason Codes and POS Operations

When the Void/Return Reason Code feature is active, anytime a return or void of
an item is attempted (and the item is not a part of the current service round), the
System will prompt the operator to enter a Void/Return Reason Code. The prompt
message (Enter Reason Code) is accompanied by the display of a Void/Reason
Code pop-up dialog box.
The dialog box contains a list of the available void/return reason codes and is
designed to assist the operator with the selection of an appropriate reason code.
The operator must enter a valid reason code in order to complete the transaction.
The selected code will not be displayed at the UWS unless it is associated with a
Direct Void. In the case of a direct void, the Void Reason name will display on the
line that precedes the detail that was voided.
Void/Return Reason Code information will not print on order requisitions,
customer receipts, guest checks. It will however appear on the journal.
V-28
Reports
Void/Return Reason Codes may be tracked and reported on any report that
includes a Tracking Totals Section.
Enabling

w Prompt for Void Reason Code - Prompt/Confirm Option #10
System Descriptor File

w Void Reason Codes field—Enter a name for each possible void/return reason
Optional
w Enable Transaction Log - Option #1
w Error Corrects to Transaction Log - Option #20
w Post Error Corrects as Voids - Control Option #8
Related Topics
w “SQL Access” on page S-48
w “Direct Void” on page V-19
w “Last Item Void” on page V-18
w “Transaction Return” in Chapter 11 of the 9700 Feature Overview Manual
w “Void Check” on page V-19

Voucher Printing
Voucher Printing
Tender/Media keys may be programmed to print Credit Authorization Vouchers.

Tender/Media Type Definition #41 (Require Credit Authorization) and Tender/
Media Output Option #8 (Suppress CA Voucher) control this feature.
Each Revenue Center may also be programmed to print vouchers when tax is
exempted, to be signed by the customer.
A Revenue Center can be programmed to print vouchers when an employee
discount or employee tender is used, to be signed by the employee receiving the
employee meal.
For a complete description of Employee Meal vouchers, refer to “Employee
Vouchers” on page E-12.
For a description of Tax Exempt vouchers, refer to “Tax Exempt Vouchers” on
page T-20.
V-30
WXYZ
Weighed Menu Items
Description
Menu items may be priced according to their weight (by pounds or kilograms).
When a server enters the weight of an item the 9700 will automatically calculate
the sale price.
Usage
Weighed menu items can be posted manually, using the [Item Weight] key. The
9700 System may also use a scale, such as the NCI 4000, to directly enter menu
item weights.
Example 1
The bakery shop in a hotel sells cookies by the pound. A customer asks for 3
cookies from the display case. The operator places those 3 cookies on the scale,
and presses the menu item key. Note that the manual weight entry is only allowed
when the scale reads zero.
9700 HMS A to Z Feature Reference Manual WXYZ-1

Weighed Menu Items
Example 2
Salad bars are often priced by weight. A customer makes a salad, and the operator
weighs it on a scale that is not interfaced to the 9700 System. The operator then
enters the weight and presses the [Item Weight] key, followed by the menu item
key. The weight must be entered as a decimal fraction of a pound (not ounces).
For example, 1-1/2 pounds (1 pound, 8 ounces) is entered as “1.5”.
Reports
The sale of a weighed menu item is recorded as one sale (in menu item Count
fields) regardless of the amount of weight sold.
Enabling
2 Menu Items | Menu Item Maintenance | Sort By Menu Item | <Select

R Tare Weight field—Enter the weight of the empty container in which
the menu item is sold.
1 Menu Item Class
R Weighed Items—Enable this option each Menu Item Class that is
priced by weight.
1 Employee Class

R Authorize/Use the [Item Weight] Key
WXYZ-2
Weighed Menu Items


R 637 - Item Weight
1 System Parameters

R Item Weight in Kilos—If this option is enabled, item weight entries
will be interpreted as kilograms; if disabled, as pounds.
R EYBS
1 Workstations

Definitions
R Enable Scale Interface
9700 HMS A to Z Feature Reference Manual WXYZ-3

Zero-Payment Transactions
Zero-Payment Transactions
Description
This feature allows an employee to post a zero payment to close a guest check
with a zero balance due and to authorize non-privileged employees to do the
same.
Usage
This feature is usually enabled only for managers and provides more control in
cases where sales may be posted and later voided to a zero balance.
Enabling
1 Tender/Media
2 System Information | Tender Media | Key Type=Payment | Key Type

R Post 0.00 Transactions to PMS

R Zero or Negative Transactions Do Not Add to Guest or Guest Check
Counts
1 Employee Class

R Authorize/Perform Close of Checks with a Zero Balance
R Authorize/Perform Close of Checks with a Negative Balance
WXYZ-4
Index
A Banquet Team Service 2 to 6

add guest check 4
Add Check 3 transfer guest check 4
about how to add detail to seat 0 6 base currency 21
about how to keep seat numbers 6 Batch Autosequences 8
described 3 Begin check 10
programming options 9 Beverage Control 14 to 20
programming requirements 8 comparison to guests 16
reporting 7 comparison to 0 15
Add Team Member key 2 tracking totals 19
adding checks Block settlement 4
with fixed price meal 15 Block transfer 23
Add-on tax 18 Breakpoint tax 18
Adjust closed check 10 Breaks
described 10 paid 26
reporting 11 unpaid 26
see also Re-open closed check Buffered printing
when to use 10 vs. line-by-line 8
alternate currency 21 By-Round
ASCII guest check 28, 4
Change sort order 43
ASCII file 27 C
Assign Cash Drawer Key 4
Asynchronous Serial Interface 5, 6 Called autosequences 28 to 31
Audit Trail Canadian Tax 28
reset by autosequence 37 Cancel Total 2
Audit Trail Report 5 Cancel transaction 1
Auto block transfer 23 and the employee closed check report 2
Auto sizing 121 cancel total 2
Autocut Printer 22 Cash drawer 4
programming options 23 assign to more than one operator 9
programming requirements 22 assign to one operator 8
autofire 15 linked to a cash drawer key 4
Autogratuity 20, 70 linked to an operator 4
Automatic Cover Charge 37 media pickup/loan keys 10
Autosequences 26 no sale 1
batch mode 8 opening
called autosequences 28 to 31 outside a transaction 7
control step 32 within a transaction 7
how used 26 programming options 10
see also PC Autosequences programming requirements 8
see also User Workstation Autosequences 26 Cash Drawer Balancing 13
types of 26
B
Backup PC 1, 16
9700 HMS A to Z Feature Reference Manual 1

Index
Cashier Closed check

linked to an operator 13 adjust
programming options 14 files 8
programming requirements 13 mask from reset 33
totals re-open 7
cash drawer balancing 13 Coin changer interface 26
described 12 Collate Program 43
linked to a UWS 12 Compounding tax (Canadian GST) 29
linked to an operator 12 Condiment 27
shift balancing 14 allowed 28
Cashier banking 72 groups 27
Chain & Fire 16 help screen 3
described 16 non-priced 29
programming requirements 17 priced 29
Chain & fire 26 print group 29
Change Transaction Revenue Center 25 programming options 32
Character set programming requirements 30
extended 4 reporting 30
Charged Tip 18, 69 required 28
automating 19 requires other condiment 28
employee tip report 18 Confidence Test 34
including in tracking totals 19 Consolidation 39
programming options 20 and sort 38
programming requirements 19 Control Step 32
Check employee 10 Course Group 10
Check Information Field 7 Course Mask 10
Check Number 22 Cover Charge 37
operator assignment of 22 automatic 37
programming requirements 23 Covers
reset 22 see Guest count
system assignment of 22 Credit Authorization
Check Window 125 interface 39
Checks Credit Card 40
add 3 charged tip 18
re-open closed check 7 keys
reprint 17 accessing 40
see also Guest Checks preamble 40
separate checks 13 programming options 43
transfer 151 programming requirements 42
Child Menu Item 10 validity 41
Class Credit card
tax 17 magnetic card reader 4
Clock in and out preamble 52
grace period 1 Credit Card Lookup 41
Clock In Status Report 24 Credit Card Recall 41
Clock In/Out 24 Currency Conversion 45
programming requirements 24 base equivalent 49
reporting 24 programming options 48
programming requirements 47
reporting 46
Current Entry Line 6
2
Index
Customer Display 50 Edit Detail 1

content summarized 50 described 1
device types 50 how used 1
format 51 programming requirements 5
Customer receipt 53 Edit Seat
and credit authorization 54 TouchShare 96
buffered 53 edit seat
for fast transaction 4 used with fixed price meal 16
line-by-line 53, 8 Edit Seat Status Window 87
programming options 57 Editing a Seat 94
programming requirements 55 Electronic journal 27
Embedded filename variables
D in autosequences 35
Employee
Data Redundancy 1 grace period 1
Database job code link 1
backup 2 Employee Card 7
maintenance 4 custom 7 to 10
audit trail tracking 5 magcard.cfg file 7
programming requirements 6 record format 7 to 8
reports 5 programming requirements 10
via system configurator 4 setup procedure 9
via uws procedures 4 Employee card reader 4
restore 2 programming requirements 5
Date format 8 Employee Financial Report 7
Default Touchscreen 10 Employee ID card 4
Descriptors 13 Employee Meal 11
Detail lines described 11
see Guest check information detail lines entering with a discount key 12
Direct Access Key 3 entering with a tender/media key 12
Direct tips 69 programming options 15
Direct void 19 programming requirements 14
Discount 16 to 26 reporting 14
itemizers 17, 1 voucher 12
prorating 18 Enhanced backup and takeover 16
resetting 18 Environment Variable
programming options 24 tms operator prompt 4
programming requirements 23 Error corrections 19
reporting 22 Error Correction, see Void
subtotal as item 19 Error Log 19
Disk file 27 reset by autosequence 37
Disk Full Warning 30 Euro Currency Conversion 21 to 26
Display Sort Options 38 currency exchange rates 23
Dopplebon printing 33 currency types 21
implementation 22
E Phase 1 22
Phase 2 22
EBUTO 16
Phase 3 23
Edit Check Screen 85
triangulation 25
Edit closed check,
euro to national 25
or Re-open closed check
national to euro 25
see Adjust closed check
Euro Printing 28

Index
Extended character set G

keyboard 4
Goods and service tax, see GST
Grace Period 1, 63
F
F & B Interface 24 using 1
Family Group 1 Gratuity 19
Fast transaction 4 Group numbers
number 22 for multiple checks at a table 13
Fidelio Food & Beverage Interface 24 GST 28
Field help 3 Guest check 4 to 18
in user workstation procedures 13 by-round 28
File identification 19 to 24
embedded filename variables 35 described 19
Finnish rounding 33 how used 21
Fire printing 21
chain & 16 programming options 24
hold & 13 programming requirements 23
Fixed Price Meal 9 suggested usage 19
course key 17 information detail lines 26
important concepts 10 number 22
programming requirements summarized 21 on-demand 1
[Fixed Price Meal] key 17 programming options 12
Fixed Price Meal Keys 10 programming requirements 8
Fixed price menu item 28 reporting 6
Flag Field 6 soft guest check 36
Florida Liquor Surcharge 34 to 37 specifications 20
Establishment Tax Report 36 TouchShare 137
Florida surcharge tax Guest Check Number, see Check Number
with fixed price meal 16 Guest checks
FLU 30 to 35 see also Checks
function key FLUs 30 Guest count 30
function key programming requirements 33, GUI
34 Government Uniform Invoice 44
sales FLUs 32
FLUs 30 H
Food & Beverage Interface 24
foreign currency 21 HALO 11
FPM, see Fixed Price Meal Help screen 2
Function keys 27 Help windows 8
add team member 2 Hexadecimal entry 8
bus table (TMS) 5 High Amount Lockout, see HALO
clear table (TMS) 5 Hold & fire 13, 27
close table (TMS) 5
remove team member 2 I
xfer table rvc (TMS) 4
Icons
xfer table (TMS) 4
see Touchscreen icons
Function Look Ups 30
Inclusive tax 17
Function Look Up, see FLU
Indirect tips 69
Function Lookup Key 3
Interface File 5
Interface Script Language 7
Item discount 16
4
Index
Itemizers 1 LAN
descriptors 2 enhanced backup and takeover 16
discount 17 remote database maintenance 5
programming requirements 3 Language Support 5
prorating 2 Last Entry Line 6
prorating for partial PMS posting 10 Last Item Void 15, 18
service charge 19 Limited availability menu item 6
Line number void 18
J Line-by-line
customer receipt 53, 8
Japanese tax 38 and a credit card payment 9
Job code 1 programming requirements 9
labor analysis 2 Local order output, see Order output
linked to an employee 1 Lookup Key 3
reporting 2 M
Job rate 4
Journal Macro 1
electronic 27 using 2
Magcard.cfg File
K see custom emp cards
Magnetic card reader 4
Keyboard 1 programming requirements 5
layouts 2 Major Group 7
PC keyboard for UWS/3 4 Managers’ procedures,
programming options 9 see User Workstation Procedures
programming requirements 5 Media loan 10
Keys Media pickup 10
alpha 4 Memo checks
assignable by Revenue Center 28 printing 27
categories 1 Menu item
direct access 3 condiment 27
extended character set 4 HALO 12
FLU 30 to 35, 3 limited availability 6
function 27 non-priced 29
key identifier 7 priced by weight 1
lookup 3 prices 28
macro 1 returns 20
NLU 3 weighed 29, 1
shifted vs. unshifted 28, 4 Menu Item Class File
standard character set 4 Option #40 - Add Course Price to Fixed Price
Meal’s Price on Check Only 18
L Menu Item Recipe File 24
Menu level
Labor day start time 1
and repeat round 11
and reporting 2
pop-up vs. staydown 20
and the system parameters file 2
serving periods 30
Labor tracking, see Time & Attendance
Menu Levels
Labor week start day 3
auto
and reporting 3
how programmed 25
and the system parameters file 4
Mod 10 algorithm 41
Multi-tasking 12

Index
N PMS
charged tip 18
national currency 21 inquire 8
Interface - 19 digit reference entry 2 interface 6
PMS - 19 digit reference entry 9 posting 10
NLU 3 prorating itemizers 10
help screens 2 record number requirements 14
pop-up vs. staydown lists 20 PMSwait program 34, 15
NLU Condiment Masking 29 Pop-up 20
No sale 1 field help 3
No Sale Key 4, 7 help screens 2
Non-priced menu items 29 NLUs 2
Non-revenue service charge 20 POS Operations
Number Look Up, see NLU auto sizing 121
Number Lookup Key 3 touchscreen icons 120
Posting
O sales 24
Preamble 40, 52
On-demand
Previous totals 2
customer receipt 53, 8
Price by weight 29
guest check 4, 1
Prices 28
Online Documentation 4
Print Check 26
Open Check Block Settlement keys 4
Print group 33, 39
Open check files 8
sort by 38
Open priced menu items 28
Print memo check 27
Operator
Printer 35
linking to cashier 13
autocut 22
on-demand 1
stand-alone autocut 22
pop-up vs. staydown 20
Printing
training mode 149
by-round 28
Order buffering 12
line-by-line 8
Order output 12
on-demand 1
dopplebon printing 33
order output
sort and consolidation options 38
sort options 38
VDU 4
special by-round 45
Order redirection 19
ProHost, see TMS 1
Order types 21
Prompt Line 6
Overtime 25
Property Management System, see PMS
job rate 4
Provincial sales tax, see PST
PST 28
P P0 through P9 2
Parent Menu Item 10
PC Autosequences 26 R
batch mode 8
Recall Order Queue 12
PMSwait program 17
Recipe File
PC Keyboard for UWS/3 4
see Menu Item Recipe File
PC Workstation 1
Redirect order output, see Order redirection
PCWS 1
Reference entry 8, 1
Period totals 2
Remote database maintenance 5
Philippine tax 41
Remote Log-In 5
Pick up Checks
Remote printing, see Order output
in another Revenue Center 26
6
Index
Remove Team Member key 2 Scale Interface 2

Re-open closed check 7 Screen Display
see also Adjust Closed Check brightness/contrast 8
Repeat round 10 feature of 3
[Repeat Round] key 17 fields explained 6
Report Writer 14 help window 8
Reports keyboard 6
order type profile 22 operator display section 5
period totals 2 PCWS and UWS/3 4
report group 12 programming options 8
resets 2 touchadvantage 8
to disk file 27 transaction descriptors 8
Reprint check 17, 26 UWS/1 & UWS/2 3
Reset Screen Lookup Key 10
period totals 2 Screen save function 7
Returned menu item 20 Seat
Revenue Center 24 TouchShare 96
change to another 25 Seat Window 89
download to UWS/3 26 Seats
guest check numbers 22 handling 11
pick up checks in another 26 programming options 13
sign in 25 seat number 7
Revenue Center Parameters File sort by 38
Minimum and Maximum RVC Serial Num- seats
bers fields 45, 49 used with fixed price meals 14
Number of Guest Check Information Lines Security
field 45, 49 access levels 17
Order Type Type Definition #4 - Output to Separate checks 13
VDU 10 Server 18
Prompt/Confirm Option Code #8 - Display Server banking 71
Summary Totals Only After Order Service charge 19
Type Declared 10 autogratuity 70
Taiwanese GUI End of Range Threshold field cover charge 37
45 itemizers 2, 19
Taiwanese GUI Tax Number Prefix field 45 non-revenue 20
Revenue Center Parameters file open dollar 19
Option #25 - Assign New Seat Numbers 6 open percentage 20
Option #40- Keep Seat Numbers on Added preset dollar 19
Check Detail 7 preset percentage 20
Roll printers 36 programming options 23
Room charge reporting 21
PMS inquire 8 Service total 26
PMS posting 10 chain & fire 16
Round balance due 33 fast transactions 4
RVC_#_TMS_PRMT= hold & fire 13
environment variable 4 programming requirements/options 28
using 26
S Service Total Marker 7
Sales
itemizers 1
posting 24

Index
Serving period 30 T
and menu levels 30
linked to tracking group 30 Table 12
masking tax rates 31 programming requirements 14
programming requirements 31 reporting 14
reporting 31 Table Management System, see TMS
Share an item Taiwanese Tax 44
TouchShare 96, 137 Tax 17 to ??
Shared Definition Files 27, 33 Canadian 28
Shift Balancing 14 exemption 19
Sign in to a Revenue Center 25 Florida Liquor Surcharge 34
SIM 50 Japanese 38
Singapore tax 43 Philippine 41
Slip printers 36 programming requirements 24
Soft check 36 reporting 23
Sorting 38, 39 serving period tax mask 31
nlu/slu 38 Singapore 43
print group 33 Taiwanese 44
programming requirements 40 Thai 46
seat number 39 types 18
transaction detail 38 types defined 17
Special by-round 45 usage summary 22
guest check 4 Tax class 17
Split a guest check and order type 21
TouchShare 137 Tax exempt coupon 31
Split Check Screen 125 Tax exemption 19
Split Check Status Window 126 Tax rates 17
Split pricing 28 TCP interface 5
Splitting a Check 134 TCP PMS interface 6
SQL 48 Team Member 2
Start of the business day, Temporary on-demand,
see Labor day start time see Special by-round
Start of the labor week, Tender Multiplication 57
see Labor week start day Tender/Media 51
Status Information Field 7 credit cards 40
Staydown 20 HALO 11
Step Summary, Autosequence 26 Open check block settlement 4
Subtotal discount 16 pickup/loan keys 10
Subtotal Discount Itemizers 18 PMS posting 10
System Configurator preamble 40
hexadecimal entry 8 service total 19
System Interface Module (SIM) 50 Thai tax 46
System Parameters File Time card 61
Minimum and Maximum System Serial Num- Time chit 61
bers fields 44, 47 Time clock
PC Containing System Serial Number field grace period 1
44, 47 Time clock schedule 63
Taiwanese GUI End of Range Threshold field Time format 8
44 Time periods 66
Taiwanese GUI Tax Number Prefix field 44
8
Index
Time & Attendance Touchscreen icons 102 to 122

clock in and out 24 auto sizing 121
grace period 1 discount file 118
labor day start time 1 ID numbers and file names 103 to 105
labor week start day 3 menu item def file 119
overtime 25 pos operations 120
time cards and time chits 61 serv charge file 118
time clock schedule 63 sys config files 114
Tips 19, 69 tender/media file 119
charged 18 touchscreen file 114 to 117
Tips paid 19, 70 touchscreen SLUs 117
TMS 1 view on desktop 106 to 113
defining an operator prompt 4 ws_icons.dat file 121
described 1 TouchShare 123
messages TouchShare an item 96, 137
guest check update 3 TouchSplit 124
table status update 3 check window 125, 128
table transfer update 3 creating touchscreens 131
Procedure split check status window 126
table status 5 TouchSplit a guest check
table transfer 5 TouchShare an item 137
transfer table 5 Tracking groups 141
programming options 10 serving periods 30
programming requirements 7 tracking totals 142
reporting 6 Tracking Totals
table transfer procedure 4 Beverage Control 19
using a 2 to 3 Training mode 149
TMS Interface enhancement Transaction cancel 1, 15
see TMS Messages Transaction employee 10
To-date totals 2 Transaction Summary Field 7
Totals Transaction void 15, 19
previous, current,to-date 2 Transfer checks 151
totals set number in autosequences 35 auto block transfer 23
touch void block transfer 23
with fixed price meal 20 transferring checks
TouchAdvantage 82 with fixed price meal 15
and the operator display screen 83 Translation Utility 156
how used 82 TSMS, see TMS
TouchEdit 84 TTY interface 5
about the edit check screen 85 TTY PMS interface 6
and the seat window 89
creating touchscreens for 92 U
how used 84
touchscreen buttons 90 Unassign Cash Drawer Key 5
TouchEdit Seat Upcharge 10
TouchShare an item 96 upcharge item 15
Touchscreen User Workstation Procedures 9
default 10 field help key 3
programming requirements 11 User Workstation, see UWS
pop-up vs. staydown 20 UWS 1
display 3
revenue center download 26

Index
UWS Autosequences 26 @/For 1

UWS/3
PC keyboard 4
V
Validation 1
Value added tax, see VAT
variables
embedded in autosequence filenames 35
VAT 17
VDU 4
Line-by-line 7
about programming 8
and order queuing 12
and order redirection 9
and the keypad 16
and the Order Type key 16
and voids 15
display detail 13
display detail explained 14
display formats 11
Order Device Options 9
Order Identifier described 13
screen configuration 10
sort/consolidation methodology 9
order output 12
Video Display Unit
see VDU
Void 18
adjust closed checks 10
re-open closed checks 7
void check 19
voids vs. returns 20
Voucher
employee meal 12
tax exemption 20
W
Weighed menu item 29, 1
weighed menu item
as part of fixed price meal 17
ws_icons.dat file 121
X
XL8700 156
XVision 5
Z
Zero payment transactions 4
10

9700 MAN AtoZFeatureRef

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

9700 MAN AtoZFeatureRef

Uploaded by

Copyright:

Available Formats

Large Enterprise Solutions

Edition Month Year Software Version

1st February 2002 1.5

2nd July 2002 1.7

1-ii Why Read This Manual?

9700 HMS A to Z Feature Reference Manual iii

9700 HMS A to Z Feature Reference Manual v

9700 HMS A to Z Feature Reference Manual vii

9700 HMS A to Z Feature Reference Manual ix

Why Read This Manual?........................................................................... ii

9700 HMS A to Z Feature Reference Manual i

Why Read This Manual?

Who Should Use This Manual?

Finding Additional Information

The 9700 and can be

9700 HMS A to Z Feature w all 9700 System features 100151-506

Hardware 9700 Site Preparation w preparing a site for MICROS 100151-508

9700 HMS A to Z Feature Reference Manual iii

How This Manual is Organized

9700 HMS A to Z Feature Reference Manual v

This symbol is used to bring special attention to a related

This symbol is used to indicate a special tip for using the

This symbol indicates that care should be exercised when

Design and Production

9700 HMS A to Z Feature Reference Manual vii

9700 HMS A to Z Feature Reference Manual A-1

w “Prices” on page P-28

w Press the appropriate [Add/XFR] key.

9700 HMS A to Z Feature Reference Manual A-3

ADDED FROM CHK 196

Add Check Methods

w Add/Trans By #, RVC?—This method provides the ability to use the check

w Add/XFR By # RVC1 - Add/XFR By # RVC 8—This method provides the

w Add/Trans By Table—This method provides the ability to use the table

w Add/XFR Check By ID—This method provides the ability to use a guest

w Add/Trans Check SLU—This method generates a touchscreen that displays a

9700 HMS A to Z Feature Reference Manual A-5

...guest checks belonging to other ...they are sorted according to

If Guest Checks are to be added across Revenue Centers, the Order

Adding Detail to the Destination Check

w By adding the detail to newly assigned seat numbers—(RVC Information |

w By keeping the seat numbers from the original check—RVC Information |

1 1 Coke 1.00 1* 1 1 Chardonnay 2.50 1*

2 1 Crab 4.50 1* 2 1 Clams Casino 3.50 1*

Detail on the Destination check after the Add transaction is completed

Financial Reports (Revenue Center and Employee)

9700 HMS A to Z Feature Reference Manual A-7

Employee Closed Check Report - Report Writer Version

Employee Closed Check Report - UWS Version

R 437 - Add/Trans Check

R 499-519 - Add/Trans Check

R 437 - Add/Trans Check

R 499-519 - Add/Trans Check

R Authorize Adding of Checks in Same Revenue Center

1 Revenue Center Parameters

w “Transfer Checks” on page T-151

9700 HMS A to Z Feature Reference Manual A-9

Adjust Closed Check

If a cashier declaration is required for tendering (Cashier

Employee Closed Check Reports

R 422 - Adjust Closed Check

R 422 - Adjust Closed Check