The Cruise Booking task sells a cruise segment, and includes an end transact that releases the data to the vendor via Apollo.
Transaction Name:
CruiseSellSegment_1_1
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 in terms of the specific business process.
Understanding of cruise-industry concepts, such as rate codes, categories, features, and options, is required. Knowledge of Galileo's LeisureShopper product is helpful.
Explain any special limits or distinct restrictions to the input data that may not be readily apparent.
The same user ID that was used to reserve the cabin must continue to be used throughout the booking process.
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.
A cruise segment cannot be added to an existing PNR with existing air, car or hotel segments using the XML Select cruise transactions. On the other hand, an existing PNR with an existing cruise segment can have air, car or hotel segments added to the PNR.
Note: For Galileo Web Services client applications only, this transaction must be submitted using the SubmitCruiseTransaction method.
Request
Unless otherwise specified, use ALL CAPS in any request data.
CruiseSellSegment_1_1 has the same request as the previous CruisingPricing_1_0 transaction, which prices the cruise segment. However, with CruisingPricing_1_0, the request is not end transacted and is, therefore, not yet committed to the CRS. This transaction does end transact with the request, which creates a PNR and stores passenger and itinerary data on the AAA.
The following elements are sent in the request:
<PNRBFPrimaryBldChgMods>. Identifies required passenger name, contact information,
and form of payment. Creates the PNR for the passenger itinerary.
Note: Form of payment for the cruise itself is performed using the
CruiseMakePayment_1_0_1 transaction. However, the FOP array in this request may be required to sell car, hotel, or cruise segments, or
to guarantee hotel segments. In rare cases, smaller airline vendors may also
require a form of payment to be associated with the sale of an air segment.
<PNRBFSecondaryBldChgMods>. Identifies passenger descriptions such as
gender and passport information.
The <CruisePricingBookingMods> element is sent with the following child elements to price the cruise itinerary:
<VendorRegionMods>. Vendor and cruise information.
<SailingMods>. Ship name, ports, and ship details.
<CabinCategoryAvailMods>. Cabin type, rate, and number.
<PricingBookingDetail>. Pricing-specific request.
<CabinDetails>. Selected cabin and location.
<CabinConfigMods>. Cabin configuration (e.g., king-sized bed).
<FeatureOptionSelected>. Features and options selected in CruiseVerifyAndOptions_1_0.
<PricingBookingDetail>. Pricing-specific request (e.g., type of pricing request, package status, record locator).
<CruiseItin>. Cruise itinerary, including ports of call, dates, and status.
<PastPassengerInfo>. Past passenger number, if passenger has previously traveled with vendor.
<SailingSpecificChoices>. Preferences such as dining and smoking options, travel agent, and booking credit information.
<TransportationDetail>. Selected transportation options for each passenger to or from departure port, or for associated pre- or post-cruise packages.
Prerequisite Tasks
The cabin, passenger information, and features/options must be determined by finalizing the cabin selection using CruiseVerifyAndOptions_1_0.
Expected Response
If the Cruise Name and Cabin Selection transaction completes successfully, the following elements are returned.
<PNRBFPrimaryBldChgMods>. Returns a record indicator.
<PNRBFSecondaryBldChgMods>. Returns a record indicator.
The <CruisePriceBookingDetail> element is returned with the following child elements:
<CruisePrices>. Returns total base price of cruise and total price base on selected or applicable options, discounts, fees, and penalties.
<CruisePricePerPassenger>. Returns cruise prices displayed by individual passenger. A returned rate code indicates that the vendor has changed the rate code to the code indicated. Use the new rate code for any subsequent transactions if you are proceeding with the selected category code. If other preliminary pricing requests are sent, supply the rate code that was used to retrieve the category availability.
<UnavailableItems>. Returns requested items that are not available within the selected cruise package. This field may or may not be returned, depending upon the specific vendor response.
<TextDisplay>. Vendor supplied text such as consumer advice.
<TextMsg>. Free-form text.
Error and Warning Responses
If Cruise Preliminary Pricing transaction encounters an error, <CruisePriceBookingDetail> is returned with the <ErrText> element. The following error messages may be received:
| 0002 – Transaction Not Allowed |
| 0054 – LeisureShopper Not Available |
| 0103 – Invalid Pick-Up Time |
| 0104 – Invalid Drop-Off Time |
| 0105 – Invalid Drop-Off Location |
| 0297 – Features / Options Limit Exceeded |
| 0390 – System Error Occurred |
| 1065 – Invalid Dining Preference |
| 1333 – Uniglobe Not Allowed |
| 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 |
| 9383 – Invalid Cabin Number |
| 9384 – Invalid Rate Code Specific Indicator |
| 9385 – Invalid Deck Name |
| 9386 – Invalid Cabin Position |
| 9387 – Invalid Cancelled Cabin Number |
| 9389 – Maximum Ports of Call Exceeded |
| 9390 – Invalid Ports of Call Type |
| 9391 – Invalid Port Name |
| 9392 – Invalid Port of Call Arrival Date |
| 9393 – Invalid Port of Call Arrival Time |
| 9394 – Invalid Port of Call Departure Date |
| 9395 – Invalid Port of Call Departure Time |
| 9396 – Invalid Port of Call Board Date |
| 9397 – Invalid Port of Call Board Time |
| 9398 – Need Port of Call Status |
| 9400 – Invalid Dining Status |
| 9401 – Invalid Smoking Preference |
| 9402 – Invalid Table Size |
| 9403 – Invalid Travel Agent Name |
| 9404 – Invalid Travel with Confirmation Number |
| 9405 – Invalid Booking Credit |
| 9406 – Invalid Booking Credit Indicator |
| 9407 – Invalid Back / Back Confirmation Number |
| 9408 – Maximum Transportation Items Exceeded |
| 9409 – Invalid Transportation Type |
| 9410 – Need Transportation ID |
| 9411 – Invalid Transportation Status |
| 9412 – Need Transportation Usage (at least one must be selected) |
| 9413 – Invalid Transportation Usage Indicator 1 |
| 9414 – Invalid Transportation Usage Indicator 2 |
| 9415 – Invalid Transportation Usage Indicator 3 |
| 9416 – Invalid Transportation Usage Indicator 4 |
| 9417 – Invalid Transportation Usage Indicator 5 |
| 9418 – Invalid Transportation Carrier Code |
| 9419 – Invalid Transportation Number |
| 9420 – Invalid Transportation Departure City |
| 9421 – Invalid Transportation Arrival City |
| 9422 – Invalid Transportation Departure Time |
| 9423 – Invalid Transportation Arrival Time |
| 9424 – Invalid Transportation Departure Date |
| 9425 – Invalid Transportation Arrival Date |
| 9426 – Invalid Transportation Equipment Type |
| 9427 – Invalid Transportation Connect Flag |
| 9428 – Invalid Transportation Meal Code |
| 9429 – Invalid Transportation Number of Stops |
| 9430 – Invalid Transportation Class of Service |
| 9431 – Invalid Pricing / Booking Request Type |
| 9432 – Invalid Pricing / Booking Status Code |
| 9433 – Invalid Pricing / Booking PNR Record Locator |
| 9434 – Invalid Pricing / Booking Vendor Record ID |
| 9435 – Invalid Pricing / Booking Vendor Name |
| 9436 – Invalid Pricing / Booking Cabin Location |
| 9437 – Invalid Pricing / Booking Second Booking Indicator |
| 9438 – Invalid Pricing / Booking Insurance / Waiver Indicator |
| 9439 – Invalid Pricing / Booking Departure Date |
| 9440 – Invalid Pricing / Booking Day / Night Indicator |
| 9441 – Invalid Pricing / Booking Booking Date |
| 9442 – Invalid Pricing / Booking Booking Time |
| 9443 – Invalid Pricing / Booking Sync Date |
| 9444 – Invalid Pricing / Booking Sync Time |
| 9445 – Invalid Pricing / Booking Passenger Information |
| 9446 – Invalid Pricing / Booking Itinerary Information Change |
| 9447 – Invalid Pricing / Booking End Date |
| 9448 – Invalid Pricing / Booking Surname Length |
| 9449 – Invalid Pricing / Booking 1st Name Length |
| 9450 – Invalid Pricing / Booking Title Length |
| 9452 – Pricing / Booking Processing Error |
| Text Not Found for MSG NBR - #### (error message number) |
For a complete list of cruise errors, see Cruise Error Messages.
Follow-On Requests
To continue the reservation process, pricing should be followed by the CruiseSellSegment_1_1 procedure.
|
<EndTransactionMods> |
Terminal Equivalents: |
Apollo: |
Not available on Galileo. |
|
Ordering |
NWB |
Min/Max |
XML Tag |
|
2030 |
1-1 |
<EndTransactionMods> |
|
<PNRBFPrimaryBldChgMods> |
Terminal Equivalents: |
Apollo: |
Not available on Galileo. |
|
Ordering |
NWB |
Min/Max |
XML Tag |
|
2100 |
1-1 |
<PNRBFPrimaryBldChgMods> |
|
<PNRBFSecondaryBldChgMods> |
Terminal Equivalents: |
Not available on Galileo. |
|
Ordering |
NWB |
Min/Max |
XML Tag |
|
2110 |
1-? |
<PNRBFSecondaryBldChgMods> |
|
<CruisePricingBookingMods> |
Terminal Equivalents: |
Apollo: LSNP |
Not available on Galileo. |
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
1 |
LCPB |
1-? |
<PricingBookingDetail> |
|
2 |
LCA0 |
1-? |
<VendorRegionMods> |
|
3 |
LCA1 |
1-? |
<SailingMods> |
|
4 |
LCAC |
1-? |
<CabinCategoryAvailMods> |
|
LCC0 |
1-? |
<CabinDetails> |
|
|
LCC1 |
1-? |
<CabinConfigMods> |
|
|
LCFS |
1-? |
<FeatureOptionSelected> |
|
|
LCPC |
1-? |
<CruiseItin> |
|
|
LCPL |
1-? |
<PastPassengerInfo> |
|
|
LCSY |
1-? |
<SailingSpecificChoices> |
|
|
LCTR |
1-? |
<TransportationDetail> |
|
<EndTransaction> |
|
Ordering |
NWB |
Min/Max |
XML Tag |
|
2031 |
1-1 |
<EndTransactionMods> |
|
<PNRBFPrimaryBldChg> |
|
|
|
Ordering |
NWB |
Min/Max |
XML Tag |
|
2101 |
N-N |
<PNRBFPrimaryBldChg> |
|
<PNRBFSecondaryBldChgMods> |
|
|
|
Ordering |
NWB |
Min/Max |
XML Tag |
|
2111 |
N-N |
<PNRBFSecondaryBldChg> |
|
<CruisePriceBookingDetail> |
|
|
Ordering |
KLR |
Min/Max |
XML Tag |
|
LCPA |
1-1 |
<CruisePrices> |
|
| LCPD | 1-5 | <CruisePricePerPassenger> | |
| LCUC | 0-99 | <UnavailableItems> | |
|
EROR |
1-? |
<ErrText> |
|
|
LCCX |
1-1 |
<TextDisplay> |