Oracle Hospitality
Description | Plugin to handle individual guests, groups, ship's crew, staff, and temporary visitors data from Oracle Hospitality Cruise Shipboard Property Management System. |
Latest Version | 2022.20.1.1 |
Release Date | Oct 17, 2022 |
Download Path | |
Type | Replicator Plugin |
Change Log:
Description
Oracle Hospitality Cruise Shipboard Property Management System is a central database containing all guest and crew information. It enables cruise operators to manage individual guests, groups, the ship's crew, staff, and temporary visitors.
To be able to use Oracle Hospitality (OH) a minimum of personal bio data is required, this information is uploaded from Adonis Personnel Manager. To activate and deactivate the crew members account in OH, the crew member must be checked in and checked out. OH allows 3rd party software systems to check in and activate the account using the API, the check out process, due to the complexity of the process to settle the account, can only be performed inside OH. This can not be controlled by 3rd party software system suppliers like Adonis.
- 1.1 Change Log:
- 1.2 Description
- 1.3 Adonis → Oracle Hospitality
- 1.3.1 Crew Bio Data
- 1.3.2 Next Of Kin
- 1.3.3 Travel Documents
- 1.3.4 Planning
- 2 Houskeeping
- 3 APM setup
- 4 Workflow
Adonis → Oracle Hospitality
Crew Bio Data
Source Data-Group: Personnel Details
Oracle Hospitality | Adonis | Comment |
UXP_C_EXTERNALID | PIN | Employee Number |
UXP_A_NAME | LASTNAME | Last Name |
UXP_A_FSTN | FIRSTNAME | First name |
RES_V_GUESTID | RES_V_GUESTID | This is a composite key used in OH exiting out of the original sign-on date plus the persons pin number. |
UXP_H_MNAME | MIDDLENAME | Middle Name |
UXP_H_BIRTHD | BIRTHDATE | Date of Birth |
UXP_H_SEX | SEX | Sex |
UXP_H_NATION | NATIONALITY | Nationality |
UXP_A_STREET | ADDRESS1 | Address1 |
UXP_A_STREET2 | ADDRESS2 | Address2 |
UXP_A_CITY | CITY | City |
UXP_A_COUNTRY | ADDRESS_COUNTRY | ADDRESS_COUNTRY |
UXP_A_ZIP | POSTCODE | POSTCODE |
UXP_H_TELNO | PHONE | Home phone or mobile phone with priority 1 |
UXP_H_MARTIAL | MARITALSTATUS | If the marital status is "MARRIED" then M else N |
UXP_H_AGE | AGE | Age |
UXP_H_HEIGHT | HEIGHT | Height |
UXP_H_WEIGHT | WEIGHT | Weight |
UXP_H_EYES | EYECOLOR | Name of the color definitions |
UXP_H_HAIR | HAIRCOLOR | Name of the color definitions |
RES_CAB | CABIN | Cabin |
UPX_A_ID | EXTID | Received from Oracle Hospitality when inserting a new crew. |
UXP_A_ID | EXTID | Received from Oracle Hospitality when inserting a new crew. |
UXP_A_SALUT | TITLENAME | Titlename |
UXP_H_BIRTHP | PLACEOFBIRTH | Place of birth |
UXP_H_EMAIL | ||
RES_TAG | RES_TAG | Hardcoded 'C' |
UXP_A_TAG | UXP_A_TAG | Hardcoded 'C' |
UXP_A_GRP | UXP_A_GRP | Hardcoded 'CRW' |
UXP_A_OTHNAME | NATIVENAME | Nativename |
Next Of Kin
Source: Data-group:Family
Oracle Hospitality | Adonis | Comment |
---|---|---|
UXP_H_CONT_NAME | NNAME | NOK Name |
UXP_H_CONT_STREET | NADDRESS1 | NOK Address1 |
UXP_H_CONT_STREET2 | NADDRESS2 | NOK Address2 |
UXP_H_CONT_CITY | NCITY | NOK City |
UXP_H_CONT_ZIP | NZIP | NOK Zip |
UXP_H_CONT_COUNTRY | NCOUNTRY | NOK Country |
UXP_H_CONT_PHONE | NOK_PHONE | NOK Phone |
UXP_H_CONT_MOB_PHONE | NOK_MOBILE | NOK Mobile |
UXP_C_RELATIONSHIP | NRELATION | Nrelation |
UXP_H_CONT_EMAIL | NOK_EMAIL | NOK Email |
UXP_H_MOB_TELNO | MOBILE | NOK Mobile |
Travel Documents
The following travel documents are exported; Passport, and Seamansbook. These documents are identify by the travel document option document type: Passport or Seamansbook.
Oracle Hospitality | Adonis | Comment |
---|---|---|
UXP_H_PASSNO | TDNUMBER | Passport number |
UXP_H_PASSPI | ISSUEDWHERE | Passport IssuedWhere |
UXP_H_PASSPI_COUNTRY | ISSUE_COUNTRY | Passport IssueCountry |
UXP_H_PASSEX | PEXPDATE | Passport Expire Date |
UXP_H_PASSDI | PDATEFROM | Passport Date From |
UXP_A_OTHFSTN | NATIVENAME | Native name, in native language like Russian, Chinese |
UXP_C_BOOKNO | SBNO | Seamenbook Number |
UXP_C_BKDATE | SB_DATEFROM | Seamenbook Datefrom |
UXP_C_BKPASSPI | SB_ISSUEDWHERE | Seamenbook IssuedWhere |
UXP_C_BKPASSPI_COUNTRY | SB_ISSUE_COUNTRY | Seamenbook IssueCountry |
UXP_C_BKPASSEX | SB_DATETO | Seamenbook Dateto |
Planning
Oracle Hospitality | Adonis | Comment |
---|---|---|
UXP_A_GL_DEPARTMENT | DEPCODE | Department OrgCode |
UXP_H_STAFF_POS | POSITION_CODE | Uses XREF code See below |
RES_EMB_E | SONDATE | SignOn Date |
RES_SIGNONPORT_ID | SONPORT | SignOn Port |
RES_DIS_E | SOFFDATE | SignOff Date |
RES_SIGNOFFPORT_ID | SOFFPORT | SignOff Port |
UXP_H_STAFF_DIV | DEPARTMENT_CODE | Uses XREF code See below |
Houskeeping
Download the Plug-In
http://download.adonis.no/files/upgrade/PersonnelManager/Plugins/Replicator/AOH/
Installing the plugin
See : Installing and distributing the Replicator plug-in
Plugin Parameters
SERVER_NAME | APM Server name |
DATABASE | APM Database Name |
SERVICE_URL | URL Provided by Oracle Hospitality |
SERVICE_USER | Username Provided by Oracle Hospitality |
SERVICE_PSW | Password Provided by Oracle Hospitality |
XREF | Plugin XREF configured in Adonis (AOH) |
TRUNCDAYS | Number of days to store plugin logs |
DAYSGAP | Number of days (GAP) from TODAY, that defines starting point to pick up PINs for export. If not defined - default value is 21. The DATEFROM of Planned activity must be >= TODAY + DAYSGAP. If all planned crew should be exported starting from TODAY, then DAYSGAP should be 0. |
USEALTPIN | If =1, then to export ALTERNATIVE pin value instead of PIN to External ID field. |
SENDPHOTO | If =1, then to export PHOTO of a person. |
PLAINPSW | 1:= password will be send in plain text |
DEBUGLOG | 0:=Minum log |
APM setup
OH is installed on each vessel and does not have one main office database. Sending of data will therefore be done in the following way:
Data in APM is updated in the office or on the vessel.
Adonis Replicator for APM will send the data between the Adonis database in the office and the Adonis Database on a vessel as per schedule set in Adonis Replicator for APM
Adonis Replicator for OH will be installed on each individual vessel. Schedule will be set up to send data between the Adonis database onboard and the Oracle database onboard.
Setup to be done in Adonis:
1. Adonis Oracle Hospitality Interface.
In General Codes | Miscellaneous | Interfaces the Code AOH should be added:
2. Department setup.
Each Department in Organization structure or Rank in General Codes must be set up with corresponding OH code. If Department XREF code is blank, then XREF from Departments in General Codes will be checked.
Go to Set up | Organization. Locate a department and go to XREF tab. Select Append and add AOH as interface and add OH code.
3. Position/Rank setup.
Each Position in Organization structure or Rank in General Codes must be set up with corresponding OH code. If Position XREF code is blank, then XREF from Ranks in General Codes will be checked.
Go to Set up | Organization. Locate a position and go to XREF tab. Select Append and add AOH as interface and add OH code.
Workflow
Key points:
System checks a vessel, meaning that crew from other vessels will not be picked up.
Only crew with activity DATEFROM >= TODAY are picked up by plugin.
Plugin performs the following operation:
Get list of Current Seaservice activities (DATEFROM <= TODAY, DATETO IS NULL, PLANNED=N)
Update records of OHC by data of persons from activity's list if persons exist in OHC and status is not 'DD'
OHC – Oracle Hospitality Cruise
DD – status of a crew, already signed off/checked out.
Insert records into OHC if records do not exist in OHC and DATEFROM=TODAY
Get list of Planned Seaservice activities (DATEFROM >= TODAY, DATETO IS NULL, PLANNED=Y)
Insert records into OHC if records do not exist in OHC or records exist, but the status is 'DD'
Update records of OHC by data of person from the list if persons exist in OHC and status is not 'DD' and persons do not exist in Current activity's list.
To avoid duplicates, plugin recognizes existing crew in OH by passport number and Last name.
Creating a person in OH:
User will plan a person in Rotation module that will create a new planned sea-service activity for the person. Activity can also be created manually directly in Activities datagroup.
A crew member should also be added to crew change port as onsigner and offsigner.
Any dates changes should be done in APM only.
As an activity is linked to a vessel, the crew member’s basic data will be sent to OH and exported to the correct vessel.
The person will appear on the expected list in OH where expected sign-on date = Date From of the sea-service activity in Adonis.
Confirming a person Sign On:
User will confirm that a person has signed on in Adonis in Crew Change Module.
This information will be sent to OH, and the person will be moved from the Expected Sign on list, to Souls Onboard, Checked-in tab.
Reason for keeping this process in Adonis, is that Adonis is the system where all information needed in the sign-on process of the crew member is kept.
E.g. certificates, passport information, payroll information, contract, etc.
Normally the Purser will check that this information matches the physical certificates, travel documents and contract the crew member brings when he comes onboard.
Confirming a person Sign Off:
User will confirm that a person has signed off in OH, which means he will be removed from Souls Onboard and can be found on Checked-Out tab.
This information will be sent to Adonis, and the person will get status Confirmed signed off in Crew Change module, and his sea-service activity will be updated correspondingly.