User Guide

/ Client Files /
CONTENT

page

INTRODUCTION ........................................................................................................... 3

HIERARCHY STRUCTURE .......................................................................................... 4

CLIENT FILE BUILD

PROCEDURE ................................................................................................................ 6
BUILD QUICK FUNCTIONALITY .................................................................................. 7
FORMATTING ............................................................................................................... 7
CHANGES ..................................................................................................................... 8
DYNAMIC UPDATE ...................................................................................................... 9
DISPLAY
Regular display .................................................................................................... 13
Partial Client File title ........................................................................................... 14
PRINT CLIENT FILES ................................................................................................... 14
RENAME ....................................................................................................................... 15
COPY............................................................................................................................. 16
DELETE ......................................................................................................................... 17
REINSTATE .................................................................................................................. 17
HISTORY ....................................................................................................................... 18
USAGE ......................................................................................................................... 18
NON UTILISATION LIST ............................................................................................... 18
OPTIONAL FUNCTIONALITY TABEL .......................................................................... 19

CLIENT FILE MOVES

MOVES .......................................................................................................................... 20
RELATED MOVE .......................................................................................................... 22
ASSOCIATION .............................................................................................................. 22
TRAVELSCREEN PERSONAL INFORMATION TABLE .............................................. 23
CLIENT IDENTIFIERS .................................................................................................. 24
SINGLE ITEM FIELDS .................................................................................................. 25

2
INTRODUCTION
Client Files (also called Local Files) enables you to store customer information in the Galileo system. The
added advantage is that this stored information in Galileo can easily be transferred into the booking file.

The two most important types of Client Files are:

CUSTOMER DATA CLIENT FILES : Is the main type of files that an agency will use. They contain
information concerning business and personal travel details such as telephone nbrs, addresses ...

N. Name field
P. Phone field
T. Ticketing field
R. Received field
W. Written address field
D. Delivery field
M. Mileage membership
F. Form of payment
V. Vendor remark ( for carrier YY )
NP. Notepad
SI. Service information : - OSI ( e.g. SI.YY* free text )
- Manual SSR (e.g. SI.SSRPSPTAAHK1/P9875445/BE/.)
- Programmatic SSR ( e.g. SI.VGML )
RI. Itinerary remarks : unassociated and associated ( ass. RI entry in CF : RI.S.*free text )
DI. Documentation/Invoice field
RA Related address
RB. Review booking
FREE FORM REMARKS ( not transferable )

INFORMATION CLIENT FILES : These files simply contain information commonly used by an agency. It
can be used to build simple databases with airline phone numbers, embassy addresses.

3
HIERARCHY STRUCTURE OF CLIENT FILE

Client File consists of 3 levels: AGENCY FILE - BUSINESS FILE - PERSONAL FILE

AGENCY
FILE

BUSINESS BUSINESS BUSINESS

FILE FILE FILE

PERSONAL PERSONAL PERSONAL PERSONAL PERSONAL PERSONAL PERSONAL PERSONAL PERSONAL

FILE FILE FILE FILE FILE FILE FILE FILE FILE

AGENCY FILE : The travel agency is the highest Client File level. The Agency File can
only be created by Galileo. It contains the agency name and pseudo city
code. Once created, it is possible for the agent to add further information.
The 1st line of the Agency File should always be the agency telephone
number.

DISPLAY AGENCY FILE : C*

BUSINESS FILE : Business Files are indexed to the Agency File, therefore an Agency File
must exist before a Bus. File can be built. It is built by the agent and
usually contains business information of corporate accounts such as
company policy, telephone numbers, billing information etc.

DISPLAY BUSINESS FILE : C*BUS. FILE TITLE

PERSONAL FILE: Personal Files are indexed to a specific Bus. File, therefore a Bus. File
must exist before a Pers. File can be created. It is built by the agent and
usually contains the client's personal preferences such as special meal
request, Mileage Plus numbers, personal telephone and address.

