E-Ticketing User Guide: Kiu System Solutions

KIU SYSTEM SOLUTIONS
E-Ticketing User Guide
KIU System Solutions

San Martín 320 Piso 5
Capital Federal (C1004AAH)
Argentina
www.kiusys.com
KIU® November 2011

Ticketing user guide
Index
1. Personal Sales Report ............................................................................................................... 4
1.1. Personal sales report opening ............................................ ¡Error! Marcador no definido.
1.2. Personal sales report closing .............................................. ¡Error! Marcador no definido.
1.3. Visualize the sales report .................................................... ¡Error! Marcador no definido.
1.3.1. Options to partially visualize the report ............................ ¡Error! Marcador no definido.
1.4. Adding remarks to the sales report ..................................... ¡Error! Marcador no definido.
1.4.1. Remote closing of the sales report .................................................................................. 7
1.4.2. Consulting other agents sales reports ............................. ¡Error! Marcador no definido.
1.4.3. Consulting the own sales reports ..................................................................................... 8
1.4.4. Consulting an specific sales report .................................................................................. 8
1.4.5. Consulting the unified general sales report of an office ................................................... 9
1.4.6. Consulting the general sales reports summary of an office: ............................................ 9
1.4.7. Consulting sales reports of a non BSP/ARC travel agency ........................................... 10
1.5. Sales Report Extension .................................................................................................... 11
1.5.1. Tour Code ...................................................................................................................... 11
1.6. Detailed summary of sales of an office ............................................................................. 11
2. Forms of payment .................................................................................................................... 13
3. Direct issue of electronic ticket ................................................................................................ 14
3.1. Issue tickets CASH .......................................................................................................... 14
3.2. Issue tickets with check ................................................................................................... 16
3.3. Issue tickets with credit card ............................................................................................ 16
3.3.1. Issue tickets with credit card in several payments ......................................................... 16
3.4. Issue tickets with debit card .............................................................................................. 17
3.4.1. Sales with debit card by batch ....................................................................................... 17
3.5. Multiple issue tickets ......................................................................................................... 17
3.6. Issue tickets to invoice (invoice) ....................................................................................... 18
3.7. Ticket issue with free form of payment or miscelanous .................................................... 18
3.8. Issue tickets with exchange form of payment (exchange) ............................................... 19
3.8.1. By mask ......................................................................................................................... 19
3.8.2. Exchange with difference in favor .................................................................................. 23
3.8.3. By transactions............................................................................................................... 25
3.9.3.1 Exchange paying fare difference .......................................................................... 26
3.9.3.2 Exchange paying fare difference with two forms of payment ............................... 27
3.9.3.3 Exchange paying penalty...................................................................................... 27
3.9.3.4 Exchange applying discounts ............................................................................... 28
3.9.3.5 Exchange with passenger selection ..................................................................... 28
3.9.3.6 Exchange selecting segments .............................................................................. 28
4. Variants for the issuance ......................................................................................................... 29
4.1. Passengers ....................................................................................................................... 29
4.2. Segments .......................................................................................................................... 29
4.3. Issue with discounts .......................................................................................................... 29
4.3.1. Issue with discounts excepting a preestablished discount ............................................ 30
4.3.2. Issue with discounts by forcing a fare basis .................................................................. 30
4.4. Quoted taxes replacement ................................................................................................ 30
4.4.1. Taxes exception ............................................................................................................. 31
4.5. Commissions..................................................................................................................... 31
4.6. Endorsment ......................................................................... ¡Error! Marcador no definido.
4.7. Tour Code ......................................................................................................................... 32
4.8. Baggage ............................................................................................................................ 32
4.9. Fiscal key .......................................................................................................................... 33
4.10. Remote issue .................................................................................................................. 33
4.10.1. Sales reports WL ......................................................................................................... 34
4.11. Issue with intervenient field ............................................................................................. 34
4.12. Issue indicating date of birth ........................................................................................... 34
5. Ticketing Masks ....................................................................................................................... 35
5.1. Create the masks header with graphic assistant .............................................................. 35
Versión 2.0 KIU® November 2012 1

5.2. Deleting the masks ........................................................................................................... 37

5.3. Ticket issue with masks .................................................................................................... 38
5.3.1. Ticket issue with form of payment exchange ................................................................. 39
6. Electronic tickets status ........................................................................................................... 40
7. E-ticket printing and recovery .................................................................................................. 40
7.1. E-ticket printing ................................................................................................................. 40
7.2. Sending an e-ticket by e- mail........................................................................................... 41
7.3. Visualize an e-ticket in the screen .................................................................................... 42
7.4. Visualize an e-ticket purged .............................................................................................. 43
7.5. Visualize an e-ticket from another system on KIU screen ................................................ 44
7.6. Visualize an e-ticket history .............................................................................................. 45
7.7. Redisplay an e-ticket in the screen ................................................................................... 46
7.8. Ignoring a displayed e-ticket ............................................................................................. 46
7.9. Retrieve the e-ticket by last name..................................................................................... 46
7.10. Retrieve the e-ticket by number ...................................................................................... 47
7.11. Retrieve the e-ticket by identification number (FOID) ..................................................... 47
7.12. Itinerary printing .............................................................................................................. 47
7.13. Itinerary delivery by mail ................................................................................................. 48
8. E-ticket voiding (VOID) ............................................................................................................ 49
8.1. VOID the only ticket in the PNR ........................................................................................ 49
8.2. VOID of a refund note ....................................................................................................... 50
8.3. Sales report ....................................................................................................................... 50
9. E-ticket refund (Refund) .......................................................................................................... 51
9.1. Direct refund of a document.............................................................................................. 51
9.2. Refund with commission ................................................................................................... 53
9.3. Refund of multiple documents .......................................................................................... 53
9.4. 10.2.1 Refund note generation ......................................................................................... 53
9.5. 10.2.2 Display of a refund note ......................................................................................... 54
9.6. 10.2.3 Close of the refund note ......................................................................................... 55
9.7. 10.2.4 Deleting of the documents included in a refund note ............................................ 56
9.8. 10.2.5 Ignore a refund note ............................................................................................... 56
9.9. 10.2.6 Voiding of a refund note ......................................................................................... 57
9.10. Remote refund of a document ........................................................................................ 58
9.11. Search of a refund note by last name ............................................................................. 58
10. E-tickets status modifications ................................................................................................ 59
10.1. Open for use to Flown ..................................................................................................... 59
10.2. Open for use to Exchange .............................................................................................. 60
10.3. Placing a NO SHOW mark in an Open for use ticket ..................................................... 60
10.4. Deleting a NO SHOW mark from an open for use ticket ................................................ 61
11. Revalidate e-tickets ............................................................................................................... 62
11.1. Revalidation of a flight coupon ........................................................................................ 62
11.2. Revalidation of several flight coupons ............................................................................ 63
11.3. Revalidations with remarks ............................................................................................. 63
11.4. Massive revalidation ....................................................................................................... 63
11.4.1. E-ticket history.............................................................................................................. 64
11.5. Massive revalidation selecting e-tickets .......................................................................... 64
12. Move e-tickets from a purged PNR ....................................................................................... 66
13. Disassociated ticket ............................................................................................................... 68
14. Change of class of a ticket (Upgrade/Downgrade) ................................................................ 69
15. E-MPD documents for excess baggage ................................................................................ 71
15.1. E-MPD issuing ................................................................................................................ 71
15.2. MPD document visualization........................................................................................... 72
15.3. E-MPD printing as passengers receipt ........................................................................... 73
15.4. Change of status of the EMPD to FLOWN ..................................................................... 73
15.5. Sending E-MPD by e-mail............................................................................................... 73
15.6. E-MPD History ................................................................................................................ 74
16. E-MPD documents for penalty and additional services. ........................................................ 75
16.1. E-MPD issue with PNR ................................................................................................... 75

16.2. E-MPD issue without PNR .............................................................................................. 76

16.3. View of an E-MPD ........................................................................................................... 76
16.4. E-MPD printing as passenger receipt ............................................................................. 77
17. Search of an E-MPD by last name ........................................................................................ 77
18. E-ticket exchange for credit e-MPD ....................................................................................... 78
18.1. E-tickets load for the credit generation ........................................................................... 78
18.2. E-MPD issue ................................................................................................................... 79
18.3. Deleting documents in the load....................................................................................... 80
18.4. Ignoring a load ................................................................................................................ 80
19. Direct issuance of e-MPD of credit ........................................................................................ 81
19.1. E-MPD issue with PNR ................................................................................................... 81
19.2. E-MPD issue without PNR .............................................................................................. 82
20. Refunds (Refund) and voiding (Void) of E-MPD documents ................................................. 83
20.1. Voiding a document (VOID) ............................................................................................ 83
20.2. E-MPD refund (Refund) .................................................................................................. 83

1. Personal Sales Report (WA)

In order to be able to issue a ticket within the system, it is required to enable a Personal Sales
Report, which stores all ticketing transactions performed by an agent.
The Personal Sales Report must be opened by the agents before issuing the first ticket.
These reports are associated to each agent’s signature, which is responsible for opening and
closing them. The same sign must be used, except in cases of remote reports’ closure which
is only permitted to certain admin users counting with the proper keyword.
It is only possible to work on a report that has been opened on the day the agent is issuing
tickets and new reports cannot be opened unless the report from the previous day is properly
closed. However, one agent may open multiple reports on the same day as long as each
report is closed before opening the new one.
Although the Personal Sales Report is directly linked to the user’s signature, the reports
remain open even when the user signs out from the system; and they remain open when the
same user signs back in.
1.1. Open
At the beginning of the day, before the first ticket is sold and issued, the agents must open a
Personal Sales Report; otherwise the ticket issuance is not allowed.
This transaction must be used in order to open a new Personal Sales Report:
WA*OPEN
Response:
REPORT SALES OPEN
Note:
It is possible to configure the system settings to automatically open a new Personal Sales
Report at the moment of the first ticket issuance and, if needed, automatically close the
previous one.
1.2. Close
The Personal Sales Reports must be closed after all necessary transactions of the day have
been performed. The Reports closure cannot be undone and some actions are then no longer
available, such as the ticket VOID.
WA*CLOSE
Response:
REPORT SALES CLOSE
1.3. Display
This transaction allows agents to view the currently open Sales Report associated to their
signature.
WA*

Response:
Description:
OFFICE - BUE00XX7 Office ID
SALES REPORT No- 12 Sales Report number
AGENCY No - AR-000040 IATA number or agency code
AGENT-MERLINI/MARIANO(40521) Agent name and sign
DATE - 15 DEC 2004 Sales Report Date
SEQ.No Correlative sequences number
TICKET Issued ticket number
FARE Applicable fare
TAX TAX total amount
COMM Commission applied
NET Net amount (Fare + TAX – Commission)
FP Form of payment
TRANS Type of transaction
TKTT: issued ticket
CANX: voided
RFND: refunded
RELOC Record locator
PAX NAME Passenger name
OBSERVATION Remarks
E-TICKET ISSUED (TKTT) Tickets issued and transaction type (TKTT)

E-TICKET VOID (CANX) Tickets voided and transaction type (CANX)
GRAND TOTAL Total tickets issued

ITEMS Number of issued tickets
ARS 1040.44 Total amount of issued tickets (NET)
OPENED AT - 1237/15DEC Report opened date and time
CLOSED AT - Report closed date and time (empty if still open)

It is possible to work with two different currencies within the system, which splits the reports
according to the currency used.
In case of having issued tickets using two different currencies, the reports are displayed one
below the other.
1.3.1. Display Options
WA Summary report display

WA*CA Tickets issued with FOP cash
WA*CC Tickets issued with FOP credit card
WA*CC+ Tickets issued with FOP credit card with details
WA*IN Tickets issued with FOP invoice
WA*XX Tickets issued with other FOP
WA*CA, IN Tickets issued with multiple FOP
WA*/USD Tickets issued in USD (currency IATA code)
WA*VV Tickets voided
1.4. Remarks
1.4.1. Add to Report
It is possible to add remarks to the sales reports, which is an optional useful functionality that
allows agents to clarify and inform certain actions taken.
WAR(remark)
Example:
WAR CHECK CASHIER DIFFERENCE BY EXCHANGE RATE
Remarks are added as a free text and support up to 100 characters.
1.4.2. Remove from Report

This transaction removes the text added to the report as remarks
WAR
1.4.3. Add to a specific ticket/item

It is also possible to add a remark or note to the line corresponding to any specific item within
the Personal Sales Report.
WAN(item)/(remark)
This text is displayed under the OBSERVATION column on the defined line. The item number
is the one in the SEQ.No. Column of the Sales Report
.

1.5. Remote Closure

It is possible to remotely close the Sales Report of another user in the same Office ID; this
functionality is only available for authorized agents that count with the proper keyword in their
signatures (RPGSPV)
The transaction to close the Sales Report of a different agent is:
WA*CLOSE/(office ID)/(user)/(date)
Example:
WA*CLOSE/TUC00DT0/TUCDT-FN/14DEC
Response:
REPORT SALES CLOSE
Note:
The Office ID may be retrieved with the DNO transaction. The device also contains the
complete Office ID plus two digits; i.e. AEP00XX4 is the office ID and AEP00XX401 is the
device.
It is also possible to remotely close a Sales Report that has been opened by a different user
on a different Office ID if the agent closing the report counts with the keyword RPGSPV, duty
4 and HDQ city configured in the sign.
1.6. Display other agents’ Reports

To consult other agent sales reports must have the keyword RPGSPV on the sign.
The basic transaction is:
WL/OFFICE/DATE
Example:
WL/BUE00XX7/10DEC
Response:
OFFICE - BUE00XX7 AGENCY No - AR-000040 DATE - 15 DEC 2004
REPORT No AGENT OPEN AT CLOSE AT

#DOCS
4 BUEXX-MM MERLINI/M. 10 DEC 2004 10 DEC 2004 2
5 BUEXX-MV VITORIO/M. 10 DEC 2004 10 DEC 2004 0
6 BUEXX-AA ALVARES/A. 10 DEC 2004 10 DEC 2004 8
7 BUEXX-SF SIERRAS/F. 10 DEC 2004 10 DEC 2004 14
Same entry can be performed without indicating the office and the date, in this case would
take by default the proper office and the date of the day..
The transaction is:
WL//
Sale report can be requested for a single date or a range of dates (optional).
In order to request a date range, a dash needs to be added followed by the next date , as
shows below Example:
WL/OFFICE/DATE-DATE

