• No se han encontrado resultados

MÓDULO I. MARCO CONCEPTUAL Y NORMATIVO

1.1 Marco conceptual

1.1.2 Definiciones

) )

)

For more information on Service Bureau procedures, contact your Apollo/Galileo help desk.

Sending Records

Once TravCom is “Waiting to Receive Data from Galileo” (see Receiving and Processing Interface Data starting on page 5-9) you are ready to transmit the records from Galileo/Apollo. Enter the following command on Galileo/Apollo:

HMOM APOID-U

When the transmission is complete, and if you have not selected Process Data, Continue Receiving, you must take the Galileo/Apollo line down by entering the following on Galileo/Apollo:

HMOM APOID-D

) )

) )

If the TravCom Interface is set to continue receiving data you do not need to down the MIR until you are ready to shut down TravCom.

Re-sending Records

To retransmit records that have already been sent to TravCom use the following entries:

HQB/ACC/DS to display the accounting records Find the sequence numbers you wish to retransmit.

HQB/MU scrolls the screen up HQB/MD scrolls the screen down Have both TravCom and Apollo up and enter:

Interface with Your Reservation System HQT/1st sequence number - last sequence number

) ) )

)

For more information on resending records, see HELP HQB or HELP HQT in Apollo.

Interface Entries

Some of the entries described in this section are standard Galileo/Apollo formats. For further information on these entries, see your Apollo documentation.

