See Managing Block Room and Rate Grid.

For properties with the Cutoff OPERA Control active, a Cutoff Schedule OPERA Control is added to enable the configuration of cutoff schedule rules. See Block Management Overview.

Create Block and Manage Block are updated with a Cutoff Schedule list field for selecting a cutoff schedule that populates the cutoff days per room type, date in the room, and rate grid (block allocation).

For properties with the Group Rooms Control OPERA Control active, Block Persons and Pickup Persons are available in the Detail Level section of the Group Room Control View Options. When you select Block Persons, you can view the total number of persons for the rooms blocked in your business block. When you select Pickup Persons, you can view the number of persons that are picked up in the reservations. The number of Pickup Persons is based on the number of adults and children entered when creating a reservation.

If the Occupancy Split per Room Type OPERA Control is inactive, the number of Block Persons is calculated based on the Persons per Room entered in Block Details. If the Occupancy Split per Rooms Type OPERA Control is active, then number of Block Persons is calculated based on the number of rooms entered for occupancy.

For properties with the Negotiated Rates, Relationships, and Relationships Rate Inherit OPERA Controls active, the Rate Code list field in the Room Details section of the Block Overview displays any negotiated rate codes inherited from a parent sales account. See Configuring Relationships. 

Rooming List is updated to ensure reservations inherit flex fields (UDFs) values selected in the PM template reservation.

Attributes Inherited from the Template Reservation:

For properties with the Room Rotation OPERA Control active, the Room list field is updated to exclude rooms where Owner Exclusive Ownership Records & Owner Referral Records exists for stay date ranges.

A Validate Room List action is added to the Rooming List to validate all reservations entered or imported prior to submitting reservations for confirmation.

The validation results appear with Sort By and Report options.

For properties with the Tour Series OPERA Control active and the Tour Series Handling OPERA Control set to Master/Sub Relations, the following update applies:

The ability to create extra sub tour series blocks is available. The I Want To . . . menu of a sub tour series block displays the Create Tour Series action. When selected, the Master Block Code and Tour Code populate automatically, allowing you to create additional sub blocks.  

From a hub location, the I Want To . . . menu of a Master Itinerary Tour block, the option for Create Tour Series appears.  When Create Tour Series is selected, the Itinerary check box is selected by default, allowing you to create additional sub tour blocks in the same or different properties. The Master Block Code and Tour Code also populate automatically.

A Calculate action link is added to the Master Block to calculate Block Statistics including Room Nights, Booked, Room Nights Picked Up, Room Revenue Booked, Room Revenue Picked Up, Average Room Rate Booked, Average Room Rate Picked Up, Event Revenue On the Books, and Event Revenue Actual.

For more information, see Creating a Group Tour Series.

Channel Distribution is updated to configure Distribution Attributes, manage translations, and configure channel rates.

For properties with the Check in Prepay Rules OPERA Control set to Advanced Folio Posting, the Auto Advanced Bill Payment Method OPERA Control is updated to allow the selection of multiple payment methods.

Advanced Bill Payment is updated to support partial payment with various payment methods and, in the event you exit without completing full payment, the partial payment in retained, allowing you to proceed with paying the remaining balance at a later time.

A Deep Link is added to launch and display Billing by passing an External Reference Number with the combination of External System or Leg Number in the OPERA Cloud URL:

https://%OPERACLOUDURL%}/bookmarks/billing?externalSystem=<param value>&externalRefLegNo=Parm value>&TPRESORT=<Hotel id>

• externalSystem (optional) = External System.

• externalRef (required) = External Reference Number.

• externalRefLegNo (optional) = Leg Number.

• TPRESORT(required) = hotelId.

See Using Deep Links to Presentations Pages.

When the Fiscal Folio Printing and Associated Folio Details Required for a Credit Bill OPERA Controls are active, and you generate a Credit Bill from Billing, the Fiscal Printing window appears with a new required field for Fiscal Bill No. See Generating a Folio for a Billing Window.

Example:

When the Fiscal Folio Printing and Print Fiscal Response On Folio OPERA Controls are active, and you generate a fiscal folio, it successfully displays large fiscal responses from the Fiscal Partner as a QR Code.

The following is generically available but should be reviewed by properties in France.

In the scenario where an Information Folio or Proforma Folio is generated, the CASHIER_NO element is updated to output the Cashier Number assigned to the user generating the folio. If a cashier number is not assigned to the user, the cashier number you select during Cashier Sign-In is output.

