Importing Blocks and Room/Rate Grid
-
"BLK_Unique_ID_Block" CSV column value is stored in "ORIG_ALLOTMENT_HEADER_ID" column.
-
"BLK_Start_Date" CSV column value is stored in the "original_begin_date" column.
-
Multiple Rate Codes and multiple Owners cannot be imported.
-
Multiple Rate Codes and Owners are not allowed in import CSV.
-
If the Ability to Quote Rates in Foreign Currencies OPERA Control is active, it is expected that the import file has property configured currency.
-
Block Begin Date must fall between Rate Code date range.
-
A group profile is automatically created and linked to Blocks.
Note:
Once all files have been imported successfully, you need to synchronize the data, so the revenue tables for the imported blocks are up to date. For more information, see Synchronizing Block OccupanciesTable 24-4 Blocks
Column | Description | Max Data Length | Sample Data | Mandatory |
---|---|---|---|---|
BLK_Unique_ID_Block |
Unique ID value for Block in the uploaded csv files for Data type "Block" within an Import cycle. |
200 |
Ex: (40001, 40002) |
|
BLK_Start_Date |
The Start Date of the Block. The format must be 'YYYYMMDD.' |
Date |
Ex: (20210121) |
|
BLK_End_Date |
This field should not be less than the Block Start Date/Business Date. |
Date |
Ex: (20210122) |
|
BLK_Name |
The Block Name. |
40 |
Ex: (Wedding Block) |
|
BLK_Code |
Group Code. If OPERA Control "Block Code Template" is active, then the block code must be as per the template defined. For better consistency, follow the setting "Block Code Generation Pattern." |
20 |
Ex: (201110WEDD) |
|
BLK_Room_Status |
Business Block Status. The Business Block Status must be pre-configured in OPERA Cloud. |
4 |
Ex: (INQ) |
|
BLK_Account_ID |
The Primary Account ID linked to the Block. Unique ID value for Account profile in the Uploaded csv files for Data type "Account" for an Import cycle. |
200 |
Ex: (200010) |
|
BLK_Contact_ID |
The Primary Contact ID linked to the Block. Unique ID value for Guest/Contact profile in the Uploaded csv files for Data type "Guest/Contact Profiles" for an Import cycle. |
200 |
Ex: (300010) |
|
BLK_Owner |
The Business Block Owner Code. |
10 |
Ex: (All)) |
|
BLK_Market_Code |
The Main Market Code. The Market Code must be pre-configured in OPERA Cloud. |
10 |
Ex: (CORP) |
|
BLK_Source |
Origin of booking that is attached to this business block. The Source must be pre-configured in OPERA Cloud. |
20 |
Ex: (CALL) |
|
BLK_Reservation_Type |
The Reservation Type attached to the Block. The Reservation type must be pre-configured in OPERA Cloud. |
8 |
Ex: (GNON) |
|
BLK_Inventory_Control |
The number of days can be extended from the End Date even after expiration. The OPERA Control parameter "Elastic" should be active to import Elastic Inventory. |
1 |
Ex: (Elastic, Non Elastic) |
|
BLK_Decision_Date |
Decision Date for Rooms. The format must be 'YYYYMMDD.' |
DATE |
Ex: (20210122) |
|
BLK_Followup_Date |
Rooms Follow-up Date. The format must be 'YYYYMMDD.' |
DATE |
Ex: (20210122) |
|
BLK_Catering_Only |
Flag which specifies if this is a Catering Only Booking. |
1 |
Ex: (Y, N) |
|
BLK_Origin |
Channel code attached to the business block. |
20 |
Ex: (Default) |
|
BLK_Allotment_Origin |
Determines which application created the Business block: PMS or SC. |
3 |
Ex: SC |
|
BLK_Type |
The Block Type. The OPERA Control Parameter "Business Block Type" should be active. The Block Type must be pre-configured in OPERA Cloud. |
8 |
Ex: (G, W) |
|
BLK_Room_Owner |
Rooms Sales Manager ID. In case the value is not populated in CSV, the value is defaulted to ALL. |
10 |
Ex: (ALL) |
|
BLK_Rate_Code |
The rate code for which this record applies. The Rate Code must be pre-configured in OPERA Cloud. |
8 |
Ex: (RACK) |
|
BLK_Currency |
Currency Code attached to the Business Block. The Currency Code must be pre-configured in OPERA Cloud. The sequence
for the Currency import is as follows:
|
3 |
Ex: (USD) |
|
BLK_Print_Rate_YN |
Default value used against Block reservations. |
1 |
Ex: (Y, N) |
|
BLK_Cuttoff_Date |
Date on which the available inventory for the block will be cut-off by the system. The format must be 'YYYYMMDD.' In case both the Cut Off date and Cut Off days is populated in Csv, then consider Cut Off date for Import. The OPERA Control parameter "CutOff" should be active. |
DATE |
Ex: (20210122) |
|
BLK_Cuttoff_Days |
The number of days prior to Arrival that the whole block will be cut off. |
2 (The Number must be between 0 to 99) |
Ex: (5, 6) |
|
BLK_Catering_Owner |
Catering Sales Manager ID. In case value is not populated in CSV, the value is defaulted to ALL. |
10 |
Ex: (ALL) |
|
BLK_Catering_Status |
The Catering Status. The Currency Status must be pre-configured in OPERA Cloud. If left Blank, the value from Property catering Currency will be populated. This column should be populated when the OPERA control parameter "Use single Block status for Rooms and Catering" is not active. |
4 |
Ex: (INQ) |
|
BLK_Event_Attendees |
The number of Attendees for the Catering Events. This field should be populated when the catering Status is populated. |
4 (The Number must be between 0 to 9999) |
Ex: (10) |
|
BLK_Resource_Discount |
The default discount percentage applied to the catering items. |
3 (The Number must be between 0 to 100) |
Ex: (20) |
|
BLK_Onsite_Name |
The Group Representative. |
40 |
Ex: (Adam) |
|
BLK_Function_Type |
The Type of Catering Function. |
60 |
Ex: (Wedding) |
|
BLK_PostAs |
The Catering Info board name. |
50 |
Ex: (Adam and Jill's Wedding) |
|
BLK_Note1 |
Block Notes 1 |
2000 |
Ex: (Outside Ceremony at 10:00AM) |
|
BLK_Note2 |
Block Notes 2 |
2000 |
Ex: (Father of the Bride pays everything) |
|
BLK_Note3 |
Block Notes 3 |
2000 |
Ex: (The block's room charges will be charged to the company's visa.) |
Table 24-5 (Block) Room and Rate Grid
(Block) Room and Rate Grid | ||||
---|---|---|---|---|
|
||||
Column |
Description |
Max Data Length |
Sample Data |
Mandatory |
BLK_Unique_ID_Block |
Unique ID value for Block in the uploaded csv files for Data type "Room and Rate Grid" within an Import cycle. |
200 |
Ex: (40001, 40002) |
|
BLK_Room_Type |
This is the Room Type booked for this allotment. The Room Type must be pre-configured in OPERA Cloud. |
20 |
Ex: (STDK, STDQ) |
|
BLK_Block_Date |
Date of Allotment for which the specified room category is booked. The format must be 'YYYYMMDD.' This date should span within the Block dates for which the Grid is uploaded. |
Date |
Ex: (20210122) |
|
BLK_Rate_Amount_1 |
1 person rate |
Ex: (100) |
||
BLK_Rate_Amount_2 |
2 person rate |
Ex: (150) |
||
BLK_Rate_Amount_3 |
3 person rate |
Ex: (200) |
||
BLK_Rate_Amount_4 |
4 person rate |
Ex: (225) |
||
BLK_Rate_Amount_AP |
Additional person rate. |
Ex: (250) |
||
BLK_Occupancy_1 |
Projected number of rooms with Single occupancy for the particular room type & date to which this record corresponds. |
4 (The Number must be between 0 to 9999) |
Ex: (1) |
|
BLK_Occupancy_2 |
Projected number of rooms with Double occupancy for the particular room type & date to which this record corresponds. |
4 (The Number must be between 0 to 9999) |
Ex: (2) |
|
BLK_Occupancy_3 |
Projected number of rooms with Triple occupancy for the particular room type & date to which this record corresponds. |
4 (The Number must be between 0 to 9999) |
Ex: (3) |
|
BLK_Occupancy_4 |
Projected number of rooms with Quadruple occupancy for the particular room type & date to which this record corresponds. |
4 (The Number must be between 0 to 9999) |
Ex: (1) |
Parent topic: About Data Import