The Hilton OnQ system can be setup to output certain Night Audit reports to reports in Rich Text Format (RTF). The files used to implement the import from OnQ are:
DSTAT will import selective data from these reports. Instructions for setting up the local workstation are found in the section titled OnQ PMS Report Export Setup.
The next step to importing the OnQ values is to setup the workstation to read the files from the pre-determined location on your network. Follow the instructions in the section titled 'Setup PMS Interface' to assure that the OnQ data will be read on your workstation. This particular setting is by user by workstation. That way, one workstation can be setup to import the data (e.g. the Night Audit workstation) while other users assume that the data has already been read.
A message is display stating "Importing OnQ Local Tracking for: ..." letting you know that the data has been found. This data will be read into the 'Gross Amount' column. This column should be locked to user input. The adjustment column should be used to make any necessary adjustments to the imported value.
The sections that read from OnQ into DSTAT should be configured with Balance Check lines. When the Balance Check is not zero, you should first verify that all the data transferred completely from OnQ to DSTAT. Print the reports listed above and compare the values to the DSTAT values.
If OnQ is in Balance but DSTAT is not, then use the information below to check the Input Configuration in DSTAT. Likely issues are:
When the interface runs, a Log file is generated indicating any data that is used by DSTAT. You can examine the log file using Windows Notepad to see what PMS code may need to be added. The filename is in the form pppp_OnQ_yyyymmdd.log where pppp is the property code and yyyymmdd is the date. A sample log file looks like that below:
Special codes have to be entered for each row in the Input Configuration for DSTAT to pull the correct values from OnQ Reports. All of these codes are entered in the column labeled ‘PMS Code’.
If a row in DSTAT is Market Segment Roomnights, the Market Segment
is read from the Local Tracking Report. The "code" is the name of the
market segment without spaces. Only the first 15 characters are
used. The code is entered into the PMS Code column with the
prefix ‘PMS_RMS.’ For example, for market segment CORPORATE
TRANSIENT, the PMS Code is PMS_RMS.CORPORATETRANSI
If a row in DSTAT is Market Segment Revenue, the Market Segment is read from the Local Tracking Report. The "code" is the name of the market segment without spaces. Only the first 15 characters are used. The code is entered into the PMS Code column with the prefix ‘PMS_REV.’ For example, for market segment CORPORATE TRANSIENT, the PMS Code is PMS_REV.CORPORATETRANSI
Transaction Codes
If a row in DSTAT is a OnQ Transaction Code value, the Transaction Code is entered in the PMS Code column. Multiple rows in the DSTAT configuration may use the same Transaction Code. The transaction values are read from the OnQ report titled 'REVENUE TRANSMISSION DAILY TRANSLATION'.
In addition to Market Segment values and Transaction Code Values, DSTAT can pull specific statistical data from OnQ. These are preceeded by 'PMS.'. This data is read from the ROOM-GUEST STATISTICS report in OnQ. The title of the statistic is entered with spaces. The first 20 characters are used.
To add an item in DSTAT, select Input Configuration from the Setup Menu or the Toolbar. Click on the line where you want to insert an item and press Ctrl-I. This opens a blank line:
Next, type the PMS code and tab to the Account Number column:
If this is an item that is linked to an account number, typing a valid account number will fill in the rest of the information for the item. If this item is not linked to an account, leave the account number cell blank and fill in the rest of the row manually. Note that the item description defaults to the account name which you can type over to enter a more specific description.