Personal Sales Report

The Personal Sales Report enables the agent to issue a ticket. The report must be opened every business day and it will show every transaction executed by an agent on that day.  It is related to a sales agent signature and it must be opened and closed with the same signature (except when remote closure is done by an agent with authorized Keyword).

To open new Sales Report, previous report should be closed. The system will admits to open several reports on the same day but will not allowed to use a report that was opened on a different day. Although the report is linked to the agent signature, every time it leaves KIU, the report will remain open, so when the same user re-enters can continue using the sales report that was opened at the time he left.

Sales Report Opening

At the beginning of a business day, the Sales Report must be opened. If the Sales Report is not opened the agent won’t be able to issue tickets. The command to open a report is:

WA*OPEN

System response:

REPORT SALES OPEN

Sales Report Closure

At the end of a business day Sales Report should be closed. The command to close a report is:

WA*CLOSE

System response:

REPORT SALES CLOSE

Sales Report Display

To display an active Personal Sales Report the command is:

WA*

System response:

WA*
   OFFICE - AEP00XX4              SALES REPORT No- 6201             AGENCY No - AR-00001-0  
   AGENT - ROCCA/LUCIANA (150)                                           DATE - 03 OCT 2017 
SEQ.No.       TICKET          FARE          TAX        FEE       COMM          NET   FP    TRANS  RELOC   PAX NAME         OBSERVATION
---------------------------------------------------------------------------------------------------------------------------------------
E-TICKET ISSUED (TKTT)
 00001    9990210005769      1000.00     300.64       0.00       0.00      1300.64   CA    TKTT   YYDLDU  SUAREZ DE CAR..
 00002    9990210005770      1000.00     300.64       0.00       0.00      1300.64   CA    TKTT   NOKWXB  SCHRODER/CAMILA
---------------------------------------------------------------------------------------------------------------------------------------
GRAND TOTAL     ITEMS 
CASH              2          2000.00     601.28       0.00       0.00      2601.28 
CHECK             #
CREDIT CARD       #
DEBIT CARD        #
INVOICE           #
OTHERS            #
                                                              ARS          2601.28      
EXCHANGE          #
VOID              #
=======================================================================================================================================
                     OPENED AT - 1448/03OCT        CLOSED AT - 
                                 # END OF REPORT # 

Description

The system can handle two different currencies. In case the agent issue in two currencies, the report will be divided showing one currency below the other.

Options to display partial Sales Report

WA                            Display the summary of the Sales Report
WA*CA                         Display tickets issued on CASH only
WA*CC                         Display tickets issued by credit card only
WA*CC+                        Displaytickets issued by credit card,  *
WA*IN                         Display ticket issued with form of payment Invoice
WA*XX                         Display tickets issued with other forms of payment
WA*VV                         Display void tickets
WA*CA,IN                      Display using more than one form of payment (divided by coma)
WA*/USD                       Display in one currency only (For example only USD)

Add comments to a Sales Report

You can add a remark to the sales report that will be only informative. Adding a remark is optional. The command is:

WAR FREE TEXT (up to 100 characters)

Example

WAR CHECK DIFFERENCE CASH DUE TO EXCHANGE RATE

If you need to remove a remark the command is:

WAR

You will be able to add a remark to a ticket with the following command:

WAN number of item / FREE TEXT

This command will allow you to add a remark to the Sales Report without affecting the ticket. The number of item is the number that appears on the first column of the Sales Report.

Close a remote Sales Report

In order to close a sales report of another agent within the office the agent must have RPGSPV keyword on his signature. 

The command to close remotely is:

WA*CLOSE/OFFICE/AGENT/DATE

Example:

WA*CLOSE/TUC00DT0/TUCDT-FN/14DEC

System response:

REPORT SALES CLOSE

Office information has 8 digits that match with the terminal information without the last two digits.

Some agents will be able to close sales reports from agent of other office. In order to do this they need to have RPGSPV keyword, duty 4 and HDQ city declare on the EPR (signature).

Display other sales report

 To display the Sales Report of other agents or offices you must have RPGSPV keyword.

The command is:

WL/OFFICE/DATE

System response:

WL/BUE00XX7/10DEC

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

If office and date are not declared, it will take the agent office and the current date as default.

The command is:

WL//

The search will allow one single date or  date range. To request a range date, you must add a dash after the first date as shown in the example.

WL/OFFICE/DATE-DATE

You can also retrieve the list of reports from other offices but in order to do this the user must be authorized and have the city HDQ, duty 4 and keyword RPGSPV in their own signature.

The data that are in brackets are optional. For example, O of Open reports or C of closed reports. In case of not putting said indicators, the default is to show both

Example:

All these commands can be executed in order to export the reports to Excel spreadsheets. To do this you must execute this command followed by -EXCEL

Example:

In response you get a link with the file name to access it directly.

Also, there is an option to retrieve the reports by user, using all the previous examples. In this case user is placed instead of the office.

Example:

WL/BUEXX-MM/20SEP-30SEP

This example will bring all the reports of the agent BUEXX-MM between the 20th and the 30th of September.

Display own sales report

In the same way as in the previous point you can retrieve sales reports from own office without having to have the corresponding keyword.

The commands are:

WL//DATE                          Own office, Specific date
WL//                              Own office, actual date
WL//O/DATE-DATE                   Open reports, range date
WL//DATE-DATE                     All reports, range date

All the commads above can be exported to Excel spreadsheet by adding -EXCEL

Display  a specific Sales Report

To recover a specific report the command is:

WL/DATE#{sales report number} 

The sales report number can be taken from the previous list. As a response the Sales Report requested is displayed.

Display a consolidated Sales Report

This command allows to display the sales report of an office consolidating the sales of all the agents of said office, inserting in order the corresponding e-tickets. 

The command is:

WL/OFFICE#DATE

Display a consolidated Sales Report Summary 

You can request a summary of all the sales reports of an office generated on the day or on a specific day. Keep in mind that when issued in two types of currency, the sales report is divided. To do this, the keyword RPGSPV is required and access to the HDQ city

The command is:

WR/OFFICE/DATE

You can also view the same report detailed by agents.

The command is:

WR/OFFICE/DATE*

WR/BUE00XX7/27DEC*

   OFFICE - BUE00XX7                                DATE - 27 DEC 2004 

============================================================ 

With RPOFFI Keyword you can retrieve the reports for all agents on the same office.

The command in this case is:

WR//                For basic summary
WR//*               For detailed summary

Display a Sales Report for  a Non- BSP Agency

This command allows the airlines to consult the sales reports for non - BSP agencies. 

The command to be entered to verify a particular date is:

WQ/OFFICE/DATE

The command to be entered to consult a date range is:

WQ/OFFICE/DATE-DATE

In both cases, the report can be exported to an Excel file. To perform this action, the -EXCEL parameter must be added to the end of the command:

WQ/OFFICE/DATE-EXCEL

Considerations to take into account in order to generate the report from the airline:

The agency to be consulted must be NO BSP and have a current account with the airline, otherwise the system will respond: INVALID OFFICE:

• If it is consulted date range, the period cannot be longer than 15 days

• You can consult sales reports up to 45 days before the current date.

• The user must have duty 4 and the ADMAGT keyword to generate the query.

Sales Report

Extensions

• To visualize a sales report indicating the VAT used for the issue, the / VT indicator must be added to the report, for example:

WL/COR00XXA#9SEP/VT

Applied only to report WL.

• To visualize a sales report indicating the Tour Code used for the issue, the / TOUR indicator must be added to the report, for example:

WL/COR00XXA#9SEP/TOUR

This extension can be applied to reports WA, WL, WQ

Is posible to use both extensions at the same time. The command is:

WL/COR00XXA#9SEP/TOUR/VTor WL/COR00XXA#9SEP/VT/TOUR

Display a detailed summary ticket issuances of an office

This command allows you to see the ticket issuances made both in travel agencies and in the airline's own offices, detailing the fees and taxes charged. It is necessary to have the keyword ADMAGT. The command is the following:

DQT{Office ID}*            Current Date

Example

DQT{Office ID}*{FECHA}                    Specified Date

Example

DQTLIM002I2*22OCT

DQT{Office ID}*{DATE}-{DATE}              15-day range 

Example:

DQTLIM002I2*22OCT-29OCT

Form of payment

Basic entry to display form of payment is

FOP

In order to display ticketing form of payment you must do the following entry:

To display the details about the form of payment you add the form of payment code to the basic entry.System will display all card  credit card companies that the airline accepts.

Entry

FOPCC

To display which credit cards are honored by another company you can do the following entry.

Entry

FOPCC/A+ Airline Code

Example

FOPCC/A8R

Description:

By default this entry displays the forms of payment enabled in the country of origin but if you wish to view those enabled in another country, the command is:

FOP / CAR

Description:

Both the country and company commands show all forms of payment except the  free form of payment because it is company private information.

Issuing an E-Ticket

Electronic Ticketing (e-ticketing) allows you to sell air transportation without issuing printed tickets. It also allows passengers to check in and board flights without holding printed tickets.

Considerations

• System issues an electronic ticket with four coupons

• E-tickets that have more than four segments will be issued in a conjunction ticket/tickets in the same transaction

• In order to issue a ticket, the reservation must be previously priced and the fare must be stored.

• PNR must not have any UN segments and it is advisable that the status codes be updated and previously recorded. (HK, HL, HM, MM). The system will issue exactly as priced.

• System allows to issue twice or more times an electronic ticket for the same passenger within  the same PNR and same segments, but from the second issuance for the same passenger ,the system sends an alert before performing the ticketing transaction.

If company policy is to require document information in the name field you can add this info before issuing a ticket with the following entry:

-1ø.NI 2041627        Changes or adds passport or document information

Description:

Issue ticket with cash form of payment

The following PNR is an example to issue a ticke with cash form of payment

WK*FCA

Description:

System response

OK. TKTs Nbr. 9990210005790

The answer is OK followed by the ticket numbers issued with a link to your display it on screen

When you retrieve the PNR the tickets will be display in this format:

Considerations:

• In the TKT / TIME LIMIT field, you can see that the deadline in element 1 was replaced by  e TKT/OK ,ticketing date and ticketing agent initials.

• From element 2 onward you will see the numbers of tickets with a link followed by the issue date,user initials and passenger last name and initial

  • To recover the data of the issued ticket can be done with CONTROL + CLICK with the mouse on the ticket link or the ET / {ticket number} command in the PNR.(This command is developed in chapter ETICKET PRINTING AND RETRIEVAL of this manual).

• You can display the ticket on a help screen only by clicking over  the ticket link.

• All these considerations are accepted for all possible forms of payment.

PNR history will display ticketing details:

Issue ticket with check form of payment

The system accepts check as another form of payment  The command for issuing with form of payment check is:

WK*FCK123455878 BCO NACION

Description:

Note: In the WR sales report this form of payment will be unified with CAS form of payment.

Issue ticket with credit card form of payment

The entry for issuing with credit card is:

WK*F/VI4054343467672121/1204/Z8990

Description:

Issue ticket with  extended credit card payment

WK*F/AX3489798789789797/1206/Z1235/C1

In the ticketing command with credit card extended payment you  can indicate the amount of installments which can be up to 12 in the C indicator

Batch Sale  

L batch number indicator

Example:

WK*F/AX3489798789789797/1206/Z1235/L354

Batch sale can be 1 to 6 digits long.It can be used for exchanges too

WK*F/AX3489798789789797/1206/Z1235/L354

In case you need to combine both installments and batch , installments must go first.

WK*F/AX3489798789789797/1206/Z1235/C1/L354

Issue ticket with debit card form of payment

Ticketing with debit card entry is as follows:

WK*F.EL4054343467672121/Z123

Description:

Add Batch Number

If you need to add batch number for debit card transactions you can use the L indicator to the ticketing entry which allows up to 6 digits.

Entry:

WK*F.EL456465464646/Z1235/L354

Issue ticket with  multiple form of payment

KIU System accepts up to two different forms of payment in the multiple ticket issuance. You can combine any of the two forms of payment

WK*FCA#/VI4054343467672121/1204/Z8990-120/40XT

Description:

Considerations:

• The amount paid  in the second form of payment is specified, the system will deduct it automatically from the total, and  have it reflected it in the sales report.

• The fare amount paid in the second form of payment can never be greater than net fare.

• When this entry is perform system assumption is that the amount input is for all passengers in the PNR unless it is specified by passenger selection of passenger type code like CHD or ADT in ticketing entry. 

• You can not combine payment methods that have online validation (credit card plus electronic accounts)

Issue Ticket with Invoice Form of Payment

The command for the form of payment to invoice is:

WK*FIN/MEDITERRANEO

Description:

Issue Ticket with Miscellaneous or Free Form of Payment

This form of payment can be used when there is a form of payment that is not described in the previous ones. The command for the free form of payment is:

WK*FXX FREE PAYROLL

You can also use the following entry as an option for the miscellaneous payment method.

WK*FMS/TO MIGRATION TICKETS

Description:

Issue tickets with segments not confirmed

If a reservation has segments with status MM (segment subject to space available), and in its JJETKT table the token named SAA (SA SEGMENTS ALLOWED) is set to N, the system does not allow the ticket to be issued.

This new functionality allows tickets to be issued even if the itinerary status is MM, regardless of the SAA token configuration of the JJETKT table, as long as the user has enabled a new keyword called TKTSAA.

SAA token configurations

Currently the SAA token settings in the JJETKT are as follows:

• Y: the issuance of segments with MM status is allowed

  • If it is in H, issuance is allowed at the airline's points of sale

  • If it is in A, issuance in travel agencies is allowed

  • If you are in HA, issuance is allowed both at the airline's points of sale and at travel agencies

• N: the issuance of segments with MM status is not allowed

  • The system response is INVALID - STATUS NOT SUPPORTED BY CARRIER

Case of use

PNR:

RP/SST00XXA - LINEAS AEREAS XX
 1.1TEST/MARCE   »PP6666
 1  XX4370Y 03AUG MO AEPMVD MM1  2200 2300
 2  XX006 Y 04AUG TU MVDCOR MM1  0500 1000
TKT/TIME LIMIT
  1 TX AEP 1619/03AUG-MON
FARE - PRICE RETAINED
CONTACTS
  1-SST 77777
AEP.KIUHELPMC 1909/03AUG20   *RWIKNK

Issuance:

• Without TKTSAA keyword

WK*FCA
INVALID - STATUS NOT SUPPORTED BY CARRIER

• With TKTSAA keyword

WK*FCA
OK. TKTs Nbr. 9990210009546

Manual Exchange with Refundable Balance

For Manual Exchanges where calculations result in a residual amount, depending on the carrier and fare rule, you may be able to refund that amount to the passenger issuing an EMD-S.

In this case passenger will have those WC,EV,UM and ZA  taxes amounts refunded.

You click NEXT and you will see following screen

There is no fare additional collection. You see that system will issue an EMD-S of 6460.11 refundable amount for residual fare and 679,33 residual taxes.

You can display EMD with the following entry:

EMD/element number

You will see the reason for issuance code which is Financial Impact with a residual value of 6460.11 to be used for future travel or refunded if applies. 

In case taxes were not applicable by the time of issuance or did not apply system will display them in this screen. 

Manual Exchange by Commands

This mode will be used for a single ticket and in full exchanges only. In case there is a used coupon or an exchange with residual value a mask must be used instead of commands. In case you want to do it by commands system will display a mask to complete with the data. 

This Exchange mode allows the system to automatically calculate the amounts net of the fee to be taken as part of payment, difference in charge rate, penalty, additional fees and taxes, etc., without the need to use the mask.

Manual Exchange with additional collection

WK*FEX#CA

