Reservations : Setup of Reservations functionality
 
Setup of Reservations functionality
 
To set up Reservations functionality:
1. Begin by creating a salespoint group name in the SysManager > Preferences > Miscellaneous > Global Salespoint .INI tab called Reservations (or some other descriptive name). This group name must also be specified using the Group=Reservations (or a different descriptive name, if used) setting in Sales32c.INI on each salespoint (in the [SalesPoint] section of the Sales32c.INI file):
[SalesPoint]
Group=Reservations
 
Note: The information entered into the SysManager > Preferences > Miscellaneous > Global Salespoint .INI tab is shared by all salespoints. If a local Sales32c.INI setting is the same as a setting in the Global Salespoint .INI tab, then the local version overrides the global version. Salespoints learn the names of the groups of which they are part (as defined by group names in the SysManager > Preferences > Miscellaneous > Global Salespoint .INI tab) via the Group= setting in sales32c.INI.
 
2. To create a Reservations interface, one .INI setting is required in the [Preferences] section of the group.INI: ReservationHeaders=TRUE. This setting activates the Reservations functionality and allows access to the Reservation Headers.
3. Set the other Reservations functionality .INI settings. All of these settings are optional and are summarized in the following table.
 
Optional .INI setting
Description
RequireResHeader=TRUE
Requires that a Reservation Header is attached to the sale before the sale may be saved or finalized.
AutoCloseGuestRes=TRUE
Changes Guest Res button (in Sales > Guest Lookup > Summary tab) functionality so that it creates a reservation for the guest without bringing up the Reservation Header dialog.
AutoDatePop=TRUE
Pops the Date dialog with every product sold.
ChangeLogForAll=TRUE
If TRUE, a reservation log entry is written for every modification to the sale, even if the modification was done at a salespoint that does not have Reservation Headers enabled.
ClearAtFinalize=FALSE
Creates the ability to not clear a sale after saving/finalizing (default is that it is cleared).
GlobalDateTime=FALSE
The default setting of TRUE retains the current functionality of the button. If FALSE, line items added to the sale reflect the sale date/time, but when the sale date/time is changed, the line item date times stick to the date/time that was set when it was added to the sale.
GuestRequired=TRUE
Creates the requirement that a guest be attached to every line item in a sale.
Household=TRUE
If TRUE, this activates the ability to define households. The reservation guest defaults to a head of household. Any guests in the sale that are under the age of eighteen, have the same last name as the reservation guest and are linked to at least one of the reservation guest’s addresses default to a dependent.
MeetingLocations=TRUE
 
Items may be configured in SysManager to require the entry of a meeting location. In order to make this requirement salespoint-specific and not impact all salespoints, only salespoints configured with MeetingLocations=TRUE force the selection of a meeting location for items configured to do so. The validity of all entered information is checked when the Save button is pressed and the interface automatically switches to the proper tab if the validity check fails.
PartialFinalize=TRUE
With this setting, a salespoint can partially finalize sales.
RecallByReservation=
TRUE
 
Both regular saved sale and reservation criteria can be used to recall saved sales/reservations. When recalling a reservation at a salespoint that uses Reservation Headers, the Reservation criteria is selected by default; when recalling a saved sale or reservation at a salespoint that does not use Reservation Headers, the Saved Sale criteria is selected by default. The default behavior at non-Reservation Header salespoints may be changed by setting this to TRUE (meaning that the reservation criteria are selected by default instead of the saved sale criteria even though the salespoint does not use Reservation Headers).
RecallDateCheck=TRUE
If TRUE, enables ability to warn if recalling a sale with line items of a different date/time than the station.
RequiredGuestFields=First_name,Last_name, Birth_date,Address,
City,State,Zip,
Area_code,Phone,E-Mail
Gives the ability to specify required guest fields at the salespoint level so that certain salespoints can force the collection of more guest information without impacting every salespoint with required guest fields.
ResDesc=<ifnconf>RES#: <reserv_no></ifnconf> <ifconf>CNF#: <user_resno></ifconf> Guest: <first_name> <last_name> Arrival: <start_date>
Used to customize the Reservation Header information at the top of the sales invoice when in a reservation.
 
ReservationsInclude
Finalized=
FALSE
If set to FALSE, recalling reservations does not include finalized reservations (the Finalized reservation box on the Recall Sale dialog by default is set to Exclude).
ReservationMacro=
SELECTITEM2(
"FACILITIES
RESERV SERVICEFEE")
 
Facilitates call center service fees. The SELECTITEM2 Sales screen action macro adds an item to a sale if the item is not already present. Also, there is a section in Sales32c.INI for a Reservations Sales screen action macro. However, generically, this allows any macro to be executed when a reservation is attached. Thus, when a Reservation Header is attached, the service fee can be applied and if the header is removed and re-attached, the service fee is not re-added.