Task: Cruise Cabin Availability

The Cruise Category Selection task allows the user to request available cabins in a specified category (cabin type), based on the sailing and rate code.

Section 1: Short Answer

Transaction Name:

CruiseCabinAvailability_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?

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.

Understanding of cruise-industry concepts, such as rate codes, categories, features, and options, is required. Knowledge of Galileo's LeisureShopper product is helpful.

Special limits or distinct restrictions to the input data.

There is no cruise-industry standard for encoded data such as credit card codes, ports of call, and airports. The specific data formats must be confirmed with individual vendors. Also, a number of response fields, such as status codes for dining and other options, are free-form text fields. Vendors may supply non-standard responses for these fields.

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 CruiseCabinAvailability_1_0 request follows the same iterative process as CruiseAvailability_1_0. <CabinAvailMods> is sent with all of the following child elements to request specific availability:

• <VendorRegionMods> – requests selected availability for a selected cruise.
• <SailingMods> – requests the price option for a selected sailing.
• <CabinCategoryAvailMods> – requests the cabin type for the selected rate code.

Prerequisite Tasks

Sailing, rate code, and category availability are requested using CruiseAvailability_1_0 prior to requesting cabin availability.

Expected Response

If the transaction completes successfully, <CabinAvail> is returned with one or more of the following child elements:

• <CruiseCabins>. Returns cabin options that meet the specified <VendorRegionMods>, <SailingMods>, and <CabinCategoryAvailMods> parameters.
• <TextMsg>. Returns additional text. Can be used for all cruise availability responses.
• <VendorChangedData>. Returns any vendor changes.  Some vendors will modify a selection, such as a rate code or category, based on the user's previous selections. For example, a user may select a category that corresponds to a rate code other than the initially selected rate code. In this case, the vendor will respond with a different rate code to be used in subsequent requests. In all subsequent requests in the booking process, the values of the items changed by the vendor should be used in place of those those initially selected.

If the vendor needs to verify the agency, <CustomerIdentification> returns with the <TextDisplay>. If it returns with a negative response 'N', the agency needs to contact the cruise line. If a positive response 'Y', the agency will need to re-submit the request.

Error and Warning Responses

If Cruise Category Selection transaction encounters an error, <CabinAvail> is returned with the <ErrText> element. <ErrText> contains the error code, the ID of the element, and text providing a complete error message, including any inserted text items. The following error messages may be received:

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

Follow-On Requests

After the cabin is selected, the cabin is held for a period of time (typically 15 to 30 minutes) to allow the user to complete the booking.  After the cabin is held, the cabin selection should be finalized by using CruiseCabinHold_1_0.

Section 3: Tables

Request (Input) Tags

Response (Output) Tags

Availability Agency Error

Related Samples

CruiseCabinAvailability_1_0_1