A tag attached to Record 1 stating that the rules are incomplete or cannot be used for autopricing.
1. The status assigned by the system to provisions that have been updated but have not yet been processed through GFS and subsequently sent in Subscriptions. See also filed data. 2. See non-filed.
Currency code XXX used to file mileage awards
Unaccompanied child (usually age 5-11 or 8-11).
ATPCO term for fares constructed by adding specified and add-on amounts together. Also called constructed.
Records in batch processing that do not pass update. The update step applies the fares to the master file. If there are difficulties, then the fare will not be applied to the master file. Instead, it becomes an update error record. Update errors occur, for example, when a carrier tries to increase a fare that does not exist, cancel a fare that is already canceled, or add a new fare that already exists.
The United States and Canada.
Fares that are published for travel within the continental United States, between the continental United States and Alaska/Hawaii, within Alaska/Hawaii, between the 50 United States and Canada/Puerto Rico/Virgin Islands, within Canada/Puerto Rico/Virgin Islands, or between Canada and Puerto Rico/Virgin Islands. Also called local fares.
The seven-character user name for access to ATPCO systems.
A group of conditions, similar to inclusive tables, created in order to speed processing for frequently used fields (location, routing, rule, footnote, and market) in a query.
Any grouping of locales using cities, states, countries, industry zones, or areas defined by a data owner and assigned a unique Table 978 number. This zone ID can then be used as a single location when creating fares in Category 25.