27.11.2014 Views

SAUDI ARABIAN AIRLINES ELECTRONIC TICKETING FOR HKG ...

SAUDI ARABIAN AIRLINES ELECTRONIC TICKETING FOR HKG ...

SAUDI ARABIAN AIRLINES ELECTRONIC TICKETING FOR HKG ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>SAUDI</strong> <strong>ARABIAN</strong> <strong>AIRLINES</strong> <strong>ELECTRONIC</strong> <strong>TICKETING</strong> <strong>FOR</strong> <strong>HKG</strong> ABACUS<br />

Quick Reference<br />

Implementation Date 21 May 2008<br />

Default E-Ticket E<br />

Carrier Yes / 21 May 2008<br />

Status Code HK-confirmed / RR-reconfirmed / HL-waitlisted / DS-opened<br />

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

Passive Segment<br />

Not Supported.<br />

Form of Identification<br />

Name Field Requirement<br />

Maximum Name Characters<br />

for E-Ticket<br />

E<br />

Maximum Segments<br />

Multiple E-tkt E<br />

for same<br />

pax in same airline RLOC<br />

Form of Payment<br />

Infant Ticket<br />

Fare not Supported<br />

Ticket Number Reporting<br />

Supported. Required for Open segments.<br />

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

Maximum of 58 characters in the surname & given name field for E-ticket.<br />

Abacus displays 31 name characters in ETR.<br />

Maximum 7 passenger per E-ticket transaction.<br />

Maximum 16 segments including surface sector per passenger/E-ticket transaction.<br />

<br />

<br />

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

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

Supported Single & Multiple FOP.<br />

Supported.<br />

Zero Fare not allowed.<br />

Automatically generated SSR TKNE to SV after E-ticket issuance.<br />

Void<br />

Applicable with same day void.<br />

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

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

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

Void Exchange Not Supported.<br />

Auto Revalidation Not Supported.<br />

Please call SV reservation office to associate ETR after flight modification or rebooking<br />

PNR.<br />

ETR Retention date<br />

ETR Status<br />

Retention DateD<br />

OPEN (unused ETR) Available 3 years from date of issue.<br />

USED (fully used ETR) Stored for 30 days after the last transaction date.<br />

VOID/EXCH/RFND Stored for 30 days after the last transaction date.<br />

ET Refund Procedures<br />

Support and please proceed with BSP Refund guidelines.<br />

Cancel E-Ticket E<br />

Refund<br />

Not supported.<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*SV for eligible Interline carriers.<br />

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

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

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

_________________________________________________________________________________________________________<br />

Last Update: 12-Apr-10 Page 1 of 2


<strong>SAUDI</strong> <strong>ARABIAN</strong> <strong>AIRLINES</strong> <strong>ELECTRONIC</strong> <strong>TICKETING</strong> <strong>FOR</strong> <strong>HKG</strong> ABACUS<br />

Airline Reminder<br />

Quick Reference<br />

SV E-Ticket Requirement<br />

With immediately effect, SV will require E-Ticket transactions to include date of birth<br />

inserted in the endorsement. Failure to do so will result in ADM (Update 25Jun09)<br />

E.g. NONENDORSALBE/D.O.B.22APR04<br />

Effective 16Aug09, Saudi Arabian Airlines (SV) will only accept auto generated E-<br />

tickets (SSR TKNE) for all its flights. Manual tickets advisory (SSR TKNM) will no<br />

longer be accepted. Flights will be cancelled if ticket number is advised using SSR<br />

TKNM.<br />

For tickets that are issued with airline offices whereby SV is the IET carrier, agent<br />

must ensure that the issuing carrier send the SSR TKNE to SV. (Update<br />

13Aug09)<br />

<br />

SV has deactivated Passive Booking & Ticketing functionality on all GDSs after system<br />

migration to new platform on 11 April 2010. (Update 12Apr10)<br />

_________________________________________________________________________________________________________<br />

Last Update: 12-Apr-10 Page 2 of 2

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

Saved successfully!

Ooh no, something went wrong!