Storing Information from Apollo PNRs
The Apollo interface transfers group information when invoices and tickets are driven for PNRs that contain the ticketing remark T-*GN.
Note: If the group ID has not been created in GlobalWare, the interface will store the group and party IDs in the invoice item and will store the item as sale type R (retail).
|
Format: |
T-*GNgggggggggg where gggggggggg is the 10-character group code. |
|
Example: |
T-*GNYOUTH |
The interface updates the group passenger tables and the Invoice table as follows.
Updating the Invoice Table
When a PNR with the group ID ticketing remark is interfaced, the following occurs for invoice items:
- The data in the remark is stored in the Group ID field.
- PNR locator is stored in the Party ID field. You can override this with T-*PX/P.
- The group’s type (G or R) is stored for the sale type.
- The commission is set to 0.00 if the sale type is G and the settlement type is I.
- For air transactions, A is stored for revenue type if the group is a true group and is set up with air included in the package price and U if it is not. You can override the revenue type with the T-*PT ticketing remark.
Updating the Group Passenger Tables
The interface creates a record for each passenger in the PNR and stores information such as the passenger name, address, title, group options, and air itinerary. The interface can also update previously recorded passengers.
|
Updating Group Passenger Information Without Invoicing Transactions |
|
Creating Passenger Records
The first time you invoice a group PNR, the interface automatically creates a record in the group passenger table for each passenger listed in the PNR, giving you immediate access to this passenger information in GlobalWare's group functionality. The interface designates the first passenger stored in the PNR as the primary contact for each party.
The interface stores the following information from standard PNR entries.
- Passenger name
- Phone and fax number
- Billing name and address (W- field)
- Booking and selling agents
- Rooming code
- Party code
You enter other passenger information, such as the rooming remarks and group options selected by the passenger, in the PNR with group passenger codes. See Additional Group-Related Information in Apollo PNRs.
Ticket numbers are not stored in the passenger record; they are read from the Invoice table for the airline manifest.
Passenger Name Field
The interface stores the first 20 characters of each passenger name. The interface designates the first passenger in the PNR as the primary contact for the party. Enter the person who should be the primary contact first and then any additional names. This information appears on most reports.
Address Field
The interface stores the address lines from the W- field. Enter the primary contact's address. If the PNR contains more than one passenger, the interface stores this address for each passenger. The primary contact's address appears on Group Travel Statements.
The interface stores the first W- field in the passenger record Statement Name field. Enter the client or company name to be billed, as it should appear on group travel statements. For example, if this passenger is in an incentive group and you bill the company, enter the company name. If you are billing an individual, enter the name in the FIRSTNAME LASTNAME format (for example, KIM BECKER).
Passenger Title
If you enter a passenger title in the Leisure Shopper LSPN fill-in format, the interface stores the title in the passenger record (comment line 103). You can also specify a title with a passenger code. For more information, see Passenger Codes: T-*PX. This information appears on the Group Manifest, Option Manifest, Rooming List, Arrival/Departure Manifest, and Group Travel Statements.
Phone and Fax Fields
The interface stores the first R/ (Residence) phone number in the free-form phone field for each passenger. If there is no R/ phone, the first B/ (Business) phone number is stored.
The interface stores the first F/ (Fax) phone number for each passenger's Fax phone number.
Additional PNR Information: T-S1
The interface stores data following T-S1 in the invoice item’s first comments line. This field appears on Group Travel Statements and optionally on the Payments In/Out Report. You can use this field to store comments about the sale or adjustment (for example, T S1CANCEL SCUBA LESSONS OPT B).
Updating Passenger Records
The interface also adds and changes certain information in existing records when the PNRs are invoiced again if the group is set up to update passenger information through the interface.
The interface always stores the rooming code, entered with the /C passenger code, even if the group is not set up to update passengers through the interface. For details, see Replace Rooming Code Only: *RC.
The interface stores the following information if the corresponding field in the passenger record is blank.
- Billing name and address
- Passenger title
- Phone number
- Group Reporting
- Rooming remarks
- Special remarks
For example, if you add special remarks to the PNR, the interface stores them if the passenger record does not already contain special remarks.
The interface always replaces the following information regardless of whether it has been previously stored for the passenger.
- Air routing (if the group was set up to have routing stored)
- Group options
For example, if you add an option for a passenger, the interface always stores the options in the PNR for the passenger in the passenger record.
Updating Group Segments
If the group is set up to have routing stored and a PNR contains an air itinerary, the interface stores the following information for each leg in the group segments table.
- Airline code
- Flight number
- Class of service
- Origin and destination cities
- Departure and arrival dates
- Departure and arrival times
- Meal code
If specific legs have already been stored, the interface determines if there has been a schedule change and if so, updates the file with the most current information. The interface can also add segments for an additional ticket.
Updating Group Passenger Information Without Invoicing Transactions
Typically, you invoice a PNR when you record a payment received from the passenger or you need to issue tickets. With group PNRs, you might need to add or update passenger information without invoicing a payment or issuing a ticket. To do this, you enter special options in the form of payment entry and use the DAD ticketing modifier.
Note: When you use this feature, Apollo deletes the PNR Ticketing Field. If the Ticketing Field contains any special ticketing arrangements (TAU, TAW, TL), you must retrieve the PNR and reenter the ticketing information.
Update Passenger Information Only: HBFX*PAX
The *PAX qualifier enables you to create new passengers and update existing ones without invoicing a transaction. For example, if you want to begin tracking passengers before they send a deposit or generate routing reports before ticketing, you can enter the information in a PNR and invoice it with the following command. The interface stores the passenger information.
HBFX*PAX/DAD
Be sure to include the DAD modifier; otherwise, the interface creates invoice items.
Later, when you receive the deposit, you can enter it in the PNR and invoice it using the normal Apollo invoicing commands.
Replace Rooming Code Only: HBFX*RC
The *RC qualifier enables you to replace the rooming code for one or more passengers in a PNR at any time. Use this when you are processing a group in which roommates will be assigned shortly before the group departs. Enter the new rooming codes in the PNR with the rooming code override (T-*PX/C) and then invoice the PNR with the following command:
HBFX*RC/DAD
Be sure to include the DAD modifier; otherwise, the interface creates invoice items.