Many of the entries provided by TravCom can be applied to a particular segment in the PNR. These entries are marked with an asterisk (*). To specify a segment, enter it after the field description. For example, T-EC/01 applies the Exception Code “01” to all sales in the PNR, whereas T-EC/*2/01 applies the Exception Code “01” only to the second sale.

Accounting line for client number:

T-CA-01„„„„004040

or you can enter multiple T- fields in one line, for example client #, agent #., exception code, dept., and low fare.

)

Note that TravCom can process client account fields entered on the T-CA, T-CD, T-SA or T-SD lines. These formats are standard Galileo/Apollo entry formats.

You can also enter the client account number using a T-CN/ remarks line. This format overrides the CA, CD, SA or SD line. For example, T-CN/1000.

Address lines:

TravCom can capture the name and address as entered in Apollo’s D- (delivery) or W- (address) fields. If both lines exist in the PNR then TravCom will process whichever line is first.

D-ABC COMPANY„„„„123 MAIN STREET, SUITE 300„„„LOS ANGELES CA„„ „„„90025 or

W-ABC COMPANY„„„„123 MAIN STREET, SUITE 300„„„LOS ANGELES CA„„ „„„90025 Accounting Lines -- General:

*T-VC/ VAT Rate Code. If your agency uses VAT or GST/PST (as defined in Files - Setup - VAT Setup) this field overrides the Tax Rate Code attached to the product code specified for the transaction.

T-BR/ Branch that you want your accounting to affect. If you are a multi-branch office and you may have one branch do the booking and another branch do the ticketing. The ticket will show on the 2nd branch's ARC report but the accounting will affect the branch number you specified in the entry.

For example, Branch 2 books the ticket but Branch 5 issues the ticket - the correct entry would be T-BR/2 so that Branch 2 gets the credit for the sale but it will affect the Arc Report for Branch 5.

T-DIV/ Division Number. For agencies that have the divisional option enabled (in Files - Setup - System Customization) the division to which this invoice belongs. Divisions affect only the Income Statement, not the Balance Sheet general ledger accounts.

For example, to show that this PNR should be processed to division 0002 enter T-DIV/0002.

*T-SF/ Selling Fare. If your agency uses bulk/discounted tickets or tracks the full fares on consolidator tickets (as defined in Files - Setup - System Customization) enter the base selling fare (not including taxes) per passenger. For example, to show that this ticket is being sold for $300.00 (plus taxes), enter T-SF/300.00.

T-DD/ The due date for a client invoice defaults to the invoice date. You can override the due date with a DD/remark line. The due date must be entered as a true date in a valid date format (for example T-DD/03MAR00). Alternatively, the due date can be entered as a number of days past the invoice date (for example, the due date is 15 days after the invoice date then you will enter T-DD/15). This will affect the Aged Schedule of Accounts Receivable.

T-PD/ The due date for a vendor invoice defaults to the invoice date. You can override the due date with a PD/remark line. The due date must be entered as a true date in a valid date format (for example T-PD/01MAR00). ). Alternatively, the due date can be entered as a number of days past the invoice date (for example, the due date is 15 days after the invoice date then you will enter T-PD/15). This will affect the Aged Schedule of Accounts Payable.

T-PPC/ The primary product code can be overridden by using the /PPC entry. This is useful when you want to identify the true product code for a transaction, such as an MCO, or a Tour Order.

For example you are issuing an MCO for your ARC report but it really is a tour sale, then you would want to affect your tour income and expense accounts by using the following:

T-PPC/TOUR or T-PPC/2

T-INV/ Invoice Number. This field overrides the standard Galileo/Apollo invoice number in the PNR. It is most commonly used when accounting was not transferred for a previously issued reservation invoice, or for a hotel/car reservation booking where you want to send a specific invoice number to TravCom.

Interface with Your Reservation System

Caution: This field should not be used with any command that would increment the TINS table. If this happens the CRS-generated number will not match the TravCom Invoice number attached to the accounting record.

T-NA/ Entry to override the product codes and vendors for non-ARC tickets. The entry is useful so non-ARC tickets will not appear on the ARC report. The entry is as follows:

NA/vc/PCn/PPCn/Vn

Where vc the airline number or code of the tickets to affect

/PCn the new product code for the ticket – will also change the primary

product code

/PPCn the new primary product code for the ticket /Vn the new vendor other than ARC

The /PC, /PPC, and /V parameters are optional. You only need to enter the relevant parameters.

T-PN/ This entry can be used to specify the penalty amount when entering a ticket exchange.

TravCom will subtract the amount you enter from the base fare and record it separately in the Penalty field.

Note that entering the penalty in this manner does not affect the accounting, statistics, or A.R.C. report. This field is for reference and custom reporting purposes only. The T-PN/

field can be applied to individual segments within the PNR

Accounting Lines -- Agent Commission/Productivity Tracking:

T-BA/ Booking Agent. This field overrides the standard Galileo/Apollo agent number. The BA field is used to override the booking agent only (not the ticketing agent). You can enter either the agent’s number or code as recorded in Files - Agents in TravCom. Do not use both the BA and AG fields in the same PNR.

T-TA/ Ticketing Agent. This field overrides the standard Galileo/Apollo agent number. The TA field is used to override the ticketing agent only (not the booking agent). You can enter either the agent’s number or code as recorded in Files - Agents in TravCom. Do not use both the TA and AG fields in the same PNR.

T-AG/ Agent. This field overrides the standard Galileo/Apollo agent number. The AG field is used to override both the booking and ticketing agents. You can enter either the agent’s number or code as recorded in Files - Agents in TravCom. Do not use the AG field in the same record as the TA or BA fields.

T-OS/ Outside Sales Agent #1. This field overrides the standard entry for this client account.

Normally, TravCom will insert the O/S agent number that has been referenced on the

client’s record in Files - Clients on the In House tab. You can override the automatic entry with the T-OS/ (O/S Agent 1 number) remark field. The commission percentage assigned cannot be overridden in the PNR. It is not necessary to enter the OS field to every PNR for an outside sales agent.

This entry affects both sales and vouchers in the PNR.

T-OS2/ Outside Sales Agent #2. This field overrides the standard entry for this client account.

Normally, TravCom will insert the O/S agent number that has been referenced on the client’s record in Files - Clients on the In House tab. You can override the automatic entry with the T-OS2/ (O/S Agent 2 number) remark field. The commission percentage assigned cannot be overridden in the PNR. It is not necessary to enter the OS2 field to every PNR for an outside sales agent.

This entry affects both sales and vouchers in the PNR.

Accounting Lines -- Handwritten Tickets:

Tax fields MUST be used when transferring a hand written ticket and the command HB:DIDAD/FS T-TK-8025123123 Handwritten ticket number. (Standard Galileo/Apollo format)

T-TK-8025123123-124 Handwritten Conjunction ticket number. (Standard Galileo/Apollo format) T-PF- Pre-Paid Fee including taxes (used with T-TK- for handwritten MCOs). This is

used on the Galileo/Apollo invoice and for TravCom accounting. The entry assumes 2 decimal places. For example, enter T-PF-3988 for $39.88. (Standard Galileo/Apollo format)

T-PFX- Pre-Paid Fee Taxes. Enter as T-PFX-3.25CA2.70XG. This field must immediately follow the T-PF field in the PNR. (Standard Galileo/Apollo format)

Commission amount is always entered as a dollar amount in the HB: command. For example, a one-way ticket with a commission cap of $25.00 would have commission of $25.00 plus 10% of the PTA charge (currently $50.00) to a total of $30.00.

The Galileo/Apollo standard format for MCOs and Tour Orders will be processed through interface only if there is an air segment included. However, the validating airline will always be credited with the

productivity for the sale, which may be incorrect for many such documents. You may also enter these sales in TUR segments or MS lines.

Accounting Lines -- Ticket Exchanges:

Tax fields must be used with all ticket exchanges (add collect, even exchange or refund).

T-EX-999.99US3.00XF999.99XT Per person tax field. Can be used for multiple exchanges. However, if taxes differ on tickets then you must do ticket exchange separately and modify the T-EX field. (Standard Galileo/Apollo format) HB:FEX/Z$1107 Command used to complete Exchange format in Apollo. Actual

Commission earned must be entered in this transaction for TravCom

Interface with Your Reservation System to be correctly updated. For an even exchange you can enter the /Z$0 or omit the commission entry. (Standard Galileo/Apollo format)

*T-PN/ Penalty Paid. Penalties are used with Ticket Exchanges. This amount will be recorded in TravCom in the Penalty field and the Published fare (and Selling fare if relevant) will be decreased by this amount.

Accounting Lines -- Service Fees:

T-SF- Service fees paid by cash including taxes only appear on the invoice, or if paid by credit card enter T-SF-26.75/CC. (Standard Galileo/Apollo format. Note that this accounting line will not be picked up when interfacing to TravCom.

Corporate Reporting Fields:

T-CD/ Corporate Department number. If the client number entered into this PNR is a

corporate or government account that requires the use of department numbers, enter the department number in this format. TravCom can also process the department number from the client account line (CA, CD, SA or SD line, as described on page 5 – 5-43).

*T-PO/ Purchase Order number. If the client requires purchase order numbers on corporate reports, the agent can enter their PO number here.

*T-RF/ Reference Fare. This is usually defined as the full coach fare for purposes of calculating the Savings amount on corporate reporting. TravCom can also process this information from the standard Galileo/Apollo entry, DS-. Enter the full price, including taxes, per passenger.

*T-LF/ Low Fare. This is usually defined as the lowest fare possible for the trip based on the client’s travel policies. It can be used to calculate the additional amount you could have saved the client under other circumstances. This field is usually used in conjunction with the Exception Code field. Enter the full price, including taxes, per passenger.

*T-EC/ Exception Code. This is normally used for Corporate and Government accounts, to explain why a particular traveler did not purchase the lowest fare, as entered in the LF field. The agent should enter the 1- to 2-digit Exception Code, not the full description.

For example, if your exception code group shows “01” represents a Saturday night stay was required to get the lowest fare, the agent would enter T-EC/01.

Exception Codes are defined in TravCom in Files - Setup - Exception Codes and cross-referenced to corporate and government accounts as required in each client’s record in Files - Clients - In House tab. For more information on setting up, maintaining and printing Exception Codes see Exception Codes in Chapter 3, Maintaining Your Agency Setup and Client File Maintenance in Chapter 4, Maintaining Agency Data Files.

*T-FF/fields Free Field(s). Free fields are used for any information you require on the record that does not have a pre-defined field in TravCom. For example, corporate clients that require employee numbers or other references, or internal tracking you wish to

maintain.

Free fields are entered in a string, separated by slashes and can be used on any custom report for sorting, selecting, or calculating.

For example: T-FF/12345 TravCom will understand free field 1 as “12345”

T-FF/SMITH V JONES/SITE 3/JASON TravCom will understand free field 1 as “SMITH V JONES” and free field 2 as “SITE 3” and free field 3 as “JASON”

To skip free fields, enter a slash as a placeholder. For example:

T-FF/SMITH V JONES//JASON TravCom will understand free field 1 as “SMITH V JONES” and free field 3 as “JASON” - free field 2 is not being used in this PNR.

Note that as free fields are specific to your custom reports, they can be used for different purposes for different clients. For example, ABC Corporation may require employee number, whereas XYZ Company requires internal billing data. Since the reports for each company will include only their own records, you can use Free Field 1 for both pieces of data.

*T-FFX/fields Additional Free Fields. Although TravCom allows us to 100 free fields on any record, your CRS may not allow enough characters on a single remark line to allow you to enter all of the data you wish to track. If this is the case, use the FFX entry to extend the original free field line. This line should follow the FF remark line, and you can use as many FFX lines as required to complete the data you want to transfer.

*T-FF14/ Specific Free Field. If you are not using all free fields in order, you can specify the free field TravCom should insert the data into. For example, if you enter T-FF4/SUSAN, TravCom will understand free field 4 as “SUSAN” and will create the Free Field line in TravCom as ///SUSAN (three empty free fields preceding SUSAN).

) ) )

)

Free Field format can be used in any combination. For example, if you want to enter 12345 into free field 1 and SUSAN into free field 4 you can enter either

T-FF/12345///SUSAN or T-FF/12345 T-FF4/SUSAN

*T-TC/ Transaction Code. This is single-character field for any sorting or selecting purposes you have in your custom reports. For example, you may want to track all sales generated by certain types of advertising such as newspaper ads, yellow pages, referrals, etc.... Transaction Codes do not need to be defined in TravCom and you can use different TC entries for different clients if required.

*T-RC/ Routing Code. This is 2-character field for any sorting or selecting purposes you have in your custom reports. For example, you may want to track all sales to a specific geographical area such as Canada, the Orient, South Pacific, Europe, etc.... Routing Codes do not need to be defined in TravCom and you can use different RC entries for different clients if required. For agencies located in Canada the Routing Code

Interface with Your Reservation System of the Routing Code is 0 or 9 the GST/PST on Commission will be calculated at the normal rate. Anything other than 0 or 9 will leave the GST/PST on Commission as zero.

*T-GSA/ Government Service Authorization number for this sale, if applicable. If you have, Government clients enter the contract number here.

T-NP/ The number of passengers for a single transaction can be entered in a NP/remark line (for example if you have a tour order for 3 passengers the entry will be T-NP/3).

T-MS/ A miscellaneous segment line used as an optional method of accounting transfer, replacing the TUR segment. See the section Optional Method of Accounting Transfer starting on page 5 – 55.

Auxiliary Accounting Segments (TUR Lines):

TUR Segments are used in Apollo to transfer all non-A.R.C. sales such as Tours, Cruises, Service Fees, etc.... They can also be used to transfer refunds for A.R.C. TUR segments are a standard Galileo/Apollo format and accomplish the same function as the TravCom MS lines. Do not use both TUR lines and MS lines to transfer sales to TravCom, as TravCom will receive and process two copies of the same sale.

) ) )

)

For TUR segments to update TravCom, you must enable the Process Miscellaneous Segments flag in the Interface - Install Interface function. See Installing the Interface starting on page 5-2.

The following list includes all of the possible indicators you can use in a TUR segment to transfer the correct accounting information to TravCom. These indicators are also used in T-MS lines. For more information on T-MS lines, refer to the section Optional Method of Accounting Transfer starting on page 5-55.

You can use a maximum of 43 characters between the double lozenges. The indicators can be used in any order, with the exception of the product code that must appear first and within the first segment.

Remember: for refunds, enter negative dollar amounts.

/PC Product Code. Enter the number or description of the product being sold. The

description must match the description for the product code in Files - Setup - Product Codes. For example, /PCTOUR or /PC02.

/V Vendor account. Enter the vendor number or sort key from the vendor record in Files - Vendors.

If you are entering the TUR segment for a Tour Order or MCO, this field does not need to reflect A.R.C. as the vendor. If you have entered the Product Code as 0 (A.R.C.) the record will be transferred correctly and show on the A.R.C. report. Enter the correct vendor number for tracking purposes, such as American FlyAAway or Delta Dream Vacations.

/A Sale amount (base published fare, without taxes). If the entry is just /A500.0 then the default currency will be used.

/AUSD Sale amount in a foreign currency. Use this format only if you have multiple currencies set up in TravCom in Files - Setup - Currencies.

/SF Selling Fare. If you handle bulk or discounted tickets enter the base fare (not including taxes) that you are charging the client for this sale.

/SF Selling Fare. If you handle bulk or discounted tickets enter the base fare (not including taxes) that you are charging the client for this sale.

Documento similar