What's New in OPERA > V5.0.03.02
|
|
|
V5.0.03.02
The following gives a brief description of New Features introduced in OPERA.
PMSThe Membership Level field is a view-only field displays the membership level attached to the guest profile or the membership type that is equal to the property default membership type.
This field’s visibility on the Dashboard 2 is determined by the property’s configuration for Menu and Screen Design for the Dashboard 2 screen attributes.
The Invoice No. field is available to enter the Invoice Number to search for. Only one invoice number can be entered and the complete invoice number must be entered. For example, if you want to search for invoice number 56789, then 56789 must be entered.
Upsell functionality has been enhanced. Please see highlights of the functionality below;
1. Upsell transaction code is now a seperate transaction code that gets posted to reservations as a separate charge
By assigning a specific transaction code for a reservation upsell posting, a separate posting will be made on the reservation/folio and the upsell amount applied can be differentiated from the actual rate code that is attached to the reservation.
2. Other improvements in look and feel of upsell configuration and logging.
The Total Upsell Charge amount is displayed in the Upsell Activity Log.
3. All applicable export views have been modified to accomodate the upsell fields.
When an upsell has been completed for a reservation, the UPSELL_CHARGE amount will be included in the following exports:
4. The Reservation Upsell report has been enhanced to include additional upsell information.
5. Confirmation and registration cards have been enhanced to include upsell information
When Upsell conditions are met for a reservation, a list of the room types that are associated with the reservation's rate code and that would constitute an upsell are printed on Registration Cards and Confirmation Letters.
Registration Card
Confirmation Letter
6. Upsell functionality has now been extended to Blocks.
And reservations that are associated with a block code are eligible for the upsell rather they have a rate code attached or not. But for blocks with no rate code associated, upsell based on formula % of difference added to original rate, may not be offered, if there is no rate defined in the Block Rate Grid for the room types involved in the upsell. Also, when applying an upsell to a reservation that is part of a block, the user will be prompted with the Apply To and the user can then apply the upsell, based on the permissions granted, to the Guest Only, All Guests in the Group' Selected Guests, Only Guests with Same Arrival Date, All Checked In Guests, or Guests in House Between.
On the Package Forecast (pkgforecast) report, 2 new columns ‘Arr. Rms.’ (Arrival Rooms) and ‘Dep. Rms.’ (Departure Rooms) have been added.
By activating the Rates>Package Pricing and Availability Attributes application parameter, the property will be able to add additional attributes to package pricing, so that the price and allowance allocation can be controlled based on the minimum and maximum nights/persons attached to the reservation.
When configuring packages using the Package Pricing and Availability Attributes, please keep in mind the following rules:
The Stay Date falls between the Start Date and End Date of the package AND
No of Nights fall between the Min/Max Nights value range AND
No of Persons fall between the Min/Max value range.
Note: When package details records are configured, each record must have at least one of the aspects i.e.; Date Range, Min/Max Night range and Min/Max persons range, different so that every package details record can be uniquely identified and there is no complete overlap. While configuring package details record, if OPERA identifies that the record overlap occurs based on either Date Range, Min/Max Night range or Min/Max persons range, user will be prompted if automatic adjustment should take place and if they select Yes, then the current record being added will be saved and existing overlapping record will be removed.
IFC
A check mark appears in the Followup column if the wake-up call request is for a follow up call. A follow-up call cannot be edited. To change the time for the follow-up call, edit the main wake up call. When cancelling a main wake-up call, the follow-up call will also be cancelled.
If the guest wishes to have a follow-up wake-up call, enter the time in the Follow Up Call Time field. The time must be later that the time specified in the Time field.
The Membership>Courtesy Card Transfer application parameter has been introduced and activating this parameter enables a property to manually send a selected number or all of the courtesy card transactions for a specific business date and a single membership type from the Miscellaneous>Membership>Courtesy Card Transfer menu option.
After the correct items have been selected, click the Transfer button to start the Transfer process. Before processing the transfer, a confirmation prompt is displayed showing a summary of the totals (number of selected transactions and total amount) that will be transferred. Select Yes to continue and process the transactions or select to No to return to the Courtesy Card Transfer screen and modify the items to process.
Select the Reference drop down arrow to choose the attributes to include in the Reference field for postings. When attributes are selected here, they will take precedence over the item selected in the Reference Field drop down list field.
Also, select the Supplement drop down arrow to choose the attributes to include in the Supplement field for postings. When attributes are selected here, they will take precedence over the item selected in the Reference Field drop down list field.
All actions performed by the Reinit All, Start All, Stop All, Start, Stop, New, and Delete are logged in the User Activity Log in the Configuration Activity Group under the IFC_CONFIG_CHANGED Activity Type.
SC/SFAA new parameter has been introduced (GENERIC - POTENTIAL PROPERTY DETAILS) that allows to load potential figures per property when active.
A property selection LOV has also been added to the Potential main screen besides the 'Calculate' button and the potential versus actuals comparison will then only be shown for the selected properties. Properties available for selection in that LOV depend on the marketing region, marketing city or hotel that has been defined for the potential.
This new report calculates catering revenues and covers for up to three different statuses over a given date range, and can be grouped by Event Types, Meal Periods, or Market Segments. It can be used as a forecast report when leaving the production date range empty, or as a production report, when defining the required production date range on the report parameter form. Revenue types and event types for calculation of average check can also be defined on the parameter form. The revenues and covers for last year over the same date range are also shown on the report. When the flag ‘Page Break’ is checked on the report parameter form, revenues are calculated and printed separately for each Sales Manager.
A total by revenue group prints at the end of the report.
It is now possible to completely delete sales information codes of the types listed below, rather than just inactivating them, provided that the appropriate code is not in use on any past or future record. In order to be able to delete the code, it has to be set ‘inactive’ first’
The ‘meeting rooms on the web’ functionality has been greatly improved and extended. It is now possible to create Inquiries from the web, as well as firm business blocks. The business blocks that can be created can either be room only, catering only, or can contain both rooms and catering. It is possible for web users to search for and look at existing business blocks, and copy or update elements of these business blocks and events. When linked to a live property, catering packages and resources can be added to business blocks from the web. We also added the possibility to add business block notes, and to print contracts from the web. Deposit and payment requirements for clients using the web booking functionality are much more flexible now through the use of credit ratings, which allow different deposit rules to be applied to different customers when booking. Rate Code and Catering Package availability are now both checked for those business blocks that include guest rooms as well as catering packages. Please note: When connecting the web booking functionality to SFA, event resources and catering packages are not available to book for properties that are remote to SFA and linked through OXI. These entities can be booked via SFA for properties that are live in the same schema as SFA though.
GENERICThe new form, PROPERTY_DELETE, is able to start and monitor property deletion. The form can be selected from Utilities>Data>Delete Property. The permission DELETE_PROPERTY needs to be granted to enable this functionality. To start the form, a password that is similar, or the same as, the reset data utility is used.
OBIAdded the following dimensions and facts to the Reservation History and Future Reservations cubes to give users the possibility to use the 2 cubes to compare past and future data based on channel and insert source.
Dimensions:
Ins Source
Ins Source All
Ins Source Type
Ins Source
Ins Source Desc
Channel
Channel All
Channel
Measures:
Arrival Guest
Arrival Resv
Arrival Room
Avail Room
Adults
Children
Cancellations
Cancel Rooms
Introduce the ability to report on Fiscal Year in BI. With this feature, users are now able to choose to report on either the Calendar Year, Fiscal Year or Both.
This feature is controlled by two new application settings: "OBI Reporting Year Mode" and "OBI Fiscal Year Start Month" and applies to all properties within the environment.
The change to these 2 application settings will apply to all future cube builds (post change). If it needs to be reflected on the previous builds as well then a Full Build of the cubes is required.
When the OBI REPORTING YEAR MODE is set to FY or BOTH, then the Financial Year cube elements become available in the following cubes:
Add 2 permissions to control users' access to dropping Cubes and Analytical Workspaces
A change has been made to send the Datamart messages when the Datamart is populated rather than wait till the Night Audit has been completed. This will ensure that the information is current in the event Income Audit is being used at the property.
New report in the OBIEE shared folder called Purge All Cache (under the OperaBI folder). Using this report will clear the report cache.
Clearing the BI Server Cache on a regular basis helps maintain OBI performance. Users with the OBI Enterprise (OBIEE) license (OPB_<version number> OBI Enterprise (OBIEE - Multiple Properties) have the option to clear the BI Server Cache from the front-end, as opposed to directly accessing the OperaBI.rpd file on the BI application server. Users can access the OperaBI report in the Shared Folders in OBI>Answers.
By simply selecting Shared Folders>Purge All Cache, files from the application server (i.e. D:\oracle\OracleBIData\cache) are removed. Several additional benefits can be gained by using the OperaBI Report:
Add Meal Periods (MP) to the POS cube.
This was accomplished by introducing a new dimension "Hour" which allows the aggregation at the hour level.
Users can then use the query below in the HOUR attribute to group the hours of the day into Meal Periods. This allows a maximum flexibility to break down the MP and also control which hours fall within which MP.
The labels of the different Meal Periods as well as the hours included in each MP can be updated in the query as needed: (refer to the test doc. attached to the scr for screen shots)
CASE
WHEN Hour.Hour IN ('05','06', '07', '08','09') THEN
'Breakfast'
WHEN Hour.Hour IN ('10','11') THEN
'Brunch'
WHEN Hour.Hour IN ('12', '13', '14') THEN
'Lunch'
WHEN Hour.Hour IN ('15','16') THEN
'Tea Time'
WHEN Hour.Hour IN ('17','18') THEN
'Early Bird'
WHEN Hour.Hour IN ('19', '20', '21','22') THEN
'Dinner'
WHEN Hour.Hour IN ('23','00','01', '02', '03','04') THEN
'Late Dinner'
ELSE
Hour.Hour
END
** A FULL Build of the POS Cube is required after the implementation of this change **
ORS/OISA new check box has been added to the MEMBERSHIP_SETUP form under the Criteria tab with the label "BB Cross Memberships". This will only display if you have the BBSP or the BBSG check box checked. This will identify Back to Back Cross Memberships and they will be sent to the Exceptions (MEM_TRAN_EXCEP) form once checked out and points have been calculated and identified as a Back to Back stay.
Additionally a check box has been added to the Membership Calculation Rule (MEMBERSHIP_POINTS) form with the label "Exclude BTBS". This check box will only display when the Program Type =Tier. This will identify a Back to Back stay and the stays will be sent to the Exceptions (MEM_TRAN_EXCEP) form once points have been calculated and only the first stay will be awarded the Tiered points where the Exclude BTBS was selected. All other qualified points will be awarded to the additional stays.
New functionality has been introduced on the OCIS Membership Module that will allow grouping of Membership Rules.
By grouping Point Calculation Rules, a property can offer a group-wide promotion together with hotel-specific promotions during the same time period and these rules can then be set under separate groups. This way the system will only credit the points based on 1 of the rules within each group which then credits the most award points to the member. But only 1 Group at a time will qualify for the reward points and if more than 1 does qualify, then the group that will reward the most points, will be the group that will be used. In case two or more rule groups score the same amount of points the sequence will determine which of the Rule Groups will be credited.
A new application setting has been introduced and will be available when the Global Parameter, RATE FLOOR is active. This setting will allow more flexibility for the Rate Floor functionality that currently exists.
The setting is available at the Property level and is as follows:
Application Setting: RATE FLOOR LEVEL OF CONTROL
Available Values: RATE LEVEL or ROOM TYPE LEVEL
When the value selected is ROOM TYPE LEVEL, there will be a new field in the Room Type configuration (RMEDIT) at the property level.
This will dictate the lowest rate that can be entered on the Rate Details Screen for that Room Type. Each Room Type can have a different value.
There has also been a new permission added:
Permission Group: RATEMGMT CONFIG
Parameter Name: RATE FLOOR OVERRIDE
When this permission is granted to a user, they will have the ability to override a rate amount entered on the Rate Details screen that is lower than the Rate Floor.
Keep in mind that once this has been overridden, it will not prompt the user again unless the Rate Floor on a room type that is on the rate detail, is changed.
New ORS reservations export introduced, users can now create a new general reservations export in ORS which will export reservations data for mutliple resorts from the same CRO (or CROs, or list or resorts)
The pre export procedures for the new exports and their usage are:
======================================================
PROCEDURE pre_export_prop_lst1( in_resort_lst VARCHAR2,
in_from_date DATE DEFAULT pms_p.business_date,
in_to_date DATE DEFAULT pms_p.business_date,
in_date_type VARCHAR2 DEFAULT 'ARRIVAL_DATE');
======================================================
PROCEDURE pre_export_cro1( in_from_date DATE DEFAULT pms_p.business_date,
in_to_date DATE DEFAULT pms_p.business_date,
in_date_type VARCHAR2 DEFAULT 'ARRIVAL_DATE',
in_cro_code VARCHAR2 DEFAULT pms_p.cro_resort);
======================================================
PROCEDURE pre_export_prop_lst2( in_resort_lst VARCHAR2,
in_from_date DATE DEFAULT pms_p.business_date,
in_to_date DATE DEFAULT pms_p.business_date,
in_date_type VARCHAR2 DEFAULT 'ARRIVAL_DATE');
======================================================
PROCEDURE pre_export_cro2( in_from_date DATE DEFAULT pms_p.business_date,
in_to_date DATE DEFAULT pms_p.business_date,
in_date_type VARCHAR2 DEFAULT 'ARRIVAL_DATE',
in_cro_code VARCHAR2 DEFAULT pms_p.cro_resort);
ORMSWith this SCR we introduce a new Price Configuration screen in ORMS ADF11 that allows the user to set up different Hurdle Steps for different time periods and DOW. In addition users will now be able to define different hurdles per Room Type within the same Yield Category and it also supports 2nd adult surcharge and Child Bucket Handling for Daily Rates. Furthermore, then Upsell Configuration has been separated from the Daily Rate calculation.