The system shows data until 45 days backwards.
The list of other offices reports can be retrieved, but in order to perform this entry, the user
must be authorized and have the city HDQ, the duty 4 and the keyword RPGSPV in his sign.
The data between [ ] is optional. For example, O it is used to display Open Reports and C for
Closed Reports. In the case that O and C indicators be not included in the entry , both Open
and Close Reports will be shown by default. The report can also be displayed by specific date
or by date range.
Example:
WL/OFFICE/O/DATE [-DATE]
All this transactions could be exported to EXCEL files. To performed this the transaction must
be executed followed by –EXCEL
Example:
WL/OFFICE/DATE -EXCEL
As response you will obtain a link with the name of the file to have direct access to the report
itself.
At the same time, there is an option to retrieve the reports by user, using al the former
examples. In this case instead of the office, user needs to be included.
Example:
WL/BUEXX-MM/20SEP-30SEP
This example will retrieve all the reports of agent BUEXX-MM between 20th and 30th
September.
1.6.1. Consulting the own sales reports
The same way as previous item, you can obtain the own report sales.
No keyword is needed in this case.
The transaction is the same:

WL//DATE Specific date
WL// Reports of own office and actual date
WL//O/DATE-DATE several dates, open records
WL//DATE-DATE several dates, all records
The same way as the previous transactions, these reports can be exported to EXCEL in the
same manner.
Notice:
Same way but with the Keyword RPOFFI, it is possible to retrieve all agents reports of the
own office.
1.6.2. Consulting an specific sales report

To retrieve a specific sales report the transaction is:
WL/OFFICE#Report number

The report number is obtained from the previous report.

As an answer the requested report is displayed.
1.6.3. Consulting the unified general sales report of an office

This transaction allows you to visualize the unified sales report of all the agents of an office,
showing in order all e-tickets issued:
The transaction is:
WL/OFFICE#DATE
1.6.4. Consulting the general sales reports summary of an

office:
A summary of all the sales reports of an office, generated on one day or on a specific date
can be consulted. Keep in mind that when issued in two types of currency, the sales report is
divided into all issued in a currency on one side, and all the other issued in the other. In order
to perform this entry, keyword RPGSPV is required, and needs to have access to city HDQ.
The transaction is:
WR/OFFICE/DATE
Response:
WR/BUE00XX7/27DEC
OFFICE - BUE00XX7 DATE - 27 DEC 2004
======================================================================
TOTAL OFFICE
CASH/CHECK 13 2765.00 479.72 0.00 3244.72

CREDIT CARD 3 600.00 105.36 0.00 705.36
INVOICE 3 765.00 128.52 0.00 893.52
VOID 4 0.00 0.00 0.00 0.00
ARS 4843.60
CASH/CHECK 10 847.46 152.41 0.00 999.87
CREDIT CARD 1 86.44 14.53 0.00 100.97
VOID 2 0.00 0.00 0.00 0.00
USD 1100.84
=====================================================================
=
The Sales Report can also be displayed with more details, including agent’s information and
amount of sales of each agent.
The transaction is:
WR/OFFICE/DATE*
WR/BUE00XX7/27DEC*
OFFICE - BUE00XX7 DATE - 27 DEC 2004
======================================================================
AGENT - BUEXX-MM MERLINI/M. REPORT NUMBER - 18 OPEN
#DOCS FARE TAX COMM NET
CASH/CHECK 2 400.00 70.24 0.00 470.24
CREDIT CARD 3 600.00 105.36 0.00 705.36

INVOICE 3 765.00 128.52 0.00 893.52

VOID 4 0.00 0.00 0.00 0.00
GRAND TOTAL ARS 2069.12
CASH/CHECK 4 271.20 47.64 0.00 318.84
CREDIT CARD 1 86.44 14.53 0.00 100.97
VOID 2 0.00 0.00 0.00 0.00
GRAND TOTAL USD 419.81
----------------------------------------------------------------------
AGENT - BUEXX-XX XIXI/X. REPORT NUMBER - 19 OPEN
CASH/CHECK 6 1365.00 233.88 0.00 1598.88
CASH/CHECK 2 101.70 19.05 0.00 120.75
----------------------------------------------------------------------
AGENT - AEPXX-FF FERNADEZ/P. REPORT NUMBER - 20 OPEN
CASH/CHECK 5 1000.00 175.60 0.00 1175.60
CASH/CHECK 4 474.56 85.72 0.00 560.28

----------------------------------------------------------------------
TOTAL OFFICE
CASH/CHECK 13 2765.00 479.72 0.00 3244.72
CREDIT CARD 3 600.00 105.36 0.00 705.36
INVOICE 3 765.00 128.52 0.00 893.52
VOID 4 0.00 0.00 0.00 0.00
ARS 4843.60
CASH/CHECK 10 847.46 152.41 0.00 999.87
CREDIT CARD 1 86.44 14.53 0.00 100.97
VOID 2 0.00 0.00 0.00 0.00
USD 1100.84
======================================================================
The same way but with the Keyword RPOFFI, all agents reports of an office can be retrieved.
Notice:
If the date and the office are not specified, the system assumes by default the information of
the office where the transaction is executed and the actual date, anyway, a double slash must
be added to frame the office. .
The transaction in this case is:
WR// Basic summary

WR//* Detailed summary
1.6.5. Consulting sales reports of a non BSP/ARC travel

agency
This transaction allows airlines to check the sales report for non BSP/ARC travel agencies.
This transaction can be executed to ask for a specific date:
WQ/OFFICE/DATE
It is also possible to ask for the sale reports for a date range, executing the following
transaction:

WQ/OFFICE/DATE-DATE
In both cases, the report could be exported to an Excel file. To perform this action the
parameter –EXCEL must be added at the end of the transaction.
WQ/OFFICE/DATE-EXCEL
Considerations to take into account to generate the report from the airline:
1. The agency to consult must be NON BSP/ARC and have a credit account with the airline, if
not the system will respond: INVALID OFFICE.
2. If a date range is requested, it cannot exceed 15 days.
3. Sales report can be displayed in the system up to 45 days prior to the current date.
4. The user must have duty 4 and the keyword ADMAGT to have access to the information.
1.7. Sales Report Extension
1.7.1. Tour Code

In order to display a sales report including the Tour Code used to issue the ticket, /TOUR
indicator must be added in the entry.
WL/COR00XXA#9SEP/TOUR
This format can also be applied to reports WA, WL and WQ
1.8. Detailed summary of sales of an office

This transaction allows us to display the sales issued by both, travel agencies and airlines
offices, detailing the fees and taxes collected. Keyword ADMAGT is required.
The transaction is:
DQT{Office ID}* Current date
Example:
DQTLIM002I2* Airline Office ID
DQTLIME8660* Travel agency Office ID
DQT{Office ID}*{FECHA} Specific date
Example:
DQTLIM002I2*22OCT
DQT{Office ID}*{FECHA}-{FECHA} Date range(maximum 15 days)

Example:
DQTLIM002I2*22OCT-29OCT
Note:
This transaction allow us to display 45 days back from requested date and a maximum range
of 15 days

2. Forms of payment
The transaction to visualize the forms of payment is:
FOP
The display shows the code and description of the different forms of payment. At the same
time to see more details about each form of payment, it is executed one of the transactions
explained in the response:
For example to see the allowed credit cards:
FOPCC
It is also possible to see the forms of payment accepted by other company. The transaction
is:
FOP/A5U
FOP Transaction (form of payment)

/ Slash
A Airline indicator
5U Airline code
By default, it brings the forms of payment allowed in the country of origin, but it can also see
the ones allowed in other country, the transaction is:
FOP/CIL
FOP Transaction (form of payment)

/ Slash
C Country indicator
IL Country code
Both the country transaction and the company transaction shows all the forms of payment,
except the FREE form of payment because is confidential information of the company.

3. Direct issue of electronic ticket

Considerations:
The system issues electronic tickets with four coupons, so on those e-tickets with more than
four coupons, the system will issue all the necessary conjunction tickets.
In order to issue a ticket, the PNR must be previously priced, the quotation recorded and
displayed on the screen.
The PNR must not contain UN segments, and it is recommended, that the status codes be
updated and recorded (HK, HL, HM, MM). System will issue exactly what it was priced.
The system allows to issue two or more times an e-ticket to a passenger within same PNR,
but counting from the second issue for the same passenger, the system send an alert
message before performing the operation warning that at least one passenger of the PNR has
a ticket already issued and forcing the user to validate it by executing the entry transaction
again.
By being an electronic ticket it is natural that the companies ask for the identification number
on the issue process, and in case it was not previously added in the PNR, must be added.
To execute this procedure, the transaction is:
-1ø.ID 2041627 it changes or adds the document type and/or number
Description:
- Indicates that the name field is changed
1 Indicates the passenger number to be modified
Ø Change indicator (tab)
. ID indicator
ID 20… FOID Type and number
There are different forms of payment accepted by the system to issue an e-ticket that are
detailed as follows:
3.1. Issue tickets CASH
Taking as an example the following PNR, the transaction to issue e-tickets cash is:
RP/BUE00XX0 - LINEAS AEREAS XX

1.1YANEZ/JUAN
2.1GOMEZ/JOSE
1 XX4420Y 11AUG TH AEPMDQ HK2 12:00 13:15
TKT/TIME LIMIT
1 TL BUE 1800/02 AUG-TUE
CONTACTS
1-BUE 7637333
RECEIVED FROM - PAX
BUE.BUEXX-MM 1354/28JUL05 *YYLUPV
WK*FCA

Description:
WK* Transaction
F Form of payment indicator
CA Cash indicator
Response:
OK. TKTs Nr. 9992200001131

9992200001132
System response is OK followed by the issued tickets numbers with a link to visualize or
recover in the screen.
The PNR will show as the follow:

1.1YANEZ/JUAN
2.1GOMEZ/JOSE
1 XX4420Y 11AUG TH AEPMDQ HK2 12:00 13:15
TKT/TIME LIMIT
1 TKT/OK * 28JUL05/BUEXX-MM
2 TKT/ET 9992200001131 * 28JUL05/BUEXX-MM - YANEZ/J.
3 TKT/ET 9992200001132 * 28JUL05/BUEXX-MM - GOMEZ/J.
FARE - PRICE RETAINED
CONTACTS
1-BUE 7637333
RECEIVED FROM - PAX
BUE.BUEXX-MM 1354/28JUL05 *YYLUPV -H
In the TKT/TIME LIMIT field, the time limit was replaced by an element 1 which indicates that
the issue is OK, the date and the initials of the agent are recorded.
After element 2, we can visualize the tickets number with a link following the date of issue, the
agent sign and the surname of each passenger.
From item 2 onwards, we can visualize the tickets numbers with a link followed by the date of
issue of each ticket, agent´s sign and the passenger´s last name and first initial of the name.
To recover the data from an issued ticket must do CONTROL + click with the mouse over the
ticket´s link or executing the transaction ET/number of item of the ticket in the PNR (This
transaction is developed in the chapter PRINT AND RECOVER THE E-TICKET of the same
guide).
In the same way, ticket can be displayed on a help screen by clicking with the mouse on the
ticket´s link.
All this considerations are accepted for all the possible forms of payment.
In the history will look as follows:
*H
-- HISTORY *YYLUPV --
XTL TL BUE 1800/02 AUG-TUE
ATT OK * 28JUL05/BUEXX-MM
AT FC WK*FCA
ATK 9992200001131 * 28JUL05/BUEXX-MM - YANEZ/J.
ATK 9992200001132 * 28JUL05/BUEXX-MM - GOMEZ/J.

BUE.BUEXX-MM 1356/28JUL05
Deletes the time limit (XTL) and adds the fields of the tickets (ATT).
3.2. Issue tickets with check

The system allows the check as other form of payment, but on the sales report, the same will
be unified with the CASH payment.
The transaction is:
WK*FCK123455878 BANK OF AMERICA
Description:
WK* Transaction
CK Check indicator (after CK code, the text is free)
1234... Free text
3.3. Issue tickets with credit card

The transaction to issue with credit card is:
WK*F/VI4054343467672121/1204/Z8990
Description:
WK* Transaction
/ Slash, indicates CREDIT CARD
VI4054343467672121 Code and credit card number
/ Slash (splitter)
1204 Expiration Date (month & year)
/ Slash (splitter)
Z8990 Authorization code (the Z its mandatory and the code admits
up to 6 characters)
3.3.1. Issue tickets with credit card in several payments
WK*F/AX3489798789789797/1206/Z1235/C1
In the issue transaction with credit card in several payments, the final indicator C after the
slash indicates payments and the following number the quantity of payments that can be up to
12.
In the transaction to issue credit card in installments, the final indicator after the C slash,
indicates installments, and the following number the quantity of payments that may be up to
12.
Sale by batch
Batch between 1 and 6 digits long.

In the same way can be loaded in the Exchange transaction:
WK*F/AX3489798789789797/1206/Z1235/L354
With payments and batch, payments should go first. In the same way can be loaded to the
Exchange transaction:
WK*F/AX3489798789789797/1206/Z1235/C1/L354
Note:
Always remind that the number of payments should go first followed by the batch number.
3.4. Issue tickets with debit card

The transaction to issue tickets with debit card is:
WK*F.EL4054343467672121/Z123
Description:
WK* Transaction
. Dot, indicates debit card
EL4054343467672121 Debit card code & number
/ Slash
Z123 Authorization code (Z it is mandatory and the code admits up
to 6 characters)
3.4.1. Sales with debit card by batch

Usual transaction is used, followed by a slash, the L indicator (batch) and the Batch number
(between 1 and 6 digits). In the same manner can be loaded in the Exchange.
WK*F.EL456465464646/Z1235/L354
3.5. Multiple issue of tickets

The system accepts up to two different forms of payment on the multiple issue, allowing using
anyone of the forms of payment enabled in the system or combined them.
The transaction is:
WK*FCA#/VI4054343467672121/1204/Z8990-120/40XT
Description:
WK*F Transaction
CA First form of payment (CASH on the example)
# Pound divide the forms of payment
/VI4054343467672121 Credit card code & number
/ Slash
1204 Expiration date (month & year)
/ Slash
Z8990 Authorization code (Z its mandatory)

- Dash to divide the amount

120 Amount to pay with the second form of payment (fare)
/ Slash
40XT Amount of airport/security taxes to pay followed by the tax
code
Considerations
In this example only it is indicated the amount paid with the second FOP, the system
automatically calculate automatically the amount of the first FOP from the total, and reflect it
on the sales report.
Also it can be indicated the amount of the first FOP and the system will calculate the amount
of the second FOP.
As a third option may be indicate the amount to be paid on each FOP. In this case both must
be accurate because the system calculates the total amounts against what is quoted.
Keep in mind that when this issue transaction is executed, the system will assume that
amount for each of the passengers who are within the PNR and will issue to them all. When
exist passengers with different fare types (like CHD or ADT) each one of them should be
selected, and apply them the corresponding amount according to the applicable fare.
3.6. Issue tickets to invoice (invoice)

The transaction FOP invoice is:
WK*FIN/MEDITERRANEO
Description:
WK* Transaction
F FOP indicator
IN/ Invoice indicator (invoice or common account)
MEDITERRANEO Free text
Note: The issue of a ticket in a current account, discounts from the virtual report of the proper
account, as explained in the module of Manual Checking Account user guide.
3.7. Ticket issue with free form of payment or miscellaneous