In a scenario where you do not have a cashier number assigned, and a Pro-forma Invoice is generated for a reservation not yet checked in, the first open cashier number in your property is output on the Pro-Forma Invoice. If no cashiers are open in your property, the cashier selected for the Night Audit Cashier OPERA Control is output.

If the Fiscal Folio Printing OPERA Control or Supporting Documents OPERA Control is active, and no cashier number is selected, no cashier number appears on the folio. 

The SAMPLE_FOLIO_TEXT1 and SAMPLE_FOLIO_TEXT2 custom text translations are output on the folio according to the Language selected in the profile.

A Health Check action is added to Transaction Code configuration to evaluate the accuracy of the transaction code configuration.

An Include Exclusive Tax in the Comp Posting Approval OPERA Control is added to the Comp Accounting group to include exclusive tax generates in the Comp Posting Approval request to the gaming system.

An Override External Rate user task is added to the Financial Admin group allowing updates to externally controlled rate codes.

A Covers export template is added to provide an export of daily covers data. See Exports.

Transaction Code configuration is updated with the Post Covers checkbox enabling you to post covers for charges posted.

For properties with the Supporting Documents and Offline Folio OPERA Controls active, generating a fiscal folio allows you to generate an Offline Folio when the fiscal service is offline.

Channel Negotiated Rates search is updated to enable the selection of multiple Property values and entry of a Channel Rate Code when operating from a hub location.

For properties with an OPERA Cloud Service, Loyalty subscription, or for properties with the Loyalty Membership Configuration OPERA Control active, you are provided with a warning to check for the Central Currency code configuration while configuring the Primary Loyalty Membership Type.

For properties validating membership numbers in an external system different from the external system configured in Membership Handling, a Card Validation External Database field is added in order to link an alternate external system.

For properties validating membership numbers using an integrated solution without having an external database selected in the Card Validation External Database field, the membership number validation is performed using the external system configured in Membership Handling,

For properties with the Keyword OPERA Control active, Keyword Type configuration is updated to support 10 character codes.

The Deep Link URL for Profile Presentation is updated to allow access to the profile presentation using a Subscription ID (External Profile ID) and External Database.

https://%OPERACLOUDURL%/bookmarks/profile?subscriptionId=<parameter-value>&externaldatabase= <parameter-value>.

When using profile lookup and download, selecting a profile with an existing subscription for download results in the existing profile being updated, rather can creating a new, duplicate profile.

A Mark/Unmark Profile as Restricted task is added to the Client Relations group to permit update of the Restricted checkbox in Guest/Contact profiles and Sales Accounts.

The Restriction Reason field supports free text entry when the Restriction/Flagged Reasons OPERA Control is inactive or provides a list of restriction reasons.

The following is generically available but should be reviewed by properties in France.

Refer to France - OPERA Cloud Fiscal Primary Data Document 2621636.1.

The sample_folio_india_buckets RTF folio template is updated to include non-tax generates in the HSN Summary SALES column. Existing customized RTF folios based on the sample_folio_india_buckets RTF template display non-tax generates in the HSN Summary without needing to update the folio.

In a scenario where Service Charge is configured as a non-tax generate on transaction codes, the service charge posted is included in the Folio Footer HSN Summary SALES column for the related HSN code.

Refer to India - HGBU OPERA Cloud Fiscal Primary Data Document 2623459.1.

The following functionality is available generically but should be reviewed by properties in Israel.

For properties with the Generate Zero Bill OPERA Control active, generating zero folio settlements from the Billing screen displays the Folio Type selection window as part of the workflow.

Refer to Italy - OPERA Cloud Fiscal Primary Data Document 2563778.1

The IT_ALLOGGIATI export is updated enabling you to use the correct China country code.

Refer to Italy - OPERA Cloud Fiscal Primary Data Document 2563778.1

The following update is generically available, but should be reviewed by properties in Nagasaki, Japan.

The JAPAN_GENERIC_TAX_UDF and JAPAN_GENERIC_TAX_CHILD_ONLY_UDF package functions are updated to allow linking of package codes for items such as Extra Beds or Crib charges (when transaction code Type = Lodging) for consideration when calculating the Nagasaki Accommodation Tax.

Refer to Japan - HGBU OPERA Cloud Fiscal Primary Data Document 2560520.1.

