10.01.2015 Views

Maximum Name Characters

Maximum Name Characters

Maximum Name Characters

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.

GARUDA INDONESIA ELECTRONIC TICKETING FOR HKG ABACUS<br />

Implementation Date 06 Jul 07<br />

Quick Reference<br />

Default E-Ticket<br />

E<br />

Yes / 29 Nov 07<br />

Status Code HK-Confirmed / RR-Reconfirmed / HL-Waitlisted<br />

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

Passive Segment Supported, Carrier RLOC must be added to the GK/GL segment.<br />

E.g. 0GA963Y02JUNHKGCGKGK1*<br />

Ticketing agent has the responsibility to verify correct booking details for passive<br />

segment creation.<br />

Please remember to report E-ticket number to “GA” if using “GK” segment issuance.<br />

Form of Identification Support & 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- <strong>Name</strong> field)<br />

GA accepted cepted FOID include:<br />

CC – Credit Card ID – Locally defined ID Number PP - Passport<br />

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

Please note that GA Departure Control System (Check-in System) cannot process<br />

names that are booked with spacing.<br />

No spacing is allowed in the name field for E-Ticket issuance<br />

<strong>Maximum</strong> <strong>Name</strong><br />

GA only accepts 29 characters for e-ticket issuance.<br />

<strong>Characters</strong> for E-Ticket<br />

E<br />

GA will reject E-ticket transaction if passenger name characters more than 29.<br />

<strong>Maximum</strong> Segments<br />

Multiple E-tkt E<br />

for same<br />

pax in same airline<br />

RLOC<br />

Form of Payment<br />

<strong>Maximum</strong> 7 passengers<br />

<strong>Maximum</strong> 16 segments per e-ticket transaction.<br />

<br />

<br />

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

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

Supported Single & Multiple FOP.<br />

Ticket Number Reporting<br />

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

Infant E-Ticket<br />

E<br />

Supported.<br />

Fare not Support<br />

Zero fare ticket.<br />

Void<br />

Applicable with same day void.<br />

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

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

Void Exchange<br />

Auto Revalidation<br />

Not Supported.<br />

Not Supported.<br />

To associate GA ETR after flight modification or rebooking PNR, please report e-<br />

ticket nbr to GA either following way:<br />

1. by call in 28400000 or<br />

2. by fax the e-ticket copy to 28455021 or<br />

3. by manual insert ticket nbr to the PNR (7T-TK12612345678903≠N1.1)<br />

_________________________________________________________________________________________________________<br />

Last Update: 29-Jan-09 Page 1 of 2


GARUDA INDONESIA ELECTRONIC TICKETING FOR HKG ABACUS<br />

ETR Retention<br />

Date<br />

ETR Status<br />

OPEN (unused ETR)<br />

USED<br />

VOID/EXCH/RFND<br />

Quick Reference<br />

Retention Date<br />

Available 24 months in system from date of last flight coupon.<br />

Available 1 month in system from date of last flight coupon.<br />

Stored for 1 month after the last transaction date.<br />

E-ticket Refund<br />

Procedures<br />

Cancel E-Ticket E<br />

Refund<br />

Code-share flights<br />

Interline Carrier<br />

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

Not Supported.<br />

Not Supported.<br />

Not Supported.<br />

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

_________________________________________________________________________________________________________<br />

Last Update: 29-Jan-09 Page 2 of 2

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

Saved successfully!

Ooh no, something went wrong!