This FOP can be used when there is some FOP that is not addressed in previous ones. The
transaction for the free FOP is:
WK*FXX FREE
Description:
WK* Transaction
F FOP indicator
XX Free indicator
FREE Free text
Also can be used as an option for the miscellaneous FOP the following transaction:
WK*FMS PAY WITH MCO 120890

Description:
MS Miscellaneous indicator
PAY WITH... Free text
3.8. Issue tickets with exchange form of payment (exchange)

The Exchange FOP can be performed on electronic tickets. Tickets can be issued in
exchange for one or more tickets issued. The system validates the status of the original ticket
provided only if it is OPEN FOR USE
Considerations:
The following considerations must be taken into account:
1) Quote the itinerary to issue the same way you would use any other FOP allowed by
the system, as the Exchange is another FOP validated by the system. Once the
itinerary is quoted, the PNR must be recorded.
2) Must display on the screen the e-ticket to be exchanged.
3) It is important to consider that the passengers in the PNR will be issued one at a time.
4) It cannot be exchanged a ticket for a passenger by the name of another passengers.
5) A ticket cannot be partially exchanged. The same must be exchanged for the total of
its OPEN FOR USE coupons (O status).
The system allows the ticket’s Exchange by TRANSACTIONS or MASK, depending on the
variables of the transaction.
3.8.1. By mask
Procedure:
The procedure for issuance in the form of exchange is through a mask which will complete
the data necessary to achieve the objective is primarily to issue a new ticket and change the
status of the tickets that were used to redeem, from OPEN FOR USE to EXCHANGE.
The transaction to perform an exchange by mask is the following:
WK*FEX
This mode of Exchange allows you to manually enter the amounts according to the user
needs.
By executing this transaction the exchange process will begin. This process has 3 steps as
follows:
Step 1:
Exchange Mask – Step 1 Last Name, First Name & Passenger Type
Ticket number or document to be exchanged and the same check digit. In this case the ticket
already displayed on the screen is retrieved by the mask. Regarding CPN DATA field, letter A

indicates that all the coupons will be exchanged (all). If at least one of those coupons is used,
this field will indicate the numbers of coupons to exchange. For Example: 234.
Original issue, Date/Place original issue, Office of original issue, original ticket FOP.
Currency code and net fare amount. This information will be taken automatically by the
system from the ticket to be exchanged; only if the exchange is by the total amount of the
ticket. When the exchange is partial (in case having coupons with status F, R, etc) the user
should complete the blank field with the amount of the coupons to be exchanged. This is valid
for the following blank fields at step 1 (EQUIV. PAID CURRENCY/AMOUNT and PD. TAX
AND CODES).
Equivalent fare amount paid on the original ticket.
Taxes amount paid on the original ticket, followed by each tax code.
There are 8 blank fields to load all the necessary fees and taxes.
In case all original ticket coupons being exchanged, the system will automatically complete
the blank fields with the fees and taxes of that ticket.
In case you want to cancel the mask the CANCEL button can be used.
To continue with the next step must click on the NEXT button.
In case that the amount of the new ticket to be exchanged have at least one used coupon; the
system will warn the user with the following message:
** PARTIAL EXCHANGE - MUST USE MASK **'
Step 2:
Exchange mask– Step 2 Last Name, First Name and Passenger type.

Net fare details, fees and taxes of the new ticket.
Currency type and additional charges to be paid.
Must click on NEXT to continue with the process.
Step 3:
Exchange mask – Step 3 Last Name, First Name and Passenger type.
The system will insert the details of:
A/C EQUIV. FARE: Net additional fare to be collected.

A/C TAX AMT: Fees and taxes additional total amount to collect.
PENALTY AMT: Penalty amount to be collected.
TOTAL A/C AMT: Total amount to be collected.
Notice:
The amounts reflected in the step 3 will be converted automatically by the system to the local
currency of the issuer or the one indicated in the issue.
First form of payment amount, first FOP code.
Second form of payment amount, second FOP code.

In this case, as this is credit card, place the same data as in a credit card issuance. This
means, credit card code follow by number, expiration date and authorization format, all
separated by slashes.
This box allows you to complete the necessary data in case of using other variants, such as
discount fares, remote issue, modifications or tax exceptions, endorsements, commissions,
etc.

Must click on NEXT to finish with the transaction and issue the new ticket.
The system will close the mask, returning to the main screen where the new ticket number will
be displayed:
The new issued ticket has a link to access and visualize it.
Once the new ticket is issued, the coupons of the ticket that were used as the FOP turns to
EXCHANGED status as seen on the following Example:
In the new ticket, same booking details of the PNR will be taken (last name, first name,
segments, etc) and the construction of the ticket fare will be visualized with the following
characteristics:
 In the row FARE and EQUIV are visualized the correspondent to the new fare.
 In TAX appears with PD before the fees and taxes paid on the original ticket.
 The rest of the fees are totalized in XT and then are discriminated on the fare
construction, always with PD before those who were paid on the original ticket.
 In FP appears the total amount of difference to be paid on this new ticket and 0.00
EXCHANGE beside the original ticket number.
Example:
In the sales report it will be reflected as follows:
2 lines are used to discriminate the new ticket. One with the EX form of payment worth 0.00
and another with the new form of payment used and the amount.
Options
The transaction detailed above is the basic of the mask, but there is the option in case that
the PNR has 2 or more passengers to select by passenger. In this case the transaction would
be:
WK*FEX*N1
Description:
* Splitter
N Passenger indicator

1 Number of passenger to issue within the PNR
It is also possible to select the PNR segments to issue. In this case would be:
WK*FEX*S1,3-5
S (segment) indicator is added, followed by the segments to issue.

In the example segment 1 and segment 3 to 5 were selected.
3.8.2. Exchange with difference in favor

When the exchange is made for an amount less than the value of e-ticket that is being used,
the system indicates that there is an amount in favor of the passenger.
In this case, that difference is highlighted in step 2 and if the company has set up the
possibility of issuing credit E-MPD, the system will automatically do it in the next step.
In these cases, the system check the exactly fare amounts and each of the fees and taxes.
Example:
In this case the difference is in favor of the passenger for 408 in fare concept and 44.2 of DL
13.06 of QN. These amounts are shown in negative.
When going to the step 3, by clicking NEXT the following mask will be displayed:

Unlike an exchange with amounts to collect, additional amounts are shown in 0.
And at the right are shown the amounts in favor that will be used to issue the credit E-MPD.
A script confirming the E-MPD issue is also displayed.
When clicking NEXT the new E-ticket is issued, issuing the E-MPD linked to the PNR
Example,
The E-MPD discriminates the fare values of the fees and/or taxes.
In the case that taxes checked are different and some of them are not in the original ticket, or
be less than the amount, the system will display them to be paid with their respective codes.
Example:

In this case the TQ and XR remain to pay and in the next step will be visualized as follows:
The E-MPD will be issued and also the e-ticket with an additional charge for the fees and/or
taxes.
3.8.3. By transactions
Procedure:
This modality will be used in cases where the Exchange is performed on a single e-ticket and
by its total amount. In the cases where it is wanted to make the exchange of an e-ticket with
at least 1 used coupon or when the new ticket amount is less than the exchanged ticket, a
mask must be done. In case of prefer to perform this type of cases by transactions; the
system will open automatically a mask for fill in.
Taking into account above considerations, when a ticket Exchange is performed, transaction
WK*FEX# needs to be used, followed by the supported options in the known forms of
emissions, already known and described on this user guide.
This exchange modality allows the system to automatically calculate the fare net amounts
taken as part of the payment, the fare difference to collect, penalty, taxes, additional, etc.
without the need to use the mask.
Following are detailed some of the possible variables to combine in the exchange transaction:

3.9.3.1 Exchange paying fare difference
WK*FEX#CA
Description:
WK*FEX Transaction
# Pound ( splitter)
CA Form f payment cash
By executing this transaction the system will display as an answer the following information:
Description:
EXCHANGE DOC NUMBER: ticket number to be exchanged, passenger name and type.
ADITIONAL COLLECT AMOUNTS: The system will calculate the fare difference to be
collected and will reflect it by making a comparison between the exchanged ticket amounts
and the ticket to be issued.
EQUIV FARE: in this field will show the amount to be collected as difference.
ARS: Currency code of the collected amount.
OLD: net fare value taken as partial payment for the new ticket issue.
NEW: net value of the new fare.
TAX: in each one of the columns ARS, OLD y NEW, the fees and taxes values will be
inserted.
PENALTY: in this field the amount of the penalty to be collected will be reflected.
TOTAL: in this field will visualize the total amount to be collected as difference, net fare plus
taxes.
A/C TAXS DETAILS: in this field will visualize the additional fees and taxes amounts to be
collected in the new itinerary.
The system will insert the following message:
RE-ENTER FOLLOWING TRANSACTION TO PROCESS

WK*FEX#CA/Y
To confirm the exchange transaction will have to execute the same transaction adding /Y at
the end, or move the cursor to the end of the second line of the script and press ENTER.

OK. TKTs Nr.: in this field the new issued ticket number will be inserted
3.9.3.2 Exchange paying fare difference with two forms of payment

In this case, it is possible to use two forms of payment besides the exchange. Use the same
criteria that the multiple form of payment, placing the first FOP separated from the second
one by a #(pound), and then place the second FOP. A dash is placed followed by the amount
that corresponds to the fare, separated by a slash and the amount that corresponds to taxes,
paid with the second FOP.
The transaction would be, as an example, as follows:
WK*FEX#CA#/DC4546424205891254/1010/Z123-108/57.26
Description:
WK*FEX Transaction
# Pound (splitter)
CA Form of payment (cash)
# Pound (splitter)
/DC4546424205891254 First FOP credit card format
/ Slash
1010 Credit card expiration date
/ Slash
Z123 Authorization number
- Dash (separates amounts)
108 Fare amount to pay with the second FOP
/ Slash
57.26 Taxes amount to pay with the second FOP
3.9.3.3 Exchange paying penalty
WK*FEX#CA*PE50.00XP
Description:
WK*FEX Transaction
* Splitter
CA Form f payment cash
*PE Penalty charge indicator followed by the amount
50.00 Penalty amount
XP Penalty identifier (Figure code)
By executing this transaction the system will display as an answer the following information:

As the same way the issue is confirmed executing the transaction with /Y at the end of the
line.
3.9.3.4 Exchange applying discounts
WK*FEX#CA*Q/AD90/DP90X
Notice: the price stored in the PNR must match the segment indicator applied. In the example
WS*Q/AD90/DP90X
3.9.3.5 Exchange with passenger selection
WK*FEX#CA*N1
3.9.3.6 Exchange selecting segments

This transaction gives the option of selecting the itinerary segments to be exchanged.
If segments on which the exchange will take place are not specified, the system will take as
default, the full itinerary of the PNR.
WK*FEX#CA*S1
Notice: the recorded quotation on the PNR must match with the applied segments indicator.
In the example WS*S1.

4. Variants for the issuance

To be able to use all the variations accepted by the system, it has to be considered that the
PNR must be quoted in the same way which is then used to issue the ticket.
4.1. Passengers
It is possible to issue a ticket selecting one or more passengers of a PNR without splitting it to
issue the tickets. This requires prior forcing the price of passenger type to be issued and
record the same.
The indicator that defines the passenger is: N
Example:
WK*FCA*N1,2
N1,2 Passengers 1 and 2
4.2. Segments
It can be partially issued one or more segments of the PNR. To perform that, those segments
to issue must be priced and its price recorded
.
The segment indicator is: S
Example:
WK*FCA*S1,3,5-7
S 1,3,5-7 Segments 1, 3 and from 5 to 7
4.3. Issue with discounts

A fare can be issued indicating a discount; which will be applied over the 100% of the
passenger that corresponds to the passenger.
WK*FCA*Q/AD90/DP90
Description:
Q Forcing indicator
/AD90/ Discount type (free text up to 9 characters)
DP Discount percentage indicator
90 Quantity that represents the discount percentage.
Note: When ticket is issued with discounts, system recovers as fare basis, the name given to
the discount at the pricing time, and not the name of the discount when issuing the ticket.

4.3.1. Issue with discounts excepting a pre established

discount
The functionality of this transaction is the same as in the previous point but the goal is to
except the discount pre established by the fare rule and quote over the 100% percent of the
published fare. For example in case of issue a CHD passenger that already has a pre
established discount percentage over an adult fare.
WK*FCA*Q/AD90/DP90X
Description:
Q Forcing indicator
/AD90/ Discount type (free text up to 10 characters)
DP Discount percentage indicator
90 Quantity that represents the discount percentage
X Indicator to except discounts in the fare rule and discount over the
100%
4.3.2. Issue with discounts by forcing a fare basis

A fare can be issued indicating a different fare basis to the ones already reserved, this action
will be applied over all the PNR flight segments.
WK*FCA*QVAP
Q Forcing indicator
VAP Fare basis to issue
4.4. Quoted taxes replacement

The quoted taxes can be replaced. This action will delete all the applied taxes replacing them
by those indicated in the transaction:
The indicator is TX.
Example:
WK*FCA* TX20TQ/65SF
TX Taxes replacement indicator

20TQ 20 is the amount and TQ the tax code
/ Flash to divide taxes
65SF Amount and code of the other tax
Fees or taxes not present in the automatic quotation can also be added.
The transactions are:

 To add:
When adding it is important to observe that must be taxes not included in the original
quotation.
WK*FCA*TX+12QO/56.50AR
TX Taxes indicator
+ Add indicator
12 Taxes amount to charge
QO Code of the tax being added
/ Splitter
56.50 Amount of the tax being added
 To delete:
When deleting it is important to observe that must be taxes that were within the quotation.
WK*FCA*TX-XR/DL
TX Taxes indicator
- Delete indicator
XR Tax code to delete
/ Splitter
DL Tax code to delete
Notice:
Both options can be combined putting first those taxes to add and then those to delete.
Example:
WK*FCA*TX+12QO/56.50AR/-XR/DL
4.4.1. Taxes exception

In the same way as the previous variant in this case can be exclude all the fees and taxes to
collect. This action will remove all the taxes applied and will issue the net fare.
The transaction is:
WK*FCA*TXEX
TX Taxes change indicator

EX All taxes exemption indicator
4.5. Commissions
The commission percentage can be added to be discounted at the moment of the issue.
WK*FCA*KP10
KP Percentage
10 Indicates the discount percentage (10% in this case).
This will be reflected on the issued e-ticket and in the sales report with the proper indicators.

4.6. Endorsement
The endorsement field in the issue takes by default whatever the company has set up, but it
can be modified in the issuance.
The indicator is: ED/
Example:
WK*FCA*ED/free text
This will be shown in the endorsements line of the e-ticket.
4.7. Tour Code