The following functionality is generically available but should be reviewed by properties in Portugal.

The Default Deposit Tax Room OPERA Control is enabled when the Advanced Tax Handling for Deposits OPERA Control is active and the Advanced Deposit Handling setting is 4 or 9.

The following functionality takes place for No Show, Cancellation, and Pre-stay Charges reservations:

In a scenario where the Deposit Tax charges offset one another and balance back to 0 (for example: A deposit is posted for 200.00, and a second deposit is posted for -200.00 to cancel the original deposit), no Deposit Transfer at check-in postings exist on the billing screen.

When the Auto Generate Credit Bill for Deposit upon Check-In OPERA Control is active, and the associated settings are updated, the following functionality takes place:

For reservations where a deposit exists, when accessing the Billing screen the first time for a No Show, Cancelled reservation, or the reservation is set for Pre-stay charges, a credit bill is automatically generated and the deposit tax postings (+ and - postings for the transaction code defined in Deposit Ledger Tax Transaction Code OPERA Control) are automatically moved to the pseudo room defined in the setting for Default Deposit Tax Room, when the room is checked in.

When the Auto Generate Credit Bill for Deposit upon Check-In OPERA Control is inactive, the following functionality takes place:

For reservations where a deposit exists, when accessing the Billing screen the first time for a No Show, Cancelled reservation, or the reservation is set for Pre-stay charges, the deposit charges (both “Deposit Transfer at Check In” and “Deposit Tax Transfer at Check In”) are posted on the Billing screen. No tax postings (+ and - postings for the transaction code defined in the Deposit Ledger Tax Transaction Code setting) are generated as no automatic credit bill is generated.

Existing behavior and the deposit transactions are posted to the Billing screen, when the Default Deposit Tax Room OPERA Control does not have a value (is blank/null) or the room is not checked in, and the Deposit transactions are posted to the billing screen.

Default Deposit Tax Room:

The Default Deposit Tax Room can be checked in and out manually. The following is a suggestion if you want the Default Deposit Tax Room to automatically be checked in after the room is checked out, using the functionality available in OPERA Cloud. The related Room Type used for the Default Deposit Tax Room should have the checkboxes selected for the Always Checked In checkbox selected. See Configuring Room Types. The Default Deposit Tax Room reservation should then be marked as Always Checked In with the checkbox selected. See Managing Reservation Payment Instructions. The Auto Check-In Pseudo Rooms after Check Out OPERA Control must also be active.

When the Default Tax Room is due out, it appears in the End of Day procedure for Departures not yet checked out. As the Default Tax Room should have a zero balance, this can be handled by selecting the “Check Out Zero Balance Departures” option. A copy of the folio is stored in Folio History.

When the Auto Check-In Pseudo Rooms after Check Out OPERA Control is active after the Zero Balance Departure has been checked out, the End of Day continues, and the reservation is automatically checked in again to the same room for the same number of nights as the original reservation checked out using Zero Balance Departure.

If the Default Tax Room has a balance, you must handle it manually.

In the Changes Log, an entry is created for "Pseudo Rooms Automatically Checked In During the End of Day Procedure."

This functionality allows flexibility for checking out the Default Tax Room reservation Daily, weekly, or monthly.

Refer to Portugal - OPERA Cloud Fiscal Primary Data Document 2629862.1.

The following is generically available in Reporting & Analytics (R&A) but should be reviewed by properties in Portugal.

Refer to Portugal - OPERA Cloud Fiscal Primary Data Document 2629862.1

The ES_INE export is updated. In a scenario where the maximum room occupancy is defined as three, four, or higher and is not achieved by adding extra beds in the room, the value is reported in the OTHER_ROOMS column, not in the DOUBLE_ROOM_DOUBLE_USE column.

Refer to Spain - OPERA Cloud Fiscal Primary Data Document 2555053.1.

A Profile_Relationship_Type element is added to the Police Registration Card data model and sample template, for the Profile Relationship Type. The element outputs the configured relationship of the Accompanying Guest profile to the main guest profile on the Accompanying Guest Police registration cards.

The Events dashboard tile is updated with a date field and < > navigation controls to view events for past or future dates.

A Start Time field is added to Function Diary 1 Day View search to determine the start time of the Function Diary. Your selection is remembered for future sessions and if no value is selected, the Function Diary display starts at midnight.

