12/09/06

POSIDBF2

The purpose of this document is to list the various DBF files that can be

produced by POSitouch. This document does not explain POSIDBFW.EXE only, rather, includes several programs maintained by POSitouch for producing a variety of DBF files.

POSitouch maintains DBF files that include sales data, time and attendance

information, inventory information, as well as, a variety of other items. At the beginning of this document, are the names of the programs that produce various DBF files along with the names of the files these programs produce. The remainder of the document is organized by executable, followed by the file(s) produced by that executable. Each section explains how to produce the various DBF files from each executable. Users may wish to note that POSitouch also maintains a variety of XML files. Documentation regarding the XML files can be found on the POSitouch ftp site.

2

DBF Files & Program Files

POSIDBF 7

POSIDBFW FILE LAYOUTS 9

ADJUSTS.DBF 9

CASHOUT.DBF 11

CASHOUT2.DBF 12

CATSALES.DBF 13

CHKHDR.DBF 13

CHKITEMS.DBF 13

CONTROL.DBF 14

DAILY.DBF 14

DEPOSITS.DBF 15

DISCOUNT.DBF 15

FCOSTN.DBF 16

HRSALES.DBF 17

ITMSALES.DBF 17

JOURNAL.DBF 18

LAYOUT.DBF 20

MITEMS.DBF 20

MAJSALES.DBF 20

NAMES.DBF 20

NAME????.DBF 21

NAMEMIN.DBF 21

NAMEJOB.DBF 22

NAMETRSN.DBF 23

NAMERACE.DBF 23

NRT.DBF 24

PAIDMAST.DBF 24

PAIDOUTS.DBF 24

PSCLUB.DBF 25

PSDEBIT.DBF 25

SALES.DBF 25

SALESTAX.DBF 26

SHFTSLS.DBF 26

USERS.DBF 27

VDUBUMP.DBF 27

PMOUTPUT.DBF 28

SHOUTPUT.DBF 29

TADBF FILES 30

LABOR.DBF 30

LABOR2.DBF 30

SCHED.DBF 31

SCHED2.DBF 31

TAW DBF FILES 32

EMPFILE.DBF 33

JOBFILE.DBF 34

JOBLIST.DBF 34

SALEPRED.DBF 34

SCHOVR.DBF 34

SCHSETUP.DBF 35

SCHSHIFT.DBF 35

DEPTFILE.DBF 35

DEPTLIST.DBF 36

TARW.EXE 37

PAYRHEAD.DBF 39

PAYRJOBD.DBF 40

PAYRPUNC.DBF 41

3

HRSLSAVG.EXE 43

HRSLSAVG.DBF 43

HRTRNAVG.DBF 43

HRCSTAVG.DBF 44

HRCOVAVG.DBF 44

HRPRDAVG.DBF 45

THE CHKTODBF DATABASE 49

Files Created by CHKTODBF 50

CHECK.DBF 50

DATE.DBF 50

MAINITEM.DBF 50

MGR_TRAN.DBF 51

OPTIONS.DBF 51

NOTFOUND.DBF 51

PAYITEM.DBF 52

PAYMEMO.DBF 52

PAYMENT.DBF 53

TAXES.DBF 53

TRANSACT.DBF 53

ZEROREC.DBF 53

MISC. REPORTSW FILES ( REPORTSW.EXE ) 55

SERVPROD.DBF 55

SERVCAT.DBF 55

INW.EXE FILES 56

INVDATE.DBF 56

INVCOUNT.DBF 56

INVTYPE.DBF 56

INVPAGE.DBF 57

INVDBFW.EXE FILES 58

CATEGORY.DBF 58

INGRED.DBF 58

MENUITEM.DBF 59

RECIPE.DBF 59

WEEKINV.DBF 59

Diagram INVDBFW file relationships 61

SCRTODBF.EXE 62

MENUS.DBF 62

CCTXCODE.DBF 63

MSCREENS.DBF 63

OSCREENS.DBF 63

CELLS.DBF 63

OPTGRP.DBF 64

OPTGRMEM.DBF 64

COUPGRP.DBF 64

CPGRPMEM.DBF 65

INCOLLCT.EXE 66

INVDAILY.DBF 66

INVTHEOR.DBF 67

APPENDIX A - PDmmddyy.LOG Log File 68

12/09/06

Important Concepts

DBF File Paths POSitouch utilities are run from wthin the \SC folder, and the output files are placed in the \DBF folder. While it is possible to define the file path for .dbf files in POSitouch through the Backoffice Setup > Payment > Sales Journal > User DBFs, it is advisable to leave these fields blank. By default, most of the POSitouch utilities listed here, will place the DBF files created, in the \DBF folder of the computer where the program is executed. Additionally, where noted, the executables listed in this document will place the DBF files in the \ALTDBF folder, when called with the /ALT parameter. Consider the \ALTDBF directory a scratch directory for any third party program to use, as desired. The \ALTDBF folder is available for third party programs to use as needed. Third party programs may place any needed DBF files in this directory without affecting any of POSitouch's operations or reporting capabilities. POSitouch also advises that third party programs, first clear the \ALTDBF folder before building any DBF files on a daily basis. By deleting files in the \ALTDBF folder, then executing the desired commands, third party programs can ensure that the data found in the \ALTDBF folder is the data desired. Finally, if users feel that populating the DBF path names in the Backoffice Setup area is needed, users should ensure that the drive letter is not included in the path name. For example, if users wish to populate a folder called "MyData", the correct path name would be \MyData. Users need not enter C:\MyData.

/ALT Parameter The /ALT parameter is used to place files in the "alternate" directory. By default, applications write DBF files to the \DBF folder. Using the /ALT parameter will write these file to the \ALTDBF folder. See the previous section for a full explanation. See each executable listed in this document for those that support the /ALT parameter. Sample Commands Using the /ALT Parameter Create POSIDBF's files in the alternate ( \ALTDBF ) directory for May 1, 2006 through May 30, 2006 POSIDBF /ALT 05/01/06 05/30/06 Create POSIDBF's files in the alternate directory for a time span of 10 days ago to 2 days ago POSIDBF /ALT 10 2 Create TAW's files in the alternate directory, including all employees, even those that may be inactive TAW exportall /ALT Create TARW's files, including open punches ( 93 ), for a week ( 2 ) for 1 week prior to the system date ( 1 ), and place the files in the alternate ( /ALT ) folder ( \ALTDBF ) TARW R 93 2 1 /ALT

5

Killproc.exe Killproc.exe is a program supplied with POSitouch that will "kill" a running process on the local computer. It is advisable to add this program to a batch file the is being used to create DBF files. This will ensure that any program that may have encountered an issue when run previously and is still loaded in memory, will be closed prior to the next execution of the program. Syntax : Killproc [exectuable_name] Sample : Killproc posidbfw.exe