In case you want to add a tour code, exists transaction *U, followed by various display options
codes (BT or IT), with or without visualization of the fare.
Example:
WK*FCA*UB/(tour code)
This indicator will print the letters BT in replacement of the fare when the e-ticket is printed.
The name of the tour code is displayed as BT (tour code)
Example:
WK*FCA*UB(tour code)
This indicator will print the fare when the e-ticket is printed.
The name of the tour code is displayed as BT (tour code)
Example:
WK*FCA*UI/(tour code)
This indicator will print the letters IT in replacement of the fare when the e-ticket is printed.
The name of the tour code is displayed as IT (tour code)
Example:
WK*FCA*UI (tour code)
The name of the tour code is displayed as IT (tour code)
Example:
WK*FCA*UN (tour code)
The name of the tour code is displayed without any single code.
The tour code field accepts up to 12 alphanumeric characters.
4.8. Baggage
The baggage field in the issuance, takes the default that the company has configured
according to the type of trip, but it can be modified during the issuance.

The indicator is BA
Example:
WK*FCA*BA 15K (or 2P or 20L)
BA Baggage indicator
15K 15 kilos
2P Pieces
20L 20 pounds
4.9. Fiscal key

The Key field can be used as an option. The format can be free or can have a rigid format,
depending on the configuration selected by the company.
The indicator is: VT/
Example:
WK*FCA*VT/fiscal key number
This will be reflected in the e-ticket, below the passenger type.
The maximum number of characters to VT field is 50 (between numbers, letters and spaces).
4.10. Remote issue

The system gives the possibility of issue remotely a ticket; it means that a user located in any
office, could issue a ticket, leaving it settled in the remote office sales report.
To perform a remote issue, system will validate the following conditions:
A). the user profile must have assigned the keyword ISSREM
b). the reservation must be quoted in remotely, if the fare conditions specify this.
Quotation with remote point(if it is necessary)
You can force the remote point of the quote by using another city.
WS*RCity
Example: WS*RMVD
WS Transaction
* Splitter
R Remote point indicator
MVD City from which the quotation is apply
Once the reservation is remotely quoted the remote issue of the ticket could be executed.
Issue at remote point
To perform the remote issue the following transaction must be used:

WK*F(Form of payment)*R(Remote office)
Example: WK*FCA*RMVD00XX2
WK*F Issue transaction

CA Cash
* Splitter
R Remote point indicator
MVD00XX2 Office in which the issue is going to be done
4.10.1. Sales reports WL

When performing a remote issuance, the sale will be reflected in the report of the indicated
city, but with the user who actually performed it.
4.11. Issue with intervenient field

Once you create a client can use the code to issue the e-ticket. The transaction to issue is the
following:
WK*FCA*I/55555
WK*FCA* Rigid Transaction for an issue with FOP Cash

I/ Intervenient indicator
55555 Client code created in the chart
This transaction will apply the correspondent commission, according to the chart, and will
place the code in the e-ticket, below the record locator.
Consulting the intervenient chart

The transaction to visualize the table is:
INT
If the response is TOO MUCH ITEMS, the following filters must be used:
INTCity Shows the intervenient for the specified city
Example: INTBUE
In case it still indicating TOO MUCH ITEMS, must continue filtering by the clients initials:
INTCity/A Show the city intervenient beginning with the letter A
Example: INTBUE/A
Another way to filter is:

INTALL/A
Indicates all cities in that the intervenient begins with the letter A
4.12. Issue indicating date of birth

To indicate the date of birth at the moment of issue a ticket, must enter:
WK*FCA*DOB/20APR77

This field is optional and will be reflected in the e-ticket.
Description:
* Mandatory splitter
DOB Date of birth indicator (Date of Birth)
/ Mandatory slash
20APR77 Date of birth. The format is DDMMMYY
5. Ticketing Masks
The purpose of the masks is to be able to issue tickets with non published fares.
The fare masks must be created in order to take the necessary information with which then
will be issued the ticket..
This way a mask will be recorded with a 30 days validity period.
Once the validity expires, the mask will be deleted.
5.1. Create the masks header with graphic assistant

To create a mask is necessary to have a PNR recently retrieved (without recently
modifications) and without UN segments.
In case have to make modifications in the PNR, they must been made, recorded and the PNR
must be retrieved again “clean”.
The transaction to start creating a mask is:
W*TKT
This transaction displays the following screen:

Once this screen is retrieved all data must be loaded on each box, once completed the
necessary data, you must continue to the next screen, by clicking NEXT.
This screen is also completed with the necessary data and once finished, must click on
Finish.
The response will show al data loaded as follows:
ADT (MASK #1)

NON END/NON REF AEP/COR
1 o AEP XX 4580Y 22JAN 1800 OK YESPECIAL K/15
COR
ARS 50.00 FC/AEP XX COR TTL ARS50.00 END
XT 10.00
ARS 60.00
BUE.BUEXX-MM 1956/15DEC04
If all data is correct, the PNR must be recorded with ER, if not can ignore with I to start over.
When recording the PNR with ER and retrieving it again, you will see a REMARKS field
where the mask was stored.
Example:
1.1ALCORA/A
1 XX4580Y 22JAN SA AEPCOR HK1 18:00 19:15
TKT/TIME LIMIT
1.TKT/OK * 15DEC04/BUEXX-MM
2.TKT/ET#9992200000362 * 15DEC04/BUEXX-MM - ALCORA/A.
3.TKT/ET 9992200000362 * VOID
CONTACTS
1-BUE 0

REMARKS
1-»» FARE MASK STORED
BUE.BUEXX-MM 1852/15DEC04 *RFCZVZ -H
Once the mask is saved, you can proceed to issue.

Up to 9 masks can be loaded within a same PNR.
It is important to have in mind that the masks are created by type of passenger. The
transaction W*TKT takes by default one ADULT passenger mask, if you want to create some
for CHD or INF, the transactions would be:
W*TKT*PCHD for Child
W*TKT*PINF for Infant
To visualize all the masks loaded within a PNR, the transaction is:
W**
Response:
MASK LIST
1 ADT
2 CHD
3 INF
4 ADT
To view the detail of each mask entered in the PNR, must be entered
W* followed by the number of mask. Example: W*1 or W*2 or W*3.
Notice:
For BT fares, as in the masks loaded by transactions, the TOUR CODE blank field must be
filled, with the initial BT and free text later.
For the automatic fare construction, the field with the same name can be marked, leaving in
blank the manual construction field.
5.2. Deleting the masks

The masks have a 30 day period of validity once are loaded, but can be manually deleted if
necessary.
The transaction is:
W*D
This transaction will delete the loaded mask in the PNR.

The correct answer is DONE
By closing the PNR the Remark field will be automatically deleted:

In case of being 2 or more masks loaded in the PNR they can be deleted individually or
partially.
The transaction would be:
W*D1,3 delete mask 1 and 3
Response:

MASK LIST
1 F CHD
Shows the masks that remained recorded in the PNR. The F that appears between the mask
number and the type of mask indicates that were already fared.
5.3. Ticket issue with masks

The ticket issue with mask is very similar to the direct issue. The difference is that it should
clarify which is the mask to be issued, besides the passengers, in the case of having different
type of passengers.
As in the direct issue, the same forms of payment are used, applying them in the same way.
It is indispensable to have the mask to be used, loaded and recorded in the PNR.
Example:
Once completed and recorded the mask, the ticket issue can be generated.
Taking as example the following PNR, the issue transaction is:

1.1CORIA/WILLIAM
2.1CANAS/GUILLERMO
1 XX4600B 28APR MI AEPMDQ HK2 7:30A 8:30A
2 XX4303Y 30APR VI MDQAEP HK2 12:00P 1:00P
TKT/TL BUE 1800/25APR-SUN
PHONES
1-4536 1723
REMARKS
RECEIVED FROM - PAX
BUE.BUEXX-MM 2034/20APR04 *DFACKN -H
WK*M1*FCA
WK*M Transaction
1 Mask number
* Splitter
F Form of payment
CA Cash
Response:
OK. TKTs Nr. 999-2100000147
999-2100000148
Shows the issued tickets numbers
When retrieving the PNR, it will be visualized as follows:

1.1CORIA/WILLIAM
2.1CANAS/GUILLERMO
TKT/TIME LIMIT
1 TKT/OK * 20APR04/BUEXX-MM
2.TKT/ET 9992100000147 * 20APR2004/BUEXX-MM - CORIA/W

3.TKT/ET 9992100000148 * 20APR2004/BUEXX-MM - CANAS/G

PHONES
1-4536 1723
REMARKS
RECEIVED FROM - PAX
BUE.BUEXX-MM 2034/20APR04 *DFACKN -H
In place of the expiration date, a ticket field is generated for each ticket issued with its
number, the passenger´s last name/initials and the date of issue.
The tickets will be issued with the value that they were loaded in the mask.
By executing the transaction, the data is recorded into the PNR as an end transaction and this
action is recorded in the history.
Example:
*H
-- HISTORY *DFACKN --
XTL TL BUE 1800/25 APR-SUN
ATT OK * 20APR04/BUEXX-MM
AT FC WK*FCA
ATK 9992100000147 * 20APR04/BUEXX-MM - CORIA/W.
ATK 9992100000148 * 20APR04/BUEXX-MM - CANAS/G.
BUE.BUEXX-MM 1356/28JUL05
5.3.1. Ticket issue with form of payment exchange

The transaction to use a payment exchange with an already paid and issued ticket is:
WK*FEX*M1*N1
W*EXC Transaction for exchange

* Splitter
M2 Mask indicator and number
* Splitter
N1 Passenger indicator 1
The procedure and the rest of the mask is completed in the same way as detailed in the direct
issue ,reminding that the fare to apply in the new ticket issue, will be the value of the mask.

6. Electronic tickets status

The status of the ticket allows us to know the status of each e-ticket coupons of the same.
Each coupon has a status. Here is a description of each status code:
O OPEN FOR USE

Means it is available to be used. It status is open.
F FLOWN
Means that it was already used to fly. Not available for use.
E EXCHANGED
It means that it was exchanged to issue another ticket. Not available for use.
V VOID
Means that it was canceled thus is not available for use.
R REFUNDED
Means it was returned. Not available for use.
I IRREGULAR TRANSACTION
It means that experienced some kind of irregular transaction. Not available for
use. It usually appears when the flight was not closed at the check in
procedure.
N NOTIFICATION
Means that is an exclusive code for the airlines use. Not available for use.
C CHECKED-IN
Means it was checked in for the boarding, when the flight is closed will
automatically become FLOWN. Not available for use.
Z CLOSED
It means that the coupon is closed or disable. Not available for use.
7. E-ticket printing and recovery
7.1. E-ticket printing

Once issued the e-tickets you can print a copy for the passenger control. It will contain all
itinerary details. Taking the following PNR as an example, the transaction would be:

1.1MANTILLA/FELIX
2.1ROBREDO/TOMY
TKT/TIME LIMIT
1.TKT/ET 999-2100000150 - MANTILLA/F * 21APR2004
2.TKT/ET 999-2100000151 - ROBREDO/T * 21APR2004
PHONES
1-56555 767
REMARKS

RECEIVED FROM - PAX

BUE.BUEXX-MM 1327/21APR04 *YZPNUD -H
ITR/2
ITR/ Transaction
2 e-ticket line number
Printing is also available indicating the ticket number.
ITR/9992100000151
ITR/ Transaction
9992100000151 e- ticket number
You can print the e-ticket from the ticket displayed on the screen:
ETP/ticket number
Or
E
ETP/Ticket item number within the PNR
This transaction prints the coupons of the ticket in the format that is displayed when
recovering with ET( see 8.3 Visualize an e-ticket in the screen).
7.2. Sending an e-ticket by e- mail

Sending e-ticket by mail is set by company.
The transaction to send is:
ITR/2-mmerlin@mail.com
ITR/ Transaction
2 Ticket item number
- Dash (splitter)
mmerlin@mail.com e-mail address
In the same way as in printing, it can be placed the complete ticket number by replacing the
item number.
An e-mail address can be loaded in the contact field and use the same contact to send the e-
ticket.
Example:
ITR/2-M2
M E-mail indicator
2 Item number in the contact field
M can be placed only if there is a one email contact.

You can also send an email with the following transaction (in order to be able to use this
option ticket must already be displayed on the screen).
7.3. Visualize an e-ticket in the screen

The electronic ticket can be visualized in the screen once issued. The transaction with a
displayed PNR would be:
ET/2
ET/ Transaction
2 Ticket number item
Without the PNR displayed, the same transaction can be executed by replacing the item
number for the ticket number.
Example:
ET/9992100001678
Response:
TKT-9992200001679 0 * ISSUE * YBIUQC
OD-AEPCOR SI-SITI POI-BUE DOI-28OCT05 IOI-55-956456
ED-NON END/NON REF
1.RAMO/ALDO ADT STATUS
1 o AEP XX 4500 Y 23NOV 0750 OK Y 15K OPEN FOR USE

COR
FARE ARS 160.00 BSR 1.000000

EQUIV ARS 160.00
TAX ARS 17.34DL 5.12QN 7.05XT
TOTAL ARS 189.51 COMMISSION :
/FC AEP XX COR ARS160.00Y TTL ARS160.00 END XT 1.00TQ 6.05XR
FP MS 99982983923
Description:
TKT-9992200001679 0 * ISSUE * YBIUQC
Ticket number and record locator to which it belongs
OD-AEPCOR
Origin and destination
SI-SITI
ISI code
POI-BUE
Point of issue
DOI-28OCT05
Date of issue
IOI-55-956456
IATA agent/office code
ED-NON END/NON REF

Endorsement field

Last name/first name, passenger type, ticket data, and itinerary and flight coupons status. In
this case OPEN FOR USE.
Ticketing information, paid taxes, fare construction and form of payment.
*Another way to retrieve the electronic ticket on the screen is by executing:

CONTROL+CLICK with the mouse over the ticket link.
*There is a way to view the ticket in a help screen without retrieving it in the main screen. The
procedure to retrieve the ticket on the screen is by clicking over the ticket link. A help screen
will be display in the following format:
This screen is independent from the working areas and is useful to visualize the ticket data.
7.4. Visualize an e-ticket purged
According to IATA criteria (Resolution 722f, Section 4 of manual “Passenger Services

Conference Resolutions”) informs that the system (CRS/GDS) must ensure access to
documents (tickets, MDPs, refund notes) on-line for 13 months from the date of issuance if
there is at least 1 coupon with any of the following states:
 O OPEN FOR USE

 I IRREGULAR TRANSACTION
 N NOTIFICATION
 G EXCHANGE/FIM
 L LIFTED/BOARDED
 S SUSPENDED
 U UNAVAILABLE
However, if the ticket has all the coupons with any of the states listed below, the document
must remain on-line 7 days after the last date of use.
 F FLOWN
 P PRINT
 E EXCHANGED
 X PRINT EXCHANGE
 V VOIDED
 Z CLOSED

Note: The purged documents will be available on Data Explorer Module
When checking a ticket, purged from the reservation system, system will respond the
following message (in English or Spanish as you have configured each terminal):
TICKET NOT FOUND – ENTER THE FOLLOWING TRANSACTION TO CONSULT USING

KIU DATA EXPLORER APPLICATION
TICKET NO ENCONTRADO - INGRESE EL SIGUIENTE COMANDO PARA REALIZAR LA

CONSULTA EN EL MODULO KIU DATA EXPLORER
Below this message appears the transaction must be entered to look for the ticket in the Data
Explorer module. The input is the same that is used to display an e-ticket from KIU but adding
an asterisk at the end, as shown below:
ET/3002600125667*
Entering this transaction, text "LOAD APPLICATION" will be read in KIU screen until a web
browser is opened, where you can view ticket information and history.
7.5. Visualize an e-ticket from another system on KIU screen

The visualization of an electronic ticket issued by other system, will be made of following
manner , and will reflect passenger data, flight number, segments issued in each coupon,
class of service, travel date and check-in status (checked or flown) for each coupon.
Open for use
-- OTHER SYSTEM TICKET * TNMOEV --

15MAR10/SYS-TTYB - TORRES/SABRINA
CPN FLT RBD DATE SEGMENT

1- XX4112 Y 16MAR AEPSLA
Checked in


1- XX4112 Y 16MAR AEPSLA-C
The –C indicator at the end of the segment represents status CHECKED-IN.
Flown


1- XX4112 Y 16MAR AEPSLA-F
The –F indicator at the end of the segment represents status FLOWN.
7.6. Visualize an e-ticket history

The e-ticket history with the PNR displayed can be seen with the following transaction:
ETH/2
ETH/ Transaction
2 Ticket item number
With the PNR displayed the same transaction can be executed by replacing the item number
for the ticket number.
Example:
ETH/9992100123654
Example:
ETH*
TICKET HISTORY DISPLAY ** 9992200001692 6
CPN FRM/TO FLT CL DATE ST DEVICE SIGN TIME/DATE OBSERVATION

1 AEPCOR XX4500 Y 23NOV E BUE00XX000 AEPXX-AA 2121 2NOV05 » ISSUE TKT
9992200001697
XX4500 Y 23NOV O BUE00XX000 AEPXX-AA 2108 2NOV05 POR CANCELACION DE
VUELO
XX4500 Y 21NOV - BUE00XX000 AEPXX-AA 2107 2NOV05
CPN e-ticket coupon

FRM/TO Origin and destination
FLT Flight
CL Class
DATE Date
ST Status
DEVICE Device
SIGN User sign
TIME/DATE Tome and date of issue
OBSERVATION Observations
In addition to the e-ticket data may also appear the record locator data when the passenger
has been divided or moved from its original record.

Example:

1 AEPCOR XX4500 Y 24NOV O BUE00XX000 AEPXX-AA 2151 2NOV05
ACTION FROM TO SIGN TIME/DATE

»SPLIT OCWYRV HAABZE AEPXX-AA 2151 2NOV05
In this case a split action was executed (ACTION SPLIT) on the original record (OCWYRV)
to a new record (HAABZE) ,setting the sign, time and date of the transaction execution.
7.7. Redisplay an e-ticket in the screen

This transaction is use to redisplay an electronic ticket active in the working area, which has
been previously retrieved.
The transaction is:
ET*
To redisplay the history of an e-ticket. The transaction is:
ETH*
7.8. Ignoring a displayed e-ticket

This transaction is used to ignore an e-ticket displayed in the working area.
It is convenient to use it in order to avoid working on the displayed e-ticket by mistake or
omission.
The transaction is:
ETI
7.9. Retrieve the e-ticket by last name

There is a way to retrieve the e-ticket by passenger last name.
The transaction is:

*T/LAST NAME
This transaction will display a list of all the tickets found with the mentioned last name, with an
access link to the e-ticket.
The search can also be restricted by placing the name and the issue dates.
Examples:
*T/LAST NAME/NAME
*T/LAST NAME/NAME/20SEP06 From the asked date in advance

*T/LAST NAME/20SEP06 From the asked date in advance (only last name)
*T/LAST NAME/NAME/20SEP06-30SEP06 Between the asked dates
7.10. Retrieve the e-ticket by number

Also exists a way to retrieve an e-ticket by the number.
The transaction is:
*T/TICKET NUMBER
This transaction will display the asked ticket with an access link to it.
It is possible also search without specifying the entire ticket number, placing the last 6 digits
of the ticket.
*T/123456
Another option is to search the last 3 ticket numbers. In this case must apply a date range
indicating the estimated date of issue.
The system will display the ticket or a ticket list containing the requested numbers considering
recent numbers. The following example will search all those tickets ending in 123.
*T/123/DATE/DATE
The DATE/DATE indicator restricts the search to a period that cannot be over 31 days. It is
mandatory and the range must belong to the ticket issue date.
7.11. Retrieve the e-ticket by identification number (FOID)

Another way to retrieve an e-ticket is by the passenger’s personal id number (FOID). In this
case, please note that you must have the ID number loaded when the issue was made.
The transaction is:
*T/.ID NUMBER
This transaction will display a list of all tickets that were found with that ID number with a link
to access to each of them.
As in the previous sections can be used the same dates options.
7.12. Itinerary printing

Besides the e-ticket printing, there is the possibility to print only the PNR itinerary.
The transaction is:
IE
This transaction prints information of the full itinerary and all passengers in the PNR. For that,
the PNR must be previously displayed in the screen.

This information can be printed without having the PNR displayed. To perform this, the
transaction is:
IE/RECORD LOCATOR
There is also the possibility of filtering the information by passenger and by segment.
The transaction is:
IE*S1*P1
Description:
IE Transaction
* Asterisk
S Segment indicator
1 Segment number to print
* Asterisk
P Passenger indicator
1 Passenger number to print
Both indicators (segment or passenger) can be executed individually.
7.13. Itinerary delivery by mail

The itinerary delivery by mail is set by company.
The transaction to send the itinerary is:
IE-mmerlin@mail.com
Description:
IE Transaction
- Splitter
mmerlin@mail.com Mail address
It also an e-mail can be loaded in the contacts and use it for the itinerary delivery.
Example:
IE-M2
M MAIL indicator
2 Item number of the contact field.
The M indicator can be placed only in case there is a single mail contact.
The passenger and segment filters can also be used in the e-mail delivery.
Example:
IE*S1*P2-mmerlin@mail.com

8. E-ticket voiding (VOID)

An electronic ticket can be voided only if it meets the following conditions:
a) Personal Sales Report must be open

