Rules Upload Record 2 (for Category 25)

Transcription

1 Rules Upload Record 2 (for Category 25) Highlighted rows represent differences in the Upload layout for Record 2 for Category 25 and the outgoing ATPCO Subscription documentation layout for Record 2 for Category 25. The Record 2 for Category 25 is similar (aside from the Tariff and Cat No field) to the Record 2 for all categories (except Category 10 and 25) up until byte 30 (that is, up until Loc 1). For the sake of consistency, please refer to the above Record 2 for all categories (except Category 10 and 25) for bytes Note that the key fields for the Record 2 for Category 25 are exactly the same as the Record 2 for all categories (except Category 10 and 25). Updating Public/Private Fare By Rule Tariffs with Public/Private Table Numbers (this refers to cross-edits E, F and G in the table number field). Copyright 2002 by Airline Tariff Publishing Company All rights reserved Page 01 - Rules Upload Record 2 for Fare By Rule (Category 25) Revised 2010

2 Public Table Number Public Fare By Rule Tariff (Permitted) Private Fare By Rule Tariff (Not Permitted) Private Table Number Private Fare By Rule Tariff (Same Carrier = Permitted, Different Carrier = Not Permitted) Public Fare By Rule Tariff (Same Carrier = Permitted, Different Carrier = Not Permitted) Page 02 - Rules Upload Record 2 for Fare By Rule (Category 25) Revised June 2010

3 TARIFF and CAT NO Fields TARIFF FBR Tariff Number: A number indicating the Fare By Rule tariff number to which the data applies Required (3 digit numeric) 2. Must be a valid Fare By Rule Tariff (see ATPCO Automated Rules Subscription Documentation Appendix H for a list of public tariffs for private tariffs contact the carrier for an applicable list) 3. Must not be an ATPCO or Vendor-owned tariff CAT NO Category Number: A number indicating the rule category that is referred to by this record Required 2. Must be 025 Bytes 31+ LOC 1 Location 1 Geographic Specification: A. Required when there is data in Loc 2 (bytes 45-58) TYPE: A code indicating the type of geographic specification that will be found in the following field: Must be Blank or value A, Z, N, S or C A. Required if there is data in Loc 1 (bytes 32-36) B. Required if the Directional Indicator (byte 126) for any recurring segment that applies to the record is value 1, 2, or 3. C. Required when there is data in Loc 1 (bytes 45-58) Page 03 - Rules Upload Record 2 for Fare By Rule (Category 25) Revised June 2010

4 GEO SPEC: The geographic specification. It may be any one of the following: AREA: A one-digit numeric area designator Must be value 1, 2, 3 or Blank A. Required when Type is value A ZONE: A numeric value assigned to a non-standard geographic description of cities, states, countries, sub-continents and/or traffic conferences. COUNTRY: The standard IATA country code. CITY: The standard industry city code. STATE: The standard Postal state code. LOC 1 ZONE TABLE NO. 978: A numeric pointer to a table containing multiple geographic specifications. It is present when the fare applies from multiple points Must be a valid zone or Blank (see ATPCO Automated Rules Subscription Documentation Appendix C geo zones) Must be a valid country code or Blank (see ATPCO Automated Rules Subscription Documentation Appendix D countries) Must be a valid 3 character standard industry city code (must be left-justified) or Blank Must be a valid state code or Blank (see ATPCO Automated Rules Subscription Documentation Appendix E states) Must be value OR an existing Geo Zone Table A. Required when Type is value Z A. Required if Type is value N or S B. Must be value US or CA when Type is value S A. Required if Type is value C (must be left-justified) A. Required if Type is value S A. When value , bytes must be Blank. B. Must be a zone table owned by the carrier specified in bytes LOC 2 Location 2 Geographic Specification: Page 04 - Rules Upload Record 2 for Fare By Rule (Category 25) Revised June 2010

