Additional Group-Related Information in Apollo PNRs

This section describes the information the Interface transfers from standard PNR entries to the group transactions and passenger records and which reports use it. It also describes any required, optional, or recommended entries related to tracking groups.

Standard Information	Passenger Information
Passenger Name Field	Passenger Codes: T-*PX
Address Field	Group Options: T-*PX/O
Passenger Title	Hotel In and Out Dates: T-*PX/H
Phone and Fax Fields	Party Code Override: T-*PX/P
	Passenger Title: T-*PX/T
Other Remarks	Other Group Reporting Info: T-*PX/G
Group Code: T-*GN	Rooming Code: T-*PX/C
No Routing Update: T-*NR	Rooming Remarks: T-*PX/R
Append Routing: T-*AR	Special Remarks: T-*PX/S
Product Type Override: T-*PT	Extra Remarks: T-PX/Xn
Additional PNR Information: T-S1

No Routing Update: T-*NR

The *NR ticketing remark indicates that you do not want GlobalWare to replace a passenger's routing in the group segments table.

If a passenger's air itinerary changes and you re-invoice or re-ticket the PNR, the Interface automatically stores the new routing, which ensures that airline reports always reflect the most recent itinerary and schedule changes.

However, you might encounter situations in which you do not want the Interface to replace a passenger's routing. For example, assume you have already issued tickets for the group and one of the passengers decides to take a side trip after the group excursion. When you issue the ticket for the side trip, enter *NR in the PNR to keep the Interface from replacing the passenger's group air itinerary.

Format:

T-*NR

Append Routing: T-*AR

The *AR ticketing remark indicates that you want to append segments to a passenger’s existing group routing, for example, if a passenger purchases another ticket for a side trip.

Format:

T-*AR

Product Type Override: T-*PT

For air transactions' revenue type, the Interface stores A if the group is set up with air included in the package price and U if it is not. The *PT ticketing remark overrides this product type with the one you specify.

For example, assume tickets are included in the package price and you will issue them after you have collected all payments. If you need to invoice a ticket separately for a passenger (for example, for an additional ticket not included in the package price), you would override the default air product type with U (air not included).

Format:

T-*PTp

where p is the product type code.

Example:

T-*PTU

Passenger Codes: T-*PX

You can enter the following information with passenger codes.

Options the passenger has selected
Hotel in and out dates
Party code
Passenger's title
Information on Group Reporting
Rooming code
Rooming remarks
Special remarks

Passenger codes are entered in the T-*PX ticketing remark. A code can be associated with all passengers in the PNR or a specific passenger. You can enter multiple T-*PX remarks if needed.

Format:

T-*PX/xvalue/yvalue/zvalue

where x, y, and z are codes and value is the data that is stored.

T-*PX##/xvalue/yvalue/zvalue

where ## is the number of the passenger that the passenger codes apply to.

Each passenger code is described below. At the end of this section are examples of multiple codes.

Group Options: T-*PX/O

Use the /O passenger code to specify the codes for optional services that the passenger has selected. This information is used to generate the Inventory Summary and Option Manifest. This information also appears on the Group Manifest and Group Travel Statements.

Format:

/Ooption.option.option

where option.option.option are the option codes.

Option codes can be up to four characters. Separate each with a period.

Example:

/OHI21.ABC1

The Group List can show the available options for a group.

Hotel In and Out Dates: T-*PX/H

The Interface stores the departure and return dates you set up for the group as the hotel check-in and check-out dates. If either date is different for the passenger, use the /H passenger code to override the group's departure and return dates for the hotel check-in and check-out dates. You can specify either date or both. If you do not enter one of the dates, the Interface stores the date set up for the group. This information appears on the Rooming List.

The DEPART DATE and RETURN DATE columns in the Group List show the group's departure and return dates.

Use the ddmmmyy format. The year is necessary only if it is different from the current year.

Format:	`/Hindate-outdate` where `indate` and `outdate` are the check-in and check-out dates
Examples:	`/H30OCT-10NOV`	Check-in is Oct. 30; check-out is Nov. 10 (of this year).
	`/H30DEC-02JAN10`	Check-in is Dec. 30 of this year, check-out is Jan. 2, 2010.
	`/H02MAY`	Check-in date is May 2; the group check-out date is stored.
	`/H-21JUL`	The group check-in date is stored; check-out date is July 21.