b) The PNR at which the e-ticket belongs must be displayed
c) The ticket must be within the current active Personal Sales Report or of the day.
d) To perform the remote voiding of a ticket the user must have the keyword RPGSPV.
Once the mentioned conditions were accomplished, the transaction to void an e-ticket is:
W*V9992100212135
W* Transaction
V Void indicator
9992100212135 Ticket number
The system will respond the following message:

W*V9992100212135/Y
In order to validate the ticket voiding action, same transaction must be executed by adding /Y
at the end of the transaction or on the transaction, press ENTER.
NOTE 1
When you void a ticket that was issued with EXCHANGE form of payment, the original e-
ticket that was used in the Exchange will go back to OPEN FOR USE status.
NOTE 2
When you void a ticket that was issued from a remote office, this action will be recorded in the
sales reports of the agent who had made the issue.
8.1. VOID the only ticket in the PNR

At the time of VOID an e-ticket, if the ticket to VOID is the only one in the PNR, the system
places an automatic cancellation expiration of 10 minutes from the moment of the execution
of the voiding transaction.
Example:
W*V9992200013196
W*V9992200013196/Y
OK
SALE IS CANCELLED IN REPORTING SYSTEM
TIME LIMIT SET TO TX AEP 1209/20JUN-FRI
The PNR will be seen as follows:
RP/AEP00XX4 - LINEAS AEREAS XX

1.1ALMEYRA/DIEGO »CI3892382
1 XX4420Y 22JUN SU AEPMDQ HK1 1205 1315
TKT/TIME LIMIT
1 TX AEP 1209/20JUN-FRI


CONTACTS
1-AEP +99 (99) 999-9999 LINEAS AEREAS XX
AEP.HLP/DESK102 1459/20JUN08 *QFAQZE –H
8.2. VOID of a refund note

If a refund note, which was performed against a credit account, is voided, the system verifies
the account credit and allows you to perform the voiding operation, if the account has enough
credit.
When a refund note is voided, the documents contained therein, change back to OPEN FOR
USE status.
8.3. Sales report

The sales report will reflect the refund note number that has been generated by the
documents refund.
The information will be visualized on the TICKET column, inside the item E-TICKET
REFUND.
OFFICE - BUE00XX0 SALES REPORT No- 292 AGENCY No - AR-000020

AGENT - HLP/DESK105 (105) DATE - 14 JUN 2007
SEQ.No. TICKET FARE TAX COMM NET FP TRANS RELOC PAX NAME OBSERVATION
-----------------------------------------------------------------------------------------------------------------------------
E-TICKET ISSUED (TKTT)
00001 9992200008265 308.00 50.28 0.00 358.28 CA TKTT TMTNPO DIAZ/MARIA
00002 9992200008267 616.00 94.50 0.00 710.50 CA TKTT JVWFXB MORENO/D
00003 9992200008268 308.00 50.28 0.00 358.28 CA TKTT ETINLU MORENO/D
00004 9992200008269 308.00 50.28 0.00 358.28 CA TKTT IOAIZJ MORENO/DANIEL
00005 9992200008282 154.00 28.67 0.00 182.67 CA TKTT AESUKC DIAZ/PEDRO
00006 9992200008283 154.00 28.67 0.00 182.67 CA TKTT AESUKC MORENO/CARLOS
E-TICKET VOID (CANX)
00007 9992200008266 0.00 0.00 0.00 0.00 CA CANX DSPRKW MORENO/D
E-TICKET REFUND (RFND)
00008 9998000000114 -308.00 0.00 0.00 -308.00 CA RFND DIAZ/MARIA
00009 9998000000115 -308.00 0.00 0.00 -308.00 CA RFND MORENO/D
00010 9998000000116 -308.00 -7.05 0.00 -315.05 CA RFND MORENO/D
-----------------------------------------------------------------------------------------------------------------------------
GRAND TOTAL ITEMS
CASH/CHECK 9 924.00 295.63 0.00 1219.63
CREDIT CARD #
DEBIT CARD #
INVOICE #
OTHERS #
ARS 1219.63
EXCHANGE 0
VOID 1
=============================================================================================================================
OPENED AT - 1027/14JUN CLOSED AT -
# END OF REPORT #

9. E-ticket refund (Refund)

The system will generate refund notes, against the execution of refund transaction of e-tickets
or MPDs.
The refund note is a document that is generated when making a refund of any document
issued.
The e-tickets and MPDs numbers retrieved will remain associated with the refund note that
contains such refund.
A refund note may contain more than one document to refund.
The refund note will be automatically generated and can be consulted and displayed in the
system. The refund notes should be displayed with the transaction ET/refund note number.
The refund notes can be “VOIDED”.

By voiding a refund note, the documents contained there, will change back to its original
status.
The following will detail the functionality and the way the information is displayed in the
system from the moment of this update:
Conditions:
An electronic ticket refund can be performed, only if the following conditions are met:
a) The personal sales report must be open (if not it will be opened automatically)
b) The flight coupons to refund must be with the status O (Open for Use)
c) All tickets to refund must be issued in the same currency
d) You always have to indicate the amount to refund
e) If any of the documents to refund will be returned to a credit account, all the documents
must be returned to the same account
9.1. Direct refund of a document

Must consider that partial refunds of a document can be performed ( is not mandatory refund
all the e-ticket coupons) and that a refund note will be generated.
The transaction to perform the refund is the following:
W*R9992200008263/E2/DEV X MET-ARS308.00/1TQ*FCA
Description:
W* Transaction
R Refund indicator
9992200008263 Ticket number
/ Splitter

E Electronic coupon type indicator

2 Coupon number to refund
/ Splitter
DEV X MET Transaction remark (optional, máx. 50 characters)
- Dash to indicate the amount loading
ARS Currency in what the refund is made
308.00 Fare amount to refund
/ Splitter
1TQ Taxes to return, can be entered all the quantity of necessary
taxes.
* Splitter for indicate Form of Payment
F Form of Payment indicator
CA Form of Payment (with the same formats and criteria of the
ticket issue)
When this transaction is executed the system will display the following script:
REFUND WILL BE PROCESS
DOCUMENT NUMBER CPN FARE TAX PEN/OTHS COMM. NET

9992200008263 2 -308.00 -1.00 0.00 0.00 -309.00
FORM OF PAYMENT (NOT INCLUDE COMMISSION)

-309.00 CA

W*R9992200008263/E2/DEV X MET-ARS308.00/1TQ*FCA/Y
To confirm the ticket coupons refund, must execute the same transaction by adding /Y at the
end of the transaction line or moving the cursor to the end of the second line of the system
response and press ENTER.
The system will return the following message:
OK. REFUND NUMBER 9998000000113
The message informs the refund note number, which has been generated and contains the
ticket refund. The same can also be seen in the history of the e-ticket that generated the
refund.
The refund note can be consulted with the following transaction:
ET/9998000000113
When performing this transaction, the system returns the following information, where you
can visualize the e-ticket or MPD number that was refunded and that is contained in the
refund note consulted:
RFND-9998000000113 6 * REFUND * TRANSAC: RFND

POI-BUE DOI-13JUN07 IOI-AR-00002-0
ED-
1.MORENO/DANIEL
FOID: DNI 4444

9992200008263 2 308.00 1.00 0.00 0.00 309.00
EQUIV ARS 308.00 PENALTY :

TAX ARS 1.00TQ
TOTAL ARS 309.00 TOUR CODE :
COMMISSION :
FP 309.00 CASH

Note
At the moment of indicate the coupons to refund, sign + can be enter, after E field, in order to
indicate that all coupons with status OPEN FOR USE will be refunded. The transaction using
the sign + is conformed as follows:
W*R9992200008231/E+-ARS616*FCA
When performing this transaction the system responds the following message, where it can
be visualized in the CPN column that the coupons 1 and 2 are going to be refunded:

9992200008231 12 -616.00 0.00 0.00 0.00 -616.00

-616.00 CA

W*R9992200008231/E+-ARS616*FCA/Y
May also be used all forms of payment enabled in the system, including multiple forms of
payment, as explained in the corresponding chapter in this manual.
9.2. Refund with commission

In the cases that an e-ticket issued with a commission must be refunded, the commission
should be retained. The transaction to retain the mentioned commission is, for Example:
W*R9992200008263/E2/DEV X MET-ARS308.00/1TQ/KP8*FCA
KP8 represents the paid commission in the original e-ticket that, in the example is of an 8%.
9.3. Refund of multiple documents

A multiple documents refund can be generated. In this case a refund note must be generated,
to which, you associate the different documents that will be refunded.
It must keep in mind that all documents entered into the refund note, will be returned in the
same form of payment, and in case of a common account, will be returned to the same
account.
A refund note may contain from one to ten documents to refund.

In the same refund note, both e-tickets and/or MPD documents can be include.
9.4. 10.2.1 Refund note generation

