Sie sind auf Seite 1von 730

Large Enterprise Solutions

Large Enterprise Solutions A to Z Feature Reference Manual Copyright 2002 MICROS Systems, Inc. Columbia, MD

A to Z Feature Reference Manual

Large Enterprise Solutions A to Z Feature Reference Manual Copyright 2002 MICROS Systems, Inc. Columbia, MD

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

Table of Contents

Preface

1-ii

Why Read This Manual? Notation Conventions

1-vi

A

A-1

@/For Function Add Check Adjust Closed Check Amount Paid vs. Amount Due Display Option Audit Trail Autofire Autocut Printing Auto Menu Level Autosequences

A-3

A-10

A-13

A-14

A-15

A-22

A-24

A-26

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

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

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 Interface File Interface Script Language

I-5

I-7

J

J-1

Job Codes

J-4

Job Rates

K

K-1

Keyboards-User Workstation

K-11

Keyboard Workstation

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 Magnetic Card Reader Major Group Media Pickup/Loan Tendering Keys Multi-tasking Capability

M-4

M-7

M-10

M-12

N

N-1

No Sale Key Number Lookup (NLU)

N-3

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

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

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

T

T-61

Time Cards and Time Chits Time Clock Schedule Time Periods Tips Handling TouchAdvantage TouchDetail TouchEdit Touchscreen Icons TouchShare TouchSplit Tracking Groups Training Mode Transfer Checks Translation Utility Two-Color Printing on Guest Check Header/Trailer

T-63

T-66

T-69

T-80

T-82

T-84

T-102

T-123

T-124

T-141

T-149

T-151

T-156

T-164

U

U-1

User Workstation User Workstation Procedures

U-9

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-1Weighed Menu Items WXYZ-4Zero-Payment Transactions

Index

Table of Contents

Preface In This Chapter In this preface, you will find information about the organization, conventions,

Preface

In This Chapter

In this preface, you will find information about the organization, conventions, and contents of this manual.

Why Read This Manual? Notation Conventions

ii

vi

Preface Why Read This Manual?

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.

Preface Why Read This Manual?

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 ordered by part number

HMS

is comprised of these manuals

which include information about

System

 

9700

HMS A to Z Feature

all 9700 System features

100151-506

Reference Manual

modifying the database for each feature

9700

Feature Overview

an introduction to the 9700 System and descriptions of major features

100151-523

Manual

9700

HMS Property

basic instructions on how to maintain and update an existing 9700 System database

MD0006-008

Maintenance Guide

Software

Library

9700 HMS SQL Manual

importing and exporting data into and out of the 9700 database

100151-502

9700 System files, fields, and status flags

9700

HMS System Setup

installing/upgrading the 9700 System software

100151-507

Manual

Hardware

9700

Site Preparation

preparing a site for MICROS equipment installation

100151-508

Library

Guide

AC power requirements

environmental considerations

Preface Why Read This Manual?

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:

Description

Usage

Examples

Reports

Enabling

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.

Preface Why Read This Manual?

Related Topics

This section will guide you to another section if you need more information about a topic related to the feature.

Preface Notation Conventions

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”

Preface Notation Conventions

Symbol

Preface Notation Conventions Symbol This symbol is used to bring special attention to a related feature.

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 featureis used to bring special attention to a related feature. This symbol indicates that care should

to indicate a special tip for using the current feature This symbol indicates that care should

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.

Preface Notation Conventions

A
A

@/For Function

Description

The [@/FOR] key is used to:

Post a quantity of items via an NLU

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].

@/For Function

Enabling

Keyboards

Touchscrns & Keyboards | Keyboards | Key Configuration | [Type = Function] | [Function Key Categories = Transaction] | Link

600 - @/For

WS Touchscreens

Touchscrns & Keyboards | WS Touchscreens | Touchscreen Screen | [Function Key Categories = Transaction] | Number

600 - @/For

Related Topics

“Function Keys” on page F-27

“Prices” on page P-28

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:

Pick up the destination guest check.

Press the appropriate [Add/XFR] key.

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?”

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:

9700

MICROS 8700

George’s check, before being added to Samantha’s.

 

Fine Dining System

411 GUSTINO

411 GUSTINO
411 GUSTINO

------------------------------

CHK 196 JUL24’94 11:29AM GST 1

 

------------------------------

9700

MICROS 8700

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 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 added.

SUBTOTAL

30.20

SALES TAX

