centralized data management 62

8/11/2019 Centralized Data Management 62

1/196

Aloha CentralizedData ManagementUsers uide

Version 6.2


2/196

Copyright

Copyright 2005, Radiant Systems, Inc. The information contained in thispublication is confidential and proprietary. No part of this document may bereproduced, disclosed to others, transmitted, stored in a retrieval system, or translated into any language, in any form, by any means, without written per-mission of Radiant Systems, Inc.

Radiant Systems, Inc. is not responsible for any technical inaccuracies or typographical errors contained in this publication. Changes are periodicallymade to the information herein; these changes will be incorporated in new

editions of this publication. Any reference to gender in this document is notmeant to be discriminatory. The software described in this document is pro-vided under a license agreement. The software may be used or copied only inaccordance with the terms of that agreement.

Radiant Systems, Inc., 2005. All Rights Reserved. ALOHA is a U.S. Reg-istered Trademark of Radiant Systems, Inc. Microsoft , and Windows are

registered trademarks of Microsoft, Inc. IBM

is a registered trademark of International Business Machines Corporation. Other products mentioned aretrademarks or registered trademarks of their respective companies.


3/196

v6.2

Table of Contents

Introduction

Getting Started ...................................................................... 1-1

Installation Requirements ................................................................. 1-4Central Site System Requirements................................................1-4Store System Requirements..........................................................1-5

General CDM Requirements .........................................................1-6CDM Installation ............................................................................... 1-7CDM Components ..........................................................................1-11

Centralsite File.............................................................................1-11CDM Directories ..........................................................................1-13CDM Utilities ................................................................................ 1-15

Aloha.ini Variables ....................................................................... 1-16

Aloha DBUP Utility.......................................................................1-16Data Updates.................................................................................. 1-18Life of a Data Update................................................................... 1-18Data Ownership ...........................................................................1-19Record Update Files .................................................................... 1-19Data Transfer Flow and Store Processing...................................1-22

Store Lockout File (Slo.cfg) ............................................................1-29Create Store Lockout File ............................................................1-30Store Lockout File Format ........................................................... 1-30Test the Store Lockout File .......................................................... 1-31

Define Stores .................................................................................. 1-33Define Store Groups ....................................................................... 1-35Summary ........................................................................................1-37
http://chapter.pdf/http://chapter.pdf/


4/196

ii Table of Contents Aloha CDM Users Guide v6.2

Data Management..................................................................2-1

Master Database Compliancy .......................................................... 2-4

Dedicated Number Ranges ........................................................... 2-4ID Marker Files .............................................................................. 2-7Separators..................................................................................... 2-8Table of Contents .......................................................................... 2-8

Item Maintenance............................................................................. 2-9Store Lockout of Items .................................................................. 2-9Store Specific Items .................................................................... 2-10

Price Maintenance.......................................................................... 2-23Configuring Price Changes ......................................................... 2-23

Promotion Maintenance ................................................................. 2-32Store Lockout of Promotions ....................................................... 2-32Promotions .................................................................................. 2-33

Tax Maintenance............................................................................ 2-42Event Maintenance......................................................................... 2-46

Configure Corporate Events........................................................ 2-48Summary ........................................................................................ 2-53

Distribution Wizard................................................................3-1

Common Buttons Used in the Distribution Wizard ........................... 3-4Launch Distribution Wizard .............................................................. 3-4Distribution Wizard Welcome ........................................................... 3-8Create a New Update ....................................................................... 3-9

Send a Corporate Event .............................................................. 3-19Work with a Pending Update.......................................................... 3-21

Finalize Updates.......................................................................... 3-23Change Update Name................................................................. 3-25Modify the Effective Date ............................................................ 3-27Delete Updates............................................................................ 3-30

Change the Effective Date of Finalized Updates............................ 3-32

Send Store File............................................................................... 3-35Send Store Events ...................................................................... 3-36Send Store Lockout File .............................................................. 3-40

View Reports .................................................................................. 3-43Summary ........................................................................................ 3-45


5/196

Aloha CDM Users Guide v6.2 Table of Contents iii

CDM Database Compliancy .................................................A-1

Globally Owned File Recommendations...........................................A-2

Access Levels (Acc.dbf) ................................................................A-2 Automenu (Amnu.dbf) - TS Only ...................................................A-2Category (Cat/Cit.dbf)....................................................................A-3Comp (Cmp.dbf) ............................................................................A-3Composite Tracking Items (Ctk.dbf) - QS Only .............................A-4Exception Modifier (Exc.dbf) - TS Only..........................................A-4Fixed Pricing (Fixpr.dbf) - TS Only ................................................A-5Flex Tax (Flextax.dbf) ....................................................................A-5Foreign Currency (Multcurr.dbf).....................................................A-5Item (Itm.dbf) .................................................................................A-5Job Code (Job.dbf) ........................................................................A-6Job Code by Revenue Center (Jrv.dbf) .........................................A-6Labor Groups (Lab.dbf) .................................................................A-6Menu (Mnu.dbf) - TS Only .............................................................A-7Modifier (Mod.dbf)..........................................................................A-7No Sale Reasons (Nosalersn.dbf) .................................................A-8Order Modes (Odr.dbf) ..................................................................A-8Performance Measures (Prf.dbf) ...................................................A-8Periods/Day Parts (Prd.dbf)...........................................................A-8Price Changes (Pc.dbf)..................................................................A-8Price Level (Prl.dbf) .......................................................................A-9Promotion (Pro.dbf) .....................................................................A-10

Quantity Item Price (Qtypr.dbf) ....................................................A-11QuickService Menu (Pnl.dbf, Btn.dbf, Scr.dbf) - QS Only ...........A-11Recipe (Rcp.dbf)..........................................................................A-12Regions (Reg.dbf)........................................................................A-12Revenue Centers (Rev.dbf) .........................................................A-12Security Level (Seclvl.dbf, Seclvldt.dbf) v5.0+ Only ....................A-12Submenu (Sub.dbf) TS Only........................................................A-12Surcharge (Sur.dbf) .....................................................................A-13Survey (Survey.dbf) .....................................................................A-13Tare Weights (Tare.dbf)...............................................................A-13Tax (Tax.dbf) ...............................................................................A-13Tender (Tdr.dbf)...........................................................................A-14Termination Reasons (Zap.dbf) ...................................................A-14Tracking Items (Trk.dbf) - QS only...............................................A-14


6/196

iv Table of Contents Aloha CDM Users Guide v6.2

Void Reason (Rsn.dbf) ................................................................ A-15Volume Levels (Vol.dbf) - QS Only .............................................A-15

Aloha POS Database Files.............................................................A-16

Distribute Datasets............................................................... B-1

Back Office Security Dataset......................................................... B-1Comps Dataset..............................................................................B-2Item Prices Dataset .......................................................................B-3Items Dataset ................................................................................ B-4Jobs Dataset .................................................................................B-5

POS Security Dataset ................................................................... B-5Promotions Dataset .......................................................................B-6QuickService Menus Dataset ........................................................B-7Revenue Dataset...........................................................................B-7System Dataset ............................................................................. B-8TableService Menus Dataset ........................................................B-8Taxes Dataset ...............................................................................B-9

Tenders Dataset............................................................................B-9Troubleshooting ................................................................... C-1

Corporate CDM Workstation Troubleshooting .................................C-1Enterprise menu option is missing. ...............................................C-1Cannot access event groups. ........................................................C-1Cannot find Distribute.exe. ............................................................C-1

Not Authorized for Distribute Error ................................................C-2Store Lockout (Slo.cfg) is not working. ..........................................C-2Cannot locate the record update. ..................................................C-2Cannot locate the event update. ...................................................C-3Distribute does not accept the record name..................................C-3The update cannot finalize. ...........................................................C-3Cannot find Slo.cfg. .......................................................................C-4

