Commissions EFT Export Functionality
How Does the Export Functionality Work?
When creating the EFT ASCII export file, OPERA first checks all records due for export to determine whether they fulfill the requirements for your selected type of export. Several export formats are supported by OPERA (HCC, WTP, EGS, NPC, or INF). Your property decides on the format that will be used. If all the required data is available, specific data fields, such as the travel agent IATA number, may be validated before processing starts.
After successful processing, the ASCII file is generated in the appropriate format and stored in the export directory defined for your property. The format of the file depends on the type of export. Specific parameters for the type of export prepared by your property are set using the ASCII File Information screen (System Configuration>Commissions>EFT File Data). See EFT File Data for details.
Note: The PMS add-on license code for the type of export to be used must be active (OPP WTP, OPP HCC, OPP EGS, OPP NPC, or OPP_INF). Only one export type may be active for the property at any given time.
Each time you process commissions, a new ASCII file will be created in the export directory you defined in OPERA. When the EFT file is generated, you may wish to send a fax or email transmittal letter to this company to notify them of the availability of the file. The transmittal letter is generated by the commission payment process. The company and address populates the To: section of the Transmittal Letter form. If commissions are calculated in a currency different from the property's base currency, the exchange rate is printed in the transmittal letter, where appropriate. Properties can modify the transmittal letter report format as desired.
Note: The transmittal letter summarizes the transactions that are included in the batch file, including null values. On the report is an authorized signature line that is to be signed by a designated property employee. This report is required by most clearinghouses for processing of the EFT file. As with the EFT file itself, OPERA is not responsible for the delivery of the transmittal letter to the processing agency. It is the responsibility of the property to send the ASCII files to the relevant clearinghouse either by modem, floppy disk or by another means of communication.
In the Thin Client environment, export files will normally be stored on the application server at , for example D:\micros\opera\export\[schema]\[resort]\. All files are accessible via Miscellaneous>File Download in Thin Client only for security purposes. EFT files can also be accessed from the Miscellaneous>File Export>General option.
If an error is found, stop the entire operation in order to correct the errors and restart processing. Or, you may put all records with errors on hold and process only those without errors. Any errors found during the validation check will be shown on the screen and may be printed. The error report can only be printed once. To view the report again, the commission records will have to be evaluated again for validation. Records containing errors will not be included in the exported ASCII file.
If the export format requires an IATA number, OPERA makes sure that only valid IATA numbers are entered in agent and source profiles if the Profiles>IATA YN application setting is set to Y. If this parameter is set to Y, all IATA numbers are checked against the IATA validation routine. In the event that your property does not require IATA numbers for agent and source profiles, the parameter should not be activated. OPERA will use an internal profile number as the IATA number when creating the export.