Fares
Transactions can be saved to a batch several ways.
After creating batch transactions, you can:
Click the
button. The transactions will be saved with the status of Not
Validated.
Click the
button. Transactions will be validated and saved to the batch. Transactions
that do not pass the validation process will hold a transaction status
of Validated with Errors.
Transactions may also hold a status of Validated
with Warnings, meaning that a transaction can be applied to
the Fare Master but a discrepancy was found in the initial validation.
For example, if the transaction is for a fare from MEX
(Mexico City) to WAS (Washington, D.C.) and the fare amount was
typed using USD (United States dollars) as the currency, the transaction
would receive a warning because the currency does not match the origin
city. If this is your intention, the transaction can be applied (you
can ignore the warning if you wish to). If this was not your intention,
you can change the currency code.
Click the
button. The transactions will be saved to the batch, validated, and
applied to the Fare Master. Transactions that do not pass the validation
or application process will hold a status of Validated
with Errors.
Click the
button. The transactions will be saved to the batch, validated, applied
to the Fare Master, and the batch will hold a status of Available
for Filing (international fares or add-on fares) or Awaiting
Distribution (US/CA fares). Batches that hold a status of Available for Filing must be filed
in ATPCO's Government Filing System (GFS). Transactions that do not
pass the validation, application, or release process will hold a status
of Validated with Errors.
However, a released batch may not be reused. For more information,
see Release a Batch.
Navigate to another screen. Transactions will be automatically saved to the batch.
Changes or additions made on this screen will be saved
whenever a user moves to a new page or clicks
,
,
,
, or
.
Related Topics