previous

Banqueting F&B Plan (REP_FBPLAN.REP with REP_FBPLAN.FMX)

This report is a great tool especially for the Banquet Chef and kitchen. It can be used additionally to the Banquet Event Orders or even instead of the Banquet Event Orders as a detailed document for any necessary food or beverage preparation and requirements.

It can be printed in a daily format, with a page break after each day, or in a continuous weekly format. There is also an option to print more details, like the account name, contacts name and communication details plus all relevant notes, or a summary format, that essentially only prints the food and beverage requirements themselves.

Note: This report requires that the user be granted the EVENT PRINT permission in the selected property to run the report. Also, the Property LOV in this report is further limited by the properties to which the user has the appropriate access granted.

Selection Criteria

Date Range (Begin/End Date). Allows the selection of any event date range.

Property. Available when the OPS_MHOT license is active; choose the property for which the report should be printed.

Business Block. It is possible to only order the report for one or several specific business blocks.

Note: When selecting a Master Block ID in the Bus.Block filter, Opera will also include the Sub Block IDs linked to that Master. The report will then print all Events linked to the Master and its Sub Blocks. If a Sub Block ID is selected, only Events linked to that Sub Block will be printed.

Event Status. This allows to filter the report by event status. Generally this would only include production status code. Cancellation status codes should be excluded.

Event Type. Allows to filter the report by event type.

Resp. Dept. Allow the selection of one or more responsible departments. If for example different menu components are prepared in different kitchen sections, and those sections / departments have been correctly assigned to all menu items, it would  be possible to produce the report separately for each kitchen section. Or, on a simpler level, it would just indicate if the kitchen, beverage staff or banquet operations staff is responsible to provide certain items on the list.

Menu. Allows the selection of one or several specific menus as report filter.

Daily/Weekly. When DAILY is selected, the report will do a page break after each day. Weekly will print continuously without page breaks, but still in date order.

Detailed/Summary. If DETAILED is selected, additional information on the account name, contact name and communication details for these are printed underneath the event time and name. If SUMMARY is selected, this information is excluded.

Food/Bev/Both. Allows the selection of either only food item, only beverage items or both to be included on the report.

Report Data

The report is sorted in date order and within each date in event time order. Information available on the report is per event, event start and end time, event name and id, function space, set-up style and number of attendees.

Note: The Event Date is repeated in the header of each page for this report.

If DETAILED has been selected on the report order form, additional information about account name, contact name, contact on site as well as contact communication details are printed for each event also.

Keep in mind that account and contact information is displayed according to the following profile type hierarchy:

For each event then follow the menu details: menu serving time, menu name, menu internal price ( total that the menu would cost if all items contained in it would be sold separately – calculated from the menu item prices), menu sales price, numbers of expected, guaranteed, set and actual covers.

On the next level, menu item detail, the information printed contains: menu item name, menu item price – if the menu item is not included in the menu , numbers expected, guaranteed, set and actual, as well as the responsible department if one is assigned to the item in question.

Following the menu item details, menu notes relating to each menu will print, followed by event notes after all menus have been printed.