Revised* UA E-Ticket Quick Reference
Revised* UA E-Ticket Quick Reference
Revised* UA E-Ticket Quick Reference
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
UNITED AIRLINES ELECTRONIC TICKETING FOR HKG ABACUS<br />
Implementation Date Dec 2000<br />
<strong>Quick</strong> <strong>Reference</strong><br />
Default E-<strong>Ticket</strong> Carrier Yes / 08 Jan 03<br />
Status Code • HK-confirmed / RR-reconfirmed / HL-waitlisted / DS-open<br />
• At least one confirm segment in <strong>UA</strong> RLOC for e-ticket issuance<br />
Passive Segment • Supported, Carrier RLOC must be added to the GK/GL segment.<br />
E.g. 0<strong>UA</strong>123Y23NOVHKGNRTGK1*<br />
• <strong>Ticket</strong>ing agent has the responsibility to verify correct booking details for passive<br />
segment creation.<br />
• Please remember to report E-ticket number to “<strong>UA</strong>” if using “GK” segment issuance.<br />
Form of Identification<br />
Name Field Requirement<br />
Maximum Name<br />
Characters for E-<strong>Ticket</strong><br />
Maximum Segments<br />
Multiple E-tkt for same<br />
pax in same airline RLOC<br />
Form of Payment<br />
Infant <strong>Ticket</strong><br />
Fare not Supported<br />
<strong>Ticket</strong> Number Reporting<br />
Not Required.<br />
Use passenger full name (same as passport) for Reservation & <strong>Ticket</strong>ing.<br />
Maximum 33 name characters for ETR (Included space & “/”).<br />
Abacus displays 31 name characters in ETR.<br />
Maximum 9 passenger per E-ticket transaction.<br />
Maximum 16 segments including surface sector per passenger/E-ticket transaction.<br />
• Allow multiple ETRs created in <strong>UA</strong> RLOC with different itinerary.<br />
• Require voiding unwanted Electronic ticket prior to issues a new E-ticket.<br />
Supported Single & Multiple FOP.<br />
Support.<br />
Nil.<br />
Automatically generated SSR TKNE to <strong>UA</strong> after E-ticket issuance.<br />
Void • Applicable with same day void.<br />
• An automated program will change the E-ticket coupon status from “OPEN” to “SUSP”<br />
for customers who NO-SHOW their flight for ALL KIND OF <strong>UA</strong> E-<strong>Ticket</strong>. Agent is no<br />
longer to VOID when ETR status is SUSP.<br />
Exchange • Supported (including ET to ET & paper to ET).<br />
• Please refer to BSP <strong>Quick</strong> <strong>Reference</strong> for Carrier preference<br />
• Submission to BSP: original ETR + reissued ETR<br />
Void Exchange • Supported.<br />
• Void Exchange allowed only on same day transaction and applicable to:<br />
E-<strong>Ticket</strong> exchange E-ticket, Paper document exchange to E-ticket.<br />
_________________________________________________________________________________________________________<br />
Last Update: 27-MAY-09 Page 1 of 2
Auto Revalidation • Not Supported.<br />
<strong>Quick</strong> <strong>Reference</strong><br />
• For <strong>UA</strong> unused ticket (all <strong>UA</strong> sectors) agent should perform the exchange transaction<br />
and associate the new itinerary into the new E-ticket record<br />
• For <strong>UA</strong> partially used ticket (all <strong>UA</strong> sectors), please call <strong>UA</strong> reservation office to<br />
associate ETR after flight modification or rebooking PNR.<br />
• For <strong>UA</strong> IET Revalidation (wholly unused or partial used), agent should perform the<br />
exchange transaction (including totally unused or partially used ), and associate the<br />
new itinerary into the new E-ticket record<br />
ETR Retention date<br />
ETR Status<br />
OPEN (unused ETR)<br />
USED (fully used ETR)<br />
VOID/EXCH/RFND<br />
Retention Date<br />
Available 390 days in system from date of last flight coupon.<br />
Stored for 8 days after the last flight coupon.<br />
Stored for 8 days after the transaction date.<br />
E-tkt Refund Procedures<br />
Support and please proceed with BSP Refund guidelines.<br />
Cancel E-<strong>Ticket</strong> Refund • Supported and Cancel Refund allowed only on same date transaction.<br />
Entry: WTRX<br />
E.g. WTRX016xxxxxxxxxx<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*<strong>UA</strong> 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 />
Carrier Policy • To avoid communication error, please void the e-ticket prior any name change.<br />
• ** Please remember to obtain airline name change authorization before name<br />
change. **<br />
E-<strong>Ticket</strong> Hotline -----<br />
_________________________________________________________________________________________________________<br />
Last Update: 27-MAY-09 Page 2 of 2