DISPLAY PERSONAL FILE : C*BUS. FILE TITLE-PERS. FILE TITLE

4
DISPLAYED AGENCY FILE

X5D /GAL BRUSSEL SA TRAINI 01DEC92

AGENCY FILE
1Y/P.BRUT*GALILEO TRAVEL 02/513 07 07
2N/FAX 02/514 19 58
3Y/DI.CR-1
END OF DISPLAY

DISPLAYED BUSINESS FILE

X5D /GAL BRUSSEL SA TRAINI/SONY 28MAY97

BUSINESS FILE
1N/SONY BELGIUM
2Y/P.BRUB*02/456 78 95
3N/FAX 02/456 80 59
4N/GENERAL MANAGER : MR HARAKARI
5N/W.AVENUE GALILEE 25*P/1120 BRUSSELS
6Y/F.INVOICE
9O/NP.ONLY BUSINESS CLASS IF WITHOUT SURCHARGE
20YB/SI.LH*CORP CARD 12345B
END OF DISPLAY

DISPLAYED PERSONAL FILE

X5D /SONY-HARAKARI 28MAY97

PERSONAL FILE
1Y/N.HARAKARI/TMR
2N/LANGUAGE : ENGLISH
3N/NATIONALITY : JAPANESE - PASSPORT NBR : 15A214A2
5Y/P.BRUP*012/14 50 88
10O/F.S
14B
15YP/NP.SEATING: S.NW
20N/---------MILEAGE MEMBERSHIP CARDS---------
21Y/M.KL1234564
22Y/M.SR98545012
23B
30R/SI.ORML
END OF DISPLAY

Each line of an Agency, Business or Personal File contains a line number, a transfer code and eventually
an optional qualifier.

5
CLIENT FILE BUILD BUSINESS AND PERSONAL FILE
3 Steps :1. - Create BUSINESS/PERSONAL FILE title

2. - Enter the line numbers and transfer codes followed by the content.

3. - Save and end

1. Create BUSINESS/PERSONAL FILE title :

Create Business File : CFB/BUS. FILE TITLE

Create Personal File : CFP/BUS. FILE TITLE - PERS. FILE TITLE

min 2, max. 21 characters

Response: proceed

2. Enter the line numbers, transfer codes and content :

1NB/Company name
| | |
| | optional qualifier
| transfer code
line number
2YB/P.BRUB*02 5130707
4YF/F.CK

Line number: The line number assigned to data in both Bus. and Pers. Files should be numerically
consistent. This will eliminate the need to display the Bus. or Pers File prior to the Move
entries.

Max. 200 lines per Agency / Business / Personal File

Max. 64 characters per line

Transfer code :

Y - Always move lines : These lines will always move into the booking file

O - Optional move lines : These lines will only move into the booking file when requested in the input.

R - Related move lines : These lines contain passenger/segment related BF fields.

- Programmatic SSR`s and associated RI`s : R transfer code
mandatory
- Mileage Membership : R transfer code optional *

N - Never move lines : These lines never move into the booking file

B - Blank lines : To improve layout of the Client File

* It is advisable to avoid R lines - if possible - because it requires an additional entry to move these lines into
the Booking File !
6
Optional qualifier : Optional. Is used to display the Client File by selected areas.

Content :
N. Name field
P. Phone field
T. Ticketing field
R. Received field
W. Written address field
D. Delivery field
M. Mileage membership
F. Form of payment
V. Vendor remark ( for carrier YY )
NP. Notepad
SI. Service information : - OSI ( e.g. SI.YY* free text )
- Manual SSR (e.g. SI.SSRFQTVYYHK1/YY12345-LEE/AMR)
- Programmatic SSR ( e.g. SI.VGML )
RI. Itinerary remarks : unassociated and associated ( ass. RI entry in CF : RI.S.*free text )
DI. Documentation/Invoice field
RA Related address
RB. Review booking
FREE FORM REMARKS ( not transferable )

NOTE
- The content of Y,O or R coded lines must be Galileo Booking File formats.

