Pizza Manager Module for Touchnet
Styling Module Version 1.03
PizzaMgr.EXE and PizzaMgr.RES Version 6.01

Last edited: December 15, 2003 08:14 AM

Disclaimer:

This product, consisting of styling files and executables, is not part of Touch Menus, Inc official Product Line. It was created by Touch Menus for educational purposes. If you desire to use this program you may obtain a copy and modify it to suit your needs. Touch Menus, Inc. will not be responsible for upgrading or fixing bugs in this product.
Overview

This module gives the application the ability to do the following:

1.  Driver drops
2.  Cashier drops
3.  Reimbursement for drivers with user choice of methods – Mileage, Delivery Fee or Zip Code
4.  Driver reconciliation reports
5.  Cashier reconciliation reports
6.  Deposits
7.  Starting store bank
8.  Ending store bank
9.  Reports from Pizza Manager:
    a. Sales Summary report
    b. Delivery Summary report
    c. Delivery Detail report
    d. Void report
    e. Paid out detail report
    f. Paid in detail report
    g. Order taker report
INSTALLATION

The module consists of two parts: the styling files and the executable files.

Styling Files Installation

1.  Place the PIZZAMGR.MOD file in the application directory and unzip.

2.  Make a chain called STARTUP with the following instructions:
      Page=PMT_LOG
      Margin=PMT_LOG
      Passcode=

3.  Modify PMLOGIN chain with Page= and Margin = to suit your application.

4.  Modify PMLOGIN chain to keep out employees clocked in to departments that should have no access to checks.  It is currently styled as an example only to keep out employees clocked in to department #2.

5.  Modify PMDISPCH chain
      Do the correct template
      Print receipt upon dispatch to appropriate printer(s)

6.  Modify PM_DDROP chain
      print drop receipt to appropriate printer(s)

7.  Modify PM_CXRPT chain
      print xreport templates to appropriate printer(s)

8.  Modify PM_CZRPT chain
      print zreport templates to appropriate printer(s)

9.  Modify PM_DTIPS chain
      order a dummy PLU for loading gratuity

10. Modify PMDZRPT2 chain
      print zreport templates to appropriate printer(s)

11. Modify PM_DXRPT chain
      print xreport templates to appropriate printer(s)

12. On Manager control page (or equivalent)
      Make three buttons
1 >            Label:  Driver Functions
Instructions:  Page = PM_DM
      Margin = PM_DM

2 >              Label:  Cash Management
Instructions:  Page = PM_CM
      Margin = PM_CM

13. Modify TENDER chain  (or equivalent)
      Add >  Chain to PM_CLOSE somewhere before closing check

14. On START Margin (or equivalent)
      Make two buttons
      1 >                Label:  Driver Functions
  Instructions:  Page = PMDRIVER
Margin = PMDRIVER

      2 >                Label:  Cashier Functions
  Instructions:  Page = PM_CASHR
Margin = PM_CASHR

15. Add a printer
      Name: PM_POST
      Port: N/A
      File: Yes
  Attached: N/A

16. On PMZIPFEE.PAG and PMZIPFEE.MGN type in the zip codes to be used for zip code reimbursement.(These zip codes should be the same as the zip codes on the CUS-EDI.CTL)
    The layout of the buttons is:

Margin          Page
      1        2        3      4        5
      6        7        8      9        10
    11        12      13      14      15

    Each button is chained to PMZ???FEE.CHN where ??? is the number of the button.

17. For each button used in step 16 go to the corresponding PMZ???FEE.CHN and set Number 1 = the zip code typed on the button.

18. In the PMZCHKCT.CHN for each IF C:ZIP= statement enter the corresponding zip code.  ie. If you typed 12345 on Button 1 on PMZIPFEE.MGN then you would have modified PMZ1FEE.CHN and set Number 1 = 12345 and now you would modify the first If C:ZIP= statement to read IF C:ZIP = 12345.

19. Make a choice on the CHOOSE menu to run PIZZAMGR.

20. Note:  For reporting purposes Groups 90 thru 99 must be reserved for “Bad” groups.  ie.  Bad pizza discounts, late discounts, etc.
Technical Information Relating to Styling