1.39

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:

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.

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.

Add Check

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.

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.

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.

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.

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.

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

guest check includes an ID, a check number, and/or a table number

a

the

ID becomes the primary

sort criteria, and all guest checks with an ID are displayed first in alphabetical order.

guest check includes a table number and a check number, but no ID

a

the

table number becomes the

primary sort criteria, and all guest checks with table numbers are sorted by table/group. They are displayed after checks with an ID.

a

the

check number becomes the

guest check includes a check number 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.

one) can be included in a Function Lookup (FLU) key. If Guest Checks are to be

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:

By adding the detail to seat zero (System default)—Transaction detail from the original check is posted to seat 0 on the destination check.

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.

Add Check

1 Coke

1

1.00

1*

2 Crab

1

4.50

1*

By keeping the seat numbers from the original checkRVC 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 Chardonnay

2.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 Chardonnay

1

2.50

1*

2 Clams Casino

1

3.50

1*

3 Crab

1

4.50

1*

4 Coke

1

1.00

1*

5 Crab

1

4.50

2*

6 Crab

1

4.50

2*

1* 5 Crab 1 4.50 2* 6 Crab 1 4.50 2* Detail from the Original check

Detail from the Original check

remains associated with seat 1 on the Destination check

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:

Begun

Transferred In

Paid

Transferred Out

Add Check

Employee Closed Check Report - Report Writer Version

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.

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

An “A” prints next to any check involved in an add transaction (i.e., either an original check or a destination check.)

Enabling

Keyboards

Touchscrns & Keyboards | Keyboards | Key Configuration | [Type = Function] | [Function Key Categories = Check Begin/Pickup] | Link

437 - Add/Trans Check

Touchscrns & Keyboards | Keyboards | Key Configuration | [Type = Function] | [Function Key Categories = Check Operations] | Link

499-519 - Add/Trans Check

WS Touchscreens

Touchscrns & Keyboards | WS Touchscreens | Touchscreen Screen | [Function Key Categories = Check Begin/Pickup] | Number

437 - Add/Trans Check

Touchscrns & Keyboards | WS Touchscreens | Touchscreen Screen | [Function Key Categories = Check Operations] | Number

499-519 - Add/Trans Check

Employee Class

Personnel | Employee Maintenance | [Sort By Class] | Guest Checks | Guest Check Control

Authorize Adding of Checks in Same Revenue Center

Authorize Adding of Checks Between Revenue Centers

Add Check

Optional Settings

The following options may be set on a discretionary basis:

Revenue Center Parameters

RVC Information | RVC Parameters | Format | Format Options

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.

RVC Information | RVC Parameters | Options | General

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.

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.

RVC Information | RVC Parameters |General

Add/Transfer Revenue Center fields—Specify up to eight specific revenue centers that are addressed by an [Add/XFR] key.

Related Topics

“Block Transfer Checks” on page B-23

“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.

key to change the tender from VISA to American Express. If a cashier declaration is required

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.

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:

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).

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

Keyboards

Touchscrns & Keyboards | Keyboards | Key Configuration | [Type = Function] | [Function Key Categories = Check Begin/Pickup] | Link

422 - Adjust Closed Check

WS Touchscreens

Touchscrns & Keyboards | WS Touchscreens | Touchscreen Screen | [Function Key Categories = Check Begin/Pickup] | Number

422 - Adjust Closed Check

Adjust Closed Check

Optional Settings

The following privilege options may be set on a discretionary basis:

Employee Class

Personnel | Employee Maintenance | [Sort By Class] | Printing | Check/ Receipt

Authorize/Perform Reprinting of a Closed Check

Personnel | Employee Maintenance | [Sort By Class] | Guest Checks | Guest Check Control

Authorize/Perform Closed Check Pickup Authorize/Perform Closed Check Adjust

Revenue Center Parameters

RVC Information | RVC Parameters | Options | General

Fast Transactions Do Not Generate Closed Check Records

RVC Information | RVC Parameters | Posting & Control | Control

Cashier Totals Declaration Required with Tender/Media and Tips Paid Allow Overtender of Closed Checks

Related Topics

“Guest Check” on page G-4

“Line Number Void” on page V-18

“Re-open Closed Check” on page R-7

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

Workstation File

System Hardware | Devices | Options | Type Definition

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.

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.

confirming this entry, the check is scheduled in the System. Printing The Time To Fire field

Printing

