XML Select supports Client File Plus (Galileo) and PRO-files (Apollo), which are an automated storage system. The ClientFile_2 transaction accesses Galileo Client File and Apollo PRO-File information and can be used to create a Client File, delete a Client File, retrieve Client File data for a user, to maintain existing Client File data, or to use Client File data in the process of creating a Booking. (As Client File and PRO-File are synonymous terms, the term Client File is used to represent both in this document.) This feature is typically used in association with a corporate application to support corporate travel requirements.
ClientFile transactions can be used in conjunction with Galileo by Travelport's TravelScreen™ product, to supply a record for both personal and business-related travel preferences, such as preferred airlines and rental car types. Furthermore, some of the additional transactions such as Currency Conversion and Reference Point Transactions may be creatively used to aid customers in planning a trip. You can use any of the transactions individually, or in combination, to invent other innovative planning services.
The hierarchy for Client File is Agency, Business, and Personal. Each Business File is associated to an Agency File, and each Personal File is associated to a Business File. A Business File can exist without a Personal File, but not vice versa.
ClientFile can be used to:
Retrieve Client File data for a user
Maintain existing Client File data
Use Client File data in the process of creating a Booking
Create a new Business or Personal Client File
Delete an existing Business or Personal Client File.
For Business or Personal Client File Maintenance and Business File Deletion, the
Client File must first be retrieved. Multiple Personal Files (up to 40) for a
particular Business File can be deleted in one request with no prior retrieval
required.
The stored information can be transferred into a PNR/BF apart from the booking process, and serves as a shortcut to manually entering the traveler's information. The movement of client file/profile information into a PNR/Booking File can be accomplished from either a displayed client file/profile or by a "blind move."
Client files/profiles consist of three (3) hierarchical levels:
Agency File Record (MAR) - Contains details about the travel provider, such as telephone numbers, out-of-office hours, and emergency numbers.
Business File Record (BAR) - Contains details about a specific business account, such as telephone numbers, ticket delivery address, payment policy, required invoice layout, etc.
Personal File Record (PAR) - Contains personal information about the
traveler, such as telephone number, address, and credit card number. A separate
PAR is normally created for each person traveling for a company for which a
BAR exists.
This version of ClientFile includes the new request sub-elements <ClientFileFixedLineData>, <ClientFileMaintenanceMods>, and <ClientFileVariableLineData>.
To review Client File Traveler Identification Values (TID Values), see the Industry Code Reference > Client File TID Values page.
In the <ClientFileFixedLineData> tag (CFFD KLR), in the <MoveInd> field, in the request, Transfer Line Codes of Y, N, and O, R, and B are allowed. (Transfer Code of X is unique to Structured Data Maintenance and is required when deleting a Client File Line.)
TID values in the <ClientFileFixedLineData> tag, in the <DataType> field, that have no Apollo or Galileo Action code are not accepted for Maintenance. Exceptions to that are the 0031, which is a text-only field, and the 0045, which is a blank line. See the TID Values in the Industry Code Reference > Client File TID Values page.
In a sessionless environment, ClientFile_2 cannot be used to create, maintain, or delete Client Files in another pseudo with which your pseudo has a selective access agreement. For example, if pseudos XX1 and YY1 have a selective access agreement, and pseudo XX1 tries to create a Client File in pseudo YY1 within a sessionless environment, a 'VERIFY AUTHORIZATION' error is returned. However, the same request made in a sessioned environment will be successful.
ClientFile_2 cannot be used to move profiles in a sessionless environment. If you need to move profiles in a sessionless environment, use PNRBFManagement.
API Developer Notes can assist you when developing applications that use Galileo Web Services and XML Select. The following table lists the API Developer Notes that are applicable to this transaction and provides a description. Each document is a link to the PDF file:
| Document | Description |
| Using TravelScreen Plus to Create, Update, and Delete PRO/Client Files | Use TravelScreen Plus to work with Apollo PRO Files and Galileo Client Files. |