To generate a refund note the following transaction must be enter:
WRFN/ADD[ticket number]/E[coupon number]/Remarks (optional)-[currency and

amount]/[taxes]
Example:
WRFN/ADD9992200008171/E1/AUTH SUP-ARS200/25.79DL/7.62QN/6.05XR

Description:
WRFN/ Transaction to generate a refund note
ADD Transaction for add documents to the refund note 9992200008171
Document number to refund
/ Slash
1 Coupon number for refund (several coupons can be entered or the +
symbol that represents all the coupons with OPEN FOR USE status)
/ Slash
AUTH SUP Remark. Optional field

- Dash before the currency in which the document will be refunded.
ARS200 Currency code and amount to refund
/ Slash
25.79DL Tax amount and code to refund. Up to three taxes per document to
refund can be entering.
Note:
During the loading of the documents to be refunded, the form of payment must not be
indicated.
This procedure should be repeated as many times as documents you want to refund and
include in the refund note.
When adding each new document. The system will respond the following message as
response:
DOCUMENT ADD FOR REFUND OK.
9.5. 10.2.2 Display of a refund note

During the process of generating a refund note, it can be retrieved and redisplayed.
By performing this transaction, the system allow you to visualize all documents that have
been added up to the moment to the refund note.
The transaction to reordering and visualize the documents contained in the refund note is:
WRFN/*
After performing this transaction, the system will display the information of the documents
contained in the refund note up to the moment:
DOCUMENTS TO REFUND * IN ARS *
It. DOCUMENT NUMBER CPN FARE TAX PEN/OTHS COMM. NET

1. 9992200008171 1 -200.00 -40.46 0.00 0.00 -240.46
2. 9992200008172 1 -515.00 -79.33 0.00 0.00 -594.33
3. 9995090000306 1 -10.00 0.00 0.00 0.00 -10.00
4. 9995090000307 1 -15.00 0.00 0.00 0.00 -15.00
In the first line is expressed the currency in which the documents will be refunded * IN ARS *
The documents are numerated as they are incorporated into the refund note. The numeration
can be seen in the It. (item) column
DOCUMENT NUMBER Document number to refund

CPN Document coupon number to refund

FARE Fare amount to refund
TAX Taxes amount to refund
PEN/OTHS Penalties and other charges amounts (penalties/others)
COMM. Commission amount to refund
NET Net amount to refund for each document (fare + tax +
pen/oths + comm.)
9.6. 10.2.3 Close of the refund note

Once you have entered all documents to be refunded, you should proceed with the closing of
the refund note. For closure and confirmation of the note, the transaction is as follows:
W*R*FCA
W Transaction
* Asterisk (splitter)
R Action code that represents the refund
F Transaction that is always place before the form of payment
CA Form of payment. In this case the refund of all the refund note documents is
made in cash.
Once the transaction was executed, you must press the ENTER key and the system will
display the following information, where you can be view the total amount to be refunded and
the way that is going to be perform the refund of all the documents included in the refund
note:

9992200008171 1 -200.00 -40.46 0.00 0.00 -240.46
9992200008172 1 -515.00 -79.33 0.00 0.00 -594.33
9995090000306 1 -10.00 0.00 0.00 0.00 -10.00
9995090000307 1 -15.00 0.00 0.00 0.00 -15.00

-859.79 CA

W*R*FCA/Y
To confirm the refund note, must execute the same transaction adding /Y at the end of the
transaction line, or move the cursor to the end of the second response line of the system and
press the ENTER key. The system will return the following message:
The number that is informed in this message is the refund note number that contains the
refunding of the documents previously loaded.
This refund note can be retrieved, as was previously explained, with the transaction:
ET/[refund note number]

9.7. 10.2.4 Deleting of the documents included in a refund

note
It can be deleted documents previously included in a refund note. This function can be
performed prior to closing or issuance of refund note.
The transaction to perform the deletion of all documents included is the following:
WRFN/DEL*
WRFN Transaction
/ Slash
DEL Transaction that indicates deletion (delete)
* Asterisk. Represents the total of the documents
When performing this transaction the system response is the following:
OK
In this way are deleted all the documents contained so far, in the refund note.
The transaction to delete a single document of the refund note is the following:
WRFN/DEL1
WRFN Transaction
/ Slash
1 Item number to delete from the refund note
When performing this transaction the system will respond the following:
OK
If after performing this transaction, again consult the refund, with the WRFN/* transaction, the
document that was placed in the deleted line will not be view.
Note
The single deletion must be done by one document at a time.
9.8. 10.2.5 Ignore a refund note

During the loading of documents to a refund note, it can be ignored and no action will take
place over the e-tickets and/or MPDs loaded at the moment.
The transaction to ignore a refund note is the following:
WRFN/I
By performing this transaction, the system responds the following information:
OK
Once ignored a refund note, if try to perform again the transaction to redisplay, WRFN/*; the
system will respond with the following message:

NO DATA
Note
The transaction, to ignore a refund note, can also be executed as follows:
WRFN/IG
WRFN/IGD
9.9. 10.2.6 Voiding of a refund note

The refund notes, once closed, can be voided with the following transaction:
W*V9998000000112
W Transaction
V Transaction to indicate voiding (void)
9998000000112 Number of the refund note to void
By performing this transaction, the system responds with the following script:

W*V9998000000112/Y
In order to confirm the voiding of a refund note, must execute the same transaction adding /Y
at the end of the transaction line, or move the cursor to the end of the second line of the
system response and press the ENTER key. The system will respond as follows:
OK
By voiding a refund note, the documents contained in it, will change their status to OPEN
FOR USE.
If we consult the history of a document that was contained in a refund note which has been
voided, will display the status change, as well as the refund note that contained it in the
refund.
If a voided refund note is consulted, it can be visualized the documents that were contained in
it before the voiding procedure, the original amount for which had been generated and their
current status CANX / VOID:
RFND-9998000000112 5 * VOID * TRANSAC: CANX

POI-BUE DOI-13JUN07 IOI-AR-00002-0
ED-
1.MORENO/CARLOS
FOID: DNI 4444

9992200008171 1 200.00 40.46 0.00 0.00 240.46
9992200008172 1 515.00 79.33 0.00 0.00 594.33
9995090000306 1 10.00 0.00 0.00 0.00 10.00
9995090000307 1 15.00 0.00 0.00 0.00 15.00
EQUIV ARS 740.00 PENALTY :

TAX ARS 81.59DL 24.10QN 14.10XT
TOTAL *** VOID ***
FP 859.79 CASH
#NOTE:

Warning Message:
If when making a refund, you make any changes to any of the documents contained in the
refund note, the system will display the following message:
SIMULTANEOUS CHANGES ON COUPONS - CHECK DOCUMENTS
The message advises that simultaneous changes were detected in some of the coupons of
the documents that are trying to be refunded.
To continue, we must check the status of each of the documents included in the refund note,
and remove it from the refunded note, in order to continue with the process.
9.10. Remote refund of a document

In the same way that you can perform the refund of a document or the note for the refund of
several, the remote refund can be executed in order to be generated in report of sales of the
user who is executing it in the selected office.
The transaction to perform a single document remote refund is:
W*R9992200008094/E1-ARS200/33.37DL/9.86QN*FCA*RBUE00XX2
It is used same transaction by adding *R at the end, and the proper office (ex. BUE00XX2)
The same applies for the refund of several documents. The refund note is made as explained
in the previous steps, and at the time of issue the same indicator is added. For Example:
W*R*FCA*RBUE00XX2
As a result, in both cases the system generates the refund note and the same is reflected in
the sales report of the office involved in the transaction (For Example: BUE00XX2)
9.11. Search of a refund note by last name

There is a way to retrieve a refund note by passenger's last name.
The transaction is:

*R/LASTNAME
This transaction will display a list of all the documents that were found with the indicated last
name, with an access link to it.
The search can also be filtered by placing the name and the issue dates. Examples:
*R/LASTNAME/NAME
*R/LASTNAME/NAME/20SEP06 From the asked date in advance
*R/LASTNAME/20SEP06 From the asked date in advance (only last name)
*R/LASTNAME/NAME/20SEP06-30SEP06 Between the asked dates (supports a 31 days
range)

10. E-tickets status modifications

The statuses of the coupons are modified by normal transactions as an exchange, a voiding,
etc. But there is also a way to manually pass from one status to another. The modifications
allowed in the system are:
10.1. Open for use to Flown

To execute this transaction DUTY 5 is needed in agent signature. The transaction to perform
it directly is:
W*F Ticket number/E1
W*F Transaction
Ticket Number e-ticket number
/ Flash (mandatory)
E Coupons identifier
1 Coupon number to modify
The same can also be done, previously retrieved the ticket in question. The procedure is as
follows:
The ticket is retrieved with this transaction:
ET/Ticket number
The transaction is executed:

W*F/E1
Several coupons can be modified at a time. The procedure is the same adding the coupon
numbers one behind the other.
Example:
W*F/E123
This is the acceptance response:

OK. STATUS CHANGE TO FLIGHT
As an option you can add a remark to the transaction. The procedure in any of the two
transactions is by adding /free text after the flight coupons.
Example:
W*F/E1/MANUAL CHECK IN
This remark can be visualized by retrieving the ticket history.

10.2. Open for use to Exchange

In order to execute this entry DUTY 4 is needed to be set in the signature. The transaction to
perform it directly is:
W*E Ticket number/E1/ (free text)
W*E Transaction
Nro.de ticket E-ticket number
/ Slash
/ Slash
NOTA Free text
follows:
The ticket is retrieved with the following transaction:
ET/Ticket number
The following transaction is executed:
W*E/E23/NOTE
Important:
It is mandatory to modify all the coupons that are Open for use.
The acceptance answer is:

OK. STATUS CHANGE TO EXCHANGE
10.3. Placing a NO SHOW mark in an Open for use ticket

In order to execute this transaction DUTY 4 is needed to be set in agent sign. The transaction
to perform it directly is:
W*NS ticket number/E1/NOTE (free text)
W*NS Transaction
/ Slash (mandatory)
/ Slash (mandatory)
NOTE Free text (optional)
follows:
The ticket is retrieved with the transaction:
ET/Ticket number

W*NS/E23/NOTE

OK. NO SHOW
10.4. Deleting a NO SHOW mark from an open for use ticket

In order to execute this transaction DUTY 4 and keyword NSHCLR is required to be set in the
sign. The transaction to perform it directly is:
W*NSC ticket number/E1/NOTE (free text)
W*NSC Transaction
/ Slash (mandatory)
/ Slash (mandatory)
NOTE Free text (optional)
follows:
The ticket is retrieved with the transaction:
ET/Ticket number
W*NSC/E1/NOTE

OK. NO SHOW CLEAR

11. Revalidate e-tickets

The electronic tickets can be revalidated if they have suffered any of the following
modifications:
1) Flight number.
2) Flight date.
3) Time of departure or arrival.
The following data cannot be modified in order to perform a revalidation:
1) Passenger name
2) Booking class.
3) Route.
The role of revalidation is to update the issued ticket data with the new itinerary information, in
this way would avoid making an exchange. It is important to note that there should be no
difference in fare between the itinerary issued and the new itinerary.
11.1. Revalidation of a flight coupon

To proceed to perform the revalidation must retrieve the PNR, update the segments status in
case of having segments UN and/or TK and record the changes. Once this operation is
performed, must execute the following transaction:
ETRV/L2/S1/E1
Description:
ETRV Transaction
/ Slash
L Ticket line number indicator within the PNR
2 Ticket item number indicator within the PNR
/ Slash
S Segment to revalidate indicator within the PNR
1 Segment number within the PNR
/ Slash
E Flight coupon to revalidate indicator within the PNR
1 Flight coupon number
Once executed the transaction, the function updates the data within the e-ticket and save.
The execution transaction is saved in the PNR history.
In the e-ticket history, the revalidated coupon will appear with the status O (Open for use) and
the former coupon with a dash (-), that indicate was cancelled by a revalidation.
Example:

1 AEPCOR XX4500 Y 23NOV O BUE00XX000 AEPXX-AA 2108 2NOV05

11.2. Revalidation of several flight coupons

It is possible to revalidate multiple segments at once. The transaction format is similar adding
the correspondent segments and coupons.
For example, to revalidate an e-ticket with segments 1 and 2 and the coupons 1 and 2, the
transaction would be the following:
ETRV/L2/S1,2/E1,2
11.3. Revalidations with remarks

It is possible to revalidate an e-ticket adding remarks. The transaction is:
ETRV/L2/S1/E1/FREE TEXT
Example:
ETRV/L2/S1/E1/DUE FLIGHT CANCELLATION
In the e-ticket history will be reflected as follows:

1 AEPCOR XX4500 Y 23NOV O BUE00XX000 AEPXX-AA 2108 2NOV05 DUE FLIGHT CANCELLATION
11.4. Massive revalidation

In order to perform a massive revalidation is necessary to have duty codes 5, 7 or 8. In case
of the duty code 5 is also necessary to have the keyword CHKLV2, allowing to work in this
case on flights that are within 2 days later or earlier.
This functionality allows a massive revalidation of all e-tickets that are in OPEN FOR USE
status of a particular flight and modify them for another flight which must be specified in the
transaction, because the system does not check the existence of the data.
The system obeys to the order that was executed by the transaction considering always that
the route that corresponds to the modified coupon is the same as the flight to which you are
specifying. Otherwise return an error.
The transaction to execute a massive revalidation of all the e-tickets of a flight is:
EMOVE4420/22DECAEPBRC#4444/22DEC1800
Description
EMOVE Transaction
4420 Flight where the coupons are placed
/ Slash
22DEC Date
AEPBRC Origin and destination of the coupons
# Pound (fix and mandatory used to split)

4444 Flight on which the coupon will be record

/ Slash
22DEC Flight date
1800 Departure time
Response:
EMOVE4420/22DECAEPBRC#4444/22DEC
CONFIRM THE OPERATION
23 TICKETS
EMOVE4420/22DECAEPBRC#4444/22DEC/Y
Once executed the transaction, requires a double confirmation, and so must execute the
same transaction with /Y at the end of the transaction line. The system response is OK.
11.4.1. E-ticket history

The e-ticket history in the massive revalidation is show as follows:
11.5. Massive revalidation selecting e-tickets

Massive revalidation can also be made by selecting desired e-tickets.
The first step is t display the list of tickets that correspond to a flight with the following
transaction:
EMOVE4444/22DECAEPBRC
EMOVE Transaction
4444 flight
/ Slash
22DEC Date
AEPBRC Origin and destination
Example:
EMOVE4444/22DECAEPBRC
TICKETS TO PROCEES IN FLT 4444/22DECAEPBRC
ITEM RBD TICKET CPN

1. K 9992200015500 1
2. K 9992200015501 1
3. S 9992200015502 1
4. Y 9992200011945 1
5. Y 9992200012217 1
6. Y 9992200013042 1
7. Y 9992200013043 1
8. Y 9992200013044 1
9. Y 9992200013045 1
10. Y 9992200013046 1
11. Y 9992200013047 1
12. Y 9992200013048 1
13. Y 9992200013049 1
14. Y 9992200013050 1
15. Y 9992200013051 1
16. Y 9992200013052 1
17. Y 9992200013112 1
18. Y 9992200015373 1
19. Y 9992200015498 1
20. Y 9992200015499 1
21. Y 9993300000291 1
22. Y 9993300000292 1
23. Y 9993300000295 1
The system displays the list of e-tickets that are OPEN FOR USE on that flight.
The second step is to execute the transaction by selecting desired e-tickets. For Example:
EMOVE.1,4,5-8,14,23#4420/22DEC
EMOVE Transaction
. point (mandatory)
1,4,5-8,14,23 Selected items
# Pound (fix and mandatory used to split)
4420 Flight number to which will revalidate
/ Slash
22DEC Flight date to which will revalidate
Response:
CONFIRM THE OPERATION

8 TICKETS
EMOVE.1,4,5-8,14,23#4420/22DEC/Y
Show the actions that will take the system and ask for the transaction reconfirmation
executing it again with /Y at the end of the transaction line.

12. Move e-tickets from a purged PNR

This transaction allows the move an e-ticket that originally belonged to a purged PNR, to a
new PNR.
This transaction will add the PNR the corresponding ticketing fields, canceling the ticket
expiration date or the manual ticket field. Furthermore, in the e-ticket history will be observed
the record locator change.
Considerations:
 The PNR retrieved in the working area must be confirmed, priced and with the pricing
recorded.
 The e-ticket to be move must be retrieved in the working area.
 The e-ticket must have at least, one Open For Use coupon.
 The e-ticket last name/name must match with the PNR passenger last name/name to
which will be associated (depending of the configuration made by the airline) .
 Also the passenger type must match.
 The record locator to which originally belongs the e-ticket must be purged.
Once the e-ticket is moved to the new PNR, you can proceed to make the revalidation or the
necessary modifications. Although it is not necessary to move an e-ticket to perform an
exchange or a refund, it also can be done.
The transaction is:
ETMV/P1
Description:
ETMV Transaction
/ Slash
P Passenger to which the e-ticket will be associate indicator
1 Passenger number within the new PNR
The positive answer is OK. This answer will modify the TKT/TIME LIMIT field with the e-ticket
data.
Example:
TKT/TIME LIMIT
TL AEP 1800/20NOV-SU
TKT field before move the e-ticket
TKT/TIME LIMIT
1 TKT/OK * 02NOV05/AEPXX-AA
2 TKT/ET 9992200000881 * 02NOV05/AEPXX-AA - HULY/F.
TKT field after moving the e-ticket
The date placed on that field is the day they make the move.
In the history will be show this way:

ACTION FROM TO SIGN TIME/DATE
»MOVE OBSQEZ NWICQL AEPXX-AA 2041 2NOV05
The same way, the system could show the following warnings:

* AT LEAST ONE TICKET IS ISSUED

When the passenger to whom you want to associate the ticket already has an e-ticket issued.
* SEGMENTS DISCREPANCIES
When the ticket that you want to associate, has different segments than the itinerary of the
PNR.
* PRICE DISCREPANCIES
When the e-ticket fare and taxes amounts differs from the fare of the passenger type priced in
the PNR (not the booking classes).
Those are general warnings. To ignore this warnings and proceed to move the e-ticket, must
execute the transaction with /Y at the end of the transaction line.(same as in ticketing).

13. Disassociated ticket

If you change the name of a passenger who already has an e-ticket issued, the system
disassociates the passenger’s ticket.
By changing some of the items of the field name (last name, name, or FOID) the system will
response the following message informing that the quote has been deleted ( if the PNR was
priced) and that the ticket has been disassociated:
OK ** PAX WITH TICKET // UNASSOCIATED TICKET **

** WARNING: TICKET REMOVED FROM PNR **
In the PNR history will be shown that the ticket is disassociated as follows:
XN 1CASARES/CLARA ** PAX WITH TICKET // UNASSOCIATED TICKET ** »DNI 43423
Note that once a ticket has been disassociated from a passenger’s name, the passenger
remains like without having an issued ticket with the following considerations:
1. If the passenger of the PNR is divided, the ticket that already had, will remain in the
original PNR and will not be moved to the new PNR.
2. The passenger ticket is not associated, so if the LD list is consulted, the indictor ET
will not appear by the passenger’s name.
3. To re-associate a ticket to a passenger must make an exchange.

14. Change of class of a ticket (Upgrade/Downgrade)

This functionality allows you to change the class of a ticket without the need to make an
exchange.
To perform this class update for a ticket must have keyword TKTUPD (ticket update) in agent
sign and one of the following duty codes: 4, 5, 7 and/or 8.
An e-ticket upgrade or downgrade could be done from:
 A ticket displayed in the screen.

 A PNR displayed in the screen.
 An e-ticket (not previously displayed in the screen)
The transaction to change a ticket class, having the ticket already displayed in the screen, is:
ETUP/E1/C/UPGRADE OK
Description:
ETUP Transaction (ET: e-ticket UP: update)

/ Slash
E1 Coupon indicator followed by the coupon number to update (It can only be
updated one coupon at a time)
/ Slash
C Class to which the ticket coupon is switch (It can be only change only to a
different cabin class from the actual cabin)
/ Slash
UPGRADE OK Free mandatory text (It can be entered up to a maximum of 50 letters)
The transaction to change a ticket class, having the PNR displayed in the screen is:
ETUP/L2/E1/C/UPGRADE OK
Description:
ETUP Transaction (ET: e-ticket UP: update)

/ Slash
L2 Line indicator where the ticket is located, followed by the line number.
/ Slash
E1 Coupon indicator followed by the coupon number to update (It can only be
updated one coupon at a time)
/ Slash
C Class to which the ticket coupon is switch (It can only be changed to a
different cabin class from the actual cabin)
/ Slash
UPGRADE OK Free mandatory text (It can be entered up to a maximum of 50 letters)
The transaction to change a ticket class, without having the ticket displayed in the screen, and
either having a PNR displayed in the screen, is:
ETUP/9992200015739/E1/C/UPGRADE OK

Same validations as above will apply, but considering that instead of indicating the line
number should be directly written the ticket number
Ticket history
The class changes, previously mentioned, will be registered in the ticket history, as follows:
In the OBSERVATION column, the text "UPDATE CLASS" will be visualized followed by the
text that has been entered in the transaction, upon change.
Queue
Each time a change of class be performed, to an issued ticket, the system automatically send
a warning message to the queue 184 of the city HDQ (see QUEUES user guide).

15. E-MPD documents for excess baggage

The E-MPD is a Multi Purpose electronic Document. This type of document allows the issue
of receipts for extra charges collected by the airlines.
The system will issue an E-MPD (electronic multiple purpose document) for the excess
baggage payments, with the transaction IATA MP10.
Considerations
 The issuing must be done over a retrieved PNR in the current working area and
without modifications.
 The documents issued are recorded in the sales report (WA*).
 In the PNR , when the first EMPD is issued, the following message will appear:
 *** MULTIPLE PURPOSE DOCUMENT DATA EXISTS *** SEE EMPD
 The issuance of the document closes an old sales report, in case it stills open and
opens the sales report for the date of issue.
15.1. E-MPD issuing

To perform the issue with a displayed PNR, the transaction would be:
WX*S1*N1*XB10K1.50ARS*RM/TEST*ED/ENDORSMENT*VT/678901*FCA*TX10DL/5QN
Description:
WX* Transaction
S1 Segments to issue indicator (is mandatory if the PNR has more than 1
segment) (same options than the tickets issue)
* Asterisk (item splitter)
N1 Passenger to issue indicator (is mandatory if the PNR has more than 1
segment) (same options than the tickets issue)
XB Excess baggage to charge (MANDATORY)
10K Quantity and weight unit of the excess baggage
1.50ARS Currency and unit amount of the excess (ARS 1.50 per kilo in the example)
ED/ Endorsements (optional), from 1 to 50 characters
RM/ Remark indicator (optional), from 1 to 100 characters
VT/678901 VAT (optional, same format than the e-tickets issue)
FCA Form of Payment Indicator (same options than the tickets)
TX10DL/5QN Taxes indicator (optional)
In this case an excess baggage will be issued to a passenger with 1 coupon, for ARS 15.-,
with form of payment CASH.
Forms of payment:
The forms of payment accepted in the system may be combined in the same way than the e-
ticket issue is performed.
Example:

WX*S1*N1*XB10K1.50ARS*ED/EXCESS BAGGAGE*RM/BAG TOO BIG*FCA

OK. XSB Nr. 9995090000056
Once issued, the PNR will show following message:

1.1AGUERO/RAMON »DNI12000989
2.1CAMESANA/CARLOS »DNI22000145
1 XX4420Y 22NOV WE AEPBRC HK2 12:05 15:15
2 XX4421Y 23DEC SA BRCAEP HK2 18:00 20:30
TKT/TIME LIMIT
1 TKT/OK * 22SEP06/AEPXX-MM
2 TKT/ET 9992200006205 * 22SEP06/AEPXX-MM - AGUERO/R.
3 TKT/ET 9992200006206 * 22SEP06/AEPXX-MM - CAMESANA/C.
*** MULTIPLE PURPOSE DOCUMENT DATA EXISTS *** SEE EMPD
CONTACTS
1-BUE +99 (99) 999-9999 LINEAS AEREAS XX
RECEIVED FROM - PAX
AEP.HLP/DESK102 1417/22SEP06 *SRGNOQ -H
In order to view the document, the transaction EMPD must be executed:
* MULTIPLE PURPOSE DOCUMENT * SRGNOQ

1- XSB /9995090000056 * 22SEP06/AEPXX-MM - AGUERO/R.
At the same time, it will be automatically loaded in the daily sales report as well as the e-
tickets issuance, under the concept E-MPD ISSUED.
Example:
SEQ.No. TICKET FARE TAX COMM NET FP TRANS RELOC PAX NAME OBSERVATION
--------------------------------------------------------------------------------------
--
E-MPD ISSUED (MPnn)
0003 9995090000056 15.00 0.00 0.00 15.00 CA MP10 SRGNOQ AGUERO/RAMON
Like the e-tickets all issued documents are recorded as an MP10 transaction.
15.2. MPD document visualization

The transaction to visualize the document is:
EMPD/E-MPD number
EMPD/9995090000056
MPD-9995090000056 0 * ISSUE * TRANSAC: MP10

C1/SRGNOQ
OD-AEPBRC POI-BUE DOI-22SEP06 IOI-AR-00002-0
ED-EXCESO VOLUMINOSO
1.AGUERO/RAMON ADT
FOID: DNI12000989
REASON FOR ISSUANCE: 10 - EXCESS BAGGAGE TICKET COUPON STATUS
1 o AEP XX 4420 22NOV 1205 OPEN FOR USE
BRC
TOTAL ARS 15.00
AMOUNT IN LETTERS: QUINCE CON 00/100
REMARKS:

10 KG AT ARS 1.50 PER KG

BOLSO DE TRANSPORTE
FP 15.00 CASH
Having the PNR displayed it is also possible to execute, EMPD/E-MPD item number
Other existing transactions are:
EMPDH* Visualize the history of the active document present

in the working area
EMPDH/document number Visualize the document history by number
15.3. E-MPD printing as passengers receipt

The transaction to print the E-MPD receipt is:
EMPDR/MPD number
EMPDR/line number within the MPD field of the PNR
This transaction displays the preview and then it is possible to print the data by clicking on the
icon of the printer.
You can also print the voucher of the ticket displayed on the screen:
EMPDR/*
EMPDR/ Fixed transaction

* Asterisk. Identifies the EMPD previously displayed on screen
15.4. Change of status of the EMPD to FLOWN

Once the passenger is checked and the flight is closed, the E-MPD coupon can be passed to
FLOWN with the following transaction:
W*F(EMPD number)/E1/Remark (optional)
15.5. Sending E-MPD by e-mail

In order to send the EMPD by e-mail you must enter the following transaction:
EMPDR/1-mail@mail.com

1 Number of item of the EMPD within the PNR.
- Dash
mail@mail.com E-mail address
You can also submit the EMPD directly indicating the document number as follows:
EMPDR/9995090001339-mail@mail.com


9995090001339 EMPD number
- Dash
With this option it is not needed to have the PNR previously displayed on screen.
If you have displayed the EMPD on screen, you can use the following option:
EMPDR/*-mail@mail.com

* Asterisk. Identifies the EMPD previously displayed on screen
- Dash
15.6. E-MPD History

In order to visualize the EMPD history, following transaction needs to be used:
EMPDH/{EMPD number}
Example: EMPDH/9995090001339
For the history of an EMPD previously displayed on screen, you must enter following
transaction:
EMPDH*
In order to check the history of an EMPD within a PNR through its item number in the
reservation must use the following transaction:
EMPDH/1
The number 1 represents the item number of EMPD in the reserve.

16. E-MPD documents for penalty and additional

services.
The system will allow to issue the penalties charges or additional services EMPD (electronic
multiple purpose document), with the IATA MP50 transaction.
Considerations:
 This document can be issued within a PNR or outside it.

 The documents issued will enter to the sales report (WA*).
 When the issue is made within the PNR, will appear this script in it:
 The issue of the document closes an old sales report in case you have one and open
the sales report for the date of issue.
16.1. E-MPD issue with PNR

To perform an E-MPD issue with a displayed PNR, the transaction is:
WZ*N1*MC10ARS/NSHW*TX10DL/15QN*FCA*ED/TEST*VT/678901*ET/9992200006304/E
12*RM/FREE TEXT
Description:
WZ* Transaction
N1 Passenger 1 indicator (same than in the e-tickets issue)
MC Document type indicator (MCO)
10ARS Amount and currency type to pay
/ Slash (only if the motive exists)
NSHW Motive indicator (optional, see Motives)
TX Fees and/or taxes indicator (optional)
10DL Amount and tax/fee code
/ Slash (divide the fees or taxes)
15QN Amount and tax/fee code
FCA Form of payment (see Forms of payment)
ED/free text Endorsements (optional, same format than the e-tickets
issue)
VT/678901 VAT (optional, same format than the e-tickets issue)
ET/9992200006304/E12 References the e-ticket for which this MCO is issue (optional,
see e-ticket option)
RM/free text Remark RM/ is the indicator, after it free text (optional)
Motives:

There are reasons that can be indicated in the issuance of an MCO, which identify it. The
motives are fixed:
NSHW For No Show

EXCH For an Exchange
RFND For a Refund
ETRV For a revalidation
OXYG For oxygen requirement
VGML Vegetarian meal
STCR Stretcher passenger
UMNR Unaccompanied minor
It is important to remind that these motives are optional. There is no obligation to use them.
Forms of payment
You can combine the forms of payment accepted into the system, the same way as it does in
while issuing e-tickets.
E-ticket option
In case of referencing a ticket to the MCO issue, the rigid format is ET/ (electronic ticket
indicator) followed by the ticket number and at the end the ticket coupons are placed with the
format /E12 (12 are the coupons 1 and 2).
16.2. E-MPD issue without PNR

To perform the issue without a PNR, you must indicate the name of the person to whom the
document will be issued, therefore, the basic transaction is:
WZ*NDOE/JHON.DNI220000011*MC10ARS*FCA
Description:
WZ* Transaction
N Name indicator
DOE/JHON Last name and first name of the person
.DNI22000… Persons ID (optional)
FCA Form of payment (same as the previous example)
Note:
The rest of the indicators (Motives, Taxes, Endorsements, VAT, Tickets, and Remarks) that
are shown in the example of the issue with PNR displayed can be also used in the same way
in this option (without PNR).
16.3. View of an E-MPD

The transaction to view the E-MPD document is:

EMPD/EMPD number
Having the PNR displayed also can be execute, EMPD/E-MPD item number
Other transactions are available:
EMPDH* Visualize the active document history in the current working

area
EMPDH/document number Visualize the document history by number
16.4. E-MPD printing as passenger receipt

The transaction to print is:
EMPDR/MPD number
EMPDR/line number within the MPD field of the PNR
This transaction shows the preview and then prints transactions by clicking over the icon of
the printer.
17. Search of an E-MPD by last name

There is a way to retrieve an e*MPD document by passenger last name.
The transaction is:
*M/LASTNAME
This transaction will display a list of all the documents found with the indicated last name, with
an access link to it.
The search can be also filtered placing the name and the date of issue.
Examples:
*M/LASTNAME/NAME
*M/LASTNAME/NAME/20SEP06 From the date requested in advance
*M/LASTNAME/20SEP06 From the date requested in advance (only last
name)
*M/LASTNAME/NAME/20SEP06-30SEP06 Between requested dates (31 days range)

18. E-ticket exchange for credit e-MPD

A simple or multiple exchanges of e-tickets can be generated for credit e-MPD MP61.
In this case the credit document must be generated loading the e-tickets data to finally issue
the same.
In a credit document can be included from one to ten e-tickets.
The MP61EX keyword is required.
18.1. E-tickets load for the credit generation

To include an e-ticket the following transaction must be entered:
WEXC/ADD [ticket number]/E+/Remarks (optional)-[currency & amount]/[taxes]
Example:
WEXC/ADD9992200008171/E+/AUTH SUP-ARS200/25.79DL/7.62QN/6.05XR
Description:
WEXC/ Transaction that generates the refund note
ADD Fix transaction to add documents to the refund note
9992200008171 Document number to refund
/ Slash
+ Indicates that all the OPEN FOR USE coupons will be exchanged
/ Slash (is place in case of using a remark)
AUTH SUP Remark. This field is optional
- Middle dash that precedes the currency in which the document will
be refund
ARS200 Currency and amount to refund
/ Slash
25.79DL Tax to refund. Up to 3 taxes to refund can be entered by document.
This procedure must be repeated many times as documents wish to include in the credit e-
MPD.
When adding each new document, the system will give following response:
DOCUMENT ADD FOR EXCHANGED OK.
To consult the documents that are being added, the transaction is:
WEXC/*
After performing this transaction, the system will display the information of the documents
contained at the moment:
DOCUMENTS TO EXCHANGE * IN ARS *

It. DOCUMENT NUMBER CPN FARE TAX PEN/OTHS COMM.
NET
1. 9992200013191 1 300.00 0.00 0.00 0.00
300.00
2. 9992200013199 1 142.00 20.39 0.00 0.00
162.39
3. 9992200013200 12 250.00 29.39 0.00 0.00
279.39

In the first line the currency in which the document will be exchanged is shown in * ARS *
The documents are numbered as they are incorporated into the refund note. The numbering
can be seen in It. (item) column.
DOCUMENT NUMBER Document number to refund

CPN Document coupon number to refund
FARE Fare to refund
TAX Taxes amount to refund
PEN/OTHS Penalties and other charges amounts (penalties / others)
COMM. Commission amount to refund
NET Net amount to refund for each document (fare + tax +
pen/others + comm.)
18.2. E-MPD issue

Once all the documents to be exchange are loaded, must proceed to issue the E-MPD, with
the following transaction:
WY*FEX*N(last name)/(Name)
WY Transaction
F Fix transaction that precedes the form of payment
EX Form of payment exchange
N Passenger name indicator
The last name and first name indication is optional. In case the issue takes place within a
PNR the system will automatically take the passenger’s name. In case the PNR has 2 or
more passengers, must indicate who will be assigned, by placing the mentioned indicator or
the passenger’s number that occupies within the PNR. Example: WY*FEX*N2
The system will return the following script:

OK. MPD Nr. 9995090000769
A new document is issued with the MP61 transaction. When consulting it, contains the
following details:
EMPD/9995090000769
MPD-9995090000769 6 * ISSUE * TRANSAC: MP61 C1/QFAQZE

OD- POI-AEP DOI-20JUN08 IOI-AR-00001-0
ED-NON END/NON REF
1.ALMEYRA/DIEGO ADT
FOID: CI3892382
REASON FOR ISSUANCE: 61 - UNSPECIFIED MISCELLANEOUS CHARGES ORDER
FARE ARS 692.00 BSR 1.000000

EQUIV ARS 692.00
TAX ARS 25.20DL 9.48QN 3.00TQ 12.10XR
TOTAL NO ADC
* OPEN FOR USE *
REMARKS:
FP 0.00 EXCHANGE 9992200013191/1/OR9992200013191/19JUN08AEP/IAR-00001-0

0.00 EXCHANGE 9992200013199/1

0.00 EXCHANGE 9992200013200/12
18.3. Deleting documents in the load

During the load, documents previously included can be deleted. This function can only be
done prior to the document issuance.
The transaction to perform the deletion of all the documents included is the following:
WEXC/DEL*
WEXC Transaction
/ Slash
* Asterisk. Represents the total of documents (ALL)
Once this transaction is performed the system responds the following information:
OK
The transaction to delete a single document is the following:
WEXC/DEL1
WEXC Transaction
/ Slash
1 Document to delete item number
OK
If after performing this transaction, it is referred back to it, with the transaction WEXC/*, the
document that was placed in the deleted line will no longer be visualized.
Note
The deletion of single documents must be done one at a time.
18.4. Ignoring a load

During the documents loading, the loading process could be ignored and no action will be
taken over the e-tickets so far loaded.
The transaction to ignore it is the following:
WEXC/I
OK
Once ignored, if the transaction to redisplay it be executed again, WEXC/*; the system will
respond the following:
NO DATA

19. Direct issuance of e-MPD of credit

The system will allow to issue EMPD (electronic multiple purpose document) for the collection
of penalties or additional services charges, with the IATA MP61 transaction.
Considerations:
 This document can be issued within a PNR or outside it.

 The documents issued will enter to the sales report (WA*).
 When the issue is made within the PNR, will appear this script in it:
 The issue of the document closes an old sales report in case you have one and open
the sales report for the date of issue.
 Keyword MP61IS is required
19.1. E-MPD issue with PNR

To perform the E-MPD issue with a displayed PNR, the transaction is:
WY*N1*MC100ARS*TX10DL/15QN*FCA*ED/TEST*VT/678901*ET/9992200006304/E12*RM
/FREE TEXT
Description:
WY* Transaction
N1 Passenger 1 indicator (same as the e-tickets issue)
* Asterisk (items splitter)
TX Fees and/or taxes indicators (optional)
10DL Amount and fee or tax code
/ Slash (divides the fees or taxes)
15QN Amount and fee or tax code
FCA Form of payment (see Forms of payment)
ED/free text Endorsement (optional, same format as the de e-tickets
issue)
VT/678901 VAT (optional, same format as the e-tickets issue)
ET/9992200006304/E12 References the e-ticket for which this MCO is issue (optional,
see e-ticket option)
RM/FREE TEXT Remark RM/ is indicator, then free text (optional)
This transaction execution gives a Credit E-MPD document with status OPEN FOR USE.
Example:
WY*N1*MC150ARS*FCA
OK. MPD Nr. 9995090000903

EMPD/1
MPD-9995090000903 0 * ISSUE * TRANSAC: MP61

C1/MAEWLB
OD- POI-AEP DOI-30JUN08 IOI-AR-00001-0
ED-NON END/NON REF
1.PEPE/A ADT
FOID:
REASON FOR ISSUANCE: 61 - UNSPECIFIED MISCELLANEOUS CHARGES ORDER
FARE ARS 150.00 BSR 1.000000

EQUIV ARS 150.00
TAX ARS
TOTAL ARS 150.00
* OPEN FOR USE *
REMARKS:
FP 150.00 CASH
Forms of payment
You can combine the forms of payment accepted into the system, the same way as it does in
while issuing e-tickets.
E-ticket option
In case of referencing a ticket to the MCO issue, the rigid format is ET/ (electronic ticket
indicator) followed by the ticket number and at the end the ticket coupons are placed with the
format /E12 (12 are the coupons 1 and 2).
19.2. E-MPD issue without PNR

To perform the issue without a PNR, you must indicate the name of the person to whom the
document will be issued, therefore, the basic transaction is:
WY*NDOE/JHON.DNI220000011*MC1000ARS*FCA
Description:
WY* Transaction
N Name indicator
PEREZ/JUAN Persons last name and first name
.DNI22000… Persons personal ID (optional)
FCA Form of payment (same as the previous example)
Notice:
The rest of the indicators (Motives, Taxes, Endorsements, VAT, Tickets, and Remarks) that
are shown in the example of the issue with PNR displayed can be also used in the same way
in this option (without PNR).

20. Refunds (Refund) and voiding (Void) of E-MPD

documents
20.1. Voiding a document (VOID)
The e-MPD can be voided as well as any other document and under the same conditions,
with the following transaction:
W*V9995090000169
W Transaction
V Mandatory transaction to indicate voiding (void)
9995090000169 Credit E-MPD number to void
When performing this transaction, the system responds with the following script:
W*V9995090000169/Y
To confirm the voiding, must execute the same transaction by adding /Y at the end of the
transaction line, or move the cursor to end of the second line of the system response and
press the ENTER key. The system will bring back the following script:
OK
In the exchange cases of the credit E-MPDs, when it is voided, the e-tickets that were
contained in it, return to OPEN FOR USE status
Warning message:
If at the moment of performing an exchange, any modification was made on one of the
documents contained in it, the system will display the following message:
SIMULTANEOUS CHANGES ON COUPONS - CHECK DOCUMENTS
The message advises that simultaneous changes were detected in some of the documents
that are you are trying to exchange.
To continue, we must check the status of each one of the documents, and then take them out
to continue with the process.
20.2. E-MPD refund (Refund)

In order to perform an E-MPD refund, must take into account the following considerations:
a) The Personal Sales Report must be open

b) The document must be valid
c) The refund amount must not exceed the MCO issuing amount.
The input transaction to perform a refund of a single document is the same as in e-ticket:
W*R9995090001015/E1/Free text-ARS100.00/12.50XR*FCA
Description

W* Transaction
R Refund indicator
9995090001015 E-MPD number
/ Splitter
E Document type indicator
1 Coupon number to refund
/ Splitter
FREE TEXT Observation for the transaction (optional, max. 50 characters)
- Splitter to indicate amounts loading
ARS Currency on which the refund is made
100.00 MCO refund amount
/ Splitter
12.50XR Taxes that are going to be refund, the necessary quantity of
taxes can be enter. If it is wish to use the XT indicator can
only load up to 3 taxes with the XT included (optional)
* Splitter to indicate the form of payment
F Form of payment
CA Form of payment (with the same formats and criteria than for
the ticketing).
The same as in an e-ticket refund (see 10.1), the system shows all data with the amounts to
refund and to confirm the MCO refund must execute the same transaction by adding /Y at the
end of the transaction line.
The system will respond with the following script:
The REFUND NUMBER is the correspondent number of the refund note.
The remark that is entered in the transaction will appear in the Sales Report with the title
EMPD REFUND (RFND) and in the subsequent queries made to the transaction.

E-Ticketing User Guide: Kiu System Solutions

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E-Ticketing User Guide: Kiu System Solutions

Uploaded by

Copyright:

Available Formats

KIU SYSTEM SOLUTIONS

E-Ticketing User Guide

KIU System Solutions

KIU® November 2011

Versión 2.0 KIU® November 2012 1

5.2. Deleting the masks ........................................................................................................... 37

Versión 2.0 KIU® November 2012 2

16.2. E-MPD issue without PNR .............................................................................................. 76

Versión 2.0 KIU® November 2012 3

1. Personal Sales Report (WA)

Versión 2.0 KIU® November 2012 4

E-TICKET ISSUED (TKTT) Tickets issued and transaction type (TKTT)

GRAND TOTAL Total tickets issued

Versión 2.0 KIU® November 2012 5

1.3.1. Display Options

WA Summary report display

Remarks are added as a free text and support up to 100 characters.

1.4.2. Remove from Report

1.4.3. Add to a specific ticket/item

Versión 2.0 KIU® November 2012 6

1.5. Remote Closure

The transaction to close the Sales Report of a different agent is:

1.6. Display other agents’ Reports

REPORT No AGENT OPEN AT CLOSE AT

The transaction is:

Versión 2.0 KIU® November 2012 7

The system shows data until 45 days backwards.

1.6.1. Consulting the own sales reports

The transaction is the same:

1.6.2. Consulting an specific sales report

Versión 2.0 KIU® November 2012 8

The report number is obtained from the previous report.

1.6.3. Consulting the unified general sales report of an office

1.6.4. Consulting the general sales reports summary of an

The transaction is:

CASH/CHECK 13 2765.00 479.72 0.00 3244.72

The transaction is:

Versión 2.0 KIU® November 2012 9

INVOICE 3 765.00 128.52 0.00 893.52

CASH/CHECK 4 474.56 85.72 0.00 560.28

The transaction in this case is:

WR// Basic summary

1.6.5. Consulting sales reports of a non BSP/ARC travel

Versión 2.0 KIU® November 2012 10

2. If a date range is requested, it cannot exceed 15 days.

1.7. Sales Report Extension

1.7.1. Tour Code

This format can also be applied to reports WA, WL and WQ

1.8. Detailed summary of sales of an office

The transaction is:

DQT{Office ID}* Current date

DQT{Office ID}*{FECHA} Specific date

DQT{Office ID}*{FECHA}-{FECHA} Date range(maximum 15 days)

Versión 2.0 KIU® November 2012 11

Versión 2.0 KIU® November 2012 12

The transaction to visualize the forms of payment is:

For example to see the allowed credit cards:

FOP Transaction (form of payment)

FOP Transaction (form of payment)

Versión 2.0 KIU® November 2012 13

3. Direct issue of electronic ticket

-1ø.ID 2041627 it changes or adds the document type and/or number

3.1. Issue tickets CASH

PARTIAL EXCHANGE - MUST USE MASK '