Prepaid Ticket Advice (PTA)

Transcription

1 2002, Worldspan L.P. All Rights Reserved.

2

3 Table of Contents Overview...1 Create Procedures...2 PTA Number Field (7PTA)...2 Purchaser Information Field (7P/)...4 Fare Construction and Amounts Collected Field (7F/)...5 Passenger Contact Field (7C/)...10 Routing Field (7Z)...12 Special Remarks Field (7S/)...14 Action Field (7A/)...15 PTA PNR Ticketing Field...20 Date of Issue Field...20 Error Correction...21 International Prepaids F/ and 7F/AMNT- Entries...25 Miscellaneous Fare Information Z Entry PTA Entry...30 Additional Collection Prepaids...30 Additional Collection for a Fare Construction on an Existing Prepaid...31 General Information...32 Mandatory ADC PTA Fields...32 Automated PTA Mask...35 PTA PNR Ticketing Field...38 Completion of MCO for PTA Purchase...39 PTA Ticketing...40 Automated Ticketing Entries...40 Manual Ticketing Entries...41 Obtaining the PTA Number...41 PTA Purge Date...42 System Purge - Normal PNR (No PTA)...42 PTA PNR Sent to an Automated Host Location...42 PTA PNRS Sent to a Non-Automated Host Location or an OAL...43 OAL PTA Numbers...43 Incomplete PTA PNR Page i

4 Table of Contents Changing the Purge Date...44 International PTA PNR...44 Page ii 0902

5 Overview Reference: HELP PTA The is an authorization permitting the issuance of a ticket at a location other than the point of payment. It can involve domestic or international reservations. A PTA is used for prepayment of tickets, baggage charges, and incidental expenses directly related to the transportation covered by the Prepaid Ticket Advice. When a PTA is entered and processed through an airline on-line reservations system it is referred to as an automated PTA. Worldspan automated PTA system processing is designed to handle prepaid tickets within the Worldspan system. The PTA is contained within the associated PNR. There are seven (7) PTA fields that can be entered into a PNR. Any addition, change, or deletion made to the PTA field is recorded in the history (*H) of the PNR. As PNRs containing PTAs are completed or purged from the system, the complete PNR with all historical data is copied to microfiche. PTA refunds are handled according to local policy. Once a PTA ticket has been issued to the traveler, unless restricted by the purchaser, the ticket can be exchanged like any other ticket. Either of the following formats can be used to display a prepaid PNR: *PTA ATL - PATEL/KAREN.MS Boardpoint -or- *PTA (check digit not included) 0902 Page 1

6 Create Procedures A PTA can be created in a retrieved or newly created PNR. There are seven (7) PTA fields, five (5) of which are mandatory in each PTA. These fields are listed below: 1. PTA Number (7PTA) Mandatory 2. Purchaser information (7P/) Mandatory 3. Fare - Construction and monetary amount (7F/) Mandatory 4. Passenger contact (7C/) Mandatory 5. Routing (7Z) Mandatory 6. Special remarks (7S/) Optional 7. Action (used by the host airline prepaid desk only) Optional The prime entry code for the PTA field is the 7 key; however, there is one PTA field that does not start with 7. That field is the Purchaser s Telephone Contact Field. The purchaser s telephone number should be the first item in the PNR phone (9) field. PTA Number Field (7PTA) Reference: Function: Function ID: Entry: HELP 7PTA Enter the PTA number into a PNR 7PTA 7PTA PTA NUMBER/VALIDATING AIRLINE/CURRENCY CODE AND TOTAL AMOUNT The PTA number begins with the airline accounting code (validation) number of the airline on which the PTA is being validated. It is followed by the ten (10) digit serial number from the Prepaid Ticket Advice or Miscellaneous Charges Order (MCO), and then the check digit from the auditor s coupon. Page

7 The example below is a PTA Number field for $ with PTA number validated on NW (012). ENTRY: 7PTA /NW/USD Entry Explanation 7PTA PTA Number field function ID. 012 All PTA numbers must begin with the airline accounting (validation) code number of the Host airline (NW = 012) The remainder of the PTA number is 11 digits; 10 digits and the check digit from the auditor s coupon. / Separator. NW The two-character code of the validating carrier. / Separator USD Use the currency of the country where the prepaid amount is collected. The currency code must be a valid ISO code The total amount of the PTA including any applicable taxes. The PTA service charge must not be included in this amount NOTES: 1. The PTA Number field (7PTA) must be entered prior to the Purchasers Information field (7P/). 2. The PTA value is limited to nine (9) numerics. However, the maximum size is twelve (12) alpha/numerics, which includes the three-character currency code. 3. The airline accounting code (validation number) and the airline two-character code must match. 4. The PTA total includes taxes but must not include the PTA service charge Page 3

8 Purchaser Information Field (7P/) Reference: HELP 7P/ Function: Enter the PTA purchaser information in a PNR Function ID: 7P/ Entry: 7P/AIRLINE RESERVATIONS OFFICE CODE/ACCOUNT NAME AND ADDRESS The Purchaser Information field contains the name and address of the purchaser or travel agency. The city code must be a valid airline reservations office and is usually the office in control of the PTA. ENTRY: 7P/ATL/KAREN PATEL 103 WEST PACES FERRY RD ATLANTA GA Entry Explanation 7P/ Purchaser Information field function ID ATL City code of the controlling airline reservations sales office / Separator KAREN Purchaser s name and address information. The PATEL maximum length of the Purchaser Information field is 127 characters, or two lines of data. If the data exceeds 127 characters, the excess data must be entered in the Special Remarks field (7S/) The following is an example of the Purchaser Information field entry for a travel agency PTA: ENTRY: 7P/MIA/THE TRAVEL EXPERT 156 BAY ST MIAMI FL Page

