Menu Record Maintenance
Creation, amendment, deletion and enquiry facilities for Menus.
All Menus must have a master record for each unit in which they are to be referenced. A unique (to CATERMAN) identifier provides the internal reference to access the record. Subsequently, all accesses to the record may take advantage of alpha-matching facilities, so the identifier need not be used. Consequently, the identifiers should be designed for your convenience as they dictate the order in which Menus appear in reports.
Creation of a Menu Record
A unique (within the Unit) Menu identifier/reference needs to be provided.
The user is asked if the menu should be copied from an existing menu. For example, a menu for afternoon tea could be repeated a number of times in a menu cycle, but, as a menu can only appear once in a menu cycle it would need a different name each time it was used (allowing for different numbers of portions for each occurrence).
The menus could be called "Afternoon Tea Monday Week 1", "Afternoon Tea Tuesday Week 1" for example.
For the same Menu in DIFFERENT Units the same identifier may be used.
Menu Identifiers should be of a form not easily confused with Item Record identifiers, Recipe identifiers, etc.
The full name of the Menu should be entered, each word separated by a space. Each word then provides a "key" in alphamatching, so that, for example, if the name of the Menu is "Xmas Dinner" then entering the word "xm" would bring that item up in a list of potential Menus meeting your search criteria. So would the word "dinner" but you might have a lot of Menus with the word "dinner" so the resulting list would be unwieldy.
The type of menu dictates whether it is used for production (P, where numbers of portions are
generated by CATERMAN according to outstanding orders from other units) or any user-desired code.
The Menu Band dictates which charge band of recipes is pertinent to this menu.
Recipes are then chosen for inclusion in the menu either by entering the recipe identifier or by alphamatching. The number of portions is also entered.
If a Price Look Up (PLU) number is associated with this menu item, it is entered, allowing the menu item to be selected by PLU (If the user PC is equipped with a retail-type PLU keyboard).
Menu totals and the cost of ingredients as a percentage of the total are shown.
Amendment of a Menu Record
The same mechanisms apply to amending a Menu record as to creating it.
The Menu is evoked by entering its identifier or by alphamatching. Alphamatching includes the ability to bring up a Menu list showing all menus containing a particular recipe (enter the recipe identifier - providing that it cannot be confused with a menu identifier!).
Deletion of a Menu Record
Menu records may only be deleted if they do not appear in the menu cycle.
Selection of a menu for deletion is similar to selection for amendment.
Display of a Menu Record
To display a Menu record, either enter its identifier or use alphamatching by entering any word or the beginning of any word in its name or a recipe identifier which appears within it.
Processing Subordinate Unit Menus
Suitably empowered passwords may change portion numbers of menus for subordinate units.
For example, restaurant manager might change portion numbers of the lunch menu of the restaurant salad bar.
Update Menu Servings Only
This is a quick update method for changing only numbers of portions in a menu.
A number of reports are available based on menu data.
Return to Menu Facilities List