Home › Forums › Knowledge Base › Legacy Applications › QSR Inventory Program
- This topic has 0 replies, 1 voice, and was last updated 19 years ago by
Rob.
-
AuthorPosts
-
April 15, 2006 at 3:45 am #1624
Rob
MemberQSR Inventory Program
Version 2.01Last edited: December 15, 2003 08:15 AM
This is a fast food inventory program. It is designed to provide an easy to use interface for collecting the data necessary for calculating inventory variances in fast food restaurants. The aspects that make this a fast food inventory program are:
1. Inventory items can be defined as a key item. This allows the lists of inventory items used when entering counts of any kind to be masked. Also this allows for reports to be run, which will only include key items rather than all items.
2. Purchases are only a quantity and not detailed invoice information.
3. All counts (purchases,wastes,transfers,ending) can be modified at any time. The user will “post” the count information to a date, but these counts can be replaced later. The functionality is replacive, rather than additive. The user will simply enter in the desired count information and “post” to the incorrect day.
4. Variance reporting is accomplished by assigning PLUs to each inventory item and a quantity used each time sold. The normal method is to create a recipe for each PLU in the Product database.
5. There are four reports:
a. key item variance report
b. key item cost of sales report
c. all item variance report
d. all item cost of sales reportInventory Item Maintenance
Maintaining a list of items used in calculating cost of sales. Each item definition is comprised of a unique number, a description, a count unit description, a cost per count unit, a key item flag and a variance on/off flag.
PLU Assignment MaintenanceMaintaining a list of PLUs assigned to each inventory item. Each inventory item will have a list of PLUs assigned to it and a quantity to use each time it is sold.
PurchasesMaintaining a list of unposted purchases. Each purchase will consist of an inventory item and a quantity recieved.
Purchases will be posted upon user action to a YYMMDD.PRC file of the user’s choice. These counts can be modified at any time by entering new counts and reposting to the incorrect day.
TransfersMaintaining a list of unposted transfers. Each transfer will consist of an inventory item and a quantity recieved.
Transfers will be posted upon user action to a YYMMDD.TNF file of the user’s choice. These counts can be modified at any time by entering new counts and reposting to the incorrect day.
Waste CountsMaintaining a list of unposted waste counts. Each waste count will consist of an inventory item and a quantity wasted.
Waste counts will be posted upon user action to a YYMMDD.WST file of the user’s choice. These counts can be modified at any time by entering new counts and reposting to the incorrect day.
Ending CountsEnter ending counts for all items currently defined in item database.
Ending counts will be posted upon user action to a YYMMDD.CNT file of the user’s choice. These counts can be modified at any time by entering new counts and reposting to the incorrect day.
File FormatsName: LOCATION.DAT
Purpose: Storage of defined locations.
Location: INVDATA subdirectory of application
Type: Binary
Size: 1600
Record size: 16
Description STRING * 16Name: INVITEMS.DAT
Purpose: Storage of defined inventory items information.
Location: INVDATA subdirectory of application
Type: Binary
Size: Variable dependent on number of records
Record size: 64
Number 2 bytes INTEGER 1 – 2
Description 16 bytes STRING 3 – 18
Count Unit 12 bytes STRING 19 – 30
Location 2 bytes INTEGER 31 – 32
Cost 4 bytes LONG 33 – 36
Purchase Count 4 bytes LONG 37 – 40
Waste Count 4 bytes LONG 41 – 44
Ending Count 4 bytes LONG 45 – 48
Transfer Count 4 bytes LONG 49 – 52
Key Item Flag 1 byte BYTE 53
Theoretical Flag 1 byte BYTE 54
UsedFlag 2 bytes INTEGER 55 – 56
Extra1 4 bytes LONG 57 – 60
Extra2 4 bytes LONG 61 – 64NOTE: UsedFlag will indicate if item has been used for a purchase or a count. If UsedFlag is > 0 and the user tries to delete the item FF_INV will warn that the deletion of that item will ruin any historical reports.
Key Item Flag will be used for masking the lists of inventory items used when entering counts. Also will be used for reporting on key items only.
Theoretical Flag will indicate whether theoretical usage will be computed for the item.
Name: YYMMDD.CNT
Purpose: Permanent storage of ending counts
Location: INV subdirectory of application
Type: Binary
Size: Variable dependent on number of records
Record size: 6
Item Number INTEGER
Count LONGName: YYMMDD.PRC
Purpose: Permanent storage of purchases
Location : INV subdirectory of application
Type: Binary
Size: Variable dependent on number of records
Record size: 6
Item Number INTEGER
Count LONGName: YYMMDD.TNF
Purpose: Permanent storage of purchases
Location : INV subdirectory of application
Type: Binary
Size: Variable dependent on number of records
Record size: 6
Item Number INTEGER
Count LONGName: YYMMDD.WST
Purpose: Permanent storage of waste counts
Location : INV subdirectory of application
Type: Binary
Size: Variable dependent on number of records
Record size: 6
Item Number INTEGER
Count LONGName: #####.RCP (where ##### is the number of an Inventory Item)
Location: INVRECIPE subdirectory of application
Purpose: storage of PLU assignments and corresponding usage quantities
Size: variable dependent on number of records
Type: Binary
Record size: 6
Record fields:
Item Number – 2 bytes (INTEGER)
Quantity – 4 bytes (LONG)
Revisions06/17/96 Beta Version 1!02
1. Fixed bug related to inventory numbers. Was storing internally as an SHORT integer, this means that an inventory item number can never be greater that 32,767. Fixed by shrinking the number field on the dialog EDITITEM to 4 digits rather than allowing 5 digits. This approach was taken rather than changing the number to a LONG integer, because of the ease.
2. Added display of version on bottom of screen.
3. Renamed the program Q.S.R. Inventory06/18/96 Beta Version 1!03
1. Added more on-line help.
2. Added HASP copy protection. (Program #10)07/23/96 Version 1.04
1. Take item cost to 4 decimal places instead of 2
2. Add dollar totals of other categories to report along with Variance $08/25/96 Version 2.00
1. Version 5 compatible. Pull down menus, new report viewer, etc….
08/27/96 Version 2.01
1. Fixed bug related to running transfers and waste reports. Was only running a purchases report.
2. Enhanced memory usage by finding more places to erase arrays and only dim when necessary.
3. Added % figures to variance reports.12/09/98 Version 6.01
1. Y2K compliant.
01/05/2000 Version 6.02
1. Cleaned up some remaining Y2K bugs
02/09/2000 Version 6.03
1. The variance report wasn’t showing Theoretical costs correctly. This has been fixed.
-
AuthorPosts
- You must be logged in to reply to this topic.