Store Troubleshooting ......................................................................C-5Record update did not process. ....................................................C-5This record is controlled by Corporate Error .................................C-6Update did not process on the Effective Date ...............................C-6


7/196

Aloha CDM Users Guide v6.2 Table of Contents v

Updates are implemented sooner than scheduled. ...................... C-7End-of-Day is taking longer than five minutes to process............. C-7

GlossaryIndex


8/196

vi Table of Contents Aloha CDM Users Guide v6.2


9/196

Introduction

Centralized Data Management (CDM) provides the ability to manage datafrom a central location, thus significantly simplifying operational elements,such as system backup, data redundancy and system security. CDM also pro-vides the ability to determine elements that are corporate-owned and store-owned. For example, employee data, such as adding and terminating, is con-sidered store-owned, but sales items, such as menu changes and pricechanges, are Corporate-owned. The CDM environment enables Corporate tocontrol all aspects of a master database from a central location, and distributeupdates to the store.

To understand CDM, a working knowledge of the Aloha POS database files(.dbf) is helpful. Aloha .dbf files are standalone, flat binary files that containconfiguration and historical data, and provide no relational referential integ-rity. Each .dbf file contains records with fields that have a unique name anddata type. CDM compares each field in two .dbf files of the same name and

produces a change record (.rec file) to record differences that are found.

For example, Itm.dbf contains records for all defined items, with fields for such things as record ID number, short name, and price, as shown in the fol-lowing example:

Item ID Short Name Price02125 Nachos Supreme $2.3909185 Dr Pepper $0.9920100 Ketchup $0.00


10/196

viii Introduction Aloha CDM Users Guide v6.2

The CDM environment employs a master database that is managed from acentral location where a data administrator maintains information and distrib-utes to stores within the organization. The master database should be set up to

include aspects of all concepts using a master menu. Items sold only at selectstores, (store-specific items) are added to the master Itm.dbf file for genericuse. These item records can be activated, named, and priced by the local store.This is accomplished using dedicated numbering ranges, as explained inChapter 2, Data Management.

Some database files have dependencies with other database files. For exam-

ple, records within the promotion file, Pro.dbf, have fields that are dependenton other files, such as Cat.dbf (contains the category to which the promotioncan be applied). It is also dependent on Itm.dbf (contains the item to which the

promotion can be applied), as shown in the following example:

CDM handles all .dbf dependencies through datasets, as discussed in Chapter 3, Distribution Wizard.

CDM provides the ability to send events to selected stores or store groups, andactivate data on a specified effective date. Events are created in the AlohaPOS system to activate certain store specific menu options and features.

Pro.dbf Description Eligible ItemsRecord 007 $0.99 Nachos Cat.dbf record 005

Cat.dbf Description Include in CategoryRecord 005 Food Itm.dbf record 2125

Itm.dbf Short Name PriceRecord 2125 Nachos Supreme $2.39

Note the price for the item Nachos Supreme is still set at$2.39. When the promotion is applied, $0.99 is charged.


11/196

Aloha CDM Users Guide v6.2 Introduction ix

CDM and Aloha Enterprise.com

CDM is a tool offered with the Aloha Enterprise.com product. Aloha Enter- prise.com is a web-based tool for polling, data warehousing, data retrieval,reporting, and back office features, offering complete 'synergy' between theinformation stored at the master database and the corresponding stores. Oncea data update is created with the Distribute Wizard, Aloha Enterprise.comcustomers use the FTP web site to send and receive updates through theWorld Wide Web.

CDM can be purchased as a standalone product, meaning it is not dependenton the Aloha Enterprise.com product. CDM standalone users, however, areresponsible for the data distribution to stores using such methods as PCAny-where or Remoteware .

CDM Benefits to Corporate UsersCentral distribution of data changes Provides a mechanism to add,modify, or delete record and field level information that exists within theAloha .dbf files. The updates are imported to the store's database withoutaffecting store-owned data, such as store-specific printer or terminal settings.Refer to Chapter 1, Getting Started, for more information.

Store Lockout (Slo.cfg) File Provides a mechanism to lock stores out of data files and record level information. When utilized, the Aloha POS systemreads the Store Lockout file to determine the data records the store can access.For example, stores could be allowed access only to an item range of 1000-10000, if desired. Refer to Chapter 1, Getting Started, for more information.

Store Groups Provides the ability to group stores together for eventupdates. Store groups are used in conjunction with corporate events to acti-

vate data at selected stores. Refer to Chapter 1, Getting Started, for moreinformation.

Corporate Events Provides the ability to create centrally-managed storeevents and distribute standard submenus, menus, items, and more, to allstores, but enable only specific menus in specific stores or store groups. This


12/196

x Introduction Aloha CDM Users Guide v6.2

feature provides flexibility in multi-store environments which supportregional menus with varying item prices, and promotions that might be avail-able at some stores. Refer to Chapter 1, Let's Get Started, for more informa-

tion.

Store Specific Items Provides the ability to manage 'store specific items',which vary from store to store either in naming and/or price. The data admin-istrator handles key item attributes for store specific items, such as default

pricing, categories, panel or submenu location, taxes, and more. The store hasthe ability to name and activate the item. This feature greatly simplifies the

process for a store user to set up manager specials, items managed by franchi-sees, or local specific items, but delivers the ultimate tracking control required by most multi-level store organizations. Refer to Chapter 2, Data Manage-ment, for more information.

QuickService Promotion Lookup Button Provides the ability to imple-ment promotions in specific stores with the Aloha QuickService product. ThePromotion Lookup button enables the data administrator to easily activatemultiple promotions that can be accessed using a single button on the FOH.Refer to Chapter 2, Data Management, for more information.

TableService First Button Available Provides the ability to implement promotions, tenders, and comps in specific stores with the Aloha TableSer-vice product without having to define specific button positions. Refer toChapter 2, Data Management, for more information.

Data Updates Provides the ability, through the Distribution wizard, to package data changes made from the central site and distribute them to thestores, using an update file (.rec). Refer to Chapter 3, Distribution Wizard, for more information.


13/196

Aloha CDM Users Guide v6.2 Introduction xi

Whats New?

We added the following enhancements to the Centralized Data ManagementUsers Guide. If you are viewing this manual in PDF format, each referencecontains a hyperlink. Click this hyperlink to move to the page containing theinformation.

Running the DBUP Utility from Distribute.exe

After you upgrade your Aloha system you can now run the DBUP utility fromDistribute.exe. This prevents you from deleting files in the Corpdata direc-tory. Refer to \Corpdata Directory on page 1-13 and Aloha DBUP Utilityon page 1-16 for more information.

Viewing the New Dataset Updates Report

You can view and/or print dataset updates. Select View Reports on the Dis-

tribution wizard Welcome screen to view the finalized update effective date,update name, record file ID number, and a description. If you select IncludePending Updates, you can view pending updates that have not been sent.Refer to View Reports on page 3-43 for more information on viewingdataset updates.

Including the Aloha Path in the Title Bar for Distribute.exe

Corporate locations that use TableService and QuickService create two desk-top icons to run Distribute.exe on their desktop, one for TableService and onefor QuickService. You can now include a command line parameter in theshortcut path to show the Aloha path in the title bar; therefore, you can deter-mine the product for which you are currently creating a dataset update. Refer to Launch Distribution Wizard on page 3-4 for more information on includ-ing the Aloha path in the Distribute.exe title bar.

Viewing Help for the Dataset Files

When you create your dataset updates, you can view the files that the datasetimpacts by clicking Help. An online style help file appears. Refer to Create a

New Update on page 3-9 for more information on the Dataset Online Help.


14/196

xii Introduction Aloha CDM Users Guide v6.2