9 NOTES: 1. The PTA Number field (7PTA) must be entered before the Purchaser Information field (7P/). 2. The purchaser s phone contact should be the first item in the Phone (9) field. 3. If a travel agency is involved in the transaction, always show the agency name and address as the purchaser. 4. Your entry is actually free-flow information after the second separator (/). 5. The maximum length of the Purchaser Information field is 127 characters, or two lines of data. 6. The city code is validated against the Reservations Office City Code (ARSO) table. The city code must be present in the ARSO table. Fare Construction and Amounts Collected Field (7F/) Reference: HELP 7F/ Function: Enter the PTA fare construction data, formof-payment, and commission information into a PNR The PTA Fare Construction field can contain up to four (4) fields for entering fare data. It is the only PTA field that must be entered in sequence. There are two (2) fields for fare construction and two (2) fields for the amounts collected. Function Ids: 7F/ For routing, fare basis, base fare, form-of-payment and issuing office information 7F/LADR- For fare construction overflow data 7F/AMNT- For numerical amounts and written amounts 7F/FARE- Used for overflow of amounts collected data 0902 Page 5

10 ENTRY: 7F/DEN CO LAS Y USD *CK-AA16 -or- 7F/DEC CO LAS Y USD *CK-AGT/ADVENTURE TRAVEL* Entry Explanation 7F Fare construction field function ID DEN CO LAS Routing (use city codes, not airport codes) Y Fare basis/ticket designator code Base fare USD Currency code and total fare * Mandatory asterisk CK Form of payment - Mandatory separator AA16 Issuing office or agency name and IATA number -or- AGT/NAME NOTES: 1. The Fare Construction field contains the complete routing including all city codes, carrier codes, and fare basis/ticket designator codes, the base fare, tax, and total fare in local currency. 2. The fare basis/ticket designator codes follow the city codes at all fare break points of the routing. 3. When the same fare basis is used for all segments it can be shown at the end of the routing. 4. When a fictitious construction point, stopover charge, or any special fare construction applies, show the construction including fares. 5. The form of payment, issuing office or AGT/agency name and ARC number must be the last items in the Fare Construction field. Page

11 6. The primary Fare Construction field is a single item field with a maximum of 127 characters. When the fare construction exceeds 127 characters, additional information can be included in a secondary Fare Construction field designated by the Function ID of 7F/LADR-. Multiple secondary Fare Construction fields can exist in a single prepaid. Secondary Fare Construction Field (7F/LADR-) The Secondary Fare Construction field is used for fare construction overflow data. If the secondary Fare Construction field is used, an asterisk (*), form of payment, issuing office or AGT/agency name and ARC number are to be omitted from the primary Fare Construction field. This information is then entered as the last items in the LAST secondary Fare Construction field entered. NOTES: 1. Commission data can be entered after the agent name and seven (7) digit ARC number. There is a mandatory space prior to the COMM RATE and the commission percentage. 2. The form of payment must be a minimum of two characters, e.g., CA, CK, or CC. Credit card forms of payment are entered with or without card numbers, e.g., CCVI , or CCVI, CCAX, etc.). 3. If more than one passenger type, e.g., adult and child are to be included in a single PTA, a separate Fare Construction field is required for each passenger type. The 7F/ field would show the adult construction and the 7F/LADR- field would contain the child s fare construction. The final 7F/LADR- field would contain the remaining items if they do not fit into one 7F/LADR- field Page 7

12 Amounts Collected Field (7F/AMNT-) The second part of the Fare Construction field cover the amount collected and is called the Numeric Fare Field. This field contains the information required to calculate the value of the PTA. The entry includes the base fare, tax (es), and total. The total is then expressed as a written amount. ENTRY: 7F/AMNT-ADULT TAX 34.55US 3.00XF 3.00ZP2.50AYTKT TOTL USD *TOTAL THREE EIGHT EIGHT POINT FIVE ZERO USD The Amounts Collected field entry consists of two elements, the numerical amount and the written amount. Entry Explanation 7F/AMNT- Amounts Collected function identifier TAX Base fare and tax amounts. TKT TOTL USD Ticket total in USD (use the ISO Currency Code of the currency collected). * Required separator between numerical and written amounts. TOTL Total amount of PTA. THREE EIGHT Amount of funds collected (written out). USD ISO Currency Code of the currency collected. NOTES: 1. The primary Numeric Fare field (7F-AMNT-) is a single item field with a maximum length of 127 characters. If the numeric fare amount exceeds 127 characters, additional information can be included in a secondary Numeric Fare field designated by the function ID of 7F/FARE-. There is no limit to the number of 7F/FARE fields, but each entry is limited to 2 lines characters. Page

