Problem
When building packages with cruise cabins, the system only allocates passengers to a single cabin even when multiple cabins are needed. For example, a package search for 4 adults requiring 2 cabins (2 passengers each) only shops for 1 cabin.
What We Found
The Price Category for cruise cabins was using UOM=units but the Max Unit Occupants field was not configured. Without this field, the system cannot determine how many passengers should fit in each unit, defaulting to placing all passengers in a single cabin. The system relies on Max Unit Occupants to calculate how many units (cabins) are needed based on passenger count.
Solution
- Navigate to Setup → Object Manager → Price Category → Field Sets
- Open the ‘Cruise Price Category Fields’ fieldset
- Add the ‘Max Unit Occupants’ field to the fieldset if not already present
- Save the fieldset changes
- Edit each cruise/cabin Price Category record
- Set the Max Unit Occupants value to the maximum passengers per cabin (e.g., 2 for double occupancy cabins)
- Save the Price Category record
- Test by searching a package with passengers exceeding the Max Unit Occupants value to verify correct cabin allocation
Notes
- UOM can remain as ‘units’ - you do NOT need to change it to ‘rooms’ for this to work
- Max Unit Occupants tells the system how many passengers can fit in one unit, enabling it to calculate the correct number of units needed
- This same pattern applies to train cabins and similar accommodation types using unit-based pricing
- Initial troubleshooting suggested changing UOM to ‘room(s)’ but this was incorrect - the correct solution is adding Max Unit Occupants
Warnings
⚠️ If Max Unit Occupants is not set, the system will default to allocating all passengers to a single unit regardless of actual occupancy requirements
Source: KHELP-12294