OPERA Controls — Blocks

The following tables outline the functions, parameters, and settings that can be configured in the OPERA Controls Blocks group.

Table 10-9 OPERA Controls — Blocks Functions

FUNCTION	RELATED FUNCTION / PARAMETER / SETTING	DESCRIPTION
BUSINESS BLOCK [BUSINESS_BLOCK]		Enables the ability to reserve multiple rooms of various room types between a start and end date range. Rooms can be held in non-deduct or deduct status and the inventory held can be washed manually or automatically based on a wash cycle. Individual reservations are then input via rooming list to deduct rooms from the block inventory rather than house inventory.
ALTERNATE DATES [ALTERNATE_DATES]		Exposes Alternate Date fields on Block Header; these fields are used to identify alternative start dates for the block and all specified dates are then shown in the result grids.
BLOCK RESTRICTIONS [SET_BLOCK_PICKUP_RESTRICTIONS]		Enables the ability to set restrictions for specific block and specific room types by date.
GROUP ROOMING LIST IMPORT [GROUP_ROOMING_LIST_IMPORT]		Enables the ability to import reservation data from an external file to form basis of rooming list entry for a group block
MASTER SUB ALLOCATIONS [MASTER_SUB_ALLOCATIONS]		Master and Sub allocation for allows for more control over the number of rooms designated for wholesale reservations by allowing for all required inventory to be placed on the Master so that the Sub-Allocation can pull its inventory from the Master. The Master Allocation, in turn pulls the allotted inventory from house availability.
MASTER SUB BLOCKS [MASTER_SUB_BLOCKS]		Enables a 'roll-up' parent/sub hierarchy for group blocks for single or multiple properties. Updates to master blocks can be automatically synchronized to all sub-blocks.
	SYNCHRONIZE MASTER SUB BLOCKS PARAMETER [SYNCHRONIZE_MASTER_SUB]	Enables the synchronization of data from the master block to the sub block.
SALES ALLOWANCE [SALES_ALLOWANCE_ACTIVE]		Activate Sales Allowance Functionality allows you to set an availability ceiling for group rooms on a day-by-day basis, requiring the user to have the Overbook Sales Allowance user task to over book the sales allowance.
TOUR SERIES [TOUR_SERIES]		The tour series functionality allows the setup of reoccurring blocks on a define frequency.
TRACES [BLOCK_TRACES]		Enables the ability to setup actionable date-driven reminders for specific blocks.

Table 10-10 OPERA Controls — Blocks Parameters

PARAMETER	RELATED FUNCTION / PARAMETER / SETTING	DESCRIPTION
ALIAS [BOOKING_ALIAS]		Enables the entry of alias name that can be used instead of a Block name when searching for a block.
ALLOW RATE EDITING WITH RATE CODE [ALLOW_RATE_EDITING_WITH_RATE_CODE]		Provides the ability to change the rate amounts on a block room grid even when a rate code has been linked to the block.
AUTO ASSIGN SUB BLOCK CODE [AUTO_SUB_BLOCK_CODES]		Automatically generates sub block codes. Enables Periodic Tour Series in addition to custom tour series. When Inactive (N),Periodic Tour Series option is not available in Tour Series functionality.
BLANK BUSINESS BLOCK START DATE [DEFAULT_BLANK_BB_START_DATE]		Sets the start date to blank for new block. If not active the Start Date is defaulted to the current business date.
BLOCK CODE TEMPLATE [BLOCK_CODE_TEMPLATE]		Activates the block code template pattern used for Central Reservation Systems.
	TEMPLATE PATTERN SETTING [BUSINESS_BLOCK_TEMPLATE]	Specifies the block code format to be used when a new block is created. Allows the user to configure the naming convention used in automatically generating block codes for new blocks. MON can be used as a code to insert the first three letters of the current month. Many properties have specific block template requirements for Central Reservation Systems. Note: this pattern must match the BLOCK CODE GENERATION PATTERN.
BLOCK CONTRACT GRID [BLOCK_CONTRACT]		Shows the contract as a selectable option in the room rate grid. Contract grid is used to track the inventory commitments for a block. The Contact grid does not affect house inventory, it is only used for tracking purposes.
	AUTOLOAD CONTRACT GRID PARAMETER [AUTOLOAD_CONTRACT_GRID]	When active, the Original Grid is auto loaded into Contract grid. User has an option to 'Stop Auto Load Contract' on a block level.
