Task: Cruise Search

The Cruise Vendor Search task returns a list of vendors offering cruises that match specified destination and sailing date parameters.

Section 1: Short Answer

Transaction Name:

CruiseVendorSearch_1_0

Can any other transactions perform this same task?

No other transaction can perform this same task.

Can this task be performed in a sessionless environment?

Yes, this task can be performed in a sessionless environment.

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

The request and response are allowed only on Apollo.

Industry-specific knowledge required to understand this task in terms of the specific business process.

No specific knowledge is required. Knowledge of Galileo's LeisureShopper product is helpful.

Special limits or distinct restrictions to the input data.

The Cruise Vendor Search task does not currently return availability, but rather offers a list of potential vendors from which an available cruise can be selected.

Note: For Galileo Web Services client applications only, this transaction must be submitted using the SubmitCruiseTransaction method.

Section 2: Detailed Description

Request

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

The <CruiseVndSearchMods> with the <RegionMods> element sends a request for a list of potential vendors from which an available cruise can be selected. The <RegionMods> element can contain the following request parameters:

Vendor Code
Destination Name (required if no Destination Code). Because a similar names list is not currently available via XML Transactions, it is recommended to provide a pop-up or other destination list to ensure that users select a supported destination code (<Region> or <RegionName>).
Destination Code (required if no Destination Name). Because a similar names list is not currently available via XML Transactions, it is recommended to provide a pop-up or other destination list to ensure that users select a supported destination code (<Region> or <RegionName>).
Departure City/Airport Code
Start Date of Cruise. While data requests are made as specific dates; the response displays available cruises by season. For example, a start date of September 14 may yield August or November sailings for that destination and vendor.

Prerequisite Tasks

No prerequisites tasks are required to request a Cruise Vendor Search. However, an accurate destination name or destination code must be supplied.

Expected Response

If the Cruise Vendor Search transaction completes successfully, the <CruiseVndSearch> (6321 1.0) with the <CruiseVendor> tag is returned to indicate a good response.

Error and Warning Responses

If the Cruise Vendor Search transaction encounters an error, the <CruiseVndSearch> is returned with the <ErrText> element. The following error messages may be received:

0002 - Transaction Not Allowed

0041 - Invalid Destination

0054 – LeisureShopper Not Available

0390 – System Error Occurred

1330 – KLR ID Does Not Match Request

1333 – Uniglobe Not Allowed

1346 – Invalid Departure Date

Text Not Found for MSG NBR - #### (error message number)

For a complete list of cruise errors, see Cruise Error Messages.

Follow-On Requests

A Cruise Vendor Search is followed by an Sailing Availability transaction.

Section 3: Tables

Request (Input) Tags

<CruiseVndSearchMods>

Terminal Equivalents:

Apollo: LSS

Not available on Galileo.

Ordering	KLR	Min/Max	XML Tag
	LCS0	1-1	<RegionMods>

Response (Output) Tags

<CruiseVndSearch>

Ordering	KLR	Min/Max	XML Tag
	LCS1	1-1	<CruiseVendor>
	EROR	1-1	<ErrText>

Related Samples

CruiseVendorSearch_1_0_1