Task: Cruise Cabin Release

The Cruise Request for New Transportation task requests transportation changes. If features or options are selected during the cabin verification process that affect the transportation dates to and from the cruise's start and end ports of call, a request for new transportation must be made.

Section 1: Short Answer

Transaction Name: 

CruiseNewTransportation_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.

There is no cruise-industry standard for encoded data such as credit card codes, ports of call, and airports. Always confirm specific data formats with individual vendors.

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.

<RequestNewTransMods> is sent with the following child elements:

Prerequisite Tasks

New transportation arrangements may be required in response to features or options selected when the cabin selection is finalized using the CruiseVerifyAndOptions_1_0 procedure.

Expected response:

If the Cruise Request for New Transportation transaction completes successfully, <RequestNewTrans> is returned with a <TransportationDetail> element  and an optional Text Message, <TextMsg>, from the vendor.  <TransportationDetail> contains transportation options for the selected package and features/options.

Error and warning responses:

If Cruise Request for New Transportation transaction encounters an error, <RequestNewTrans> is returned with an <ErrText> element.  The following error messages may be received:

0002 – Transaction Not Allowed
0025 – Vendor Response Error
0042 – Invalid Destination
0045 – Invalid Vendor Code
0048 – Invalid Currency Code
0054 – LeisureShopper Not Available
0091 – Invalid Length
0103 – Invalid Pick-Up Time
0104 – Invalid Drop-Off Time
0105 – Invalid Drop-Off Location
0245 – Invalid Ship Name
0297 – Features/Options Limit Exceeded
0358 – Feature Option Not Compatible
0390 – System Error Occurred
1050 – Air City Not Supported
1051 – Invalid Air City
1052 – Cruiseline Air Unavailable
1053 – Name Change Not Allowed
1054 – Vendor Air Required
1055 – Vendor Air Not Supported
1056 – Waiver required
1057 – Title Required
1058 – Age Required
1059 – Gender Required
1060 – Past Pax Number Required
1061 – Travel Agent Name Required
1062 – Dining Room Pref Required
1063 – Booking Credit Required
1064 – Smoking Pref Required
1065 – Invalid Dining Preference
1068 – Invalid Booking Credit Number
1069 – Invalid Back-to-Back Confo
1070 – Air City Not Valid for Rate Code
1071 – No Features Exist for This PKG
1072 – No Options Exist for this PKG
1073 – Change Not Allowed by Vendor
1081 – Invalid Package ID
1092 – Invalid Embarkation Port
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
9205 – Invalid Start Date
9206 – Invalid End Date
9351 – Invalid Feature/Option ID
9352 – Invalid Feature/Option Status
9353 – Invalid Item Quantity
9354 – Invalid Unique Set ID
9355 – Invalid Set Name Description
9356 – Invalid Unique Item ID
9357 – Invalid Description of Feature/Option
9358 – Invalid Price
9359 – Invalid Currency
9360 – Invalid Decimal Places
9361 – Invalid Feature Allocated to Passenger 1
9362 – Invalid Feature Allocated to Passenger 2
9363 – Invalid Feature Allocated to Passenger 3
9364 – Invalid Feature Allocated to Passenger 4
9365 – Invalid Feature Allocated to Passenger 5
9366 – Invalid Affect Transportation Indicator
9367 – Invalid Affect Air Transportation Indicator
9368 – Invalid Feature Back-Up Indicator
9369 – Invalid Pick-Up Indicator
9370 – Invalid Drop-Off Indicator
9371 – Invalid Purchaser Indicator
9372 – Invalid Pick-Up Drop-Off Indicator
9373 – Invalid Pick-Up Location Description
9374 – Invalid Pick-Up Description
9375 – Invalid Pick-Up Carrier Code
9376 – Invalid Pick-Up Flight Number
9377 – Invalid Drop-Off Location Description
9379 – Invalid Drop-Off Carrier
9381 – Invalid Drop-Off Flight Number
Text Not Found for MSG NBR - #### (error message number)

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

Follow-on requests:

After requesting modified transportation, the process returns to the standard flow and the newly modified itinerary is priced using CruisePricing_1_0.

Section 3: Tables

Request (Input) Tags

<RequestNewTransMods>

Terminal Equivalents:

Apollo:  none

Not available on Galileo.

Ordering

KLR

Min/Max

XML Tag

 

LCA0

1-1

<VendorRegionMods>

 

LCA1

1-1

<SailingMods>

 

LCCR

1-1

<CabinCategoryHoldMods>

 

LCFS

1-1

<FeatureOptionSelected>

 

Response (Output) Tags

<RequestNewTrans>

 

Ordering

KLR

Min/Max

XML Tag

 

LCTR

0-30

<TransportationDetail>

 

TEXT

0-1

<TextMsg>

 

EROR

0-1

<ErrText>

 

Related Samples

CruiseNewTransportation_1_0_1