- It is advisable that Booking File single item fields ( T.,R.,W.,D.,F. ) are only set to transfer
code Y in one level ( Bus. or Pers. File ) IF a Multiple Move will be applied afterwards.

3. Save and end : CE

BUILT QUICK FUNCTIONALITY

It is possible to build and save a Client File ( of max. 12 lines ) just using one input :

BQB/Bus. File title +2N/.....................+5Y/P.BRUB*....................+7O/.........

or
BQP/Bus. File title - Pers. File title+1Y/.......................+3O/.......................

Save and end ( CE ) NOT required.

FORMATTING

It is possible to include special characters ( Som and Tab Stop ) for some Booking File fields ( Phone and
Notepad field ) in a Client File.

Procedure
- While creating a Client File :
- enter FMT before creating the line with special characters.
- create the line : 2Y/NP. :*S.NW:- ( :* represents a Som while :- is a Tab Stop )

- While updating a Client File :

- enter C@FMT before adding/modifying the line with special characters.
- add/modify the line : C@2Y/NP. :*S.NW:-

7
CHANGES TO CLIENT FILES

WHILE CREATING IN A RETRIEVED CLIENT FILE

ADD A LINE

6Y/P.BRUB*02 555 22 22 C@6Y/P.BRUB*02 555 22 22

CHANGE A LINE

11OA/NP.SMOKING AISLE SEAT C@11OA/NP.SMOKING AISLE SEAT

CANCEL A LINE
6 C@6

RE-ARRANGE LINES

/2L10 C@/2L10
(line 10 will be renumbered into line 3)

INSERT A LINE

/10 C@/10
11N/PREFERS KLM C@11N/PREFERS KLM

CHANGE TRANSFER CODES

50Y/ C@50Y/

CHANGE ADDRESS BY SUBFIELD

50Y/D.2*1050 BXL C@50Y/D.2*1050 BXL

UNNUMBER
CUN C@CUN

RENUMBER

CNM C@CNM

TEMPORARY UNNUMBER

