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.