Task: Client File/PRO-File Move

This task moves data from Client File into a Booking. Data can be moved:

From a single Client File level (“Blind” or “Display” move).
From multiple Client File levels based on the Client File hierarchy (“Blind” or “Display” move). See the Quick Info for details on the Client File hierarchy.
By “Select Line” using specific lines from a single level (specific lines can be moved from more than one level but must come to the host as three separate <ClientFileMods> tags, one for each level requested).
As "Related" with or without Passenger and/or Segment relation.
To include Passenger Relation information for Secure Flight type data.

For clarification purposes, a “Blind” move is a process that will first retrieve a Client File and then move the Client File data to the Booking, all within one call to the host. A “Display” move is a two part process which requires Client File Display request in a <ClientFileMods> tags followed by a “Display” move request in a separate <ClientFileMods> tags. More details on the differences between “Blind” and “Display” move will be given throughout this document.

Section 1: Short Answer

Transaction Name:

ClientFile_2

Can any other transaction(s) perform this same task?

This is the only transaction available to move data from Client File to the Booking.

Can this task be performed in a sessionless environment?

This task can be performed in a sessioned or sessionless environment. However, in order to move Client File data, the Client File must first be retrieved.

Are the request and response identical on both the Apollo and Galileo systems?

The request and response for this task are identical on both the Apollo and Galileo systems. Error text may differ slightly between the two cores, but the tags in the request and response are no different.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

Users who are not familiar with the Client File package should use the “Blind” move with all levels. Users who are more familiar with the Client File package can use the more advanced capabilities of “Display,” “Select Line,” "Passenger Relation for Secure Flight," and "Related" move. There is much more involved in the “Display,” “Select Line,” "Passenger Relation for Secure Flight," and "Related" move varieties of this transaction that are not beneficial to the user unless they understand fully the concepts of Client File move. The idea of Selecting and De-Selecting Client File lines to be moved can be a confusing concept unless the user is familiar with the Client File system.

Explain any special limits or restrictions to the input data that may not be readily apparent.

If an error occurs during the process of adding data to the Booking, the process stops at that point and no additional data from the Client File will move. Any information moved to the Booking prior to the error will remain in the Booking.
ClientFile_2 cannot be used to move profiles in a sessionless environment. If you need to move profiles in a sessionless environment, use PNRBFManagement.

Section 2: Detailed Description

Request:

Unless otherwise specified, use ALL CAPS in any request data.

For a Client File/PRO-File move request (“Blind” or “Display” with no lines Selected), a <ClientFileMods> tag is required with a <ClientFileMoveHeaderMods> tag. The <ClientFileMoveHeaderMods> tag must contain the CRS and Pseudo City of the owner of the Client File, the Business and/or Personal File Titles of the Client File, the type of move, and a Preference indicator.

If the move request is for a “Select Line” move or a “Display” move where lines are either Selected or De-Selected, a <ClientFileMoveLineMods> tag for each line to be moved is required. This includes lines that were not changed but have a Transfer Code of “Y”. For this reason, the “Blind” move is a better option in most cases as there is less information required in the request.

If the move request is for a "related" move and specific passenger and/or "segment" relation is requested, a <ClientFileMovePsgrSegMods> element for the passenger/segment relation is required before the <ClientFileMoveLineMods> in the request.

If the move request includes Passenger Relation for Secure Flight data, a <ClientFileMovePsgrSegMods> for the Passenger Relation is required.

Prerequisite tasks:

The Client file must be “active” prior to the move. This can be accomplished by either providing another <ClientFileMods> tag with a Client File Display request, or by invoking a “Blind” move request as described above.

Expected response:

The response from any variety of Client File move will be in a <ClientFile> tag and will be a positive acknowledgement that the move occurred or an error response. If the request is for a “Blind” move, and the requested Client File title is not found, a Similar Name List will be returned (if similar titles are found).

The most common error returned for a “Blind” move will be an error that no match (exact or similar) was found. Another common error will be an error from the Booking process that the data is not valid. The error messages that are returned from the Booking process are numerous but are normally self-explanatory. Possible errors include but are not limited to:

VERIFY – UNABLE TO LOCATE TITLE/S No match at all could be found
VERIFY – FORMAT Information in the request is incorrect

Error and warning responses:

The most common error returned for a “Display” or “Select Line” move will be an error from the Booking process that the data is not valid. The error messages that are returned from the Booking process are numerous but are normally self-explanatory.

Follow-on requests:

If a <ClientFileSingleTitleList> tag or <ClientFileDoubleTitleList> tag is returned (for a Similar Name List response) and more data is available, a <MoreData> tag will also be returned. In this scenario, the <MoreData> tag will be sent back to the Host in a <ClientFileMods> tag to retrieve the additional data. This process continues until no <MoreData> tags are returned, meaning that all data has now been retrieved or until the required Client File is found. The <MoreData> tag processing is not available in a sessionless environment.

Section 3: Tables

1) Business File “Blind” Move

Request (Input) Tags

<ClientFileMods>		Terminal Equivalents:			Apollo MVT/BAR		Galileo CMT/BAR
	Ordering		KLR	Min/Max		XML Tag
			CFMH	1 – 1		<ClientFileMoveHeaderMods>

Response (Output) Tags

<ClientFile>		If Exact match found and no errors in the Booking Process
	Ordering		KLR	Min/Max	XML Tag
			CFPA	1-1	<ClientFilePositiveAck>
<ClientFile>		If Similar Name list returned (No exact match found)
	Ordering		KLR	Min/Max	XML Tag
			CFSL	1-nnn	<ClientFileSingleTitleList> A <ClientFileSingleTitleList> is returned for every possible match. This can be a very resource intensive response, so the closer to the title the request is the better the response time.
<ClientFile>		If Error occurred
	Ordering		KLR	Min/Max	XML Tag
			EROR	1-1	<ErrText>

2) Business File “Display” / “Select Line” / "Related" Move

Request (Input) Tags

<ClientFileMods>		Terminal Equivalents:			Apollo MV/		Galileo CM/
	Ordering		KLR	Min/Max		XML Tag
	A		CFMH	1 – 1		<ClientFileMoveHeaderMods>
	B		CFMR	0 – 1		<ClientFileMovePsgrSegMods> only if passenger/segment is required.
	C		CFML	1 – 200		<ClientFileMoveLineMods>
	Above 3 repeat for each level

Response (Output) Tags

<ClientFile>		If no errors in the Booking Process
	Ordering		KLR	Min/Max	XML Tag
			CFPA	0-1	<ClientFilePositiveAck>
<ClientFile>		If Error occurred
	Ordering		KLR	Min/Max	XML Tag
			EROR	1-1	<ErrText>

3) Personal File “Blind” Move

Request (Input) Tags

<ClientFileMods>		Terminal Equivalents:			Apollo MVT/BAR-PAR		Galileo CMT/BAR-PAR
	Ordering		KLR	Min/Max		XML Tag
			CFMH	1 – 1		<ClientFileMoveHeaderMods>

Response (Output) Tags

<ClientFile>		If Exact match found and no errors in the Booking Process
	Ordering		KLR	Min/Max	XML Tag
			CFPA	1-1	<ClientFilePositiveAck>
<ClientFile>		If Similar Name list returned (No exact match found)
	Ordering		KLR	Min/Max	XML Tag
			CFDL	1-nnn	<ClientFileDoubleTitleList> A <ClientFileDoubleTitleList> is returned for every possible match. This can be a very resource intensive response, so the closer to the title the request is the better the response time.
<ClientFile>		If Error occurred
	Ordering		KLR	Min/Max	XML Tag
			EROR	1-1	<ErrText>

4) Personal File “Display” / “Select Line” / "Related" Move

Request (Input) Tags

<ClientFileMods>		Terminal Equivalents:			Apollo MV/		Galileo CM/
	Ordering		KLR	Min/Max		XML Tag
	A		CFMH	1 – 1		<ClientFileMoveHeaderMods>
	B		CFMR	0 – 1		<ClientFileMovePsgrSegMods> only if Passenger/Segment relation is required.
	C		CFML	1 – 200		<ClientFileMoveLineMods>
	Above 3 repeat for each level

Response (Output) Tags

<ClientFile>		If no errors in the Booking Process
	Ordering		KLR	Min/Max	XML Tag
			CFPA	0-1	<ClientFilePositiveAck>
<ClientFile>		If Error occurred
	Ordering		KLR	Min/Max	XML Tag
			EROR	1-1	<ErrText>

Related Samples