The Time To Fire field is available for use in SIM scripts and SQL queries.

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:

An Autofire check can be scheduled from 1 to 150 days in advance, with the default being 30 days.

A previously posted guest check cannot be used as an Autofire check.

Once an Autofire check has been fired, it then becomes a regular check and all related check functions can be performed.

Autofire

Menu item additions and voids on Autofire checks are treated as previous round items, while tender changes are treated as current round items.

Split checks are not allowed.

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

Autofire Check Report

Open Check Report

Enabling

System Parameters

System Information | System Parameters | General

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.

RVC Parameters

RVC Information | RVC Parameters | Autofire

Autofire Workstation—Select the workstation from which Autofire checks will be fired and printed.

Autofire Checks Allowed—Specify the number of Autofire checks that may be scheduled. The maximum allowed is 9999.

Default Autofire Tender/Media

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.

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

Tender Media

System Information | Tender Media | General

Create a new Tender Media record.

Name—Enter Autofire as the name of the new key.

Key Type—Select Service Total.

System Information | Tender Media | <Select Autofire Key> | Key Type | Category=POS Ops Behaviors

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.

System Information | Tender Media | <Select Autofire Key> | Menu Levels

Specify the menu levels on which the Autofire key is active.

System Information | Tender Media | <Select Autofire Key> | Output

Tender Output—Select the output device(s) for Autofire checks.

System Information | Tender Media | <Select Service Total Key> | Category=POS Ops Behaviors

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.

Autofire

Touchscrns & Keyboards

Touchscrns & Keyboards | WS Touchscreens | Touchscreen Screen

Create a touchscreen, similar to the one shown below, for date and time entry for Autofire checks.

shown below, for date and time entry for Autofire checks. Screen Name —Enter a name for

Screen Name—Enter a name for this touchscreen, such as Autofire Screen.

Autofire

Key—Current MMDDYY

Legend—Specify Current MMDDYY for the key label.

Type—Select 9 - Keypad.

Number—Select 22 - Current MMDDYY.

Key—Enter

Legend—Specify Enter for the key label.

Type—Select 9 - Keypad.

Number—Select 12 - Enter.

Key—Clear

Legend—Specify Clear for the key label.

Type—Select 9 - Keypad.

Number—Select 13 - Clear.

Key—Cancel

Legend—Specify Cancel for the key label.

Type—Select 11 - Function.

Function Key Categories—Select Movement.

Number—Select 20 - Cancel.

Key—Numbers 0-9 and 00 (repeat these steps for each number)

Legend—Specify a number 0-9 for the key label.

Type—Select 9 - Keypad.

Number—Select the appropriate Numeric setting (0-9 or 00).

Key—Decimal Point

Legend—Specify “.” for the key label (do not include the quote marks).

Type—Select 9 - Keypad.

Number—Select 11 - Decimal “.” key.

Add an Autofire button to an appropriate touchscreen, such as the Food shell.

Legend—Enter a key label, such as Autofire.

Type—Select 7 - Tender/Media.

Touchscrns & Keyboards | WS Touchscreens | Touchscreen Assign

Autofire Time Edit Screen—Select the Autofire screen you created previously (for date/time entry).

Autofire

UWS Autosequences

Reporting | UWS Autosequences

Create a new Autosequence.

Autosequence Name—Enter a name for the Autosequence, such as Autofire Reporting.

Reporting | UWS Autosequences | <Select Autosequence> | <Add Autosequence Step>

Type—Select Report.

Report #—Select 30-Autofire Open Check.

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.

automatically cut the paper below the printed information. Epson U200B Rollcut Printer Usage Autocut printers are

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

Device Table

System Hardware | Devices | General

Device Type—Select 2 - Roll Printer.

System Hardware | Devices | Printers

These fields assign certain printers for specific tasks (e.g., Customer Receipt Printer, Credit Card Voucher Printer, etc.)

Autocut Printing

Order Devices

System Hardware | Order Devices

Fields in this file assign specific printers to remote and local order printing.

Optional Settings

The following options may be set on a discretionary basis:

System Parameters

System Information | System Parameters | Reporting | Reporting Options

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.

Revenue Center Parameters

RVC Information | RVC Parameters | Format | Format Options

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.

Order Devices

System Hardware | Order Devices |General | Order Device Options

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

“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.

levels for up to eight time slots in a day or a week. The Type Definition

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.

Auto Menu Level

Enabling

Revenue Center Parameters

