www.UTS2000.com
Back 
Help
contents 
Print
www.UTS2000.com
Back Help
contents Print
Sales reports and ticket masks for your booking office and for your IATA office number are daily loaded from Gabriel system through UTS REPORTS program. The sale report and ticket mask data are analyzed on separate fields (ticket number, fares, taxes, PNR, passenger name, flight number and so on) and saves to disk in the flat table format. The data contains information about auto-tarification tickets, hand-issued tickets, void tickets and refund tickets. The structure of this data is described below. The fields in the data separates by ";" symbols. These data you can use for import to you database or Excel and then for the analysis of tickets sales of your travel agency or airline.
UTS REPORTS downloads sale reports and ticket masks for your IATA office number. The office number and other configuration data contains in the configuration (uts_reports.ini) file. You receive statistical data with one day delay. It is necessary to guarantee full information about sold tickets for one day. Program starts after time that given in the configuration file. After reports reception, two data file are formed. First file contains general tickets information-ticket number, fares, taxes, PNR, passenger name, currency rate and so on. The second file contains information about flight segments - airline code, flight date, departure time, booking class, fare code and so on. The fields of data separates by ";" symbol. These data format you can import to local database or to EXCEL program. The main data and segments data has common fields - IATA office number, sale date and ticket number.
Sale reports and ticket mask you can receive for last 45 days.
UTS REPORTS program creates data files in the folder с:\Program files\UTS Access\Bin\Reports\Data\Year\Airline\PID
where:
Year - sale reports year
Airline - airline code
PID - airline PID number. This PID uses for access to Gabriel system
For example:
folder с:\Program files\UTS Access\Bin\Reports\Data\2003\SU\12345 contains sale reports data for 2003 year, for SU airline and the data were received from PID 12345.
File names creates as yy-mm-dd-MAIN.txt and yy-mm-dd-SEG.txt
where:
yy - year
mm - month
dd - day
MAIN - this file contains main data (ticket number, fares, taxes, PNR and so on)
SEG - this file contains flight segments data (flight number, airline code, booking class, fare code and so on)
For example:
03-01-03-MAIN.txt - contains main data for 03 JAN 2003 YEAR
03-01-03-SEG.txt -contains flight segments data for 03 JAN 2003 YEAR
If с:\Program files\UTS Access\Bin\Reports\Data\Year\Airline\PID folder does not contain a files with data then UTS REPORTS will create the data file for previous day at start. If this folder contains files, for example 03-01-20, 03-01-22, 03-01-25 and program start day is 03-01-27 the UTS REPORTS creates following data files 03-01-21,03-01-23,03-01-24,03-01-26. That is the UTS REPORTS collects the absent data at the current day. If you want to repeat data for any date, you have to delete data file for this date and program recollect these data by automatically.
UTS REPORTS is daily loaded sale report from Gabriel system for IATA travel agency office number. The sale report data writes to с:\Program files\UTS Access\Bin\Reports\Data\Year\Airline\PID folder. The data filename is created as yy-mm-dd-MAIN.txt.
For example:
File 03-01-03-MAIN.txt. contains data report for 03 JAN 2003 YEAR.
The detail of data structure see here.
UTS REPORTS is daily loaded ticket masks for ticket numbers which contains in the sale report data file. For ticket masks reception add stroke Tickets_Receive=Y to the configuration file (uts_reports.ini). The file with ticket masks data is kept to folder с:\Program files\UTS Access\Bin\Reports\Data\Year\Airline\PID. The data file name creates as yy-mm-dd-SEG.txt. This file contains data for flight segments for each ticket.
For example: file 03-01-03-SEG.txt contains flight segments data for tickets which were received for 03 JAN 2003 YEAR.
The detail of data structure see here.
If the uts_reports.ini contains Ticket_Masks=c:\program files\UTS Access\Bin\Log\ticketsSU.txt record, then program will create file ticketsSU.txt with full ticket text image.
www.UTS2000.com
Back Help
contents 
Section contentsDownload UTS REPORTS 6 and set up it to your PC.
After set up you can see icon UTS REPORTS on the desk top of your PC and UTS REPORTS program will be run by automatically. The program serial number (SN) will appear at the window caption.
Attention! Serial number (SN) is used for program registration in the UTS NET network. The UTS REPORTS registration is the same as UTS Access registration. More details here.
Before UTS REPORTS use it is necessary to configure file с:\Program files\UTS Access\Bin\Options\uts_reports.ini.
The uts_reports.ini file contains main section [UTS REPORT] and additional sections [XXXXX]. Main section contains common parameters for program work and additional section contains parameters for modes of data downloading for each PID. The name of additional section is defined as PID number, for example [12345], [54321], [55555] and so on.
If at first program start the uts_reports.ini file does not exists, this file will be created by program and records in this file will be filled as empty. In this case the program will be stopped and it is necessary to set the real parameters.
After the real parameters are defined, run the program. Process of data loading will start after some time. The value of this time contains in the uts_reports.ini file in the TIME_START record. After the all data will be loaded, the program will be stopped and will start at the next day after TIME_START time by automatically.
| Field | Description |
|---|---|
| HOST | IP address of the UTS NET server. The program has access to Gabriel
system through UTS NET server. For access to UTS NET server use IP Port=18000.
For example: HOST=80.92.32.245 For example: HOST=192.168.40.22:500 where 192.168.40.22 is IP of proxy server, 500 is IP port for access to proxy server The list of UTS NET IP addresses you can receive from system administrator |
| SITA_HOST |
The SITA interface name for access to Gabriel system. You can use SITA_1 or SITA_2 names For example: SITA_HOST=SITA_1 |
| HEADER | To write or to not write the header of the data structure definition For example: HEADER=Y If HEADER=Y then the header with data structure definition will be added to data file as first record |
| TIME_START | Time of process start for data loading
For example: TIME_START=04:00, where 04 is hour and 00 is minutes |
| Field | Description |
|---|---|
| AIRLINE | Airline code for which the PID 12345 is defined
For example: AIRLINE=SU It means that PID 12345 is defined for SU airline PID should has terminal (UVTC) type. This PID should be registered on the Registration server through UTS Access program. Do not use PCPCM(PCPC) or PRN(UVTP) PID type.
|
| SI | Sign in command is for sign in to Gabriel system for PID 12345
For example: SI=SI16787/12345A |
| Validator1 - Validator99 | IATA office number. You can use several office numbers for data loading
For example:
|
| TICKETS_RECEIVE | To receive or not to receive ticket masks information
For example: TICKETS_RECEIVE=Y In this case you will receive ticket masks and program will create the segments data for each ticket. TICKETS_RECEIVE=N In this case you will not receive ticket masks and program will not create the segments data for each ticket.
|
| TICKET_MASKS | File name for ticket masks images
For example: TICKET_MASKS=c:\program files\UTS Access\Bin\Log\ticketsSU.txt.
|
| LOG_FILE | Log file name. In this file the full information about data processing will
be written
For example: LOG_FILE=c:\Program Files\UTS Access\Bin\Log\ReportSU.txt |
www.UTS2000.com
Back Help
contents
Section contents
UTS REPORTS writes some messages during work.
It is main window of UTS REPORTS program.
Host IP is IP address and IP Port number for access to UTS NET server.
SITA Host is name of SITA interface.
Start Report Time is time of program start
Received (Total bytes) is total bytes amount, which was received from Gabriel system.
Airline/PID is airline code/PID number
Messages is text of messages.
Start processing is real time of program start for data processing.
End processing is real time of program data processing stop.
Date processing is currently time of data processing..
Report Date is sale report data.
| Message | Description |
|---|---|
| ...Please, register UTS REPORTS program on the registration server. | The UTS REPORTS is not registered on the Registration server. To register program from UTS Access program through menu Help->Registration in the UTS Access. |
| ERROR:Parameters for Sale Reports receiving are absent. See configuration file С:\Program files\Uts Access\Bin\Options\uts_reports.ini | The uts_reports.ini file does not contain the real parameters of program work Check uts_reports.ini file. |
| Connect to Gabriel | Operation of connection to Gabriel system is carried out. |
| Sale report for validator 12345678A in progress | Operation of sale reports reception is in progress for 12345678A office number |
| Validator 12345678A, no tickets | The tickets are absent for 123456789A office number. |
| ERROR: PID 12345 is busy. Restart sale report | The PID 12345 is busy by another program. The download process will be repeated. |
| ERROR: Sign in command is not correct | The sign in command is not correct. Check this command in the uts_reports.ini file. |
| ERROR: Sale report for validator 12345678A is not accessible | The IATA office number is not correct. Check this number in the file uts_reports.ini, field Validator1= and restart program. |
| ERROR: 10065 CONNECT TO HOST | UTS NET server is not accessible. Set new UTS NET IP address in the uts_reports.ini file, see field HOST= and restart program. |
| ERROR: Not response from UTS NET server. Restart | UTS NET does not response big time. The process of data loading will be restarted by automatically. |
| Sale Report 12345678A has received | The data for sale report is received for 12345678A office number. |
www.UTS2000.com
Back Help
contents
Section contents
This topic contains the description of sale report and ticket masks data. The description are submitted as tables. First column contains data field name, second column contains the length of field in the char and the third column contains the description of this field. The data field size is described as Char(X) or VARCHAR(X). In the first case is required to create field in the local database as fixed size. In the second case is required to create field in the local database as variable length. X - is length of field in char.
| Field | Size (in char) | Description |
|---|---|---|
| VALIDATOR | VarChar(9) | IATA office number. For example 12345678A. |
| DATE_REPORT | VarChar(8) | Date of sale report. For example 20030130, where 2003 is year, 01is month number, 30 is date number. |
| TICKET_NBR | VarChar(10) | Ticket number. |
| TYPE_TKT | Char(1) | Type of ticket.
A - auto tarification |
| ALN_CODE | Char(3) | Airline code as 3 digits. For example 555 is airline code fo Aeroflot(SU) airline. |
| FARE_AMOUNT | VarChar(9) | Base fare or equivalent amount in the currency of the issuing office. |
| TAX_AMOUNT | VarChar(9) | Total of taxes collected in the currency of issuing office. |
| TOTAL_AMOUNT | VarChar(9) | Total amount of ticket in the currency of issuing office. |
| COMM_AMOUNT | VarChar(9) | Commission amount. |
| AXG | VarChar(20) | Sales report element entry. |
| AGENT | VarChar(5) | Agent number. |
| FIRST_PAY_FORM | Char(2) | First form of payment code. |
| FIRST_PAY_AMT | VarChar(9) | First form of amount. |
| FIRST_PAY_CURR | Char(3) | First form of currency. |
| FIRST_PAY_REF | VarChar(20) | First form reference info. |
| SECOND_PAY_FORM | Char(2) | Second form of payment code. |
| SECOND_PAY_AMT | VarChar(9) | Second form of amount. |
| SECOND_PAY_CURR | Char(3) | Second form of currency. |
| SECOND_PAY_REF | VarChar(20) | Second form reference info. |
| ADDINFORM_CODE | Char(2) | Additional code. |
| ADDINFORM_TEXT | VarChar(20) | Additional text. |
| TAX1_CODE | Char(2) | First tax code. |
| TAX1_AMT | VarChar(9) | First tax amount in the currency of issuing office. |
| TAX2_CODE | Char(2) | Second tax code. |
| TAX2_AMT | VarChar(9) | Second tax amount in the currency of issuing office. |
| TAX3_CODE | Char(2) | Third tax code. |
| TAX3_AMT | VarChar(9) | Third tax amount in the currency of issuing office. |
| TAX4_CODE | Char(2) | Fourth tax code. |
| TAX4_AMT | VarChar(9) | Fourth tax amount in the currency of issuing office. |
| TAX5_CODE | Char(2) | Fifth tax code. |
| TAX5_AMT | VarChar(9) | Fifth tax amount in the currency of issuing office. |
| TAX6_CODE | Char(2) | Sixth tax code. |
| TAX6_AMT | VarChar(9) | Sixth tax amount in the currency of issuing office. |
| TAX7_CODE | Char(2) | Seventh tax code. |
| TAX7_AMT | VarChar(9) | Seventh tax amount in the currency of issuing office. |
| SITI | Char(4) | Code place of issuing office (SITI,SOTO,...). |
| PNR | Char(5) | Record locator number. |
| PAX_NAME | VarChar(30) | Passenger name. |
| BLCCR_FARE | VarChar(9) | Fare amount for block seats for regular flight. Fields BLCCR_FARE, BLCCR_CURR, BLCCR_RATE_CURR is filled if the ticket is issued as fare for block seats on the regular flight, another these fields are empty and BLCCR_RATE_CURR field fills as 1. |
| BLCCR_CURR | Char(3) | Currency code for block seats for regular flight. |
| BLCCR_RATE_CURR | VarChar(9) | Currency rate for block seats for regular flight. |
| Field | Size (in char) | Description |
|---|---|---|
| VALIDATOR | VarChar(9) | IATA office number. For example 12345678A. |
| DATE_REPORT | VarChar(8) | Sale report date. For example 20030130, where 2003 is year, 01is month number, 30 is day number. |
| TICKET_NBR | Char(10) | Ticket number. |
| SEGM_NBR | Char(1) | Flight block number. For example 1,2,3,4. |
| FROM_CITY | VarChar(20) | City of departure. For example MOSCOW. |
| FROM_AIRPORT | Char(3) | Airport of departure. For example SVO. |
| TO_CITY | VarChar(20) | City of arrival. |
| TO_AIRPORT | Char(3) | Airport of arrival. |
| AIRLINE | Char(2) | Airline code in letters. For example SU. |
| FLIGHT_NUMBER | Char(5) | Flight number. |
| BOOK_CLASS | Char(1) | Booking class. |
| DEPARTURE_DATE | Char(5) | Date of departure. For example 19FEB. |
| DEPARTURE_TIME | Char(4) | Time of departure. For example 1630. |
| TICKET_STATUS | Char(2) | Ticket status. For example OK. |
| FARE_CODE | VarChar(12) | Fare code. For example KPXOW. |
All fields are separated by ";" symbol in the data files
www.UTS2000.com
Back Help
contents
Section contents