Data Import
Note:
Profile match and merge are not supported.The following data types (entities) can be imported based on the Cloud Service(s) and OPERA Controls that are active in your property.
Table 21-1 Data Types
| Data Type | Notes | Template Filename |
|---|---|---|
|
Guest /Contact Profiles |
Profile match and merge is not supported. |
Guest_Contact_Profiles.csv |
|
Sales Accounts (Travel Agent, Company, Source) Profiles |
Profile match and merge is not supported. |
Accounts.csv |
|
Relationships (Account/Contact relationship only) |
Available when the Relationships OPERA Control is active. |
Relationships.csv |
|
Reservations (Future) |
Room type availability (including sell limits) are checked; reservations exceeding the room type availability will not be imported. Block pickup is not possible; rooms are deducted from House. Use Rooming List import instead. |
Reservations.csv |
|
Blocks and Room/Rate Grid (Current and future only) |
Only the primary Block, Account, and Contact will be imported. 3 Block Notes can be imported. |
Blocks.csv Room_And_Rate_Grid.csv |
|
Catering Events |
Available when the Simple Events or Catering Events OPERA Control is active. Current/Future Events Only. Event Forecast information will be imported for each Event. Only four Forecast Revenue Types and their corresponding Forecast Revenue will be imported. If any notes are populated in the CSV file, the Note Type defaults to "Event" and the Note Title is derived from the Note Type. Only three event notes will be imported. The Rental Code corresponding to the Rental Amount will always be "Custom.". Take this into account during the import process. |
Events.csv |
|
Sales Activities |
Available with an Oracle Hospitality OPERA Cloud Service, Sales and Event Management Standard Edition or Sales and Event Management Premium Edition subscription. Available with an Oracle Hospitality OPERA Cloud Service, Sales and Event Management Standard Edition or Sales and Event Management Premium Edition subscription. Only the primary Account and Contact will be imported. |
Activities.csv |
Note:
Each data file can have a maximum file size of 10MB. You can upload and import multiple files per data type.
Only one import cycle per property is permitted at any given time.
The data import utility is intended for all entities to be uploaded, validated, and imported in one cycle to ensure data consistency.
You have 14 days from the first successful file upload to complete the data import cycle. If the data import cycle has not been completed in 14 days, you will need to restart the data import process again.
Data import user activity is tracked in the +changes log under the Miscellaneous group and Import Data action type.
Data File Requirements and Considerations
The upload data files must meet the following requirements:
-
All the mandatory columns should be present in the template along with values.
-
Column data must meet (not exceed) the OPERA Cloud field length requirements.
-
Column data only contains western characters.
-
String values are imported 'as-is' in term of letter case.
-
Unique Id's (primary key) in each data type must not be used in another file for same data type in the same import cycle. For example: if you are uploading two files Account01.csv and Accounts02.csv for Accounts data type, a ACC_Unique_ID_Account value specified in file Account01.csv cannot be used in Account02csv or any other files for the same data type within the same import cycle.
-
The order/sequence of the columns can be different.
-
All column names must match with respective template provided.
-
The columns names are case-insensitive.
-
Date column values must be in YYYYMMDD format.
-
There must not be any new line characters in the CSV files.
-
The uploaded file for a data type must not contain any additional header columns which are not part of template.
-
Non-mandatory columns can be excluded from upload file.
Any reservation exceeding the inventory checks in place in OPERA Cloud will not be imported. These records will be generated in the error file after the import process is completed. Ensure that the files uploaded for data type Reservations, the cumulative number of rooms for a room type in all the files do not exceed the inventory checks in place.
Data Types (Entities) and Data Elements
Guest / Contact Profiles
-
Mandatory columns are marked in bold.
-
The Keep History YN and ActiveYN fields for Guest/Contact profiles default to Y for all imported profiles.
Table 21-2 Guest / Contact Profiles
| Column Name | Description | Max Data Length | Sample Data | Mandatory |
|---|---|---|---|---|
| IC_Unique_ID_Ind_Contact (PK) |
Unique ID value for Guest/Contact Profiles in the uploaded csv files for data type Guest/Contact Profiles within an import cycle.
|
200 |
Ex: (30001, INC20001) |
Y |
| IC_Contact_YN |
|
N/A |
Ex: (Y, N) |
Y |
| IC_Last_Name |
The Last name of an Guest/Contact Profile name. |
40 |
Ex: (Smith, Brown) |
Y |
|
IC_Middle_Name |
The Middle name of an Guest/Contact Profile name. |
40 |
Ex: (David, James) |
|
|
IC_First_Name |
The First name of an Guest/Contact Profile name. |
40 |
Ex: (Robert, John) |
|
|
IC_Profile_Language |
Primary language used for the profile. The language code needs to be pre-configured in OPERA Cloud. |
20 |
Ex: (DE, E, RU) |
|
|
IC_Title |
The title of the Individual. The Title code needs to be pre-configured in OPERA Cloud. |
20 |
Ex: (Mr., Mrs., Dr.) |
|
|
IC_Nationality |
Nationality of the Individual. The Title code needs to be pre-configured in OPERA Cloud. |
20 |
Ex: (IND, US) |
|
|
IC_Position |
The business title for the Guest/Contact Profile. |
60 |
Ex: (Director) |
|
|
IC_Owner_Code |
Owner Code associated with the Guest/Contact Profile. If blank value is provided, it will be defaulted to ALL. |
10 |
Ex: (ALL) |
|
|
IC_VIP_Code |
VIP Code associated with the Guest/Contact Profile. The VIP code needs to be pre-configured in OPERA Cloud. |
20 |
Ex: (VIP, VVIP) |
|
|
IC_Address_Type |
The address type code. The address code needs to be pre-configured in OPERA Cloud. |
20 |
Ex: (HOME, BUSINESS) |
|
|
IC_Address_Line1 |
The first line of street address. |
80 |
||
|
IC_Address_Line2 |
The second line of street address. |
80 |
||
|
IC_Address_Line3 |
The third line of street address. |
80 |
||
|
IC_Address_Line4 |
The fourth line of street address. |
80 |
||
|
IC_City |
The City of this address. |
40 |
||
|
IC_Postal_Code |
The Postal Code of the address. |
15 |
||
|
IC_Postal_Code_Ext |
The Postal Code Extension of the address. |
20 |
||
|
IC_Country |
The Country code of the address; pre-configured in OPERA Cloud. |
40 |
||
|
IC_State |
The State code of the address; pre-configured in OPERA Cloud. |
40 |
||
|
IC_Address_Language |
The Language code used for the address; pre-configured in OPERA Cloud. |
20 |
||
|
IC_Ref_Currency |
Currency code to be used for the commission payment; pre-configured in OPERA Cloud. |
20 |
||
|
IC_Communication_Type1 |
The Communication type code; pre-configured in OPERA Cloud. |
4000 |
||
|
IC_Communication1 |
The value for the communication for IC_Communication_Type1. |
4000 |
||
|
IC_Communication_Type2 |
The Communication type code; pre-configured in OPERA Cloud. |
4000 |
||
|
IC_Communication2 |
The value for the communication for IC_Communication_Type2. |
4000 |
||
|
IC_Communication_Type3 |
The Communication type code; pre-configured in OPERA Cloud. |
4000 |
||
|
IC_Communication3 |
The value for the communication for IC_Communication_Type3. |
4000 |
Ex: (xxx@xxxxx.xxx) Code: EMAIL |
Sales Account Profiles (Company/Agent/Source)
-
Mandatory columns are marked in bold.
-
The ActiveYN field for Accounts defaults to Y for all imported profiles.
Table 21-3 Sales Account Profiles (Company/Agent/Source)
| Column Name | Description | Max Data Length | Sample Data | Mandatory |
|---|---|---|---|---|
|
ACC_Unique_ID_Account (PK) |
Unique ID value for Sales Account in the uploaded csv files for data type Accounts within an import cycle. |
Ex: (40001, AC40001) |
Y |
|
|
ACC_Profile_Type |
The type of sales account. The account type can be TA, Source, and Company. |
Ex: ( TA, Source, Company) |
Y |
|
|
ACC_Name |
Name of the account profile. |
80 |
Ex: ( Company Name, Source Name) |
Y |
|
ACC_Name2 |
Second name of the account profile. |
80 |
||
|
ACC_Name3 |
Third name of the account profile. |
80 |
||
|
ACC_Profile_Language |
Primary language of the profile; pre-configured in OPERA Cloud. |
20 |
Ex: (DE, E, RU) |
|
|
ACC_Address_Type |
The address type code; pre-configured in OPERA Cloud. |
80 |
Ex: (HOME, BUSINESS) |
|
|
ACC_Address_Type1 |
The first line of street address. |
80 |
Ex: 100 West Monroe |
|
|
ACC_Address_Type2 |
The second line of street address. |
Ex: Suite 100 |
||
|
ACC_Address_Type3 |
The third line of street address. |
|||
|
ACC_Address_Type4 |
The fourth line of street address. |
|||
|
ACC_City |
The City of this address. |
Ex: (Chicago) |
||
|
ACC_Postal_Code |
The Postal Code of the address. |
Ex: (60601) |
||
|
ACC_Postal_Code_Ext |
The Postal Code Extension of the address. |
Ex: (0401) |
||
|
ACC_Country |
The Country code of the address; pre-configured in OPERA Cloud. |
Ex: (US) |
||
|
ACC_State |
The State code of the address; pre-configured in OPERA Cloud. |
Ex: (IL) |
||
|
ACC_Address_Language |
The Language code used for the address; pre-configured in OPERA Cloud. |
Ex: (E, JPN, CHN) |
||
|
ACC_Ref_Currency |
Currency code to be used for the commission payment; pre-configured in OPERA Cloud. |
Ex: (INR, USD) |
||
|
ACC_Communication_Type1 |
The Communication type code; pre-configured in OPERA Cloud. |
4000 |
Ex: (MOBILE) |
|
|
ACC_Communication1 |
The value for the communication for ACC_Communication_Type1. |
4000 |
Ex: 9999999111 |
|
|
ACC_Communication_Type2 |
The Communication type code; pre-configured in OPERA Cloud. |
4000 |
Ex: (WEB) |
|
|
ACC_Communication2 |
The value for the communication for ACC_Communication_Type2. |
4000 |
||
|
ACC_Communication_Type3 |
The Communication type code; pre-configured in OPERA Cloud. |
4000 |
Ex: (EMAIL) |
|
|
ACC_Communication3 |
The value for the communication for ACC_Communication_Type3. |
4000 |
Ex: (xxxx@xxxxx.xxxCode: |
|
|
ACC_Owner_Code |
Owner Code associated with the Guest/Contact Profile. If NULL, it will default to ALL. |
Ex: (ALL , BB) |
Relationships (Account/Contact)
-
Mandatory columns are marked in bold.
-
Records reference the ACC_Unique_ID_Account and IC_Unique_ID_Ind_Contact values from Sales Account and Guest/Contact data files respectively.
-
The default relationship between the account and Guest/Contact profile will be Employer (Type: ACCOUNT) and Employee (Type: CONTACT) relationship.
Table 21-4 Relationships (Account/Contact)
| Column Name | Description | Max Data Length | Sample Data | Mandatory |
|---|---|---|---|---|
|
REL_Unique_ID_Relationship (PK) |
Unique ID value for Relationship in the uploaded csv files for Data type Relationships within an Import cycle. |
200 |
Ex: (50001, RL50001) |
Y |
|
ACC_Unique_ID_Account (FK) |
Foreign Key: Linked Unique ID value of Sales Account Profile. Reference PK value from Sales Account data file within an import cycle. |
200 |
Ex: (40004, AC40004) |
Y |
|
IC_Unique_ID_Ind_Contact (FK) |
Foreign Key: Linked Unique ID value of Guest/Contact Profile. Reference the PK value from Guest/Contact data file within an import cycle. |
200 |
Ex: (30003, INC20003) |
Y |
Sales Activities
-
Mandatory columns are marked in bold.
-
The ACT_Unique_ID_Activity value is stored in "ORIG_WO_NUMBER" field.
-
Child Activities will not be imported.
Table 21-5 Sales Activities
| Name | Description | Max Data Length | Sample Data | Mandatory |
|---|---|---|---|---|
|
ACT_Unique_ID_Activity (PK) |
Unique ID value for Activity in the uploaded csv files for Data type "Activity" within an Import cycle. |
200 |
Ex: (10001, 10002) |
Y |
|
ACT_Start_Date |
The Start Date of the Activity. The format must be 'YYYYMMDD.' |
Date |
Ex: (20210121) |
Y |
|
ACT_End_Date |
The End Date of the Activity. The format must be 'YYYYMMDD.' |
Date |
Ex: (20210122)) |
Y |
|
ACT_Start_Time |
The Start Time of the Activity. This field is available for an Appointment Activity. The format must be ' HH24MI.' |
Time |
Ex: (1400) |
Y |
|
ACT_End_Time |
The End Time of the Activity. This field is available for an Appointment Activity. The format must be ' HH24MI.' |
Time |
Ex: (1500) |
|
|
ACT_Type |
The Activity Type of the Activity. The Activity Type must be pre-configured in OPERA Cloud. |
20 |
Ex: (FOL, SAL) |
Y |
|
ACT_Owner |
The Owner of the Activity. |
10 |
Ex: (ALL) |
|
|
ACT_Class |
Activity Class like TODO, APPOINTMENT. |
20 |
Ex: (TODO, APPOINTMENT) |
Y |
|
ACT_Purpose |
The description of this Activity. |
2000 |
Ex: (Sales Call) |
Y |
|
ACT_Account_ID (FK) |
The Primary Account ID linked to the Activity. Unique ID value for Account profile in the Uploaded csv files for Data type "Account" for an Import cycle. |
200 |
Ex: (200010) |
|
|
ACT_Block_ID (FK) |
The Primary Block ID linked to the Activity. Unique ID value for Block in the Uploaded csv files for Data type "Block" for an Import cycle. |
200 |
Ex: (400010) |
|
|
ACT_Contact_ID (FK) |
The Primary Contact ID linked to the Activity. 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) |
|
|
ACT_Priority |
Priority of the current Activity. |
1 |
Ex: (Y, N) |
|
|
ACT_Completed_Date |
Date on which the Activity was completed. The format must be 'YYYYMMDD.' |
DATE |
Ex: (20210122) |
|
|
ACT_Completed_Time |
Time on which the Activity was completed. The format must be 'HH24MI.' |
Time |
Ex: (1500) |
|
|
ACT_Notes |
Notes about the problem, which can be used by different employees working on this problem. |
4000 |
Ex: (Follow Up call with Customer) |
|
|
ACT_RESULT |
Activity result. This field is available when activity is completed and Activity Results parameter is Active. The Activity Result must be pre-configured in OPERA Cloud. |
2000 |
Ex: (Success) |
Reservations
-
Mandatory columns are marked in bold.
-
Records reference the IC_Unique_ID_Ind_Contact from the Guest/Contact data file.
-
Reservation Status will be auto-populated with values: Reserved (if arrival date is greater than business date), Arrival (if arrival date is equal to business date).
-
Payment method is defaulted to "CASH."
-
Any reservation exceeding the inventory checks in place in OPERA Cloud will not be imported. These records will be generated in the error file after the import process is completed. For files uploaded with the data type "Reservations," ensure the cumulative number of rooms for a room type in all the files does not exceed the inventory checks in place.
Table 21-6 Reservations
| Column Name | Description | Max Data Length | Sample Data | Mandatory |
|---|---|---|---|---|
|
RES_Unique_ID_Reservation (PK) |
Unique ID value for reservation in the uploaded csv files for Data type Reservations within an Import cycle. |
200 |
Ex: (30001, INC20001) |
Y |
|
IC_Unique_ID_Ind_Contact (FK) |
Foreign Key: Unique ID for Linked Guest Profile. Reference PK value from Guest / Contact Profiles data file for an Import cycle. |
Ex: (30001, INC20001) |
Y |
|
|
RES_Confirmation_Number |
This is the confirmation number from OPERA5 or third-party PMS. If provided, res_confirmation_number will be migrated as an external reference number of type 'IMPORTCNF' A new/unique OPERA Cloud confirmation number is generated for each reservation. |
50 |
Ex: ( 3451267345) |
|
|
RES_CRS_Number |
This is the CRS confirmation number from OPERA5 or third-party PMS. res_crs_number will be migrated as an external reference number of type res_external_ref_type_crs (if provided) else 'IMPORTCRS' as default. |
50 |
Ex: (56712345245) |
|
|
RES_External_Ref_Type_CRS |
The External Reference Type code. |
50 |
Ex: (CRS) |
|
|
RES_Reservation_Type |
The Reservation Type code; pre-configured in OPERA Cloud. |
20 |
Ex: (6PM) |
Y |
|
RES_Arrival_Date |
The Arrival Date of the reservation. The format must be YYYYMMDD. |
Ex: (20201121) |
Y |
|
|
RES_Departure_Date |
The Departure Date of the reservation. The format must be YYYYMMDD. |
Ex: (20201125) |
Y |
|
|
RES_Room_Type |
The Room type code; pre-configured in OPERA Cloud. |
50 |
Ex: (KNGN) |
Y |
|
RES_Room_Type_Charge |
The room type to charge code; pre-configured in OPERA Cloud. |
50 |
Ex: (KNGN) |
|
|
RES_Number_Rooms |
The number of rooms for this reservation. |
The value must be between 1 to 150 |
Ex: (1) |
|
|
RES_Number_Adults |
The Number of Adults: Defaulted to 1 in case of Null value. |
The value must be between 1 to 99 |
Ex: (2) |
|
|
RES_Number_Children |
The number of Children. |
The Value must be between 0- 99 |
Ex: (1) |
|
|
RES_Rate_Code |
The Rate Code for the reservation; pre-configured in OPERA Cloud. |
20 |
Ex: (RACK) |
Y |
|
RES_Rate_Amount |
The Rate Amount for the reservation. |
Ex: (100.00) |
Y |
|
|
RES_Currency_Code |
The Currency code for the reservation; pre-configured in OPERA Cloud. |
20 |
Ex: (USD) |
|
|
RES_Fixed_RateYN |
The Fixed Rate Flag.
|
1 |
Ex: ( Y, N) |
Y |
|
Room_Number |
The Room Number allocated (pre-assigned) to the reservation. |
200 |
Ex: (101) |
|
|
RES_Market_Code |
The Market code; pre-configured in OPERA Cloud. |
20 |
Ex: (CORPC) |
Y |
|
RES_Source_Code |
The Source code; pre-configured in OPERA Cloud. |
20 |
Ex: (REF) |
Y |
|
RES_Origin_Code |
The Origin code; pre-configured in OPERA Cloud. |
40 |
Ex: (PMS) |
|
|
RES_Source_Profile_ID (FK) |
Unique ID value of the Source profile in the uploaded csv files for Data type Accounts within an Import cycle. Foreign Key: Unique ID for Linked Accounts Profile. Reference PK value from Accounts Profiles data file for an Import cycle. |
200 |
Ex: (40002, AC40002) |
|
|
RES_Company_Profile_ID (FK) |
Unique ID value for Company profile in the uploaded csv files for Data type Accounts within an Import cycle. Foreign Key: Unique ID for Linked Accounts Profile. Reference PK value from Accounts Profiles data file for an Import cycle. |
200 |
Ex: (400013, AC40003) |
|
|
RES_Travel_Agent_Profile_ID (FK) |
Unique ID value for Travel agent profile in the uploaded csv files for Data type Accounts within an Import cycle. Foreign Key: Unique ID for Linked Accounts Profile. Reference PK value from Accounts Profiles data file for an Import cycle. |
200 |
Ex: (40004, AC40004) |
|
|
RES_Contact_Profile (FK) |
Unique ID value of the Guest/contact profile of uploaded csv files for Data type Reservations within an Import cycle. Foreign Key: Unique ID for Linked Guest Profile. Reference PK value from Guest / Contact Profiles data file for an Import cycle. |
200 |
Ex: (30003, INC20003) |
Blocks
-
Mandatory columns are marked in bold.
-
"BLK_Unique_ID_Block" CSV column value is stored in "ORIG_ALLOTMENT_HEADER_ID" column (Table: Allotment$Header).
-
"BLK_Start_Date" CSV column value is stored in the "original_begin_date" column (Table: Allotment$Header).
-
Past dated Blocks will not be imported.
-
Multiple Rate Codes and Owners are not allowed in import CSV.
-
If the Multi Currency OPERA Control is active, it is expected that the import file has property configured currency.
-
Sell Limits cannot be imported.
-
Blocks having a Start date less than the property date will be imported with an adjusted (Business Date) Start date.
-
Master/Sub Blocks, Packages, and Attachments will not be imported.
-
Production Data and Change Log Data will not be imported.
-
Non-primary Blocks/Account/Contacts will not be imported.
-
Block Begin Date must fall between Rate Code Date Range.
Table 21-7 Blocks
| Name | 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) |
Y |
|
BLK_Start_Date |
The Start Date of the Block. The format must be 'YYYYMMDD.' |
Date |
Ex: (20210121) |
Y |
|
BLK_End_Date |
This field should not be less than the Block Start Date/Business Date. |
Date |
Ex: (20210122) |
Y |
|
BLK_Name |
The Block Name. |
40 |
Ex: (Wedding Block) |
Y |
|
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) |
Y |
|
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)) |
Y |
|
BLK_Market_Code |
The Main Market Code. The Market Code must be pre-configured in OPERA Cloud. |
10 |
Ex: (CORP) |
Y |
|
BLK_Source |
Origin of booking that is attached to this business block. The Source must be pre-configured in OPERA Cloud. |
20 |
Ex: (CALL) |
Y |
|
BLK_Reservation_Type |
The Reservation Type attached to the Block. The Reservation type must be pre-configured in OPERA Cloud. |
8 |
Ex: (GNON) |
Y |
|
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 |
Y |
|
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.) |
(Block) Room and Rate Grid
-
Mandatory columns are marked in bold.
-
If the "BLK_Rate_Code" column value is populated in the Blocks Import csv, then consider the BLK_Rate_Amount (1, 2, 3, 4, AP) for import from the Block Rate Code configuration. Otherwise, consider the values for import from the Room and Rate Grid import CSV file.
-
"BLK_Room_Type" column value within Room and Rate Grid CSV and Block's "Rate Code (Configured Room Types)" value should match. Otherwise, the record will not be imported.
-
"BLK_Block_Date" column value within Room and Rate Grid CSV and Block's "Rate Code (Dates within pricing Schedule)" values should match. Otherwise, the record will not be imported.
-
Room and Rate Grid details will not be imported for a Catering only Block.
-
In case the OPERA Control "Occupancy Split per Room" is not active, only "BLK_Occupancy_1" Occupancy column should be populated.
Table 21-8 (Block) Room and Rate Grid
| Name | 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) |
Y |
|
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) |
Y |
|
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) |
Y |
|
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) |
Events
-
"EVT_Unique_ID_Event" CSV column value is stored in ”ORIG_EVENT_ID" column (Table: GEM$EVENT).
-
The Rental Code corresponding to the Rental Amount will be "CUSTOM" always.
-
More than three Event Notes will not be imported.
-
Past dated Events will not be imported.
-
No Resources will be imported.
-
Packaged Events will not be imported.
-
Non Forecast Revenue will not be imported.
-
Production Data, Change Log data will not be migrated.
-
For Master/Sub/Alternate Event imports, consider the following:
-
Master Event should be placed in CSV before the Sub/Alternate Event.
-
The above should be imported in sequence.
-
-
Events won’t be imported for Out Of Order Function Space.
-
Events will be imported for Blocks which have "BLK_Event_Attendees" populated in Blocks.csv.
-
Return to Inventory status Events should not be imported for active Blocks.
-
You can't do Event Import for a PMS Property if "Simple Events" is Not active.
-
You can import Events in an OSEM property where "Catering Events" is active.
-
Table 21-9 Events
Name Description Max Data Length Sample Data Mandatory EVT_Unique_ID_Event
Unique ID value for Event in the uploaded csv files for Data type "Events" within an Import cycle.
200
Ex: (5010, 5011)
Y
EVT_Block_ID
The Business Block ID.
200
Ex: (400010)
Y
EVT_Type
The Event type of the Event.
8
Ex: (MTG)
Y
EVT_Name
The Event Name of the Event.
60
Ex: (Meeting)
Y
EVT_Status
The Event Status of the Event.
8
Ex: (INQ)
Y
EVT_Start_Date
The Event Start Date. The format must be 'YYYYMMDD.'
DATE
Ex: (20210121)
Y
EVT__End_Date
The Event End Date. The format must be 'YYYYMMDD.'
DATE
Ex: (1500)
Y
EVT_Start_Time
The Event Start Time. The format must be 'HH24MI.'
TIME
Ex: (1500)
Y
EVT_End_Time
The Event End Time. The format must be 'HH24MI.'
TIME
Ex: (1500)
Y
EVT_Expected_Attendees
The Expected number of people attending the Event.
Ex: (20)
Y
EVT_Guaranteed_Attendees
The Guaranteed number of people attending the Event.
Ex: (15)
EVT_Actual_Attendees
The Actual number of people attending the Event.
Ex: (10)
EVT_Space
Reserved Function Space for the Event
8
Ex: (CORA)
EVT_Shareable_YN
This flag indicates whether the Shareable Function Space would be booked as Exclusive or Shareable.This flag should be populated for a Shareable Function Space only.
1
Ex: (Y)
EVT_Master_YN
This flag indicates whether the Event is a Master Event.This flag should be populated if Master/Sub/Alternate Events are to be Imported.
1
Ex: (N)
EVT_Master_Event_Link_ID
Linked Master Event ID. This column should be populated if Master/Sub/Alternate Events are to be Imported.
200
Ex: (5012)
EVT_Link_Type
Event link type like ALTERNATE/SUB EVENT will be stored. This column should be populated if Master/Sub/Alternate Events are to be Imported.
20
Ex: (ALTERNATE)
EVT_Setup_Style
Function Space Setup. This column should be populated when "EVT_Space" is provided.
8
Ex: (CONF)
EVT_Setup_Time
Setup Time in Minutes.
Ex: (15)
EVT_Tear_Down_Time
Teardown Time in Minutes.
Ex: (15)
EVT_Rental_Amount
Rental Amount for the Event.
Ex: (105)
EVT_Display_Doorcard_YN
Display Doorcard Y/N.
1
Ex: (Y)
EVT_Doorcard
Doorcard Signage
50
Ex: (Adam's and Jill's Reception)
EVT_Loud_Event
This flag indicated whether it’s a Noisy Event.
1
Ex: (N)
EVT_Do_Not_Move
Don't move Flag.
1
Ex: (N)
EVT_NOTE1
Event Note 1.
2000
Ex: (Guest book at Entrance)
EVT_NOTE2
Event Note 2.
2000
Ex: (Guest book at Entrance)
EVT_NOTE3
Event Note 3.
2000
Ex: (Guest book at Entrance)
EVT_Forecast_Revenue_YN
This flag indicates, even though resources may be booked, only the forecasted values will drive reporting revenue.
1
Ex: (N)
EVT_Forecast_Revenue_Type_1
The Forecast Revenue Type 1 of the Event.
8
Ex: (BEV)
EVT_Forecast_Total_Revenue_1
The Forecasted Revenue 1 of the Event.
Ex: (20)
EVT_Forecast_Revenue_Type_2
The Forecasted Revenue 2of the Event.
8
Ex: (FOOD)
EVT_Forecast_Total_Revenue_2
The Forecasted Revenue 2 of the Event.
Ex: (30)
EVT_Forecast_Revenue_Type_3
The Forecast Revenue Type 3 of the Event.
8
Ex: (RENTAL)
EVT_Forecast_Total_Revenue_3
The Forecasted Revenue 3 of the Event.
Ex: (100)
EVT_Forecast_Revenue_Type_4
The Forecast Revenue Type 4 of the Event.
8
Ex: (MISC)
EVT_Forecast_Total_Revenue_4
The Forecasted Revenue 4 of the Event.
Ex: (25)
Data Type / Entity Relationships
To establish the relationship between records in each data type, the Unique ID primary key (PK) values are referenced as the foreign key (FK) IDs in other entities.