A EDW_EXPORT_ADVANCED export template is added to General Export templates and has the fields available in EDW_EXPORT plus the following additional fields:

If the process is manually paused during the day, the Start Auto Check In Process procedure starts it again the next day, either immediately or according to the Auto Check In Start Time OPERA Control.

The processor runs every five minutes and checks whether any of the advance checked-in reservations meet the criteria for auto check-in. If Auto Check In Start Time and Auto Check In End Time are defined, auto check in reservations only occur during those times or if a user has manually overridden the start time by using the action link the I Want To . . . menu of Advance Checked In.

The minute value before ETA (estimated time of arrival) is considered only during those times. It does not override the start time. For example, if the start time is set for 2 p.m., the ETA on the reservation is 1:30 p.m., and the setting is set to 30 minutes before the ETA, then the reservation is not auto checked in at 1:00 p.m. as configured. The first time the process runs after the configured start time, 2 p.m. (which could be up to 2:04 p.m.), it finds the reservation, checks the room status, and, if that meets the criteria, automatically checks in the reservation.

If a reservation is assigned to a room with a room condition selected in the Exclude Room Conditions OPERA Control, the reservation will be skipped when the auto check in is processed. Should the room condition be removed from the room, the reservation is auto checked in the next time the processor runs as long as the reservation meets all other criteria for auto check in.

See Auto Check In of Advance Checked In Reservations.

Country and Nationality flag images are displayed in the profile business card of Manage Reservation and Check In.

A Consider ETD and ETA checkbox is added to Room Assignment Auto Assign and is enabled when the Include Departure Rooms checkbox is selected. When you select the Consider ETD and ETA checkbox and run the auto assign process, rooms with an ETD (Estimated Time of Departure) after the ETA (Estimated Time of Arrival) of the arriving reservation are not assigned. Also, a time buffer can be configured in the Auto Assign ETD - ETA Buffer OPERA Control, which then considers the extra buffer (in minutes) between the ETD of the departing reservation and the ETA of the arriving reservation when processing the auto room assignment with the Consider ETD and ETA checkbox selected. When a value is configured in the Auto Assign ETD - ETA Buffer OPERA Control, the Consider ETD and ETA checkbox is selected by default once the Include Departure Rooms checkbox is selected. See (Batch) Room Assignment.

For properties with the Registration Cards, Relationships, and Accompanying Guest OPERA Controls active, an ACCOMPANYING_RELATIONSHIP_TYPE element is added to the G_ACC_GUEST section of the registration card data model (sample_registration_card.xml) and RTF template to output the relationship of the accompanying guest profile to the main guest profile on the accompanying guests registration cards. To update your current customized registration card templates, see Updating Customized Stationery with Current Data Model.

For properties with the Vouchers OPERA Control active, the following updates apply:

You are prompted with the reservation vouchers immediately when launching Reservation Check-in, enabling you to print the vouchers and, while processing, continue the check-in process. See Managing Vouchers.

A Batch Vouchers option is added to generate, print, and reprint vouchers. See Generating and Printing Vouchers.

The User Name data element is added to cancel Reservation Business Events.

The following update is available generically and should be reviewed by properties in Germany and Austria.

EFSTA (European Fiscal Standards Association) is added to Fiscal Business Event Partner OPERA Control. Selecting EFSTA auto-subscribes Cashiering Fiscal Business Events New Posting with Generates and Delete Posting with Generates.

Existing properties with no value selected in the Fiscal Business Event Partner OPERA Control are not affected and will continue to generate the currently subscribed Cashiering Fiscal Business Events New Posting with Generates and Delete Posting with Generates.

For properties with the Fiscal Business Event Partner OPERA Control set to GENERIC1 after the Fiscal Business Event Partner is selected, the Posting Business Events for Fiscal OPERA Control can be activated, auto-subscribing the Cashiering Fiscal Business Events New Posting with Generates and Delete Posting with Generates for the GENERIC1 Fiscal Business Event Partner.

Fiscal integration is updated with the following Fiscal Bucket Codes.

Fiscal Partner configuration is updated with a Send Folio after Fiscal Payload checkbox (deselected by default).

Once the fiscal folio generates successfully, the fiscal service can request the folio as encoded data, which allows the Fiscal Partner to create a copy of the folio.

Example:

The Guest Service Status Request business event is added to the Housekeeping module.