Description:

When executing this command the system will return the following information in response:

Description:

• EXCHANGE DOC NUMBER: ticket number to be exchanged, passenger name and type

• ADDITIONAL COLLECT AMOUNTS: The system will calculate the fare difference to be collected and reflected by comparing the values of the exchanged ticket and the ticket to be issued.

• EQUIV FARE: in this field the amount to be charged as difference will be displayed.

• ARS: currency code of the amount to be charged.

• OLD: net fare that will be taken as part of payment  towards the issuance of the new ticket.

• NEW: net value of the new fare.

• TAX: in each of the OLD and NEW columns 

• PENALTY: this field will reflect the amount of the penalty to be charged.

• TOTAL: in this field the total amount to be charged as difference, net rate plus taxes

• A / C TAXS DETAILS: in this field you will see the additional fare amounts  and taxes to be charged on the new itinerary

The system will display the following warning when ticketing:                  To confirm the Exchange transaction you must execute the same command by adding it / Y at the end of it, or move the cursor to the end of the second line of the system response and press the ENTER key

OK. TKTs Nr and EMD ISSUED

New ticket number will be displayed and EMDS with the additional collection.

Manual Exchange with additional collection and two forms of payment

In this case, you can use two forms of payment in addition to the exchange:

• Use the same criteria for multiple form of payment, placing the first form of payment separate from the second with a # pound sign and after placing the second form of payment.

• After second form of payment add a hyphen and add the amount of the second form of payment and then add a slash and then total tax amout followed by XT

WK*FEX#CA#/DC4546424205891254/1010/Z123-108/57.26

Description:

Manual Exchange with Penalty Collection

Whenever you need to add a penalty on an exchange you need to perform the following entry:

WK*FEX#CA*PE50

Description:

And still confirm with /Y in order to complete the transaction

Manual Exchange applying discounts

WK*FEX#CA*Q/AD90/DP90X

Pricing  stored in the PNR should match the discount indicator applied.

In the example WS*Q/AD90/DP90X

Manual Exchange Selecting Passengers

WK*FEX#CA*N1

Manual Exchange Selecting segments

In case  you want to select the segments of the new itinerary to be exchanged. If you do not specify the segments system will reprice whole PNR route by default.

WK*FEX#CA*S1

Automated Exchange

When the airline profile is enabled for this function, the system will process all the Exchanges, with or without flown coupons , calculating the amounts automatically, both in the ticketing by masks as in the direct ticketing.

The following indicators should be activated in the JJETKT table. Modification must be requested host@kiusys.com

[AEX]AUTOMATIC EXCHANGE: Y

The main action of this functionality is that in cases where the ticket to be exchanged contains flown or non-exchangeable coupons  the system will automatically take OPENvalue coupons  to perform the assessment and subsequent exchange of these coupons.

On the other hand, with this  functionality activated, the amounts, in all types of Exchanges, CANNOT be modified manually unless the agent has OVERAUER keyword in the profile .

The commands to perform these transactions are the same ones that are used regularly, only the necessary commands and indicators are added to modify or manipulate the amounts.

Modify Exchange Amounts with a Mask

WK*FEX/OVEREX

Description:

Modify Exchange amount in Direct Ticketing

WK*FEX#CA/OVEREX

Description:

Modify Exchange amount and Waive Penalty

WK*FEX/OVERPE/OVEREX

Description:

Modify Exchange amount and Waive Penalty a Add manual Penalty

WK*FEX*PE50/OVERPE/OVEREX

Description:

Partial Exchange with Unidentified  Amounts

For those ticket  issuances with masks, which come from another system / GDS or issuances  made prior to the activation of this functionality by the airline.
There are two options for processing them, depending on the configuration you decide to use:

Partial Exchange Enabled

When performing this transaction, the system will display the values in favor of the blank passenger in the first mask . (without reference values) since it can not calculate the values automatically in the ticketing scenarios described above. The agent will  have to manually input fare and taxes in order to execute the exchange The entry of this information does not imply that the user must have the keyword that allows data manipulation.

To accept this option in the table JJETKT/<country> must be configured the following parameter in the selected sales channels.

When you perform one of these exchanges the system will display the legend Partial Exchange

Add Residual Amounts to prompt the user to enter the data manually

Partial Exchange Disabled 

When you do not allow partial exchange, the system will display the following error message when want to proceed to perform an exchange of a ticket issued with masks, which come from another system / GDS or ticket issuances prior to the airline activation of this functionality.

The only way to proceed will be with the keyword OVAUER that allows the manipulation of the exchange masks:

WK*FEX/OVEREX

Once this command is executed, the previous mask will be opened to manually enter the residual values on the passenger behalf. To accept this option in the table JJETKT / <country> must be configured with the following parameter in the selected sales channels.

Involuntary Exchange (Not implemented)

When the ticket exchange is not requested by the passenger, and is caused by the airline, an Involuntary Exchange can be carried out, using the following command:

Example:

WK*FEXI*S1*E1

Notes:

• Do not quote the new itinerary

• The ticket to be exchanged must be displayed prior to the involuntary exchange command

• When an involuntary exchange is carried out, no fare difference or penalties will apply

• The total field of the new ticket will show NO ADC

• The endorsement INVOL REROUTE will be added automatically

• At the beginning of the fare construction, the indicator "I-" will be added.

