Reservations

This module describes how to work on a flight reservation in KIU. The main functions are the following:

• Create
• Modify
• Cancel
• Price
• Passenger lists
• Fare rules
• Messages

back to top

PNR (Passenger Name Record)

A PNR is an electronic record which consists of the passenger’s travel information. There are some mandatory fields and some optional fields required to create the PNR and obtain the record locator.

Records locators are unique and can be retrieved at any time.

There are individual PNRs (maximum of 9 passengers) and groups PNRs (minimum of 10 passengers).

The system stores a total of 99 passengers in a PNR, including adults, minors and infants, whether an individual or group PNR.

PNR mandatory fields are:

• Passenger Name
• Itinerary
• Contact Information
• Ticket Number/Time Limit
• Received From
• End Transaccion

back to top 

PNR description

PNR display screen:

 RP/BUE00XX7 - LINEAS AEREAS XX
 1.1CAMPACHO/SEBASTIAN
 2.1VERTENA/DAMIAN
 3.1CAMORALEJO/ERNESTO
 1 XX4500N   22JUL JU AEPCOR HK3  08:00 09:00
 2 XX4444Y   23JUL VI CORAEP HK3  13:00 14:05
TKT/TIME LIMIT
 1.TL BUE 1800/10JUL-SAT
CONTACTS
  1-BUE 5455 7878
  2-COR  0351 46731213
  3- MAILTO:CAMPACHO@HOTMAIL.COM
REMARKS
  1-CHEQUEAR DOCUMENTACION AL EMBARCAR
  2-PASAJERO VIP*/P2
RECEIVED FROM - JOSE
BUE.BUEXX-MM 1909/29JUN04   *PLRKZB

Description:

RP/BUE00XX7 - LINEAS AEREAS XX

PNR responsible -   PNR creator

1.1CAMPACHO/SEBASTIAN
2.1VERTENA/DAMIAN
3.1CAMORALEJO/ERNESTO

1 XX4500N   22JUL JU AEPCOR HK3  08:00 09:00
2 XX4444Y   23JUL VI CORAEP HK3  13:00 14:05

TKT/TIME LIMIT
 1. TL BUE 1800/10JUL-SAT

CONTACTS
 1-BUE 5455 7878
 2-COR 0351 46731213
 3- MAILTO:CAMPACHO@HOTMAIL.COM

REMARKS
  1-CHEQUEAR DOCUMENTACION AL EMBARCAR
  2-PASAJERO VIP*/P2

Remark field

RECEIVED FROM - JOSE

BUE.BUEXX-MM 1909/29JUN04   *PLRKZB

PNR creator sign - date and time - record locator

back to top 

PNR creation

Availability

The availability request format displays the list of flights available from the requested date to 6 am of the following day, in ascending order by departure time.

The format is the following:

102JUNAEPCOR0900

1COR

• the departure date is the date on which the request is made
• the city of origin is the city from where the request is made
• the time is the present time where the request is made

Response:

** KIU® AVAILABILITY ** TO COR/CORDOBA, ARGENTINA      WED 02JUN04 H0400   1D
 
  1 XX4512 Y9 B9 HR K9 M9 N9 OR AEP3A COR C 04:00   05:00      0 DC9 234   1:00
            T9 GR
  2  XX4628 Y9 B9                AEP   COR   04:00   05:05      0 DC9 D     1:05
  3  XX4500 Y9 B9 HR N9          AEP   COR   08:00   09:00      0 DC9 D     1:00
  4  XX4556 Y9 N9 M9 B9          AEP   COR   10:00   11:00      1 DC9 D     1:00
  5  XX4514 Y9 B9                AEP   COR   12:00   14:45      1 DC9 X7    1:05
* 4 MORE FLT [XX]

Description:

First line display description (availability request):

1 XX4512 Y9 B9 HR K9 M9 N9 OR AEP3A COR C 04:00   05:00      0 DC9 234   1:00 

An availability request displays up to 9 flights. If more flights are available the system will show:

* 4 MORE FLT [XX]

The system response indicates that there are 4 more flights on the requested date to be displayed operated by XX carrier. In order to visualize them, the following format must be used:

1*

** KIU® AVAILABILITY ** TO COR/CORDOBA, ARGENTINA      WED 02JUN04 H0400   1D
  6  XX4520 Y9 B9                AEP   COR   14:00   16:45      1 DC9 D     2:45
  7  XX4432 Y9 B9 HR             AEP   COR   22:40   23:40      0 DC9 D     1:00
  8  XX4512 Y9 B9 HR K9 M9 N9 OR AEP   COR   04:00+1 05:00+1    0 DC9 234   1:00
            T9 GR
  9  XX4628 Y9 B9                AEP   COR   04:00+1 05:05+1    0 DC9 D     1:05
* MORE

This response shows operating flights from item 6 to 9. Flights on items 8 and 9 are operating on the following day as shown by +1 indicator placed after the departure or arrival time.

  9  XX4628 Y9 B9            AEP   COR   04:00+1 05:05+1    0 DC9 D     1:05

At the end of the response, the system displays the following message:

* MORE

This message indicates that there are more flights available operated by other airlines. The same format may be used to continue with the search:

 1*

** KIU® AVAILABILITY ** TO COR/CORDOBA, ARGENTINA      WED 02JUN04 H0400   1D
  1  A46594 Y9 B9                AEP   COR   10:00   11:15      0 737 D     1:15
  2  A46670 Y9 B9                AEP   COR   11:00   14:20      1 737 D     3:20
  3  A46668 Y9 B9                AEP   COR   12:00   14:00      1 737 D     2:00
  4  A46588 Y9 B9 H9 K9 N9 M9 T9 AEP   COR   13:15   14:30      0 737 X6    1:15
            X9 W9 Q9
   #EMBARCA POR PUERTA 12
 
*NO MORE

The system response displays flights operated by A4 carrier. The message EMBARCA POR PUERTA 12 (BOARDING GATE 12) appears below item 4 as a comment, which was introduced when the flight was created.  

At the end of the response, the system displays the following message:

*NO MORE

This message indicates that there are no more flights available.

Options:

The search can be done from an availability request using previous or subsequent days. The formats are the following:

1R20JAN

1R+2

back to top

Availability request including connection flights

Connection flights

If there is no space available on direct flights, the system displays segments including connection flights. For example:

120SEPBUERGA

** KIU® AVAILABILITY ** TO RGA/RIO GRANDE, AR          TUE 20SEP05 H0000   4D
   1  5U 752 P9 S9 Q9 J9 R9 E9 F9 AEP   RGL   08:00   11:55      1 F28 2     3:55
  ->  5U 954 P9 M9 S9 Q9 J9 R9 E9 RGL   RGA   15:00   16:10      0 TWO 2     1:10 > 8:10
             F9
   2  5U 752 P9 S9 Q9 J9 R9 E9 F9 AEP   RGL   08:00   11:55      1 F28 2     3:55
  ->  5U 952 P9 S9 Q9 M9 E9 J9 R9 RGL   RGA   16:00   17:10      0 TWO 25    1:10 > 9:10
             F9

The connection flights are shown on the same item.

Item 1 shows flight 752 from AEP to RGL and, on the next line, -> indicates the connection with flight 954 from RGL to RGA. Both flights are followed by the departure and arrival time, the number of connections, the aircraft equipment, the operating days and the duration of the flight.  

