23.02.2014 Views

HONG KONG EXPRESS ELECTRONIC TICKETING FOR HKG ...

HONG KONG EXPRESS ELECTRONIC TICKETING FOR HKG ...

HONG KONG EXPRESS ELECTRONIC TICKETING FOR HKG ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>HONG</strong> <strong>KONG</strong> <strong>EXPRESS</strong> <strong>ELECTRONIC</strong> <strong>TICKETING</strong> <strong>FOR</strong> <strong>HKG</strong> ABACUS<br />

Implementation Date 01 Apr 08<br />

Default E-Ticket<br />

E<br />

Yes / 01 Apr 08<br />

Quick Reference<br />

Support Status Code HK-confirmed / RR – Reconfirmed / HL-waitlist / DS - open<br />

At least one confirm segment in UO RLOC for e-ticket issuance.<br />

Require first segment must be the confirmed segment.<br />

Airline cannot receive ticket number when booking contains HK and GK segment<br />

booked on carriers hosted in Travel Sky (3U,CA,CZ,FM,HU,HX,MF,MU,NX,SC,UO,ZH).<br />

Please contact airline for manual ticket number reporting.<br />

Passive Segment Not Supported.<br />

Form of Identification Required & Mandatory.<br />

Entry: 3FOID/-<br />

E.g<br />

3FOID/PP<br />

PPHK664574857-1.1<br />

(PP– FOID code, HK – Country Code, 664574857-Passport No., 1.1- Name field)<br />

<br />

<br />

Please be informed that it is required to input FOID for UO E-Ticket issuance.<br />

Passenger will not be accepted on board if information of FOID does not contain<br />

in PNR & ETR.<br />

Name Field<br />

Requirement<br />

Maximum Name<br />

Characters for E-Ticket<br />

E<br />

Maximum Segments<br />

Multiple E-tkt E<br />

for same<br />

pax in same airline<br />

RLOC<br />

Form of Payment<br />

UO accepted FOID include:<br />

PP - Passport<br />

NI – National Identity<br />

Use passenger full name (same as passport) for Reservation & Ticketing.<br />

Name Spacing : Not allowed at Infant Surname field but Allowed at given name field<br />

Maximum 29 characters for ETR including “/” and space.<br />

Max 4 pax x 2 segments / per E-Ticket transaction<br />

Max 2 pax x 4 segments/ per E-Ticket transaction<br />

Remarks:<br />

Please issue ET separately if more than above limitation. However, ticketing data including<br />

fare calculations, tour code, endorsement will affect e-ticket message size. So, please<br />

ensure e-ticket records are created properly if e-tickets are issued for multiple pax in the<br />

same ticket transaction.<br />

<br />

<br />

Allow multiple ETRs created in UO RLOC with different itinerary.<br />

Require voiding unwanted Electronic ticket prior issue a new E-ticket.<br />

Supported Single & Multiple FOP.<br />

Infant E-Ticket<br />

E<br />

Fare not Supported<br />

Ticket Number<br />

Reporting<br />

Void<br />

Supported.<br />

Nil.<br />

Automatically generated to UO and filed SSR TKNE in PNR history after E-ticket issuance.<br />

Applicable with same day void.<br />

Exchange Support (including ET to ET, ET to Paper & Paper to ET).<br />

Please refer to BSP Quick Reference for carrier preference.<br />

Submission to BSP: original ETR + reissued ETR<br />

Void Exchange<br />

Auto Revalidation<br />

Not Supported.<br />

Please input E-ticket number with indicate Eticket Revalidation request in SSR field as follow,<br />

Entry: 3OTHSx/TKNO 1281234567890-1.1 (where x = segment no., 1.1 – name field)<br />

Entry: 3OTHSx/REQ TO TICKET RE LINK<br />

_________________________________________________________________________________________________________<br />

Last Update: 01-Dec-10 Page 1 of 2


<strong>HONG</strong> <strong>KONG</strong> <strong>EXPRESS</strong> <strong>ELECTRONIC</strong> <strong>TICKETING</strong> <strong>FOR</strong> <strong>HKG</strong> ABACUS<br />

Quick Reference<br />

ETR Retention date<br />

ETR Status<br />

Retention Date<br />

OPEN (unused Available 13 months in system from date of last flight coupon.<br />

ETR)<br />

USED (fully used Stored for 15 days from date of last flight coupon.<br />

ETR)<br />

VOID/EXCH/RFN Stored for 15 days from the last transaction date.<br />

D<br />

E-ticket Refund<br />

Supported and please process with BSP Refund guidelines.<br />

Procedures<br />

Cancel E-Ticket<br />

E<br />

Not Supported.<br />

Refund<br />

Code-share flights Supported<br />

After segment sold: "/E" indicator will be appended<br />

For Non ET sectors: “/N” indicator or blank will be appended<br />

Interline Carrier Supported.<br />

Please refer to WETP*UO for eligible interline carriers.<br />

To successfully issue the interline E-ticket, all flight segment must have an indicator<br />

“/E” at the end of segment sold.<br />

E-Ticket Hotline -----<br />

_________________________________________________________________________________________________________<br />

Last Update: 01-Dec-10 Page 2 of 2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!