Message File Export or Import

DCO, Revenue and EFO File export handling in OXI – HOLIDEX only

The communication method for DCO/Revenue and EFO Export has to be fully configured in OPERA and OXI in order to create successful export files.

• OPERA PMS creates the detailed check-out (DCO), the revenue (REV), and Electronic Folio (EFO) data for each business day after night audit
• OPERA PMS creates the revenue information based on calculations from occupancy statistics and revenue categories as described in the revenue occupancy file specification.
• The EFO export is detailed folio information regarding guests staying at the hotel. EFO exports are created each day even if checkouts have not occurred for that business date.
• Transportation of the EFO export file is done by OXI through the IHG Network to a router and then IHG will forward to Third Parties involved in handling this information. If the receiving party has not received the file they will contact, the hotel directly and request regeneration of the file for them.
• OXI will upload this extract data from the database when OPERA calls an OXI function; in turn OXI will create the file for DCO, REV or EFO information and have these uploaded to the FTP server.
• Files for DCO and REV will be shown in the OXI Message Status and can be identified by module FILE EXPORT and actions DCO_UPLOAD, REV_UPLOAD or EFO_UPLOAD.
• There is a 10-minute delay before OXI takes the data and creates the export file, so the timestamp for the DCO, REV and EFO files may differ a few seconds in the OXI Message Status screen.
• If an export routine is issued other than DCO, REV or EFO export, the OXI does not recognize it and will not send a response to the OXI call function. OPERA will then create a file and issue the respective message to the user.
• The status for these files is NEW and will change to SUCCESS when files have been deposited on the FTP server. As the files are transferred we will receive a response from the FTP server within the same message. There will be no return/response message in the OXI Message Status screen.
• Should the export file require to be resent from OXI, the REPROCESS button can be used.
• A DCO/REV/EFO file that has a status of NEW and has not been successfully uploaded on the date of generation or during the retries will be held until the next upload time. Check the Start Time under Interface Configuration>Comm Methods>DCO/Rev Export>More tab. For EFO the Comm Methods is E_Folio Export->More Tab. The time is set in military format.
• A DCO/REV/EFO file that has a status of NEW and has not been successfully uploaded will NOT be removed from the Message Status screen, even if the time frame has passed for the No of days to keep or the Purge No of days.
• Manual generation of the DCO, REV or EFO file on the OPERA side will generate data, OXI will create the file and the message will show in the OXI Messages Status screen awaiting the Start Time to kick in before sending to the FTP server.
  1. If the Start Time is now in the past the file will have to wait until the next day at the same time
  2. If the Start Time is still to come the file has the chance to upload of the same day of generation
• If the ‘Start Time’ is set to ‘null’, the DCO/RE/EFO files will immediately be sent to the FTP server, after OXI’s 10-minute delay. It then bypasses the ‘Retry Count’ and will keep sending the file until it is successfully deposited in the specified FTP directory.

  Note: When REPROCESS key is used or when retries are applied by OXI, the DCO/REV/EFO message will receive a new timestamp and move up in the OXI Message Status screen, it does not disappear. The message is reused each time until successfully deposited on the FTP server.

Export File Types – MARSHA Only

Pre-Arrival Export-

An export file generated 9 days prior to arrival from PMS. This will be known as a Pre- Arrival export and will be uploaded by OXI. The Pre-Arrival file will contain three kinds of entries, Pre-Arrival, In-House, and Cancel/No-Show. Pre-Arrival entries will consist of reservation information for a guest who has not arrived yet. In-House entries will consist of stay information for the in-house guest.  Cancellation/No-Show entries will be information to cancel a guest reservation.

Post-Stay Export-

An export file generated after the guest departure from the PMS. This will be known as Post-Stay export and will be uploaded by OXI. The Post-Stay file will contain information needed for customer stay history maintenance. This information will consist primarily of customer ID, contact, and revenue information.

PMS Export File Naming Conventions Chart

File Name Parts	Possible Entries	Example
Prefix (2 Characters)	PS     PA	PS
Marsha Property Identifier (5 characters)	Any Marsha Prop Code	ASERZ
Dot (1 character separator)
Suffix (3 characters)	DAT	DAT

Example:  The following are two example files names:

• PAASERZ.DAT - Pre-Arrival file from Aspen for today.
• PSASERZ.DAT - Post-Stay file from Aspen for today.

Export File Headers and Footers Charts

The PMS-CLASS interface files will use both header and trailer records in order to maintain file transmission integrity.

The header for all files sent from OPERA to CLASS will be as follows:

FIELD	COMMENTS
Control Character	Indicates nature of row. Use “H” for header row.
Creation Date	MMDDYYYY, This would be the business date being rolled for the hotel i.e. if the property was conducting the night audit of the 1st to 2nd then it would carry the date of the 1st.System date at extract file creation.
Creation Time	HH:MM:SS - System time at file creation. 24 hr syntax.
File Type (Must Be Capitalized)	PA - Pre-Arrival File PS - Post-Stay File
Extract Record Count	Count of records extracted.

Sample:  This example would be interpreted as a Pre-Arrival file that was created for the business date of May 27, 1997 at 5:00 am in the morning of May 28, 1997 with 4622 records in it.

H|05271997|05:00:00|PA|4622|

The detail for all files sent from OPERA to CLASS will be as follows:

FIELD	COMMENTS
Control Character	Indicates nature of row. Use (D) for Detail row.

Sample:  D|0|

The footer for all files sent from OPERA to CLASS will be as follows:

FIELD	COMMENTS
Control Character	Indicates nature of row. Use (Z) for Trailer row.

Note:  The export filenames and file contents will always be in uppercase

Active Comments Files Import – MARSHA Only

