|
|
|
Import File Standards (Sales & Catering to OPERA)
The Sales & Catering third party system export transfers all tentative and definite group room blocks and booking changes to OPERA.
From System Configuration>Setup>Note Types>New, add a new note type called Info. See Note Types for more details.
The import files are created by Sales & Catering and hold information/details on new or changed blocks and allotted room types. These ASCII files are automatically created during the operational day. The Import Files from Sales & Catering-to OPERA are stored on the OPERA/Sales & Catering PC in the Transmit (Input) folder. These files are read when you select the Import button from the Groups screen. The names of the import files are prefixed with the following letters:
Each record should be terminated with a carriage-return/line-feed.
All text fields denoted by the alpha-numeric representation - CHAR(##) - should be left- justified and padded with ASCII spaces to fill out the field.
All text fields are sent in uppercase to ensure uniqueness.
Numeric fields will always be right justified. If the number stored in a numeric field does not fully occupy the specified size, then the field should be padded with zeros.
Rate and revenue information passed between both systems will be stored in the ASCII files as whole numbers. The placement of the decimal point should be a configuration option for each system. Due to the differences each property may have regarding decimal accuracy, Newmarket Software has opted to not force 2 decimal places for currency, revenue or rates. The software running on both sides of the interface should be able to take the necessary steps to handle the whole number conversions. All rate, currency and revenue will be stored as a 9 digit whole number and padded with zeros.
Dates are stored with a four character year followed by a two character month and day in the following format - YYYYMMDD.
The import files are created by Sales & Catering and hold details on new and changed blocks and room types allotted. These ASCII files are automatically created during the operational day. The OPERA/Sales & Catering PC places the information in the Transmit (Input) folder. These files are read when you select Import from the options button on either to Business Block Search screen or from the booking directly.
Group bookings should always be created in Sales & Catering and later imported into OPERA. Control of the booking should remain in Sales & Catering if the booking is still not definite and until individual reservations need to be entered in OPERA. All block changes are entered in Sales & Catering until the control of the block is released.
The actual room rate without tax and breakfast should be entered in Guest Room Rate and this is imported into OPERA. Users adjust the rate code in OPERA manually, as only the default rate code configured in the translation table is transferred.
Notes can be viewed when the block is imported into OPERA. Only the first 300 characters of the Sales & Catering's booking notes are imported.
The following statuses can be sent to OPERA. It will be up to each property to determine which status to send (except for canceled).
"D" Definite
"T" Tentative
"C" Canceled
"N" will indicate a new booking not previously sent to OPERA.
"M" will indicate a changed booking that was already sent to OPERA.
"S" will indicate a booking that has been downgraded to a non-interfaced status booking (for example, if a property chooses to send only "D" (definite) bookings to the interface and then changes the status of the booking to "T" (tentative). This booking should no longer be considered an interfaced booking by OPERA. If the booking is later upgraded to a definite, Sales & Catering will send another HR (and HD) with a "N" (new booking) in this field.
Housing By is stored in Sales & Catering as a two character field. Each two character field is translated as follows:
" " None Entered
"RL" Rooming List
"RC" Reservation Card
"IN" Individual
"CB" Convention Bureau
The Rate Type is entered in Sales & Catering as either Estimated or Confirmed. Sales & Catering transfers an "E" for Estimated or a "C" for confirmed.
The Billing Types are defined in Sales & Catering for Rooms, Meals, Lounge and Incidentals. These categories can be billed as Master, individual or Combined. Sales & Catering will output this information as follows:
Rooms: |
(1) Master |
On Own Dining: |
(1) - Master |
Incidentals: |
(1) - Master |
|
(2) Individual |
|
(2) - Individual |
|
(2) - Individual |
|
(3) Combined |
|
(3) - Combined |
|
(3) - Combined |
|
|
|
|
|
|
Catered F&B: |
(1) Master |
Lounge: |
(1) - Master |
|
|
|
(2) Individual |
|
(2) - Individual |
|
|
|
(3) Combined |
|
(3) - Combined |
|
|
Sales & Catering allows each property to configure up to 15 unique User-Defined Fields (UDFs). Sales & Catering allows five 5-character fields, five 40-character fields, and five 9-character numeric fields. The 9-character numeric fields may pertain to a date, currency, or a whole number.
You may configure UDFs for credit cards, deposits received, on site contacts, etc. Sales & Catering only passes the raw data as input. Since each site may have different needs, each field cannot possibly be labeled. It is up to the OPERA interface programs to parse out pertinent information.
Contract type (1 char) allows you to flag each booking as either a group (G) or transient (T) booking. For a group type, OPERA deducts inventory from the group allotment in Sales & Catering. For a transient type, OPERA deducts inventory from transient allotment based on the pickup received from OPERA.
This field is filled in only if the Sales & Catering internal ID has been changed (e.g., joining of Sales & Catering accounts). If the Sales & Catering internal ID is altered, OPERA receives this new 18 character ID. The first 12 characters of the internal ID pertains to the account. The last six characters correspond to the booking number. This booking number is simply a sequential number used to give each booking an unique ID.
The Sales & Catering system provides a mechanism which allows a salesperson to consolidate accounts. This enables you to combine the entire contents of 2 separate accounts into a single consolidated account. When this joining of accounts is executed, bookings linked to these accounts will have their Sales & Catering internal IDs altered. Although the bookings detail information remains unchanged, it can no longer be accessed by its previous internal ID.
This definition offers the options Cutoff By Arrival and Cutoff By Consumption. These values are placed in offset 112 or 482 of the Detail Record.
A status trace date prompts you to perform an action in Sales & Catering. For example, Tentative - Decision due date, or Definite - Check Room Blocks or Rooming List Due.
In other words, if the status trace date comes up Tentative and a decision needs to be made on whether or not a due date needs to be given for a definite block, you need to check Room Blocks or the Rooming List Due in order to make the decision.
The Header Record file is passed from the third party Sales & Catering system to OPERA anytime a booking is created or modified in the Sales & Catering system. The numbering scheme for the file name must match for the HR and DR (detail record) files. This is to insure the header (HR) and the detail (DR) get processed together (if the HR is HR000005, then the corresponding DR must be DR000005).
The Header Record File contains the following record types:
Offset |
Field |
Format |
Interpretation by OPERA |
1 |
Property Code |
Char(5) |
Translated to OPERA Property Code |
6 |
S&C System Internal ID |
Char(18) |
Booking ID. (Also refer to position 463) |
24 |
Reservation ID |
Char(15) |
Not Used |
39 |
Booking Name(Post as Name) |
Char(40) |
Booking Description |
79 |
Arrival Date |
Date |
Booking Begin Date YYYYMMDD |
87 |
Departure Date |
Date |
Booking End Date YYYYMMDD |
95 |
Booking Status |
Char(2) |
Can be T, D or C. If this is T, OPERA will populate the booking status for the booking as the booking status setup in OPERA with the following attributes (If there are multiple booking statuses that satisfy the condition, one of them will be considered). (a) Starting-Status = YES. (b) Deduct-Inventory = NO. (c) Allow-Pickup = NO. If this is D, OPERA will populate the booking status for the booking as the booking status setup in OPERA with the following attributes (If there are multiple booking statuses that satisfy the condition, one of them will be considered). (a) Starting-Status = YES. (b) Deduct-Inventory = YES. (c) Allow-Pickup = NO. If this value is sent as C, the booking status setup in OPERA with status type = CANCEL will be populated |
97 |
Meeting Type |
Char(12) |
Not Used |
109 |
New, modified or status change to non interfaced bkg |
Char(1) (N, M,S,C) |
N - New Booking, M - Modified Booking, C - Cancel, S - Status downgrade |
110 |
Room Block Flag |
Char(1) (B/NULL) |
Not Used |
111 |
Released Flag |
Char(1) |
Not Used |
112 |
Cutoff Date |
Date |
Cut-Off Date. (Should be less <= Booking Begin Date) |
120 |
Date Definite |
Date |
Populated as Booking Comments (Notes) |
128 |
Booked by |
Char(3) |
Populated as Booking Comments (Notes) |
131 |
Guestroom Source |
Char(3) |
Populated as Booking Comments (Notes) |
134 |
Catering Source |
Char(3) |
Populated as Booking Comments (Notes) |
137 |
Service Manager |
Char(3) |
Populated as Booking Comments (Notes) |
140 |
Outside Lead |
Char(3) |
Translated to OPERA's Source Code (Origin Of Booking) |
143 |
Housing By |
Char(2) |
Translated to OPERA's Reservation Method attached to the booking |
145 |
Rate Type |
Char(1) |
Not Used |
146 |
Billing Rooms |
Numeric(1) |
Populated as Booking Comments (Notes) |
147 |
Billing Catered F&B |
Numeric(1) |
Populated as Booking Comments (Notes) |
148 |
Control Flag |
Char(1) |
D - S&C is in control of the booking. Any value other than D - OPERA is in control of the booking. Empty - OPERA is in control of the booking |
149 |
Billing Lounge |
Numeric(1) |
Populated as Booking Comments (Notes) |
150 |
Billing Incidentals |
Numeric(1) |
Populated as Booking Comments (Notes) |
151 |
Booking Comments |
Char(300) |
OPERA Booking Notes -> need a note type INFO |
451 |
Geographic Code |
Char(3) |
Populated as Booking Comments (Notes) |
454 |
Market Segment |
Char(5) |
Translated to OPERA Market Segment Code. Will also be pasted into Booking Notes as Contract Name (4) and Contract Type (1). |
459 |
No. of Nights |
Numeric(4) |
Not Used |
463 |
New S&C ID |
Char(18) |
Booking ID. If this value is empty, then the value in position 6 will be considered as the booking ID. |
481 |
Cutoff Type |
Char(1) (A or C) |
Not Used |
482 |
# of Cutoff Days |
Char(3) |
Cut-Off Days for the booking |
485 |
Status Trace Date |
DATEYYYYMMDD |
Populated as Booking Comments (Notes) |
493 |
Date & Time stamp file created |
Char(12) YYYYMMDDHHMM |
Populated as Booking Comments (Notes) |
505 |
Arrival Date Change Flag |
Char(1) Yes/No Indicator |
Not Used |
506 |
Reserved |
(45) |
Not Used |
Offset |
Field |
Format |
Interpretation by OPERA |
551 |
Account Name |
Char(60) |
Not Used |
611 |
Account ID |
Char(12) |
If this value is not empty, this will be populated as the Company Profile ID. Attached to the booking |
623 |
Acc Market Segment |
Char(8) |
Not Used |
631 |
Acc Contact Name |
Char(40) |
Not Used |
671 |
Acc Contact Title |
Char(40) |
Not Used |
711 |
Acc Contact St(Line1) |
Char(40) |
Not Used |
751 |
Acc Contact St(Line2) |
Char(40) |
Not Used |
791 |
Acc Contact City |
Char(25) |
Not Used |
816 |
Acc Contact State |
Char(5) |
Not Used |
821 |
Acc Contact Postal |
Char(12) |
Not Used |
833 |
Acc Contact Country |
Char(12) |
Not Used |
845 |
Acc Contact Phone |
Char(24) |
Not Used |
869 |
Acc Contact PhoneExt. |
Char(5) |
Not Used |
874 |
Acc Contact Fax |
Char(24) |
Not Used |
898 |
Acc Contact FaxExt. |
Char(5) |
Not Used |
903 |
Acc Contact Telex |
Char(24) |
Not Used |
927 |
Acc Contact TelexExt. |
Char(5) |
Not Used |
Offset |
Field |
Format |
Interpretation by OPERA |
932 |
Agency Name |
Char(60) |
Not Used |
992 |
Agency ID |
Char(12) |
Not Used |
1004 |
Agency Mkt Segment |
Char(8) |
Not Used |
1012 |
Agn Contact Name |
Char(40) |
Not Used |
1052 |
Agn Contact Title |
Char(40) |
Not Used |
1092 |
Agn Contact St(Line1) |
Char(40) |
Not Used |
1132 |
Agn Contact St(Line2) |
Char(40) |
Not Used |
1172 |
Agn Contact City |
Char(25) |
Not Used |
1197 |
Agn Contact State |
Char(5) |
Not Used |
1202 |
Agn Contact Postal |
Char(12) |
Not Used |
1214 |
Agn Contact Country |
Char(12) |
Not Used |
1226 |
Agn Contact Phone |
Char(24) |
Not Used |
1250 |
Agn Contact PhoneExt. |
Char(5) |
Not Used |
1255 |
Agn Contact Fax |
Char(24) |
Not Used |
1279 |
Agn Contact FaxExt. |
Char(5) |
Not Used |
1284 |
Agn Contact Telex |
Char(24) |
Not Used |
1308 |
Agn Contact TelexExt. |
Char(5) |
Not Used |
Offset |
Field |
Format |
Interpretation by OPERA |
1313 |
Bkg Contact Name |
Char(40) |
Not Used |
1353 |
Bkg Contact Title |
Char(40) |
Not Used |
1393 |
Bkg Contact St(Line1) |
Char(40) |
Not Used |
1433 |
Bkg Contact St(Line2) |
Char(40) |
Not Used |
1473 |
Bkg Contact City |
Char(25) |
Not Used |
1498 |
Bkg Contact State |
Char(5) |
Not Used |
1503 |
Bkg Contact Postal |
Char(12) |
Not Used |
1515 |
Bkg Contact Country |
Char(12) |
Not Used |
1527 |
Bkg Contact Phone |
Char(24) |
Not Used |
1551 |
Bkg Contact Phone Ext. |
Char(5) |
Not Used |
1556 |
Bkg Contact Fax |
Char(24) |
Not Used |
1580 |
Bkg Contact Fax Ext. |
Char(5) |
Not Used |
1585 |
Bkg Contact Telex |
Char(24) |
Not Used |
1609 |
Bkg Contact Telex Ext. |
Char(5) |
Not Used |
Offset |
Field |
Format |
Interpretation by OPERA |
1614 |
Field 1 |
Char(5) |
Not Used |
1619 |
Field 2 |
Char(5) |
Not Used |
1624 |
Field 3 |
Char(5) |
Not Used |
1629 |
Field 4 |
Char(5) |
Not Used |
1634 |
Field 5 |
Char(5) |
Not Used |
1639 |
Field 6 |
Char(40) |
Not Used |
1679 |
Field 7 |
Char(40) |
Not Used |
1719 |
Field 8 |
Char(40) |
Not Used |
1759 |
Field 9 |
Char(40) |
Not Used |
1799 |
Field 10 |
Char(40) |
Not Used |
1839 |
Field 11 |
Numeric(9) |
Not Used |
1848 |
Field 12 |
Numeric(9) |
Not Used |
1857 |
Field 13 |
Numeric(9) |
Not Used |
1866 |
Field 14 |
Numeric(9) |
Not Used |
1875 |
Field 15 |
Numeric(9) |
Not Used |
The detail record is passed from the third party Sales & Catering system to OPERA anytime a booking is created or modified in the Sales & Catering system. It contains room type and block/agreed information for the booking. The Detail Record repeats for each room type and for each night.
Offset |
Field |
Format |
Interpretation by OPERA |
1 |
S&C internal ID |
Char(18) |
Booking ID. |
19 |
Date |
Date |
Booking Date |
27 |
Room Type |
Char(20) |
Translated to OPERA's Room Type |
47 |
No. Rooms Block |
Numeric(7) |
Not Used |
54 |
Single Rooms Block |
Numeric(7) |
# Single Occ. Rooms |
61 |
Double Rooms Block |
Numeric(7) |
# Double Occ. Rooms |
68 |
Triple Rooms Block |
Numeric(7) |
# Triple Occ. Rooms |
75 |
Quad Rooms Block |
Numeric(7) |
# Quad. Occ. Rooms |
82 |
Single Rate |
Numeric(9) |
1 Person Rate |
91 |
Double Rate |
Numeric(9) |
2 Persons Rate |
100 |
Triple Rate |
Numeric(9) |
3 Persons Rate |
109 |
Quad Rate |
Numeric(9) |
4 Persons Rate |
118 |
No. Rooms Agreed |
Numeric(7) |
Not Used |
125 |
Single Rooms Agreed |
Numeric(7) |
Not Used |
132 |
Double Rooms Agreed |
Numeric(7) |
Not Used |
139 |
Triple Rooms Agreed |
Numeric(7) |
Not Used |
146 |
Quad Rooms Agreed |
Numeric(7) |
Not Used |
153 |
Reserved |
Char (48) |
Not Used |
See Also