RVC Information | RVC Parameters | Menu Levels

For each Auto Menu Level, set the appropriate fields (e.g., Menu Level, Start Time, End Time, etc.).

fields (e.g., Menu Level, Start Time, End Time, etc.) . Auto Menu Levels cannot be programmed

Auto Menu Levels cannot be programmed to have overlapping start and end times on the same day.

Revenue Center Descriptors

RVC Information | RVC Descriptors | General | [Select a Category]

Main Menu Level Names

Sub-Menu Level Names

Related Topics

“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:

Access all reports

Print to disk

Print to the operator display or PC monitor

Reset reports

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.

Autosequences

UWS Autosequences

These are designed to be taken from a User Workstation. Reports may be output to:

the operator display

a printer defined in the Workstation Table (usually a roll printer)

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:

change the totals set(s)

save a totals set(s)

export database information

save or reset the Audit Trail File or the Error Log File

run an external program (i.e., non-9700 System application)

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

#10

Autosequence

#27

Step 1

Step

Step

Step 16

Step 16

Step 1: System Tip Report

Step 2: Call #27

Step 3: Table Sales Report

Step 4
Step 4
Step 2: Call #27 Step 3: Table Sales Report Step 4 Step 3 in Autosequence #10
Step 2: Call #27 Step 3: Table Sales Report Step 4 Step 3 in Autosequence #10

Step 3 in Autosequence #10 executes after Autosequence #27 is complete.

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.

Autosequence Autosequence #10 #27 Step 1 Step 1: System Tip Report View: System View: RVC
Autosequence
Autosequence
#10
#27
Step 1
Step 1: System Tip Report
View: System
View: RVC
Step 16
Step 2: Call #27
View: RVC
Step 3: Table Sales Report
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.

Step 3 inherits “RVC” from Step 2.

Autosequence Autosequence #10 #27 Step 1 Step 1 inherits “RVC” from Step Step 1: System
Autosequence
Autosequence
#10
#27
Step 1
Step 1 inherits
“RVC” from Step
Step 1: System Tip Report
View: System
View: Inherit
Step 5
Step 2: Call #27
View: RVC
View: System
Step 16
Step 3: Table Sales Report
View: Inherit
Step 16 inherits
“System” from
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
Step
Step
Step
Step
Step
Step
Step
Step
Chain
Step
Step
Step
Step
Step
Step

Remember to leave a trail of bread crumbs.

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.

Autosequence

#10

Autosequence

#27

Step 1

#27 Step 1 Step Step Step 16

Step

#27 Step 1 Step Step Step 16

Step

Step 16

Step 16

Step 1: System Tip Report

Step 2: Job Code Report Call #27

Step 3: Table Sales Report

Step 4

Code Report Call #27 Step 3: Table Sales Report Step 4 Autosequence #27 executes after the
Code Report Call #27 Step 3: Table Sales Report Step 4 Autosequence #27 executes after the
Code Report Call #27 Step 3: Table Sales Report Step 4 Autosequence #27 executes after the

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.

Autosequence Autosequence #10 #27 Step 1 Step 1: System Tip Report Step Step 2: Control
Autosequence
Autosequence
#10
#27
Step 1
Step 1: System Tip Report
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.

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:

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:

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 SEP25’94 03:57AM

33.09

356 SEP25’94 03:58AM SEP25’94 03:59AM

16.25

357 SEP25’94 03:59AM SEP25’94 04:01AM

4.87

358 SEP25’94 04:00AM SEP25’94 04:01AM

21.86

Closed Check File at the time the file is reset.

CHK OPENED/CLOSED --- -----------------

PAYMENT

--------

357 SEP25’94 03:59AM SEP25’94 04:01AM

4.87

358 SEP25’94 04:00AM SEP25’94 04:01AM

21.86

Closed Check File after being 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.

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:

$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.

$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:

Employee Open Check

Employee Financial

Employee Closed Check

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

UWS Autosequences

Reporting | UWS Autosequences | General

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.

PC Autosequences

Reporting | PC Autosequences | General

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.

Workstations

System Hardware | Devices | Printers | Printers

UWS Report

Keyboards or WS Touchscreens

Touchscrns & Keyboards | Keyboards | Key Configuration | [Type = Function] | [Function Key Categories = General] | Link

Touchscrns & Keyboards | WS Touchscreens | Touchscreen Screen | [Type = Function] | [Function Key Categories = General] | Number

