|
|
|
Country Exports
The Miscellaneous > File Export > Country or Configuration > External > Country Exports menu items display when the Exports > Country Exports application parameter is set to Y. This option is used to generate all country specific legal exports and does not require any particular export license code to be set. The data that is extracted from OPERA is inserted into a separate database to be processed.
Note: If a property has the OPP_PMS license active, OPP_S&C license active, OPP_BO add-on license inactive, OPP_EXP add-on license inactive, OPP_ESM add-on license inactive, OPP_COM add-on license active, Commission > Positive Pay Check Export application parameter is inactive, and Exports > Country Export application function is inactive, the Configuration menu option for External will no longer display without any menu options.
When in the Country Exports option, you can Edit, View and Generate exports.
Note: Exports cannot be created except from OPERA-provided templates. Availability of templates for the legal exports for the different countries may depend on the country mode selected on the Property Details screen.
The procedure GENERATE EXPORT NA DATA, in the End of Day Routine may be used to generate these exports on a nightly basis. If so, this procedure must exist in the End of Day Routine Sequence for the exports to be generated.
The ASCII file will be generated to a defined location (in export definition) automatically during the night audit and can be downloaded from the application server to a local machine using the option Miscellaneous > File Download.
The location of the directory where OPERA export files are stored is defined in the default_<schema>.env file environment variable (default_brisbane.env), FORMS90_OUTOUT. At installation, this variable is set to D:\micros\opera\exports. Use oappcfged.exe to make configuration changes.
As an alternative to mapped drives, UNC (Universal Naming Convention) network share paths (e.g., \\app_server1\micros\opera\export) are also supported. This is also applicable for the zipping of the export files if the zip file name is defined in the export file details.
File Type |
File Type Description |
Police Export |
|
Tourist Export |
|
CURRENCY EXCHANGE |
Currency Exchange Export |
Greece Doorbook Export |
|
Spain Police Export |
|
Spanish Country Statistics (INE) |
|
FOLIOTAX SUMMARY |
Foliotax Summary Export |
GDPDU 3 Folios |
|
GDPDU 5 Export Index File |
|
GDPDU 1 Transaction Details |
|
GDPDU 2 Transaction Summary |
|
GDPDU 4 Statistics |
|
NIS EXPORT |
NIS Statistics |
NIS EXPORT DAY |
NIS Statistics by Day |
POLICE EXPORT |
Police Export |
PROFILE REQUESTS |
Profile Requests Export |
Police Export |
|
Nationality Statistics Export - Sweden |
|
Tax Export |
For example, the Belgian Tourist Export acts as the following:
An ASCII export file will be generated, which gives the nationality statistics of the property. By default the export file will be made to generate at the end of each month during the night audit. There also exists an option to generate this file manually if for some reason the night audit export did not go through. The export file can be generated for any given date range, in the past.
This export file will contain the detailed information listed below, for all checked out guests for the given date range. No-shows and cancellations will not be included in the export.
The following information for each guest will be sent across in the export:
The following table lists the details of the export file being created.
Sequence |
Column in CDHOTEL.DBF |
Column |
Length |
OPERA Source of Data |
1 |
MOIS |
Business date month |
2 |
Business date |
2 |
ANEE |
Business date year |
2 |
Business date |
3 |
OUVERTURE |
Current month no. of days |
2 |
Business date |
4. |
INS ETAB |
Property ID Number |
9 |
Tab: RESORT Col: HOTEL CODE |
5 |
INS HEB |
Lodging type ID code |
3 |
|
6 |
NPAYS |
Guest country |
20 |
Tab: COUNTRY, Col: COUNTRY NAME (For the country code in the guest profile) Tab: NAME ADDRESS, Col: COUNTRY) |
7 |
CPAYS |
Guest country Statistic number |
3 |
Tab: COUNTRY, Col: STATISTIC CODE |
8. |
BUT |
Purpose of Stay |
1 |
User Defined field in RESERVATION NAME |
9. |
DEPART |
Departure Date (day of month) |
2 |
Tab: RESERVATION NAME, Col: END DATE |
10. |
NUITEES |
Number of nights |
2 |
Tab:RESERVATION NAME, Col:BEGIN DATE and Col:END DATE (END DATE-BEGIN DATE) |
11 |
PERSONNES |
Number of people |
2 |
Tab: RESERVATION DAILY ELEMENTS; Col: ADULTS + Col: CHILDREN (on the date of departure) |
12 |
CHAMBRES |
Number of rooms |
2 |
Tab: RESERVATION DAILY ELEMENTS; Col: QUANTITY (for the departure date) |
Another ASCII export file is generated containing the property information. The following information of the property is sent across in the export:
The format is as follows:
VERZENDING NIS |
BEST and HOTEL |
Statistiekjaar |
1 |
Statistiekmaand |
5 |
Firma |
Property Name |
NIS-code |
NIS-Code of the property(Property Code) |
Verantw. Persoon:Legal Owner |
|
Straat |
Address of the property |
Postcode |
Postal code |
Gemeente |
|
Telefon |
Telephone number of the property |
Toestel |
|
Telefax |
Fax number of the property |
Logiesvorm HOTEL(Vragenformulier I) |
T (if property type = HOTEL) or F |
Logiesvorm CAMPING(Vragenformulier Ibis) |
T (if property type = CAMPING)or F |
Logiesvorm VERHURING(Vragenformulier II) |
T (if property type=VERHURING) or F |
NIS-Code voor de logiesvorm HOTEL |
000 (defined by Property) |
NIS-Code voor de logiesvorm CAMPING |
000 (defined by Property) |
NIS-Code voor de logiesvorm CAMPING |
000 (defined by Property) |
The field values and their source table and columns in OPERA are defined in the table below:
Sequence |
Column |
OPERA Source of Data |
1 |
Month/Year of Business date |
Business date |
2 |
Property Name |
Tab: RESORT, Col: NAME |
3 |
NIS- Code of the property |
Tab: RESORT, Col:HOTEL CODE |
4 |
Owner |
Tab: RESORT, Col: OWNERSHIP |
5 |
Address of the property |
Tab: RESORT, Col: STREET |
6 |
Postal code |
Tab: RESORT, Col: POST CODE |
7 |
Gemeente |
|
8 |
Telephone number |
Tab: RESORT, Col: TELEPHONE |
9 |
Toestel |
|
10 |
Fax |
Tab:RESORT, Col: FAX |
11 |
Property Type |
Tab: RESORT, Col: RESORT TYPE (can be HOTEL, CAMPING or VERHURING) |
All static text like Statistiekjaar, Statistiekmaand, Firma, NIS-code voor de logiesvorm HOTEL, etc. can be defined in the export definition. This can be changed by the property to get the correct information.
The values for NIS-code voor de logiesvorm HOTEL can also be defined by the property, in the export definition.
File Type. Select from the lists of values the file type to be exported explained in the Grid below
Property. If Multi Property is active, select the property you want to export file type information from.
Show Inactive. Display all inactive file types.
Search. Search for the selected file type in the File Type List.
Grid. The grid (file type and description) will display only those templates that you select.
Generate. Start the export data generation.
View Data. View the export data that has already been created.
To create a new country export, select New.
You can create the export file by copying an existing export file as a template, and editing it, or by starting with a blank Export File Details screen. If you select the template option, you are prompted to select the export file type(s) to be copied as templates. If the OPP_MHOT Multi-property license code is active, you are prompted to select the properties to which you want to copy them (the current property is selected by default).
The Export File Details screen allows you to specify the particular features of the export file.
File Type. Name of the export. To create a new file type, select New from the Export File List and enter a new file type name for the export.
File Description. Long description of the file type.
Export Source. Select the down arrow to choose from a list of available views for the export procedure.
Source Description. The description will be automatically populated when the Export Source view is selected.
Pre Export Procedure. Internal setup procedure that will be executed before the data export is done.
Post Export Procedure. Internal setup procedure that will be executed after the data export is done.
Parameter Form. Commonly used for exports that can be manually generated. This field contains the parameter form, which is used to generate a manual export. The parameter form, would take the required input from the user in order to generate a manual export. An example of the required parameters is the date range for which the export needs to be run. Each pre-export procedure has a unique parameter form, as the procedure is hard- coded within the form. Normally, if the parameter form is used, the pre-export procedure does not need to be used, but this can vary depending on the definition of the export.
Night Audit Export. Check this box if the export is to be run during the night audit.
Frequency. When the Night Audit Export check box is selected, select the down arrow to select the frequency of how often the export is to be run during the night audit process. Will it be run Daily, End of month, End of Year, or Weekly.
HTTP Upload. Select to use an HTTP Upload, through an OXI interface, of the export file. This file can be uploaded and transferred to the HTTP address automatically using the night audit. Also, the export file HTTP upload is available on demand and can be transferred manually to allow for more up to the minute information.
Note: If the export is configured to run during the night audit and the HTTP transmission fails, the night audit will continue to run to complete the End of Day. But, an error message will display in the naweather.rdf report to notify the user of the transmission failure. As this report is non- mandatory, properties using the HTTP transmission must configure the report.
HTTP Address. When the HTTP Address check box is selected, type the database HTTP address where the export file will be uploaded to.
Filter Condition. Condition for the export. By default, depending on the view all data will be exported. But if a certain type of data only requires to be exported, then the condition can be filled. Technically, this is the where clause in the select statement. For example, market codes statistics export, if only certain market codes statistics are required, like FIT, COM and IND, then the condition Market code IN (FIT,COM,IND) can be entered, where market code would be one of the column names in the Export source view/table.
When clicking OK, the export setup is saved and now the columns can be defined. When the export setup is saved, the button option Export Columns will now be available.
Select this button and the entire list of columns, which are available in the view, will be brought up. This occurs the first time, when setting up a new export. If the columns are already defined, then the option Export Columns will list out the columns, which have been selected. New columns can also be added.
File Name Formula. Name of the ASCII export file that will be created when the option to generate file is selected. This field can accept SQL formulas so that the file name can include dates or other program specific exports information (First5Characters of Property Code +Current System Month+F would be SUBSTR(property code,5)||MM||F). This should be a valid SQL formula. On clicking the list of values box, a list of all the columns defined in the Export Source View/Table will appear. These are the columns that can be used to create the File Name Formula. The name of the ASCII text file can be made from any of these values or can also be any string of characters. If the file has to be always called WY P296, then enter 'WY P296' (the single quotes are necessary). If the file has to depend on the business date of the property, then enter the following, for example:
'WY'||TO CHAR(PMS P.BUSINESS DATE,'MMDD')||'EXP'
This gives the name WY1103EXP for a business date of November 3.
File Extension Formula. Used to create any file extension for the daily export. This field can accept SQL statements so that the extension can include dates or other program specific export information (Current System Month +Day MM||DD). Examples for the file extension name would be TXT or EXP. The single quotes are necessary.
Zip File Name. The name of the zipfile if the export files are to be zipped. To make use of this functionality, the EXPORT ZIPPROGRAM parameter must be filled in with the zip program namezip. The Zip Program name parameter EXPORT ZIPPROGRAM is already set up in User Set-up > Application Parameter > OPERA > General. The Zip Program name (executable file) must be present in the \RUNTIMES directory.
Compress Data. Select this check box to compress all records in the export file. This would be used for delimited ASCII text files. The delimiter can be entered in the box given.
Col. Separator. Displays when the Compress Data check box is selected. Select the Space, Tab, Comma, or Enter (Ctrl or carriage return line feed) option as the character column separator. The data column is delimited by the selected character that follows it.
Always Export Header and Footer. Based on the export setup, if no data has been generated within the export and if a header and footer is defined and a file name given in the export setup, OPERA will always generate the export file that contains no information other than the header and the footer.
Inactive. Mark this check box to make a file type Active or Inactive. If the box is checked, the file type will be Inactive. If the box is not checked the file type will be Active. The box will be unchecked by default.
Add Newline. Check this box to have each record displayed on a separate line in the ASCII text file.
Export Columns. Click this button to display the Export Columns Detail screen where the columns to appear on the export are selected.
See Also