• The fare construction of the new ticket will be a copy of the one in the original ticket

• The fare basis of the new ticket corresponds to that of the first affected segment (original ticket), and is repeated in all coupons impacted by the change

• The command requires confirmation adding / Y at the end of it

Exchange simulation

In order to know the amounts as result of the exchange without saving itinerary changes, it is possible to simulate a ticket exchange.

The following steps will allow the user to simulate the ticket exchange and see the amounts on the screen:

1. Retrieve the PNR

2. Modify the itinerary as needed (Do not save changes)

3. Quote the new itinerary selecting corresponding segments. E.g.: WS*FEX*S2 (Do not save changes)

4. Display the e-ticket to be exchanged

5. Enter the exchange transaction as follows and the system will display on screen the amounts that will result from the exchange: WK*FEX*S2

WK*FEX*S2/USD
 EXCHANGE DOC NUMBER 9990210029539 ** PAX NAME: MILES/PETER  ADT

 ADITIONAL COLLECT AMOUNTS:                        USD             OLD             NEW
                           EQUIV FARE <           0.00>         333.33          333.33
                           TAX        <           0.00>           0.00            0.00
                           PENALTY    <           0.00>   
                           TOTAL      <           0.00>
                           FEE        <           2.00> 
                           GRAND TTL  <           2.00>

TO PROCEED WITH THE TICKET EXCHANGE, SAVE CHANGES IN THE RESERVATION

Further options for ticketing

In order to use all the options accepted by the system, it must be taken into account that the PNR must be priced in the same way that will  be ticketed. 

Ticket  Issuance Selecting Passengers

You can issue tickets by selecting one or more passengers of a PNR without having to divide it in order to issue. To do this, you must first select the passenger ,price and record it.The indicator that defines the passenger is: N

Example:

WK*FCA*N1,2

Ticket  Issuance Selecting Segments

You can partially issue one or several segments of a PNR. To do so you have to price those selected segments,record pricing and then issue.

• Segment indicator is S

Example:

WK*FCA*S1,3,5-7

Ticket with discount

You can issue a fare with a discount  percentage from the 100% that you would normally pay. 

WK*FCA*Q/AD90/DP90

Description:

Ticket with discount excluding a preset discount

The functionality of this command is the same as in the previous point but the objective is to exclude the pre-established discount by the fare rule and quote on 100% of the published,fare for example in case of issuing a CHD passenger that already has a percentage of pre-established discount on an adult rate.

WK*FCA*Q/AD90/DP90X

Description:

Ticket with discount forcing fare basis

You can issue a ticket with a different fare basis than the one matching RBD

WK*FCA*QVAP

Description:

Ticket  replacing Taxes

You can ticket  replacing taxes. This action will eliminate all applied taxes replacing them with those indicated in the command.

WK*FCA* TX20TQ/65SF

Description:

You can also add or remove taxes or fees that are not in the automatic pricing

To add

When adding, it must be taken into account that the same taxes are not repeated.

WK*FCA*TX+12QO/56.50AR

Description:

To delete

When deleting it must be taken into account that the taxes are within those applied in the fare quote.

WK*FCA*TX-XR/DL

Description:

Ticket  Exempting Taxes

This action will eliminate all applied fees.
The command is:

WK*FCA*TXEX

Description:

When  issuing tickets with tax exemptions using the * TX- or * TXEX modifier, instead of simply removing the values, the word EXEMPT will be followed by the exempt tax code.

This change can be seen in the pricing response as well as  in the ticket displays, and  ITRs.

Ticket indicating commission

You can add a commission percentage  to be  discounted  at the time of ticketing.

Example:

WK*FCA*KP10

Description:

This will be reflected in the e-ticket issued and in the sales report

Ticket with endorsement field

The endorsement field when ticketing is taken by default  from what the company has configured, but the it can be modified in the ticketing command.

• Indicator is ED/

Example:

WK*FCA*ED/free text

This will be reflected in the e-ticket endorsement box.

Ticket with Tour Code

In case you want to add a tour code there is the command * U followed by different options of BT or IT tour code display with or without fare displayed or hidden.

Example:

WK*FCA*UB/(tour code)

This indicator will print the acronym BT  instead of the fare amount when printing the electronic ticket The name of the tour code is displayed as BT (tour code)

Example:

WK*FCA*UB(tour code)

This indicator will print the fare amount on the electronic ticket print. The name of the tour code will be displayed as BT (tour code)-

Example:

WK*FCA*UI/(tour code)

This indicator will print the IT symbol in place of the fare amount when the e-ticket is printed. The name of the tour code  will be displayed as IT (tour code)

Example:

WK*FCA*UI(tour code)

This indicator will print the fare amount on the printing of the electronic ticket print. The name of the tour code is displayed as IT (tour code)

Example:

WK*FCA*UN(tour code)

This indicator will display the fare amount, The name of the tour code will be displayed without any acronym. The tour code field accepts up to 12 alphanumeric characters.

Ticket with Baggage Allowance detail

The  baggage field when ticketing is taken by the company default that  has been configured according to the type of travel,  but the same can be modified in the ticketing command.

• Indicator is BA

Example

WK*FCA*BA 15K (or 2P or 20L)

Description:

Ticket with Fiscal Identification Code

The fiscal identification code can be used  optionally . The format can be free or you can have a fixed format, depending on the configuration of the country.

