Passive Hotel Segments with MK or BK Status
A passive hotel segment can be created with the MK status. The MK status allows hotel passive segments to be tracked and facilitates passive segment reporting.
Passive hotel segments have required data that must be sent in a request to complete the sell process. This required data also applies to the MK status.
- The MK status must be the first passive hotel segment booked. Passive hotel segments with a BK status can follow the segment with the MK status.
- A PNR can have multiple passive hotel segments with a status of MK. In the response, passive hotel segments with Status="MK" are returned before any passive hotel segments with Status="BK". If there are multiple hotel passive segments with Status="MK", they are sequenced in Start Date order.
- Passive remarks for Rate Code and one or both of Hotel Code and Hotel Short Name are required when the status is MK for a passive hotel segment. Specific values must be assigned for PassiveRemark/Text and the corresponding Type.
- Rate Code
<PassiveRemark>
<Text>Rate Code value<Text>
<Type>R<Type>
- Hotel Code (unique Property ID)
<PassiveRemark>
<Text>Hotel Code value<Text>
<Type>P<Type>
- Hotel Short Name
<PassiveRemark>
<Text>Hotel Short Name value<Text>
<Type>H<Type>
- Passive hotel segments with an MK status have the following required attributes in PassiveSegment:
- SupplierCode
- Status
- StartDate
- EndDate
- NumberOfItems
- Origin
- SegmentType
Optional attributes can be added to PassiveRemark in Type and Text.
The following codes apply to both MK and BK status:
- G - Guarantee (maximum length 29)
- SI - Service Information (maximum length 50)
- CF - Confirmation number (maximum length 30)
- CD - Corporate Discount number (maximum length 25)
- EX - Extra adult (maximum length 9)
- EC - Extra child (maximum length 9)
- CR - Crib (maximum length 9)
- W - Written field for address info (maximum length 100)
The following codes apply only to MK status:
- BC - Booking reason code (maximum one character)
- RQ - Rate quote (maximum 12 characters)
- RC - Rate Access Code (maximum six characters)
- CM - Commission (Y for yes, N for no, or a percent; for example, "02" for two percent)
Example:
<PassiveRemark>
< Text>I</Text>
<Type>BC</Type> </PassiveRemark>
Hotel passive segments with a BK status can be created to update back-office systems to include Amount Type of Due or Paid. When a passive hotel segment with BK status and AmountType of Due or Paid is created, the Origin and SupplierCode are required. Without this data, the request fails. Origin value defaults to "SWI" and SupplierCode value defaults to "ZZ" if other values are not provided.
If an MK status is used for a passive hotel segment with AmountType of Due or Paid, the transaction fails and an error is returned:
SYSTEM ERROR | FINISH OR IGNORE TRANSACTION/MODIFY.
Passive hotel segments, including MK segments, cannot currently be modified. However, passive hotel segments with MK status can be canceled using PassiveCancelReq. The provider is not notified when a passive segment is canceled so a separate cancellation must be arranged with the provider.
Notes:
-
Subsequent PNR data retrieved from Galileo (1G) and Apollo (1V) via Terminal Data is affected by data created in Travelport Universal API for Passive Hotel segments that were added to an existing PNR through either Passive Booking (PassiveCreateReservationReq) or Universal Record Modify (UniversalRecordModifyReq/UniversalModifyCmd/PassiveAdd).
- This error did not occur for PNRs that were retrieved though Travelport Universal API using UniversalRecordRetrieveReq or UniversalRecordImportReq.
- This applies only to PNRs that were created in Travelport Universal API for Galileo (1G) and Apollo (1V).