1 Features and Updates

The content below is a list of features and updates for the Oracle Hospitality Cruise Property Management Border Control 23.2.0 release.

Tools and Technology Updates

The licensing terms have been updated. For detailed information, please refer to Licensing Information User Manual on the Oracle Help Center.

OHC Tools

Enhanced the Database Password Change feature to automatically update the Property Management System database credential when changing the password using Change Password or Change Database Encryption Key. A restart the API services is needed post password change. See chapter OHC Tools in Shipboard Property Management User Guide for more information.

Entry / Exit System (EES)

The application is designed with simplicity, ease of use while fully aligning to EES requirements, allowing users to perform necessary tasks and fulfill all requirements seamlessly.

In this release,
  • Departure Scheduled Date and Time field has been remodeled to capture the guest or passenger first port of entry into European country instead of the last European Port in previous versions.
  • Integrated the Border Control application into Role Manager function in Cruise Property Management System, allowing users to manage the Role Access from a single point. This feature is only applicable from SPMS versions 23.1.0 and later.
  • Enhanced the Manage EES Response File page to allow all EES status records to be deleted.
  • Enhanced the submission of the EES request file to use the eu-LISA System to System (S2S) interface method. The below are the changes in EES Setup page:
    • A new configuration section Carrier Interface Method were introduced, giving users the option to choose the transfer request file type.
    • In the Carrier Interface Method, users may choose to use the System to System option, which support EES request file transfers in JSON file format or select the Web Portal for request file in CSV file format
    • The use of System to System as a carrier interface method would generate the EES Request file in JSON file format. This feature will connect to eu-LISA endpoint via an API call to process the file generate
    • Configuration such as Carrier ID, Service Provider ID and EES endpoint URL is needed if the preferred interface method is System to System.
    • This enhancement also changes the EES Response file processes. For System to System option, the process of uploading the response file is no longer needed. The system automatically receives the response request via the API call and update the status for each of the records.

      However, if the carrier interface method Web Portal is the preferred, manual uploading of the EES Response file remains unchanged.