• Indicator is VT/

WK*FCA*VT/Fiscal Identification Code

This will be reflected in the e-ticket below the passenger type

The maximum number of characters to enter in the VT field is 50 (between numbers,spaces and letters)

Remote Ticketing

The system gives you the possibility of remotely issuing a ticket, that means that a user physically located in an office  can perform a sale leaving it settled in the report of sale of the remote office.

In order to perform a remote ticketing the system will validate the following conditions;

• User profile must have keyword ISSREM assigned.

• Reservation must be priced remotely, if the conditions of the tariff so specify

• Price  with remote location (if necessary)

• You can force the remote location for pricing using another city.

Example WS *RMVD

WS*Rcity

Description:

Once the reservation is priced remotely, the ticket can be sold remotely.

Remote Location Ticketing

To perform a remote sale, you must use the following command:

WK*F(Form of payment)*R(Remote office)

Example:

WK*FCA*RMVD00XX2

Description:

WL Sales Report

When performing a remote ticket issuance the sale will be reflected in the report of the indicated city, but with the user who actually did it.

Ticketing with Agency Involved field

Once a customer has been created, the code can be used to issue the e-ticket. The command to issue is the following

WK*FCA*I/55555

Description

This command will apply the corresponding commission according to the table and will place the code in the eticket below the reservation code

Verify Agency Involved Table 

You can verify the customer table with the following command

IT

Also you can narrow your search if the answer is TOO MANY ITEMS.

• INT

• INTJNB (filtered by city)

• INTJNB/A(filtered by city and letter starting with)

Ticket indicating date of birth

To indicate the date of birth at the time of ticketing you must type the following entry

WK*FCA*DOB/20APR77

This field is optional and will be reflected in the e-ticket

Description:

Description

Ticket considering Eligibility rule

To issue fares that have an eligibility rule you must use the following entry

WK*FCA*P<eligibility code>

Example:

WK*FCA*PSD

Ticket indicating Passenger Type Code

After creating a PNR indicating a specific passenger type code or PTC, pricing follows next and finally ticketing with the regular command you will see the PTC in the name filed and the the end of the fare basis.

PTC does not have to be indicated in the ticketing entry.

WK*FCA*N3

YTH (Youth passenger) example in ET:

ET/2
TKTT-9990210005872                                                          C1/HJOJHX
  OD-AEPCOR      POI-AEP    DOI-6NOV17           IOI-AR000010      0  0                  I/
  ED-END / REF  CONDITIONS AND PENALTY APPLY
     1.TEST/JOVEN                              YTH
       FOID: PP2233                           CUIT: 
/..72  1   AEP        XX  203 Y 10NOV 0725 OK YYTH                          20K    OPEN FOR USE    
           COR
FARE      ARS      150.00                                BSR      1.00000
EQUIV     ARS      150.00
TAX       ARS       16.46DL        6.75QN       20.00TQ       35.97XR
TOTAL     ARS      229.18
                                                      TOUR CODE  : 
                                                      COMMISSION : 
/FC BUE XX COR 150.00ARS150.00END
FOP:       229.18  CASH

CHD PTC example:

ET/3
TKTT-9990210005873                                                          C1/HJOJHX
  OD-AEPCOR      POI-AEP    DOI-6NOV17           IOI-AR000010      0  0                  I/
  ED-END / REF  CONDITIONS AND PENALTY APPLY
     1.TEST/PEQUE                              CHD*YTH
       FOID: PP556677                         CUIT: 
/..73  1   AEP        XX  203 Y 10NOV 0725 OK YYTH                          20K    OPEN FOR USE    
           COR
FARE      ARS      150.00                                BSR      1.00000
EQUIV     ARS      150.00
TAX       ARS       16.46DL        6.75QN       20.00TQ       35.97XR
TOTAL     ARS      229.18
                                                      TOUR CODE  : 
                                                      COMMISSION : 
/FC BUE XX COR 150.00ARS150.00END
FOP:       229.18  CASH

Fill in Masks for ticketing

The objective of the masks is to be able to issue tickets with fares that are not published. Pricing  masks must be created  first to be able to take the necessary information and store it in order to be able to issue the ticket. The mask will be stored with a validity period of 30 days and after that it will be deleted.

Create Mask Header with Graphical Assistant

To create a mask it is necessary to have a newly retrieved  PNR (without any recent modifications) and with no UN segments.

In case of having to make any modifications in the PNR, theses must be done first, recorded and then you must retrieve the unchanged status PNR.

The command to start creating a mask is:

W*TKT

This command displays the following screen

• To enter the different Tour Code options, the U indicator must be omitted. example: instead of entering UB / <TOUR CODE> to hide the fare, you must enter only B / <TOUR CODE>. In case you want to use the option UN in the fare mask,it will not be necessary to enter the acronym.

• Currencies offered in the mask correspond to those configured in the country of origin of the trip ,and those of the country of the terminal that is creating the mask.

Once this screen is recovered, the data corresponding to each box is loaded,Once you have completed the necessary data, you will go to the next screen, by pressing the button NEXT

This screen is also completed with the necessary data and once finished, press the Finish button.

The response displays the loaded data in the following way

If the data is correct, the PNR must be recorded with ER, if not, it can be ignored with I to start again

When recording the PNR with ER and then retrieving it will be possible to see a REMARKS field where the mask  has been stored.

