etix issuance for group travel May 26st,2008 Lufthansa France informs Version 1.1 Introduction So far the issuance of group electronic tickets via other GDS than Amadeus was t possible, due to the fact that travel agents had to build passive segments for ticketing purposes and etix for passive segments is t allowed, as the ticket number transmission to Check-In is t guaranteed Contrary to paper tickets where passengers will always show their Paper tickets to the check-in agent, in an electronic environment it is essential that the ticket number is transmitted automatically to the Lufthansa Check-In system or the other Airlines. This automated ticket number transmission is triggered via the FA-Element or the SSR TKNE Element in the Amadeus PNR. All other manual ticket number entries do t transfer the electronic ticket information to Check-In. However in view of the IATA Deadline Simplify the Business (100% etix), a solution had to be found and here it is: The etix for groups procedure enables the issuance of electronic tickets in all GDS, ensures that the etix data will be transferred correctly to the check-in system, thus allowing that rmal check-in procedures may apply. 1
Introduction... 1 Ad hoc groups... 3 1. Handling of the group PNR... 3 PNR Access... 3 2... 3 2.1. Direct access via Amadeus... 3 2.2. Claim PNR... 3 2.3. Galileo Drop Through... 5 general rules for all groups... 5 8. Open segments... 5 9. Ticketing limitations of tickets in one transaction... 5 Attention: limitation on SSR Handlings... 5 10... 5 11. Interlining... 6 12. Name change after etix issuance... 6 14. Itinerary Receipt of the electronic ticket... 6 2
Ad hoc groups 1. Handling of the group PNR So far passive segments were sometimes used to merge bookings done in separate PNR s. This is t possible anymore. All reservations have to be done in one single PNR including feeders and/or onto flights as well as other airlines Flights. Any attempt to merge or enter passive segments will result in difficulties at Check-In. All general group procedures remain unchanged. As before entry of names, splits, changes of reservation, ASR and feeder bookings have to be performed by LH if the travel agent does t have access to the Amadeus group PNR. 2. PNR Access There are basically three different possibilities for the travel agency to have access to the LH Amadeus Group PNR. These options depend on the GDS the travel agent is using for the ticket issuance. (Japanese market is considered separately, Apollo, Abacus, Travelsky and Topas are still pending) Direct Access (Amadeus) Claim PNR (Sabre and Worldspan) Drop Through (Galileo) These options can t be compared with each other, e.g. if the drop through option is chosen, the Galileo Agent will have a passive copy of the PNR and a certain interactivity with the Amadeus PNR is given whereas a claimed PNR generates an active PNR in e.g. Sabre with nearly interactivity with the Amadeus PNR. Therefore a PNR Access via Claim is solely for ticketing issue. 2.1. Direct access via Amadeus Amadeus travel agents can issue etix when having access to the Amadeus group PNR if either: PNR has initially been booked with the travel agent s responsibility Or LH retroactively grants the travel agent access by entering the respective ES Element with the travel agents office code In case travel agents are using several GDS s for the issuance of tickets it goes without saying that the issuance via Amadeus will always be the most interactive and most secure (e.g. for ticket data transmission to check-in) compared to other options. 2.2. Claim PNR Once the group PNR is ready (all names have been entered and more manual changes are to be performed by LH) the travel agent may contact LH to enable him to access the PNR and go ahead to issue electronic tickets. As of 05.05.08 for Sabre and Worldspan LH will offer the Claim PNR option. 3
2.2.1. Steps to follow before Travel agent may issue electronic tickets If the agent is ready for ticket issuance, please proceed as follows: 1) make sure, all final names are entered 2) make sure, further manual changes by LH in the group PNR are necessary 3) The travel agent will inform LH with the agency s pseudo city code (PCC) for the ticketing location of the agency. The PCC ensures that only the dedicated travel agency can access the PNR. The transactions e.g. for claim used by the travel agent depend on the GDS used, however this procedure is familiar. If t, the agent has to contact his GDS help desk. 2.2.2. PNR Claim Details Please keep in mind that PNR Claim describes a functionality which allows a travel agent to get his own active PNR in his own GDS but once this active PNR has been generated any manual transaction performed by Lufthansa in the Amadeus PNR will t be reflected in the Claimed PNR. So manual updates by LH are possible anymore. Topic 2.2.2.1. Schedule changes after claim PNR Since this is t a manual but an automatic change, the correct information will be sent to the active group PNR in the other GDS. 2.2.2.2. Invol handling In cases where the passenger is enroute and involuntary handling needs to be performed by a LH office, rmal irreg procedures apply. The claimed PNR in the other GDS may t reflect these changes. 2.2.2.3. Overview of situations and possible actions for LH and travel agent The following table gives an overview of the transactions that may or may t be performed either by a LH office and/or travel agent after the PNR is claimed. LH add passive segment add active segment increase of group by copy PNR with creation of AXR record (1A transaction RRA) increase of group by copy PNR without creation of yes AXR record (1A transaction RRN) group name change in GDS passenger name change under clarification travel agent 4
respo change Split manual change e.g. rebooking of segment SSR e.g. FOID or ASR yes 2.3. Galileo Drop Through The Galileo Drop Through functionality for Groups is in place for a couple of years by w. The only change in this process is that from w on it is possible to issue electronic tickets. 2.3.1. Approval of Drop through Agents 1G Agents have to apply for an Amadeus office ID before they can use Drop through. Attention! The request must be done minimum 14 working days before departure! General rules for all groups 3. Open segments If the ticket issuing office issues the ticket in one active PNR adding the segments from the other PNR as open segments there will be possibility to connect the issued electronic tickets in the database with the PNR. The entry of the FHE Element does t help, as the system will t be able to link the tickets. 4. Ticketing limitations of tickets in one transaction Due to message limitations, it is t possible to issue the whole group in one transaction. Therefore the travel agent needs to partially ticket the group. No Split of the group is required, but a maximum of 9 passengers can be ticketed at the same time. Depending on the number of segments also less than 9 passengers can be ticketed at the same time. Travel agents will run into a time Out situation if the message is too big, and should then retry with less passengers. Ticket numbers will automatically be entered as SSR TKNE (n Amadeus Ticket issuance) or FA- elements into the 1A PNR. You do t need to enter the Ticket numbers manually ( FHE Element necessary). 5. Attention: limitation on SSR Handlings Amadeus has a limitation of a maximum of 127 t ASR related SSR Elements. Any SSR Element exceeding this number will t be processed. As the ticket number is the only guarantee that rmal check-in routines apply it is fundamental that the ticket number is in the face of the PNR. In case the group etix are to be issued via a 3 rd party GDS, for each segment and passenger one SSR TKNE element will be built so e.g. if you have a group of 40 Pax and 4 segments the maximum number of SSR elements is already exceeded. 5
6. Interlining Group PNR s including LH and Other Airline segments can be handled via Claim/drop through as described in any GDS. 7. Name change after etix issuance Normal group conditions do allow with fees in general name changes without running into the name change controller. But due to the critical data synchronization in an electronic environment some GDS s may have restricted or even disabled the possibility to perform a name change once the electronic tickets are issued. Also for this reason, PNR Claim /Drop through and ticket issuance should only be done once all names are correct and final. 8. Itinerary Receipt of the electronic ticket Passengers do need to receive the itinerary receipts of their electronic tickets from the ticket issuing office before departure. They have to retain this receipt throughout their journey as the receipt is proof that an electronic ticket has been issued and may always be requested at Check-in or at a ticket counter. Furthermore the Receipt may be requested at immigration in compliance with national immigration rules. 9. Issuance of Papertix For the following business cases you will need to request the issuance of a paper ticket at your Lufthansa Groupdesk missing Interlinings (most GDS s will implement a check at time of itinerary pricing if IET s with all participating carriers are in place) In order to check this please use the Amadeus :transaction code TGAD-LH/xx for ex Galileo : GC*LH SABRE : DRS ( www.eservices.sabre.com ) Lufthansa Destinations which may t be eligible for electronic tickets (No E- Indicator is set booking or availability display) BASICALLY ALL LH OPERATED DESTINATIONS ARE ETIX AFRICA/MIDDLE EAST - NON ETIX DESTINATIONS : ALG The BUS from Strasbourg will be eligible for all departures from June 1 st,2008. Handling of Infants with Interline partners (LH will reject the printing of an electronic ticket if an Interline Partner is involved in the itinerary) In all other cases an electronic ticket is to be issued. Prepayment in the Travel Agency via MPD If your GDS supports the use of a MPD without a value coupon, it is Lufthansa s preference that this option is to be used. Otherwise the VMPD via BSPlink GDS MPD without a value coupon: Follow your GDS instructions on how to fill in the data for the issuance of the 6
automated MPD. Use the option specified Air transportation and /or PTA as reason for issuance code (RFIC). No PTA fee will be charged by Lufthansa. The former PTA process required a Sponsor information, this information is t necessary anymore, as the RFIC PTA is only used as a temporary request for the issuance of a paper ticket at a Lufthansa office. Form of payment: the former PT identification is t required. Use Standard Forms of payment. VMPD via BSPlink: Follow the BSPlink instructions on how to fill in the data. Use the option specified Air transportation and/or PTA as reason for issuance code (RFIC). Enter all relevant data e.g. via OSI Elements into your booking record follow your GDS descriptions for correct handling. No PTA fee will be charged by Lufthansa. The former PTA process required a Sponsor information, this information is t necessary anymore, as the RFIC PTA is only used as a temporary request for the issuance of a paper ticket at a Lufthansa office. Form of payment: the former PT identification is t required. Use Standard Forms of payment Request Lufthansa to issue Ticket via GDS MPD /VMPD No Paper ticket will be issued if an e-ticket is possible. Please contact the Lufthansa under: From Monday to Friday : 10 am to 12am and 2pm to 5 pm Phone 0826 10 38 37 Email : cotxpress@dlh.de Amadeus Queue: PARLH0103/0 Deadline for Ticket request All requests have to be done at least 14 working days before departure.ticket request, excluding mailing day and departure day, with your the full mailing address including the contact person. 7