Updated Dataset Files

Updated the dataset information and the data dependencies in Appendix B.

Added TableService Menus Dataset on page B-8 and the data dependenciesthat are included in a menu update in TableService. Additionally, updated thePromotions Dataset on page B-6 to include all the promotions supported onan update.

Locking Item Prices at the Store Location in Price Changes

Added two new options in Configuring Price Changes on page 2-23 thatenable the corporate location to control the items the store can manually price.The corporate location can lock an item using the Locked check box and notallow the store location to edit the price of the item. The corporate locationcan also select the items to make active at the store using the Active check

box. These two options provide you additional ways to control your pricing atthe store level.


15/196

Aloha CDM Users Guide v6.2 Introduction xiii

How This Guide is Organized

This guide is designed to help you familiarize yourself quickly with AlohaCentralized Data Management . It is organized as follows:

Chapter 1: Getting Started

This chapter discusses the setup requirements and additional directories toenable CDM. Also discussed are creating the Store Lockout (Slo.cfg) file for

record level restrictions and performing store and store group maintenance.

Chapter 2: Data Management

This chapter discusses the recommended setup of a master database to operatein the CDM environment. Also discussed are procedures to create store spe-cific items, and corporate events, and other Aloha POS related functions to

ensure proper data management for stores.

Chapter 3: Distribution Wizard

This chapter discusses the Distribution wizard used to package POS changesinto a data update.

Appendix A: CDM Database Compliancy

Appendix B: Distribute Datasets

Appendix C: Troubleshooting

Glossary

Index


16/196

xiv Introduction Aloha CDM Users Guide v6.2

Conventions Used in This Guide

Numerous graphics and instructions appear throughout this guide. These con-ventions make it easy to find and understand information.

Symbols and Alerts

The following graphic symbols alert you to important points throughout thisguide:

Highlights a special point of interest about the topic underdiscussion.

Alerts you that the operation being described can cause problems if you are not careful.

Directs you to a more complete discussion in another chap-ter of the current guide, or other reference material.

Points to a useful hint that may save you time or trouble.


17/196


18/196

1 2 Getting Started Aloha CDM Users Guide v6.2


19/196

Aloha CDM Users Guide v6.2 Getting Started 1 3

G e t t i n g

S t ar t e d

This chapter discusses how to configure the central site as a centralized loca-tion to operate in a Centralized Data Management (CDM) environment. Alsodiscussed is the process of transporting data changes to the store locations.

The central site must have security key access to CDM and the Aloha POSsystem must be loaded to perform the procedures in this chapter.

You can use Centralized Data Management with either the Aloha POSTableService or QuickService product. This chapter also discusses installationfor Aloha POS versions 5.0 or greater. CDM can operate with Aloha POS ver-sion 4.4. Refer to the notes outside the text margin for information pertainingto the Aloha POS version 4.4.

We discuss the following points in this chapter:

Installation requirements for the central site, as well as the directories,files, the utilities installed at the central and store sites, and the utili-ties installed by the Aloha system and used by CDM.

The life of a data update as it relates to CDM and the difference between central site-owned and store-owned data. We also explainhow to process updates.

Store Lockout (Slo.cfg) file and how it restricts access to certain .dbffiles.

Store maintenance. Store Group maintenance.


20/196


21/196


G e t t i n g

S t ar t e d

You need to meet the following requirements to install CDM on the centralsite system:

Store System RequirementsChanges are updated during the End-of-Day process at the store. The updatesremain unprocessed until the effective date occurs. The store must be able tomake a connection to receive updates.

You need to meet the following requirements to install CDM at the store:

Hardware Requirements: Dedicated workstation Dedicated (preferred) modem Dedicated or dial-up Internet connection Aloha security key authorized for version 4.4, or greater, and CDM 4MB of free disk space

Software Requirements: Windows 95, 98, NT Workstation/Server, or 2000 Internet Explorer connection 4.0 or greater CDM compliant Aloha version Master database containing corporate owned data

Hardware Requirements: Minimum 1 GB hard drive Minimum 32 MB RAM Minimum Pentium 75 Mhz processor Dedicated modem Dedicated or dial-up Internet connection Aloha security key authorized for version 4.4, or greater, and CDM 3 MB of free disk space


22/196


General CDM Requirements To preserve data integrity, download the 'Master' database to all stores

prior to using CDM. Aloha system store software equal to the minimum CDM compliant

Aloha version, otherwise, updates are not processed.

Software Requirements: Windows 95, 98, NT Workstation/Server 2000 Internet Explorer 4.0 or greater CDM compliant Aloha version, equal or less than the corporate site


23/196


G e t t i n g

S t ar t e d

CDM InstallationYou can install Aloha on any disk drive and CDM utilizes either the TableSer-vice or QuickService product. For example, QuickService installed on driveD would read as D:\Alohaqs. In this manual, we refer to the Aloha directoryas %iberdir%. CDM also checks for local hard drive space and Aloha versionnumbers. As noted, when installing at the store, the Aloha version cannot behigher than the version installed at the central site.

Also provided during the installation is Aloha Connect which automaticallyconnects, downloads, and installs new updates to the Aloha system at the cen-tral site. You must select an update method to transfer data. You must alsoselect the 'Download the latest CDM updates now' check box on the Installa-tion Complete dialog box to receive new updates.

To load CDM from the CD-ROM drive:

1. Load the CD into the CD-ROM drive.2. Click CDM CorpSetup.exe, if installing at the central site, or CDMStoreSetup.exe for a store site. The Welcome dialog box shown inFigure 1-2 displays:

Figure 1-2 Welcome Dialog Box


24/196


3. Click Next . A message displays asking you to view the CDMReadMe.txt file. This file contains the latest facts regarding the CDMinstall and feature set. We recommend you click Yes , and read the

document carefully before installing CDM.4. The CDM install detects the Aloha directory located on your system,and displays it in the Choose Destination Location dialog box, asshown in Figure 1-3:

If the destination is not found, or Aloha is installed on multipledrives, click Browse to find the necessary directory, and click OK .

5. Click Next . The confirmation message displays.6. Click Yes . The Start Installation dialog box displays.

Figure 1-3 Choose Destination Location Dialog Box


25/196


G e t t i n g

S t ar t e d

7. Click Next . CDM installs the necessary files and utilities. Upon completion, the Installation Complete dialog box shown in Figure 1-4 displays:

8. Clear the Download the latest CDM updates now check box only ifyou do not want to check for the latest CDM executables, and proceedto Step 10. Updates can be downloaded at a later date through theDistribution wizard. When selected, the Intelligence Update ProcessWelcome screen shown in Figure 1-5 displays:

Figure 1-4 Corporate Installation Complete Dialog Box

Figure 1-5 Intelligence Update Process Welcome Screen


26/196


27/196


G e t t i n g

S t ar t e d

CDM ComponentsAfter installation, the central site and store locations are installed with addi-tional components, files, and directories to enable CDM features.

The following components are installed, which are explained in detail:

Centralsite file (central site or corporate location only) CDM directories CDM utilities Aloha.ini variables

Centralsite File

The Centralsite file is added to the Aloha TableService or QuickService direc-tory at the central site. The Centralsite file has no extension, and enables

access to additional CDM features within the Aloha system. Store sites mustnot have the Centralsite file. If deleted or renamed, the additional features arenot available.


28/196


The existence of the file enables access to the Enterprise menu option, asshown in Figure 1-6:

Figure 1-6 Enterprise Menu Option

For Aloha versions below 5.0, select MX/Enterprise from theMaintenance program.


29/196


G e t t i n g

S t ar t e d

CDM Directories

Additional directories are created within the \Aloha or \AlohaQS directories,

as shown in Figure 1-7:

These are explained in the order of process:

\Corpdata Directory

The \Corpdata directory resides at both the central site and store. For the cen-

tral site, this directory contains the working .dbf files from the last menu build. For the store site, this directory contains record update files that are dis-tributed from the central site. When upgrading the Aloha version at the centralsite, it is necessary to upgrade the database files in the Corpdata directory.

When a user upgrades their Aloha POS version at the store, Distribute.exedetects the upgrade and requires the user to upgrade the Corpdata folder to

Figure 1-7 Directory Structure for CDM


30/196


accommodate the database changes that have occurred at the store. Distrib-ute.exe compares the Cltsvr version to the software version logged in the Ver-sion.ini file. CDM creates the Version.ini file during the install and logs the

version of Cltsvr at the time of the CDM installation.Version.ini File

The version.ini file contains the Aloha version number and the DBUP genera-tion number.

\Update Directory

The \Update directory resides at the central site and contains finalized records(.rec files). Records located in this directory are marked for distribution.

\TMP Directory

The \TMP directory is an existing directory located at both the central site andstore. For the central site, it is used to find pending record updates for reviewuntil they are finalized. For the store site, it is used to find store records thathave failed during processing. The Debout.ftp file, which reports processingerror messages, is also found in the \TMP directory.

\FTP Directory

The \FTP directory resides at the central site and contain utilities required totransport information to and from the Aloha FTP server. For existing AlohaEnterprise.com customers, the \FTP directory already exists.

\Store Directories

When stores are defined at the central site, a Strxxxxx directory, where xxxxx

is the store ID number, is created for each store. Each directory holds specificinformation pertaining to the respective store.


31/196


G e t t i n g

S t ar t e d

CDM Utilities

Updates created and distributed from the central site rely on the following

installed utilities located in the \Bin directory:

Distribute.exe

Resides only at the central site and provides a graphic interface wizard tomanage data updates. The wizard enables the data administrator to build menuchanges and assign an effective date for data updates. Updates are sent to the

store when finalized in the Distribution wizard, however, changes are onlyimplemented at the store when the effective date occurs.

Dbfdiff.exe

Resides at the central site and compares differences of .dbf files of the sametype between \Newdata and \Corpdata. When the utility is invoked by the Dis-

tribution wizard, a single text file is created, containing only the differences between recently modified .DBF files in production, for an entire dataset.

Procrecs.exe

Resides at both the central site and store. The utility initially runs at the cen-tral site to verify processing errors. When the store's End-of-Day occurs, Pro-

crecs.exe is launched and finds .rec files in the store's Corpdata directory. Thefiles are processed when the effective date occurs.

Procrecs.exe accelerates the processing of updates and event files as appropri-ate. Each update is processed by the effective date and sequence number order and sent to the DBUP utility for application to the database, if the effectivedate is less than or equal to the current date of business (DOB). All updateswith an effective date greater than the current DOB, are checked for possibleacceleration. An update is accelerated if it contains the same type of change asan update with a higher sequence number.