Once the mask has been recorded,you can proceed to ticketing .Up to nine masks can be loaded within the same PNR.

It is important to keep in mind that masks are created by passenger type. The command W * TKT creates by default an ADULT passenger mask, if you want to create some of CHD or INF, the commands would be

W*TKT*PCHD for Child

W*TKT*PINF for Infant

To view all the masks loaded inside a PNR, the command is:

To see the details of Mask 1 you must enter W*1 ,W*2 according to the mask number.

Delete a Mask

The masks have a validity of 30 days once loaded but can be erased  manually in case it is necessary.

W*D

This command deletes the mask that is stored in the PNR. The correct answer is DONE

Closing the PNR will automatically delete the Remark field:

If there are 2 or more masks recorded in the PNR, they can be deleted individually or partially.
The command would be:

W*D1,3 Deletes mask 1 and 3

Ticketing overriding Currency

In case you want to create a ticketing mask with a currency different from the origin of the trip or the terminal, it is allowed to override the currency with the following commands

W * TKT / <CURRENCY

Example:

W*TKT/EUR

To override currency and  passenger type , the command is as follows:

W * TKT / P <PASSENGER TYPE > <CURRENCY>

Example:

W*TKT/PCHD/EUR

Ticketing  with Masks

Ticket issuance with mask is very similar to direct ticketing .The difference is that you must clarify what mask you want to issue, in addition to passengers, in the case of having different passenger types.

As in the direct ticketing, the same forms of payment are used, applying them in the same way.It is essential to have the mask that will be used, loaded and recorded in the PNR.

Once the mask is created and recorded, the issuance of a ticket can be generated.

Taking as an example the following PNR, the input command for ticketing is:

Code Block
language xml
WK*M1*FCA

Description:

WK*M	Fixed ticketing entry
1	Mask number
*	Divider
F	Form of payment
CA	Cash

System Response:

When retrieveing the PNR, it will look like this:

Replacing ticket time limit , a ticket field is generated for each one issued with the number of the same, the last name / initial of the passenger and the date of issue. Tickets will be issued for the value that is loaded in the mask.
When executing the command, that data is recorded in the PNR as a transaction in the PNR history.

Ticketing  with Exchange Form of Payment 

---

The command to use an exchange payment method with an issued ticket with mask is:

Code Block
language xml
WK*FEX*M1*N1

Description:

WK*FEX	Fixed Format
*	mandatory divider
M1	Mask number 1
*	mandadory divider
N1	Passenger number 1

The procedure and the rest of the mask is completed in the same way as detailed in direct ticketing .It should be noted  that the fare to be used in the issuance of the new e-ticket will be the value of the mask.

E-Ticket Status

These codes are used in the e-ticket display which allow to display the coupon status. Every coupon has a status which are identified by a letter.

Mass email sending

This option is valid only for sending  several ITRS by email, but to a single email address.

Command examples:

ITR / 2,3-MAIL @ MAIL.COM ->     ITRs to an e-mail (the "comma" works as a "y")
ITR/2-5-MAIL@MAIL.COM ->         ITRs to an email (the "hyphen" forms range of tickets)

Example with ticket numbers:

ITR/9990210005147-MAIL@MAIL.COM -  >              1 ITR to a single email address
ITR/9990210005147,9990210005148-MAIL@MAIL.COM --> 2 ITRs a un mail ("comma" works as a "y")

Same scenarios as above but with email entered as contact (when referring to the letter "M" to an email previously entered in the reservation):

• ITR / 2-M2

• ITR / 2,3-M2

• ITR / 2-5-M2

Void a Ticket

An electronic ticket can be canceled or voided provided that it meets the following conditions:

1. Personal Sales Report must be open

2. PNR associated to the ticket must be displayed.

3. Ticket must be within the Personal Sales Report active or in the current day.

4. The execution time of the command may not exceed the flight schedule, unless the user has the VOIDAL keyword to bypass this restriction

5. To perform the cancellation of a ticket remotely, the user must have the RPGSPV keyword.

Fulfilling the conditions mentioned, the entry command to cancel a ticket electronic is:

W*V9992100212135

Description:

The system will return the following message.

W*V9990210005980
RE-ENTER FOLLOWING COMMAND TO PROCESS
W*V9990210005980/Y

To validate the cancellation of the ticket, you must execute the same command by adding / Y at the end .

Void a Single Ticket within a PNR

When performing a  VOID transaction , if the ticket to be voided is the only one in the PNR, the system places an automatic cancellation expiration of 10 minutes from the moment of execution of the cancellation command.

Example

TX will display cancellation time:

Code Block
RP/AEP00XX4 - LINEAS AEREAS XX 1.1MAR/AREL »PP909099091 XX203 Y 20FEB TU AEPCOR HK1 0725 0825 TKT/TIME LIMIT 1 TX AEP 0528/17NOV-FRI FARE - PRICE RETAINED CONTACTS1-BUE H RECEIVED FROM - XAEP.KIUHELPPC 0758/17NOV17 *CNBEIG -H~006CNBEIG

Void a Reimbursement Note

---

if a void is performed on a reimbursement note that was paid against an electronic account , the system checks the credit of the account and allows to perform the void operation,as long as there is enough credit.

When performing the cancellation of a reimbursement note , the documents contained therein,  will have the status OPEN FOR USE again.

Reimbursement note will be generated and reflected in the sales report for the voided documents. Information will be displayed in the TICKET column inside the E-TICKET REFUND item.

Move E-tickets from a Purged PNR 

This command allows you to move an e-ticket that belonged to a PNR already purged, to a new one PNR. This command will add the corresponding ticketing fields to the PNR, canceling the expiration or the manual ticket field. In addition there will be a change to the booking in the PNR history of the electronic ticket.

Considerations

•   PNR displayed in the work area must be confirmed, priced and recorded in the pricing mask

•   E-ticket that you want to move must be retrieved in the work area.

•   E-ticket must have at least one Open For Use coupon.

•   Last / First name of the e-ticket must match the Last / First name of the passenger of the PNR  to which it will be associated (depending on the configuration made by the airline).

•   Passenger type must also match.

•   Booking code to which the e-ticket originally belonged must be purged.

Once the e-ticket has been moved to the new PNR, it is possible to carry out the revalidation or necessary changes. Although it is not necessary to move an e-ticket to make a exchange or a refund, it can also be done.

The command is:

ETMV/P1

Description:

The positive answer is OK. It will modify the TKT / TIME LIMIT field with e-ticket data.

Example:

Date displayed on this field is the e-ticket move date.

PNR history will display it in the following format

In addition, the system may display 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 e-ticket to be associated has different segments than the PNR itinerary

PRICE DISCREPANCIES When the fare amounts and e-ticket fares do not match the passenger type fare quoted in the PNR (not the classes)

These warnings are general. To ignore these warnings and proceed to move the eticket, the command must be executed with / Y at the end (as in ticketing )

Unassociated Ticket

If  the name of a passenger who already has a ticket issued is changed, the system disassociates the passenger ticket.
When changing some of the items in the name field (last name, first name, or foid fied) the system will respond to the following message informing that the quote has been deleted (if the PNR was quoted) and that the ticket has been disassociated:

In the PNR history there will be a record of this

XN 1CASARES/CLARA ** PAX WITH TICKET // UNASSOCIATED TICKET ** »DNI 43423

** WARNING: TICKET REMOVED FROM PNR ** »PP 61195904

Keep in mind that once a ticket has been disassociated from a passenger name, there will be no ticket Open for Use .So please take into account this considerations;

1. If a passenger is split from a pnr,the previously issued ticket will remain in the original  PNR and will not be moved into the new one. 

2. The passenger is left without an associated ticket ,when checking LD list no et indicator will be shown.

3. To re-associate a ticket with a passenger, an exchange must be made

Ticket Upgrade/Downgrade 

This functionality allows you to change the cabin class of a ticket without the need to make an exchange

In order to perform this ticket class update, you must have  keyword TKTUPD (ticket update) in the signature and one of the following duties: 4, 5, 7 and / or 8.

The command to change the class of a ticket, having the PNR and the ticket displayed on screen, is:

ETUP/E1/C/UPGRADE OK

Description:

The command to change the class of a ticket with PNR displayed on the screen is:

Description:

You could also indicate the e-ticket number in the command as follows:

ETUP/9992200015739/E1/C/UPGRADE OK

Ticket history
Class changes, previously mentioned, will be recorded in the ticket history as shown in the image below:

In the OBSERVATION column the text UPDATE CLASS will be displayed  and  the text that added in the command.

Queue

Each time a change of class is made, to an issued ticket , the system will  automatically send a warning message to queue 184 of the HDQ city (see Queues Manual)

Final Status Tickets Deletion

This function allows deleting active PNR data from  ETKTs and EMDs coupons with final status.

ETCHK/CLEAR

• Remove TICKETS with final status coupons from the active part of the PNR

EMDCHK/CLEAR

• Remove EMDs with final status coupons from the active part of the PNR

Once the command has been executed, the system will display all those ETKTs or EMDs, that will be removed from the active part of the PNR and recorded in the history.

The display will show the document type (TKTT or EMD); documents order number in the PNR;  document number to be removed; passenger order number in the reservation, last name and the name initial.
To confirm the action, the command must be re-entered by adding the / Y flag to the end of it.

Example:

Once the transaction is confirmed, you must enter  E / ER command to record the changes, or I / IR to ignore the changes made.

Coupons with these final status will be recorded in PNR history. 

• REFUNDED

• CLOSED

• EXCHANGED

• FLOWN

• PRINTED

• PRINT

• EXCHANGED

• NOT AVAILABLE

• FIM

If any of the following  status is found on the coupons transaction will be ignored.

• OPEN FOR USE

• AIRPORT CONTROL

• NOTIFICATION

• CHECKED-IN

• IRREGULAR

• LIFTED/BOARDED

• SUSPENDED
  

Considerations:

• This functionality can be executed with any of the available duties

•  The command can be executed as long as the PNR is not in the Update Mode

• If, as a result of the ETCHK / CLEAR command, the PNR has no deadline then a new time limit must be set.

• If the command is executed on a reservation without ETKTs / EMDs, or in which there would be no documents to remove, the system will respond to the following error:

INVALID - NO DOCUMENTS TO CLEAR

You can view changes made by the commands ETCHK/CLEAR y EMDCHK/CLEAR in the PNR history under XTK and XEMD indicator and with the text CLEARED as shown in the following example.

This functionality is not available for webservices