Global variable usage:

    Number 1: Dispatch Time
    Number 2: Return Time
    Word 1  : Dispatch Status –  DI or DO  (Dispatch In or Dispatch Out)
    Word 2  : Return

These variables only apply to Delivery checks (Ordtype = DELVRY)

NOTE:  In styling:  Word 1 must contain DI or DO to denote dispatch status.  Order Type must be DELVRY for delivery checks.
Bucket File Formats

REIMBRS.BUK
(stores the Mileage Rate,Delivery Rate, and Driver’s standard starting bank)
  Col
  Row      1
  1      Mileage Rate (####.##)
  2      Delivery Fee (####.##)
  3      Standard Bank(####.##)
  4      Zip Code Fees(####.##) Columns 1,11,—141 (max 15 fees)

EMPS.BUK
(stores Employee IDs and Names for asthetic use throughout the module)
      Col
      1                      20
  Row = Emp ID        Emp Id (#####)          Emp Name ($$$$$$$$$$)

INDIVIDUAL EMPLOYEE # .BUK    (eg. 1234.BUK)
(stores sales information in buckets named after the Emp Id)
    Col
  Row        1
  1        # of Checks (#####)
  2        Sales (####.##)
  3        Drops (####.##)
  4        Individual Starting Bank (if applicable) (####.##)
  5        Tender (####.##)
  6        Zip Code Check Count(#####) Columns 1,11,21 — 141
      (max 15 counts)
PM_POST File Information

This file contains the information collected by the Pizza Manager styling files.  It is created using the PRINT TO instruction in Touchnet.  The file is an appending list of transactions which Pizza Manager executable will post to appropriate journal files.
Below is an example of a transaction which might be contained within the file:

Date = 951128
Description = Driver Drop
Amount = 25.00
Kind = 7
Time = 0925
Employee = 1

---

Each of the lines must contain the text description as typed here.  Pizza Manager will be looking for this specific text.  Each line must also have an ( sign following the text.  This is to tell Pizza Manager where the text ends and the value for the field begins.  The lines must also contain specifically formatted information following the ( sign.

      Date = Decimal Date
      Description = up to 12 characters of text
    (used for Cash Paid Outs and Cash Paid Ins)
      Amount = currency value
      Kind =  1 – Cash Paid In
      2 – Cash Paid Out
      3 – Deposit
      4 – Bank Bag Drop (Cashier Drop)
      5 – Store’s Starting Bank
      6 – Store’s Ending Bank
      7 – Driver Drop
      Time = Decimal Time
      Employee = #####
      The entries below are hard coded to appear only when necessary.
      Bag = #####  (when applicable)
      Mileage = ##### (when applicable)
Executable Files Installation

1. Place the PizzaMgr.EXE and PizzaMgr.RES files in the TOUCHNET directory.
Technical Discussion Of PizzaMgr Executable

The following is a description of the steps that Pizza Manager goes through upon running the program and the files used in each step.

Step 1 –  Check for SHARE
    This step will create Share.TST in the DATA directory.  If it is deleted it will be recreated.  It has no bytes and has no further value.  If SHARE is not present, Pizza Manager will error out, displaying the reason.

Step 2 –  Check for CHECKS DATA REPORTS
    This step checks for the existence of the proper subdirectories of the directory Pizza Manager is being run from.  It should be run from the application directory.  If any of these subdirectories are not found, Pizza Manager will error out, displaying the reason.

Step 3 –  Check for the Resource File
    This step checks for the existence of the resource file (PizzaMgr.RES).  This file should be located in the same directory as the executable (PizzaMgr.EXE)  If this file is not found, Pizza Manager will error out, displaying the reason.

Step 4 –  Delete *.RP files
    This step will delete any files with the extension .RP in the REPORTS directory.  These files are the files created when running reports in Manager and Pizza Manager.  This is done for house cleaning purposes.

Step 5 –  Load Report Options
    This step will read the Manager.CFG file in the DATA directory.  The information in this file is created by Manager in Report Options.  Pizza Manager will read the extra text if defined and the Eject Page option.  The extra text will be printed as a header for each report.  The Eject Page option is useful if you are using a laser or ink-jet printer.  This file is not required.  If this file is not present, Pizza Manager will skip this step.

Step 6 –  Load Global Options
    This step will read the Global.DAT file in the application directory.  This file is created in Editnet.  Pizza Manager will read the New Day Hour option.  This value is used to determine which journal files to post information to.  It follows the same posting convention as Touchnet.  This file is not required.  If this file is not present, Pizza Manager will skip this step.

Step 7 –  Post the Pizza Manager File
    This step will read the PM_POST.PRN file in the DATA directory and post the findings in the appropriate journal files.  All information posted is appended to the journal files.  This file is created by Touchnet using the Pizza Manager styling files and the Print To instruction. This file is not required.  If this file is not present, Pizza Manager will skip this step.

NOTE: For detailed information concerning the codes used for posting the information contained in the PM_POST.PRN file see the JOURNAL.DOC file.

Step 8 –  Load the Groups
    This step will read the Groups.DAT file in the DATA directory.  This file is created by Manager.  Pizza Manager will read the Group descriptions  for use in reports.  Pizza Manager does not write to this file.  This file is not required.  If this file is not present, Pizza Manager will skip this step.

Step 9 –  Load the Product Descriptions
    This step will read the Product.DAT file in the application directory.  This file is created by Editnet and maintained by Manager.  Pizza Manager will only read the descriptions of the PLUs for use in the reports.  Pizza Manager will not write to this file.  This file is not required.  If this file is not present, Pizza Manager will skip this  step.

Step 10 – Load Employees
    This step will read the Employee.DAT file in the DATA directory.  This file is created by Manager.  Pizza Manager will only read names from this file.  Pizza Manager will not write to this file.  This file is not required.  If this file is not present, Pizza Manager will skip this step.

Step 11 – Load Media Definitions
    This step will read the Media.DAT file in the application directory.  This file is created by Editnet.  Pizza Manager will only read the defined medias, this file is not written to.  This file is not required.  If this file is not present, Pizza Manager will skip this step.

Step 12 – Load Departments
    This step will read the Depts.DAT file in the DATA directory.  This file is created by Manager.  Pizza Manager will only read the labor departments from this file.  This file is not written to.  This file is not required.  If this file is not present, Pizza Manager will skip this step.

Step 13 – Run the Main program
    This step will run the user interface.

Other files used by Pizza Manager:
  All *.JOU files in the REPORTS directory for sales information.
  All *.TIM files in the REPORTS directory for labor information.
  Customer.DAT,CusAcnt.DAT, CusName.DAT files in the DATA directory for use  in detailed  delivery reports.

Files created by Pizza Manager:
  Report files in the REPORTS directory:
    SSRRep.RP    – Sales Summary Report
    DLVSMRep.RP  – Delivery Summary Report
    DLDTRep.RP    – Delivery Detail Report
    CPORep.RP    – Detailed Cash Paid Out Report
    CPIRep.RP    – Detailed Cash Paid In Report
    VoidRep.RP    – Void Report
Revisions

12/11/95

Version 1.10 (Executable)

  Added HASP copy protection.  Added support for New RP Libs -> features to be seen in version 4.42 of Touchnet – defining printer port, page break, and condensed printing when report is > 80 columns.

12/13/95

Version 1.03 (Styling Module)

  Found bug in styling related to Cashier/Bank Drops.  This function was not storing the drop amount in the employee’s bucket, therefore the X and Z reports were incorrect.  The affected chain was PMCSHDRP.

12/19/95

Version 1.11 (Executable)

  Fixed bugs relating to reporting on Dispatch Time and Time on Road.  Fixed bug relating to reporting on mileage.

12/08/98

Version 6.01 (Executable)

  Y2K compliant.

Disclaimer:

This product, consisting of styling files and executables, is not part of Touch Menus, Inc official Product Line. It was created by Touch Menus for educational purposes. If you desire to use this program you may obtain a copy and modify it to suit your needs. Touch Menus, Inc. will not be responsible for upgrading or fixing bugs in this product.