Ticket Data Entry Detail MCDB

You will be presented with this screen when you insert or amend a ticket in the current batch.

To create a new ticket you must:

Enter a Card Number. A ticket requires a card number. The customer account linked to this card will then be defaulted from the card
Enter a ticket reference
Enter a Transaction Type and Sub Type
Enter the Ticket transaction date (defaults to today's date)
Enter the Carrier airline number
Enter the Approval Code
Enter the Point of sale code (the agent that sold the ticket)
If Accounts Receivable Internal structures are being used, enter a Location code
Enter the Gross value in the Ticket Currency. See Below for further details on Currency

Other details can optionally be entered at this level, including Port Tax and Discount details, other ticket details (such as number in party, passenger name etc.); collection and payment details and dunning details.

When you are happy with the Ticket details, click Edit | Segments to amend or insert segment journey details for this ticket. Click Edit | Insert to enter new segment details on Screen MCDC.

On return from MCDC, click Update to update this ticket's details and go on to the next ticket.

Use of Currency

You can enter a third currency for tickets which represents the currency in which the customer paid for the ticket. Consequently, a rate type and rate is required to convert this currency value to the customer's currency. The rate type will default from Card Billing Controls with the currently effective rate based on the ticket date.

If the customer's currency is not your company base currency, then a second rate type and rate will be required to convert to company base value. These details will default based on Accounts Receivable Company Controls.

Interline Processing

If you intend to use Interline Matching functionality, then you must enter an Invoice Number against the ticket. This number is used by the interline matching process to identify tickets making up an interline sale and along with the ticket value will be used to match to other airline submissions.

If you are entering ticket details on an Interline Payable or Interline Receivable customer, then the ticket will automatically have its memo flag set. This is to prevent any impact on debtor's control and General Ledger postings.

PBI Processing

A plan code may be entered against a ticket which will be used to generate a PBI plan from the ticket details. This feature will be used when a ticket is to be paid on an instalment basis over a pre-determined period of time. The instalments may also be paid by a DDI Mandate if specified on the controls when creating the plan code.

Screen Specific Actions

Action	Displays
EDIT SEGMENTS	Click Edit \| Segments to create or amend ticket journey segment details for this ticket.
EDIT CURRENCY CALC	Click Edit \| Currency Calc to display the calculations involved for a particular currency conversion. You need to have the cursor positioned on one of the currency values on the screen (Customer or Base) to be able to use this action.
EDIT ERROR MESSAGES	Click Edit \| Error Messages to view all the error messages generated previously for this Ticket. This action is particularly useful when amending a batch entered off line as all the originally occurring error messages are listed.

If not described elsewhere in this topic, click in the field and press F1 to view a description. See Common Fields for more information.

Fast prompt allows you to quickly view a list of options for certain fields.

NOTE Field visibility can be defined by your System Administrator, so not all fields documented may be shown.

See Using the Command Line on opening the screen without going through the menu.