Task: Cruise Cabin Reservation

The Cruise Cabin Reservation task puts a hold on a selected cabin, which, in turn removes the cabin from the vendor's inventory.

Section 1: Short Answer

Transaction Name:

CruiseCabinHold_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 is required. Knowledge of Galileo's LeisureShopper product is helpful.

Special limits or distinct restrictions to the input data.

The same user ID that is used to reserve a cabin must continue to be used throughout the booking process.

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.

<CabinResMods> must be sent with all of the following child elements to put a hold on a selected cabin:

<VendorRegionMods>. Requests selected vendor and passenger data.
<SailingMods>. Rrequests selected sailing and package data.
<CabinCategoryHoldMods>. Requests selected rate code, category, and cabin number.

Prerequisite Tasks

CruiseCabinAvailability_1_0, which displays available cabins within the selected category, must be returned prior to sending this transaction.

Expected Response

If the Cruise Cabin Reservation transaction completes successfully, <CabinRes> is returned with one or more of the following child elements:

<CabinConfigMods>. Returns cabin configuration options for a selected cabin (e.g., king-sized bed or double beds).
<PassengerDataRules>. Returns required passenger information (e.g., insurance option, gender, past passenger number, and passenger name).
<TextMsg>. Returns additional text from the vendor.

If a more than one cabin configuration, <Config>, is returned in the <CabinConfigMods> element, the user is required to select one configuration. If only one <Config> element is returned in the <CabinConfigMods>, it is automatically selected.

Error and Warning Responses

If the CruiseCabinHold_1_0 transaction encounters an error, <CabinRes> with the <ErrText> element is returned. <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:

0002 – Transaction Not Allowed

0024 – Link Not Available

0042 – Invalid Destination

0045 – Invalid Vendor Code

0048 – Invalid Currency Code

0054 – LeisureShopper Not Available

0091 – Invalid Length

0245 – Invalid Ship Name

0277 – Cabin Cannot Accommodate Number in Party

0278 – Third/Fourth Berths Not Available

0279 – Cabin Not Available

0280 – Cabin Invalid for Category

0390 – System Error Occurred

1081 – Invalid Package ID

1330 – KLR ID Does Not Match Request

1333 – Uniglobe Not Allowed

1334 – Invalid Category Changed Indicator

1335 – Invalid Category

1336 – Invalid Cabin Number

1340 – Invalid Vendor Confirmation Number

1341 – Invalid Number of Passengers

1342 – Invalid Rate Code

1343 – Invalid Rate Code Change Indicator

1344 – Invalid Vendor Record ID

1345 – Invalid Disembarkation Port

1346 – Invalid Departure Date

1347 – Invalid Departure City

1348 – Invalid Departure City Changed

1349 – Invalid Air Transportation

1350 – Invalid Air Transportation Change

1351 – Invalid Age

1358 – Invalid Lowest Rate Code Indicator

1367 – Cabin Invalid for Rate Code

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

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

Follow-On Requests

The CruiseVerifyAndOptions_1_0 transaction designates the passengers for the reserved cabin. However, if the cabin hold has ended before the vendor’s time-out, CruiseCabinRelease_1_0 should be used to return the cabin to the vendor’s inventory.

Section 3: Tables

Request (Input) Tags

<CabinResMods>

Terminal Equivalents:

Apollo: LSCABNxxxxx (where xxxxx indicates the cabin number)

or LSn (where n indicates the line number of the selected cabin).

Not available on Galileo.

Ordering	KLR	Min/Max	XML Tag
N/A	LCA0	1-1	<VendorRegionMods>
N/A	LCA1	1-1	<SailingMods>
N/A	LCCR	1-1	<CabinCategoryHoldMods>

Response (Output) Tags

<CabinRes>

Ordering	KLR	Min/Max	XML Tag
	LCC1	1-1	<CabinConfigMods>
	LCPX	1-1	<PassengerDataRules>
	EROR	1-1	<ErrText>
	TEXT	1-1	<TextMsg>

Related Samples

CruiseCabinHold_1_0_1