Party Code Override: T-*PX/P

Use the /P passenger code if you want to use a party code other than the PNR locator.

Format:

/Ppartycodec

where partycodec is the party code (up to 10 characters).

Example:

/PSANDERSKIM

Passenger Title: T-*PX/T

Use the /T passenger code to specify the passenger's title. The /T entry overrides the LSPN passenger title. This information appears on the Group Manifest, Option Manifest, Rooming List, Arrival/Departure Manifest, and Group Travel Statements. The data is stored in Passenger Comment line 103.

Format:

/Ttitle

where title is the passenger's title (up to 30 characters).

Example:

/TVP MANUFACTURING

Other Group Reporting Info: T-*PX/G

Use the /G passenger code to specify additional information about a group passenger. This information can be printed on the Group Passenger list. The data is stored in Passenger Comment line 104.

Format:

/Ggroup info

where group info is any additional information (up to 30 characters).

Example:

/GASDFE

Rooming Code: T-*PX/C

The Interface stores the party code as the rooming code because usually all passengers in the same party room together. Use the /C passenger code to override the rooming code when members of a party are not rooming together. This information appears on Group Travel Statements and is used to sort the Rooming List.

Format:

/Crrrrrrrrrr

where rrrrrrrrrr is the rooming code (up to 10 characters).

Example:

/CKIM277B KIM277B

/C no rooming code stored.

You can replace the rooming code without updating any other information in the Passenger File. See Replace Rooming Code Only: *RC for more information.

Rooming Remarks: T-*PX/R

Use the /R passenger code to store rooming remarks for a passenger. This information appears on the Group Manifest and Rooming List. The data is stored in Passenger Comment line 102.

Format:

/Rrooming remarks

where rooming remarks is any additional rooming information (up to 30 characters).

Example:

/RNEEDS 1ST FLOOR ROOM

Special Remarks: T-*PX/S

Use the /S passenger code to store any special remarks for a passenger. This information appears on the Group Manifest, Option Manifest, and Arrival/Departure Manifest. The data is stored in Passenger Comment line 101.

Format:

/Sspecial remarks

where special remarks is any additional information (up to 30 characters).

Example:

/SNEEDS WHEEL CHAIR

Extra Remarks: T-*PX/Xn-

Use the /X passenger code to specify additional information about a group passenger. This information can be printed on the Group Passenger list. The data is stored in Passenger Comment lines 1-99.

Format:

/Xn-extra info

where n is the remarks number (1 to 99) and extra info is additional information (up to 30 characters).

Example:

/X1-BUS SEAT 12B

Passenger Code Examples

T-*PX/SVEGETARIAN MEALS ONLY/OAEFG

The Interface stores VEGETARIAN MEALS ONLY for special remarks and option AEFG for all passengers in the PNR.

T-*PX2/TVP MANUFACTURING/RROOM ON SECOND FLOOR/SDIABETIC

The Interface stores the following information for the second passenger only: VP MANUFACTURING for the passenger title, ROOM ON SECOND FLOOR for rooming remarks, and DIABETIC for special remarks.

T-*PX5/TMARKETING MANAGER/RREQUEST FRUIT BASKET T-*PX5/OAFG

The Interface stores information from both *PX ticketing remarks for the fifth passenger in the PNR: MARKETING MANAGER as the passenger title, REQUEST FRUIT BASKET in rooming remarks, and AFG as the passenger's options.

T-*PX/OABC/ROCEAN SIDE ROOMT-*PX3/CWIL447B/OAB

The Interface stores option ABC and rooming remarks OCEAN SIDE ROOM for all passengers in the PNR. The Interface then stores rooming code WIL447B and option AB for the third passenger only. Note that the options specified in the *PX3 override the options entered in the *PX for the third passenger.

Note: If you have entered one or more *PX ticketing remarks in a PNR for individual passengers (for example, *PX1 and *PX2), do not use the name-select feature to invoice the PNR. Using the name select feature could cause the Interface to store the wrong information for the passenger that is name-selected. For example, assume you entered *PX ticketing remarks for each passenger in a three-passenger PNR. If you name-select the third passenger, the Interface would associate the information specified in *PX1 with that passenger and could store incorrect information. If you must name-select, you should replace the asterisk (*) in each *PX with some other character, such as a dash.