/PROG_HDR/

Program Description:

This programs prints all of the scheduled documentation out for each tour on the correct date.

Program Explanation:

Vendors usually receive some of the following documents:

* Tour Orders

* Passenger lists

(Sometimes with detailed passenger information)

* Rooming lists

* Itineraries

* Prepayments (handled by A/P system)

* Recaps

Passengers usually receive some of the following documents:

* Tour Vouchers (usually copies of tour orders)

* Passenger lists

* Tickets (handled by TK system)

* Rooming lists

* Itineraries

* Checklist of items (Flight bags, baggage tags, etc)

Documentation can be printed on the:

1 - Booking date

2 - Date deposit is received

3 - Date all services are confirmed ("OK")

4 - Date final payment is received

5 - Tour Finalization date (Close tour) (AP also updated) 6 - Final Documents date (Send final docs)

7 - Ticketing date (TK also updated)

8 - Special date 1

9 - Special date 2

10- Departure date (AP, AR, GL, TK, TOUR and BK also U/D)

11- Cancellation date (Documentation to be processed)

Some dates do special updating:

5 - Tour Finalization date

- Check all bookings are paid in full and status = OK

- Write/update all of the A/P estimates for the tour

7 - Ticketing date

- Transfer information to be ticketed to ticketing

10- Departure date

- Update agency sales, type information

- Write/update all A/P departure estimates

The finalization knows what to print by the Documentation file maintenance screen in the tour header maintenance. When the action date comes up, the system looks at the documentation file to see what should be printed on this date. After the documents have been created, the action date is set to the next item in the documentation file.

The finalization system knows what format to use for a document by the text file name in the document screen. If the name is blank, the system uses the name in the header file and if that name is blank, the system will use the default in the booking control file. If the filename is a number, then the corresponding default format will be used.

The finalization knows how to scan the file information by the document type code in the documentation screen. The following table lists all the document type codes:

Order Code Examples

TOUR,HOTEL

R Hotel Request form (internal)

H Hotel Tour Orders

V Hotel Vouchers

TOUR,LAND VENDOR

S Land & Transportation Request form

L Land & Transportation Tour Orders

W Land & Transportation Vouchers

TOUR,AIR

Q Air Request form (internal)

T Ticket Request form (internal)

TOUR,BOOKING

B Booking Confirmation

I Tour Itinerary

C Tour Checklist

TOUR,BOOKING,PAX

P Passenger list

O Rooming list

NOTE: On the Finalization date, before anything is run, the system will check every booking to make sure that they are paid in full and the status is OK.

NOTE: On the Finalization date, A/P is updated before the documentation is printed. This way the A/P voucher reference number can be included on the tour orders. This will make payments much easier. This also updates A/P so prepayments can be made.

NOTE: On the ticketing date, the ticketing information is transfered to the ticketing system for each passenger (if it is not there already). The ticketing system will handle it from there. It will print the tickets or the ticket requests and keep track of commissions and overrides.

If a booking is modified or cancelled after tour documents have been sent, the tour finalization is scheculed to re-run. This program will create all of the back-documents and compare them to the versions at the original date. If they are different, then the system will and print ** Revised ** on the new documents.

Usually, this program will run in a batch nightly. In the morning, operators will load each type of paper and print the documents which were created during the run.

/SCREEN11/

Program Operation:

The Cut-off-date is the last action date to check.

Following is a detailed explanation of each process:

Order Code Examples

TOUR,HOTEL (Also See BK_H_VOUCHER)

R Hotel Request form (internal)

H Hotel Tour Orders

V Hotel Vouchers

The document selected is printed once for each hotel in the hotel detail

This is the information available to documents using these formats:

Voucher Number - After finalization date only

Arrival Information - Carrier, Flight no, Date, time (Starts search two days before arrival; Any flight with matching arrival City or First flight on arrival day. If no flights on arrival day, then takes flight from previous day. Stops on arrival day.

Departure Information - Carrier, Flight no, Date, time (Starts search on departure date; Any flight with matching departure city or First flight on departure day. If no flights on departure day, takes flight on next day. Stops on next day.

Hotel Information - Reads the hotel information record.

TOUR,LAND VENDOR (See BK_L_VOUCHER)

S Land & Transportation Request form

L Land & Transportation Tour Orders

W Land & Transportation Vouchers

First, All the land and transportation for this tour are scanned to get a starting and ending date for each vendor involved (20 max). Then a tour order/whatever is printed for each vendor, printing only the detail that belongs to the vendor.

The other information is the same as Hotel Information except: Hotel Information - If specified, will list all hotels, dates and length of stays.

The following documents actually print in BOOKING order:

TOUR,AIR

Q Air Request form (internal)

T Ticket Request form (internal)

TOUR,BOOKING

B Booking Confirmation

I Tour Itinerary

C Tour Checklist

TOUR,BOOKING,PAX (See BK_PAX_LIST and BK_ROOM_LIST)

P Passenger list

O Rooming list

/USE: BK_V_HOTEL/

/USE: BK_V_LAND/