Runwait.exe Runwait.exe is a utiltiy supplied by POSitouch, that when called, ensures that a program completes execution prior to moving on the next command in a batch file. Syntax : Runwait [executable_name] [executable's_parameters] Sample : RUNWAIT POSIDBF /ALT 10 1

6

Sample Batch File Below is a sample batch file that creates files in the alternate folder ( \ALTDBF ), by using the /ALT command where supported. ;Sample Batch File ;If running the batch on a machine that is not the POSDRIVER, but the data ;resides on the POSDRIVER ( mapped drive letter L: ), change to the L: drive L: ;Clear the \altdbf folder cd\altdbf del *.* ;Stop any processes that may be running cd\sc killproc posidbfw.exe killproc taw.exe killproc chktodbf killproc scrtodbf killproc inw killproc incollct killproc invdbfw ;Execute programs to build dbf files RUNWAIT POSIDBF /ALT 10 1 create files from 10 days to 1 day ago RUNWAIT CHKTODBF 05/01/06 /ALT create files for May 1, 2006 RUNWAIT INVDBFW /ALT RUNWAIT REPORTSW.EXE 7 F 04/01/06 05/01/06 /ALT create files from start date to end date RUNWAIT TAW exportall /ALT create files in the alternate directory

7

POSIDBF

POSIDBF.EXE Command Line Switches /DAILY - Daily processing - Create files in \DBF\ for all checkfiles from the beginning

of this year to present. /DAILY # - Daily processing - Create files in primary directory for all checkfiles for the

beginning of # years ago to present. /DBF mm/dd/yy - Process data bases. Create files in the primary directory for checkfile for

specified date (mm/dd/yy) /ALT mm/dd/yy mm/dd/yy - Alternate dir for dates - Create files in alternate directory for all checkfiles

from first date (mm/dd/yy) to last date (mm/dd/yy) /ALT #1 #2 - Alternate dir for relative days create files in alternate directory for all files

from #1 days ago to #2 days ago /ALT ... /F file file - With above to create only listed files, e.g. posidbf /alt 1 1 /f hrsales users

will create hrsales.dbf and users.dbf in alternate directory from yesterdays checkfile

/PURGE - Purge data bases /REDO - Recompile selected data this really just erases the dbf files in the primary

directory /HELP - Display help /SETUP - Set up for data base processing advance the year /MENU - Menu /LOC- - runs POSIDBFW and places the output DBF files into the specified directory.

If the directory contains spaces in the name, then the entire parameter should be enclosed in quotes. For example, POSIDBFW /daily /LOC-C:\test dbf folder\. Note that a hyphen is required between LOC and the directory path. For path locations without a space in the directory name, the following example would work : POSIDBFW /daily /loc-C:\newdbfs\

/RDC Creates files in the directory of C:\RDCDBF Logging Capabilities - See Appendix A POSIDBFW writes a log file of activites when run. The log file is named PDmmddyy.LOG, where mmddyy is the month, day, year when the program was run. Directories Note that if the DBF directories under Setup > Payment > Sales Journal > User DBFs are left blank, the default Primary Directory will be \DBF and the Alternate Directory will be \ALTDBF. When defining a directory other than the default, users should NOT enter a driver letter as part of the path.

8

POSitouch dBASE Compatible File Output This document describes the POSitouch dBASE compatible file output facility. The purpose of this feature is to build a .dbf database at each site to make key data easily available to produce standard and custom reports. The key features of the .DBF facility are:

Multiple selectable files - each site need only produce the files it wants. For example if Paidout detail records are not needed, the Paidout file need not be produced.

Purging timeframes for each file and some subsections of files. If you want Item Sales data to be kept for 2 years you can specify this and if you want Hourly Sales data purged after 2 months, you can specify this.

Store number in each record to facilitate merging multiple sites' data at a central site. Purging and processing steps built into POSitouch nightly procedures. Names and Item Names files created each night to give user POSitouch names for

fields such as Payment Types, Menu Items, Terminals, Shifts, Costcenters. Ability to reprocess dates whose data may be damaged or has been adjusted. Ability to process files for any time period including previous years. All files put into a separate subdirectory: \DBF. Ability to make a set of files on the fly into an alternate directory.

The setups are found in SETUP-PAYMENT-SALES JOURNAL-DBASE FILES. In this area the flags to select which files to produce are set as well as the purging timeframes in days. If the purging timeframe is 0, data is never purged. At present it is required that there be a \DBF subdirectory as this is where the files will be stored. Once this setups have been done, fiscal year dates can be setup under SETUP-DBASE FILES. In this area a menu of 4 choices is available:

Process Files - this function processes check files for a fiscal year from a list of 10 fiscal years. The processing starts with the Processing Start Date for the year and continues for 365 days (for previous years) or until the last completed checkfile, usually yesterday's (for the current year). If the file has already been processed, it is skipped. If it is missing, it is skipped. This function is generally not needed as it is run automatically during nightly processing. It would be used if a previous year needed processing or if a range of days was being recompiled (see below).

Recompile Days - This function resets the "already processed" flag for a range of dates and purges data from all .dbf files for those dates. The next time check files are processed for the year(s) in question, these files will be reprocessed and added to the .dbf files.

Setup Years - This function allows entry of the Fiscal Year, Year Start Date and Processing Start Date for each of 10 fiscal years. The Year Start Date is important as it determines the week start day and must be selected correctly to determine this day. The Processing Start Date determines the processing of check files for the nightly procedure. There is a function available to create a new year which pushes the table down and opens up entry number 1 which is the "current year". It should be noted that since data can be retained indefinitely, reports can retrieve data for any dates without regard to the fiscal year setups.

Process Single Day - This processes a single check file. This function should be seldom needed.

9

POSIDBFW FILE LAYOUTS The following are the file layouts for the .DBF files. Note the file NAMES.DBF which contains names related to coded fields in other files.

ADJUSTS.DBF Lists adjustments made to the check file via PSNEWW.EXE. All fields are not used in all records, see following page.

# Name Type Width Dec Usage 1 ADJ_TYPE N 2 Adjustment type ( 1 8 see table below ) 2 DATE D 8 Date of this transaction 3 TIME C 5 Military Format, HHMM format 4 LOG_DATE D 8 Date adjustment was performed 5 TO_ACCTNUM C 20 Account number adjusted to 6 TO_ACCTNAM C 30 Account name adjusted to 7 AMOUNT N 12 Amount of adjustment 8 ACCT_NUM C 20 Account number adjusted from 9 ACCT_NAME C 30 Account name adjusted from 10 CASHIER_ID N 4 Cashier number 11 SERVER_ID N 4 Server number 12 TERM_NO N 4 Terminal number to adjust 13 SHIFT N 1 Shift being adjusted 14 TAX_NO N 20 15 TAX_AMOUNT N 12 Tax amount of adjustment 16 TIP_AMOUNT N 12 Adjusted tip amount 17 CC_NUM N 4 Cost center number 18 CC_NAME C 30 Cost center name 19 Category N 4 Sales Category Number Adjustment Type Key Valid values for the adjustment type are 1 8, inclusive. Value Definition 1 Move Money 2 Tip Account Adjustment 3 Change or Issue 4 Paidouts Adjustment 5 Customer Count Adjustment 6 Misc. Deposit Adjustment 7 Additional Sales ( positive dollar value ) 8 Overrings ( or Additional Sales with a negative dollar value )

10

Field Adjustment Type

1 2 3 4 5 6 7 8 1 D D D D D D D D

2 D D D D D D D D

3 D D D D D D D D

4 D D D D D D D D

5 D

6 D

7 D D D D D D D D

8 D D D D D D D

9 D D D D D D

10 D D D

11 D D D D

12 D D D

13 D D

14 D D D D D D D

15 D D

16 D D

17 D D D

18 D D D

19 D D D

11

CASHOUT.DBF All of the cashout data, continued in Cashout2.dbf.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of this transaction 3 SHIFT C 1 'E' = Entire Day, 'P' = Partial Shift 4 SH_START C 5 Start of shift 5 SH_END C 5 End of shift 6 CO_TYPE C 1 Cashout type: 0-Entire House, 1-Term, 2-Server 7 DESCR C 20 Name of cashout 8 CO_NUMBER N 3 Device/server number 9 DRAWER N 2 Cash drawer number 10 COST_CENTR N 2 Cost center number 11 CC_CODE C 5 Cost center code number CC### 12 US_SLSWTX N 12 2 Total sales plus tax - For Server Cashouts Only 13 US_CHECKS N 6 Number of checks - For Server Cashouts Only 14 US_SALES N 12 2 Total sales - For Server Cashouts Only 15 US_TIPS N 12 2 Total Tips - For Server Cashouts Only 16 DEPOSIT_01 N 12 2 Payment type 1 deposit amount 17 TIPS_01 N 12 2 tips 18 CHANGE_01 N 12 2 change issued 19 TRANS_01 N 6 number of transactions ... ... ... 92 DEPOSIT_20 N 12 2 93 TIPS_20 N 12 2 94 CHANGE_20 N 12 2 95 TRANS_20 N 6 96 DISCOUNT01 N 12 2 Total discounts given . ... . 110 DISCOUNT15 N 12 2 111 TIPS_SERVR N 12 2 Tips paid to servers 112 PAIDOUTS N 12 2 Paidouts 113 TRAINING N 12 2 Total training sales 114 MISC_DEP N 12 2 Miscellaneous deposit 115 ACT_DEP N 12 2 Actual deposit 116 CC_TIP_SLS N 12 2 Credit Catd Tip Sales 117 CC_TIP_TIP N 12 2 Credit Catd Tip Tips 118 TIP_CHECKS N 12 2 Tip Checks 119 TP_CHK_SLS N 12 2 Tip Check Salse 120 TOT_TP_DSC N 12 2 Total tip discounts 121 SVR_NRT_DL N 12 2 Server NRT Deletes 122 SVR_NRTD_M N 12 2 Server NRT Delete Multiplier 123 NUM_ITEMS N 12 2 Number of Items 124 US_DECL_TP N 12 2 Server declared tips 125 TP_ADJ_THS N 12 2 Adjusted tips this week 126 TP_ADJ_LST N 12 2 Adjusted tips last week 127 IS_TIPPED L 1 Logical, is user tipped 128 SEQ_NUM N 6 Sequence number to relate to cashout2.dbf Index :DATE

12

The proper formula for determining expected cash for a terminal, server or entire house is as follows: Expected Cash = DEPOSIT_01 - PAIDOUTS Note that if Miscellaneous Deposits are entered via the Sales Journal program, these must be added in (MISC_DEP).

CASHOUT2.DBF Extension of Cashout.dbf.

# Name Type Width Dec Usage 1 STORE C 4 Store number 2 DATE D 8 Date of transaction 3 SHIFT C 1 E = Entire Day, P = Partial Shift 4 SH_START C 5 Start of shift 5 SH_END C 5 End of shift 6 CO_TYPE C 1 Cashout type, 0-Entire House, 1-Terminal, 2-Server 7 DESCR C 20 Name of cashout 8 CO_NUMBER N 3 Device or server number 9 DRAWER N 2 Cash drawer number 10 COST_CENTR N 2 Cost center number 11 CC_CODE C 5 Cost center code CC### 12 SEQ_NUM N 6 Cashout number for this date. Each day starts at 1. 13 CASHO_SEQ N 3 Sequence number of cashout for this server/terminal/house 14 TRAIN_CHK N 6 Number of training checks for this cashout 15 TRAIN_AMT N 12 2 Dollar amount of the training checks 16 DEL_BEFORE N 6 Number of deletes before sending 17 DEL_BF_AMT N 12 2 Dollar value of deletes before sending 18 DEL_AFTER N 6 Number of deletes after sending 19 DEL_AF_AMT N 12 2 Dollar value of deletes after sending 20 OVERRINGS N 6 Number of overrings 21 OVERRN_AMT N 12 2 Dollar value of overrings 22 CANCELS N 6 Number of cancels user quit from check 23 CANCEL_AMT N 12 2 Dollar value of cancels 24 NRT_CN_AMT N 12 2 Dollar value of cancels affecting the NRT total 25 NONZ_CANCL N 6 Count of non-zero cancels 26 NO_SALES N 6 Number of No sales 27 ACT_DEP_01 N 12 2 Actual Deposit for Pay Type 01 - Cash 28 ACT_DEP_02 N 12 2 Actual Deposit for Pay Type 02 ... Actual Deposit for Pay Types 3 - 19 46 ACT_DEP_20 N 12 2 Actual Deposit for Pay Type 20 47 BANKS_SKIMS N 12 2 Net Total of Banks and Skims, included in Paidouts Total 48 Sale_amt01 N 12 2 Sales amount for Sales Category 1 49 Sale_cnt01 N 6 Count of items sold from Sales Categroty 1 ... Fields 48 & 49 repeated for all Categories 2 - 20 86 Sale_amt21 N 12 2 Sales amount for Unassigned Sales 87 Sale_cnt21 N 6 Count of items sold for Unassigned Sales

13

CATSALES.DBF Sales for categories, with item numbers

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 Inv_Number N 9 Inventory Number of the item 3 CATEGORY N 2 Major Category

CHKHDR.DBF CHKHDR.DBF and CHKITEMS.DBF together contain information about individual checks in the file. CHKHDR contains check header data, referring to general information about the check. # Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of this transaction 3 CHECK_NUM N 5 Check Number 4 DISC_NUM N 2 Discount Number (Zero for no disc) 5 OVERRING L 1 Is this an Overring? 6 TABLE N 4 Table Number 7 COST_CENTR N 5 Cost Center Number 8 USER_NUM N 3 User Number 9 TIME N 4 Time of Check 10 SHIFT N 2 Shift Code 11 NUM_PARTY N 4 Number in Party 12 AMOUNT N 9 2 Amount of Check 13 TAX_TOTAL N 9 2 Total Tax 14 DISC_PRINT N 9 2 Discount Printed 15 DELIV_TIME N 6 Delivery time in seconds 16 SERV_TIME N 6 Service time in seconds 17 SEQ_NUM N 6 Unique transaction sequence number 18 DISC_MNGR N 6 Manager who applied discount for discount check 19 CO_SEQ_HSE N 3 Link to CASHO_SEQ -Cashout.dbf Entire House shift records 20 CO_SEQ_TRM N 3 Link to CASHO_SEQ -Cashout.dbf Terminal shift records 21 CO_SEQ_USR N 3 Link to CASHO_SEQ -Cashout.dbf Cashier shift records 22 PAY_TERM N 3 Terminal check paid at link to cashout.dbf 23 PAY_DRAWER N 2 Drawer check paid to link to cashout.dbf 24 PAY_CASHR N 6 Cashier who paid the check link to cashout.dbf 25 US_SLSWTX N 9 2 Check total with tax preferred check total figure 26 PAY_TIME N 6 Time check was paid in HHMMSS format(Hour Minute Seconds)

CHKITEMS.DBF This contains information about individual check items. # Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of this transaction 3 CHECK_NUM N 5 Check Number 4 SEQ_MAIN N 4 Item Sequence Number 5 OPTION L 1 Is this an Option (TRUE) or main item (FALSE) 6 ITEM_NUM N 9 Item inventory number 7 MAJOR N 2 Major Category Code 8 MINOR N 2 Minor Category Code 9 SALES_CAT N 2 Sales Category Code 10 DISC_NUM N 2 Discount Number (Zero for no disc)

14

11 TAXCODE N 1 Tax Code 12 NUM_SOLD N 8 2 Quantity Sold 13 DELETION N 1 Deletion Code 14 DEL_USER N 3 Deletion User 15 OVERRING L 1 Is this an Overring? 16 COVER L 1 It this a Cover Item? 17 MENU_PRICE N 9 2 Full Price 18 SALES_AMT N 9 2 Real Price (after discount) 19 TABLE N 4 Table Number 20 COST_CENTR N 5 Cost Center Number 21 USER_NUM N 3 User Number 22 TIME N 4 Time of Check 23 SHIFT N 2 Shift Code 24 COVERS N 6 2 Number of covers - decimal 25 PRICELEVEL N 2 Price level 1-10 26 COMP L 1 This item is a comp 27 SEQ_NUM N 6 Unique transaction sequence number 28 DISC_MNGR N 6 The manager performing the discount 29 COMP_APPL L 1 Comp applied to this check item ( boolean ) 30 COUP_APPL L 1 Coupon applied to this check item ( boolean ) 31 SEND_TIME N 4 When the option Record Send Times is on, this field Displays the time the item was sent. 32 COMP_USER N 3 Person performing the comp 33 CP_ZERO L 1 The item whose price is reduced to zero because of a Coupon. In cases where Buy One Get One free coupons are used, the item that is free will have a Y ( YES ) for CP_ZERO. In cases where multiple items are discounted for A set price, like buy 2 for $ 2.00, the 2 items CP_ZERO Field is set to Y and the coupons value is the $ 2.00

CONTROL.DBF This sets the fiscal year dates. It is used by PS determine the starting date for daily processing.

# Name Type Width Dec Usage 1 FISCL_YEAR N 2 Fiscal year. 2 YEAR_START D 8 Start of Fiscal year, could be in previous year. 3 PROC_START D 8 First date to be processed, usually YEAR_START.

DAILY.DBF This controls the daily processing of the data files. Except for YEAR all fields flag whether

a particular date or week has been processed. The letter "U" means Unprocessed, "P" means Processed, and "R" means Reprocess.

# Name Type Width Dec Usage 1 YEAR N 2 Calendar Year 2 LABOR1 C 122 Labor data, one character per day of the year 3 LABOR2 C 122 It takes 3 consecutive fields for all 365 (366) 4 LABOR3 C 122 days of the year. 5 SALES1 C 122 Sales data, one character per day of the year 6 SALES2 C 122 It takes 3 consecutive fields for all 365 (366) 7 SALES3 C 122 days of the year. 8 WEEKLY C 53 Weekly labor figures. One character for each of the 52 (53) weeks of the year.

15

DEPOSITS.DBF This lists the deposits for all the terminals. There is one record per terminal, shift, and

cash drawer. # Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE N 8 Date of check file 3 TERMINAL N 2 Terminal # - 0 means entire house 4 DRAWER N 1 Drawer # - 1 or 2 5 SHIFT N 1 Shift 1-5 6 AMOUNT N 9 2 Deposit amount Index: DATE

DISCOUNT.DBF Discount.dbf contains information about all discounts, sorted by cost center and then

discount code. # Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of this transaction 3 CAT_CODE C 5 Sales category number( 3 digits ), with SC as a prefix. 4 DISC_CODE C 5 Discount number ( 3 digits ), with DI as a prefix. 5 AMOUNT N 9 Total Dollar value of Discounts 6 QUANTITY N 9 Total Number of Discounts

16

FCOSTN.DBF This list all menu items in the inventory file.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 INV_NUMBER N 9 Inventory number 3 DESCR C 25 Inventory description 4 MAJOR N 2 Major category 5 MINOR N 2 Minor category 6 CODE C 5 Major/minor code MM### 7 REPORT_SEQ N 6 Report sequence number 8 PRICE_1 N 8 2 Menu price #1 9 PRICE_2 N 8 2 Menu price #2 10 PRICE_3 N 8 2 Menu price #3 11 FOOD_COST N 8 2 Food Cost 12 ALT_INVNUM N 6 Alternate inventory number 13 POINTS N 7 2 Country club system points earnable 14 BAR_CODE C 15 Optional bar code number for laser scanner 15 PRICE_4 N 8 2 Menu price #4 16 PRICE_5 N 8 2 Menu price #5 18 PRICE_6 N 8 2 Menu price #6 19 PRICE_7 N 8 2 Menu price #7 20 PRICE_8 N 8 2 Menu price #8 21 PRICE_9 N 8 2 Menu price #9 22 PRICE_10 N 8 2 Menu price #10 23 START_DATE D 8 Start Date 24 END_DATE D 8 End Date 25 MASTER_ITEM N 9 Master menu item number 26 EXT_DESCR C 10 Extended description 27 PREP_TIME N 2 Prep Time 28 COVERS N 4 1 Covers Index: DESCR, str(MAJOR,2,0)+str(MINOR,2,0)

17

HRSALES.DBF This is daily sales totals by half hour and cost center.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of this transaction 3 COST_CENTR N 2 Cost Center (0=Entire house) 4 CC_CODE C 5 Cost Center code CC### 5 HOUR N 2 Sales period (1 to 48) 6 SALESCT_01 N 9 2 Sales for category #1 ... ... 26 SALESCT_21 N 9 2 Sales for unknown category 27 TOT_SALES N 9 2 Total sales 28 VOID_SALES N 9 2 Total voids in dollars 29 VOID_COUNT N 9 2 Total number ov voids 30 DINE_TIME N 9 2 Total dining time in minutes 31 COVR_SALES N 9 2 Total cover sales 32 COVR_COUNT N 4 Total cover counts 33 COVR_CHKS N 4 Total cover checks 34 CHECKS N 4 Total number of checks 35 PARTY N 4 Total number in party Index: DATE

ITMSALES.DBF This file contains item by item sales by shift. Cost center is not presently available.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of this transaction 3 COST_CENTR N 2 Cost Center (0=Entire house) 4 CC_CODE C 5 Cost Center code CC### 5 SHIFT C 1 Shift number 6 INV_NUM N 4 Inventory number 7 SALES N 9 2 Total sales in dollars 8 COUNTS N 9 2 Total quantity sold 9 DELS N 9 2 Total quantity deleted ( See notation below ) Index: DATE Note : In Backoffice Setup > Deletion Reasons, each reason contains a flag Prepared. This flag allows POSitouch to determine those items that should be removed from inventory for control purposes. This flag will cause a reduction in inventory on hand. An example of this would be an item prepared, refused by a guest and then discarded. There are two instances where deleted items will not be shown in the DELS ( deletes ) field, these are :

a. Deletes before sending b. Deletes after sending, when the Deletion Reason used does not have the Prepared

flag set.

18

JOURNAL.DBF This is the sales journal report with each individual line as a record.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of this transaction 3 COST_CENTR N 2 Cost Center (0=Entire house) 4 CC_CODE C 5 Cost center code number "CC###" 5 ACCT_POSI N 4 POSITouch Account number 6 ACCT_NUM C 15 Account number 7 ACCT_NAME C 20 Account name 8 CREDIT N 9 2 Credit amount 9 DEBIT N 9 2 Debit amount Index: DATE

The ACCT_POSI number is defined below :

Standard Account Numbers: 1 Sales Category 1 (Food) 2 Sales Category 2 10 Sales Category 10 Sales Category 11 20 are continued at account number 50. 11 [Unused] 20 Tax 1 21 Tax 2 22 Tax 3 23 Tax 4 30 Miscellaneous Deposit

31 Discount #1 (Manager) 32 Discount #2 33 Discount #3 34 Discount #4 35 Discount #5 41 Manager Paidout Category 1 42 Manager Paidout Category 2

50 Manager Paidout Category 10 51 Miscellaneous Manager Paidout 60 Tips To Servers 61 Training Total

62 Discrepancy 71 Discount #1 (As of Version 4.57) 72 Discount #2

73 Discount #3 74 Discount #4 75 Discount #5 76 Discount #6

19

77 Discount #7 78 Discount #8 79 Discount #9 80 Discount #10 81 Discount #11 82 Discount #12 83 Discount #13 84 Discount #14 85 Discount #15 111 Manager Paidout Category 1 (As of Version 4.59) 112 Manager Paidout Category 2

140 Manager Paidout Category 30 141 Miscellaneous Manager Paidout

101 Actual Deposit Total (Cash) 102 Payment Type 1 Refund Amount (always Credit) 103 Over/Short 104 Over 105 Short 150 Sales Category 11 151 Sales Category 12 159 Sales category 20 160 Unassigned Sales 201 Payment Type 2 Total 202 Payment Type 2 Refund Amount 203 Payment Type 2 Cash Change (Debit = Credit) 204 Payment Type 2 Tip Credit 301-304 Pay Type 3 - Same as for Payment type 2 (201-204)

2001-2004 Pay Type 20 - Same as for Payment type 2 (201-204)

20

LAYOUT.DBF This file contains miscellaneous information.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant Store number 2 NAME C 25 Store name 3 LASTSDDATE C 8 Last shutdown date 4 LASTSDTIME C 5 Last shutdown time 5 BUS_SDTIME C 8 Business shutdown date 6 EURO_DATE L 1 Is date in European format (DD/MM/YY)?

MITEMS.DBF A matrix of menu items sold. Sorted by Shift, then cost center, then by item. Only items with non zero in quantity sold are recorded.

# Name Type Width Dec Usage 1 STORE C 4 Store number 2 DATE D 8 Date 3 COST_CENTR N 2 Cost Center 4 CC_CODE C 5 Alpha numeric cost center code 5 INV_NUM N 9 Inventory number of menu item 6 SHIFT N 1 Shift 7 SALES N 10 2 Total sales of the item in dollars and cents 8 COUNTS N 10 2 Number sold 9 DELS N 10 2 Number of deletes

MAJSALES.DBF This is a sales by major category DBF

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of this transaction 3 CC_CODE C 5 Cost center code number "CC###" 4 SHIFT_CODE C 5 Shift code number "SH###" 5 MAJOR_CODE C 5 Major category code number "MA###" 6 SALES N 9 2 Total sales in dollars Index: DATE

NAMES.DBF This is a list of all of the various user assigned names.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 CODE C 5 Source of the name, described below 3 NAME C 20 The user assigned name Index: CODE CODE is made up of 2 upper case letters and 3 decimal sequence number. Although some names are unassigned they are included, but are left blank. The following is a list of the codes:

CC - Cost Centers DI - Discounts DS - Discount subtracts from sales GR - Gratuities

21

LD - Labor Departments MA - Major category names MI - Minor category names OD - Other devices PC - Payment change types PD - Payment deposit types PO - Paidouts PR - Printer Devices PY - Payment types SC - Sales Categories SG - Service Charges SH - Shifts TD - Terminal Devices

NAME????.DBF NAMES.DBF contains all of the codes for user-defined names. This information is also in a series of tables that each contain an single type of name and a relation through a numeric value for the related field. In general these tables represent a simpler way to get names for things in POSitouch. NAMESCAT.DBF - Sales Categories NAMEUTYP.DBF - User Types NAMEDEL.DBF - Deletion Codes NAMECC.DBF - Cost Centers NAMELADJ.DBF - T & A Adjustment Reasons NAMESHFT.DBF - Shifts NAMEPAY.DBF - Payment Types NAMEDSC.DBF - Discounts NAMESCAT.DBF - Category Names as defined in Setup > Reports > Sales & Cat. Sls Trend NAMETERM.DBF - Terminals NAMEPRTR.DBF - Printers NAMEOTHR.DBF - Other devices NAMELABR.DBF - Labor Departments NAMEMAJ.DBF - Major Categories NAMEMIN.DBF - Minor Categories NAMEHCAT.DBF - Hourly Categories NAMEHSFT.DBF - Hourly Shifts NAMEPAID.DBF - Manager Paidouts All of these files with the exception of NAMEMIN have the same structure: # Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 CODE N 2 Code Number 3 NAME C 20 The user assigned name

NAMEMIN.DBF # Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 3 MAJOR_NUM N 2 Major Category Number 2 CODE N 2 Code Number 3 NAME C 20 The user assigned name

22

NAMEJOB.DBF # Name Type Width Dec Usage 1 STORE C 4 0 Restaurant Chain Store number 2 DEPT_NUM N 2 0 Department Number 3 CODE N 2 0 Code Number 4 NAME C 20 0 The user assigned named

23

NAMETRSN.DBF This file contains the Termination Reasons as defined in Setup > Time & Attendance > Backoffice Setup > Options > Termination Reasons.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 CODE N 2 Termination reason number, starts at 1. 3 NAME C 30 Name of termination reason ( text ).

NAMERACE.DBF This file contains the RACES as defined in Setup > Time & Attendance > Backoffice Setup > Options > Race.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 CODE N 2 Race code, starts at 1 3 NAME C 15 Race label ( text ).

24

NRT.DBF This file contains Non-Resettable Totals data.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of check file 3 NRT_START N 13 2 Starting NRT number. 4 NRT_END N 13 2 Ending NRT number. 5 NRT_OPNTAB N 9 2 NRT open tables 6 NRT_DELITM N 9 2 NRT deleted items + deleted tables 7 NRT_DSCSUB N 9 2 NRT discounts that subtract 8 NRT_ADDSLS N 9 2 NRT additional sales 9 NRT_OVRING N 9 2 NRT overring sales Index: DATE

PAIDMAST.DBF This is a list of the 30 potential paidout names and account number.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 CODE C 5 Paidout Category (POxxx: xxx = 001-030) 3 NAME C 20 Paidout Name 4 ACCT_NUM C 15 Paidout Account Number

PAIDOUTS.DBF This lists all of the paidouts.

# Name Type Width Dec Usage 1 STORE C 5 Restaurant chain Store number 2 DATE S 8 Paidout date 3 TIME S 5 Paidout time 4 CODE C 5 Paidout Category (POxxx) 5 AMOUNT S 9 2 Paidout amount 6 MEMO S 30 Paidout memo Index: DATE

25

PSCLUB.DBF Club account transactions details.

# Name Type Width Dec Usage 1 STORE C 4 Store Number 2 DATE D 8 Date of transaction 3 ACCOUNT C 20 Account Number 4 AMOUNT N 7 2 Amount of transaction 5 PAY_CODE C 5 Payment type in Code format 6 CHECK_NUM N 5 Check number 7 COST_CENTR C 5 Cost Center 8 NUM_PARTY N 4 Number in party 9 SALESCT_01 N 9 2 Sales amount for category 1 10 SALESCT_02 N 9 2 Sales amount for category 2 28 SALESCT_20 N 9 2 Sales amount for category 20 29 SALESCT_21 N 9 2 Sales amount for category 21 30 TAX_1 N 9 2 Tax 1 amount for the check 31 TAX_2 N 9 2 Tax 2 amount for the check 32 TAX_3 N 9 2 Tax 3 amount for the check 33 TAX_4 N 9 2 Tax 4 amount for the check 34 DISC_CODE C 5 Discount code for any applied discount 35 DISC_AMT N 9 2 Discount amount for the check 36 TIP N 9 2 Tip ( Gratuity ) amount 37 SPLIT_PAY L 1 Logical Payment was split 38 CLUB_TIP N 9 2 Tip Amount

PSDEBIT.DBF Debit transactions details.

# Name Type Width Dec Usage 1 STORE C 4 Store number 2 DATE D 8 Date of transaction 3 MEMNUM C 5 Member number 4 FAMNUM C 2 Family number 5 ACCOUNT C 20 Account number 6 TRANS_AMT N 9 2 Transaction amount 7 TRANS_TYPE C 1 Transaction type - U-Debit redeemed S-Sale of debit 8 CHECK_NUM N 5 Check number 9 BALANCE N 9 2 Balance on account 10 TIME N 4 Time of transaction

SALES.DBF This is daily sales totals for entire day.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of this transaction 3 COST_CENTR N 2 Cost Center (0=Entire house) 4 CC_CODE C 5 Cost Center code CC### 5 SALESCT_01 N 9 2 Sales for category #1 ... ... ... 25 SALESCT_21 N 9 2 Sales for unknown category

26

26 TOT_SALES N 9 2 Total sales 27 VOID_SALES N 9 2 Total voids in dollars 28 VOID_COUNT N 9 2 Total number ov voids 29 DINE_TIME N 9 2 Total dining time in minutes 30 COVR_SALES N 9 2 Total cover sales 31 COVR_COUNT N 4 Total cover counts 32 COVR_CHKS N 4 Total cover checks 33 CHECKS N 4 Total number of checks 34 PARTY N 4 Total number in party 35 TAX_COLL_1 N 9 2 Sales Tax Collected #1 36 TAX_COLL_2 N 9 2 Sales Tax Collected #2 37 TAX_COLL_3 N 9 2 Sales Tax Collected #3 38 TAX_COLL_4 N 9 2 Sales Tax Collected #4 39 TAX_OWED_1 N 9 2 Sales Tax Included #1 40 TAX_OWED_2 N 9 2 Sales Tax Included #2 41 TAX_OWED_3 N 9 2 Sales Tax Included #3 42 TAX_OWED_4 N 9 2 Sales Tax Included #4 Index: DATE

SALESTAX.DBF This lists the sales and tax data.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of check file 3 COST_CENTR N 2 Cost Center, 0=Entire House 4 CC_CODE C 5 Cost center code number CC### 5 SLS_TAXABL N 9 2 Sales---Taxable 6 SLS_TAXINC N 9 2 Sales---Tax Included 7 SLS_TAXEMT N 9 2 Sales---Tax Exempt 8 TAX_COLETD N 9 2 Tax Collected 9 TAX_OWED N 9 2 Tax owed Index: DATE

SHFTSLS.DBF This is daily sales totals by shift and cost center.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of this transaction 3 COST_CENTR N 2 Cost Center (0=Entire house) 4 CC_CODE C 5 Cost center code number "CC###" 5 SHIFT_CODE C 5 Shift code number "SH###" 6 SALESCT_01 N 9 2 Sales for category #1 ... ... ... 26 SALESCT_21 N 9 2 Sales for unknown category 27 TOT_SALES N 9 2 Total sales 28 VOID_SALES N 9 2 Total voids in dollars 29 VOID_COUNT N 9 2 Total number ov voids 30 DINE_TIME N 9 2 Total dining time in minutes 31 COVR_SALES N 9 2 Total cover sales 32 COVR_COUNT N 4 Total cover counts

27

33 COVR_CHKS N 4 Total cover checks 34 CHECKS N 4 Total number of checks 35 PARTY N 4 Total number in party 36 TAX_COLL_1 N 12 2 Tax collected, Tax 1 37 TAX_COLL_2 N 12 2 Tax collected, Tax 2 38 TAX_COLL_3 N 12 2 Tax collected, Tax 3 39 TAX_COLL_4 N 12 2 Tax collected, Tax 4 40 TAX_OWED_1 N 12 2 Tax owed, Tax 1 41 TAX_OWED_2 N 12 2 Tax owed, Tax 2 42 TAX_OWED_3 N 12 2 Tax owed, Tax 3 43 TAX_OWED_4 N 12 2 Tax owed, Tax 4 Index: DATE

USERS.DBF This lists system users (Not from Time and Attendance).

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 USER_NBR N 3 User Number 3 NAME_LAST C 15 Last Name 4 NAME_FIRST C 10 First Name 5 TYPE N 1 User Type 6 MAGCARD_ID N 4 Mag Card Number

VDUBUMP.DBF Lists VDU bump times as well as length of time between SEND and BUMP.

# Name Type Width Dec Usage 1 STORE C 4 Store number 2 DATE D 8 Date 3 DEVICE N 3 Device number where item was bumped from 4 SEND_TIME C 8 Time item was sent to VDU 5 BUMP_TIME C 8 Time order was bumped off the VDU 6 TIME_SEC N 5 Time in seconds between SEND and BUMP 7 SEND_TERM N 3 Terminal menu item was sent from 8 CHECK_NUM N 5 Check number, the check number of the order --- End POSIDBFW.EXE files.

28

PRODUCT MIX DBF FILES (PSNEWW)

PMNEWW.EXE produces two DBF files when run with the correct command line parameters. These two files are PMOUTPUT.DBF ( product mix output ) and SHOUTPUT.DBF ( sales history output ). Currently PMNEWW does not purge existing PMOUTPUT or SHOUTPUT files. Users will need to purge existing files, then run the command line parameters to produce new files. These DBF files can also be produce from within the program by choosing the FILE output button.

PMOUTPUT.DBF Product mix for the period desired. Must be setup in backoffice. # Name Type Width Dec Usage 1 STORE C 4 Store number 2 DATE D 8 Date 3 CAT_NUMBER C 6 Category number 4 TIME C 11 Time 5 ITEMS_SOLD N 10 2 Number of items sold 6 INGR_UNITS N 10 2 Ingredient units used 7 CAT_UNITS N 10 2 Category units 8 IT_SOLD_AV N 10 2 Item sold average 9 INGR_UN_AV N 10 2 Ingredient unit average 10 CAT_UN_AV N 10 2 Category unit average To produce the PMOUTPUT.DBF file the following command line parameters must be used with PMNEWW.EXE :

Command Line: PMNEWW C P R 0 0 YYYYYYYYYY YYYYNNNNNNNN 0 Fields:

PMNEWW - Program Name C - Command line mode P - Product Mix Report, S - Sales History Report R - Print Report , F - Create DBF File 0 - Number of Days Ago for Report

0 - Time Increment 0 - Period 1 - 1 Hour 2 - Half Hour 4 - Qtr of Hour YYYYYYYYYYYY - Weeks Selection Y or N 1 - 12 (depends on backoffice setup) YYYYNNNNNNNN - Day Parts Selection

0 - Category To Print ( 0 - All, or Num for Selected )

29

SHOUTPUT.DBF Sales History Report # Name Type Width Dec Usage 1 STORE C 4 Store Number 2 DATE D 8 Report Date 3 TIME C 11 Time Period 4 CHECKS N 10 Number of Checks in this Time Period 5 SALES N 10 2 Total Sales (same Period) 6 CHECKS_AVG N 10 1 Average Number of Checks (same Period) 7 SALES_AVG N 10 2 Average Total Sales (same Period)

Command Line to Run Product Mix Report:

PMNEWW C S R 0 0 YYYYYYYYYY YYYYNNNNNNNN YYYYYYYYY Fields: PMNEWW - Program Name C - Command line mode S - Sales History Report R - Print Report , F - Create DBF File 0 - Number of Days Ago for Report 0 - Time Increment 0 - Period 1 - 1 Hour 2 - Half Hour 4 - Qtr of Hour YYYYYYYYYY - Weeks Selection Y or N 1 - 12 (depend of setup) YYYYNNNNNNNN - Day Parts Selection

YYYYYYYYY - Cost Center Selection Y or N ----END PSNEWW SECTION

30

TADBF FILES

TADBFW32 produces four files, Labor.dbf, Labor2.dbf, Sched.dbf and Sched2.dbf. Each is explained in detail below. TADBFW32 USAGE TADBFW32 [/reset] or [/daily] or [/?] or [/DOIT] /reset to reset tadbf and reprocess the files for the last 14 days. /daily to process files days in the last two weeks that have not been processed

already. /DOIT will reset the flags in Daily.dbf and process daily files. This command Combines the /Reset and /Daily commands, rebuilding all files for the last 14 days. Previous data is removed. /ALT places files in the ALTDBF folder as defined in Setup > Payment > Sales

Journal > User Defined DBFs /SCHED produces SCHED.DBF and SCHED2.DBF for 2 and 3 weeks in advance.

LABOR.DBF This is a compilation of daily labor information by half hour and department. Person

hours are such that if a single person works for one of the half hour periods, the value in HOURS will be 0.5.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of this transaction 3 PR_DATE D 8 Payroll date for this data 4 DEPT N 2 Labor department 1 - 20 5 HOUR N 2 Half hour period 1 - 48 6 DOLLARS N 8 2 Labor Dollars 7 HOURS N 6 2 Person Hours Index: DATE

LABOR2.DBF This is a compilation of daily labor information by 15 minutes and job/department. Person

hours are such that if a single person works for one of the quarter hour periods, the value in HOURS will be 0.25.

# Name Type Width Dec Usage 1 STORE C 4 Restaurant chain Store number 2 DATE D 8 Date of this transaction 3 PR_DATE D 8 Payroll date for this data 4 DEPT N 2 Labor department 1 - 20 5 JOB N 3 Job 1 - 100 6 HOUR N 2 Quarter hour period 1 - 96 7 DOLLARS N 8 2 Labor Dollars 8 HOURS N 6 2 Person Hours Index: DATE

31

SCHED.DBF Schedule information aggregated by day and time period in hours and dollars.

# Name Type Width Dec Usage 1 STORE C 4 Store 2 DATE D 8 Date 3 PR_DATE D 8 Date entry 4 DEPT N 2 Deptartment 5 HOUR N 2 Half hour marker, by the half hour 1 - 48 6 DOLLARS N 8 2 Scheduled dollars for the period 7 HOURS N 6 2 Scheduled hours for the period

SCHED2.DBF Schedule information aggregated by day and time period in hours and dollars.

# Name Type Width Dec Usage 1 STORE C 4 Store 2 DATE D 8 Date 3 PR_DATE D 8 Date entry 4 DEPT N 2 Department 5 JOB N 3 Job 6 HOUR N 2 Quarter hour marker, 1 - 96 7 DOLLARS N 8 2 Dollars 8 HOURS N 6 2 Hours ---- End TADBFW32 Section

12/09/06

TAW DBF Files

The following files can be produced by running the command TAW EXPORT in the \SC folder of the POS Driver. The following files are placed in the \sc folder of the POS Driver.

When using the TAW EXPORT command, only those employees who are active will be added to the EMPFILE.DBF file. To include ALL employees, including inactive employees, use the TAW EXPORTALL.

Command Options : TAW EXPORT - Creates files listed below for active employees TAW EXPORTALL - Creates files listed below for all ( including inactive ) employees TAW [export/ exportall ] [/ALT] [/DBF] - The /ALT and /DBF commands place the output files into the /DBF folder or the /ALT folder as defined in Setup > Payment > Sales Journal > User DBF files TAW [export/ exportall] [PATH] - where PATH may be a user defined path, for example, C:\Temp. Users should use extreme caution with this parameter and NEVER export to C:\SC or L:\SC, as Schedule.DBF and Schedule.CDX will be overwritten.

33

EMPFILE.DBF Displays employee data from the employees file. EMPFILE.DBF lists Active employees

only, by default. To list ACTIVE EMPLOYEES and the TEMPLATES in Time & Attendance, turn on the flag in Setup > Time & Attendance > Options > Show Templates in New Scheduler

When using the TAW EXPORT command, only those employees who are active will be added to the EMPFILE.DBF file. To include ALL employees, including inactive employees, use the TAW EXPORTALL.

# Name Type Width Dec Usage 1 EMP_NUMBER N 8 Employees Number 2 LAST_NAME C 20 Employees Last Name 3 FIRST_NAME C 15 Employees First Name 4 BASE_PAY N 8 2 Employees Salary Field 5 WAGE_TYPE C 1 Wage Type, H = Hourly, S = Salary, N = Salary, not on Reports 6 PAY_PERIOD C 1 Pay period. W = Weekly, B = Biweekly, S = Semi Monthly ( every 15 days ), M = Monthly, O = Always pay base salary 7 ENFORC_SCH C 1 Y = YES, N = NO 8 EMP_TYPE C 1 R = Regular, S = Select Alternate Job, M = Manager 9 EMP_STATUS C 1 F = Active, I = Inactive 10 ADDRESS_1 C 30 Address # 1 11 ADDRESS_2 C 30 Address # 2 12 ADDRESS_3 C 30 Address # 3 13 PHONE C 10 Phone Number 14 SOC_SEC C 11 Social Security Number 15 CARD_NUM N 8 Magnetic Card Number 16 POS_CARD C 9 Magnetic Card Number are these ever different? 17 POS_TYPE N 3 18 ALT_NUM C 9 Alternate Employee Number 19 POOL_CODE N 2 Tip Pool Code Number, see Setup > Payment > Tips > Tip Pool % 20 DATE_HIRED D 8 Date hired 21 DATE_LEFT D 8 Date employee left employment 22 CITY C 20 City 23 STATE C 2 State 24 ZIP C 5 Zip Code 25 DATE_BIRTH D 8 Date of Birth 26 MIDDLE_INT C 1 Middle Initial 27 SEX C 1 Sex 28 MARITAL_ST C 1 Marital Status 29 RACE N 2 Race 30 TERM_REASN N 2 Termination Reason 31 EXEMPTION N 2 Number of exemptions claimed 32 Zip_Six C 6 Populated if the six digit zip code option is on

34

JOBFILE.DBF Displays employees job data.

# Name Type Width Dec Usage 1 EMP_NUMBER N 4 Employee Number 2 JOB_CODE N 4 Job Code Number see JOBLIST.DBF for codes 3 PRIME_JOB L 1 Primary Job, Logical 4 RATE N 10 3 Rate of pay 5 Active_job L 1 Job is active ? Y = Yes, N = No JOBLIST.DBF

List the various jobs setup in Setup > Time & Attendance > BOH > Deprtments & Jobs.

# Name Type Width Dec Usage 1 JOB_CODE N 4 Job Code Number 2 JOB_NAME C 20 Job Name as Setup in Time & Attendance 3 DEPT_CODE N 4 Department Code ( optional ) 4 JOB_DESC C 50 Job Description, Name 5 ALT_CODE C 15 Alternate Job Code 6 NO_OUT_TM L 1 No Out Time Displayed on Printed Schedule, Logical

SALEPRED.DBF Lists the sales predictions for a period of time, by date.

# Name Type Width Dec Usage 1 WEEK_DESC C 10 Week Descriptor, 3 Options Are: This Week, Last Week, Next Week 2 WEEK_END D 8 Week Ending Date ( MM/DD/YYYY ) 3 PRED_DATE D 8 Prediction Date, Single Day ( MM/DD/YYYY ) 4 PRED_SALE N 14 2 Sales Amount Prediction for the PRED_DATE

SCHOVR.DBF Lists the sales predictions for a period of time, by date. This file relates to Setup > Time &

Attendance > Backoffice > Payroll & Overtime > Overtime Rules.

# Name Type Width Dec Usage 1 OVR_TYPE N 2 A number ranging from 1 - 3 1 Max Hours/ Day, may contain two records for #1. Column 1 represented by first record Column 2 represented by second record 2 Max Hours/ Week 3 Max Hours/ 7th. Day ** No entry for Max Hours /6th. Day ** 2 OVR_HOURS N 3 # of hours to work before Overtime begins 3 OVR_RATE N 4 2 Overtime rate

35

SCHSETUP.DBF Various fields used for the Labor Scheduler.

# Name Type Width Dec Usage 1 STORE_NUM C 4 Store number, populated from the file \DBF\LAYOUT.DBF 2 STORE_NAME C 25 Store name 3 SCH_VERSN N 4 Scheduler version in TAW, not the Advanced Labor Scheduler 4 LAST_WEEK D 8 Start Date for Last Week 5 CURR_WEEK D 8 Start Date for Current Week 6 NEXT_WEEK D 8 Start Date for Next Week 7 START_DAY D 8 Start Date for this weeks schedule 8 NUM_SHIFTS N 1 Number of shifts as defined in Setup > Time & Attendance > Backoffice Setup > Work Shifts 9 STARTSHFT1 C 7 Start time for shift 1 10 STARTSHFT2 C 7 Start time for shift 2 11 STARTSHFT3 C 7 Start time for shift 3 12 STARTSHFT4 C 7 Start time for shift 4 13 STARTSHFT5 C 7 Start time for shift 5 14 REGWEEKSTR C 24 String for Regular Week text ( Regular )

SCHSHIFT.DBF Schedule shifts.

# Name Type Width Dec Usage 1 SHIFT_CODE N 4 Shift code number, range is 101 - 250 2 SHIFT_NAME C 20 Custom name for the shift 3 SHIFT_ABBR C 5 Abbreviation for SHIFT_CODE, currently unused 4 JOB_CODE N 4 Job Code number 5 BEG_TIME N 4 Start time for the shift 6 END_TIME N 4 End time for the shift

DEPTFILE.DBF Schedule shifts.

# Name Type Width Dec Usage 1 EMP_NUMBER N 4 Employee number 2 DEPT_CODE N 4 Department number for employee. If the employee has multiple departments ( as defined in Setup > Time & Attendance > Backoffice Setup > Department and Jobs ), then the employee is listed more than once, with each department listed once.

36

DEPTLIST.DBF Schedule shifts.

# Name Type Width Dec Usage 1 DEPT_CODE N 4 Department Number, as defined in Setup > Time & Attendance > Backoffice Setup > Department & Jobs 2 DEPT_NAME C 20 Name of the deaprtment 3 DEPT_DESC C 50 Currently, unused 4 LOCAT_CODE N 4 Currently, unused ---- End TAW EXPORT Section

37

Tarw.exe

The following three files contain all the payroll information for a period and can be used to retrieve information regarding payroll information. The three files are PAYRPUNC.dbf, PAYRJOBD.dbf and PAYRHEAD.dbf. Payrhead.dbf contains a summary of an employees payroll information and summarizes payrjobd.dbf. Payrjob.dbf in turns is a summary of payrpunc.dbf which contains records of each punch for an employee. The diagram below shows the flow of information and each file is explained in more detail on the next page.

Store Empl_num Job Dept Pay_type Hours Rate Pay Tips_decl Srvr sales

Store Date_start Date_end Empl_num Empl_alt Empl_nameEmpl_ssecWage_typeHrs_reg Hrs_ovrdayHrs_ovrwk

Store Empl_num Job Dept Date Time_in Time_out Punch_type Adju_reasn Adju mgr

Store Empl_num Job Dept Date Time_in Time_out Punch_type Adju_reasn Adju mgr

Store Empl_num Job Dept Date Time_in Time_out Punch_typeAdju_reasn Adju mgr

PAYRPUNC.dbf one record per punch

Store Empl_num Job Dept Pay_type Hours Rate Pay Tips_decl Srvr sales

Employee As Punches for Job 1 Employee As Punches for Job 2

PAYRJOBD.dbf sums employee payroll info by Job

PAYRHEAD.dbf one record per employee, sums all hours and wages, not all fields shown here.

Store Empl_num Job Dept Date Time_in Time_out Punch_typeAdju_reasn Adju mgr

Job 1 Summary

Job 2 Summary

38

The PAYRPUNC.DBF file contains data for each employees punch in/out. Each punch is recorded, along with the department, job and rate for that punch in/out. Additionally, these records reflect any adjustments performed on those punches. Each record in this file is a punch in/ punch out. This is similar to looking at the detail of an employees time card.

The PAYRJOBD.DBF in turn, sums up the hours and lists each employees payroll summary by job. Each record in the file is one job held by that employee. For instance, if an employee has two jobs, each job will be a different record, summing up the hours worked for that job. This file is similar to viewing payroll information By Employee, then by Department and Job.

Finally, PAYRHEAD.DBF combines all hours and jobs an employee worked and reports the total hours worked for an employee, along with their payroll information ( social security number, alternate number, ect ) - in one record per employee. This is similar to viewing payroll as : Summary by Employee.

In short, PAYRPUNC is summed up in PAYRJOBD, which in turn is summed up in PAYRHEAD.DBF TARW can be called with a parameters of 52 ( exclude open punches ) or 93 ( include open punches ) to produce the following DBF files. The commands are:

TARW R 52 N2 [N3] [N4] [/APPEND] [/ALT] ( Exclude Open Punches ) TARW R 93 N2 [N3] [N4] [/APPEND] [/ALT] ( Include Open Punches, requires TARW.EXE dated 10/21/05 or later ) N2 - :

1 - report for a day: 2 - report for a week:

3 - report for two weeks: 4 - report for an arbitrary period:

If N2 = 1: N3 - how many days ago from the system date.

If N2 = 2 or 3: N3 - how many weeks ago from the system date.

If N2 = 4: N3 - start date N4 - end date.

Format for N3 and N4: year, month, day ( Asian format ). For example: 950901 - September 1, 1995

Notice: 1. Period cannot be more than 31 days; 2. N3 must be earlier than or equal to N4; 3. both dates must be earlier than or equal to the system date. /APPEND Adds the newly produced file to the existing DBF file. The Absence of the /APPEND command, causes TARW to create a new File, and deletes the existing file before creating a new DBF file.

/ALT Places the output files into \ALTDBF, or if Backoffice Setup > Payment > User DBFs is populated, writes to the specified directory

39

PAYRHEAD.DBF Contains all hours and jobs an employee worked and reports the total hours worked for an

employee, along with their payroll information ( social security number, alternate number, ect ) - in one record per employee.

# Name Type Width Dec Usage 1 STORE C 4 Store number 2 DATE_START D 8 Start date for report 3 DATE_END D 8 End date for report 4 EMPL_NUM N 8 Employee number 5 EMPL_ALT C 9 Alternate employee number 6 EMPL_NAME C 35 Employee name 7 EMPL_SSEC C 11 Employee social security number 8 WAGE_TYPE C 1 Wage type ( Hourly, salary ) 9 HRS_REG N 8 4 Regular hours worked 10 HRS_OVRDAY N 8 4 Max # of hours/day before considering it overtime 11 HRS_OVRWK N 8 4 Max # of hours/week before considering it overtime 12 HRS_HOLIDA N 8 4 Holiday pay hours 13 HRS_DIFF N 8 4 Shift differential hours 14 HRS_ADJUST N 8 4 Hours adjusted 15 TOTAL_PAY N 9 2 Total pay 16 TIPS_DECL N 9 2 Declared tips 17 TIPS_ADJU N 9 2 Adjusted tips 18 TIPS_CHRG N 9 2 Charged tips 19 TIPS_POOL N 9 2 Tip pool amount 20 SRVR_SALES N 9 2 Server sales 21 HRS_OVRD2 N 8 4 Max hrs/ day column 2 ( California ) in Overtime 22 HRS_OVRWK2 N 8 4 Max hrs /week colmn. 2 ( Californai ) in Overtime 23 HRS_OVRSV N 8 4 Max # of hours on day 7 to consider it overtime 24 HRS_OVRSV2 N 8 4 Max # of hrs on day 7, column 2 ( California O/T ) 25 HRS_OVR6D N 8 4 Max # of hours on day 6 to consider it overtime 26 HRS_OVR6D2 N 8 4 Max # of hours, day 6, column 2, ( California O/T )

WAGE_TYPE H-Hourly, S-Salary, N Salary, not on report. TIPS_DECL - Total declared tips for period for all jobs.

40

PAYRJOBD.DBF Contains payment amounts by job/ department.

# Name Type Width Dec Usage 1 STORE C 4 Store number 2 EMPL_NUM N 8 Employee number 3 JOB C 16 Job code ( number ), as defined in Setup > Time & Attendance > Backoffice Setup > Dept & Jobs. See JOBLIST.DBF for links to the job numbers and job names. 4 DEPT N 4 Jobs department 5 PAY_TYPE N 2 Type of pay 6 HOURS N 8 4 Number of hours worked for department 7 RATE N 7 3 Rate of pay 8 PAY N 7 2 Pay amount 9 TIPS_DECL N 9 2 Declared tips 10 SRVR_SALES N 9 2 Server sales total 11 DATE_START D 8 Start date for report 12 DATE_END D 8 End date for report 13 BASE_RATE N 7 3 Base rate, may differ from RATE, when employee Enters into overtime hours. Rate would be the overtime Rate, while BASE RATE would be the non-overtime rate.

PAY_TYPE - POSitouch categorizes pay into categories such as Regular, Overtime-Day and Overtime-Week.

POSitouch computes overtime based on cumulative hours per day or week. For example if an employee hits 40 hours in the middle of Thursday's work period then they are paid regular pay until the minute they hit 40 and week-overtime thereafter regardless of whether they work a variety of jobs. Pay type 8 is used for additional daily overtime e.g. double pay after 12 hours. Pay types 10, 11 are similar to Overtime-Day but only for 7 day weeks.

Field Values: 1 - Regular & Salaried 2 - Overtime-Day 3 - Overtime-Week 4 - Miscellaneous Pay 5 - Shift Differential 6 - Holiday Pay 7 - Previous Period Adjustment 8 - Overtime-Day 2 9 - Overtime-Week 2 (not used) 10 - Overtime-7th Day of week 11 - Overtime-7th Day of week 2

41

PAYRPUNC.DBF Contains payment amounts by job/ department. Note : When including open punches, the TIME_OUT field is populated with the time the file was produce, enabling wage calculations on open punches.

# Name Type Width Dec Usage 1 STORE C 4 Store 2 EMPL_NUM N 8 employee number 3 JOB C 16 Job code ( number ), as defined in Setup > Time & Attendance > Backoffice Setup > Dept & Jobs. See JOBLIST.DBF for links to the job numbers and job names. 4 DEPT N 4 Punch department 5 DATE D 8 Punch date 6 TIME_IN C 6 Punch in time 7 TIME_OUT C 6 Punch out time 8 PUNCH_TYPE N 4 Type of punch See table below 9 ADJU_REASN N 2 Adjusted punch reason 10 ADJU_MGR N 5 Manager responsible for adjustment 11 JOB_WAS_CH L 1 Logical, was job changed? 12 SCH_OVERR L 1 Schedule Overridden ? 13 IN_EARLY L 1 Logical, Employee in early ? 14 IN_LATE L 1 Logical, Employee in late ? 15 OUT_EARLY L 1 Logical, Employee out early ? 16 OUT_LATE L 1 Logical, Employee out late ? 17 OUT_OF_SCH L 1 Logical, Off schedule ? 18 MGR_PNC_IN L 1 Logical, Manager punched in Employee ? 19 MGR_PNC_OU L 1 Logical, Manager punched Employee out ? 20 BACKOF_ADJ L 1 Logical, Backoffice adjustment ? 21 DATE_START D 8 Start date for period 22 DATE_END D 8 Ending date for period 23 ON_CLOCK L 1 Is employee still punched in ?

Punch Type ( next page )

42

PAYPUNC.DBF Punch Types 1 - Regular punch - from clock 2 - Deleted Punch - from clock, deleted later 3 - Adjustment - created through adjustment process. In punch is always adjustment but Out punch may have come from time clock. 4 Previous Period Adjustment - Adds to pay for this period, but does not figure into overtime calculations.

5 Shift differential pay adjustments for working same position on a different shift 6 Holidays 7 Previous Adjustments - Adds to pay for this period but does not figure in overtime calculations. 8 Breaks

43

Hrslsavg.exe

The HRSLSAVG program creates DBF files containing sales based on hour, customer counts, sales, productivity units or transaction counts. HRSLSAVG builds a 7 day rolling average for the files listed below, based on 10 weeks of data. Files are located in the \Forecast directory off the root of the POSdriver.

HRSLSAVG.DBF Contains sales information, broken down by day of the week, by hour, into 15 minute

intervals. 15 minute intervals are noted on the 00, 15, 30 and 45 minute marks.

# Name Type Width Dec Usage 1 STORE C 4 Store number 2 DATE D 8 Date of the sales ( MM/DD/YY ) 3 DAY_OF_WK N 1 Numeric representation of the day of the week. Sunday = 1 4 HOUR N 2 Hour of the day. Zero ( 0 ) is midnight. 5 MINUTS N 2 Sales noted on the 15 minute mark. Values = 00/15/30/45 6 AMOUNT N 9 2 Dollar value for 15 minutes. Other hourly sales DBF files are available. These files contain hourly sales for each cost center, and are created by default when HRSLSAVG is run. The naming format for these files resemble HRSLSxx.DBF, where XX is the cost center number. Examples include the following for cost centers 1 and 2 : HRSLS01.DBF, HRSLS02.DBF

HRTRNAVG.DBF Contains number of transactions, broken down by day of the week, by hour, into 15 minute

intervals. 15 minute intervals are noted on the 00, 15, 30 and 45 minute marks.

# Name Type Width Dec Usage 1 STORE C 4 Store number 2 DATE D 8 Date of the sales ( MM/DD/YY ) 3 DAY_OF_WK N 1 Numeric representation of the day of the week. Sunday = 1 4 HOUR N 2 Hour of the day. Zero ( 0 ) is midnight. 5 MINUTS N 2 Noted on the 15 minute mark. Values = 00/15/30/45 6 AMOUNT N 9 2 Unit value for 15 minutes. Other hourly transaction DBF files are available. These files contain the number of transactions for each cost center, and are created by default when HRSLSAVG is run. The naming format for these files resemble HRTRNxx.DBF, where XX is the cost center number. Examples include the following for cost centers 1 and 2 : HRTRN01.DBF, HRTRN02.DBF

44

HRCSTAVG.DBF Contains customer counts, broken down by day of the week, by hour, into 15 minute

intervals. 15 minute intervals are noted on the 00, 15, 30 and 45 minute marks. Denoted from Number in party when a new table is opened.

# Name Type Width Dec Usage 1 STORE C 4 Store number 2 DATE D 8 Date of the sales ( MM/DD/YY ) 3 DAY_OF_WK N 1 Numeric representation of the day of the week. Sunday = 1 4 HOUR N 2 Hour of the day. Zero ( 0 ) is midnight. 5 MINUTS N 2 Counts noted on the 15 minute mark. Values = 00/15/30/45 6 AMOUNT N 9 2 Customer counts for 15 minute period. Other hourly customer count DBF files are available. These files contain average customer counts for each cost center, and are created by default when HRSLSAVG is run. The naming format for these files resemble HRCSTxx.DBF, where XX is the cost center number. Examples include the following for cost centers 1 and 2 : HRCST01.DBF, HRCST02.DBF

HRCOVAVG.DBF Contains number of covers, broken down by day of the week, by hour, into 15 minute

intervals. 15 minute intervals are noted on the 00, 15, 30 and 45 minute marks. Denoted from Count as cover in the Backoffice > Menu Editor > Prep printers > prep Category names > Count As Cover.

# Name Type Width Dec Usage 1 STORE C 4 Store number 2 DATE D 8 Date of the sales ( MM/DD/YY ) 3 DAY_OF_WK N 1 Numeric representation of the day of the week. Sunday = 1 4 HOUR N 2 Hour of the day. Zero ( 0 ) is midnight. 5 MINUTS N 2 Counts noted on the 15 minute mark. Values = 00/15/30/45 6 AMOUNT N 9 2 Cover counts for 15 minute period. Other cover count DBF files are available. These files contain the number of covers for each cost center, and are created by default when HRSLSAVG is run. The naming format for these files resemble HRCOVxx.DBF, where XX is the cost center number. Examples include the following for cost centers 1 and 2 : HRCOV01.DBF, HRCOV02.DBF

45

HRPRDAVG.DBF This file reflects the number of productivity units required during a given period.

POSitouch allows users to set a Productivity number within a menu item. This number reflects a number of labor units required to produce an item. For instance, items that are prepared quickly would have a lower productivity number, while harder to prepare items would have a higher number. Examples of this would be a soda menu item with a productivity unit of 1, while an entre would have a higher productivity number of 5.

By using the productivity feature, users can schedule based on the average number of productivity unit ( or labor units ) required throughout the day.

# Name Type Width Dec Usage 1 STORE C 4 Store number 2 DATE D 8 Date of the sales ( MM/DD/YY ) 3 DAY_OF_WK N 1 Numeric representation of the day of the week. Sunday = 1 4 HOUR N 2 Hour of the day. Zero ( 0 ) is midnight. 5 MINUTS N 2 Counts noted on the 15 minute mark. Values = 00/15/30/45 6 AMOUNT N 9 2 Productivity units for a 15 minute period. Other productivity DBF files are available. These files contain the number of productivity units for each cost center, and are created by default when HRSLSAVG is run. The naming format for these files resemble HRPRDxx.DBF, where XX is the cost center number. Examples include the following for cost centers 1 and 2 : HRPRD01.DBF, HRPRD02.DBF Note : To produce the file HRPVDAVG.DBF, users must setup the option in Backoffice Setup > Restaurant Misc. Data > System 2 > Labor Schedule Productivity Measure in Price XX. Where XX is a number from 1 to 10. Users then go to the menu items and enter a productivity number in one of the 10 price fields referred to in the above setting. If XX above, is set to Price Level 4, then the PRICE 4 field for any menu item will be used as the productivity unit field. HOW TO PRODUCE ( all files ) The program HRSLSAVG.exe builds a rolling 7-day forecast of sales; cover counts, customer counts and item sales for the entire house and each individual cost center by 15 minute increments. This program runs as part of nightly processing, and defaults to averaging data for a 10-week period. If 10 weeks is not considered reasonable you can alter this default setting by changing the setting in the Backoffice Setup > Payment > Sales Journal > Standard DBFs > HRSLSAVG weeks to track.

Additionally, if using batch files for processing, adding a command line parameter allows users to run HRSLSAVG with a custom set number of weeks to process.

For example, running Hrslsavg to get a 4-week average would look like this: Hrslsavg 4

46

Hrslsavg has a default setting to include any negative items or over-rings in the averages. You have the ability to change this through an ini file if you want your forecasting data to ignore negative items. Create an HRSLSAVG.INI file, in the \SC folder : [Sales] ExcludeNegativeItems=YES

ExcludeOverrings=YES

47

CHKTODBF FILES

CHKTODBF makes it easy to create and maintain custom reports and DSRs from Positouch data, by producing an relational database of DBF tables. The tables can be read using FoxPro, Access, Delphi, Excel, and many other database manager and spreadsheet programs. The user can specify a date or range of dates for checkfiles to process. Each checkfile is read and the information contained in it is added to the database. CHKTODBF Usage

Usage: CHKTODBF [Period] [Offset] [Offset2] [/nocat] [/CLEAR] [/ALT] [/LOC-] - OR - CHKTODBF [mm/dd/yy] [/nocat] [/CLEAR] [/ALT]

Period specifies the unit of time used to decide which checkfiles to read.

Parameter Meaning Action 1 day Process a single days checkfile 2 week Process checkfiles for an entire week 3 month Process checkfiles for an entire month 4 arbitrary number of days Process checkfiles for a specified range of

days

Note: Due to the size of the database produced, we do not recommend processing an entire month except under special circumstances.

Offset specifies the number of days/weeks/months previous to today for the report, or of

start of arbitrary period. 0 (zero) will process records for the current day, week or month, 1 for the previous day, week or month, etc.

Offset2 is used only for Arbitrary Periods. It defines the # days previous to today for end

of arbitrary period

mm/dd/yy - Use this date format to process the checkfile for the date specified.

/nocat tells CHKTODBF not to create the category sales file (CATSALES.DBF). By default,

CHKTODBF creates Catsales every time it runs. Catsales does not use information from checkfiles. It only needs to be updated when items are added to inventory or the sales category setup is changed. You can use the nocat switch to speed up processing when Catsales does not need to be updated.

/CLEAR tells CHKTODBF to clear out the target directory before creating files. This

prevents appending the files to the existing DBF files in that location.

/ALT tells CHKTODBF to create dbf files in the alternative directory set up in Setup-Payment-Sales Journal-Users DBF Files. Enter a path in DBF primary path and DBF alternate path. If there is no entry in DBF primary path, it defaults to \DBF, a blank \ALT path, defaults writing files to the \ALTDBF folder.

/LOC- runs CHKTODBF and places the output DBF files into the specified directory. If the directory contains spaces in the name, then the entire parameter should be

enclosed in quotes. For example, CHKTODBF 2 2 /LOC-C:\test dbf folder\. For directories without spaces in the name, quotes are not required. For example, CHKTODBF 2 2 /loc-c:\testdbf\. Note that a hyphen is required

48

between LOC and the directory path.

Directories Note that if the DBF directories under Setup > Payment > Sales Journal > User DBFs are left

blank, the default Primary Directory will be \DBF and the Alternate Directory will be \ALTDBF. When defining a directory other than the default, users should NOT enter a driver letter as part of the path. Logging Capabilities - See Appendix A

CHKTODBF writes a log file of activites when run. The log file is named PDmmddyy.LOG, where mmddyy is the month, day, year when the program was run. If CHKTODBF is called without parameters, it defaults to the shutdown date (the date of

the most recently completed checkfile). Examples: CHKTODBF 1 3 Creates DBF files from a checkfile dated 3 days ago. CHKTODBF 2 1 Creates DBF files from all checkfiles from last week. CHKTODBF 4 9 3 Creates DBF files from all checkfiles between nine

days ago and three days ago. CHKTODBF 4 1 0 Creates DBF files from checkfiles from yesterday

and today. CHKTODBF Creates DBF files from the most recently

completed checkfile, also creates catsales.dbf.

CHKTODBF /nocat Creates DBF files from the most recently completed checkfile, but doesnt create catsales.dbf.

Users who create DSRs utilizing CHKTODBF can integrate the program into their batch files in the following ways:

From nightly.bat to update the CHKTODBF database every night.

or From Dsr.bat - so that the DSR can call CHKTODBF on an as needed basis.

49

THE CHKTODBF DATABASE

Transact.dbf is at the top of the CHKTODBF database. It contains a record for every transaction recorded in the checkfile. Transactions can be checks, payments, manager transactions, or cashouts (zero records), so each record in Transact will have a corresponding record in Check, Payment, Mgr_Tran, or Zerorec. A Check record is produced for each check in the checkfile. Each Check record will have one or more Mainitem records and zero or more Taxes records. Taxes records are created for each tax type applied to a check, so one Check record could have multiple Taxes records. Option records will be created for each option associated with a main item. An option record (in options.dbf) can be linked to its parent main item (in mainitem.dbf) by matching the DATE, TRANS_NO, CHECK_NO and SEQ_MAIN fields from the two tables. Each Payment record has at least one payitem record. If more than one pay type is used (e.g. part of the check is paid with credit card and part with cash) there will be multiple Payitem records for the Payment record. Paymemo records are only created if there is a memo attached to a particular payment. A Payitem record can not have more than one Paymemo records. Zerorec contains a record for each end-of-shift cashout. Mgr_Tran contains manager transaction records. If the manager transaction is a paidout or overring, there will be a corresponding record in Payitem and Paymemo. Catsales is a cross-reference between inventory numbers and category numbers. Each option should match one Catsales record. This is the structure of the CHKTODBF database:

Each box represents a table. The name of the table is at the top of the box.; the remaining items are the field names.

50

Files Created by CHKTODBF

CHECK.DBF Contains a record for each check.

# Name Type Width Dec Usage 1 DATE D 8 Date 2 TRANS_NO N 5 Transaction number 3 CHECK_NO N 5 Check number 4 START_TIME N 4 Start time 5 PRINT_TIME N 4 Print time 6 TABLE_NO N 4 Table number 7 COSTCENTER N 3 Cost center 8 STATION_NO N 3 Station number 9 SERVER_NO N 4 Server number 10 SERVER_CHK N 4 Server check number 11 NO_IN_PRTY N 4 Number in party 12 AMOUNT N 10 2 Dollar amount of check 13 TAX_TOTAL N 10 2 Tax Total 14 DISC_PRINT N 10 2 Printed discount total 15 DISC_TYPE N 2 Discount type 16 DISC_ODLR N 10 2 Open dollar discount, dollar amount 17 DISC_OPCT N 10 2 Open percent discount, discount percent 18 DISC_SUBTR L 1 Logical, discount subtracts from sales 19 OVERRING L 1 Logical, Overring check? True or false 20 DISC_MNGR N 6 Manager who applied discount

DATE.DBF Contains a record for each check.

# Name Type Width Dec Usage 1 PROC_DATE D 8 Process date if run for particular date(s)

MAINITEM.DBF Contains a record for each check item defined as a main item. # Name Type Width Dec Usage 1 DATE D 8 Date 2 TRANS_NO N 5 Transaction number 3 CHECK_NO N 5 Check number 4 SEQ_MAIN N 3 Sequence number 5 INV_NUMBER N 5 Inventory number 6 DISC_NBR N 2 Discount number 7 TAX1FLAG L 1 Logical, tax 1 applies 8 TAX2FLAG L 1 Logical, tax 2 applies 9 TAX3FLAG L 1 Logical, tax 3 applies 10 TAX4FLAG L 1 Logical, tax 4 applies 11 TAXCODE N 2 Tax code 12 MULTIPLIER N 10 2 Quantity of items sold 13 DELETION N 2 0 if not deleted, 1-10 deletion reasons 14 DELETION_U N 3 User who deleted item

51

15 COVER L 1 Number of covers 16 FULLPRICE N 10 2 Full price amount 17 REALPRICE N 10 2 Price net of discount, void, tax included 18 DISC_AMT N 10 2 Item discount amount 19 TAX_INC_1 N 10 2 If tax included, amount 20 TAX_INC_2 N 10 2 If tax included, amount 21 TAX_INC_3 N 10 2 If tax included, amount 22 TAX_INC_4 N 10 2 If tax included, amount 23 COMP L 1 This item is a comp 24 COMP_APPL L 1 This item had a comp applied to it 25 COUP_APPL L 1 This item had a coupon applied to it 26 SEND_TIME N 4 Time sent to prep 27 COMP_USER N 3 User who applied Comp

MGR_TRAN.DBF Manager transactions. # Name Type Width Dec Usage 1 DATE D 8 Date 2 TRANS_NO N 5 Transaction number 3 TYPE N 5 Type ( see below ) 4 MGR_TRN_NO N 5 Manager transaction number 5 USER N 3 User number 6 TABLE_NO N 6 table number 7 CHECK N 7 Check number 8 AMOUNT_1 N 10 2 See Appendix A for field definitions 9 AMOUNT_2 N 10 2 10 MISC_1 N 8 11 MISC_2 N 8 12 CODE_1 N 8 13 CODE_2 N 8 14 TIME N 4

OPTIONS.DBF Contains a record for each option in the check.

# Name Type Width Dec Usage 1 DATE D 8 3 Date 2 TRANS_NO N 5 Transaction number 3 CHECK_NO N 5 Check number 4 SEQ_MAIN N 3 Sequence number 5 INV_NUMBER N 5 Inventory number

NOTFOUND.DBF Contains a list of check files not found for processing

# Name Type Width Dec Usage 1 PROC_DATE D 8 Date 2 FILE_NAME C 15 Name of file not processed

52

PAYITEM.DBF Contains a record for each payment line.

# Name Type Width Dec Usage 1 DATE D 8 Date 2 TRANS_NO N 5 Transaction number 3 PAY_ITM_NO N 2 Payment sequence number with multiple pay types 4 Pay_type N 2 Payment type number ( See below ) 5 MGR_TRN_NO N 5 Manager transaction number ( if applicable ) 6 AMOUNT N 10 2 Check amount 7 TIP N 10 2 Tip amount 8 CASH_PDOUT N 10 2 Cash paid out, i.e. change 9 ISSUE N 10 2 Gift cert issue amount

PAY_TYPE field: Type of Payment record: 0 Cash 1 - 19 User Definable - See Setup-Payment-Forms of Payment 20 Non-Payment - Checks not setup for payment at any station - rare,

usually an error in setup 21 Manager Discount - 100% - before version 4.57 22 - 25 User Definable Discounts before version 4.57 26 Manager Paidout - This record will occur without records 1-5. Paidout type is first byte of memo (see record type 7 below).

27 Training Amount - This record will occur without records 1-5. 28 43 User Definable Discounts - As of Version 4.57

PAYMEMO.DBF Contains a record for each memo field used in payments

# Name Type Width Dec Usage 1 DATE D 8 Date 2 TRANS_NO N 5 Transaction number 3 PAY_ITM_NO N 2 Shows which pay item the memo belongs to 4 PAY_TYPE N 2 Payment type 5 MGR_TRN_NO N 5 Manager transaction number 6 MEMO_TYPE C 8 Memo type ( see below ) 7 MEMO C 50 Memo text

Memo Types CREDCARD Credit Card MGRPAID Manager Paidout CLUBCHRG Club Charge CLUBREF Club Reference (no charge made to club account) ROOMCHG Room Charge GIFTCERT Gift Certificate OTHER None of the above

53

PAYMENT.DBF Contains a record for each payment header.

# Name Type Width Dec Usage 1 DATE D 8 Date 2 TRANS_NO N 5 Transaction number 3 CHECK_NO N 5 Check number 4 SERVER_CHK N 4 Server check number 5 STATION_NO N 3 Station number 6 SERVER_NO N 3 Server number 7 CASHIER N 3 Cashier 8 TERM_NO N 2 Terminal number 9 DRAWER_NO N 2 Drawer number 10 TIME_PAID N 4 Time check paid

TAXES.DBF Reports taxes on each check. Reports only taxes setup with an amount greater than 0 in

Setup > Taxes > Tax Rates 1 - 4.

# Name Type Width Dec Usage 1 DATE D 8 Date 2 TRANS_NO N 5 Transaction number 3 CHECK_NO N 5 Check number 4 TAXCODE N 2 Values are 1 and 2. 2 if tax included, otherwise 1. 5 TAX_NO N 1 Tax rate 1 - 4. Starts as 0. Possible values : 0,1,2,3 6 TOTAL_TAX C 10 2 Total tax 7 PRINT_TAX C 10 2 Tax printed on check

TRANSACT.DBF This contains a record for each transaction recorded in the checkfile. Transactions may

be checks, payments, or cashouts.

# Name Type Width Dec Usage 1 DATE D 8 Date of transaction 2 TRANS_NO N 5 Transaction number

ZEROREC.DBF Contains the cashout zero records from the checkfile.

# Name Type Width Dec Usage 1 DATE D 8 Date 2 TRANS_NO N 5 Transaction number 3 TIME N 5 Time of cashout 4 CASHIER N 3 Cashier 5 TERM_NO N 2 Terminal number 6 CASHOUT_TYP C 1 Cashout Type

54

Appendix A Types of Manager Transactions Chktodbf.exe

Description Type Table Check Amt 1 Amt 2` Misc 1 Misc 2 Code 1 Code 2

Paidout 1 PO amt PO # Disc -V/E

+Mgr 2 Table check Disc #

Table Delete 3 Table check NR Total

Real Total

Server Terminal

Source Cost Center

Mgr Item Delete

5 Table check Reason

Chng User/Tbl 9 new table

check Check amount

old server

Old tbl New server

Transfer Tbl 10 new table

new check

Check amount

old server

Old table

New server

Shutdown 11 Disc - Paymnt

Screen 12 Table check Disc #

No Sale 13 term # Gratuity/Sev.

Chg 14 Table check Gratuity

# Svc Chg

# Overring 15 Table