Interface Mapping is added for Central Exchange Interfaces, allowing you to configure data transformation (code conversion) for OPERA Cloud and external system codes. See Configuring Interface Mapping.

The Create Wake Up Call, Update Wake Up Call, and Delete Wake Up Call Business Events are added to the Reservation module.

For properties with the Fiscal Folio Printing and the Supporting Documents OPERA Controls active, generating confirmation letters results in a supporting document generating for the fiscal partner.

Based on Central Interface selected as the Type in Switch Interface, OPERA Cloud Central Exchange only displays menu options relevant to OPERA Cloud Central when selecting Save to initiate the switch.

When no interface is currently configured, a Create New Interface Setup action link is added to launch Interface Setup.

1. When the Supporting Documents OPERA Control is active, and you generate a Confirmation Letter, the universal payload is updated to include a new value of CONFLETTER in the tag for <DocumentTypes>.

Example:

<Command>INFO</Command>
<FiscalTimeoutPeriod>30</FiscalTimeoutPeriod>
<CallbackURL/>
<FiscalParameterString/>
<SupportingDocumentSeqNo>123</SupportingDocumentSeqNo>
<DocumentType>CONFLETTER</DocumentType>
</DocumentInfo>

2. When the Supporting Documents OPERA Control is active, and you generate a Confirmation Letter, the universal payload is updated to include a new tag for <StayTotal>.

The value for <StayTotal> is equal to the Total Cost of Stay.

Example:

</GuestInfo>
<RoomRate>1000</RoomRate>
<StayTotal>2000</StayTotal>
<RatePlanCode>RACK</RatePlanCode>
<RoomNumber>1020</RoomNumber> 
<RoomClass>ALL</RoomClass>
<RoomType>SINGLE</RoomType> 
<NumberOfRooms>1</NumberOfRooms>
<Guarantee>CHECKED IN</Guarantee>
<MarketCode>OTH</MarketCode> 
<ResStatus>CHECKED IN</ResStatus>
<UserDefinedFields /> 
<SourceCode>IND</SourceCode>
<SourceGroup>ALL</SourceGroup>
</ReservationInfo>  

<Command> INFO</Command>
<FiscalTimeoutPeriod>30</FiscalTimeoutPeriod>
<CallbackURL/>
<FiscalParameterString/>
<SupportingDocumentSeqNo>123</SupportingDocumentSeqNo>
<DocumentType>CONFLETTER</DocumentType>
</DocumentInfo>

For properties with the Item Inventory and Reservation Traces OPERA Controls active, Item Inventory configuration is updated with a Configure Traces for all Item Inventory Days checkbox and the ability to create multiple trace texts.

The item inventory quantity selected in the reservation appears in the trace text. See Configuring Item Inventory.

You can delete the Membership Type Card Number Details configuration for Card Number Validation and Card Number Auto Generation using the Delete button. See Configuring Membership Type Card Number Details.

The Membership Card Number is updated to appear as masked (last four digits in plain text) by default in OPERA Cloud.

A View Membership Number task is added to the Client Relations Group, allowing you to view the unmasked Card Number using the Show Masked Information button in Profile Memberships.

The Show Masked Information action is logged in the Changes Log for the View Unmasked Info action type.

You can search Membership Transactions and Membership Awards using the following search criteria.

For properties with the Fiscal Folio Printing OPERA Control active:

Changes to Fiscal Folio Bucket Types configuration are tracked in the Changes Log.

Changes to Fiscal Bucket Code configuration are tracked in the Changes Log

A new asynchronous operation called BlockAllocationProcess is available in the Block Asynchronous API. This allows you to update a block's room grid, including inventory and rates. Using this operation ensures that updates for large blocks with multiple room types have time to process and update OPERA Cloud efficiently.

When calling the getBlockAllocationSummary operation in the Block Asyncronous API, with request parameters startLastModifiedDate and endLastModifiedDate, block change log entries are also considered along with the block header update date. This ensures that all block changes are considered when calling this operation.

A blockChangesByTimeDate operation is added to the Block API. You can search for blocks created, updated, and/or deleted within a maximum 3-day date range. The response includes block id, block code, array of external system and external system id, block start date, block end date, room status, catering status (if applicable), and last change date and time. If a block was created and deleted in the time period of your search, the query does not return this information. If a block is created and updated, the create information is returned. If a block is updated only, it returns the update. If a block is updated and deleted, it returns the delete.