> 8:10 shows total flight time considering flight duration and connecting time.

How to book connection flights:

In order to book a connection flight from an availability request, as shown in the previous example, there are two ways:

• Same booking class:

02P1

1    5U 752 P  20SEP TU AEPRGL SS2  08:00   11:55      1   F28
2    5U 954 P  20SEP TU RGLRGA SS2  15:00   16:10      0   TWO

The system books the two segments on the same booking class. 1 and 2 indicate the item number. In order to crate the PNR, the rest of the mandatory fields must be created.

• Different booking class:

02PS1

  1    5U 752 P  20SEP TU AEPRGL SS2  08:00   11:55      1   F28
  2    5U 954 S  20SEP TU RGLRGA SS2  15:00   16:10      0   TWO

The system books each segment on the requested booking class.

Error response:

In the event of requesting a booking class which is not available on any flight, the system shows:

01Y1
INVALID CLASS

In the event of requesting a booking class which is not available on one of the flights, the system shows:

01PY1
  1    5U 752 P  20SEP TU AEPRGL SS1  08:00   11:55      1   F28
INVALID CLASS

When the desired booking class is available on a flight, the system books the segment. However, when the desired booking class is not available, the system responds INVALID CLASS, and does not book the segment.

back to top

Availability by airline

Flights can be requested by carrier. The format to request availability for a flight is followed by /A and the airline two letter code, as follows:

 110OCTBUEGOG/AXX

back to top

Filter by flight number

1<date><route>/FL<carrier><flight number> 

Example:

120AUGAEPCOR/FLXX506

Flight specific availability will be displayed.

Filter by number of available spaces

1<date><route>/PQ<value>

Example:

120AUGAEPCOR/PQ3

This command will display options with at least 3 spaces available.

Filter by class of service

1<date><route>/CL<value>

Example:

120AUGAEPCOR/CLY,B,H

This command will display class specific available options.

Filter by time window according to departure time

1<date><route>/TD<minimum departure time>-<maximum arrival time>

Example:

120AUGAEPCOR/TD0800-1600

This command will display options with available flights within the time window requested.

Filter by time window according to arrival time

1<date><route>/TA<minimum arrival time>-<maximum arrival time>

Example:

120AUGAEPCOR/TA0800-1600

This command will display options with available flights within the time window requested.

Itinerary

Direct segment sell

Space Request:

In order to use the direct segment sell, the flight number, the booking class, the date and the routing are required. The format is the following:

 0XX4520Y20JUNAEPCORNN1

 1    XX4520 Y  20JUN SU AEPCOR SS1 14:00   16:45      1   DC9

Description:

In the event of requiring confirmed spaces (NN) and the flight being full, if the waiting list is open the system responds:

1 XX4520 Y 08JUN TU AEPCOR LL1 14:00 16:45 1 DC9 ** NOT AVAIL, SEGMENT IN WAIT LIST

The required segment will be booked as LL (waitlisted status) and followed by a message indicating that the flight is placed on the waiting list. 

There is a possibility that the system books the flight as HM (required status) when the booking class is configured as required or when the spaces requested exceed the number of places for groups PNRs.

back to top

Waiting list request

In order to request a waiting list for a specific flight, the format is the following:

0XX4520Y08JUNAEPCORLL1

System response:

  1   XX4520 Y  08JUN TU AEPCOR LL1 14:00   16:45      1   DC9

The only difference between this format and the format to request a confirmed flight is the flight status code. In this case, the status code is LL.   

back to top

Standby list request

In order to request a standby list for a specific flight, the format is the following:

0XX4520Y08JUNAEPCORMM1

  1   XX4520 Y  08JUN TU AEPCOR MM1 14:00   16:45      1   DC9

The only difference between this format and the format used to request a confirmed flight is the flight status code. In this case, the status code is MM.

back to top

Sell from availability

In order to book a flight from an availability request, an availability request for a specific date and routing must be made. The format is the following:

01Y2

  1    XX4520 Y  20JUN SU AEPCOR SS1 14:00   16:45      1   DC9

The response is the same as the direct segment request response. Thus, in the event of requiring confirmed spaces (NN) and the flight being full, if the waiting list is open the system will response also the same.

01Y1LL

01Y1MM

Insert segment sold and unknown arrival segment

When several segments are booked on a PNR, the system orders them chronologically. In the event of adding more segments, the system inserts them and places an asterisk after the item number.

For example:

PNR showing a segment booked for 8JUN:

NO NAMES
 1 XX4520B    8JUN TU AEPCOR LL2  14:00 16:45
NO PHONE

A new segment is then requested for 6JUN:

 1*   XX4512 B  06JUN SU AEPCOR SS2 04:00   05:00      0   DC9

The system reorders the segments and places the segment for June, 6th first and adds and asterisk after the item number:  

NO NAMES
 1 XX4512B    6JUN SU AEPCOR SS2  04:00 05:00
 *** ARNK ***
 2 XX4520B    8JUN TU AEPCOR LL2  14:00 16:45
 NO PHONE

The message *** ARNK ***, inserted by the system automatically, indicates a discontinuity between the arrival and departure time on segments 1 and 2. In the event of adding a new segment for June, 7th, the system shows the following:

  2*   XX4500 K  07JUN MO AEPCOR SS2 08:00   09:00      0   DC9

The system places the new segment on item 2, between the existing segments:

NO NAMES
 1 XX4512B    6JUN SU AEPCOR SS2  04:00 05:00
 *** ARNK ***
 2 XX4500K    7JUN MO AEPCOR SS2  08:00 09:00
 *** ARNK ***
 3 XX4520B    8JUN TU AEPCOR LL2  14:00 16:45
 NO PHONE

In addition, in order to sell a segment the command 0 (cero) can be replaced by SS.

back to top

Segment status codes in the itinerary

Status codes indicate the itinerary segments status on the PNR. There are three types of status: action code, status code and reply code.

Action code

Status used to sell a segment:

Status used by the system to reflect the current segment status:

Status used by airlines to advice that segments has changed.

A message is sent to the PNR and, almost every time, the message is sent to the queues and is highlighted on the PNR.

Once reply codes are found, they must be changed to status codes (HK o HL):

In order to change a segment from reply code to status code the format is the following:

For example:

RP/BUE00XX7 - LINEAS AEREAS XX
 1.1LLENOS/S
 2.1LLENOS/D
 1 XX4144Y   25FEB MI TUCAEP KL2  20:00 21:30

 .1HK

System response:

1. KL => HK

Several status changes can be done at the same time, the format is the following:

.1HK.2KK.3HL

back to top

Change several reply status codes to HK simultaneously

In order to perform this action, the user must be signed in Duty 2.

This format changes, in only one transaction, all the TK, KL, KK status on the PNR to HK status, and at the same time cancel all the UN segments.

The format is the following:

.HKALL

For example:

RP/AEP00XX4 - LINEAS AEREAS XX
 1.C/10-10/GRP GRUPO AGENCIA
 1  XX4112Y 08JUL WE AEPSLA UN10 1900 2100
 2  XX4176Y 08JUL WE AEPSLA TK10 2015 2210
 3  XX1806Y 20JUL MO SLAAEP KK10 1300 2000
