Fares

Submit to Batch

A criteria set can be submitted by clicking the button, which displays the Submit to Batch pop-up dialog. This submission will process all the Inclusions, Exclusions, Changes, and Matches group boxes coded in your criteria set and will create a fares batch with transactions.

You can view query results and submit them to a batch if you plan to distribute them. Once changed fares are submitted to a batch, they are considered transactions. If you click the button, a pop-up dialog box opens, which allows you to create a new batch or submit the fares to an existing batch.

Select one of the following Batch Action Types (required to submit to batch):

• Hold— Creates a batch that allows you to store transactions that will not be validated at this time.

• Validate— Creates a batch and sends the Changed Fares through the validation process. A status of Validated, Validated with Warnings, or Validated with Errors will be attached to the transactions. Low Fare Check is an option. During validation the Low Fare Check is enabled.

• Apply— Creates a batch, sends the Changed Fares through the validation process, and attempts to apply the transactions to the database. Just because a record is validated or validated with warning does not mean it will apply to the database.

During the apply process, if the system does not encounter any apply errors then the transactions will reach an end status of Applied or Applied with Warnings. Fare sequences with an Applied or Applied with Warnings status is visible in the Fare Master to the owning carrier or authorized organization. Any transaction that results in errors will have an end status of Validated with Errors and will not be in the Master file.

• Release— Creates a batch, sends the Changed Fares through the validation process, applies the transactions to the database, and makes the batch Available for Filing (International scope) or Available for Subscriptions (US/CA scope).