• This is an import file returned to the PMS outlining specific information pertaining to the arrivals.
• The OXA download processor will download the Active Comments File. OXI will parse the data and calls the PMS_API to populate the guest RESERVATION_ALERTS table, which will be referenced during the check-in of the guest arrival.
• The Active Comments file will contains data being sent from the CLASS system to the PMS. This file will be generated once a day, at the time specified by the EXTRACT_TIMING table in the CLASS database.  The Data is mapped to PMS table RESERVATION_ALERTS.
• The full alerts screen will be displayed if the parameter for ALERTS = Y, the Alert Code = IMPORTED and Configuration Mode = RITZ- CARLTON.
• Irrespective of whether or a not an alert record has been created previously from the CLASS system, OXI when receiving information from Marsha, will always insert the full (I) field information of up to 2000 characters into the description field. If an alert record already exists that is called “imported” due to one having created because of the class interface, then the description field will simply be appended.

Active Comments File Pickup – MARSHA Only

A file containing the active comments for a particular property will be generated daily by the CLASS Application server.  The CLASS server generates these files after what should be the conclusion of the business day for a given property.  The active comments file will be available for pickup by the property management system when they are dropping off their pre-arrival and post-stay files.  The deletion of the Active Comments File from the CLASS outbox directory after the "get" is mandatory. See Script file below -

Example:  Night Audit Pickup/Drop-off Script (.netrc file).This is a example of the pickup/drop-off file transfer script that is executed during the property's night audit process.

machine class login xxxxx password yyyyyy macdef init

cd /cis/test/pms/inbox/resrz/tmp

put /usr/fidelio/data/RLCLASSA.MON PARESRZ1.DAT

put /usr/fidelio/data/RLCLASSP.MON PSRESRZ1.DAT

rename PARESRZ1.DAT ../ PARESRZ1.DAT

rename PSRESRZ1.DAT ../PSRESRZ1.DAT

cd /cis/test/pms/outbox/resrz/getfile

rename ../ACRESRZ.DAT ./ ACRESRZ.DAT

get ACRESRZ.DAT /usr/fidelio/data/ ACRESRZ.TXT

delete ACRESRZ.DAT

quit     

                                           

Example:  Active Comments Data

H|12021997|21:16:03|AC|25|

D|CR-481456-1|83033491||N/A|N/A|Unknown|0|0|||||||

D|CR-481398-1|82990696||N/A|N/A|Unknown|0|0|||||||

D|CR-474467-1|82583549||Repeat|N/A|Unknown|18|18|Pentagon City|10/15/1997|||||

D|CR-481413-1|83005542||Repeat|N/A|Unknown|1|1|Pentagon City|10/19/1997|||||

D|CR-481445-1|83028412||N/A|N/A|Unknown|0|0|||||||

D|CR-482031- 1|83488821||Repeat|N/A|Unknown|11|7|Buckhead|10/29/1997|GST GENDER IS MALE||||

D|CR-482032- 1|83488765||Repeat|N/A|Unknown|4|2|Philadelphia|08/11/1997|||||

D|CR-482039-1|83497732||Repeat|N/A|Unknown|9|8|Pentagon City|10/09/1997|GST GENDER IS MALE||||

D|CR-477572-1|80293979||Repeat|N/A|Unknown|3|2|Tysons Corner|01/22/1997|||||

D|CR-482047-1|83502967||Repeat|Property VIP|Unknown|14|14|Pentagon City|09/29/1997|PLEASE MAKE SURE ALL MSGS AND FAXES ARE SENT ASAP|RM MUST BE IMMACULATE, GST VERY PARTICULAR  H.K.|||

D|CR-473018-1|81479267||Repeat|N/A|Unknown|1|1|Pentagon City|10/15/1997|||||

D|CR-478603-1|81092149||Repeat|N/A|Unknown|6|1|Pentagon City|11/11/1996|||||

D|CR-479498-1|81827252||Repeat|N/A|Unknown|2|1|Pentagon City|06/11/1996|||||

D|CR-472983-1|81454068||Loyal|Property VIP|Unknown|86|39|Buckhead|09/03/1997|GST IS THE OWNER OF MGM DESIGNS||||

D|CR-476847-1|84300648||Repeat|N/A|Unknown|18|14|Pentagon City|10/28/1997|||||

D|CR-482941-1|84162806||N/A|N/A|Unknown|0|0|||||||

D|CR-482943-1|84162954||N/A|N/A|Unknown|0|0|||||||

D|CR-472981-1|81453773|289431|Repeat|Property VIP|Unknown|10|3|Buckhead|09/03/1997|TRAVELING WITH MR. DUPREY||||

D|CR-475082-1|82965189||Repeat|N/A|Unknown|51|50|Pentagon City|10/14/1997|||||

D|CR-482951-1|84164298||N/A|N/A|Unknown|0|0|||||||

D|CR-475125-1|82994774||N/A|N/A|Unknown|0|0|||||||

D|CR-482959-1|84168884||Repeat|N/A|Unknown|16|14|Pentagon City|04/28/1997|SMOKING ROOM||||

D|CR-463721-1|83260672||N/A|N/A|Unknown|0|0|||||||

D|CR-481558-1|83110523||N/A|N/A|Unknown|0|0|||||||

D|CA-999999-1|99999999||Repeat|Corporate VIP|German|7|6|Cancun|10/28/1997|GUEST IS THE OWNER OF THE ATLANTA BRAVES|GUEST IS ALLERGIC TO DAIRY PRODUCTS|MUST BE ON THE TOP FLOOR OF THE HOTEL|CLEAN ROOM BETWEEN 3- 5PM EACH DAY|

Z|