13 2. The Numeric Fare field of a prepaid can contain up to five (5) items used to calculate the value of PTA. In constructing this element each of the items must be shown in the following order a. Base Fare b. Tax (es) c. Ticket total d. Other charges (excess baggage, pocket money, etc.) e. PTA total 3. The amounts entered MUST include a decimal. 4. The primary Numeric Fare field always includes the total ticket charges for all passengers followed by any other charges or expenses, and finally the total sum of the PTA. If prepaid funds require additional explanation, enter this information in a secondary Numeric Fare field after the written PTA total. 5. Precede each amount with the applicable passenger type, for example, ADULT, CHILD, MILITARY, YOUTH, etc. Do not use PTC codes. When more than one passenger type is included in a PTA breakdown with the base fare, tax, and total is shown in a secondary Numeric Fare field after the written amount in the same order as entered in the fare construction field. This clarifies the individual ticket values. 6. The ISO currency code should appear before or after the written amount. 7. The written amount is given number by number and not shown as the whole number. For example, the number 12 would be written as one two and not twelve Page 9

14 Passenger Contact Field (7C/) Reference: HELP 7C/ Function: Enter the necessary passenger information into the PNR for the creation of the Prepaid. The passenger contact field is a single item field with a maximum length of 127 characters. Function ID: 7C/ Entry Formats: Information Phone and Address Phone Only Address Only No Contact Entry 7C/AREA CODE & PHONE NUMBER- IDENTIFIER*ADDRESS 7C/AREA CODE & PHONE NUMBER- IDENTIFIER 7C/*ADDRESS 7C/PWCT ENTRY: 7C/DEN B*1622 WESTSIDE RD DENVER CO The asterisk (*) separates the phone and address information. Entry Explanation 7C/ Passenger Contact field Function Identifier. DEN 303 Area code and phone number. -B Phone type identifier (B= Business, H= Home, etc.) * Required asterisk to separate the phone and address information WEST Address Page

15 Other examples: 1. Passenger s home phone and address (for OAL PTA s or nonautomated offices). ENTRY: 7C/DEN B*1622 WESTSIDE RD/DENVER CO Separators (/) shown after the asterisk (*) cause a new line to generate on teletype messages sent to an OAL or non-automated office. 2. Passenger s home number only. 3. Passenger s address only. ENTRY: 7C/DEN H ENTRY: 7C/*1622 WESTSIDE RD DENVER CO Note the asterisk (*) follows the 7C/ when only the address is given. This asterisk is needed for teletype programs to recognize a phone number is not present and the word PHONE does not precede the address. 4. No phone number or address. The passenger will contact the validating airline. ENTRY: 7C/PWCT By using the code PWCT (Passenger will contact), messages are sent without the word PHONE. The code PWCT is sent in its place Page 11

16 Routing Field (7Z) Function: Function ID: Entry Formats: Identifies the office and airline to issue the ticket and provides PTA issuing instructions. 7Z 7ZCNI 7ZIOD Examples: 1. Contact and issue (default routing to be used) ENTRY: 7ZCNI CNI is used when a phone number and/or address has been entered in the Passenger Contact field. The receiving airline calls the passenger to advise a prepaid ticket is waiting and establish a ticketing arrangement. CNI generates a teletype message to an OAL or non-automated office or sends the PNR to Q/17 of a host airline automated office. CNI is recommended for all international PTAs. 2. Issue on demand (default routing to be used) ENTRY: 7ZIOD IOD is used when the passenger contact is unknown and the Passenger Contact field shows 7C/PWCT. IOD is used when the passenger will contact the airline to establish ticketing usually at a ticket office or at the airport prior to departure. IOD generates a message to an OAL or host non-automated office. For a host airline automated office, the PTA is stored in Worldspan at end transaction (ET) and is accessible to the controlling office when needed. Page

17 3. Override the default routing in order to send PTA to Delta Air Lines in Frankfurt, Germany. ENTRY: 7ZCNI/FRA/DL -OR- 7ZIOD/FRA/DL There are times when a PTA is sent to an airline other than the first carrier or board point of an itinerary. The prepaid may not always be for travel on the first segment of the itinerary, or the first airline in the itinerary may not issue prepaids. NOTES: 1. CNI - Contact and Issue, is used when a phone number and/or address has been entered in the Passenger Contact field. The receiving airline will call the passenger and advise a prepaid ticket is waiting for issuance. 2. IOD - Issue on Demand, is used when the passenger contact is unknown and the Passenger Contact field shows 7C/PWCT. 3. The PTA Routing field is a single item field. 4. When the city code and two alpha airline code are not input, Worldspan automatically routes the PTA message to the proper recipient according to the first airline/boardpoint shown in the itinerary and according to the PTA Routing/Agreements (KAI) database. 5. Worldspan automatically appends to the PTA Routing field the applicable airline and city code; therefore the default routing should always be used. 6. The routing override entry is to be used when the prepaid is to be sent to someone other than the first airline/boardpoint of the itinerary Page 13

18 Special Remarks Field (7S/) Function: Used to enter any pertinent data pertaining to the PTA that cannot be appropriately be stored in any PTA fields. Function ID: 7S/ Entry Formats: 7S/FREE-FLOW REMARKS ENTRY: 7S/REFUND TO AGCY ONLY Field Explanation 7S/ Special Remarks field function identifier. Refund to Free-flow remarks. The maximum length of the Special Remarks field is 127 characters, or two lines of data. NOTES: 1. The Special Remarks field is a single item field with a maximum length of 127 characters. 2. Special Remarks can be used for entries such as: a. Special travel instructions imposed either by the tariff or purchaser. b. Passenger has no identification. For example, the mother s maiden name or code word can be used. c. Refunding instructions. 3. The use of the Special Remarks field is optional. 4. The Special Remarks field can be used to store overflow data from the Purchaser Information field. Page

19 Action Field (7A/) Function: Used to show the current status of a PTA. Function ID: 7A/ Of the seven (7) Action fields, all but two (PAR, ACK) close the PTA and inhibit any further modifications of the PTA information. Modifications to the PNR are still possible. Acknowledged Acknowledged (ACK) indicates a PTA sent to an off-line carrier has been received. This function is only entered if the ACK for the OAL does not go into the PTA PNR automatically. ENTRY: 7A/ACK/CHIRPUA 15JUL Field Explanation 7A/ Action field function identifier. ACK Acknowledged indicator. / Separator. CHIRPUA 15JUL City/airline/date from which ACK was received. NOTE: There are 31 characters allowed after the ACK/ Page 15

20 Ticketed Ticketed (TKT) indicates all ticketing against a PTA has been completed. ENTRY: 7A/TKT/ /USD Field Explanation 7A/ Action function identifier. TKT Ticketed indicator. / Separator Host airline ticket number. / Separator. USD Ticket amount. NOTE: Never enter an off-line ticket number in the TKT field. If an off-line carrier sends ticket numbers, enter in the Special Remarks (7S/) field. There are 31 characters allowed after the TKT/. Partial Ticketing Partial ticketing (PAR) indicates partial ticketing against a multiname PNR or partial value of the PTA was used, the balance to be refunded. The action field remains open for the addition of 7A/TKT or 7A/PRF. ENTRY: 7A/PAR/ /USD Field Explanation 7A/ Action function identifier. PAR Partial ticketing indicator. / Separator Host airline ticket number. / Separator USD Ticket amount. Page

21 NOTE: If there is more than one name in the PNR, a name should follow the dollar amount if possible. There are 31 characters allowed after the PAR/. Partial Refund Partial Refund (PRF) indicates a partial refund was made against a PTA. ENTRY: 7A/PRF/ JUN Field Explanation 7A/ Action function identifier. PRF Partial refund indicator. / Separator Optional free-flow information. NOTE: There are 31 characters allowed after the PRF/ Page 17

22 Refund Refund (RFD) indicates a refund has been made against a PTA. ENTRY: 7A/RFD/ATC142 ISSUED 01JUL Field Explanation 7A/ Action function identifier. RFD Refund indicator. / Separator ATC142 Optional free-flow information. NOTE: There are 31 characters allowed after the RFD/. Canceled Canceled (CNL) indicates a PTA has been canceled due to either agent error or other unusual circumstances. ENTRY: 7A/CNL/XLD DUE AGT ERROR SEE RLOC YHEI83 Page

23 Field Explanation 7A/ Action function identifier. CNL Canceled indicator. / Separator. XLD DUE AGT Optional free-flow information. NOTE: There are 31 characters allowed after the CNL/. Relay Relay (RLA) indicates a re-routing of an existing PTA PNR to another airline. ENTRY: 7A/RLA/SMFRPUA Field Explanation 7A/ Action function identifier. RLA Re-routing indicator. / Separator. SMFRPUA City/prepaid code/carrier. NOTE: There are 31 characters allowed after the RLA/ Page 19

24 NOTES: 1. The PTA Action field is only used by the host airline prepaid desk. 2. If an acknowledgement (ACK) is not received from the carrier to whom the original message was routed, Worldspan automatically resends the message after 12 hours. 3. If an ACK is not received from the second message generated, Worldspan places the PNR on queue at the host airline prepaid desk for manual generation of a third message and follow-up. 4. Acknowledgements do not apply to prepaids where a host airline is the issuing carrier. PTA PNR Ticketing Field Ticketing Time Limits should be the only ticketing field used in a PTA PNR. 1. Ticketing field entry for host origination: ENTRY: 8TL30//PTA.IN.FILE 2. Ticketing field entry for OAL origination: NOTE: ENTRY: 8TLSAN/UA3P/15AUG//PTA.TO.FOLLOW If an OAL is issuing the ticket, the second entry above should be used to send the entire PNR itinerary to the originating carrier. Date of Issue Field Worldspan automatically appends the Date of Issue to a PTA PNR when the prepaid number is entered into the PNR: DATE OF ISSUE 03 OCT 01 Page

25 NOTES: 1. The Date of Issue appears directly above the prepaid number in the PNR. 2. The date is transmitted on a teletype message when sending a prepaid to an OAL. 3. The error message INVALID PTA ND DATE OF ISSUE is received at End Transaction (E) if a PTA number has not been entered in the PNR. Error Correction Prepaid field modifications (error corrections) can only be made prior to End Transaction (E) during the prepaid creation. The only field that can be changed after ET is the Ticketing field. In most instances, to modify a field in a prepaid you simply add the change symbol (@) after the PTA field identifier (7), and then enter the correct information as in the original PTA field. NOTE: Any correction required on a PTA after ET must be made by the validating host airline prepaid desk in their reservations office. Change PTA Number (7@PTA) ENTRY: 7@PTA /NW/USD Change Purchaser Number (7@P) ENTRY: 7@P/MIA/KAREN PATEL 36 MAIN ST MIAMI FL Page 21

26 Change Fare Construction Information Original Entry Change Entry Primary Fare Construction 7F/ Secondary Fare Construction 7F/LADR- Primary Numeric 7F/AMNT- Secondary Numeric 7F/FARE- NOTE: A PTA Fare Construction field cannot be deleted once it has been entered. If the information in a field must be removed and no replacement information is to be provided, XXX can be used to overlay the information. For example: 72@/LADR-XXX. Change Passenger Contact (7@C/) ENTRY: 7@C/SFO H Change Routing (7@Z/) ENTRY: 7@ZCNI/BOS/DL (CHANGE CONTACT AND ISSUE ENTRY) -OR- 7@ZIOD/BOS/DL (CHANGE ISSUE ON DEMAND ENTRY) Change Special Remarks (7@S/) ENTRY: 7@S/CHANGES TO THE ITINERARY NOT ALLOWED Page

27 Change/Reopen Action Once a 7A field has been entered it can only be changed or re-opened by a special change format. This function is limited to designated CRTs in the host airline reservations office. ATO/CTO and general sales agents are not permitted to change the action field. Action Fields that can be re-opened are: dedicated CRT with a FA or SU duty code. Action ADK ACK TKT CNL Re-open Using TKT/PAR/RFD/PRF ACK/PAR/RKR/RFD/PRF TKT/PAR/PRF/RFD CNL/ACK/PAR/TKT/PRF/RFD ENTRY: 799@A/PAR/ /USD NOTE: This function opens only the last Action Field in a multiple Action Field PTA PNR. Once an action field has been opened or changed, any other action field that needs to be updated should be entered as usual without using the 799@A/ entry. Action fields that cannot be reopened: PRF, RFD, RLA Some action fields may be superseded. For example another action field can be entered to override the original action field without having to reopen it Page 23

28 1. Action fields that can be superseded: Action RLA ACK PAR Supersede using ACK/PRF/RFD PRF/RFD PAR/TKT/PRF 2. Action fields that cannot be superseded: TKT, PRF, RFD, CNL Page

29 International Prepaids International prepaids are formatted the same as domestic prepaids. The only difference in the construction of a domestic PTA PNR and an international PTA PNR is the 7F, 7F/AMNT- and the 7Z entries. 7F/ and 7F/AMNT- Entries Most international PTAs involve fare constructions using NUCs (Neutral Units of Currency) and involve currency conversions. As a result, the 7F/ and 7F/LADR- fields become a horizontal fare ladder, as the value of each segment must be included. The basic differences between domestic and international prepaids are: 1. International PTAs include the fare construction in the 7F/ and 7F/LADR- entries. 2. Fares are shown either in NUCs or in the currency of the country where the passenger actually boards the originating flight. Tax and total must be in the currency of the country where payment is received. EXCEPTION: U.S. Government ordered fares are always collected and issued in U.S. dollars (USD). 3. Banker s Buying Rate is mandatory when using currency conversions Page 25

30 Examples: Step Action 1 International PTA with domestic origination. ENTRY: 7F/SOTI VIE DL X/ATL Q5.00 DL MCO KKSPX3M DL X.NYC DL VIE Q5.00 KKSPX3M NUC END. ROE XF ATL3MCO3ATL3*CA-DL333 a. SOTI is the sale indicator (SOTI = Sold Outside/Ticketed inside) b. ROE is the Rate of Exchange (ROE) used to convert NUCs to Austrian Schillings (ATS). 2 Enter numeric amount. ENTRY: 7F/AMNT-ATS 9520 EQUIV USD RATE 1ATS/.08639USD TAX 3.46AT 6.00US 1.45XA 9.00XF 6.50YC 6.00 XY TTL USD NOTE: The base fare is shown in the currency of the country of origin. All other amounts are shown in the currency of the country where payment is made. 3 Due to the length of the entry, it is necessary to add the written fare amount in the Secondary Numeric Fare field. These two fields can be entered in one entry by using the end item (#) key. ENTRY: 7F/FARE-*TOTL USD EIGHT FIVE THREE POINT FOUR ONE Page

31 Since international PTA entries are fairly complex, it is recommended a PTA format guide or a rate sheet be used as a guide to properly format the entry. The only prepaids currently being sent abroad in U.S. dollars (USD) are only for military or government fares published only in USD. Step Action 1 International PTA where the origination is abroad, paid in the U.S., and there is more than one passenger traveling on different fare types. ENTRY: 7F/AMNT-HUF EQUIV USD RATE HUF/ USD TAX 2.90XA 13.00YC 12.00XY PTA TOTL USD ENTRY: 7F/FARE-*TOTL USD ONE SEVEN EIGHT NINE POINT NINE ZERO 3 ENTRY: 7F/FARE-ADULT HUF EQUIV USD TAX 1.45XA 6.50YC 6.00XF TKT TOTL USD ENTRY: 7F/FARE-CHILD HUF EQUIV USD TAX 1.45XA 6.50YC 6.00XF TKT TOTL USD Page 27

32 NOTES: 1. To clarify individual ticket values, each passenger type is shown with the base fare, tax, and total after the written amount in the same order as they were entered in the Fare Construction field. 2. The primary numerical fare 7F/AMNT- and the secondary Numerical Fare 7F/FARE- fields can contain up to seven (7) items: a. Base Fare b. Equivalent amount c. Banker s Buying Rate d. U.S. and foreign taxes e. Ticket total f. Other charges and expenses g. PTA total 3. There is no limit to the number of 7F/FARE- fields used to create a PTA, but each entry is limited to two (2) lines of characters. 4. Enroute expenses, excess baggage and other miscellaneous funds paid for in the U.S. and included in the PTA are shown in the primary Numerical Fare 7F/AMNT- field in U.S. dollars and included in the total dollar amount of the PTA. A secondary Numerical Fare 7F/FARE- field is then added giving the dollar amounts in the foreign currency equivalent. Miscellaneous Fare Information Entry 7F/SITI WAS TW PAR Q5.00 //FRA LH ATH C M NUC NUC END 7F/SITI NYC TW PAR Q5.00 Y /-FRA T NYC Q5.00 Y11 M NUC END XF JFK3 Explanation Surface or unflown segments included in a fare are defined by the symbols: // Open jaw or surface fare breaks are shown as: /- Page

33 Entry 7F/ SITI NYC TW PAR Q5.00 AF FRA Y2 M D NYCPAR NUC END XF JFK3 7F/SITI NYC TW ATH Q5.00 KHXAB TW NYC Q5.00 Q50.00 KHXAB NUC END XF JFK3 7F/SITI NYC TW MAD Q5.00 AZ ROM QHXPX M TW NYC Q5.00 QHXPX M S NUC END XF JFK3 Explanation Differentials are shown as: D Surcharges are shown as: Q Stopovers are shown as: S 7Z Entry International PTAs must always be sent as Contact and Issue (CNI). Issue on Demand (IOD) is never used for international PTAs. International PTA routing entries are identical to domestic routing entries with one exception, an international identifier is added to the end of the routing. The international identifier is: -I ENTRY: 7ZCNI/DUB/EI-I 7ZCNI/SCL/LA-I 0902 Page 29

34 7PTA Entry The PTA Number field for an international PTA must always include the currency code of the country where the payment is made before the total PTA amount. ENTRY: 7PTA /NW/USD PTA /AA/FRF PTA /DL/ITL Additional Collection Prepaids Reference: HELP PTA ADC There are times when additional collections are required to be sent as a prepaid. These usually fall in two categories: 1. Additional collection for a ticket re-issuance or update. 2. Additional collection for a fare construction on an existing prepaid. NOTES: 1. If a prepaid was not part of the original transaction and the additional collection is for a ticket reissue, the new PTA PNR should reflect this information. 2. In all cases, the additional collection PTA PNR must reflect complete information pertaining to the reissue. This would include the new fare construction and routing from the point of origin, as this information is required for a ticket reissue. 3. If the original PNR has already been purged, then there is no way of retrieving it in Worldspan. However, when sending an additional collection for reissue, the original PNR should be checked to see if it is still active, the purge date should be changed or bumped to ensure that a PNR cross-reference is possible. Page

35 4. It is the responsibility of the prepaid desk to make certain that complete and accurate information is sent in all cases of reissuance or upgrade. Additional collections for ticket reissuance or upgrades are set up like a normal prepaid. Care should be taken that all routing and fare information from the point of origin is included in the PTA. Additional Collection for a Fare Construction on an Existing Prepaid When an additional collection is necessary on an existing prepaid, the add collect PTA must be put into the original prepaid PNR using an ADC (Add Collect) format. An ADC PTA can be entered into a PTA PNR showing an action field response of ACK from and OAL or a non-automated host airline city. An ADC PTA cannot be entered into a PTA PNR showing an action field status of TKT. An additional collection must never be put into a closed or ticketed PTA PNR. If an additional collection is required on a ticketed PTA PNR, a new record must be created and the additional collection PTA is entered in the new PNR in the normal manner. The two PNRs are then crossreferenced. Worldspan will not accept an ADC entry if any other entry has been made in the PNR first. The first entry must be and ADC format entry to tell Worldspan an add collect is beginning Page 31

36 General Information 1. A PTA PNR must exist before an ADC PTA can be input. 2. Additional collection PTA formats follow the same basic rules of input as normal PTA entries, but include an indicator of ADC as part of the entry. 3. Six (6) mandatory fields are required for an ADC PTA. End Transaction is not permitted if any fields are missing. 4. An ADC PTA cannot be input in the same transaction with original PTA format entries. 5. Multiple ADC PTAs can be added to a prepaid, however; only one ADC PTA can be input at a time. Each ADC PTA must appear in the PNR in the sequence of input. 6. All ADC PTA entries can be changed prior to end transaction except for the ADC action field entry. The action field can only be changed by dedicated sets located at the central prepaid desk. 7. All ADC PTA entries can be changed after end transaction except for the ADC PTA number field. Mandatory ADC PTA Fields There are six (6) mandatory fields required for an ADC PTA. These fields are: Field New Routing/Fare Construction field 7F/ADC/ Explanation a. This field contains the routing or fare construction information that the ADC us covering and/or the form of payment. b. When an ADC is for a new routing or fare construction the complete routing, including city codes, carrier codes, and fare basis codes used in the new calculation should be in accordance with standard fare construction principles. Page

37 Field Amount field 7F/ADC/AMNT- Special Remarks Field 7S/ADC Message Field 7M/ADC Routing Field Explanation c. If the ADC is for other than a new routing or fare construction (excess baggage, pet charges etc.) only the form of payment is required. d. An asterisk (*) is used as a delimiter to separate the form of payment from the new routing or fare construction information. The form of payment will be the last item in this field and contains the same information as a normal PTA entry. a. The amount field contains the same type information as the normal PTA 7F/AMNTfield. The base fare, applicable taxes, and the total value in numerics, followed by an asterisk (*) and the total value spelled out are included. b. Where applicable, equivalent amount, currency exchange rate, and currency codes are required. a. The special remarks field is used to indicate the reason for the ADC. b. If a PTA special remarks field 7S/ exists on the original PTA PNR, it will not be affected by this entry. If it does exist, the normal 7S/ will not be allowed after an ADC special remarks field is input. The ADC message field is a single item mandatory entry. No other information can be entered in this field. Worldspan automatically generates a teletype message with the information contained in the ADC PTA fields. a. The routing field is exactly like the routing field used for the original PTA. It is used to indicate the city and airline where the ADT PTA is to be sent. There are two (2) items that are unique when used in conjunction with an ADC PTA Page 33

38 Field Explanation The routing field with CNI automatically places the PNR on the ARSO queue 17, category 0 (Q17*C0). If the ADC PTA is being sent to an OAL or host non-automated office, a teletype message will be generated. b. If an ADC is being added to a PTA PNR, the routing field can only be input only after one of the mandatory ADC items is input. If the routing field is input prior to the first ADC field, the ADC entry is not allowed and an error response will occur. PTA Number Field 7PTA Action Field 7A/ADK The ADC PTA number field contains the same type information as the original PTA number field except it has an indicator of ADC in the format: 7PTA /NW/25.00/ADC The action field acknowledgement code of ADK is used to show the acknowledgement of an ADC PTA when it has been an OAL or host non-automated office. This action field is required for each ADC PTA sent to an OAL or host non-automated office. This field can be input only at dedicated sets located at the central prepaid desk. When an ADC PTA is sent to an OAL or host non-automated office, that office sends a message back to the issuing office acknowledging receipt of the ADC PTA. Once the message has been received, the 7A/ADK field is used to update the acknowledged ADC PTA number from an ADC to an ADK. The action field is also updated to show an ADK and any free-flow information. Page

39 Field Explanation An ADK action field can be changed but not in the same transaction as input. An ADK action field can only be re-opened with a TKT, PAR, RFD, or PRF action code. Automated PTA Mask Reference: HELP 7/PA HELP PTAMASK Worldspan has created a PTA mask (template) to aide in the input of a prepaid into a PNR. The mask has all the fields required in order to successfully create a basic PTA. ENTRY: 7/PA A PNR must be displayed and the PNR must have a fare stored in the 4PQ field in order to use the automated PTA template Page 35

40 Step 1 ENTRY: 7/PA Explanation Response: ***WARNING*** THE PTA FARE FIELDS FROM THE AUTOMATED PTA PROCESS WILL BE BUILT BASED ON INFO FROM THE STORED FARE QUOTE 4PQ. IF YOU ARE NOT SURE OF THE ACCURACY OF THE INFORMATION STORED PLEASE CHOOSE A DISPLAY OPTION TO EXAMINE CURRENT DATA. >4*Q( >*A( >*I( >7/P( )> TO DISPLAY CURRENT STORE FARE QUOTE TO DISPLAY PNR TO DISPLAY ITINERARY TO INITIATE AUTOMATED PTA PROCESSING The mask list several PNR display options. These display options provide the opportunity to display applicable sections of the PNR, if needed, to ensure all information is correct prior to initiating the PTA processing. Page

41 Step Explanation 2 Enter 7/P to display the next screen, tab to or type: ENTRY: 7/P Response: (a) 7/PT-*************** AUTOMATED P T A *************** (b) PTA NUMBER: (...)(...) (c) TOTAL AMOUNT OF PTA INCLUDING TAX: (USD)( ) (d) FORM OF PAYMENT: (CK...) (e) AGENCY/STATION NUMBER: (...) 1-5 DIGITS (f) RESPONSIBLE RES OFFICE CITY CODE: (...) (g) PASSENGER WILL CONTACT AIRLINE: (Y) Y OR N ROUTE PREPAID TO FIRST BOARDPOINT: (Y) Y OR N COMPLETE DATA AND ENTER Field (a) (b) (c) (d) (e) (f) (g) (h) Explanation Standard automated PTA template header. First parenthesis: Airline numeric accounting code. Defaults to the airline issuing the PTA. Second parenthesis: PTA number including check digit. This information is automatically placed from the stored fare quote information in the PNR. The 4PQ entry must be used if pricing in a currency other than USD. The form of payment stored in the PNR is not read. This information must be entered manually. Enter the station number for the issuing location. The validating carriers local reservations office city code is entered. If the wrong code is entered, a mask with the correct city codes should appear. Arrow over to the correct city code and enter. Default for this field is Y (yes). If N (no) is entered, another template appears requesting passenger contact information. Default for this field is Y (yes). If N (no) is entered, another template appears to enter the prepaid routing information Page 37

42 Step Explanation 3 After completing the previous template, the prepaid purchaser information screen displays. ****************PREPAID PURCHASER INFORMATION************** >7/P/ NAME AND ADDRESS OF PURCHASER: ( ) NOTE: IF THE PTA WAS ORIGINATED BY A TRAVEL AGENT THE ADDRESS FIELD SHOULD CONTAIN THE ADDRESS AND PHONE NUMBER OF THE TRAVEL AGENCY. COMPLETE DATA AND ENTER 4 When the purchaser information template is accepted, the following response is returned: Response: ** AUTOMATED PTA COMPLETE PRESS ENTER TO REDISPLAY ** >*PTA This template advises Worldspan has accepted the information and the PTA is complete. In order to display the completed PTA, tab or move the cursor to the *PTA line and enter or type *PTA, then enter. PTA PNR Ticketing Field Ticketing time limits should be the only ticketing field used in a PTA PNR. Ticketing field entry for host origination: ENTRY: 8TL30//PTA.IN.FILE Page

43 Ticketing field entry for OAL origination: NOTE: ENTRY: 8TLSAN/UA3P/15AUG//PTA.TO.FOLLOW If an OAL is issuing the ticket, the entry above should be used to send the entire PNR itinerary to the originating carrier. Completion of MCO for PTA Purchase When a Miscellaneous Charges Order is required for a PTA, the following are instructions for completing the transaction. MCO Field Name of Passenger Type of Service for Which Issued Amount in Letters Currency Amount in figures To At Reservation Data Remarks Endorsements Restrictions Issued in exchange for Original issue Rate of Exchange Equivalent amount paid Explanation Passenger Name PTA Total fare, without PTA fee, spelled out in letters Three letter ISO currency code used to purchase PTA Total fare, without PTA fee, written in numbers Airline to whom PTA is being sent City PTA being sent to Record locator/airline/flight number/date/city pair Refund to purchaser only Purchaser name/address Purchaser address continued Blank If foreign currency, the ROE used, otherwise, leave blank Used only for foreign currency 0902 Page 39

44 MCO Field Tax on MCO Service Charge Total Issued in connection with Explanation Use only if taxes are not included in the total fare Amount of PTA service charge Total amount collected, fare plus service charge If PTA is issued in conjunction with a ticket, note the ticket number in this space, otherwise leave blank PTA Ticketing Automated Ticketing Entries Entry 4T$PT 4TT*#$PT 4TT15MAY#$PT 4T$PT*EE Explanation Basic entry (auto-priceable) Ticket for past ticket date Override ticketing date Ticket with additional document Continuation entries for response: *PTA DIFF USE 4T$PT/FOP-USD T$PT/CCVI USD T$PT/CA-USD T$PT*EE USD T$PT*EE /EE * T$PT/CK-USD48.00#N1.2 -or- 4TN1.2#$PT/CK-USD48.00 Page

45 Continuation entries for response: *TKT ISSUED - OVERLAY *** WITH TKT OR PAR TAB TO END OF LINE ENTER THEN ET 7A/***/ /FRF/CURRENCY MISMATCH Type in either TKT or PAR over the three asterisk (***), use the tab key to move to the end of the line and enter. Then End the PNR (E). Manual Ticketing Entries Modify the PNR to allow re-ticketing (for example, when a printer malfunctions): ENTRY: 799@A/PAR/ /USD0.00 To enter a PTA ticket number in Worldspan, the number must be preceded by the action field identifier 7A and a three-letter action code. ENTRY: 7A/TKT/ Obtaining the PTA Number When the ticket numbers of a valid host ticket have been input, the response is the PTA number as shown below. 7A/TKT/ /USD * PTA /AA/ The PTA number can then be entered in the Issued in Exchange for block on the ticket. The PTA number is not displayed until a valid host ticket number input Page 41