TKT/TIME LIMIT
  1 TKT/OK
CONTACTS
  1-AEP +99 (99) 999-9999 LINEAS AEREAS XX
RECEIVED FROM - PAX
AEP.HLP/DESK105 1919/08JUL09   *VCQPCR -H

After entering .HKALL, the system responds:

  1. UN => DELETE
  3. KK => HK
  2. TK => HK

Once the transaction is complete, the PNR shows the following:

1  XX4112Y 09JUL TH AEPSLA HK10 1900 2100
2  XX1806Y 21JUL TU SLAAEP HK10 1300 2000

back to top

Priority waiting list

The priority waiting list has 4 hierarchy levels restricted by duties and keywords (WAITLA, WAITLB). The waiting list levels are the following:

The formats to book a priority waiting list are:

• Direct segment sell:

 04580Y25DECAEPCOR LA 1

System response:

1    XX4420 Y  21DEC TU AEPBRC LA1  12:00   15:15      1   DC9

LA status turns into HL status when the transaction on the PNR is ended, then the PNR history shows the following:

-- HISTORY  *EAYUBJ --
AS XX4420Y   21DEC WE AEPBRC LA/HL1  12:00 15:15
HDQ.BUEXX-MM 1708/25OCT0

• Request from a waitlisted segment on a PNR:

For example:

RP/BUE00XX7 - LINEAS AEREAS XX
 1.1MAQUEZ/ANIBAL
 1 XX4420Y   21DEC MA AEPBRC HL1  12:00 15:15
TKT/TIME LIMIT
  1.TX HDQ 2355/04 NOV-THU
CONTACTS
  1-BUE 4567 1256
RECEIVED FROM - PAX
HDQ.BUEXX-MM 1655/25OCT04   *UPRQKE

The format to request the priority waiting list is:

For example:

 .1LA

System response:

1. HL => LA

PNR display:

*A
RP/BUE00XX7 - LINEAS AEREAS XX
 1.1MAQUEZ/ANIBAL
 1 XX4420Y   21DEC MA AEPBRC LA1  12:00 15:15
TKT/TIME LIMIT
  1.TX HDQ 2355/04 NOV-THU
CONTACTS
  1-BUE 4567 1256
RECEIVED FROM - PAX
HDQ.BUEXX-MM 1655/25OCT04   *UPRQKE

*The segment status is now LA.

After ending the transaction, the PNR displays the following:

RP/BUE00XX7 - LINEAS AEREAS XX
 1.1MAQUEZ/ANIBAL
 1 XX4420Y   21DEC MA AEPBRC HL1  12:00 15:15
TKT/TIME LIMIT
  1.TX HDQ 2355/04 NOV-THU
CONTACTS
  1-BUE 4567 1256
RECEIVED FROM - PAX
HDQ.BUEXX-MM 1655/25OCT04   *UPRQKE -H

*The segment status is booked in HL.

PNR history display

-- HISTORY  *UPRQKE --
MS XX4420Y   21DEC WE AEPBRC HL/LA/HL1  12:00 15:15
HDQ.BUEXX-MM 1701/25OCT04  

*The PNR history shows how the priority status change was done.

Priority waiting list request options

There are easier formats to request a waiting list segment. The following is a comparative chart between requests and duties or keywords:

The format to reorder the segments is the following:

/2/1

Description:

The previous example shows the original segment 2 changing into segment 1, and segment 1 changing into segment 2.

If the format is entered correctly, the system responds OK.

This format is not stored in the PNR history.

back to top

Name field

In order to create a PNR, the name field must be completed. The system stores a total of 99 passengers, including adults, children or infants.

Adult passenger

The format to store a passenger name on the PNR is the following:

For example:

-NIETO/JORGE

System response:

OK

Several passenger names can be stored at one time:

back to top

Passenger Type Code in the field name

Passenger Type Code must be entered in the name field so that the passenger can qualify for that specific discount type.

The command to detail the PTC is as follows:

-PEREZ/JUAN YTH

 Different passenger types codes or PTC can be specified in the following way:

-3PEREZ/JUAN YTH/PEDRO ADR/LUIS CHD

Response:

 1.1PEREZ/JUAN *YTH
 2.1PEREZ/PEDRO *ADR
 3.1PEREZ/LUIS  *CHD

Every PTC will be displayed after each name after the asterisk

You can specify different PTC and Identity Document in the same command as follows:

Three Different passenger type examples:

-3PEREZ/JUAN YTH.PP45879/PEDRO ADR.PP87788/LUIS CHD.PP110011

Response:

1.1PEREZ/JUAN *YTH   »PP45879
2.1PEREZ/PEDRO *ADR   »PP87788
3.1PEREZ/LUIS  *CHD   »PP110011

FOID (Form of identification)

ID card number (DNI) can be entered together with the passenger name. The format to do so is the following:

or

FOID types

FOID types are the following:

For example:

 -GOMEZ/PABLO.PP123456789 o NMGOMEZ/PABLO.PP123456789

INVALID FOID LENGTH - BETWEEN 1 AND 25 CHARACTERS ACCEPTED

INVALID FOID TYPE - PLS CHECK http://www.kiusys.com/docs/foid VALID OPTIONS ARE:
PP PASSPORT NUMBER
NI NATIONAL IDENTITY NUMBER
ID LOCALLY DEFINED ID NUMBER

back to top

More common FOID types

The more common FOID types are:

• PP: Passenger passport number

For example:

 -LOPEZ/MARTIN.PP12345678N

• NI: Identity card number (in Argentina: “DNI”, “CI”, “CED”, although these abbreviation signs are not accepted by the system).

For example:

-LOPEZ/MARTIN.NI7896541

• ID: Locally defined identity number (any ID type proving identity).

For example:  

NM1LOPEZ/MARTIN.ID45889633

back to top

Other FOID types

There are other FOID types allowed by the system, which are not common but are accepted:

• CC: Credit card number (the format includes the credit card type -two letter code- and the credit card number.

For example:

-PEREZ/CARLOS.CCVI42424242424242

• DL: Driver license number.

For example:

-PEREZ/CARLOS.DL78564521

• TN: Ticket number.

For example:

-PEREZ/CARLOS.TN9992200036750

• CN: Record locator.

For example:

NM1PEREZ/CARLOS.CNQRMUNP

back to top

How to add a FOID in other GDS PNR

KIU system allows the user to include a FOID to PNRs created by other GDS travel agencies, then the airline can issue the ticket.

The format is the following:

For example:

4FOIDXX/PPAR123456/P1

or:

For example:

SRFOIDXX/PPAR123456/P1

In order to enter the FOID for an infant passenger, the format is the following:

 SRFOIDXX/PPAR123456789INF/P2

back to top

Date of birth (DOB)

The format to enter the DOB is the following:

-GOMEZ/DANIELA.DNI 25820362/19APR74

The format is DDMMMYY and it has to be separated by a slash (/).

When entering a FOID, a slash must be placed after.

back to top

Minor passenger (CHILD)

When entering a child passenger into the PNR the name field must include CHD:

There must be a space between the passenger name and CHD indicator. Once the format is entered, the system responds OK and shows next to the child’s name *CHD:

-ALMENDRES/JUAN  *CHD

 back to top

For example:

-CASARES/MARTIN CHD CHD

 back to top

Infant passenger

The format to add an infant passenger to the PNR includes the indicator INFOA.

The format is the following:

Once the format is entered, the system responds OK and shows next to the baby’s name *INFOA:

-ALBOM/JUAN  *INFOA

On the contrary, the system responds:

PREVIOUS PSGR MUST BE ADT

In order to add an infant passenger to the PNR, the infant has to be link to an adult passenger. The format is the following:

-I/GOMEZ/PEDRO.DNI 787878*P1

Description:

If the passenger to which the infant is linked (*P1) does not exists or is a CHD or an INF, the system does not add the INF to the PNR and responds the following:

ITEM NOT FOUND

 -GOMEZ/DANIELA.DNI 25820362/19APR74

Infant with seat

The format to add an infant occupying a seat is as follows:

Once the format is entered, the system responds OK and displays the PTC INS on screen:

-MILES/PETER  *INFOA *INS

 back to top

Name field variants

Name field changes

The passenger last name, first name or both can be changed.

In order to make a change on an existing PNR name field, the user must be signed in keyword CHGNAM.

At the moment the PNR is created, such keyword is not required. The format is the following:

Passenger PEREZ/WALTER to PRADO/WALTER:

back to top

How to delete a passenger from a PNR

A passenger can be deleted from a PNR:

back to top

Contact field

Phone field

All the necessary contact information (address, phone number, etc.) is entered on this field. After the set command, the text is free.

The system allows a total of 99 fields and 127 characters per field.  The field is named CONTACTS.

The format to add contact information to the PNR is the following:

9BUE 4555-8989-H

The system responds showing the contact information added to the PNR.

In the event of adding a city which is not the city to where the contact belongs, the system uses the city on which the user is signed as city of origin.

Also, if the user enters the format 9 only, the system adds by default the contact information from the office generating the PNR (if configured).

If an "@" is entered in the normal 9 or AP  the system will request to  add  the correct entry for contact email ( 9E or APE) and an error message will be displayed  INVALID FORMAT - FOR EMAIL 9E-MAIL@MAIL.COM OR APE-MAIL@MAIL.COM

E-MAIL

An email address can be used as contact information.

The format is the following:

 9E-WPROCOC@HOTMAIL.COM

The system shows the following information on the PNR:

MAILTO:WPROCOC@HOTMAIL.COM

The system creates a link in order to send emails to that email address by clicking on it.

Address Field (9A-)

In order  to add an address or several according to the airline needs the following entries must be done.

9A-110 LOMBARD STREET /SAN FRANCISCO/CA/US/99100
110 LOMBARD STREET/SAN FRANCISCO/CA/US/99100

Description:

110 LOMBARD STREET

DIisplay in PNR:

CONTACTS
  1-A-SAN MARTIN 140 P13/BUENOS AIRES/BUENOS AIRES/AR/1004

Changes on the contact field

The steps are similar to the steps to change the passenger name.

For example, if the contact added is BUE 5371 1111, then: change BUE 5371 1111 for SLA 4316000

91 ø SLA 4316000

 91,3,5-7 ø

back to top

Time Limit/Ticket

This field shows the PNR time limit or the ticket number. These fields are mandatory and are identified on the PNR as TKT/TIME LIMIT.

Time Limit

The time limit is cancelled automatically or can be cancelled manually. For fares with a pre-established time limit use the following format:

Automatic cancellation:

8X1800/30SEP

The system responds:

TKT/TX HDQ 1800/10APR-SA

Manual cancellation:

81800/30SEP

TKT/TL HDQ 1800/10APR-SA

10 minutes automatic cancellation:

8X

Time limit cancellation options

Time limit can be set by the day of departure of the first segment or by the date on which the PNR was created, by hours or days:

By the date on which the PNR was created or modified

8+1D

8+12

By day of departure of the PNR first segment

8-1D

8-12

Time limit cancellation options by city and time

Time limit cancellation can be set by indicating the city on which the PNR is created so as the system to use the indicated city time as time limit. The time limit format adds /citycode:

8X1800/20JUL/MIA

Changes to the time limit

Changes to the time limit field are made by entering a new time limit, which automatically delete the previous one.

ManualTicket

The electronic ticket (e-ticket) and the stock control procedure are described on their respective manuals. The format to introduce the ticket number manually to the PNRis the following

7T 429 4210 565756

2.6.6 Changes to the ticketing field

Changes to the ticketing field are made by introducing a new ticket number, and this action automatically deletes the previous ticket. In order to introduce a ticket number on a PNR with a set time limit, the user must enter the ticket number. The time limit is deleted automatically. Likewise, to introduce the time limit on a PNR with a ticket number, the user must enter the time limit.

Receive from field

This field identifies the person who requests the creation of the PNR or a change on the PNR. After the set command, the text is free.  The field name is RECEIVED FROM.

The format is the following:

6JORGE

The name of the passengers on the PNR can be used to complete the received from field using the the following format:

Optional Information and comments REMARKS

• In this field, the user can add all additional information or comments considered important.
• After the set command the text is free.
• The system stores a total of 127 fields of 127 characters each.
• The name of this field is REMARK FIELD.

Description:

Changes on the remark field

The procedure is similar to the procedure to make changes on the contact field. Below, there is an example using 5VIP PASSENGER:

51 ø VIP PASSENGER TEXTIL COMPANY

Description:

Entry IE

The command for comments that need to be included in IE (Itinerary Voucher) is as follows:

or

Description:

Example:

5I.PLEASE BE AT THE AIRPORT 3 HOURS BEFORE YOUR FLIGHT DEPARTS

or

RMI.PLEASE BE AT THE AIRPORT 3 HOURS BEFORE YOUR FLIGHT DEPARTS

Response:

ITINERARY RECEIPT - PLEASE BE AT THE AIRPORT 3 HOURS BEFORE YOUR FLIGHT DEPARTS

Passenger Asociation

To associate a comment to a particular passenger, you must enter it as follows:

Description:

INVALID - MAXIMUM PERMITTED 9 PAX PER TRANSACTION

Flight Segment Asociation

To associate a comment to a particular flight segment, you must enter it as follows:

Description:

INVALID - ONLY ONE SEGMENT PER TRANSACTION IS ALLOWED

Passenger and Segment Asociation

To associate a comment with a passenger and a particular flight, you must enter:

Description:

INVALID - MAXIMUM PERMITTED 9 PAX PER TRANSACTION

INVALID - ONLY ONE SEGMENT PER TRANSACTION IS ALLOWED

Example:

5I.PLEASE BE AT THE AIRPORT 3 HOURS BEFORE YOUR FLIGHT DEPARTS/P1-3/S1

RMI.PLEASE BE AT THE AIRPORT 3 HOURS BEFORE YOUR FLIGHT DEPARTS/S2/P2,4,5

Delete

To delete a comment for IE, it must be done in the same way that comments entered with field 5 or RM are deleted:

or

Update

To modify a comment for IE, it must be done in the same way that comments entered with field 5 or RM are modified:

or

Historia

The comments entered to be shown in the IE will also be displayed in the history of the reservation, putting the text "ITINERARY RECEIPT" before the text entered by the user.

Example:

*HRM
-- HISTORY REMARK *IRCASA --
ARM ITINERARY RECEIPT-BE AT THE AIRPORT 3HS BEFORE YOUR FLIGHT
ARM ITINERARY RECEIPT-COMPLIMENTARY VEGAN MEAL-1BOLT/PETER
     /XX803 Y 25AUG MADBCN
ARM ITINERARY RECEIPT-FREE ACCESS TO VIP LOUNGE-1MILES/A
     /XX060 Y 20AUG LHRMAD
AEP.AEPXX-JF 2032/06APR20

Reservation Display

When you enter a comment for IE, it will be shown in the REMARKS section of the PNR, under a title called ITINERARY RECEIPT.

IE (Itinerary Receipt)

When printing or emailing IE, comments entered as 5I or RMI will be included, first showing general comments for all passengers, and then individual comments for each flight.

Example:

External Record Locator (Tour Operator)

This type of codes are provided by Tour Operators when creating a PNR belonging to allotments, from their own systems.

The allotment is a negotiated space between the airline and a tour operator. The allotment is a sub-inventory within the general flight inventory.

This type of remarks are mainly created automatically through APIS, but it is also possible to add them manually by entering the following command:

Description:

Example: 5K.ERLOC/A776-ABC123456

RP/AEP00XX4 - LINEAS AEREAS XX
 1.1BOLT/MIKE   »NI123456
 1  XX060 Y 20DEC SU LHRMAD HK1   1000 1400
TKT/TIME LIMIT
  1 TKT/OK
CONTACTS
  1-LHR 123456
REMARKS
   KIU ALLOTMENT
  1.ERLOC/A776-ABC123456
AEP.KIUHELPJF 1333/17NOV20   *GHJUFI

End transaction format

This format allows the user to end and store the transaction on the PNR. Once ended, the system response is the PNR record locator.  The format can be used to create a new reservation or to store any change made on an existing PNR.

To end and store the PNR, the format is the following:

E

To end, store and re display the PNR, the format is the following

ER

Ignore format

This format is used to ignore any changes made to the PNR or to create a new reservation. The format works if used before ending or storing the transaction (E o ER). The format is the following:

To ignore changes or ignore a PNR:

I

To ignore and re display the PNR:

IR

Multiple data entry format

Passenger data can be introduced to the PNR using one format only.

This format can be configured on the system (check General Information Manual) or used when creating a PNR by pressing SHIFT + ENTER:

Example:

-PEREZ/JUAN¶
04500Y20AUGAEPCORNN1¶
9BUE 5371 1111¶
81800/14AUG¶
6PAX¶
ER

Response:

RP/BUE00XX7 - LINEAS AEREAS XX

 1.1PEREZ/JUAN

 1 XX4500Y   20AUG VI AEPCOR HK1  08:00 09:00

TKT/TIME LIMIT

 1.TL BUE 1800/14AUG-SAT

CONTACTS

  1-BUE  5371 1111

RECEIVED FROM - PAX

BUE.BUEXX-MM 1717/12AUG04   *JIRSVS

If some information is introduced incorrectly, the system only stores the information entered correctly.

PNR ownership release

PNR ownership can be released to a different airline or office/agency so they  can work on the PNR. It is important to note that, a PNR created by a specified airline cannot be open by a different airline unless such PNR has segments operated by said airline.

Then, the PNR ownership release function is used to cede the control of the PNR control to another airline.

The format is the following:

RP/CTY00XX1

For example:

RP/BUE00XX7 - LINEAS AEREAS XX

 1.1FERRER/AMALIA

 1 XX4444Y   23JUL VI CORAEP HK1  13:00 14:05

TKT/TIME LIMIT

 1.TL BUE 1800/12JUL-MON

CONTACTS

  1-SIN  CTC

RECEIVED FROM - PAX

BUE.BUEXX-MM 2007/29JUN04   *SPGZKF

The user introduces the format to cede the control of the PNR to MJRA1110. The system response is OK:

RP/MJRA1110

OK

Then, when opening the PNR, the PNR ownership release:

RP/MJRA1110 - PANDA VIAJES

 1.1FERRER/AMALIA

 1 XX4444Y   23JUL VI CORAEP HK1  13:00 14:05

TKT/TIME LIMIT

 1.TL BUE 1800/12JUL-MON

CONTACTS

  1-SIN  CTC

RECEIVED FROM - PAX

BUE.BUEXX-MM 2007/29JUN04   *SPGZKF

Modify inventory from a PNR

The booking class on a PNR can be changed without the need to display the availability for a flight or to sell a new segment. The SB command modifies the itinerary booking class or the number of seats sold (add or reduce) on a PNR.  

This transaction cancels (X) the unwanted segment and book (0) a new segment on the desired booking class.

Modify seat/inventory in a specific segment

This formats changes the number of seats sold and the booking class in a specific segment:

SB1V2

 

It is important to bear in mind that, the segment is confirmed only if there are spaces available on the flight. If there are no spaces available but the waiting list is open, the system books the segment on the waiting list. If the waiting list is closed, the system does not sell the segment.

The format to waitlist a passenger is the following:

SB1B2LL
 

These formats cancel the unwanted segment and the booking class and, then, sell a new segment on a new booking class. The transaction is shown in the PNR history: XS indicates that a segment has been cancelled and AS indicates that a new segment has been booked (see PNR history).

Modify seat/inventory for the entire itinerary

This format changes the number of seats sold and the booking class for the entire itinerary:

SB1Y 

Modify inventory for a specific segment

This format changes the booking class for a specified segment:

SBY1

Modify inventory for the entire itinerary

This format changes the booking class for the entire itinerary:

SBY

Error messages

• ERROR OCCURRED-CHECK ITIN OR IGNORE WITH IR

One or more segments on the PNR cannot be modified using the SB format.

• [ID] NOT FOUND

One or more segments on the PNR do not exist or are in HM or MM status.

• CHECK ITIN

The SB format does not indicate the segment number or one or more segments on the PNR are in HM or MM status. 

PNR cancellation

Manual cancellation

In order to cancel a reservation (PNR), the user must cancel the itinerary. The other fields remain in the record locator for 48 h. The format to cancel the itinerary is the following:

X1

The entire itinerary can be canceled using the following format:

XI

Several segments can be canceled at the same time using the following format:

X1-3,5                    cancel segment 1 to 3 and segment 5

Also, several segments in UN status can be canceled at the same time using the following format:

XU

Automatic cancellation

The system cancels automatically the segments configured to be cancelled automatically. The segments are deleted from the itinerary and shown in the PNR history. Also, these segments are sent to queue 5 of the city in where they were booked.

The history shows the canceled segment with an indicator:

SYS-TX 1838/26JUL18 

Description:

Redisplay PNR or fields

In order to redisplay a PNR, the format is *A o RT.

Also, fields can be redisplayed separately using the following formats:

*N                                                         Name

*I                                                         Itinerary

*K                                                         Ticket or time limit

*F                                                         Fares

*J                                                         Contact

*R                                                         Remarks

*O                                                         Special services (SSR)

If the PNR is being modified when the user redisplays it, the system shows the following message:

*** UPDATE MODE ***

Automated pricing

 Basic pricing

Basic pricing format stores the price quote (fare applicable) to future issuance of the ticket. In order to price the PNR, the itinerary must be displayed on the screen. It is important to note that, once the PNR is priced, the transaction must be stored using E or ER.

The format to automatically price all the segments and passengers is the following:

WS

For example:

Pricing by passenger

This format is used to price a specified passenger:

WS*N1

Also, this format price many specified passengers at the same time:

Pricing different passenger types

This format is used to price different passenger types at the same time or separately. This allows the user to price and existing PNR without considering the passenger type.

The format to price a specified type of passenger is:

WS*PCHD1

The format to price several type of passenger is:

WS*PADT.CHD2.INF

For example:

This format forces the pricing to get 2 CHD fares and 1 ADT fare, but as on the PNR there are 2 ADT, the system prices 2 ADT.

Also, the format to price the itinerary without selecting passengers is: 

WS*1.1.1

The order in this format is the following: ADT CHD and INF.

The system does not price a specified passenger type if a 0 command or none command are entered. For example:

WS*1..1                Passenger type CHD is not priced

WS*1.1                 Passenger INF is not priced

WS*..1                   Only INF passenger is price

Also, the following format can be used in the same way as the previous one:

WS*P1.1.1

5 Pricing including discount

When pricing, the user can apply a discount to the fare basis published.

If a fare has a discount, for example CHILD fares which are adult fares with a prearranged discount, the system prices the new discount on top of the CHILD discount.

The format is the following:

WS*Q/AD90/DP90

WS*Q/AD90/DP90X

WS FARE NOT GUARANTEED UNTIL TICKETED PASSENGER TYPE FARE (IN ARS) TAX FEE PER PSGR 1. TEST/UNO YTH 150.00 79.18 0.00 229.18 TOTALS 1 150.00 79.18 0.00 229.18 AIRLINE FORM OF PAYMENT FEES MAY APPLY PRICED WITH VALIDATING CARRIER XX

WS
FARE NOT GUARANTEED UNTIL TICKETED
     PASSENGER           TYPE       FARE (IN ARS)          TAX        FEE       PER PSGR
  1. TEST/JOVEN           YTH              150.00        79.18       0.00         229.18
  2. TEST/PEQUE           CHD*YTH          105.00        72.22       0.00         177.22
                   TOTALS   2              255.00       151.40       0.00         406.40
AIRLINE FORM OF PAYMENT FEES MAY APPLY
PRICED WITH VALIDATING CARRIER  XX

WS
FARE NOT GUARANTEED UNTIL TICKETED
     PASSENGER           TYPE       FARE (IN ARS)          TAX        FEE       PER PSGR
  1. TEST/JOVEN           YTH              150.00        79.18       0.00         229.18
  2. TEST/PEQUE           CHD*YTH          150.00        79.18       0.00         229.18
                   TOTALS   2              300.00       158.36       0.00         458.36
AIRLINE FORM OF PAYMENT FEES MAY APPLY
PRICED WITH VALIDATING CARRIER  XX

 1.1TEST/UNO *GOV   »PP003388
 2.1TEST/DOS  *CHD   »PP223344
 3.1TEST/TRES *YTH   »PP3344

WS
INVALID - MULTIPLE PTC PRESENT IN PNR

WS*N1-2
FARE NOT GUARANTEED UNTIL TICKETED
     PASSENGER           TYPE       FARE (IN ARS)          TAX        FEE       PER PSGR
  1. TEST/UNO             GOV              180.00        83.82       0.00         263.82
  2. TEST/DOS             CHD*GOV           72.00        67.11       0.00         139.11
                   TOTALS   2              252.00       150.93       0.00         402.93
AIRLINE FORM OF PAYMENT FEES MAY APPLY
PRICED WITH VALIDATING CARRIER  XX   

WS*Q<base fare>

For example:

WS*QVAP10

The fare basis can be forced by segment, taking into account the RBD in which is booked and the fare restrictions.

The formats to price an itinerary using a specified fare basis always include *FC<fare basis> and are the following:

To price the entire itinerary:

WS*FB/<farebasis>

		

WS*FB/<farebasis>-<farebasis>-<farebasis>

WS*FB/<farebasis>.<farebasis>.<farebasis>

WS*Rcitycode

WS*RMVD

WS/Currencycode

WS/USD

WS*TX12QN/32.50DL

WS*TXEX

WS*TX+12QO/56.50AR

WS*TX-XR/DL

WS*TX+12QO/56.50AR/- XR/DL

TCODE/*

TCODE/*H

WS*CQ35

WS*CQEX

WS*D<date>

WS*N1*S1*QY/AD50/DP50

WS*NF

Group PNRs

As individual PNRs, group PNRs can be divided, the only difference is that in group PNRs there are passengers and booked spaces. The formats are the following:

In the following example, 8 spaces are divided from the original PNR, items 2 to 4, 6 and 9 (passengers) and other 3 booked spaces.

For example:

In the new PNR, the number of booked spaces and passengers is updated. The following steps are the same as in individual PNR division.

In order to divide booked spaces only, the format is the following: 

DC15

Reduce PNR

The number of passengers on a PNR can be reduced. First, the user must retrieve the PNR, then cancel the desired passenger and finally, reduce the number of spaces booked.  

The format to reduce the passenger number on a PNR is the following:

,2                   Set command to indicate reduction + number of spaces to be cancelled

Then, the PNR must be ended (E or ER).

For example:

RP/BUE00XX0 - LINEAS AEREAS XX

 1.1GENTILCORE/S

 2.1SERRANO/V

 3.1CASAIS/V

 1 XX4580Y   22SEP TH AEPCOR HK3  18:00 19:05

TKT/TIME LIMIT

  1 TL BUE 1800/30AUG-TUE

CONTACTS

  1-BUE 5371 1151

RECEIVED FROM - MARIANO

BUE.BUEXX-MM 1810/24AUG05   *UXVWEK

In order to delete passenger number 3 the format is:

-3ø

System response:

OK

Then, to reduce the number of spaces booked, the format is the following (Note that: the number to be reduced is the number of spaces that remains on the PNR):

,2

System response:

OK

Then, the system displays the following:

RP/BUE00XX0 - LINEAS AEREAS XX

 1.1GENTILCORE/S

 2.1SERRANO/V

 1 XX4580Y   22SEP TH AEPCOR HK2  18:00 19:05

TKT/TIME LIMIT

  1 TL BUE 1800/30AUG-TUE

CONTACTS

  1-BUE 5371 1151

RECEIVED FROM - MARIANO

BUE.BUEXX-MM 1810/24AUG05   *UXVWEK -H

The example shows how the PNR passengers are reduce from 3 to 2. First, the third passenger is eliminated and then the spaces booked are reduced to 2.

Increase PNR

The number of passengers on a PNR can be increased. The steps are the following: 

1)           Display PNR

*WWLOHA

RP/BUE00XX7 - LINEAS AEREAS XX

 1.1CATRELLI/ANA

 1 XX4520Y   22AUG DO AEPCOR HK1  04:00 05:10

TKT/TIME LIMIT

 1.TL BUE 1800/12AUG-THU

CONTACTS

  1-BUE 4555 1243

RECEIVED FROM - PAX

BUE.BUEXX-MM 1831/28JUL04   *WWLOHA

2)           Introduce passenger name

-FABRINI/JULIA

3)           Booked the desired segments

SB2Y1

1  XX4520 Y  22AUG SU AEPCOR SS2  04:00   05:10      0   J32

4)           End and store transaction

ER

RP/BUE00XX7 - LINEAS AEREAS XX

 1.1CATRELLI/ANA

 2.1FABRINI/JULIA

 1 XX4520Y   22AUG DO AEPCOR HK2  04:00 05:10

TKT/TIME LIMIT

 1.TL BUE 1800/12AUG-THU

CONTACTS

  1-BUE 4555 1243

RECEIVED FROM - PAX

BUE.BUEXX-MM 1831/28JUL04   *WWLOHA -H

The format ADN is used:

RP/AEP00XX4 - LINEAS AEREAS XX

 1.1ARDERIO/A

 1 XX4500Y   22MAY SU AEPCOR HK1  07:50 09:00

TKT/TIME LIMIT

  1 TKT/OK

CONTACTS

  1-BUE 565671112

REMARKS

  1.»» SPLIT BY BUE.BUEXX-MM 1905/05APR05-XQAOUL

BUE.BUEXX-MM 1905/05APR05   *VTKZZY -H

ADN

XQAOUL - 3 CARRO/A - CORMEL/A - PROCFIO/W

     » NQCEYF - 1 ALVES/A

           » GUXPID - 1 ROMEL/A

     » KFHZST - 1 BUESTER/A

           » GCIIOS - 1 PERES/C

           » DLBIJG - 1 COMINGES/A

     » VTKZZY - 1 ARDERIO/A

PNR history

All the changes made to the PNR are stored in the PNR history, and the sign of the agent who performed the change, the date and the time on which the change is made are detailed.

 If the PNR has a history stored, the system displays the -H indicator next to the record locator.

 The format to open and read the PNR history is:

*H

If the user presses the indicator –H using the mouse left button, the system opens a window containing the PNR history. By pressing ESC or CLOSE BUTTOM, the system closes the window. Then, by pressing CTRL + LEFT BUTTOM, the system displays the PNR history.

For example:

PNR: *ESZSAG

RP/BUE00XX0 - LINEAS AEREAS XX

 1.1NIETO/JORGE

 2.1HERRAIZ/FLOR

 3.1NIETO/OLIVIA  *CHD

 4.1HERRAIZ/JULIETA  *INFOA

 5.1NIETO/ANA  *CHD

 1 XX4580B   22SEP TH AEPCOR UN4  19:45 21:00

 2 XX4580B   22SEP TH AEPCOR TK4  18:00 19:05

TKT/TIME LIMIT

  1 TKT/-000 2353323627/1/32/4

CONTACTS

  1-BUE 56532654

  2-BUE  7877878

REMARKS

  1.CHEQUEAR DOCUMENTACION

RECEIVED FROM - JORGE

HDQ.HLP/DESK101 1752/24AUG05   *ESZSAG –H

History:

*H

-- HISTORY  *ESZSAG --

AN 1HERRAIZ/JULIETA  *INFOA

HDQ.AEPXX-AB 1752/24AUG05   

AS XX4580B   22SEP TH AEPCOR SS/HK4  19:45 21:00

XS XX4580Y   22SEP TH AEPCOR    HK3  19:45 21:00

AN 1NIETO/ANA  *CHD

RF JORGE

HDQ.AEPXX-AB 1752/24AUG05   

APH  7877878

ARM CHEQUEAR DOCUMENTACION

XTL TL HDQ 1800/30AUG-TUE

ATK -000 2353323627/1/32/4

RF FLORENCIA

BUE.AEPXX-AB 1754/24AUG05   

SC XX4580B   22SEP TH AEPCOR HK/UN4  19:45 21:00

AS XX4580B   22SEP TH AEPCOR SS/TK4  18:00 19:05

SYS-SC 1755/24AUG05

Description:

The PNR history must be read from the top to the bottom, from the oldest changes to the latest. Changes indicators are the following:

The following fields may be in the PNR history next to the indicator:

SP field indicating name field division does not have an indicator.  

PNR queue history

In order to open and read a PNR queue history, the formats are the following:

PLACED ON                                         

REMOVE FROM                                  

The queue history displays all the changes occurred in the PNR within the company queues. In order to check the changes within other companies’ queues, the user must be signed in keyword QHSHOW.

The format is the following:

*QH

Example

-- QUEUE HISTORY  *ESZSAG --
PLACED ON    XX.HDQ (30)  BY SYS 1755/24AUG05
PLACED ON         colocado en 
XX.HDQ (30)       empresa, ciudad y número de cola
BY SYS            agente
1755/24AUG05      hora y fecha
PLACED ON    XX.BUE (201)  BY AEPXX-AB 1755/24AUG05 

Partial history

The user can display only specified fields of the PNR history without the need to display the entire history.   

The formats for each field are: 

KNS movements history- KIU Notification Service 

Actions taken by the KNS notification service can be viewed by executing the following command with a PNR previously displayed:

*KNS

Response:

*KNS
-- KSN PROCESS HISTORY  --
MAIL (MAILPAX@MAIL.COM} GENERAL MESSAGES/24HS BEFORE DEPARTURE XX4505/13APR PTYBOG
  13APR20/1605Z

Description:

• Shipping method:  email or SMS
• Shipping address: email or phone number where the notification was sent
• Function: KNS function used to trigger the shipping
• Sub-function: template used for submission
• Flight/Segment: processed flight information
• Date and time: record when the shipment was executed, expressed in GMT

If there are no movements for the PNR, the system will respond:

NO HISTORY

PNR Retrieval

External Record Locator (Tour Operator)

A PNR can be retrieved in KIU using an external record locator provided by the system used by Tour Operators. 

These external codes are used when the airline has created allotments and the Tour Operator, that owns that allotment, uses its own reservation system, where a code is assigned to each reservation.

Once the Tour Operator interacts with KIU, the PNR is created and the external record locator is associated in the Kiu PNR.

The airline, the travel agency through Kiu GDS, and the passenger through the airline's site, can retrieve the PNR created in KIU, using the external record locator.

Example: *ERLABC123

PNR Purge

A PNR is purged 48 hours after the start date of its last segment, whether that segment was canceled or not.

Once the PNR is purged, it can be viewed by retrieving it with the SEARCH command.

The PNR purge date can be modified by entering an SSR OTHS as follows:

Example: 4OTHS/PURGE/20DEC

The PNR will show that the PNR purge was postponed according to the date entered in the SSR:

RP/AEP00XX4 - LINEAS AEREAS XX
1.1MILES/JOHN »NI12345
1 XX060 Y 11NOV WE LHRMAD HK1 1000 1400
TKT/TIME LIMIT
1 TKT/OK * 10NOV20/AEPXX-JF
2 TKT/ET 9990210024993 * 10NOV20/AEPXX-JF - MILES/J.
FARE - PRICE RETAINED
CONTACTS
1-AEP 11223344 LINEAS AEREAS XX
SSR
1 OTHS YY HK PURGE POSTPONED UNTIL 20-DEC-2020 
RECEIVED FROM - PAX
AEP.KIUHELPJF 1758/10NOV20 *JLNVLT -H

Passenger list

Confirmed passengers

The format to request a confirmed passenger list using the routing and flight number is the following;

LD FLIGHT NUMBER/DATE

For example:

LD21/20SEP

System response:

Description:

First, the system displays the flight details: 

Then, for each city pair the system describes the following:

*In this column the options are the following:

LD4420/22JULAEP         	Request by departure airport
LD4420/22JULAEPBRC    	    Request by flight segment

LDA1                                                     1 indicates the item number on the availability request

LDP1                                                     1 indicates the segment number on the availability request

T                      Passenger PNR including ticket number: LD4420 / 22JUL / T
V                      Passenger PNR including time limit: LD4420 / 22JULALL / V
C                      Passenger PNR booked in a specific booking class, which has to be specified after C indicator: LD4420 / 22JUL / CY. Several booking classes can be specified (one after the other).
K                      Confirmed passengers only
M                      Standby passengers only
P                      Passenger type (PADT for adult, PCHD for child, PINF for infant): LD4420 / 22JUL / PADT
US                     (user id) PNR creator (agent sign): LD4444 / 20MAR / USMAD00XXPD

LD4100/10JULALL/R17MAR   

Using return date

/F

Using FOID

/ET

Using e-ticket

/OF

Using PNR owner office

/OFAEP00XX2

 Using specified office

/FF

Using frequent flyer number

../US

 Using PNR creator

R(3)4667Y2SEPBRCAEPHK

LD4100/20JULALL/T/CY

LW4420/22JUL                                  displays waiting list passengers

LX4600/15APR

LRFLIGHTNUMBER/DATE

LK FLIGHT NUMBER/DATE

LK<flight>/<date> * office

LK49/25NOV*MVDM6320

LK90/13NOVAEPJUJ

LTFLIGHT NUMBER/DATE

LT4500/12JAN-EXCEL

LT4500/12JAN/FB-FARE BASIS

To this command is posible to add the extension -EXCEL.

LL FLIGHT NUMBER/DATE<origin>

LL FLIGHT/DATE # NUMBER OF PNRS

LL4420/22DECAEP-EXCEL

LL4420/22DEC-QAEP215

LG FLIGHT NUMBER/DATE

LI FLIGHT NUMBER/DATE AIRPORT

This list allows to view the reservations created on the airline's website, and whose tickets were not issued for any reason.

The reasons why tickets have not been issued can be:

• Some error in the payment gateway process
• Option "Pay Later"

Commands

Basic

The transaction, or basic command, to generate the list is as follows:

Description:

Display:

Detail:

• The name of the list and date of creation of the bookings are displayed at the top.
• In section OFFICES INCLUDED, the codes of the analyzed web offices will be shown.
• In section STATUS INCLUDED, the different error transaction statuses supported by the payment gateway are shown, and also the option "Pay Later" if implemented.
• Each of the transaction statuses are represented by a number. For example:

1 COMPLETED-REJECTED

2 PAYMENT EXPIRED

3 COMPLETED-EXCEPTION

4 COMPLETED-ERROR

5 PENDING

9 OTHERS

A summary of the number of reservations will be displayed in each transaction status:

Notes:

• PNRs created on the airline's website, whose tickets were not issued, will be listed
• If not entering a date, the system assumes by default, the date of the day
• The reservations created on the day (GMT time) will be listed
• Duty 5 is required to generate the list
• Only active (not purged) reservations will be displayed
• If any modification is required in the transaction status, it must be requested to Kiu
• The list can be exported with ALT + ENTER, or adding -CSV or -EXCEL 
• The list can be sent to queue by adding the extension /-Q
• The system will consider reservations made in any office whose "Stat.Channel" is WEB
• If there is no office configured as WEB, the system will show the error: INVALID OFFICE

The following filters can be added to generate the list:

By Date

To view unpaid reservations on the web on a specific date, the entry is as follows:

Example:

LU22APR

By Office

To view unpaid reservations at a particular office on the Web, the entry is as follows:

The /OF (Office) indicator must be added followed by the office ID.

Example:

LU22APR/OFAEP00XX8

Notes:

• If the office ID does not contain 8 characters, the system will display: INVALID OFFICE
• If the office ID is not configured as a web office, the system will display: INVALID OFFICE

By Transaction Status

To view the unpaid reservations on the Web, organized by transaction status, the entry is as follows:

The /TS (Transaction Status) indicator must be added followed by the transaction status code. The transaction status code is represented by a number:

1 COMPLETED-REJECTED

2 PAYMENT EXPIRED

3 COMPLETED-EXCEPTION

4 COMPLETED-ERROR

5 PENDING

9 OTHERS

Example:

LU22APR/TS1

Combined Filters 

Date, office and transaction status can be combined as follows:

Example:

LU22APR/OFAEP00XX8/TS1

Passenger list (Travel agencies)

LMXX3468/17FEB

LMXX3468/17FEB-Q202

Flight inventory

In order to display a flight inventory, the format is the following: 

VIE FLIGHT NUMBER/DATE ALL                        ALL indicates on the entire flight

Example 1:  Direct flight

Example2:  Flights connecting in two or more cities

Inventory options

By airport

VIE4900/05NOVCOR                                        COR displays segments only from COR.

 

VIE4900/05NOV                                                If the origin city is AEP, there is no need to specified the departure airport.

Note:

If the user requesting the VIE is on the city of origin of the flight, there is no need to enter the airport code in the format. 

From availability

 An inventory request can be display from an availability request using the following format:

VIEA item number

VIEP item number

The system uses the city of origin of the PNR as city of origin of the flight.

Total number of seats sold per cabin

The format used to display the total number of seats sold per cabin shows the partial number of seats booked on each segment and on each cabin, and the total number of seats sold on each leg and each cabin. The format is the following: 

VIL FLIGHT NUMBER/DATE

VIL FLIGHT NUMBER

VIL4520/COR

VLC*FLT                           By flight number (only one flight)

VLC*FLT*FLT                      By flight number (more than one flight)

VLC*FLT/DATE                     By flight number and date (optional/the system by default uses the date on which the request is)

VLC*AEPCOR/02AUG

Unlike the option by flight number, this format displays the column TIME, which indicates that the order of the segments is by time of departure of each flight.

If the user selects the format of every possible flight from any origin to a specified airport/city, the order of the segments is determined by the time of arrival to the destination. 

• By airport:

This format displays departures and arrivals from a specified airport. If no date is entered, the system uses the date on which the request is made by default.

VLC*AEP

Unlike the option by flight segment, this format displays the column ST after TIME column, which indicates if the flight departs (OUT) from the airport requested or arrives (IN) to the airport requested.

Round trip flights will be shown twice, its departure and arrival. In the previous example: flights 4134, 4320 y 4390.

Flight 4390 departs at 2330 and arrives at 0330+1, that is to say, the following day.  This is because the sale date is the date of the request, then the system uses +1 to indicate that the flight arrives on the day after the departure.  

Catering information

This format displays and determines the number of meal services required for a specified flight. The format is the following:

VCC FLIFHT NUMBER/DATE ROUTING

VCCFLIGHT NUMBER                   using the date on which the request is made

 

VCCFLIGHTNUMBER/DATE              specified day

 

VCCFLIGHTNUMBER/DATEBRD           specified date and departing airport

Flight information

This format displays data regarding the operation of a specified flight: 

DO XXFLT/DATE

For example: