New E-ticket Carrier – Royal Nepal Airlines (RA)

13 May 2008
New E-ticket Carrier –
Royal Nepal Airlines (RA)
Dear valued customers,
Abacus is pleased to advise you that Royal Nepal Airlines
(RA
RA) implement Electronic Ticketing (with default E-Ticketing) in Abacus
system on 14 th May 2008. Attached please find RA e-ticket details or you
may refer to Whiz Menu Mask – ET Quick Reference Mask.
Thanks very much for your attention and continuous support.

ROYAL NEPAL AIRLINES ELECTRONIC TICKETING FOR HKG ABACUS
Implementation Date 14 May 2008
Quick Reference
Default E-Ticket E
Carrier Yes / 14 May 2008
Status Code HK-confirmed / RR-reconfirmed / HL-waitlisted / DS-open
At least one confirm segment in RA RLOC for e-ticket issuance
Passive Segment Supported, Carrier RLOC must be added to the GK/GL segment.
E.g. 0RA123Y23NOVHKGKMTGK1*
Ticketing agent has the responsibility to verify correct booking details for passive
segment creation.
Please remember to report E-ticket number to “RA” if using “GK” segment issuance.
Form of Identification Not required.
Name Field Requirement
Maximum Name
Characters for E-Ticket
E
Maximum Segments
Multiple E-tkt E
for same
pax in same airline RLOC
Form of Payment
Infant Ticket
Fare not Supported
Ticket Number Reporting
Void
Use passenger full name (same as passport) for Reservation & Ticketing.
Maximum 31characters for ETR.
Passenger name field is truncated in ETR when over 29 characters.
Maximum 7 passenger per E-ticket transaction.
Maximum 16 segments including surface sector per passenger/E-ticket transaction.
Allow multiple ETRs created in RA RLOC with different itinerary.
Require voiding unwanted Electronic ticket prior to issues a new E-ticket.
Supported Single & Multiple FOP.
Supported
Nil.
Automatically generated SSR TKNE to RA after E-ticket issuance.
Applicable with same day void.
Exchange Supported (including ET to ET, ET to Paper & Paper to ET).
Please refer to BSP Quick Reference for Carrier preference
Submission to BSP: original ETR + reissued ETR
Void Exchange Not Supported.
Auto Revalidation Supported.
Provided coupon is confirmed to confirmed status
Allow change in date and flight only
If revalidation involved rebooking fee, please contact “RA” directly.
Please remember to report (either by call RA or 7T-TK) E-ticket number to “RA” for new
segment or rebooking PNR.
Steps
to revalidate the E-ticket: E
1. Display the PNR e.g. *ABCDEF
2. Display the E-ticket record e.g. WETR*T2851234567890
3. Enter the segment & coupon
number to be revalidated.
e.g. WETRL/S2/C2
(Where S2 = segment 2 in PNR, C2 = coupon 2 in ETR)
Unable to revalidate if:
- Class code /routing changed
- Code-share flights
_________________________________________________________________________________
Last Update: 13-May-08 Page 1 of 2

ROYAL NEPAL AIRLINES ELECTRONIC TICKETING FOR HKG ABACUS
ETR Retention date
Quick Reference
ETR Status
Retention DateD
OPEN (unused ETR) Available 13 months in system from date of last flight coupon.
USED (fully used ETR) Stored for 3 months after the last flight coupon.
VOID/EXCH/RFND Stored for 3 months after the transaction date.
E-ticket Refund
Procedures
Cancel E-Ticket E
RefundNot Support.
Support and please proceed with BSP Refund guidelines.
Code-share flights Supported.
After segment sold: "/E" indicator will be appended.
For Non ET sectors: “/N” indicator or blank will be appended.
Interline Carrier Supported.
Please refer to WETP*RA for eligible Interline carriers.
To successfully issue the Interline E-ticket, all flight segments must have an indicator
“/E” at the end of segment sold.
_________________________________________________________________________________
Last Update: 13-May-08 Page 2 of 2