46 The typical sequence of a PTA ticketing transaction would be: Step Action 1 Display the PTA PNR 2 Generate the automated ticket 3 Compare the value of the ticket with the value indicated in the PTA fare field 4 Enter the ticket number in the appropriate action field 5 Enter the displayed PTA number in the Issued in exchange for block of the ticket 6 End Transaction 7 PTA is completed and attached to the auditors coupon PTA Purge Date System Purge - Normal PNR (No PTA) Worldspan currently purges non-pta PNRs 24 hours after: a. The date shown in the last flight segment in the PNR b. If all space in the PNR is open, the date shown in the last open segment With the addition of the PTA date fields to a PNR the purge date associated with the PTA PNR can either be equal to or greater than the purge date originally calculated for the PNR. Only a PTA PNR has the purge date shown in history. PTA PNR Sent to an Automated Host Location If the PTA PNR remains unchanged after the initial PTA entry in Worldspan, the purge date is based on the last segment of the PNR. When the action field codes of TKT/RFD/PRF/CNL are entered in the PTA PNR, the purge date remains unchanged. Page

47 PTA PNRS Sent to a Non-Automated Host Location or an OAL The purge date of the PNR is calculated according to the date shown in the last flight segment in the PNR. When the acknowledgment message is received and the PTA PNR is updated with the action field code of ACK, the purge date is recalculated by Worldspan to add thirty (30) days from the original date. OAL PTA Numbers If an OAL sends a PTA for an itinerary either booked with the host airline via a booking message or booked directly with the host by the passenger, upon entry of the PTA data and the OAL MCO Number, Worldspan automatically adds 30 days from the original purge date. Incomplete PTA PNR An incomplete PTA PNR has no action field code entered or an action field showing PAR (partial ticketing). On the day after the first segment in the PTA PNR, Worldspan places the PNR on queue 18 (Q18) of the city designated in the purchaser field. Worldspan also automatically changes the purge date to the 10 th day of the following month on the day the PNR would purge from the system. If no action is taken, Worldspan re-queues the PTA PNR to Q18 on the 1 st, 5 th, and 9 th day of the purge month. The same PNR can be queued to Q18 at least 4 times in a month. On the 12 th day of the purge month, with no action taken on the PTA PNR (either completing the action field or changing the purge date), the PTA PNR will be purged from the system. Should the action field be completed after the purge date has been changed either by the system or manually, Worldspan does not place the PTA PNR on Q Page 43

48 Changing the Purge Date When the PTA PNR is placed on Q18, the agent working the queue should review the PTA PNR and determine if the purge date should be changed. ENTRY: DATE This entry extends the purge date by an additional 30 days. International PTA PNR 7ZCNI is mandatory on all PTA PNRs with international space in the itinerary. If -I is appended to the 7Z field, the purge date is extended an additional sixty (60) days from the normal purge date calculation. Page