BLOCK OWNER LOCKING [BLOCK_OWNER_LOCKING]		Once activated, user can select from what block status forward a block owners field will be uneditable.
	BLOCK OWNER LOCKING STATUS SETTING [BLOCK_OWNER_LOCKING_STATUS]	Specifies the status at which the Owner field becomes locked within the block status flow.
BLOCK RANKING [RANKING]		Enables a Ranking field on blocks. The Ranking list field can be used to indicate the rank (or priority) of a block. This field will be editable on for blocks having a status configured as INQUIRY or NON DEDUCT. Ranking is displayed on the Group Rooms Control screen, Function Diary, and the Business Block Short List reports. [PREMIUM]
BLOCK RATE CODE NO OVERLAP [BLOCK_RATECODE_NO_OVERLAP]		Disables blocks with overlapping dates from having the same rate code.
BUSINESS BLOCK TYPE [BUSINESS_BLOCK_TYPE]		This feature allows users to attach a "category of business" designation to each booking. For example, they can identify the booking as a wedding, a tour, a conference, a meeting, a convention, and so on. This information can be used later for reporting purposes.
CATERING ONLY BLOCK		Controls the functionality of the Catering Only check box in the following manner: If the parameter is set to Y and the check box is checked on a block, the Room Details section on the Block Details is hidden. In addition, Room & Rate Grid is not available for this block. User will not be able to allocate inventory for 'Catering Only' block. However, block reservations are allowed for this type of blocks. 'Catering Only' check box is also used in reports. If the parameter is set to N and the check box is checked on a block, no changes applied to the block and the check box is ONLY used for reports.
CONVERSION [CONVERSION]		Enables Conversion field to be available on business blocks. Block conversion gives sales managers a way to assign a likelihood of conversion to blocks.
COPY WITH DATE OPTION [COPY_WITH_DATE_OPTION]		Copies blocks with the option to select a date range from the source block.
CUTOFF [CUTOFF]		Do you want OPERA Cloud to automatically release non-picked up block rooms back to the house on a given date or do you wish to manual manage the release of allocations? Allotted rooms for a group that are not picked up by a certain date or number of days prior to the group’s arrival can be released back to house inventory for pickup by other group or individual reservations. To release all unused allotments at one time, the cutoff function is used. Rooms can be cut off for an individual block or for all blocks at one time. If the cutoff functionality is not activated, then OPERA Cloud will internally see the cutoff values for each of the days of the block as the actual block date and as such internally the rooms will be cutoff on the night that they were due to be used. This function does not affect the manual Cutoff button. A block can still be cutoff manually through the Cutoff button.
ELASTIC BLOCK [ELASTIC_BLOCK]		Activates the elastic block functionality that gives ability to book group reservations outside of the block dates, or for room types not included in the block.
	SELL LIMITS [SELL_LIMITS]	This function provides the ability to define a set number of rooms per room type that can be borrowed from house availability once the total rooms within the block have been picked up. Once the maximum number of rooms in the limit is reached, the user must have the appropriate permissions to continue pick up of reservation above the sell limit. Sell limits are not deducted from inventory and are based on house availability.
	SHOULDER DATES [SHOULDER_DATES]	If the block is marked as Elastic or Sell Limits in the Inventory Control section of the Block Details, shoulder dates can be added to the block prior to the start date and/or following the end date of the block. These dates are marked with red corner on the Rooms Grid. These 2 fields can be used to define a shoulder period start date and shoulder period end date. The start shoulder period will run from the Shoulder Start date until the start date of the block. The shoulder end period will run from the end date of the block to the Shoulder End date.
	MAXIMUM SHOULDER DAYS [MAX_SHOULDER_DAYS]	Some guests may arrive earlier or depart later than the start or end date for a block. This parameter controls the maximum number of days that the start or end date can exceed the group's dates.
ENFORCE BLOCK CODE PATTERN LENGTH [ENFORCE_BLOCKCODE_TEMPLATE_LENGTH]		Enforces the maximum length based on the block code pattern for manual entry when the block code template is not defined. This control is only visible when the control fpr Block Code Template is not active.
LOWEST GUARANTEED RATE [RATE_PROTECT]		Enabled a Rate Protect checkbox on blocks. This is an indicator that no other groups should be booked using rates lower than those assigned to the block that is flagged as rate protect. The rate protect flag can be applied to all or selected dates of the flagged block. (OPERA does not enforce this restriction.) An indicator is displayed on the Group Rooms Control screen for any date that has a rate protect booking. [PREMIUM]
MULTI BLOCK RATES [MULTI_BLOCK_RATES]		When the parameter is active, users can select the Rate Codes for the block from a multi-select Rate Code LOV on the Create Block and Block Details screen. The multiple selected rates display on the Rooming List Pickup screen. If the parameter is not active, the Rate Code LOV only provides a single rate code selection.
	MAXIMUM BLOCK RATES [MAXIMUM_BLOCK_RATES]	If multiple rate codes are selected for a block, the Rate Code field will display a total count of them as a special indiator. If you select more than one rate code, one rate code must be selected as the primary rate code. The primary rate you select will be displayed in Rate Code field and carried over to the Room Grid. If the Elastic check box is selected, or if the Inventory Control value is Elastic or Sell Limits, you may select rate codes to apply to Allotments, Begin and End Shoulder periods, as applicable.
NAME VALIDATION IN ROOMING LIST NAME_VALIDATION_ROOMING_LIST		When enabled, first and last name entries in Group rooming list will require a minimum number of alpha-numeric characters. Last name requires 2 characters and first name requires 1 character. When disabled name field entries will not be validated
NON_COMPETE [NON_COMPETE]		Makes Non-Compete flag available on business blocks. The Non Compete flag on a block can be used to indicate that no competing accounts (accounts having the designated NC Industry code) should be booked at the same time as this block. The non compete flag may be applied to all or selected dates of the flagged block. (OPERA Cloud does not enforce this restriction.) An indicator is displayed on the Group Rooms Control screen and Function Diary for any date that has a non compete booking.
OCCUPANCY SPLIT PER ROOM TYPE [USE_OCCUPANCY_FOR_ROOMBLOCK]		Determines whether rates for blocks can be split by occupancy or not. When the parameter is Y, room grids will be built based on room type and occupancy. The number of rooms for each occupancy level must be entered separately. This will result in a more accurate forecasting of the number of persons arriving with a group as well as the total revenue if rooms are priced differently based on the number of people in the room. When the parameter is set to N, room grids are built using only the total number of rooms of each room type and forecasted revenues are based on single occupancy of all rooms.
RATE CODE MANDATORY BLOCK HEADER [MANDATORY_RATE_CODE_BLOCKS]		Determines whether or not a rate code is a mandatory field for blocks. If rate code is not mandatory, blocks can be made without a rate code.
RETURN BLOCK TO HOUSE [BLK_TO_HOUSE]		After a block has been cutoff, this parameter can either return the unused rooms ( cancelled block reservations or no shows from a block) to house availability or maintain them for the group. If this is not active, the rooms for cancelled reservations will always be returned to the block first, even after the cutoff date. However, the next night audit will cut the rooms off again.
ROOM TRANSACTION CODE ON BLOCK [ROOM_TRX_CODE_ON_BLOCK]		When active, the field Room Revenue Transaction Code is available on the block, Room Details section of the Block Details screen. It identifies the Transaction Code to be used when posting the room charge for reservations linked to the block. If the code entered is a valid Lodging Transaction Code, that Transaction Code is used when posting Room Revenue for Reservations linked to the current block. If the Transaction Code is not valid, or the field is left blank, then the Transaction Code linked to the Rate Code will be used. Or, if no Rate Code is attached to the Block, the Default Transaction Code will be used.
SHIFT DATE [SHIFT_DATE]		Enables the ability to move a block to a new arrival and departure dates when a block grid already exists. If there are any reservations (beside PM reservations) attached to the block, you will not be able to shift dates for the booking.
UNIQUE BLOCK CODE [UNIQUE_BLOCKCODE]		This parameter controls whether or not each block must have a unique block code. If the control is set to "N", the same block code can be used for several blocks. In the user interface, this will change certain features such as selecting a block code on a reservation, as the user will in the case of duplicate codes need to select the block they want to use based on and assuming that a different block name has been entered. Internally, OPERA stores the block ID so it know exactly which block the reservation is associated to for the purposes of availability, statistics, etc.
USE SINGLE BLOCK STATUS FOR ROOMS AND CATERING [USE_SINGLE_BLOCK_STATUS]		This parameter is only available when OPERA Controls Catering Eventsis active. It controls the visibility of the Block Catering Status the Block. When this parameter is active, the Catering Status is hidden. Instead, the rooms, catering, and event statuses are controlled by the Block Status. When this parameter is set to N, the Catering Status and Room Status are visible on a block.
WASH SCHEDULE [WASH_SCHEDULE]		Enables you to configure the wash schedule.
CONVERSION		Providing sales managers with a way to grade the likelihood of conversion (signing a contract) to blocks. The conversion rating is selected in the Block Overview panel and is visible on the Group Rooms Control screen and on the Function Diary. The conversion rating is also displayed in reports including the Group Rooms Reservation Sheet and the Business Block Short List reports. [PREMIUM]
NON-COMPETE		The Non Compete flag on a block can be used to indicate that no competing accounts (accounts having the designated NC Industry code) should be booked at the same time as this block. The non compete flag may be applied to all or selected dates of the flagged block. (OPERA Cloud does not enforce this restriction.) An indicator is displayed on the Group Rooms Control screen and Function Diary for any date that has a non compete booking. [PREMIUM]

