Please enable JavaScript to view this site.

ASSD - Ho(s)tel Management Software PMS 3

Navigation: What's New in PMS2

Version 2.13

Scroll Prev Top Next More

What's New in Version 2.13 – 24 July 2018

 

2.13 aka 2.12.50

 

1.Room prices with flexible number of people. Menu Settings Supervisor “roomjourna” = “P”. This feature is for room price articles. It doesn’t work for packages nor within an article split. Articles assigned via rooms ‘article for room’ fill column ‘Room’ of tab Billing with ‘pax’ followed by the number of people.  

2.Automatic Bed Filler (Private Rooms): new feature in tab Rooms of Reservations, the +/- buttons adjust automatically the bed filler. Rooms are filled up per default unless there are already other guests in this room or the fillers have already been adjusted manually.  

3.Currency Calculation Improved: it’s no longer required to maintain two rate entries for one pair of currencies. To use a single rate entry, delete the second entry! Round is now optional and the default is two digits. Calculations are usually made via the accounting currency. If input and output currency are the same, double calculation via accounting currency takes no longer place and rounding issues with pricelists are solved.

4.Rateplans Absolute Price Modifications: a new type “V” is supported which changes the price by an absolute value (+/-).

5.Remember Flex Rates: the dynamic prices remembered on tab Prices are no longer stored immediately but when the reservation is saved. So, as long as a reservation is not saved yet, prices change on tab Billing depending on selected rates or guests. Once a reservation is saved, users must remember to remove saved prices from tab “Prices” if they want to apply another rate/guest rate.

6.Rates for Reservations: the field “guarantee” on tab Terms can now be assigned to a rate plan. This way the user can select different rates. Guest defined rate plans or prices have higher priority. Guest type defined prices have lower priority. The priority is decided for each article individually.

7.Guarantee is stored in invoice data (s_jhead.article). It’s shown in Journal on tab ‘Misc’. This way a selected rate is stored with invoice data for reporting.

8.Special Meals: instead of using the predefined up to 4 general special meals per meal plan, it is now possible to specify up to 4 special meals for each reservation individually. For example from a total of 18 special meals, 4 can be assigned to a reservation. It’s also possible to use this only partly and e.g. take the first 2 special meals from meal plan and the remaining ones of reservation entry.

9.CXL: s_reser.cancelw turns into CXL field. Values are -1 (=not guaranteed - usually till 18:00), 0 (guaranteed - cancel till 18:00 same day), 1 cancel free of charge till 18:00 previous day. E.g. 3, 7, 14, 21, 45 days before arrival cancellation is free. The night after, we charge 100%. 99 = non-refundable. Can be imported from CRS/CM with XML <cxl>. Added to column ‘Guarantee’ of arrival list (first part of description till first space).

 

2.13 aka 2.12.52

 

10.Fix Billing Summary: r_invoice fix departure to selection

11.Fix: Delete Button Reservation

12.Fix: Copy/Paste edit price calendar without user rights

13.Database Audit Trail - for Meta/Switchboard

14.Retrieve Internet Bookings - Support for XML <restid>. CRS article restriction id fills PMS field ‘guarantee’ (only if not already configured in PMS retrieval entry or in XML). Support for XML <cxl>.

15.Auto-room-allocation: For preferred room types (only without guest split) the command ‘*ord’ can be used on top line to define an allocation order in ascending room size and within one size in the order of room types specified. This is applied only to button ‘New’ not ‘Adapt’ (and only for the *stop case). Purpose are automatic private room allocation for individual travellers where a category booked can fall back to higher ones. (Without ‘*ord’ the order is building, floor, corridor, room.)

16.Article split makes use of field s_article.argr2 “article group 2” sent to s_journal.jrefno to modify s_jhead.guestcode.

17.Room prices with 2 kinds of guests in one room, flexible number of people and flexible split. Menu Settings Supervisor “roomjourna” = “S”. Room article needs to get “Z” in package. The room price can be split into 2 parts based on number of people. The second figure comes from column 6 in room allocation. This feature is for room price articles. It doesn’t work for packages nor within an article split. Articles assigned via rooms ‘article for room’ fill column ‘Room’ of tab Billing with ‘pax’ followed by the total number of people, followed by ‘s’ and the number of people via column 6: e.g. pax4s1 means 4 people in total, 3 of first type and 1 of second type (e.g. different age or VAT). The article split consists of exactly two rows with a special quantity: 9000 = first group, 9001 = second group. Each of the two split article can have its own VAT and stats configuration. Additionally another split which is based on number of people e.g. breakfast. The field w_journal.room e.g. pax4s1 can be used for invoice printing also e.g. to supress the VAT code od this row.

18.Fix button VAT-Deposit-Invoice 3: the non-vat amount article is not created if value equal zero.

19.CRS room sizes exceed number of people: if e.g. CRS sends one 4-bed private room occupation but just 2 person, it will be modified automatically to one 2-bed private room to ensure that auto-room allocation works correctly.

20.Room Plan Highlight Reservation: with drag and drop to the left or right a reservation with all its rooms is highlighted in a special color (default grey/yellow - flexible via default values highbg/highfg e.g. RGB(209,166,131)). The information box on the top right shows an additional line with arrival, departure and number of guests.

21.Transactions Search: if on the last data record, a search for amount or reservation starts automatically at the start of current shift. The amount tolerance field tab stop has been enabled.

22.Group Agent Interface: pmsi.exe support for rate plans assigned to guests. Reservation types can be mapped to another code for agents reading reservation data (“regmap”).

23.Upload of rate plans to CRS. It’s now possible to upload rate plan price changes into CRS and CM. To accomplish this rate plans that should be uploaded need to be marked as public (“Y”). Only those rates are uploaded! With regard to rates based on week days and special days a maximum upload date is needed. The default is 732 days (can be changed via a default date via field validation ‘maxdate’) e.g. reduced for speed reasons or not needed because of no weekdays/special days or increased to cover a longer period.

24.Upload of guarantees to CRS PMS Restrictions. It’s possible to upload guarantees into CRS “PMS Restrictions”. To accomplish this the ‘Export path prices’ need to be set to ‘/interface/set-price-rest.php’. All guarantees that are not disabled and haven’t got a delete mark are uploaded. Existing entries are fully updated but never deleted. So in CRS/CM you could create additional restriction sets manually.

25.Support for AssaAbloy Vingcard Vision Door Key Cards

26.Room Types and Prices (a_calendar18) show Guarantees and their restrictions and rates if set to public (Y).

27.Contacts of Guests: a new button next to the contact drop down allows to show existing contact. If none is selected, it starts the creation of a new contact. A right click also starts the creation of a new contact. Via guest form valid other contacts can be pasted, too. Remember existing feature: if for the main field a contact is selected, it fills the main guest and its contact automatically.

28.Contacts of Guests: no longer get field validation via form ‘s_guest’. Instead they use form ‘s_contact’. This way you can configure different validations for main guest and contacts.