C*R/*

NEW NUMBERING FROM A SPECIFIC LINE

CN20 C@CN20
8
DYNAMIC UPDATE

Dynamic Update provides the ability to update multiple Client Files (all belonging to the same
agency) simultaneously.

Because careless use of Dynamic Update can have a major impact on ALL your Client Files we suggest it
should be used in a disciplined environment!
Access to the Dynamic Update functionality is controlled by:
- the security profile of your sign on (updated by Galileo)
- the activation of the appropriate field in the Optional Functionality Table (see page 19)

Dynamic Update facilities are:

Add a line
Insert a line
Delete a line
Number/Unnumber/Renumber

To access the Dynamic Update Request Fill-in Format: C*DU/

C*DU/ DYNAMIC UPDATE MENU - X5B

ADD A LINE C*DU/A

INSERT A LINE C*DU/I
DELETE A LINE C*DU/X
REPLACE A LINE C*DU/R
NUMBER, UNNUMBER, RENUMBER C*DU/N

IGNORE I

9
ADD A LINE :

Tab to ADD A LINE in the previous fill-in format or enter C*DU/A

C*DU/A DYNAMIC UPDATE - X5B ADD A LINE

CUSTOMER DATA:. ITINERARY:.
 TRANSFER CODE:. CLIENT ID:. QUALIFIER:. SEGMENT ID:.
 DATA: ........................................................
..............................................................
...............................................................
...............................................................
 AGENCY. ALL BUSINESS. ALL PERSONAL.
 ENTER HERE TO SUBMIT FOR UPDATE
 OR SELECT BUSINESS AND/OR PERSONAL TITLES

Select the type of Client File you want to update: place an X after the Customer data File field.

 Specify the characteristics of the line being added:

Transfer code (mandatory) :Y-O-N-B-R

Client Identifier (optional) : from 1 to 9
Qualifier (optional) : any alpha character
Segment Identifier (mandatory but only used with Itinerary Files)

 Enter the content of the line being added (e.g.: NP. free text)

 Specify the level to be updated (all Business or all Personal Files)

 Enter to confirm your request for updates if one of the fields from line  are selected.

 Enter if the update is only required for selected Business and/or Personal Files.
Another fill-in format will appear:

C*DU/A SELECT TITLES LIST BUSINESS PERSONAL

1........................................... . .
2........................................... . .
3........................................... . .
4........................................... . .
5........................................... . .
6........................................... . .
7........................................... . .
8........................................... . .
MORE TITLES PREVIOUS SCREEN
ENTER HERE TO SUBMIT FOR UPDATE

10
In the Select Titles List the Business and/or Personal File titles to be updated, must be entered.
For each File title the level (Bus. or Pers.) must be specified by placing an X in the Bus. and Pers. File
columns.

C*DU/A SELECT TITLES LIST BUSINESS PERSONAL

1ROLEX...................................... X X
2IBM-JOHN................................... X X
3SIEMENS-LEE................................ . X
4NIKE....................................... . X
5........................................... . .
6........................................... . .
7........................................... . .
8........................................... . .
MORE TITLES PREVIOUS SCREEN
ENTER HERE TO SUBMIT FOR UPDATE

ROLEX : Update the Business File ROLEX and all attached Personal Files.
IBM-JOHN : Update the Business File IBM and the Personal File JOHN.
SIEMENS-LEE : Update the Personal File LEE (belonging to the Bus. File SIEMENS).
NIKE : Update all the attached Personal Files belonging to the Bus. File NIKE.

Enter to submit for update and a prompt appears:

CONFIRM DYNAMIC UPDATE Y OR N
Y Dynamic Update has been accepted for processing.
N Dynamic Update ignored.

DYNAMIC UPDATE PROCESSING

Once the Update request has been confirmed by you, the following process takes place :

- The request is logged to the Dynamic Update Queue (controlled by Galileo)

- When the process begins, the Dynamic Update Queue will reflect IN PROGRESS. To display
this status : C*DU/S*

- When the Dynamic Update is completed a Quality Report is created and send to the Supervisory
Queue of the agency (enter QS but do not forget to remove this Q by afterwards by entering QRS)
This report informs you whether the update was fully successful or not.
The report can also be accessed directly by doing CL*DU/QR

- Before another Dynamic Update request can be made, the active Quality report must be canceled:
C*DU/QX

- The history on all Dynamic Updates is kept for 30days and can be displayed by entering C*DU/H*

11
INSERT A LINE

Tab to the line INSERT A LINE of the fill-in format obtained by C*DU/ or enter C*DU/I
The same procedure as described under ADD A LINE must be followed.
The only new fields in the fill-in format are:
- new line number
- insert after line number

NOTE: The lines that follow the inserted line will be renumbered.

DELETE A LINE

Tab to the line DELETE A LINE of the fill-in format obtained by C*DU/ or enter C*DU/X
A similar procedure as described under ADD A LINE must be followed.

REPLACE A LINE

Tab to the line REPLACE A LINE of the fill-in format obtained by C*DU/ or enter C*DU/R
The same procedure as described under ADD A LINE must be followed.

LINE NUMBERING/UNNUMBERING/RENUMBERING

Tab to the line NUMBER/UNNUMBER/RENUMBER of the fill-in format obtained by C*DU/ or enter
C*DU/N
A similar procedure as described under ADD A LINE must be followed.

12
DISPLAY CLIENT FILE

AGENCY FILE : C*

BUSINESS FILE : C*BUS. FILE

PERSONAL FILE : C*BUS. FILE - PERS. FILE

C*B.FILE - P.FILE:1-4 ( only line 1 to 4 )
C*B.FILE - P.FILE:T-Y ( only transfer codes Yes )
C*B.FILE - P.FILE:Q-A (only opt. qualif. A )
C*B.FILE - P.FILE :C-3 ( only client ident. 3 )
C*B.FILE - P.FILE *ALL ( all levels of the Cl. File )
C*B.FILE -P.FILE .B ( only transfer code B or
optional Qualifier B, whichever comes first )

ACTIVE CLIENT FILE : C*R

LAST REFERRED BUS.FILE : C*B

LAST REFERRED PERS. FILE : C*P

LIST OF ALL AGENCY FILES : CLM ( alpha/numeric listed )

with the same group code.

LIST OF ALL BUS. FILES : CLB ( alpha/numeric listed )

CLB/L (all Bus. Files starting with a specific character
e.g. L - min 1/ max. 21)

LIST OF ALL PERS.FILES : CLP/BUS.FILE ( alpha/numeric listed )

RELATED TO A SPECIFIC BUS. CLP/BUS. FILE-T ( all Pers. Files starting with a
FILE specific character - min1/max 21 )

13
DISPLAY USING PARTIAL CLIENT FILE TITLE :

BUS. FILE while C*BUS. FILE ( min 2 first characters

title partially unknown followed by an * )

PERS. FIL while C*BUS.FILE - PERS. FILE ( B. File :

Bus. File title partially unknown min. first 2 characters followed by an * )

PERS. FILE while C** - PERS. FILE

Bus. File title completely unknown

PERS. FILE while C*BUS.FILE - PERS. FILE ( min 2 first

Pers. File title partially unknown characters followed by an * )

LAST REFERRED LIST CL*L ( similar titles list is displayed if a

file title is incorrect or incomplete )

BUS. FILE OR PERS. FILE FROM LIST CL*1

PRINT CLIENT FILES

Client Files can be printed easily by adding P- before any display entry.

P-CLB
P-C*BUS.FILE
.....

14
RENAME CLIENT FILE TITLE

AGENCY FILE

Can only be changed by Galileo

BUSINESS FILE
3 steps:

1. Display BUS. FILE : C*BUS. FILE TITLE

2. Enter CRB/OLD BUS FILE:NEW BUS. FILE

3. Confirm with Y

PASSENGER FILE

3 steps:

1. Display PERS. FILE : C*BUS. FILE-PERS. FILE

2. Enter CRP/OLD PERS. FILE:NEW PERS. FILE

3. Confirm with Y

15
CLIENT FILE COPY

BUSINESS FILE
3 steps :

1. Display BUS. FILE: C*BUS. FILE TITLE

2. Enter CFB/C/NEW BUS. FILE (copies the complete Bus. File)

or
CFB/C/NEW BUS. FILE: 2.5-10 ( copies the selected line numbers )
CFB/C/NEW BUS. FILE:2-10 ( copies the selected line numbers , even if some line numbers do not exist

3. CE (ends the newly created Client File )

PERSONAL FILE

3 steps:

1. Display PERS. FILE: C*BUS. FILE-PERS. FILE

2. CFP/C/BUS. FILE-NEW PERS. FILE (copies the complete Pers. File to any specified existing
Business File )
or
CFP/C/BUS. FILE - NEW PERS. FILE:2.4.7.20 (copies the selected line nbrs)
CFP/C/BUS. FILE - NEW PERS. FILE:2-20 (copies the selected line nbrs, even if
some line nbrs do not exist)

3. CE (ends the newly created Client File)

COPY BETWEEN CLIENT FILE LEVELS

A BUSINESS FILE INTO A PERSONAL FILE :

1. Display Business File : C*BUS. FILE
2. CFP/C/BUS. FILE-PERS.FILE ( with or without specifying line numbers )
3. CE

A PERSONAL FILE INTO A BUSINESS FILE :

1. Display Personal File : C*BUS.FILE-PERS.FILE
2. CFB/C/BUS. FILE (with or without specifying line numbers)
3. CE

16
DELETE CLIENT FILES
PERSONAL FILE

2 steps :

1. CXP/BUS. FILE-PERS. FILE : deletes 1 PERS. FILE

2. Confirm with Y for Yes

CXP/BUS. FILE-P.FILE:P.FILE:P.FILE : delete several PERS.FILES from the same BUS.FILE

BUSINESS FILE

3 steps :

1. Display BUSINESS FILE: C*BUS. FILE

2. CXB/BUS. FILE : deletes the Business File

3. Confirm with Y for Yes

NOTE: - By deleting a Business File all the associated Personal Files will be deleted !

- A deleted Client File remains inactive for 30 days. During this time the CF can be reinstated.

REINSTATE CLIENT FILES

CLXB : Displays a list of all inactive Business Files

CXB@BUS. FILE : Reinstates the inactive Bus. File ( all the associated Pers.Files
will also be reinstated )

CLXP/BUS. FILE : Displays a list of all inactive Personal Files attached to a

specific Bus. File

CXP@BUS. FILE-PERS FILE : Reinstates the inactive Personal File.

17
CLIENT FILE HISTORY
C*H : Displays the history of the Client File ( the Client File must be displayed first )

The Client File History reflects all modified, deleted or added data on a maximum of 200 lines. The most
recent changes will be on top.

Each line will be preceded by an action identifier which indicates the action that has been taken.
DA data added
DM data modified
DO data originator ( = creation of the Client File )
DX data deleted
DR data reinstated

USAGE
2 steps:
1. Display the Client File ( Agency, Business or Personal )
2. Enter C*U

Usage displays statistics about:

- number of times the Client Files have been accessed
- number of Dynamic Update requests
- number of Active and Inactive Client Files
- number of Active and Inactive Travelscreen Preferences

CLIENT FILE NON UTILISATION LIST

Client Files not accessed for a period between 6 and 13 months become TRANSITIONAL Client Files. Once
a Transitional File is 14 months old it will be purged from the system.
Purged Client Files are NOT available for reinstate!

CLTB List of Transitional Business Files

CLTP List of Transitional Personal Files

CT*BUS. FILE or Displays the Client File without affecting the

CT*BUS. FILE-PERS. FILE transitional status.

To cancel the Transitional status simply display the Client File the regular way :
C*Bus.File or C*Bus. File - Pers. File

18
OPTIONAL FUNCTIONALITY TABLE

This table determines the way in which your Client Files are displayed and updated.

C*OT/ : displays table

C*OT/
X5D OPTIONAL FUNCTIONALITY TABLE

DESIGNATED PCC 1G/....

ORDER OF DISPLAY PBA ABP COMBINATION OR D
ALIGN FORMAT OF DISPLAY N Y/N/D
ASSOCIATION L F/L/N/D
DYNAMIC UPDATE N Y/N/D
CHANGE:
DISPLAY RECORD N Y/N/D
 Choice of settings: Yes - No - First - Last
Designated PCC

Designated PCC The set up of this table can be done by 1 designated agency.
All the other agencies of that same group can input the PCC of the
designated agency to become the same set up.

Order of display The default order when displaying all levels of a Client File is Personal -
Business - Agency File. It is possible to reverse this order by entering ABP.

Align format of display The Client File can be displayed aligned or unaligned.

Association Selects which Travelscreen preferences will be active when multiple

Client Files have been used.

Dynamic update Provides the ability to update multiple Client Files simultaneously

Display record If set to Yes the Client File will automatically be redisplayed after
an update, to reflect the change that has been made.

19
CLIENT FILE MOVE
The MOVE function is designed to move information stored in the Client File into a Booking File.
This Move function is only possible for lines bearing Y, O and R transfer codes (N transfer code = Never
move).

There are 4 types of Moves:

MULTIPLE MOVE:

Moves all the Y lines from the specified level and any higher level

Moves any selected O lines from the level that is entered.

e.g. A Multiple Move of a Personal File will move all the Y lines from that Personal File and -
eventually - selected O lines , but also all the Y lines from the Business File into the BF.

SINGLE MOVE:

Moves all the Y lines and any selected O lines from the specified level.

e.g. A Single Move of a Personal File will move all the Y lines and -eventually- selected O lines
into the BF. Nothing will be moved from the Business File.

The agency phone field of the Agency File will always be moved

RELATED MOVE:

Moves only the R lines into the Booking File

SELECT MOVE:

Disregards the Y transfer code and treats all Y lines as O.

Therefore all line numbers required to move must be specified.

20
The Move can be performed in 2 ways :

- Displayed Move : The Client File is first displayed on screen and then moved into the
Booking File.

- Blind Move : The Client File is moved into the Booking File without being displayed.

Symbols

// Must be added to the PCC when using a Blind Move.

During the Move data, line numbers and Booking File fields can be appended.
The following symbols are used :
st
/+ To append data and/or line nbrs and/or the 1 Booking File field to the Move entry of a
Business or Personal File.
st
//+ To append data and/or line nbrs and/or the 1 Booking File field to the Move entry of an
Agency File.

* To append the agents name to Agency Files telephone field.

+ As usual: to append several Booking File fields.

DISPLAYED BLIND
CLIENT FILE MOVE

MULTIPLE Agcy. File CM/+*name CMT/PCC//+*name

MOVE CMT/PCC//+*name/+N.
Bus. File CMT/B.FILE/+*name
CMT/B.FILE/+*name/+R. .
Pers. File CMT/B.FILE-P.FILE/+*name
CMT/B.FILE-P.FILE/+*name/+R. .

SINGLE Agcy File CMM/+*name CMMT/PCC//+*name

MOVE
Bus. File CMB/+*name CMBT/B.FILE/+*name

Pers. File CMP/+*name CMPT/B.FILE-P.FILE/*name

SELECT Agcy File CMM/S/+2-4.6 CMMT/PCC//S/+2-4.6

MOVE
Bus. File CMB/S/+2-4.6 CMBT/S/B.FILE/+2-4.6

Pers. File CMP/S/+2-4.6 CMPT/S/B.FILE-P.FILE/+2-4.6

CM/R
RELATED All Files CM/R/P-2 (See next page for full details)
MOVE CM/R/S-1/P-2

21
RELATED MOVE (For all types of files ):

CM/R Moves related lines into the BF for ALL segments and applicable
to ALL passengers.

CM/R/P-2 Moves related lines into the BF for ALL segments and applicable
to the specified passenger ( nbr 2 ).

CM/R/S-1 Moves related lines into the BF for the specified segment ( nbr 1 ) and
applicable to the 1st passenger.

CM/R/P-2/S-1 Moves related lines into the BF for the specified segment ( nbr 1 )
and applicable to specified passenger ( nbr 2 )

Important notes!

When moving passenger/segment related line a name field and/or itinerary must exist.
If your agencies main activity is to move Personal Files (probably containing the name field) the
following procedures is advised

 Moving passenger/segment related lines ( SI. or M. ) : the CM/R entry needs to be done
AFTER the original move entry but BEFORE ending the Booking File.
E.g.: CMT/BUS.FILE - PERS. FILE (enter)
CM/R (enter)

 Moving segment related line ( RI.S.* free text ) the /R entry can be attached to the move
entry, specifying the segment.

E.g.: CMT/BUS. FILE - PERS. FILE/R/S-2

After the Booking File is ended the related lines can only be moved using the SELECT Move entry.

Related lines and moves can be avoided very often by using Travelscreen (see next page)

ASSOCIATION

When a Client File has been moved into a Booking File this Client File will become associated to this
Booking File. The line CLIENT FILE REFERENCES EXISTS *CF is added, and tabbing to this entry
will give access to the Client File.

CMREF@ : removes the Client File Reference Line from the Booking File, to prevent access to
the Client File from the Booking File.

NOTE : CMREF@ does NOT remove the Booking File fields that have been entered by means
of the original Client File Move !

22
TRAVEL SCREEN - PERSONAL INFORMATION TABLE
1. CREATE

- Display Personal File

- Enter CP*PI and fill in the Personal Information Table :

CP:PI PERSONAL INFORMATION GALI-MAES

SPECIAL SERVICE REQUIREMENTS
CODE T TEXT CODE T TEXT
1..... *................ 2..... *................
3..... *................ 4..... *................
5..... *................ 6..... *................

SEAT DATA
. NON-SMOKING OR SMOKING ( ENTER N OR S )
. WINDOW OR AISLE ( ENTER W OR A )

Code : enter SSR code

T : enter A for all flights or M if only for flights with meals
Seat data : enter N for non-smoking or S for smoking seats and W for window or A for aisle
seats

2. MODIFY / DELETE PERSONAL INFORMATION TABLE

- Display Personal File and enter CP*PI

- To modify : replace existing codes with new ones

- To cancel : replace the codes with dots.

3. ACTIVATE TRAVELSCREEN

- Move Personal File

- Book segments
- Enter CPM to activate the Personal Information table : the requested seat types and SSR`s will be booked.

4. REACTIVATE TRAVELSCREEN

After a rebook or adding segments to the Booking file, Travelscreen can be reactivated by doing CPM
again.

5. DISPLAY TRAVELSCREEN/PERSONAL INFORMATION TABLE

Enter CP*P after the move of the Personal File or after displaying the Personal File.

23
CLIENT IDENTIFIERS
Client Identifiers can be useful for Client Files that contain more than 1 passenger.
A Client Identifier (ranging from 1 to 9) can be added after the transfer code of a line.

X5B /ROLEX-JONESFAMILY 03JUN97

PERSONAL FILE
1YC1/N.JONES/AMR
2YC2/N.JONES/JMRS
3YC3/N.JONES/KMISS
4YC1/P.LONB*0171 99887 PHONE OF JONES MR
5YC2/P.LONB*PHONE OF JONES MRS
6YC1/W.MR JONES
BAKERSTREET
LON
P/ABC123
7Y/T.T*
8YC1/NP.CLIENT PAYS CASH FOR PERSONAL TRVL
9RC1/SI.VGML
10RC2/SI.SPML*NO EGGS
15RC1/M.LH12345646
16RC2/M.SR1478444
END OF DISPLAY

The Client Identifiers are used to indicate which lines must be moved (1 Client Identifier can move several
lines).
All kind of Moves (Blind - Displayed - Single - Multiple - Related) may be used BUT only lines with the
specified Client Identifier will be moved!

CMT/ROLEX-JONESFAMILY/C-1 ONLY the Y lines with Client Identifier 1 will be

or transferred.
CM/C-1

CMT/ROLEX-JONESFAMILY/R/C-1 ONLY the R lines with Client Identifier 1 will be

or transferred.
CM/R/C-1

CM/R/C-1/P-1 ONLY the R lines with Client Identifier 1 will be

transferred, passenger related to the 1st passenger in
the BF (M.P1/LH12345646 and SI.P1/VGML)

CM/R/C-2/P-2 If a Related Move is needed for a 2nd passenger in the

Booking File, this Move must be done in a 2nd action

CM/R/C-1/P-1/S-3 ONLY the R lines with Client Identifier 1 will be

transferred, Passenger and Segment related to the
1st passenger and the 3rd segment of the BF
(M.P1S3/LH12345646 and SI.P1S3/VGML)
24
SINGLE ITEM FIELDS

Single item Booking File fields are :

Form of Payment ( F. )
Received ( R. )
Ticketing ( T. )
Written Address ( W. )
Delivery Address ( D. )

If a Client File move entry is made, the system will check if all the lines can be moved.
If single item fields are present twice, the move will be performed as follows:

1... The single item field already exists in the Booking File when the Move entry is made

The duplicate fields from the Client File will be moved to the Booking Files in Notepad en
Related Address Fields.

2... Multiple Move : both the Personal and Business File contain duplicate single item fields

The Personal File single item field(s) will be moved into the Booking File and the Business File
single item field will be moved into a Notepad or Related Address field.

25