Procrecs.exe also accelerates event files (EVE###.rec) that have sequencenumbers identical to accelerated updates. Acceleration of event files is caused

by the presence of other event files based on the effective date and sequence


32/196


number. Event files are processed as a separate series (EVE). Any existing,greater sequenced event file with a later effective date is unaffected until theeffective date. Procrecs.txt logs any accelerated update.

Aloha.ini Variables

The following variables are added to the Aloha.ini file:

CDMACTIVE=TRUE Enables CDM when set to true.

EODCTLWATTIME=# Determines the number of minutes to wait after Procrecs.exe completes during the End-of-Day and the BOH starts.

EODFOHWAITTIME=# Determines the number of minutes for the sys-tem to wait after Procrecs.exe completes during the End-of-Day and the FOHstarts.

Aloha DBUP Utility

The Aloha system installs the DBUPx utility in the %Iberdir%/Bin directory.The DBUPx utility, where x is the version number of the utility, upgrades arelational database (RDB) if one is present on the system. The utility upgradesthe master database to the highest version and makes it compatible to all cor-responding stores. To avoid relational integrity errors, updates are sorted in

proper population order prior to passing the file to DBUP.


33/196


G e t t i n g

S t ar t e d

Each time you launch the Distribution wizard at the central site it checks for anew version of the Aloha software. If a new version of Aloha is installed, theDistribution wizard prompts you to update your \Newdata and \Data files.

Running the DBUP utility from the Distribution wizard does not delete thecorporate files that CDM maintains in the \Corpdata directory.

The only time you upgrade your database is when you upgrade the Aloha sys-tem.

If you run DBUP from within the Aloha system to upgradeyour database, DBUP deletes the following files:Dataset.dbf, Datastdl.dbf, Datastue.dbf, Sysdata.dbf,Sysdd.dbf, and Sysdepn.dbf.


34/196


Data UpdatesAn important aspect of CDM is that all data updates are controlled by the dataadministrator at the central site, using standard Aloha POS functions. Updatesare then distributed to stores in a designed process.

Life of a Data Update

A flowchart of the life of a data update is shown in Figure 1-8 :

1. From the central site, make data changes in the Aloha POS system.

2. Run Verify and test the changes in the Aloha POS system.3. Run Distribution wizard to build the data update.

The Dbfdiff.exe utility compares the \Newdata directory against the\Corpdata directory. Data changes are output to an update file for dis-tribution.

Once finalized, the records are pushed to the Enterprise server. Theinformation is pushed to the store sites. When the End-of-Day occursat the store site, Procrecs.exe processes the record edits to the \New-data directory at the store, per the effective date. The store site's datafiles are updated at POS startup.

Figure 1-8 Life of a Data Update


35/196


G e t t i n g

S t ar t e d

Data Ownership

Data ownership of .dbf files should be determined beforehand for proper dis-

tribution processing. It is important to decide the data that is owned at the cen-tral location and the data owned at the store level. The data administrator must

become a data operations expert to be able to manage data changes andupdates within the CDM environment.

Central site-owned Data Dedicated .dbf files designed to be managed atthe central location. The data administrator creates, makes changes, and sends

updates to override store-owned data.Store-owned Data Dedicated .dbf files designed to be managed at thestore. The Distribute.exe utility does not build differences from store-owneddata. The central site can permit adding and editing privileges so store manag-ers can modify only certain data records. This control is managed using theSlo.cfg file discussed later in this chapter.

Record Update Files

The record update (.Rec) files are text files containing the result of the datadifferences generated by the Dbfdiff.exe utility. The text file can be openedwith MSNotepad , or other text editors of your choice, and saved to a text file.


36/196


37/196

Data Transfer Flow and Store Processing


38/196


Data Transfer Flow and Store Processing

The following section describes the finalized data transfer from the central

site and how updates are processed at the store level. The central site must beable to dial out, establish a connection with each store and transfer data intothe specified files, as outlined in this manual. All menu data updates areentered in the Aloha system at the central site. For Enterprise users, the update

process is automated. For CDM Standalone users, they are responsible to pro-vide their own connection method to transfer updates to stores, and move filesto the correct directories.

Finalized Updates

A CDM record update is a read only text file containing results of the changedinformation from the Aloha system, significantly reducing the size of data

being transferred. An update is created using the Distribution wizard andshould be finalized after it has been thoroughly reviewed and tested, and isready to be implemented at the store. Enterprise automates the file exchange

by transferring data from the \Update directory to the proper directory at thestore. Once the transfer process is complete, the record update is deleted fromthe \Update directory.

Central Site- Record Transfer

To maintain data integrity, all stores receive finalized record updates. Thereare special corporate and store event updates that are distributed to specificstores to activate local features. The following are the different types of final-ized updates to be transferred:

Standard Record Update

All stores receive standard record updates to maintain data integrity.

Naming convention Dataset short name, sequence number, .rec fileextension, such as ITM00001.rec.

Record updates are transferred to the stores on a daily basis (or as pre-defined by the user).

Standard record updates are generated from the Dataset selection in


39/196


G e t t i n g

S t ar t e d

Standard record updates are generated from the Dataset selection inthe Distribution wizard, excluding event updates, which are handleddifferently.

Standard record updates are transferred from the \Update directory tothe stores \CorpData directory. If the record file was not placed in thecorrect directory, it will not be processed.

Store-specific Event and Slo.cfg Updates

Distributed to specific stores only. The event or Slo.cfg update is placed in a series of directories, which

identify the store number to receive the download. Slo.cfg and Events-s.cfg files are transferred to the \Newdata direc-

tory at the store. Eve#####.rec and Events-c.cfg files are transferred to the store's

\CorpData directory. Store-specific updates are not archived like standard .rec files in the

Iberarch.zip.

IberArch.zip Archive Winzip File

Archive of all standard record updates. If a record update must be re-sent, the file can be extracted from Iber-

Arch.zip and transferred to the store.

Archive.zip should not be included in the data transfer. Event and Slo.cfg updates are not archived, and can be recreated by

updating the event file for the store in the Distribution wizard (Sendstore file feature).

The updates remain unprocessed at the store until the End-of-Day occurs onthe effective date. The data can be transferred as the updates are completed,

allowing additional distribution time in case there are connection problems.

Event Records


40/196


Event Records

Event record updates are Store-specific because they activate and deactivate

certain features at the local store level. Event updates are transferred only tothe directory for the corresponding store number. Store ID numbers andnames can be found under Maintenance/Enterprise/Stores.

The following are the different event record formats:

Corporate Events

Corporate events are usually created with a menu update. The seriesnumber for this event is related to the menu dataset series, if theupdate was created at the same time. Only corporate events can beassigned an effective date.

Finalized corporate event path - %iberdir%\Update\#####\Corp-data\EVEnnnnn.rec, where ##### is the store number and nnnnn isthe sequence number.

EVEnnnnn.rec files are transferred to the \CorpData directory at thestore.

Special Corporate Event Updates for a Single Store

Special corporate event updates are used in instances when a store isdeleted from a store group or event group and the corporate event for

this store needs to be updated. The user can rebuild the corporateevent or store event for a specific store. When corporate events are

built in this format, an effective date cannot be assigned. Finalized corporate event update for store path - %ibe-

dir%\Update\#####\Newdata\Events-c.cfg, where ##### is the storenumber.

Events-s.cfg file updates are transferred to the \NewData directory at

the store.

Store Specific Events Events-s.cfg


41/196


G e t t i n g

S t ar t e d

p g

Store-specific events are events that are distributed to a specific storeonly, rather than a store group, and are implemented immediatelyafter EOD (no date scheduling).

Finalized store event path - %iberdir%\Update\#####\New-data\Events-s.cfg, where ##### is the store number.

Events-s.cfg files are transferred to the \Newdata directory at thestore.

Slo.cfg Updates

Slo.cfg updates can be distributed to a specific store or group of stores(lockout may vary by concept or store).

Finalized Slo.cfg path - %iberdir%\Update\#####\Newdata\slo.cfg,where ##### is the store number.

Slo.cfg updates are transferred to the \Newdata directory at the store.

An example of the data transfer flow in the \Update directory is shown in Fig-


42/196


ure 1-10:

Standalone users must manually move the update records to the proper store directories.

Store System Processing a Record Update

Record updates are processed at End of Day on the effective date. When theeffective date occurs, the record is copied from \Corpdata to the TMP\CDMfolder for validation and processing. Once validated, copies of the databasefiles needed to process the update are extracted from \Newdata. The changesare processed and upon successful completion, the modified database files arecopied back into \Newdata. Upon refresh at EOD, the files are updated andthe information becomes effective on the FOH. The changes are processed ina temporary directory to prevent partial or faulty updates from being imple-mented directly into the system.

When record updates are successfully implemented, a copy of each update is placed in \CorpData\Success directory and a message is written to \TMP\CDM text noting the success.

Figure 1-10 Data Transfer Flow

If a record update fails during processing, the file is renamed with the specific


43/196


G e t t i n g

S t ar t e d

error code and copied into the \CorpData\Failed directory. An error messageis logged in Procrecs.txt and CDM.txt, located in %iberdir%\tmp. Any further

processing of updates are suspended until the failed record update is resolved.The replacement .rec file should be copied back into the \CorpData directory,and the next EOD attempts to successfully process the update. If the replace-ment update is successful, the system deletes the failed record update andresumes normal processing for any files in the queue.

Files should not be manually deleted from the failed directory.

Possible Processing Failures

Record updates can fail, and are not limited to the following situations:

The file cannot be validated Occurs when there is a missing or invalidaction request, the record ID is missing, or the record update has beenrenamed incorrectly. These errors usually occur when the user is trying tomanually alter a record file, rather than make the proper change through theDistribution wizard. Processing fails until the unchanged record update is

placed into \CorpData.

The file could not be opened Occurs when a record update is corruptedduring the transfer process. This is not a common scenario, but a system mal-function from the transmitter or recipient could cause the problem.

Non-critical Warnings

The following warnings do not cause records to fail during processing, butconstitute a warning message:

An unrecognized file exists in the \CorpData directory If a file other than the stipulated format is downloaded (Excel spreadsheet, Word document)than the system will ignore the file, but writes out a warning message that anunrecognized file exists.

Add detected for record that already exist In some cases, the store data-b b f f h d b If h d h


44/196


bases may be out of sync from the master database. If the system detects thatthe record update would like to add a file that already exists at the store, it willchange the action request to Edit and overwrite the store file with the newinformation. A warning message will be written out to alert the user that thefile was already in existence so they can make sure all databases are in sync.

Missing .dbf file In some cases, the CDM workstation may be on a higher version of Aloha than the existing stores in the field. With different versions,new database files or enhancements may be introduced. The system willignore and write out a warning message if a database change is required to a

database file that does not exist at the store. For example 5.0 users can makeupdates to Security levels (Seclvl.dbf), while 4.4 users cannot, because theSeclvl.dbf file does not exist in 4.4. Bohsec.dbf is used in 4.4. The system willwrite out a message stating the database file does not exist at the store andcannot be updated.

Store Lockout File (Slo.cfg)


45/196


G e t t i n g

S t ar t e d

( g)The Store Lockout file (Slo.cfg) can be used to prevent stores from accessingentire records, or a defined range of records within an Aloha .dbf file. TheSlo.cfg file is created by the data administrator, using the text editor of their choice, and is distributed to the \Newdata directory of the store.

When properly configured, the store cannot edit a record that exists in theSlo.cfg file, hence the name "Store Lockout". It is important to understandthat entries made in the Slo.cfg file are database records that the store cannot

edit. If an entry is not made pertaining to a .dbf file, the .dbf file is notaffected. Stores can still be locked out by using security levels in Mainte-nance/Labor/BackOffice Security Levels. It is recommended that the dataadministrator determine beforehand the database elements that should be cen-tral site-owned, and which should be store-owned.

If entries for a specific .dbf file do not exist in Slo.cfg, the store isallowed editing rights to the file, based on the security leveldefined within the Aloha POS system.

Any .dbf file can be included in the Store Lockout file, with the exception of Btn.dbf, Pnl.dbf, and Scr.dbf found in the Aloha QuickService product. These

files are NOT supported in the CDM environment. To restrict access to PanelEditor, the data administrator must use Back Office Security Levels. TheSlo.cfg file also does NOT support files with a .cfg or .ini extension.

Create Store Lockout File


46/196


To protect the integrity of the Slo.cfg file, the file is distributed to the store.

The Slo.cfg file is read when the Back-of-House (BOH) is launched. TheSlo.cfg file updates can be sent through the Distribute wizard.

To create a Store Lockout file using MSNotepad:

1. Locate the Aloha\Newdata or AlohaQS\Newdata directory in Win-dows Explorer.

2. Right-click in a blank space inside MSWindows Explorer and selectNew/Text Document . A new text document is created.

3. Type Slo.cfg and press Enter.

Store Lockout File Format

The Store Lockout file format is very specific. Each line entry must includethe .dbf file name, followed by a comma, and the lockout ID number. The for-mat is not case sensitive and leading zeros are not necessary.

All line entries must be followed by Enter, or a carriage return,including the last entry.

The following options are available for the Store Lockout format:

Lock Stores out of a Single Record Entry

To lock a store out of a single record, such as the promotion record number 002, the text entry would be as follows:

PRO,2

GSLock Stores out of a Range of Records Entry


47/196


G e t t i n g

S t ar t e d

To lock a store out of a range of records in a single entry, such as for all

restricted central site-owned items 2000-20000, the text entry would be as fol-lows:

ITM,2000-20000

Lock Stores out of a Record and a Range ofRecords Entry

To lock a store out of a single record number and a range of numbers in thesame Slo.cfg file, such as for items 1-50, and item 900, the text entry would

be as follows:

ITM,1-50ITM,900

Lock Stores out of an Entire File

To lock a store out of an entire file, such as all tenders, the text entry would beas follows:

TDR,0

Test the Store Lockout FileThe restrictions set in the Store Lockout (Slo.cfg) file should be tested prior toimplementation. Multiple Slo.cfg files could exist at the central location for different stores. For handling ease, store the Slo.cfg file in a different direc-tory when testing at the central site. The file must be named Slo.cfg when it isdistributed to stores.

If a change is made to Slo cfg while logged in to the BOH you


48/196


If a change is made to Slo.cfg while logged in to the BOH, youmust log out before you can test the file.

To test the Slo.cfg file:

1. Log in to the BOH .2. Select the menu option indicated in the Store Lockout file.3. Click add , edit , or delete from the menu option.

IF the error messages shown in Figure 1-11 and Figure 1-12 display, the test-ing of Slo.cfg is a success. The messages are seen by the store manager whenthey are locked out of a function they are attempting to perform.

Click OK to clear the error message.

Figure 1-11 Add Record Error Message

Figure 1-12 Edit Record Error Message

GSDefine Stores


49/196


G e t t i n g

S t ar t e d

Add stores to the CDM database to activate and distribute store specific fea-

tures, such as events. Each location is assigned a unique store ID number within the database. The store ID in the CDM database must match the storenumber in the Aloha.ini file located in the field. Define stores using the Enter-

prise drop-down menu. When you add a new store, the system creates a storedirectory within the \Aloha directory in the following format:

Strxxxxx - where xxxxx is the store ID number.

To define a store site:

1. Select Maintenance/Enterprise/Stores. The Store Maintenancefunction tab displays, as shown in Figure 1-13:

Figure 1-13 Store Maintenance Function Tab

For Aloha versions 4.4, select MX/Enterprise/Stores from theMaintenance program.

2. Enter an unused number in the Store ID drop-down box, such as2610, representing the store's unit number.


50/196


3. Enter a store description for the store in the Name text box.4. Click Save .5. Repeat steps 2 through 4 until all necessary stores are defined.

6. Exit the Store Maintenance function.

A

Aloha Enterprise users with existing store IDs cannot import IDsinto the CDM environment. Those stores must be re-created forCDM.

G S Define Store Groups


51/196


e t t i n g

t ar t e d

Once you define your stores, you can use store groups to group stores based

on the information they receive from CDM. For example, you have 200stores, and 20 of them need to receive the same item changes. Rather thansend the update twenty different times, once to each store, create a store groupthat contains these stores. Then send the update, using an event, to the storegroup.

A store can belong to multiple store groups. For example, a store can belong

to a store group where the units have similar menus, and also to a store groupwhere the units require the same pricing updates, etc.

To add a store to a store group:

1. Select Maintenance/Enterprise/Store Groups . The Store GroupMaintenance function tab displays, as shown in Figure 1-14:

Figure 1-14 Store Groups Maintenance Function Tab

F

For Aloha versions 4.4, select MX/Enterprise/Store Groups fromthe Maintenance program.

2. Enter an unused number , up to five-digits, in the Store Group drop-down box.

3 E h d i i f h i h D i i b F


52/196


3. Enter the description for the group in the Description text box. Forexample, Texas to represent all stores located in Texas.

4. To Add a store to the group, select the store (s) from the right list boxand click .5. Click Save .6. Repeat steps 2 through 5 until you define all necessary store groups.7. Exit the Store Group Maintenance function.

When you delete a store from a store group that has been addedas a subscriber, you must update the corporate event file throughthe Distribution wizard.

Ge

S t

Summary


53/196


e t t i n g

t ar t e d

This chapter covered the installation requirements and configurations required

to ensure the proper setup of Centralized Data Management (CDM). It alsoexplained the utilities involved with CDM and the setup of the store lockoutfile, stores, and store groups. The chapter covered the following points:

The installation requirements for the central site and the directorieswithin the structure.

The life of a data update.

The data transfer flow and store processing of data updates. How to configure and test the Store Lockout (Slo.cfg) file. How to configure stores. How to configure store groups.

In the next chapter you learn how to perform data maintenance with CDM for both the Aloha TableService and QuickService products.


54/196


Data Management


55/196

Chapter 2

This chapter discusses the procedures involved in sending certain data

updates to be distributed, as well as configuring the Slo.cfg file for restricted access. Also discussed are recommended databaseattributes for easy database management.

Master Database Compliancy...........................................................2-4Dedicated Number Ranges ...........................................................2-4ID Marker Files .............................................................................. 2-7Separators .....................................................................................2-8Table of Contents ..........................................................................2-8

Item Maintenance ............................................................................. 2-9Store Lockout of Items ................................................................... 2-9Store Specific Items..................................................................... 2-10

Price Maintenance ..........................................................................2-23Configuring Price Changes.......................................................... 2-23

Promotion Maintenance.................................................................. 2-32Store Lockout of Promotions ....................................................... 2-32Promotions................................................................................... 2-33

Tax Maintenance ............................................................................ 2-42Event Maintenance .........................................................................2-46

Configure Corporate Events ........................................................ 2-48Summary ........................................................................................2-53
http://chapter.pdf/http://chapter.pdf/


56/196

2 2 Data Management Aloha CDM Users Guide v6.2

To benefit from the Centralized Data Management (CDM) feature, the AlohaPOS database must be properly set up and maintained. Each store database,regardless of concept or menu, contains the master data information. In most


57/196

Aloha CDM Users Guide v6.2 Data Management 2 3

D

a t a

M an a g em en t

g pscenarios the data administrator manages data from a dedicated workstation ata central office and the workstation is not used to actually ring sales. POSchanges are then pushed down to all stores. An example of a company struc-ture hierarchy is shown in Figure 2-1:

This chapter explains how to:

Configure the master database to easily manage data changes andupdates.

Configure store and group events. Perform item, modifier, price, promotion, and tax maintenance.

Figure 2-1 Company Structure Hierarchy

Master Database CompliancyCDM i d i d d i f i f i ll d l i


58/196


CDM is designed to update certain sets of information called central site-

owned data. A master database must be created and contain the same IDs atevery location in order to extract proper data and manage a single database. Itis important to determine the similarities and create a master database with acompilation of all IDs from the store sites. To make an existing databaseCDM compliant, refer to Appendix A CDM Database Compliancy. Menu dif-ference at the store is handled through events.

Dedicated number ranges should be put in to place to help guide the user through large records, such as the item information, and to convey to storeswhere new IDs can be created. Records that can be edited by the store should

be given a separate number range within the master database. By centralizingthe master database, file, field, and record level updates can be distributed tostores, rather than distributing full .dbf files. Currently there are 57 Aloha .dbf files, and the information found at each store should be found in the master.

For an existing user, converting a database to be compliantshould take place immediately and might result in extensivechanges to some records, such as reassigning ID numbers forconflicting information and data.

There are several recommendations provided in this section for creating amaster Aloha POS database. Some, or all of these recommendations, could beemployed to simplify data management and prepare for future expansion.

Dedicated Number Ranges

Dedicated number ranges help identify files with a large number of records.The following are two common methods of assigning ranges:

Ranges by Concept Ranges by Menu

Ranges by Concept

Many master databases contain multiple concepts within the same database.


59/196


D

a t a

M an a g em en t

Each concept could sell different items, offer different promotions, employdifferent operating procedures, and more. This method usually does not shareID records across store sites, and each concept would be assigned a dedicatednumber range. The range should be assigned per concept, as shown in the fol-lowing example:

Within the range of each concept, a dedicated subset range should be estab-lished for central site items. Menu breakdowns include such things as entrees,desserts, drinks, and more, as shown in the following example:

If locations are allowed store-owned items, a dedicated local store rangeshould be established for each concept, as shown in the following example:

Concept Item ID RangeConcept A 10,000 - 19,999Concept B 20,000 - 29, 999

Concept Breakdown Item ID Range

Concept AEntrees 10,001 - 11,999Drinks 12,000 - 13,999

Concept B 20,000 - 29, 999Entrees 20,001 - 21,999Drinks 22,000 - 23,999

Concept Breakdown Item ID RangeConcept A

Entrees 10,001 - 11,999

Drinks 12,000 - 13,999Local Items 14,000 - 15,999

Concept B 20,000 - 29, 999Entrees 20,001 - 21,999Drinks 22,000 - 23,999Local Items 24,000 - 25,999

With this method, other records could be assigned ranges by concept to coin-cide with items, as shown in the following example for submenus and menus:

C I S b M


60/196


Ranges by a Menu

Many master databases assign ranges by menu. In this scenario, IDs are usu-ally shared. The central site pulls sales information using the same item num-

bers from all their stores. For example, if Chicken Fried Steak is item number 5010, every store that sells Chicken Fried Steak, rings sales under the sameitem number, 5010. Through this method, the central site receives consoli-dated reporting on all Chicken Fried Steaks sold across all stores.

This method limits item duplication and, therefore, must have a wider rangefor records. The similar items of all stores are assigned first, as shown in the

following example:

Concept Items Submenus Menus

Concept A 10,000 - 19,999 100 - 199 10,000 - 19,999Concept B 20,000 - 29,999 200 - 299 20,000 - 29,999

Item Ranges Item IDAppetizers 20,000 - 39,999Soup and Salad 40,000 - 59,999Entrees 60,000 - 79,999

If locations are allowed store-owned items, a dedicated subset range should beassigned for each core range, as shown in the following example:

L l It R ID


61/196


D

a t a

M an a g em en t

With this method, other records could be assigned ranges by core to coincidewith items, as shown in the following example for modifiers, submenus, andmenus:

ID Marker Files

ID markers help sort files with a large number of records, such as items.Markers help separate the database ID ranges for organization, as shown inthe following two examples:

Local Item Ranges IDAppetizers

Core 20,000 - 34,999Local 35,000 - 39,999

Soup and SaladsCore 40,000 - 54,999Local 55,000 - 59,999

EntreesCore 60,000 - 74,999Local 75,000 - 79,999

Core/Local Items Submenus MenusCore 1,000 - 49,999 100 - 499 10,000 - 49,999Local 50,000 - 79,999 500 - 799 50,000 - 79,999

Beef NachosBean Nachos

**BEVERAGES**Dr. Pepper Sprite

Markers are created as blank items used to define ranges. They never printand they are not used to ring sales. They are commonly created in differenttype faces, such as capital letters, or a preceding indicator.


62/196


SeparatorsSeparators enhance marker IDs by making them stand out, if the file is sorted

by numeric preference, as shown in the following example:

Separators are created as blank items used to identify the marker. They never print and are not used to ring sales. They are commonly created as a longstring of characters, such as asterisks (*), to separate them from categories of items.

Table of Contents

A table of contents is also a common technique used in files with a large number of records. They provide a guide for the user, when sorting records bynumeric preference. The following is an example of a table of contents for theitem file:

Table of content entries are created as blank items to reference a number range. They never print and are not used to ring sales. They should be placed before any assigned number range.

ID Item Record Entry00499 ****************00500 00501 ****************

ID Table of Contents Entry00001 Appetizers 2000 - 299900002 Soup and Salads 3000 - 399900003 Entrees 4000 - 4999


63/196

Store Specific Items

Store specific items are distributed as inactive to all stores with the intentionto allow the store to modify and activate the item locally These items can be


64/196


to allow the store to modify and activate the item locally. These items can belocally activated or controlled by a corporate event. This feature delivers theultimate tracking control required by most multi-store concepts.

A local item range can be added with predefined field settings, such as printer,category, and tax assignments. Local items can be pre-assigned to a TableSer-vice submenu, or QuickService panel on which the item resides. The storewould rename the item to activate it.

If stores are given access to store specific item records, theseitem IDs should never be placed in the Slo.cfg file.

Store specific items are marked inactive by the tilde (~) symbol entered as thefirst character in the 'Short Name' text box and are preassigned to a submenuor panel. Once the store receives the new item, they must rename the item byremoving the tilde (~) to activate the item. If the item was preassigned to asubmenu, menus, and/or modifier groups, it displays on the FOH. Thisenables the central site to lock stores out of submenus and panels, if neces-sary.

This section is divided in to several separate procedures related to store spe-cific items. Please refer to the procedure pertaining to the Aloha productinstalled at your location and the corresponding manual to fully complete theimplementation of an item. This section discusses the following procedures:

Create Store Specific Item Add Store Specific Item to a Submenu

Add Store Specific Item to a Panel Add Store Specific Smart Item Set Activate Store Specific Item Event Set Activate Panel Button Event

Create a Store Specific Item

Store specific items must have the tilde (~) placed as the first character in theitem's short name. The example provided in this procedure is for the item,


65/196


D a t a

M an a g em en t

item s short name. The example provided in this procedure is for the item,Manager Special, which store managers can manually activate at their store.In most situations, there could be multiple items for manager specials. Usethis procedure as an example for both the TableService and QuickService

products.

To create a store specific item:

1. Select Maintenance/Menu/Items . The Items function tab shown inFigure 2-2 displays:

2. Enter an unused ID number in the Number drop-down box and press Enter .

Figure 2-2 Items Function Tab

For Aloha versions below 5.0, select M enu/Items from the Mainte-nance program.

3. Enter the name of the item in the Short Name text box with the tilde(~) symbol as the first character.

4. Complete the item record, such as chit name , long name , category ,tax , printer routing , price , etc.


66/196


5. Click Save .6. Repeat steps 2 through 5 until all necessary items are entered, being

careful to place the tilde (~) symbol in the first character.7. Exit the Items function.

To activate the store specific item, stores should be instructed to

remove the tilde (~) symbol.

Add Store Specific Item to a Submenu

The manager special (inactive item) should be attached to a submenu so that itis available once the manager activates the item. If the central site sends an

item that is not assigned to a submenu, the item does not display on the FOHterminals. Use this procedure as an example for the TableService product.

To assign a store specific item to a submenu for TableService:

1. Select Maintenance/Menu/Submenus . The Submenus function tab(Figure 2-4) displays.

2. Create an unused ID number or select an existing number from theSubmenu ID drop-down list and press Enter .

For Aloha versions below 5.0, select Menu/Submenus from theMaintenance program.

3. Double-click an unused box on the right to add an item. The Sub-menu dialog box shown in Figure 2-3 displays:
http://-/?-http://-/?-


67/196


D a t a

M an a g em en t

4. Select Manager Special from the Item drop-down list.5. Select Use Item Price from the Pricing Options inset and click OK .

For CDM, the Use Item Price pricing method references the priceset at the item level and should be selected to manage multi-store

pricing.

Figure 2-3 Submenu Item Dialog Box


68/196

To assign a store specific item to a panel:

1. Select Maintenance/Menu/Panel Editor . The Panel Editor work-space and toolbar shown in Figure 2-5 displays:


69/196


D a t a

M an a g em en t

2. Select CMDS/Open Existing Panel/Button Functions . The Paneldialog box shown in Figure 2-6 displays:

Figure 2-5 Panel Editor Workspace and Toolbar

For Aloha versions below 5.0, select Menu/Panel Editor from theMaintenance program.

Figure 2-6 Panel Dialog Box

3. Select the panel and click OK . The selected panel displays.4. Double-click an unassigned button or create a new button . The Edit

Button dialog box displays, as shown in Figure 2-7 :


70/196


5. Select Order Item from the Function drop-down list.6. Select the store specific item from the Item list box. The button text

changes from Order Item to the description of the item.7. Enter the tilde (~) symbol as the first character in the Text text box.

Figure 2-7 Edit Button Dialog Box

8. Complete the order item button within the Edit Button dialog box,such as text placement , color selection , etc., and click OK . Thenewly assigned button displays on the panel, as shown in Figure 2-8:


71/196


D a t a

M an a g em en t

9. Click Exit from the Panel Editor toolbar. The save confirmation dia-log box displays.

10. Click OK to save and close the panel. The Panel Editor functioncloses.

To activate the store specific item, the store site must remove thetilde (~) symbol at the item level only. It is not necessary toremove the tilde from the 'Button Text'.

Create Smart Item Button

The items placed in Smart Item groups are configured the same as other storespecific items, as explained in the Create Store Specific Item section. A tildeis not required on the button text when using smart items.

The smart item displays on the FOH if one or more items in the functiongroup are active. If all items in a smart item group are inactive, the button

Figure 2-8 Panel with Store Specific Item

MGR Specbutton

does not show on the FOH. For example, a smart group, shown in Figure 2-9 ,can be configured for a soft drink to be sold as small, medium, large, and x-large sizes, but one region does not offer large. The tilde would be placed onthe extra large item in Maintenance/Menu/Items. The smart item button

ld till di l th FOH b t th l d i k ill t b il bl If


72/196


would still display on the FOH, but the x-large drink will not be available. If all items in the group contain the tilde symbol, then the smart item button doesnot display on the FOH.

Set Activate Store Specific Item Event

Store specific items can be activated from the central site via a scheduledevent. When the event is set, the new item event name replaces the item shortname, in memory, while the item may appear inactive at the item level. Usethis procedure as an example for both the TableService and QuickService

product

Figure 2-9 Smart Item Configuration

Refer to theEvent Mainte-nance section and theAloha TableService orQuickService UsersGuides for further infor-mation on Events.

To set an Activate Store Specific Item event:

1. Select Maintenance/System/Events . The Select Event Type dialog box displays.


73/196


D a t a

M an a g em en t

2. Select either Event Group or Store. A selection list box displays.3. Select a store or an event group from the list box and click OK . The

Events function tab displays.4. Click Add . The Event Time & Type dialog box shown in Figure 2-10

displays:

5. Select Activate Store Specific Item from the Event Type drop-downlist.

6. Enter the hourly time for activation in the Time text box using a 36-hour clock.

7. Select either Daily , Weekly , Monthly , or Special for the time intervalof the event.

For Aloha versions below 5.0, select System/Events from the Main-tenance program.

Figure 2-10 Event Time & Type Dialog Box


74/196

3. Select a store or an event group from the list box and click OK . TheEvents function tab displays.

4. Click Add . The Event Time & Type dialog box shown in Figure 2-12 displays:
http://-/?-http://-/?-


75/196


D a t a

M an a g em en t

5. Select Activate Panel Button from the Event Type drop-down list.6. Enter the hourly time for activation in the Time text box. Enter the

time in hours and minutes using a 36-hour clock.7. Select either Daily , Weekly , Monthly , or Special for the time interval

of the event.8. Click OK . The Activate Panel Button dialog box displays, as shown

in Figure 2-13 :

Figure 2-12 Event Time & Type Dialog Box

Figure 2-13 Activate Panel Button Dialog Box

9. Select the panel.10. Select the button .11. Clear Set Button as Inactive .12. Click OK . The Events function tab displays with the event's proper-

ties.13 Cli k D


76/196


13. Click Done .

Price MaintenanceThe Aloha system provides flexibility in establishing a price for an item. Thefollowing list starts with the highest level of pricing and descends to the low-est pricing method. For example, Button pricing overrides Price Change pric-


77/196


D a t a

M an a g em en t

est pricing method. For example, Button pricing overrides Price Change pricing, Price Level pricing and Item Level pricing. The pricing methods are:

Quantity Item pricing Fixed Item Pricing (TableService only) Button pricing

Price Changes pricing Price Level pricing Item Level pricing

Refer to your Aloha TableService Users Guide or Aloha QuickService UsersGuide for more information on the pricing hierarchy in the Aloha system.

When using CDM, use the Price Changes method to set prices for items atyour stores and activate the changes at the store level through events. PriceChanges enables you to update prices at the item level, using price levels, or using promotions.

Configuring Price Changes

Price Changes supports the following methods of pricing:

Item Level pricing Price Level pricing Promotion

Item Level pricing is the lowest form of pricing in the pricing hierarchy, and

the one you should use for CDM; however, if you are currently using PriceLevel pricing for certain items, you can continue to use it in CDM. The PriceChanges method overrides all prices assigned at the item level or using PriceLevels.

To implement a Price Change at the store, create an event that activates the price change in the FOH. Refer to Configuring an Event for more informationon configuring your events. When performing price maintenance throughPrice Changes, consider the following:

When sending an item price change price your items at the item
http://-/?-http://-/?-


78/196


When sending an item price change, price your items at the itemlevel, as defined in Maintenance/Menu/Items. When using TableSer-vice, price the item at the item level instead of the submenu level.

All priced modifier item pricing must be placed at the item levelinstead of the modifier level, if you are controlling modifier pricing atcorporate.

Set an event to activate the price change.

When these considerations are addressed, the central site is able to maintain pricing at your stores.

Configuring an Item Price Change at the Corporate Location

Generally, you use Price Changes to control pricing at the stores at the itemlevel. When two or more stores price the same item differently, you can stillmaintain one master database by creating an item price change and sendingthe price change to the stores requiring the new price.

The Price Changes method of pricing enables the corporate location to controlthe minimum price and set a recommended price for an item on a pricechange.

Locked Indicates the store is restricted from changing the item price. TheLocked column only appears when you access the Price Changes functionfrom the corporate location. Stores are unable to view the Locked column.

Active Indicates the price change for the item affects the price of the itemin the FOH. If you clear the check box, the item uses the price defined at the

item level.Item Name Indicates the name of the item as defined in Maintenance >Menu > Items. All items in the Items file appear in the list.

Min Price Indicates the minimum price the store can use for pricing theitem. The Min Price is not editable at the store level. A CDM administrator sets the minimum price for the item.

Rec. Price Indicates the recommended price of the item. A CDM adminis-trator determines the recommended pr

centralized data management 62

Documents