300 - Mode—This key is used to change from the Transaction Mode to UWS Procedures and UWS Reports.

Autosequences

Optional Settings

The following options may be set on a discretionary basis:

UWS Autosequences

Reporting | UWS Autosequences | General

PC Autosequences

Reporting | PC Autosequences | General

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:

Type—Set this to 3-External Program

External Program User Interface Type—Set this to 0-No User Interface

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 the variable <filename>.

errlog_b save <filename>

atrail_b save_reset <filename>

These commands save the file to the file specified in the variable <filename>, and then reset the file.

errlog_b save_reset <filename>

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

System Parameters File

System Information | System Parameters | Workstations

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.

PC Table

System Hardware |Devices | Select PC | General | Printer Settings

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.

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.

Lines/Report Page—This field determines the number of lines that a report will print before starting a new page and printing another header.

Autosequences

Report Configuration File

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.

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.

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.

Totals Sets

System Information | Totals Sets | General

For each saved totals set defined in a PC Autosequence, complete all fields in this file.

Optional Settings

The following options may be set on a discretionary basis:

UWS Autosequences

Reporting | UWS Autosequences | General

Privilege Group

PC Autosequences

Reporting | PC Autosequences | General

Privilege Group

Autosequences

Employee Class

Personnel | Employee Maintenance | [Sort By Class] | Procedures & Reports | UWS PC Auto Sequences

Run UWS Reports In Another Revenue Center

Reset UWS Reports

Reset UWS Reports without Printing—if Reset UWS Reports is enabled.

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

“Batch Autosequences” on page B-8

“PMSwait” on page P-15

“Report Writer” on page R-14

“Using Autosequencer” in Chapter 1 of the 9700 Reports Manual

B
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

System Hardware | Interface | General

Backup PC #

Banquet Team Service

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.

Banquet Team Service

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

Downe, Mark

 

Ready For Your Next Entry

 

3

4

Ender, Bart

Medium

Lunch

Rose

 

5

---------------------------------------------------------------

6

1 Fried Cheese

2.95

CHK 61

 

7

1 Bread Sticks

1.50

8

9

2 Glass Rose

1 Iced Tea

3.00

.75

Mikey #1

JAN 25 ‘96

00

8:30PM

GST 1

10

1 Spiced Shrimp

7.95

SUBTOTAL

 

11

12

13

14

15

16

1 New York Strip

9.95

TAX AUTO SVC CHG OTHER SVC CHG PAYMENT TOTAL DUE

 

23.49

1.17

3.52

3.50

31.68

0.00

17

 

Eat In

 

TTL 0.00

18

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.

(**). A single asterisk means the check belongs to another operator. 9700 HMS A to Z

Banquet Team Service

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 without team information

Lose team information on original check

Add check with no team info to an existing check which includes team information

Team information stay with existing check

Transfer check with existing team information

Check employee of original check will be replaced with the check employee of the new check. The remaining team information will stay with the check 1

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.

member’s name will now be displayed first on the UWS. If a team member guest check

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.

Banquet Team Service

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.

Tip Report. For example, Autogratuties and Service Charges. No other report is affected by the Banquet

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.

Tip). The totals were split among each employee on a Banquet Service check. 9700 HMS A

Banquet Team Service

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

Revenue Center Parameters

RVC Information | RVC Parameters | Format | Format Options

Use Team Information on Guest Check

Keyboards or WS Touchscreens

Touchscrns & Keyboards | Keyboards | Keyboard Overhead | <Select Keyboard> | Key Configuration | Type=Function | Function Key Categories=Check Operations | Link

Touchscrns & Keyboards | WS Touchscreens | Key Configuration | Type=Function | Function Key Categories=Check Operations | Number

549 - Add Team Member—This key will add an employee as a Team Member for the current transaction.

550 - Remove Team Member—This key will remove a team member from the team for the current transaction.

Employee Class File

Personnel | Employee Maintenance | Sort By Class | Guest Checks | Editing Checks

Authorize/Add Team Members to Check

Authorize/Remove Team Members from Check

Related Topics

Refer to the 9700 SQL Manual.

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

parameters and cannot output reports to the display. Usage Batch mode allows autosequences to be executed

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:

Log in as root (the superuser).

Enter su - m9700 (Make sure there is a space before and after the dash {–} character.)

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.

Batch Autosequences

Argument

Remarks

<aseqn>

Multiple PC Autosequences may be run in a single batch.

Enabling