The getblocks and putblocks operations in Block (BLK) API are updated with an autoloadForecastGrid element.

Three new operations are added to the Block (BLK) API: getCutoffScheduleDetails, putCutoffScheduleCode, and removeCutoffScheduleCode. Use these operations to fetch details about a blocks cutoff schedule, or to update the cutoff Schedule, or delete the cutoff Schedule.

The getProfileMembershipStatistics operation in the Customer Relationship Management API is updated with new query parameters (transactionDate, hotelId, confirmationNumber, limit, offset) and response body parameters (totalPages, offset, limit, hasMore, totalResults, count). This allows you to search membership transactions based on the transactionDate, hotelId, and confirmationNumber, along with paginations.

The getRoomKeys operation in the Front Office API now includes a query parameter called includeInactiveRoomKeys. Setting this to True allows any inactive room key details to be included in the response.

The getInventoryItems and postInventoryItems operations in the Inventory API include a TracesPerDay element. Setting TracesPerDay to true creates the traces for all inventory days in the reservation.

The getHotels operation in the Price Availability Rate (PAR) API is updated with a websiteAddress element in the response. This new element is within the hotelSummaryInfoType definition.

The getRoomsSummary operation in the Room Configuration API now includes Room Status, Component Room Info, and Component Suite Info in the response.

The copyRatePlans operation in the Rate API includes an approvalStatus element that allows rate code approval should the property have the Rate Code Approval OPERA Control activated.

The getHotelReservations operation in the Reservation API allows you to research by the externalReferenceLegId query parameter. This is useful when searching for itinerary reservations as they have the same confirmation number (external reference number) but different leg numbers.

The postReservationLinksByChain, postReservationLinks, and postReservationLinksByExtId operations in the Reservations API provide a new, optional request attribute for hotelId to define the property where a given reservationIdList belongs. A new optional query parameter hotelId is added to the getReservationIndicators operation to define the property where a given reservationId belongs. The hotelid is needed when the reservationId is no longer unique across properties in a multi-tenant environment.

For properties with the Relationships OPERA Control active, an Add Relationship action link is added for you to add a relationship.

A Refresh button is added to update the page with any changes made to an accompanying profile.

A Show Masked Information action is added for users with the View Identification Details task granted, displaying the unmasked Birth Date and Identification Number details.

See Managing Accompanying Guests.

For properties with Award Points Redemption OPERA Control active, the Redeem Awards checkbox is not available in Look to Book search when copying a reservation.

See Editing a Reservation.

Linked Reservations is updated to auto-generate a Linked Name identifier when splitting a multi-room reservation or linking individual reservations. This allows you to search for all linked reservations using the Linked Name identifier.

Departure Date, Room, Adults, and Children columns are added in the Linked Reservation panel.  

Share Reservations are excluded from the Linked Reservations panel, but continue to appear in the Additional Reservations tab. 

The Profiles Per Day and Reservation Traces OPERA Controls are updated as complimentary functions.

https://%OPERACLOUDURL%/bookmarks/reservation?externalSystem=<parameter-value>&externalRef=<parameter-value>&externalRefLegNo<parameter-value>&TPRESORT=<parameter-value>.

See Using Deep Links to Presentations Pages. 

Manage Task Sheet and Task Companion are updated to display Room and Room Type as links for displaying room and room type information.

Manage Task Sheet displays the Confirmation Number as a link for launching Manage Reservations if you have the Reservation Manage task granted to your role.

The Update Vacant Room Status OPERA Control is updated with a Custom option that allows you to configure rules for the Updating Room Statuses End of Day procedure to process, updating rooms of select room type(s) and vacant for a specified number of days, to a nominated housekeeping status. For example, you can configure rules to update vacant rooms to pickup status after 14 days, ensuring the vacant room is scheduled for a housekeeping task (for dusting and "running the taps" in the room). See Configuring Vacant Room Status.

RESV_NAME_ID is added to the guest_ledger.csv and the deposit_ledger.csv templates to accommodate multiple reservations with the same confirmation number. See About Importing Data.

The option to use external (non-Oracle) Simple Mail Transfer Protocol (SMTP) servers for email delivery is added. See Configuring SMTP Connections.

Email Delivery Management is updated with an Email Server Code list field for selecting an SMTP Server configuration.