Table 10-11 OPERA Controls — Blocks Settings

SETTING	DESCRIPTION
BLOCK CODE GENERATION PATTERN [DEFAULT_BLOCK_CODE_TEMPLATE]	Defines the block code pattern to auto generate the block code. Allows the user to configure the naming convention used in automatically generating block codes for new blocks. If BLOCK CODE TEMPLATE is active, the BLOCK CODE GENERATION PATTERN must match the TEMPLATE PATTERN SETTING. Valid values: 'Y', 'YY', 'YYYY' for year 'M', 'MM', for month number 'MON' for the month name 'D', 'DD' for the day number '?' to define the increment position 'A' for any alpha
BLOCK CODE VALIDATION RULE [BLOCK_CODE_VALIDATION_RULE]	Controls the validation of when a specific block code can be reused. Note: this setting is only available when the Unique Block Code parameter is inactive. Valid values: NON_OVERLAPPING_DATES START_OF_INVENTORY_WEEK For example, if the parameter value is set to 90 and the block is 91 nights, the block room nights and revenue will not be calculated when you access the Block presentation until you select the Calculate link.
CALCULATE BLOCK STATISTICS	When a property defines a variable for this setting, for example, 90 days, the room and revenue details will not be calculated automatically for bookings lasting longer than 90 days when opening the block screen in order to improve the speed with which the screen opens. If a block lasts longer than 90 days, user can click on 'Calculate' button on the Block Overview in order to have the statistics displayed on the Block Overview.
CATERING STATUS WHEN COPYING AN EVENT [COPY_CATERING_STATUS]	Identifies the catering status when copying an event. Valid values: All status codes where the catering deduct inventory = N and starting status = Y.
COPY BOOKING NOTES [COPY_BOOKING_NOTES]	Copies booking notes by default. Valid values: Yes No
COPY BOOKING STATUS [COPY_BOOKING_STATUS]	Identifies the booking status while copying a booking. Valid values: All status codes where the starting status = Y.
DEFAULT CATERING STATUS	This is the default catering status assigned to a block when new blocks are created. Valid values: All status codes where the catering deduct inventory = N and starting status = Y.
DEFAULT NEW BLOCK STATUS [DEFAULT_NEW_BLOCK_STATUS]	Identifies the default block status for new blocks. Valid values: All status codes where the starting status = Y.
MAX BLOCK AVAIL DAYS [MAX_BLOCK_AVAIL_DAYS]	Defines the maximum number of days from the current business date, for which a block can be created.
MAXIMUM BLOCK ADVANCED BOOKING DAYS [MAX_BLOCK_ADV_BOOKING_DAYS]	Defines how far into the future from the current business date a group block can be created.
MAXIMUM NUMBER OF NIGHTS FOR BLOCK RESERVATION [MAX_BLOCK_DAYS]	Defines the maximum number of nights a block reservation can be booked.
MAXIMUM NUMBER OF BLOCK DAYS [MAXIMUM_NIGHTS_FOR_BLOCK_RESERVATIONS]	Defines the maximum number of nights allowed for a block.
PROFILE PROMPT FOR BLOCKS [PROMPT_PROFILE_BB]	This control determines if the user will be prompted to associate a profile to a block if one has not been attached. The control can be set to N (None), P (Prompt) or R (Require a profile for all blocks).
ROOMING LIST RESERVATION METHODS [RESV_METHOD_TYPE]	Identifies the reservation methods that enable entry of the rooming list due date. Valid values: All booking methods.
TURN BOOKING INTO ACTUAL UPON [TURN_BOOKING_INTO_ACTUAL_UPON]	Turns a booking into status ACTUAL upon booking arrival / booking departure. Valid values: ARRIVAL (bookings turn to ACTUAL on the booking arrival date) DEPARTURE (bookings turn to ACTUAL on the booking departure date) NOTUSED (bookings do not turn to ACTUAL) When Not Used is selected, the booking will NOT be automatically updated to ACTUAL status, users will have to change the booking status manually.