File Finishing Remarks for PNR Fields

The host accepts multiple values for some PNR fields, and accepts a single value for other PNR fields. Therefore, if a file finishing remark is applied to a PNR field that only accepts one value and if that field that already has a value, the file finishing remark will overwrite the existing value.

The table below lists the fields (selected in the PNR field on the General tab) that can be affected by file finishing remarks. The GDS column indicates to which GDS the field applies. The Occurs column identifies whether the PNR field can occur once or multiple times. If the field accepts multiple values, file finishing will always create a new entry.

Field

GDS

Occurs

Notes

Accounting Remarks

Galileo and Apollo

Multiple

Associated at the PNR level.

The administrator is expected to format the string content per host requirement. For information on host-specific formatting, see:

Address

(both Delivery and Written)

Galileo and Apollo

1

Associated at the PNR level.

If the field is already populated, file finishing changes the data to the data sent in the file finishing remark.

Galileo Format

  • Use an asterisk (*) as the separator.

  • Use P/ before the zip (postal) code.

  • Example:
    INEZ WHOEVER*1234 BROADWAY*INGLEWOOD, CA*USA P/12345      

Apollo Format

  • Use @ as the separator.

  • Use Z/ before the zip code.

  • Example:
    Jan Restora@6901 S. Havana\Apt 2@Englewood CO@US Z/80111     

Associated Itinerary Remarks

Galileo and Apollo

Multiple

Associated at the segment level, and applied to all segments.

The administrator is expected to format the string content per host requirement.

A maximum of 70 characters is permitted. All characters beyond the 70th character are ignored.

Unassociated Itinerary Remarks

Galileo and Apollo

Multiple

Associated at the PNR level.

The administrator is expected to format the string content per host requirement.

A maximum of 70 characters is permitted. All characters beyond the 70th character are ignored.

Customer ID

Apollo

1

Associated at the PNR level.

If the field is already populated, file finishing changes the data to the data sent in the file finishing remark.

General Remarks

Galileo and Apollo

Multiple

Associated at the PNR level.

The administrator is expected to format the string content per host requirement.

A maximum of 87 characters is permitted. All characters beyond the 87th character are ignored.

Example string of a general remark:

This is a test without qualifiers.

For Galileo, two general remark qualifiers can be specified. To specify a remark for a particular qualifier, enter the qualifier in the first and/or second character, followed by a slash (/), followed by the remark text.

Example string to set C in qualifier 1 and A in qualifier 2:

CA/This is a qualifier test.

 

Form of Payment

Galileo and Apollo

1

Associated at the PNR level.

If the field is already populated, file finishing changes the data to the data sent in the file finishing remark.

Form of payment options include:

  • Credit card - see example below for formatting

  • S - Cash

  • CK - Check

  • INV - Invoice

  • NONREF - Nonrefundable

 

Users with permission to view and/or edit Agent profiles will not see the following forms of payment for an existing agent:

As any user with permission to view and/or edit Agent profiles, I should not see the following forms of payment for an existing agent:

  • Cash

  • E-Voucher

  • Agency Payment

  • Credit

  • NONREF - Nonrefundable

  • Freeform
  • Invoice
  • Miscellaneous Credit Card
  • Miscellaneous
  • Non Refundable
  • Non Standard Credit Card
  • Government Requisition
  • Government Transportation
  • Special Government Requisition Cash
  • Guarantee to Agency IATA
  • Guarantee to Another Agency IATA

Galileo Credit Card Format

<vendor><card number>/D<expiration>/A<authorization code>/E

Example:

AX370000000000000/D1212/A4321/E

Apollo Credit Card Format

<vendor><card number>/D<expiration>/*<authorization code>/E

Example:

AX370000000000000/D1212/*4321/E

Name Field Remarks

Galileo and Apollo

1

Associated at the PNR level.

Name field remarks are attached to all travelers except infants. Infants will not have name remarks applied during file finishing.

A maximum of 33 characters is permitted. All characters beyond the 33rd character are ignored.

If the field is already populated, file finishing changes the data to the data sent in the file finishing remark.

Phone Field

Galileo and Apollo

Multiple

Associated at the PNR level.

Phone type values:  

  • R = Residence (home)

  • B = Business

  • A = Agency

  • H = Hotel

  • N = No contact

  • F = Fax

  • M = Mobile

Galileo Format

Format the phone field with the 3-character city code (optional), followed by the 1-character phone type, followed by an asterisk (*), followed by the phone number.

Example:

LONB*3033331212

Apollo Format

Format the phone field with the 1-character phone type, followed by an asterisk (*), followed by the phone number.

Example:

B*3033331212

PostScript

Apollo

1

Associated at the PNR level.

A maximum of 64 characters is permitted. All characters beyond the 64th character are ignored.

Special Service Request (SSR)

Galileo and Apollo

Multiple

Associated at the segment level; associated with all air segments by default.

Format the SSR with the 4-character code, followed by an asterisk (*), followed by SSR text.

File Finishing adds the SSRs, irrespective of the SSRs already present in the PNR.

Example:

WCHR*Need Wheelchair

Other Services Information (OSI)

Galileo and Apollo

Multiple

Associated at the PNR level.

Format the OSI with the 2-character airline code, followed by an asterisk (*), followed by OSI text.

Example:

YY*2ND OSI TEXT

Ticketing Field

Galileo and Apollo

1

Associated at the PNR level.

If the field is already populated, file finishing changes the data to the data sent in the file finishing remark.

The administrator is expected to format the string content per host requirements. The string is mapped as-is to the host. The following are differences between the hosts:

  • For TTL, the format for Apollo should be TL1856/20AUG, where 1856 is the time and 20AUG is the date. In Galileo, the format is TLDEN/UA1856/20AUG.

  • For TAW, the format for Apollo is TAW/15JUL-0400P or TAW/15JUL-1100A, whereas for Galileo, the format is TAW/15JUL/1600.

  • For TAU, the difference is in the delimiter. The Apollo format is TAU/09SEP/CONTACT AIRLINE, and the format for Galileo is TAU/09SEP*CONTACT AIRLINE (i.e., an asterisk instead of a slash).

Model Tab Examples

The following examples illustrate how the Model tab can be completed for file finishing remarks.

Ticketing Field Remarks

This example adds a booking date to the ticketing field. This example can be used for both Galileo and Apollo.

Line #

Field Selected

Free Text Entry

Notes

1

Freeform Text

TAU/

Indicates that the field listed below will be added to the ticketing field.

2

Booking Date - DDMMM

 

 

When all remarks have been entered, the Model tab contains the following when Galileo is the GDS provider:

 

OSI Remarks

These file finishing remarks add a date of birth to the OSI field. Note that OSI field formatting is different between the hosts; therefore, examples are provided for each host.

Line #

Field Selected

Free Text Entry

Notes

1

Freeform Text

Galileo entry: YY* 

Apollo entry: YY 

Indicates that the fields listed below will be added to the OSI field.

Note: The format for OSI differs slightly between Galileo and Apollo.

2

Freeform Text

 

Freeform Text without data indicates that a space is being added between assignable field data elements. The default function of the Freeform Text assignable field is a "space".

3

Traveler - First Name

 

 

4

Freeform Text

 

 

5

Traveler - Last Name

 

 

6

Freeform Text

 

 

7

Traveler - Passport Date of Birth

 

 

When all remarks have been entered, the Model tab contains the following when Galileo is the GDS provider: