Redbook

  • This topic has 0 replies, 1 voice, and was last updated 19 years ago by Rob.
Viewing 1 post (of 1 total)
  • Author
    Posts
  • #1628
    Rob
    Member

    Redbook

    The report is a weekly summary of sales, bread count and inventory information, using Monday as the beginning day. (See Report.DOC)

    This program is property of Power Menus POS and was written for Blimpie corporation.  It can be used for other applications but can not be changed. Only Blimpie can make suggestions for program changes.

    The program requires TOUCHNET, BASICINV and BREADMGR programs to generate the information reported on. It can be run without these, but the report will be incorrect.
    [color=red:29z2cv0y][u:29z2cv0y][b:29z2cv0y]
    Download Redbook[/b:29z2cv0y][/u:29z2cv0y][/color:29z2cv0y]

    Installation

    The installation procedure below is not technically the only way to install the program, but rather the Power Menus standard installation procedure.

    Required Files:

      1. RedBook.EXE – executable program file
      2. RedBook.RES – resource file

    Required Subdirectories:

        * BREAD
        * BREADRECIPE
        * CHECKS
        * DATA
        * INV
        * REPORTS

      1. Place the required files in the TOUCHNET directory.
      2. Make required subdirectories of application directory.
      3. Make a method of launching the program. Working directory should be the application subdirectory. To launch the program use the executable filename (REDBOOK)

    Operation

    Setup

    It will require some setup steps to generate the report correctly. To access the setup options, select Options from the Main Menu. The steps will be:

      1. DEFINE MEAT SALES GROUPS

          The sales section of the Redbook report has two subtotals, a meat sales subtotal and an other sales subtotal. The meat sales subtotal is a combination of several TOUCHNET sales groups. The definition of exactly which groups make up the Meat sales subtotal is left to the user. The user will create a list of the TOUCHNET sales groups to include in the Meat Sales Subtotal. This will require that the sales groups are setup in such a manner that sales dollars within each group will be included in the Meat Sales. The groups can not be used partially. This list will be editable at any time. The user will be able to add, modify or delete entries from the list. The entries will be stored in DATAMGroups.DAT file. See File Formats section for detailed file information.
      2. DEFINE CATERING SALES GROUPS

          The average check figure in the Statistical Section of the Redbook report uses the net sales minus the catering sales divided by the check count. The user will create a list of the TOUCHNET sales groups to include in the Catering Sales Subtotal. This will require that the sales groups are setup in such a manner that sales dollars within each group will be included in the Catering Sales. The groups can not be used partially. This list will be editable at any time. The user will be able to add, modify or delete entries from the list. The entries will be stored in DATACGroups.DAT file. See File Formats section for detailed file information.
      3. DEFINE BLAST BREAD PLUs

          The Redbook report has a “Bigger Bite %” figure that is computed using this formula:

          Qty of Bigger Bites sold / (Bread sold – Blast bread used)

          NOTE: All bread is counted/used in feet. The user must define which PLUs are considered Blast Bread PLUs, and how much bread is used each time one is sold. This list is editable at any time. The user will be able to add, modify or delete entries from the list. The entries will be stored in DATABlastPLU.DAT file. See File Formats section for detailed file information.
      4. DEFINE BIG BITE PLUs

          This is used to define which PLUs are considered Bigger Bite PLUs and the quantity of bread used each time one is sold. This information is used when computing the “Bigger Bite%” figure. This list is editable at any time. The user will be able to add, modify or delete entries from the list.  The entries will be stored in DATABigPLU.DAT file. See File Formats section for detailed file information.
      5. DEFINE SUB SALES PLUs

          The Redbook report has a “Net Bread Factor” figure which represents the dollar amount brought in by each foot of bread. This figure is derived by the following formula:

          Sub Sales $ / (Bread Sold – Blast Bread)

          The user will create list of the PLUs to be included in “Sub Sales”. This list will be editable at any time. The user will be able to add, modify or delete entries from the list. The entries will be stored in DATASubPLUs.DAT file. See File Formats section for detailed file information.
      6. DEFINE UNIT PLUs

          The Redbook report has a “Productivity” figure. This figure represents the number of subs/pita/salads sold per man hour worked. The formula used is:

          Number of units sold / Number of Man Hours worked

          The user will create list of the PLUs to be considered a “Unit” and the number of units each will count for when sold. This list will be editable at any time. The user will be able to add, modify or delete entries from the list. The entries will be stored in DATAUnitPLUs.DAT file. See File Formats section for detailed file information.
      7. DEFINE INVENTORY ITEMS TO BE USED IN MEAT & CHEESE SECTION

          The Redbook report has a weekly meat and cheese inventory section. The user must define which inventory items from Basic Inventory are to be included in this section. The user will create a list of the items to use. This list is editable at any time. The entries will be stored in DATAMandC.DAT file. See File Formats section for detailed file information.

    Maintenance

    The Redbook report has a simple cash reconciliation section. The user can enter deposits, paid outs and cash adjustments to balance for the day. To access these procedures, select Cash Transactions from the Main Menu. All transactions are stored in a temporary file until they are posted. Each transaction requires a date, when posted, the transactions are posted the the corresponding YYMMDD.JOU (sales journal) file.

    ENTER DEPOSITS

    Enter a date and an amount. (See File Formats Section for temporary file format)

    ENTER PAID OUTS

    Enter a date and an amount. (See File Formats Section for temporary file format)

    ENTER CASH ADJUSTMENTS

    Enter a date and an amount. (See File Formats Section for temporary file format)

    Action

    To run the report, select Report from the Main Menu. The date currently selected will be shown above the report menu selections. Choose an ending date by selecting the appropriate menu choice. The report is designed to be run from Monday to Sunday, but can be run from any ending date. To run the report as designed, choose a Sunday as the ending date. The program will find the first Monday preceding the ending date selected and start processing the sales, bread and inventory journals from that day forward. (See Report.DOC for example report format.)
    Technical

    Steps Redbook performs upon execution

      1. Checks for existence of SHARE.
      2. Checks for required subdirectories. (BREAD, CHECKS, DATA, REPORTS, BREADRECIPE). Checks version compatibility. (Reads GLOBAL.DAT)
      3. Loads report options as defined in TOUCHNET’s MANAGER program. Will respect extra text, printer port, condensed and normal print codes, lines per page and eject page options. (Reads Manager.CFG)
      4. Initialize the program.

          Check for resource file

          Initialize Help File

          Draw initial screen
      5. Delete any files in the REPORTS directory with the extension .RP.
      6. Initialize XMS memory area.
      7. Draw Main Menu.

    Maximum Values
    Report Dates 730
    Bread Types 20
    PLUs 1000
    Inventory Items 2000
    Unposted Cash Transactions 100
    Meat and Cheese Items 1000

    File Formats
    Name MGroups.DAT
    Location Data subdirectory of application
    Purpose Storage of sales group #’s to include in Meat Sales
    Type Binary
    Size variable, dependent on number of records
    Record size 2 bytes
    Record fields
    Group # 2 bytes (INTEGER)

    Name CGroups.DAT
    Location Data subdirectory of application
    Purpose Storage of sales group #’s to include in Catering Sales
    Type Binary
    Size variable, dependent on number of records
    Record size 2 bytes
    Record fields
    Group # 2 bytes (INTEGER)

    Name BlastPLU.DAT
    Location Data subdirectory of application
    Purpose Storage of PLUs and bread used quantities for Blast Bread
    Type Binary
    Size variable, dependent on number of records
    Record size 6 bytes
    Record fields
    PLU # 2 bytes (INTEGER)
    Quantity 4 bytes (LONG)

    Name BigPLU.DAT
    Location Data subdirectory of application
    Purpose Storage of PLUs and bread used quantities for Bigger Bites
    Type Binary
    Size variable, dependent on number of records
    Record size 6 bytes
    Record fields
    PLU # 2 bytes (INTEGER)
    Quantity 4 bytes (LONG)

    Name SubPLUs.DAT
    Location Data subdirectory of application
    Purpose Storage of PLUs to be included in the “Sub Sales” figure
    Type Binary
    Size variable, dependent on number of records
    Record size 2 bytes
    Record fields
    PLU # 2 bytes (INTEGER)

    Name UnitPLUs.DAT
    Location Data subdirectory of application
    Purpose Storage of PLUs and their corresponding “Unit” value
    Type Binary
    Size variable, dependent on number of records
    Record size 6 bytes
    Record fields
    PLU # 2 bytes (INTEGER)
    Quantity 4 bytes (LONG)

    Name MandC.DAT
    Location Data subdirectory of application
    Purpose Storage of inventory items to include in the “Meat & Cheese” section
    Type Binary
    Size variable, dependent on number of records
    Record size 2 bytes
    Record fields
    Item # 2 bytes (INTEGER)
    Revisions

    03/26/96 Beta Version 1.01

      1. Changed the way Redbook collected and used the Unit PLUs. Previously the user would simply build a list of PLUs to be considered a unit. Now the user will also define a unit value for each PLU. For example, when making a 3 or 6 foot sandwich the unit value would be higher that making a 6 inch sandwich.
      2. Added feature(?), when adding entries to any list the highlight would not move to the new entry. Now it will.

    04/01/96 Beta Version 1.01

      1. Did not release previous version 1.01. Need to add some additional features before releasing.
      2. Added ability to define which TOUCHNET sales groups count as “Catering” sales. This will function just like the Meat Sales Groups definitions. Added the ability to print any database/list.
      3. Changed the way Redbook computed Average check. Previously would not subtract checks that were “No-Sales” and used total net sales, now will not include “No-Sales” and not include Catering sales.

    04/05/96 Beta Version 1.02

      1. Fixed bug in all procedures in OPTIONS.BAS relating to defining a PLU. The list was not built correctly nor was it compressed in the combo box.

    04/06/96 Beta Version 1.03

      1. Fixed bug related to printing lists. Would print report and CALL SeeReports.
      2. Fixed bug related to defining a PLU, version 1.02 made the bug.
      3. Fixed bug related to counting checks. Will no longer include checks with a zero amount, these are considered “No-Sales”. Version 1.01 attempted to address this issue, but I forgot to complete the code necessary to implement all of it.
      4. Renamed all references to Blast Bread -> Catering Bread. The bigger bite percentage formula originally was subtracting all Blast Bread sold, but should actually subtract all Catering Bread. Also the “Net Bread Factor” was doing the same thing, but should not.
      5. Fixed bug in computing Net Bread Factor. Had pasted code from Day 1 net Bread computation, but not changed the array element numbers to address the corresponding day. All array elements were #1. )-:

    05/15/96 Version 1.04 (Official Release!)

      1. Fixed bug related to adding up the “Total Cash” The formula used was: PaidOuts+Deposits/100 (PaidOuts and Deposits store the info in cents) This would not compute correctly in a CALL MakeRP(Using$”##.##”) situation. Changed it to offload the computation into a long variable before printing.
      2. Fixed bug related to reporting sales group 0. The For Next loop responsible for reporting this information began at 1 not 0!
      3. Added ability to see all 2000 PLUs available in Version 5.xx Touchnet.
      4. Added ability to define which inventory items from BasicInv are to be used in the Meat & Cheese inventory information section.
      5. Composed more help information for on line help system.
      6. Composed a user’s manual and support manual.
      7. Compiled a release version.

    06/17/96 Version 1.05

      1. Fixed bug related to creating an array filled with the names of journal files from Monday to Sunday. (SUB BuildWTD)
      2. Changed some code in SUB RangeOfDates. (Library.BAS)
      3. Changed Report Output menu to:

          View instead of Print
          Print View
          Exit Exit

    11/20/96 Version 1.06

      1. Added on-line help for Defining Meat and Cheese Inventory Items.
      2. Added ability to output Redbook report as text file.
      3. Fixed bug related to “Other Sales” section on Redbook Report. Was correctly showing positive sales for individual day columns, but was showing that specific group’s totals in total column. This presented a problem when the group was used for negative AND positive sales.

    04/21/97 Version 4.07

      1. Fixed bug related to respecting condensed print codes defined in Manager.
      2. Changed time stamp and version number to match file format version of Touch Menus core products (TouchNET/Manager/Cus_Mgr).

    06/09/97 Version 6.00

      1. Compiled with new libs for SHARE and ERRORS. No longer requires SHARE.
      2. Updated version checking. (global.dat)
      3. Updated loading of Product.DAT
      4. Included void, and overring handling.
      5. Incorporated new print outputs used in Manager.
      6. Fixed bug related to posting cash transactions. When posting, it would not erase the temporary file. (not sure about this bug, it only happened on my PC not Tim’s)
      7. Changed format of report to include requested information at the top of the report.
      8. Added ability to do Credit Card Settlements.
      9. Incorporated all of Bread Manager into Redbook.
      10. Changed GUI to pull down menus.

    10/08/97 Version 6.01

      1. Fixed a bug related to date calculation. Would incorrectly calculate Sept 31st, which does not exist, and generate an error 9 when building the report for a week that spanned two months where the first month did not have 31 days. Now will check validity of date.

    11/13/97 Version 6.02

      1. Fixed a bug related calculating total Cash Collected. Was not including the Credit Card Settlement totals.
      2. Adjusted saving of unposted bread counts to address the possibility of running the unposted bread usage report and not seeing the most recent counts because it had not been saved yet.

    12/12/97 Version 6.03

      1. Added support for 1999 PLUs, was missing in previous versions.
      2. Renamed Bread Usage Reports to: Bread VARIANCE reports.
      3. Fixed bug in both Unposted and Regular Variance reports that cause report to be incorrect. The problem was related to incorrect date information being acted on.

    07/29/98 Version 6.04

      1. Added support for virtual HASP (standalone)

    12/08/98 Version 6.05

      1. Y2K compliant

    1/07/02 Version 6.06  rw

      1. Removed HASP copy protection to work with keylok copy protection system.  Prior to this version, Redbook required a HASP license 12 to run.

    10/17/02 Version 6.07  rw

      1. Corrected problem of error 255 occurring when selecting Baked Counts, Throw Out Counts, or Free Counts from the Bread Counts pull down menu.

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.