5 TYPE: Same as for LOC Must be Blank or value A, Z, N, S or C A. Required if there is data in Loc 2 (bytes ) B. Required if the Directional Indicator (byte 119) for any recurring segment that applies to the record is value 4. GEO SPEC: Same as for LOC 1. NOTE: A $ coded in place of an Area, Zone, Country or State in conjunction with a valid code of the same type in the LOC 1 specification indicates any Area, Zone, Country or State other than the one coded in the LOC 1. LOC 2 ZONE TABLE NO. 978: A numeric pointer to a table containing multiple geographic specifications. It is present when the fare applies from multiple points (SAME AS LOC 1 SEE bytes 31-44) (SAME AS LOC 1 SEE bytes 31-44) RESERVED Reserved for future expansion FARE APPL Fare Application: Indicates the application of fares used in calculated Fare by Rules Must be value D, I or Blank JT CXR TBL NO Joint Carrier Table # 997: A numeric pointer to a table containing the joint carriers participating in the rule Must be value OR be an existing Joint Carrier Table A. Joint Carrier Table is not permitted unless the tariff (bytes 3-5) is an international tariff or both US/CA domestic and international. DATES Effective and Discontinue Dates: Page 05 - Rules Upload Record 2 for Fare By Rule (Category 25) Revised June 2010

6 EFF: The date on which the record is effective. DISC: The last date on which the record is effective Required 2. Must be 0YYMMDD format 3. Must be <= current date plus 2 years 4. Must be a valid calendar date See Section Change Transaction Processing and Date Logic Required 2. Must be 0YYMMDD format (may be ) 3. Must be a valid calendar date (may be ) See Section Change Transaction Processing and Date Logic A. When Tariff (bytes 67-69) is an EDOT tariff must be => current date B. When Tariff (bytes 67-69) is a non- EDOT tariff must be > current date (Systems should contact the carriers uploading data to determine the EDOT [Effective Date of Today] tariffs they use. These tariffs are within the US.) A. Must not be more than one day less than the effective date (bytes 81-87). RESERVED Reserved for future expansion NO APPL Category Not Applicable: A code indicating that no specific rule data applies to fares identified by this record Must be value X or Blank RESERVED Reserved for future expansion DATA TABLE STRING Data Table String: A series from 0 to 200 data table numbers and relational indicators. Page 06 - Rules Upload Record 2 for Fare By Rule (Category 25) Revised June 2010

7 # SEGS: The number of occurrences of the table field in this record Must be value A. Must match the number of occurrences of bytes B. Must be value 000 when the No Appl field (byte 102) is value X C. If value 000, there must be no data in beyond the segment count. RI: Relational indicator used to imply a condition between data tables CAT NO: The number of the category to which the following table applies Must be value =, :, &, /, * = (THEN) : (IF) & (AND) / (OR) * (ELSE) Must be value , , 025, or Blank A. Must not be value =, :, &, /, * if there is data in bytes B. See Section Stringing Logic and Coding Conventions Page 07 - Rules Upload Record 2 for Fare By Rule (Category 25) Revised June 2010

8 TBL NO: A number that links this record to the associated table containing the data elements that state the condition of the footnote Must be value OR a valid existing table number on the ATPCO database A. Required if CAT NO (bytes ) is present B. Must be a valid data table for the Category specified in bytes C. Must not be a data table where the Tariff (bytes 3-5) is a first ticket date restricted tariff (See Appendix E Tariff Identification List) and Cat No (bytes ) is 015 and the data table contains data in the first ticket date field OR contains an Override Date Table with data in the first ticket date field (Note: Override Date Tables are present in Categories 1-9, 11-23, 25, 26-29, 31, 33, 35, and Record 1). D. Must not be a data table where the Cat No (bytes ) is 025 AND the data table being sent is public AND the data table is updating a private fare by rule tariff (bytes 3-5) E. Must not be a data table where the Cat No (bytes ) is 025 AND the data table being sent is private AND the data table is updating a private OR public fare by rule tariff (bytes 3-5) AND the carrier whose data is being sent (bytes 6-8) is not the same as the carrier that owns the table. I/O: Inbound-Outbound indicator Must be value I, O or Blank A. Must be Blank when Cat No (bytes ) is Category 006 or 007 or Blank Page 08 - Rules Upload Record 2 for Fare By Rule (Category 25) Revised June 2010

9 DI: Directional Indicator: A code indicating the direction of travel or the direction from which travel originates Must be value 1, 2, 3, 4 or Blank A. Must be Blank when LOC 1 (bytes 32-44) is the same value as LOC 2 (bytes 51-58) B. Must be Blank when Cat No (bytes ) is Category 006 or 007 or Blank Page 09 - Rules Upload Record 2 for Fare By Rule (Category 25) Revised June 2010